Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    emard
    @emard
    @vmedea Yes blink bit makes linux FB show orange as yellow, and it actually blinks in linux terminal, incrasing colorfulness of the board, thenx :)
    pushed new tetris :)
    Erik Piehl
    @Speccery
    @kost no change for me with the new version. I wonder if my FTDI drivers are somehow broken
    kost
    @kost
    stupid question. have you connected it to the USB (US1)? USB (US2) will not work. Also, do you get the micropython terminal screen when run screen /dev/tty.usbserial-XXXX
    ?
    Erik Piehl
    @Speccery
    Yes I am using US1. Again, the old ujprog works (with adding 3.0.8). Micropython I haven't tried
    kost
    @kost
    how about openfpgaloader with --board specified?
    Erik Piehl
    @Speccery
    micropython does respond (I needed to provide bitrate of 115200).
    Eriks-MacBook-Pro:icy99 perik$ sudo openFPGALoader --board ulx3s ti994a_ulx3s.bit unable to open ftdi device: -5 (unable to claim usb device. Make sure the default FTDI driver is not in use) Error: Failed to claim cable
    kost
    @kost
    will try on my colleagues macbook with Catalina if I can reproduce.
    Have you tried installing these? https://www.ftdichip.com/Drivers/VCP.htm
    Erik Piehl
    @Speccery
    I think so, but let me do that again. Installing 2.4.4.
    I did run it again, no change. This actually makes me wonder if the drivers were properly installed, since when I did run this in the past, I needed to use System Preferences/Security to allow access for the kext.
    kost
    @kost
    but you see ftdi loaded with kextstat or ?
    Erik Piehl
    @Speccery
    195 0 0xffffff7f85521000 0x7000 0x7000 com.FTDI.driver.FTDIUSBSerialDriver (2.4.4) B137605C-32D8-3E81-89B6-E1F8039FC427 <100 60 6 5 3 1>
    That's the output of kextstat
    kost
    @kost
    ~/code/mygithub> sudo kextstat | grep -i ftdi
  222    0 0xffffff7f83aa5000 0x3000     0x3000     com.apple.driver.AppleUSBFTDI (6.0.0) E35C349C-8115-37BA-B4C9-8034D1ED8B8B <221 63 23 6 5 3 1>
