Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    Paul Ruiz
    @pnru_gitlab
    Sorry - I am behaving like a cat dragging random stuff into the house.
    Dolu1990
    @Dolu1990
    magnificent
    no no, that's nice
    Paul Ruiz
    @pnru_gitlab
    It seems that the JESD252 document is not freely available. It also seems to be quite new - so this may be something that is coming, not something that has been around for a while. It does indicate that other ways to achieve a reset were perhaps not so easy - as we are experiencing.
    Dolu1990
    @Dolu1990
    Just tried, it do not seem to have any impact
    But now we will mesure the pins, to be sure we do what we think we do ^
    Lawrie Griffiths
    @lawrie
    @ThomasHornschuh That version of SaxonSoc is a bit out of date. We are currently running the newer Smp version. @kost has not yet built an Smp version, but there are versions in my repository - https://github.com/lawrie/saxonsoc-ulx3s-bin/tree/master/Smp. Currently, you have to create the sd card manually for this version and it now has 2 partitions, the first being FAT32.
    However, the version you are using should work. Can you look at the sd card from your Linux machine to see if it contains a sensible ext2 partition?
    You could try taking out the sd card and putting it back in when in u-boot and then doing mmc rescan and mmc part, and it it lists partitions, do "boot".
    Thomas Hornschuh
    @ThomasHornschuh
    My problem is solved, the first SD card was "dead". Bit strange anyway, because I was sure that it worked before.
    Paul Ruiz
    @pnru_gitlab

    Ok, I've done a bit more reading and also scanned the ISSI datasheet. You guys probably already thought of all the below, but just to make sure. My current understanding of the "all cases covered" reset sequence is as follows:

    • set CLK low and CS high
    • wait for 15ms to give time to any command (other than erase types) to complete
    • send 0xAB, 0xFF, 0xFF, 0xFF, read ID byte in quad mode
    • wait 5us
    • send 0x66, 0x99 in quad mode
    • wait 35 us
    • make sure that HOLD & WP are high.
    • send 0xAB, 0xFF, 0xFF, 0xFF, read ID byte in regular SPI mode
    • wait 5us
    • send 0x66, 0x99 in regular SPI mode
    • wait 35 us

    Larry Wall once observed that "given enough eye balls, all bugs are shallow". It seems to me we don't have enough eye balls yet :^)

    Dolu1990
    @Dolu1990
    XD
    thanks ^^
    Hmmm, yet i don't have the quad mode in the hardware
    Thomas Hornschuh
    @ThomasHornschuh
    This time I wrote the image with SD Imager from Windows, unfortunately there is no way for VMWare to pass a raw SD card to a Linux VM. Currently I have no computer with an SD card reader booting Linux natively
    But anyway, I was sucessfull. I will take a look into the newer SaxonSoC in the next days. I was observing this gitter channel briefly in the past few months waiting or my board to arrive. But today my goal was to bring the board up running, mission acomplished !
    Lawrie Griffiths
    @lawrie
    I use a USB sd card reader with the VirtualBox VM that I use.
    Paul Ruiz
    @pnru_gitlab
    @ThomasHornschuh What OS is the machine with the SDCard reader natively using?
    Thomas Hornschuh
    @ThomasHornschuh
    Thank you to everyone helping me today. I have never seen an FPGA board with such an active community before, I'm looking forward for doing more with ulx3s !
    Paul Ruiz
    @pnru_gitlab
    @Dolu1990 I am not sure I understand Autoboot Mode well, but it seems to me that after the 15ms wait one must read at least one byte (i.e. do 8 clocks with CS low, then set CS high) to make sure to exit this mode. I guess one could send NOP on the output line for this.
    Thomas Hornschuh
    @ThomasHornschuh

    @ThomasHornschuh What OS is the machine with the SDCard reader natively using?

    It is my Laptop with Windows 10 and an internal SD card reader, but I think I will give @lawrie recommendation of using an USB reader I try. VMWare can pass USB transparently to VMs (it works e.g. with USB disk drives), but the SD Card reader in Laptops are often a Realtek PCIE chip

    Dolu1990
    @Dolu1990
    @pnru_gitlab I'm adding the NOP to try
    Lawrie Griffiths
    @lawrie
    @ThomasHornschuh Yes, on my Windows 10 laptop, I use the built in SD card reader only from Windows, but the VirtualBox VM can access the USB card reader fine. VMWare is probably similar. I am currently using Ubuntu 20.04 in my VirtualBox VM.
    Paul Ruiz
    @pnru_gitlab
    This may be an option: https://www.balena.io/etcher/
    It has binaries for Win, Lin & Mac
    Lawrie Griffiths
    @lawrie
    @emard Did you ever try loading the SaxonSoc bitstream from flash, to see if that leaves the flash memory in a more consistent state?
    Dolu1990
    @Dolu1990
    Hooo right
    that's something i wanted to try XD
    emard
    @emard
    @lawrie Yes of course I have tried to flash saxonsoc directly to 85F flash, but in my experiments was the same
    Dolu1990
    @Dolu1990
    Where are the source of the ecp5 library used in micropython ?
    emard
    @emard
    https://github.com/emard/esp32ecp5 but ecp5.py is already the source itself, around are some readmes and various stuff
    Thomas Hornschuh
    @ThomasHornschuh

    This may be an option: https://www.balena.io/etcher/
    It has binaries for Win, Lin & Mac

    Ok. Thanks for the link. I used a different tool Win32DiskImager. It was sucessfull. Still no idea why my first SD card died...

    Ed Bordin
    @edbordin
    Hey @emard I'm just playing around with the highres mode of ecppll and I noticed it when I run ecppll -i 25 -o 96 --highres -f /dev/stdout some code you contributed annotates (* FREQUENCY_PIN_CLKOP="96" *). Am I missing something or should that frequency actually be ffeedbackas calculated here? https://github.com/YosysHQ/prjtrellis/blob/74f2c76/libtrellis/tools/ecppll.cpp#L317
    (it probably doesn't affect the functionality, but I'm just trying to figure out what's going on so I can manually add a couple of extra outputs to the generated config)
    emard
    @emard
    @edbordin ecppll has bugs in the float-to-integer math that calculates its internal parameters. I tried to make it better, integer-only and inside of the language, not the external script, so my hopfully better ecp5pll is here: https://github.com/emard/ulx3s-misc/tree/master/examples/ecp5pll
    Ed Bordin
    @edbordin
    @emard oh that's cool you can do it all in vhdl! maybe I will try to look at how your implementation works and see if I can help contribute bugfixes to ecp5pll for verilog users
    I actually found that when I tried to use the ecppll --highres output it caused nextpnr errors because it had connected CLKOP and CLKOS to the same net
    emard
    @emard
    Yes I managed to make the same both in vhdl and systemverilog. I havent implemented all the possible features, upgrades/pullrequests are welcome.
    Ed Bordin
    @edbordin
    I do like having the option to edit generated files, but your approach looks really easy to use! nice work :)
    e2kgh
    @e2kgh
    @ThomasHornschuh : I also work on a Win10 laptop and VMware. No problems writing my sdcard via USB.
    Niko-La
    @Niko-La
    Hi everyone. happy to join this lobby and learn about open source fpga :)
    Goran Mahovlic
    @goran-mahovlic
    @Niko-La Hi, and welcome!
    Lawrie Griffiths
    @lawrie
    My Pmod collection has now arrived from Crowdsupply.
    emard
    @emard
    pmods originals wow plenty of devices to add :)
    Dolu1990
    @Dolu1990
    @pnru_gitlab Emard got the good call, it was the holdn/wpn pins which where glitching because of crosstalk and possibily too week pullup XD
    Now it is solved
    all works
    and pushed in the dev-0.1 branch
    emard
    @emard
    Amazing news, I assembled remote RPI3 with ULX3S connected with USB to US1 port and with USB-FT2232 JTAG to GN pins for softcore CPU. RPI3 can remotely power cycle the board. Also LA was used with SOIC-8 clip directly to FLASH chip. And we found crosstalk at WP and HOLD lines that were confusing ISSI flash which didn't respond to 0xAB in this case
    @Dolu1990 had remotely logged to RPI3 and fixed saxonsoc to work :)
    Goran Mahovlic
    @goran-mahovlic
    wow!