hexdump -C mtd1 | grep -A 5 -i bootcmd gives nothing hexdump -C mtd1 | grep -A 5 -i 115200 gives 00115200 1a ac ff a6 b4 61 ae 91 fe 5d 85 7e ff f5 a7 b9 |.....a...].~....| 00115210 6c 6f b2 d3 5b 17 ed f4 ea 8d f9 69 8e d3 51 7e |lo..[......i..Q~| 00115220 79 71 55 5e 49 22 19 62 99 a7 e9 3e 7f e8 df 7b |yqU^I".b...>...{| 00115230 25 3f 43 be 9e 66 95 c6 58 ef c5 deby saschadd - Debian
bodhi, hexdump -C mtd0 | grep -A 5 -i bootcmd gives 000b82f0 65 6e 74 20 62 6f 6f 74 63 6d 64 3a 20 25 73 0a |ent bootcmd: %s.| 000b8300 00 0a 50 65 72 6d 61 6e 65 6e 74 20 63 6f 6e 73 |..Permanent cons| 000b8310 6f 6c 65 3a 20 25 73 0a 00 69 70 61 64 64 72 00 |ole: %s..ipaddr.| 000b8320 73 65 72 76 65 72 69 70 00 62 6f 6f 74 61 72 67 |serverip.bootarg| 000b8330 73 5f 65 6by saschadd - Debian
bodhi, just tried it grep -i bootcmd mtd0 gives me matches in binary file mtd0. grep -i bootcmd mtd1 gives nothing.by saschadd - Debian
bodhi, just tried your script but seems not to find anything /dev/mtd0 0xe0000 0x20000 0x20000 stuff found at mtd0 e0000 Warning: Bad CRC, using default environment bootargs= bootcmd=bootp; setenv bootargs root=/dev/nfs nfsroot=${serverip}:${rootpath} ip=${ipaddr}:${serverip}:${gatewayip}:${netmask}:${hostname}::off; bootm bootdelay=3 baudrate=115200 stdin=serial,cros-ec-keyb stdoby saschadd - Debian
bodhi, just had the time to test it again. i think i forgot the mdtparts environment and the uImage was not correct. Copied the /boot folder from SATA drive to USB drive and did another kwboot. now cat /proc/mtd gives me correct dev: size erasesize name mtd0: 00500000 00020000 "U-Boot" mtd1: 00a00000 00020000 "uImage" mtd2: 00f00000 00020000 "uRamdiskby saschadd - Debian
bodhi Wrote: ------------------------------------------------------- > saschadd, > > The DTB file is old in this run. So you need to re > do the uImage on the USB rootfs to append the new > one. > > Other than that, everything looks great! bodhi, you are right. Was still using the old one. Just appended the new file and made a new kwboot and usb boot. Followingby saschadd - Debian
bodhi Wrote: ------------------------------------------------------- > Since you are running this u-boot version that has > USB patch. You could try to use the envs set that > we used before to boot USB and boot all the way in > to Debian. Please do that and post the serial log > here. ok here the serial console output from kwboot and usbboot printenv CASset=max MALby saschadd - Debian
Cool, kwboot is running now!!! :) UPDATE: i am using sudo ./kwboot -f -t -B 115200 /dev/ttyAMA0 -b u-boot-a38x-Yellowstone_2014T30p6_bodhi-tld-1-nand-uart.bin -s 0 -q 1 with your first kwboot for arm (not the 2017-05 version) First try was 3 times i think. Second try was more than 10 times 12 or 13, forgot to count from 10 onwards. ;) Last try was at 5th try. printenv giveby saschadd - Debian
/dev/mtd0 0x100000 0x80000 0x20000 gives Warning: Bad CRC, using default environment bootargs= bootcmd=bootp; setenv bootargs root=/dev/nfs nfsroot=${serverip}:${rootpath} ip=${ipaddr}:${serverip}:${gatewayip}:${netmask}:${hostname}::off; bootm bootdelay=3 baudrate=115200 stdin=serial,cros-ec-keyb stdout=serial,lcd stderr=serial,lcd /dev/mtd0 0x500000 0x80000 0x20000 givesby saschadd - Debian
hmartin Wrote: ------------------------------------------------------- > Quotesaschadd > UPDATE: > Could it be that the BootROM version 1.73 is not c > ompatible with kwboot? > @hmartin: could you check your BootROM version? > > > I have BootROM version 1.73, kwboot does work. > > Your log shows that the device booted normally, me > aning kwboot did nby saschadd - Debian
bodhi Wrote: ------------------------------------------------------- > > Okay, so i boot to debian and edit that file on > th > > e SATA rootfs and try fw_printenv > > > > Correct? > > Correct. > > It is a non-destructive test. If the location is w > rong then you'll get a CRC error. Tried that and it gave me an CRC as earlier above.by saschadd - Debian
bodhi Wrote: ------------------------------------------------------- > > Should i make a new file /etc/fw_env.config with > t > > he info you posted? > > You can edit the existing file on the SATA rootfs. Okay, so i boot to debian and edit that file on the SATA rootfs and try fw_printenv Correct?by saschadd - Debian
bodhi Wrote: ------------------------------------------------------- > > What happens when the handshake occurs? > > Any different output that indicates that handsha > ke > > worked? > > You would see > > > Sending boot image... > 0 % [........................................... > ...........................] > 99 % [...................by saschadd - Debian
bodhi Wrote: ------------------------------------------------------- > saschadd, > > > Can't interrupt u-boot by pressing 1 like in pic > oc > > om. > > I did not look at the log carefully! the hanshake > did not occur. Please try running it as many time > as you can. What happens when the handshake occurs? Any different output that indicatesby saschadd - Debian
bodhi Wrote: ------------------------------------------------------- > @saschadd, can you interrupt u-boot and printenv? Can't interrupt u-boot by pressing 1 like in picocom.by saschadd - Debian
bodhi Wrote: ------------------------------------------------------- > Here is the ARM version for kwboot with the Kevin > Smith's patch that hmartin found previously. Looks like the handshake is working at first try. kwboot works but sometimes the output is a bit "defective" pi@raspberrypi:~ $ sudo ./kwboot -f -t -B 115200 /dev/ttyAMA0 -b u-boot-a38x-Yellowstonby saschadd - Debian
bodhi Wrote: ------------------------------------------------------- > Here is the new DTB and its DTS. > > I've looked at that EX2 Ultra DTS. It came from th > e same mainline version I'm basing on. There is no > t much difference, except for the flash partitions > . > > Please try this version I attached here. See if th > e kernel find the correcby saschadd - Debian
bodhi Wrote: ------------------------------------------------------- > > unfortunately this doesnt work or change somethi > ng > > > > cat /proc/mtd > > dev: size erasesize name > > mtd0: 00800000 00020000 "U-Boot" > > mtd1: 00800000 00020000 "Linux" > > mtd2: 1f000000 00020000 "Filesystem" > > OK tby saschadd - Debian
bodhi Wrote: ------------------------------------------------------- > Here is the stock u-boot build for UART booting. This binary should be used in testing kwboot the box. > > 1. Download hmartin kwboot binary for x86 64 bit (kwboot-x86_64.gz). If you dont have a Linux box running on x86_64 then I'll compile ARM version. My serial console connection is between NAS and Raspby saschadd - Debian
bodhi Wrote: ------------------------------------------------------- > saschadd, > > Lets' try booting SATA with this new mtdparts env. > All other envs are the same as before. > > > setenv mtdparts 'mtdparts=pxa3xx_nand-0:5m(u-boot) > ro,5m@5m(kernel),5m@10m(uRamdisk),441m@15m(image.c > fs),15m@456m(rescue_fw),20m@471m(config),10m@491m( > resby saschadd - Debian
bodhi Wrote: ------------------------------------------------------- > Yes, boot to stock and > > > cat /proc/mtd > cat /etc/fv_env.config > fw_printenv > this gives me cat /proc/mtd dev: size erasesize name mtd0: 00500000 00020000 "U-Boot" mtd1: 00500000 00020000 "uImage" mtd2: 00500000 00020000 "uRamdisk" mtd3: 1b90000by saschadd - Debian
> 2. Boot back to stock OS and get the location of the u-boot envs > > > cat /etc/fw_env.config > gives me in stock os cat: can't open '/etc/fw_env.config': No such file or directory :( Should i boot to stock os or interrupt console boot?by saschadd - Debian
Good that i asked, they looked all the same to me. ;) Ok, so here the debian part Marvell>> setenv load_initrd_addr 0x2900000 Marvell>> setenv load_image_addr 0x02000000 Marvell>> setenv load_initrd 'echo loading uInitrd ...; ext2load scsi 0:1 $load_initrd_addr /boot/uInitrd' Marvell>> setenv load_image 'echo loading Image ...; ext2load scsi 0:1by saschadd - Debian
bodhi, following the console output after each setenv change bodhi Wrote: ------------------------------------------------------- > Try setting the bootargs to > > setenv bootargs 'console=ttyS0,115200 root=/dev/sda1 rootdelay=10 ${mtdparts} earlyprintk=serial' > [ 0.000000] Kernel command line: console=ttyS0,115200 root=/dev/sda1 rootdelay=10 ${mtdparts}by saschadd - Debian
with appended dtb-file Marvell>> setenv load_initrd_addr 0x2900000 Marvell>> setenv load_image_addr 0x02000000 Marvell>> setenv load_initrd 'echo loading uInitrd ...; ext2load scsi 0:1 $load_initrd_addr /boot/uInitrd' Marvell>> setenv load_image 'echo loading Image ...; ext2load scsi 0:1 $load_image_addr /boot/uImage' Marvell>> setenv boby saschadd - Debian
bodhi Wrote: ------------------------------------------------------- > This uImage does not have the DTB appended to it. > We need that for the SATA rootfs too! Thats why i added setenv dtb_file '/boot/dts/armada-385-wd-ex4100.dtb' but seems not to work here. Will prepare the disks uimage. Btw do you have an idea why picocom sometimes eats up text i copy paste intoby saschadd - Debian
seems to be something wrong with that Marvell>> setenv load_initrd_addr 0x2900000 Marvell>> setenv load_image_addr 0x02000000 Marvell>> setenv dtb_file '/boot/dts/armada-385-wd-ex4100.dtb' Marvell>> setenv load_initrd 'echo loading uInitrd ...; ext2load scsi 0:1 $load_initrd_addr /boot/uInitrd' Marvell>> setenv load_image 'echo loadby saschadd - Debian
bodhi Wrote: ------------------------------------------------------- > What is the partition type on this HDD ? its ext3 as in the rootfs howto > And how about if you try step-by-step, to see what > the error is: > > ext2load scsi 0:1 0x02000000 /boot/uImage > ext2load scsi 0:1 0x2900000 /boot/uInitrd > seems fine Marvell>> scsi init AHCI init forby saschadd - Debian
well, this gives me Marvell>> scsi init AHCI init for unit0 SATA link 0 timeout. SATA link 1 timeout. AHCI init for unit1 Target spinup took 0 ms. SATA link 1 timeout. Error: SCSI Controller(s) 1B4B:9215 1B4B:9235 not found scanning bus for devices... Device 0: (2:0) Vendor: ATA Prod.: ST3250318AS Rev: CC44 Type: Hard Disk Capacity: 238475.1 MB =by saschadd - Debian