~/code/mygithub> fujprog blink/blink_12f.bit
ULX2S / ULX3S JTAG programmer v4.6 (git 720e92b built Oct  7 2020 10:53:42)
Copyright (C) Marko Zec, EMARD, gojimmypi, kost and contributors
no root permissions, not handling kexts
Using USB cable: ULX3S FPGA 12K v3.0.8
Programming: 100%
Completed in 8.32 seconds.
    I see difference here in kexts
    Erik Piehl
    @Speccery
    Thanks, good catch. Yes you have 6.0.0. I wonder if this is coming from Apple directly.
    kost
    @kost
    maybe running manually: /sbin/kextunload -bundle-id com.FTDI.driver.FTDIUSBSerialDriver and/or /sbin/kextunload -bundle-id com.apple.driver.AppleUSBFTDI
    Erik Piehl
    @Speccery
    Magic! That worked! Thank you so much. I ran sudo /sbin/kextunload -bundle-id com.FTDI.driver.FTDIUSBSerialDriver and then openFPGAloader worked!
    kost
    @kost
    I guess fujprog will work as well
    Erik Piehl
    @Speccery
    Yes it does. No root needed. Interestingly sudo kextstat | grep -i ftdi returns nothing, but things work. Thank you so much @kost
    Erik Piehl
    @Speccery
    I think it was the driver issue all along. I also prepared a Xcode project to debug easier (using the older source code, without serial=NULL on line 525). I just got the project together, and it works too.
    kost
    @kost
    @Speccery you're welcome. glad we managed to troubleshoot it.
    Erik Piehl
    @Speccery
    Yes, thanks for your real-time help. I also learned a few useful commands as well :)
    sxpert
    @sxpert
    this may be related with the new "we don't like kext anymore" policy from apple
    Paul Ruiz
    @pnru_gitlab

    From memory, I think Apple included native FTDI drivers from High Sierra (10.13 - maybe even Sierra 10.12) onwards and in my old private ujprog builds I had the kext lines commented out.

    Probably if you had the FTDI written drivers installed before that, the automatic upgrades grandfathered them in. There is a lot of outdated information on MacOS and FTDI on the web. Maybe it makes sense to have a few lines about this in a Getting Started page for fujprog

    kost
    @kost
    currently, kext are handled if you provide root perms. if you run as user those lines are not executed anyway.
    kost
    @kost
    but thanks @pnru_gitlab on suggestion. definitively is needed to document. including that if you have this line: 
    195 0 0xffffff7f85521000 0x7000 0x7000 com.FTDI.driver.FTDIUSBSerialDriver (2.4.4)
    it will not work
    kost
    @kost
    will have to work on documentation, I guess ;)
    Joseph Tang
    @josephtang3_gitlab
    where is GN pins for CPU softcore? how to connect RPi3 to these pins?
    Dolu1990
    @Dolu1990
    https://github.com/SpinalHDL/SaxonSoc/blob/dev-0.1/hardware/synthesis/radiona/ulx3s/smp/ulx3s_v20_linux_uboot.lpf#L342
    so GN0 to GN3
    Paul Ruiz
    @pnru_gitlab

    Yes it does. No root needed. Interestingly sudo kextstat | grep -i ftdi returns nothing, but things work. Thank you so much @kost

    That is probably related to what @sxpert said earlier. In Catalina, kernel extensions (kext) are being phased out and replaced by system extensions (essentially user mode drivers). It seems that the Apple FTDI driver has already become a system extension in 10.15.7, and hence kextstat does not list it. Probably the best thing to do is to uninstall the old FTDI kext on Catalina systems where it is still grandfathered.

    Lawrie Griffiths
    @lawrie
    @josephtang3_gitlab Which softcore are you asking about?
    Goran Mahovlic
    @goran-mahovlic
    @emard where do we hold ESP32 mouse/keyboard example for Oberon - and do we have prebuild bitstream for this version
    headkaze
    @headkaze
    My ULX3S just shipped! Woot!
    Joseph Tang
    @josephtang3_gitlab

    @josephtang3_gitlab Which softcore are you asking about?

    https://twitter.com/RadionaOrg/status/1313054364815314944?s=20

    Lawrie Griffiths
    @lawrie
    Ah, that was using SaxonSoc Linux, but the RPi was only being used as a convenient server to put on the internet so that @Dolu1990 could remotely diagnose a problem with Ulx3s boards that have the ISSI flash chip. @Dolu1990 used remote Jtag debugging. @emard connected openocd on the RPi via a ft2232 usb jtag device connected to the GN 0-3 pins on the Ulx3s. It is not something you would usually need to do, but it is rather cool being able to do remote debugging from Switzerland to Croatia over the internet.
    Joseph Tang
    @josephtang3_gitlab
    @Dolu1990 thanks!!
    @lawrie thanks!!
    derekmulcahy
    @derekmulcahy
    When trying to build blink I get an error from ecppack
    Failed to process input config: unrecognised config entry .sysconfig
    I saw the previous discussion and installed the latest from the kost repository but it didn't fix it.
    Trying https://github.com/open-tool-forge/fpga-toolchain/releases ...
    Paul Ruiz
    @pnru_gitlab
    Thinking a bit more about fujprog on Catalina, and why ujprog was working for @Speccery This code in fujprog should have unloaded the unwanted kext:
    https://github.com/kost/fujprog/blob/master/fujprog.c#L898-#L912
    In ujprog the similar code does not have the user id checks:
    https://github.com/f32c/tools/blob/master/ujprog/ujprog.c#L753-#L759
    It would seem to me that the user id checks in fujprog are not correctly recognising sudo.
    emard
    @emard
    @goran-mahovlic esp32ps2 is here https://github.com/emard/esp32ps2 for oberon it should follow "pygame" to export both keyboard and mouse. I haven't long time used it so some pinouts between oberon and esp32 may need to be reviewed perhaps modified and recompiled
    Lawrie Griffiths
    @lawrie
    @derekmulcahy The problem is definitely due to prjtrellis being out of date, so I am surprised if @kost's latest build did not fix it. Are you sure you have that first on your PATH? Commenting out the sysconfig in the lpf file probably fixes it too.