bodhi, My F660 box's uboot is more complex. Bootcmd doesn't contain the command that copies the kernel to RAM. It is done before bootcmd. Then uboot will do a checksum on the kernel to decide whether to run bootcmd. If the checksum doesn't pass, uboot will just print 'No Version Available on Flash'. If the checksum passes, uboot will continue to run bootcmd. I'm sby 8086k - Debian
bodhi, Have you tried kirkwood ethernet driver yet? I hope it will work. If not, you can choose to use the old armada driver on the new kernel or look at the patch of the driver source code. I will soon post it. But I can't understand why you want it. U-boot envs can be set successfully and written to nand. I'm now using an env to boot openwrt more quickly. It doesn't affectby 8086k - Debian
bodhi, Can you understand assembly code of arm? I want to autoboot openwrt. Rebuild u-boot is impossible and counterfeiting kernel checksum is impossible too. Exactly, I have the good backup of original firmware. I get 'No Version Available on Flash' only during using my openwrt and don't interrupt autoboot. 8086kby 8086k - Debian
How to boot ZTE F420/F460/F620/F660 with 88f6560 into u-boot through UART This is the u-boot file that I used. I will do more research on it later, maybe I will improve it. Use this file like following: 1,Install the latest version of Ubuntu(I'm using Ubuntu 20.04) 2,Use 'sudo apt install u-boot-tools' to install kwboot 3,Connect your F420/F460/F620/F660 to your Ubuntuby 8086k - Debian
bkallus, Thanks, I installed ubuntu 20.04 and now kwboot can send the whole image. But F660 is still not booting from uart. When the transfer is done, my F660 resets and starts to boot from NAND flash. I have also tried mi424wr's uboot image, it stops responding when the transfer is done(this isn't strange). bodhi, The uboot of F660 is interesting, it's header is strangeby 8086k - Debian
bodhi, Mtdblock1 is the uboot. I have checked it. I have also tried mi424wr's uboot, it always print 'bad message'. So I think my kwboot binary is not good. 8086kby 8086k - Debian
bodhi, user@ubuntu:~$ sudo ./kwboot -t -B 115200 /dev/ttyUSB0 -b mtdblock1.bin -p Sending boot message. Please reboot the target...| Sending boot image... 0 % [++++++.+.+.+BootROM: Invalid header checksum Booting from NAND flash l BootROM 1.34 Booting from NAND flash l BootROM 1.34 Booting from NAND flash BootROM 1.34 Booting from NAND flash BootROM 1.34 Booting from NANDby 8086k - Debian
bodhi, I know the problem. I have installed u-boot-tools, but it doesn't contain kwboot command. Can you get the amd64 version of u-boot-tools.deb contains kwboot command? edit: I have downloaded the newer version of kwboot. Invalid image disappeared. But bootrom printed xmodem protocol error. What's that thing? 8086kby 8086k - Debian
bodhi, It is actually an ubuntu VM in VMware. I am using it. 8086kby 8086k - Debian
bodhi, I notice the uboot header of 88f6282 is different from the uboot header of 88f6560. Maybe the old version of kwboot(compiled in 2012) doesn't support 88f6560. 8086kby 8086k - Debian
bodhi, Please post the log of your mi424wr rev i debian boot log. I can't make RTL8192CE work by changing the PCI-E port. I notice there are three PCI-E ports in the bootlog if I enable both ports in DTS. This is very strange. I can't find any device except 88f6560 with lspci. 8086kby 8086k - Debian
bodhi, I'm using kwboot which compiled in 2012. Have you tried to use kwboot on your mi424wr? I still get invalid image when using your attachment. If there is a newer version of kwboot, please post it. 8086kby 8086k - Debian
bodhi, Still getting invalid image. I found when I use -p parameter, invalid image will appear. Maybe the version is too old? Can you upload the latest binary you have? 8086kby 8086k - Debian
bodhi, I have tried kwboot. It interrupted the normal boot successfully, but kwboot didn't give any other results. It stuck. user@ubuntu:~/kwboot$ ./kwboot -t -p -B115200 /dev/ttyUSB0 -b mtd0-u-boot.img Sending boot message. Please reboot the target...- This is the result when I was using a kirkwood image provided by another forum. When I was using my backup or your mi424wr rev i uboby 8086k - Debian
bodhi, I have tired the rtl8192ce driver pack in openwrt. It doesn't work. I'm quite sure rtl8192ce is using pci-e bus. And the active pci-e device in device tree is pcie1,0. What do you think the problem is? The driver or the pci-e port id? 8086kby 8086k - Debian
Ignore this, I just click on the wrong place and post this message.by 8086k - Debian
bodhi, I've browsed all the information I have, then find this https://lists.denx.de/pipermail/u-boot/2012-June/125700.html The F660 of the author of this page is running an older version of U-Boot I think. This version of U-Boot shows more detail of the checking process. I can't find any available download link of this version of U-Boot. 8086kby 8086k - Debian
bodhi, OK, I will try kwboot first. Mi424wr's Uboot is certainly not suitable for F660. They have different NAND and ETH config. 8086kby 8086k - Debian
bodhi, No, it is not working. This appears again. BootROM 1.34 Booting from NAND flash BootROM: Image checksum verification PASSED U-Boot 2009.08 ( 5月 13 2013 - 18:06:09) Hit enter to stop autoboot: 0 No Version Available on Flash. I have told you the check to the kernel image is run before boot_cmd. It isn't contained in the env. If you use hex editor or ida to viewby 8086k - Debian
bodhi, BootROM 1.34 Booting from NAND flash BootROM: Image checksum verification PASSED l U-Boot 2009.08 ( 5月 13 2013 - 18:06:09) Hit enter to stop autoboot: 0 => => => => => => => => nboot 0x2000000 0 0x80000 Loading from NAND 32MiB 3,3V 8-bit, offset 0x80000 Image Name: ARM OpenWrt Linux-3.14.34 Image Type: ARM Linux Kernel Image (by 8086k - Debian
bodhi, I didn't change any of the envs because changing them can't make the uboot boot openwrt automaticly(the checksum before running bootcmd stopped it). So I use these three commands to boot openwrt. wdtdbg watchdog 0 (disable watchdog) nboot 0x2000000 0 0x80000 (read kernel from NAND to RAM) bootm (boot kernel from RAM) This box only have a 32MB NAND flash so I think opby 8086k - Debian
bodhi, Do you know how to solve the serial interrupt problem? It happens almost everytime when I turn on my box. I am busy making patches to put my changes into the builder now, I will try kwboot later. 8086kby 8086k - Debian
bodhi, BootROM 1.34 Booting from NAND flash BootROM: Image checksum verification PASSED l U-Boot 2009.08 ( 13 5 2013 - 18:06:09) Hit enter to stop autoboot: 0 => => => => => => => => => printenv baudrate=115200 loads_echo=0 rootpath=/mnt/ARM_FS/ netmask=255.255.255.0 netdev=mii0 EMAC=EMAC0 MACMODE=GMII rootfile=rootfs.img bootfile=ubooby 8086k - Debian
bodhi, Exactly, I think the way to solve it is to modify the assembly code to make the uboot continue when the check is not passed. But I am very poor at ARM assembly code. So it is too hard for me to do that. The cheking part seemed not to be included in bootcmd or any other envs. How can we sign the new uboot image? As far as I know, bootrom won't boot an unsigned uboot image. 80by 8086k - Debian
bodhi, There is a very annoying problem on the uboot of F660. It doesn't run bootcmd directly. Instead, It will read the kernel into ram and check the image. If it doesn't pass, U-boot won't continue to run bootcmd. So everytime I must enter the uboot console to boot the openwrt kernel manually. Can you crack the uboot a little? 8086kby 8086k - Debian
bodhi, There are some details changed. First, I commented out these codes phy0: ethernet-phy@9 { reg = <9>; }; ð1 { status = "okay"; phy = <&phy0>; phy-mode = "rgmii-id"; }; Next, I changed cpu-port-0 = <5>; cpu-port-1 = <6>; into cpu-port-0 = <4>; cpu-port-1 = <5>; I also changed the ethby 8086k - Debian
bodhi, This is the DTS file of F660. It's for linux 3.14 kernel. It is not very perfect but works well. 8086kby 8086k - Debian
bodhi, Can linux 5.11 kernel drive the eth device of 88f6560 now? I am trying to update openwrt version. 8086kby 8086k - Debian
bodhi, I have tested it. Ethernet is completely working. I can connect to the terminal with telnet. The next thing is WIFI chip. 8086kby 8086k - Debian
bodhi, Yes this box do have a wifi chip. The wifi chip is RealTek RTL8192CE. I haven't worked on the wifi module yet. But I believe it won't be so hard as ETH device. I believe the order of two eth device in avanta.dtsi is upside down. So I swapped the two eth nodes in avanta.dtsi. (According to the stock log of mi424wr rev i, It uses eth1) However, that's same as just usinby 8086k - Debian