Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    emard
    @emard
    Do i need gcc or clang to compile?
    Dolu1990
    @Dolu1990
    hmmm
    no no
    i mean
    hmmm
    to compile openocd ?
    then
    cd openocd_riscv
    ./bootstrap
    ./configure --enable-ftdi --enable-dummy
    make
    the thing is i don't know how to enable the rasberry pi gpio based jtag XD
    emard
    @emard
    I have usb-ft2232, not a gpio based
    I'm currently resolving debian dependencies for rpi3 to start building openocd
    configure passed, now make started... It should run for some time, I remember my adventures on getting ft231x support into openocd ... I recommend this to everyone with too much free time :)
    Dolu1990
    @Dolu1990
    XD
    emard
    @emard
    src/target/vexriscv.c:28:10: fatal error: yaml.h: No such file or directory
     #include <yaml.h>
    Is yaml some system package
    emard
    @emard
    ups I have small problem
    Dolu1990
    @Dolu1990
    hoooo
    emard
    @emard
    root@raspberrypi:~# apt-get install yaml
    Reading package lists... Done
    Building dependency tree       
    Reading state information... Done
    E: Unable to locate package yaml
    Dolu1990
    @Dolu1990
    libyaml-dev
    emard
    @emard
    yeeees this one exists
    Dolu1990
    @Dolu1990
    sudo apt-get install libtool automake libusb-1.0.0-dev texinfo libusb-dev libyaml-dev pkg-config for the full depedency on debian
    emard
    @emard
    make continues, and I started dependency install
    Lawrie Griffiths
    @lawrie
    I am going to try this on one of my Raspberry Pis, but I have not used it for a while so am doing an upgrade first.
    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