Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    emard
    @emard
    I tried it and behaves mostly the same
    kost
    @kost
    nice progress.
    regarding uart problem. i have tried to lower baudrate on slirp down to 2400 and mtu/mru to 296 which is recommended values for slow links, but it doesn't help.
    I have managed to transfer bigger files by setting block size in ftp to lower value and to introduce delay between transferring of blocks.
    pip install microftp
    microftpcmd --host 192.168.5.7 --delay 0.3 --block 32 -v -d --user root put ~/wget /root/wget
    of course, you should not perform any other action over serial line (like telnet to ulx3s in parallel). and it is pretty slow, of course. so, works for smaller files.
    kost
    @kost
    i find microftp useful to automatize upload of bitstreams to fpga as well as I can do it as oneliner:
    For example:
    microftpcmd --host 192.168.4.1 put  saxonsoc-ulx3s-85f.bit fpga
    Lawrie Griffiths
    @lawrie
    There are u-boot versions in saxonsoc-ulx3s-bin/linus/u-boot now.
    The only difference is that if you are using an 85f with 64MB you need to use sdimage64 which contains a dtb that specifies 64MB of memory, and you should then use saxonsoc-ulx3s-linux-85f-64.bit. For the green 85F with 32MB use saxonsoc-ulx3s-linux-85f-32.bit.
    They should work with any flash chip as they wake up the flash chip.
    Rangel Ivanov
    @ironsteel
    Hi guys! Is the ulx3s pin map (.lpf) identical for all FPGA sizes for the BGA 381 package?
    Lawrie Griffiths
    @lawrie
    I use the same one for the 12F and 85F.
    Rangel Ivanov
    @ironsteel
    cool, thanks! I came to the same conclusion after checking the kicad project but I wanted to make sure
    Lawrie Griffiths
    @lawrie
    Here is a README on building SaxonSoc Linux from source - https://github.com/SpinalHDL/SaxonSoc/tree/dev/bsp/Ulx3sLinuxUboot
    emard
    @emard
    @ironsteel yes lpf is identical for all fpga sizes 12-85F because the PCB is designed to accept all chips. Chips slightly differ in available pins and only common pins to all sizes have been used, so far I think there are no bugs in this direction :)
    Rangel Ivanov
    @ironsteel
    Great! That's really convenient!
    Lawrie Griffiths
    @lawrie
    I added a README for running the u-boot version from binaries - https://github.com/lawrie/saxonsoc-ulx3s-bin/blob/master/linux/u-boot/README.md
    emard
    @emard
    @lawrie great, seems clear and easy for anyone starting from 0 to linux prompt
    emard
    @emard
    @lawrie if sdcard images for 32/64MB RAM differ only in a single small file, I'd have 32MB default and place both dtb_32MB and dtb_64MB on sdcard and have some symlink ln -s dtb_32MB dtb. So after reboot 64MB is used instead of 32MB
    I mean after changing this symlink and reboot then 64MB I forgot to mention but it's obvious
    emard
    @emard
    @lawrie another question, will changing u-boot default commandline parameters permanently work like this (suppose I want to change partition to boot from):
    NAON#setenv bootargs 'root=/dev/mmcblk0p1 rw console=ttyO0,115200n8 earlyprintk mem=176M vram=46M notifyk.vpssm3_sva=0xBF900000'
    NAON#saveenv
    Saving Environment to SPI Flash...
    Erasing SPI flash...Writing to SPI flash...done
    NAON#
    this is copy pasted from another board, please specifiy related parameters for saxonsoc
    Lawrie Griffiths
    @lawrie
    I don't think we have an environment set up for u-boot, so I don't think saveenv will work. I don't think anyone has tried bootargs with it. @Dolu1990 may know more.
    Dolu1990
    @Dolu1990
    @emard i don't know nothing about u-boot env, sorry XD
    But
    normaly that should only be about properly configuring u-boot
    also, i made some additions (on Arty7) to get the SPI flash read/write access from linux itself, and it worked, so should be easy to do with u-boot
    todo
    Lawrie Griffiths
    @lawrie
    @Dolu1990 I think u-boot has options for either using the sd card or SPI flash for storing the environment.
    emard
    @emard
    I want sdcard's 1st partition mmcblk0p1=msdos, 2nd mmcblk0p2=linux. If uboot can get it working great - msdos can contain commandline parameters...
    Lawrie Griffiths
    @lawrie
    @emard Why do you want to change the partition? On the Arty7, @Dolu1990 is using multple partitions. He has the u-boot files in p1 and linux in p2, both ext2. I could build an sdcard, the way you want it.
    Dolu1990
    @Dolu1990
    Hoo then i would prefer sdcard to store the env, if possible
    I thinkg having multiple partitions is the good way to go, especialy if we want :
    • p1 : u-boot
    • p2 : regular linux
    • p3 : Linux used to update P1 and P2 + serial flash
    emard
    @emard
    I want same SD card to hold content for DOS and amiga and linux. Amiga wants to mount only 1st partition. Even ESP32 ftp> site mount is picky on partition sizes, in some special cases it will mount msdos which is not on 1st partition but in general it can also refuse
    Lawrie Griffiths
    @lawrie
    Currently the dtb specifies the partition that linux uses for its rootfs, and u-boot.bin has the default boot command built in, and that specifies where uImage and dtb are loaded from. It is not too hard to rebuild them using the building from source description - https://github.com/SpinalHDL/SaxonSoc/tree/dev/bsp/Ulx3sLinuxUboot
    emard
    @emard
    Well to make things super simple - can we make this: have dtb on SPI flash and few options for boot partition: p1,p2,p3. Or If I can somehow find and replace in hex editor mmcblk0p1 with mmcblk0p2 and flash it to spi, that is also ok
    Lawrie Griffiths
    @lawrie
    I think getting the environment working with a uEnv.txt file is probably the best solution. But u-boot.bin would still probably specify which partition and directory that file was in.
    We would have to change things in the bootloader to allow the dtb in flash, and that is not sufficient as u-boot.bin also needs to change.
    @emard I too would like an sd card that supports multiple applications including Amiga and Linux.
    emard
    @emard
    OK let it all be some TODO, and perhaps good serial port would get pretty high bang for the byte :)
    emard
    @emard
    I have ordered compatible spi-eth module from ebay but ETA is jan-feb next year
    Lawrie Griffiths
    @lawrie
    @Dolu1990 has a W5500 module working as well on other boards, but I couldn't get my one to work.
    emard
    @emard
    I ordered ENC28J60 Ethernet LAN Network module, saw its driver in kernel, I dont care about the performance just that it works
    Lawrie Griffiths
    @lawrie
    He also has a Microchip wilc1000 Wifi module working.
    Yes, the ENC28J60 works for me, is easy to connect, and is fast enough for such a small linux system.
    Dolu1990
    @Dolu1990
    @lawrie Normaly, today i will put in service my one on Arty7, will let's you know how it goes
    Also, will likely work on some scripts to update the images from the network
    Goran Mahovlic
    @goran-mahovlic
    @lawrie is there any ENC28J60 PMOD? or I need to make one?