Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    emard
    @emard
    I have jessie and upgrade crashed so imaged SD minimal image with dd
    Lawrie Griffiths
    @lawrie
    I have a large collection of Raspberry Pis, but am trying the one with the LCD screen as I used to use that as a portable FPGA development system.
    emard
    @emard
    build completed, will copy executable to /usr/local/bin :)
    
    ./openocd --version
    Open On-Chip Debugger 0.10.0+dev-01230-g33f5b081-dirty (2020-10-03-19:45)
    so, I have new openocd, fujprog and openFPGALoader compiled on RPI3, so far so good :)
    Now a small pause and soldering
    Dolu1990
    @Dolu1990
    No hurry ^^
    Tomorrow, if things are connecting, i can debug
    Goran Mahovlic
    @goran-mahovlic
    @ThomasHornschuh sorry on trouble I will try to fix links tomorrow ...
    Lawrie Griffiths
    @lawrie
    @Dolu1990 Does it complicate things at all for your debugging that for a green 85f, which has the flash problem, @emard currently has a 2-cpu configuration?
    emard
    @emard
    Escape character is '^]'.
    Open On-Chip Debugger
    > init 
    > scan_chain
       TapName             Enabled  IdCode     Expected   IrLen IrCap IrMask
    -- ------------------- -------- ---------- ---------- ----- ----- ------
     0 fpga_spinal.bridge     Y     0x10001fff 0x10001fff     4 0x01  0x0f
    Got openocd to connect
    Dolu1990
    @Dolu1990
    @lawrie No worries with the multi core, basicaly, the openocd script i use put all core to halt excepted the 0
    @emard Cool :D
    Let's try to sync tomorrow for some debug ^^
    If you have time
    emard
    @emard
    Yes, tomorrow!!! I have time most day I must goto sleep() now;
    drr
    @danrr_au_twitter

    that is some impressive progress on saxon + ulx3s. this project seems to move very, very fast

    Does it complicate things at all for your debugging that for a green 85f, which has the flash problem

    @lawrie What flash problems are there on the green board? If it's ISSI flash specific then very curious since I haven't confirmed my own flash reader works on non-winbond parts

    Are there also any other major functional differences (apart from SDRAM and flash config) between blue vs green?

    emard
    @emard
    @danrr_au_twitter I can partly answer, board schematics/constraints are practically the same from user point of vew, but boards are produced at different time so different pin-compatible parts on them. Main aspects are green = v2.1.2 PCB, ISSI 16MB flash + micron 32MB SDRAM + ESP32 w/4MB FLASH older, blue = v3.0.7 PCB = Winbond 16MB flash + micron 32MB SDRAM + ESP32 w/4MB FLASH, newer. "green" is not a good term because there are new latest "greens" from CS, they have v3.0.8 PCB = Winbond 16MB flash + ISSI 32MB SDRAM + ESP32 w/16MB FLASH even newer than at blue.
    Dolu1990
    @Dolu1990
    @emard i'm setuping some stuff for the debug
    emard
    @emard
    I will open outside ports in few minutes so you can remote ssh
    Dolu1990
    @Dolu1990
    So the target that you setuped has which sdram and which flash ?
    thanks :)
    emard
    @emard
    its v2.1.2 green prototype board, ISSI flash and 32MB micron. I must look at the discussion history which exact ISSI part number
    IS25LP128FBLE 16MB ISSI
    Dolu1990
    @Dolu1990
    and there is two CPU cores right ?
    emard
    @emard
    Yes 2 cores and on SD cards FAT root is "green" dtb and uImage. This SD has no ext2 fs yet, but if we come so far I will replace SD with one that has rootfs
    Currently flash ID = 0xFF and reading first bytes is all FFFFFFFFFFF
    On the pi home directory is "ecp5_prog", there you can "fujprog ulx3s_85f_green_2core_saxonsoc.bit" or "fujprog ulx3s_85f_passthru.bit" for example
    Lawrie Griffiths
    @lawrie
    @Dolu1990 The bitstream that @emard is using, if it the latest from my saxonsoc-ulx3s-bin repository was built using the mdio branch.
    Lawrie Griffiths
    @lawrie
    @emard I thought it was the openocd and gdb ports (4444 and 3333) that @Dolu1990 needed, rather than ssh, so he can connect to openocd with gdb remotely.
    Dolu1990
    @Dolu1990
    hoo right, need both
    hmmm
    emard
    @emard
    ports 3333 and 6666 open, do you want additionaly 4444
    Dolu1990
    @Dolu1990
    Yes it might be quite usefull
    emard
    @emard
    currently open 2222, 3333, 4444, 6666
    Dolu1990
    @Dolu1990
    Thanks
    Those number remember me those old adds to download music / app on old mobile XD
    Lawrie Griffiths
    @lawrie
    @emard What is ecp5_prog on the Raspberry Pi and where does that come from?
    emard
    @emard
    :) I enabled them as DNAT at access point, let me know do they work. ecp5_prog is in my RPI3 a subdirectoy with some silly openocd test scripts
    It has also bitstreams 85F passthru and copy of your green 2 core, to be fujprog'd. Its home directory content
    Dolu1990
    @Dolu1990
    Got the core connected and can read sdram from telnet
    emard
    @emard
    eheheheeee wonderful, RPI3 is blinking as usual :)
    Dolu1990
    @Dolu1990
    can connect with gdb, all good ^^
    emard
    @emard
    Hohoohooo :))
    Lawrie Griffiths
    @lawrie
    @emard So do you have fujprog built for the RPi as well?
    emard
    @emard
    Yes and openFPGALoader too
    Maybe fujprog has some bugs related to -t option I'm not sure it works perfectly, but it can upload bit
    Dolu1990
    @Dolu1990
    @emard I will bypass the boot loader for now and see if vex-linux can access the spiflash
    Do you have a 2 cores ready sdcard under the hand ^^ ?
    emard
    @emard
    Yes, the sdcard is inside only with vfat, only it has no ext2 rootfs