first try Marvell>> setenv fdt_skip_update yes Marvell>> usb start (Re)start USB... USB0: Port (usbActive) : 0 Interface (usbType = 3) : USB XHCI 1.00 scanning bus 0 for devices... 2 USB Device(s) found scanning usb for storage devices... 1 Storage Device(s) found scanning usb for ethernet devices... 0 Ethernet Device(s) found Marvell>> ext2load usbby sorgonas - Debian
All right, then it wasn't my fault up to here and couldn't help it that he didn't continue. At least something positive, thought the whole time, it's due to my inability ;-)by sorgonas - Debian
Marvell>> run usb_set_bootargs Marvell>> bootm 0x02000000 0x2900000 ## Booting image at 02000000 ... ## Booting kernel from Legacy Image at 02000000 ... Image Name: Linux-5.2.9-mvebu-tld-1 Created: 2021-05-28 12:36:26 UTC Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 5073874 Bytes = 4.8 MiB Load Address: 00000080 Entry Point:by sorgonas - Debian
My result Marvell>> setenv bootdev usb Marvell>> setenv device '0:1' Marvell>> setenv load_initrd_addr 0x2900000 Marvell>> setenv load_image_addr 0x02000000 Marvell>> setenv load_initrd 'echo loading uInitrd ...; ext2load $bootdev $device $load_initrd_addr /boot/uInitrd' Marvell>> setenv load_image 'echo loading Image ...; ext2lby sorgonas - Debian
I'm still up to date and waiting for the next steps ;-)by sorgonas - Debian
Hy Bodhi, 1. It's a 2.0 USB stick from bluemedia, my Samsung or Intenso sticks are all USB-3. 2. I've been using the stick the whole time, and so far, yes. ok I will do it all over again and delete it completely beforehand. 3. Hit any key to stop autoboot: 0 Marvell>> 1111 Unknown command '1111' - try 'help' Marvell>> usb reset (Re)start USby sorgonas - Debian
Hello Bodhi, I've now done it as described, but it still starts normally, as you can see below. But slowly I don't feel like it anymore, but rather frustration because of the thing. I think I'll just leave the crap thing like that and come to terms with the fact that it doesn't work. Greetings from Sorgonas USB-Create: root@Server:~# parted --script /dev/sdc \by sorgonas - Debian
Hey Bodhi, I have the new creation of the USB here, but there was no error, it looks like the last time. The new start went like the last one and the system started normally. can it possibly be that this does not work, because my device had not loaded a firmware update too long ago? ./usr/lib/python2.7/encodings/iso2022_jp_3.py ./usr/lib/python2.7/encodings/cp720.pyc ./usr/lib/pythonby sorgonas - Debian
The next attempt is now through. This time it didn't stop, but in the end it started the system normally, and not Debian. Here is the next log: Net: | port | Interface | PHY address | |--------|-----------|--------------| | egiga0 | RGMII | 0x00 | | egiga1 | RGMII | In-Band | | egiga2 | SGMII | 0x01 | egiga0 , egiga1, egiga2 Hit any key tby sorgonas - Debian
ok bodhi, I will create a new usb and will do this again, I will let you know when I have finished the next runby sorgonas - Debian
Hey, so, have now put a desktop on my Linux machine so that i can copy the terminal as well. So here is the result: root@debian:~# ./kwboot -f -t -B 115200 /dev/ttyUSB0 -b u-boot-a38x-Yosemite_2014T3_PQ-nand-uart.bin -s 0 -q 1 Sending boot message. Please reboot the target...-DUfw�"3DUfw�"3DUfw�"3DUfw�"\DUfw�"3DUfw�"3DUfw�"3DUfw�"3DUby sorgonas - Debian
Hello again, I've now also registered, D.Jeschke here ;-) I'm currently browsing my data on the NAS, but I don't know whether this is the right log fileby sorgonas - Debian