Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    emard
    @emard
    Lawrie found that FLASH needs some POWER ON command before being useable
    Lawrie Griffiths
    @lawrie
    @e2kgh I You can now do SDRAM_SIZE=32 CPU_COUNT=2 saxon_netlist, and FPGA_SIZE=85 saxon_bitstream. Is that good enough for what you want?
    emard
    @emard
    Also we must be aware that lattice FPGA itself talks to flash initially and sends some commands and potentially leaves it in state different than power on default
    Lawrie Griffiths
    @lawrie
    @emard Yes, waking up the chip was one thing that I thought might be the problem. I had that problem with SaxonSoc on ice40 boards. I don't know if is that or some other issue that @Dolu1990 wants to test.
    If wake-up is the problem, loading the bistream from flash could possible fix it, as that might leave the flash memory powered on. On ice40 boards there is an option in the bitstream to say whether to put the flash chip to sleep or not after loading from flash, but I don't think ecp5 has that option. Alternatively doing something else that powers up the flash chip and leaves it on before programming the bitstream could fix it.
    Lawrie Griffiths
    @lawrie
    @emard I have started looking at putting PPPD and SCREEN bach. We seem to have lost the BR2_PACKAGE_PPPD and BR2_PACKAGE_SCREEN. I have added those but I don't know if I need any other options. The kernel has CONFIG_PPP and CONFIG_PPP_ASYNC, so pppd ought to work.
    When I type screen I get:
    root@buildroot:~# screen
    socket: Address family not supported by protocol
    I seem to remember that from before. How do you plan to use screen?
    emard
    @emard
    I need screen for multi-terminal use. Maybe it needs some IP address or similar assigned to start hmm
    Currently I got 12F booted with latest audio kernel and now I will transfer some mp3
    Lawrie Griffiths
    @lawrie
    I don't think we got screen working before.
    I can add the image of the rootfs that includes screen and pppd if you like, so you can investigate.
    I don't think the problem with flash memory is the wake-up as SaxonSoc does a wake call - https://github.com/SpinalHDL/SaxonSoc/blob/dev-0.1/bsp/radiona/ulx3s/smp/app/bootloaderConfig.h#L70
    emard
    @emard
    great
    Lawrie Griffiths
    @lawrie
    @Dolu1990 Could we add a test that the flash copy to SDRAM has worked in the bootloader. For example check the first few bytes or compare the SDRAM with the flash memory?
    emard
    @emard
    I think screen worked if logged over the network. For flash I can try tu run ecp5.flash_read or similar. I can also try to erase boot flash (passthru) and things like this
    Lawrie Griffiths
    @lawrie
    I have added a new version of rootfs.tar.gz to images. It contains pppd and screen.
    emard
    @emard
    Right I will download! I am listening to mp3 and it WORKS!!!
    Lawrie Griffiths
    @lawrie
    It works better on the blue 85F with 4 cpus, as it doesn't slow down other stuff.
    emard
    @emard
    4-core is really powerful :) I will retry green 85f!
    e2kgh
    @e2kgh
    The boards which should be available from Mouser, are all "blue"?
    emard
    @emard
    They are green but have winbond flash and I have 12F it boots saxonsoc. blue iwas produced by "watterott" germany in some quantity about 100 pcs but I dont know if they produced more (probaby some)
    Currently the blue only has 64MB they probably found cheap enough source around 2-3$ I guess. current 64MB on Mouser are all 10$ or more so Goran decided to put 32MB, I found some ISSI that is around 2$ and has grade 7
    Dolu1990
    @Dolu1990
    @lawrie Sure we can
    e2kgh
    @e2kgh
    @lawrie : On the saxon web, you're(?) writing that for the 64MByte Memory, the :
    saxon_standalone_compile bootloader CFLAGS_ARGS="-DSDRAM_TIMING=AS4C32M16SB_7TCN_ps"
    SDRAM_SIZE=64 saxon_netlist
    FPGA_SIZE=85 saxon_bitstream
    should run. But isn't the :
    saxon_standalone_compile sdram_init CFLAGS_ARGS="-DSDRAM_TIMING=AS4C32M16SB_7TCN_ps"
    missing?
    Dolu1990
    @Dolu1990
    sdram_init is only used if you want to use openocd to connect to the FPGA
    i mean, to connect to the SoC
    e2kgh
    @e2kgh
    Ah! OK!
    Lawrie Griffiths
    @lawrie
    @emard I am guessing that we need CONFIG_UNIX=Y for screen to work. As that enables Unix domain sockets, and screen does things like if ((s = socket(AF_UNIX, SOCK_STREAM, 0)) == -1)
    emard
    @emard
    yes unix doman sockets are needed for many similar things
    Lawrie Griffiths
    @lawrie
    Sockets need adding to the lcc C library sometime.
    emard
    @emard
    Oh well yes it can be on todo list :)
    Lawrie Griffiths
    @lawrie
    Adding CONFIG_UNIX=Y did not fix screen.
    Lawrie Griffiths
    @lawrie
    It made no difference to the size of the kernel, so presumably that option was already on.
    emard
    @emard
    If you have network functionaly, can you try to telnet or ssh to saxonsoc and then try screen?
    BTW 85F I have here has only 32MB SDRAM so first memtest fails
    Lawrie Griffiths
    @lawrie
    I don't have any network functionality.
    Dolu1990
    @Dolu1990
    what is the linux.config / buildroot defconfig you are using ?
    Lawrie Griffiths
    @lawrie
    I have just added BR2_PACKAGE_PPPD=Y and BR2_PACKAGE_SCREEN=Y to spinal_ulx3s_defconfig.
    I tried adding CONFIG_UNIX=Y to linux.config, but that made no difference.
    Dolu1990
    @Dolu1990
    that should have been enough
    weird
    and you rebuilded the whole buildroot from scratch ?
    Lawrie Griffiths
    @lawrie
    Yes, but we got the same error with screen on the old version of SaxonSoc.
    Dolu1990
    @Dolu1990
    ahhh