Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    Dolu1990
    @Dolu1990
    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
    Dolu1990
    @Dolu1990
    hoo right
    emard
    @emard
    I can replace SD with another which has ext2
    Dolu1990
    @Dolu1990
    I'm on uboot right now
    So
    Lawrie Griffiths
    @lawrie
    How did you get to u-boot? Have you solved the flash problem?
    Dolu1990
    @Dolu1990
    i didn't solved the flash problem, just loaded opensbi and uboot via openocd and booted on it
    I can try to do the same for linux and the rootfs
    i have to check, i remember that the 32 MB sdram was just not enough for the ramfs XD
    I will give a try
    without the sdcard
    Paul Ruiz
    @pnru_gitlab
    @emard Tank you for the post about what version is what above. Once on the ULX3S pages there was a table with all ULX3S production runs, but I cannot find the link right now. I think it would be a good idea to update this table and extend it with a few columns detailing ram/flash details and giving each line (other than independent builds) a batch number or something that people can refer to. I'm a regular reader of this gitter and always confused about the meaning of "green 85", etc. A table would help.
    Lawrie Griffiths
    @lawrie
    @Dolu1990 We did eventually run with ramfs in 32MB.
    Dolu1990
    @Dolu1990
    Yes, but the ramfs growed quite a bit ^^
    emard
    @emard
    @pnru_gitlab This is good idea, when I still remember what parts are soldered onboard. This list is at the end of MANUAL.md
    Paul Ruiz
    @pnru_gitlab
    So far I have never played with code that was sensitive to flash/sdram differences but probably I will stumble into it at some point. I have two boards, both of which are "Goran specials" I think,
    emard
    @emard
    Yes, the boards have been bought in skriptarnica cheap, then goran was replacing better parts and adding esp32 manually then sending because there was lot of demand and production was slow
    Paul Ruiz
    @pnru_gitlab
    @emard yes, that is the table I was thinking of. Maybe the production dates are already "batch numbers". So an "old green 85F" is a "Sep-2018 85F", a blue 85F is a "Nov-2019 85F" and a "new green 85F" is a "Jul-2020 85F". I assume each run uses the same sdram and flash, and only the ECP5 differs. Correct? Are there meaningful differences in other parts as well? (e.g. ESP32 hardware).
    Lawrie Griffiths
    @lawrie
    I think "blue 85F" is fairly specific as it refers to one batch of blue 85F boards with 64MB of SDRAM. "green 85F" refers to a variety of green 85F boards with different chips, but I believe they all (apart from perhaps emard specials) have 32MB of SDRAM, which is what is important for SaxonSoc builds. It seems to be the ones with the ISSI flash chips which have the problem with SaxonSoc.
    emard
    @emard
    @pnru_gitlab I'm now pulling my memory and trying to make some table with PN's. There can bi some mistakes even I'm not too shure. But "BLUE" is distinctive, made by watterott and not too many have them
    Goran Mahovlic
    @goran-mahovlic
    Yes, "blue 85F" was small production in Germany with 64Mb SDRAM
    Green boards are made by KonĨar with random mouser available 32Mb SDRAM