bodhi Wrote: ------------------------------------------------------- > Cool! Thanks wacke! > > Btw, I've included your RT NAS V3 support in the > MVEBU kernel release thread. Hi bodhi, Many thanks. I've attached my self build uboot to that post, or it won't boot to debian at all.by wacke - Debian
Hi bodhi, The attached uboot was from my self built with ext4 support and partation layout change, and have tested with no issues. Other users should flash this uboot to boot debian, or it won't boot.by wacke - uBoot
Hi bodhi, There are some patches for this problem, you can fallow these patches: https://www.spinics.net/lists/netdev/msg743188.htmlby wacke - Debian
bodhi Wrote: ------------------------------------------------------- > Continue with my post above. > > As I've learned in the past, the 6171 switch chip > does support Jumbo Frame! > Hi bodhi, Maybe that the 6171 switch actually don't support support jumbo configuration per port like the change log said? Some of the chips in the mv88e6xxx family doby wacke - Debian
Hi bodhi, Tried modify (mv88e6xxx_ops mv88e6171_ops @ linux-5.9/drivers/net/dsa/mv88e6xxx/chip.c): remove .port_set_jumbo_size = mv88e6165_port_set_jumbo_size, add .set_max_frame_size = mv88e6185_g1_set_max_frame_size, Seems worked: root@debian:~# scp rescue.img Wacke@192.168.1.2:/NAS/Software/Software/ Password: rescue.imgby wacke - Debian
Hi bodhi, I've confirmed that the issue was actually start from 5.9.0, it's about the port mtu setting. The change log of kernel 5.9.0: commit dfecd3e00cd32b2a6d1cfdb30b513dd42575ada3 Merge: 9b964f1654616 1baf0fac10fbe Author: David S. Miller <davem@davemloft.net> Date: Fri Jul 24 20:03:28 2020 -0700 Merge branch 'net-dsa-mv88e6xxx-port-mtu-support'by wacke - Debian
Hi bodhi, Actually I can't get any kernel message when transfer data at all....by wacke - Debian
bodhi Wrote: ------------------------------------------------------- > Yes, indeed it is broken. > > From the Linksys EA4500 (switch chip 6171), I can > copy a file (pull) from another Kirwood box. But > when I push a file from the EA4500 to that > Kirkwood box, it hang. Hi bodhi, Then is there anyway to fix this?by wacke - Debian
Hi bodhi, Tested using rsync, seems the same issue, it just hangs: root@debian:/tmp# rsync -v -a rescue.img Wacke@192.168.1.2:/tmp Password: sending incremental file list rescue.imgby wacke - Debian
Hi, Is there anyone noticed that the kernel dsa driver for 88e6171r and 88e6161 switch chip was broken from kernel 5.10 and above? The issue is that it can't transmit data from mvebu device (eg: via scp), it just hangs like this: root@debian:~# scp /tmp/rescue.img Wacke@192.168.1.2:/tmp/ Password: rescue.img 5% 1920KB 1.9MB/s 00:16 ETA Bby wacke - Debian
Hi, bodhi Something wrong with my self build uboot, it always crash when transferring large files (scp,samba etc.), but it won't crash when booting with the stock uboot. Below is the crash log (your latest mvebu kernel 5.11.7): [ 197.305774][ T3031] 8<--- cut here --- [ 197.305788][ T3031] Unable to handle kernel paging request at virtual address 0b3ed5a2 [ 197.305802][ T303by wacke - uBoot
bodhi Wrote: ------------------------------------------------------- > wacke, > > I've confirmed that fw_printenv does not have > support for MLC NAND flash yet. Then I have to give up for now, and can you build a kernel with hw i/o patch? Also the switch seems did not working properly on the lateset kernel.by wacke - uBoot
Hi bodhi, Still no luck, maybe the fw_printenv didn't support the mlc nand? root@debian:~# cat /etc/fw_env.config # MTD device name Device offset Env. size Flash sector size Number of sectors /dev/mtd1 0x0000 0x100000 0x100000 4 root@debian:~# fw_printenv Unsupported flash type 8 on /dev/mtd1 CASset=min MALLOC_lenby wacke - uBoot
Hi Bodhi, No luck. root@debian:~# cat /etc/fw_env.config # MTD device name Device offset Env. size Flash sector size Number of sectors /dev/mtd1 0x0000 0x100000 0x100000 root@debian:~# fw_printenv Unsupported flash type 8 on /dev/mtd1 Too few good blocks within rangeby wacke - uBoot
Hi bodhi, The output: root@debian:~# cat /etc/fw_env.config # MTD device name Device offset Env. size Flash sector size Number of sectors /dev/mtd1 0x0000 0x100000 0x40000 4by wacke - uBoot
Hi bodhi, Tried, but no luck: __ __ _ _ | \/ | __ _ _ ____ _____| | | | |\/| |/ _` | '__\ \ / / _ \ | | | | | | (_| | | \ V / __/ | | |_| |_|\__,_|_| \_/ \___|_|_| _ _ ____ _ | | | | | __ ) ___ ___ | |_ | | | |___| _ \ / _ \ / _ \| __| | |_| |___| |_) | (_) | (_) | |_ \___/by wacke - uBoot
Hi bodhi, Uboot env: BootROM 1.08 Booting from NAND flash General initialization - Version: 1.0.0 High speed PHY - Version: 2.1.3 (COM-PHY-V20) Update PEX Device ID 0x67100 High speed PHY - Ended Successfully DDR3 Training Sequence - Ver 5.5.1 DDR3 Training Sequence - Run without PBS. DDR3 Training Sequence - Ended Successfully BootROM: Image checksum verification PASSED __by wacke - uBoot
Hi Bodhi, Please use this dts (readded the uboot_env partition) : // SPDX-License-Identifier: (GPL-2.0+ OR MIT) /* * Device Tree file for Marvell RTNAS V3 * (RD-88F6710-A1) * * Copied from arch/arm/boot/dts/armada-370-db.dts * * Copyright (C) 2021 Wacke <cao88yu@gmail.com> * * Note: this Device Tree assumes that the bootloader has remapped the * internal registers tby wacke - uBoot
Hi Bodhi, The DTS of my box: // SPDX-License-Identifier: (GPL-2.0+ OR MIT) /* * Device Tree file for Marvell RTNAS V3 * (RD-88F6710-A1) * * Copied from arch/arm/boot/dts/armada-370-db.dts * * Copyright (C) 2021 Wacke <cao88yu@gmail.com> * * Note: this Device Tree assumes that the bootloader has remapped the * internal registers to 0xf1000000 (instead of the defaultby wacke - uBoot
tme Wrote: ------------------------------------------------------- > Hi wacke, > > Very interesting! > > Can you make a patch with all the differences > between mainline U-Boot 2021.01 and > 2021.01-00707-ge716c90229-dirty? I would be happy > to test if the DDR training works on Netgear > ReadyNAS RN102 as well. > > Regards, > Trond Melen Hiby wacke - uBoot
Hi Bodhi, Now I'm trying to build the mainline uboot for my box, thanks the uboot patch of this site: https://sites.google.com/site/shihsung/88fxxxx-soc Using some source of my box and with some modify, now got some success (previous build it just hangs): HOME-Server:/NAS/Software/kwboot # ./kwboot -p -t /dev/ttyUSB0 -b u-boot-spl.kwb Sending boot message. Please reboot the tarby wacke - uBoot
Hi Bodhi, I just got the uboot source of my box, so many years later, fainally got this, i just rebuilt the uboot with added ext4 filesystem support. Many tanks.by wacke - uBoot
Hi Bodhi, I mean that I read the GPIO data from orignal uboot, and then how can I transform these data to GPL source?by wacke - uBoot
Hi Bodhi, I can read the gpio data from uboot that mapped to ram, but then how to use these data? Marvell>> md 0xf1018100 f1018100: 00000d60 fffff29f 00000000 80000000 `............... f1018110: ffffff7f ffffff7f 00000000 00000000 ................ f1018120: 00000000 00000000 00000000 00000000 ................ f1018130: 00000000 00000000 00000000 00000000 ................by wacke - uBoot
Hi Bodhi, Tried the Linux-5.9.3-mvebu-tld-1, also hangs on starting kernel, since the uboot built by my self is based on Netgear RN102, so what is the defiernce (kernel config) between the new uboot and old uboot? Marvell>> run bootcmd4 Reset IDE: Marvell Serial ATA Adapter Integrated Sata device found Device 1 @ 0 1: Model: JMicron Firm: 1by wacke - uBoot
Hi Bodhi, I've got the usb and one of sata working on my self-built uboot, then i tried the 5.9.3-mvebu-370xp-tld-4 kernel: With stock uboot, it just hangs on starting kernel ... __ __ _ _ | \/ | __ _ _ ____ _____| | | | |\/| |/ _` | '__\ \ / / _ \ | | | | | | (_| | | \ V / __/ | | |_| |_|\__,_|_| \_/ \___|_|_| _ _ ____by wacke - uBoot
Hi Bodhi, The kernel and rootfs are only on NAND for now, because the USB and SATA port not working. The original uboot env: Marvell>> pri CASset=min MALLOC_len=5 OpenWrtLinux=Yes autoload=no baudrate=115200 bootargs=console=ttyS0,115200 ubi.mtd=5 root=ubi0:rootfs ro rootfstype=ubifs bootargs_end=:10.4.50.254:255.255.255.0:KW40:eth0:none bootargs_root=root=/dev/nfs rwby wacke - uBoot
Hi bodhi, Good news: uboot can recognize 1G RAM now. Bad news: the uboot i built cant boot linux, it's stuck at starting linux. HOME-Server:/NAS/Software/kwboot # ./kwboot -p -t /dev/ttyUSB0 -b u-boot-a370-1.0-nand-rd-uart.bin Sending boot message. Please reboot the target...| Sending boot image... 0 % [......................................................................]by wacke - uBoot
Hi Bodhi, Trying to build the switch driver into uboot, but I getting these errors, is there anyway to solve this? And the source file is attached. /NAS/Software/uboot/u-boot-2011.12-armada370/board/mv_ebu/common/USP/ethSwitch/mvSwitch.o: In function `mvEthSwitchRegWrite': /NAS/Software/uboot/u-boot-2011.12-armada370/board/mv_ebu/common/USP/ethSwitch/mvSwitch.c:385: multiple definitiby wacke - uBoot
Hi Bodhi, Manay thanks to @whitepawn and his job, I just downloaded the uboot source from his dropbox, with some modify, now I can run the self-built uboot and detected the MLC NAND chip successfully, but there still a lot of things to do: 1. The uboot my built can only recognize 512M RAM while my box actually have 1024M RAM. 2. SATA Port and USB Port seems not work. 3. My box have an 88Eby wacke - uBoot