Hi Bodhi, This is the log: root@debian:~# cat /proc/mtd dev: size erasesize name mtd0: 00100000 00020000 "uboot"by dirkpitt74 - uBoot
Hi Bodhi, The chip is a SLC, not a MLC. In this thread I've find a complete bootlog of another Netgear Stora that have a Samsung NAND chip. The only difference with mine is the linux kernel version. I updated the rootfs to the 4.20.6 and now the chip is correctly recognized. This is the bootlog with the printenv U-Boot 2017.07-tld-1 (Sep 05 2017 - 00:38:05 -0700) Netgear Stora MS211by dirkpitt74 - uBoot
Hi Bodhi, I've changed the env as you suggested, but the NAND still read only mode. U-Boot 2017.07-tld-1 (Sep 05 2017 - 00:38:05 -0700) Netgear Stora MS2110 SoC: Kirkwood 88F6281_A1 DRAM: 128 MiB WARNING: Caches not enabled NAND: 256 MiB In: serial Out: serial Err: serial Net: egiga0 PHY reset timed out 88E1116 Initialized on egiga0 Hit any key to stop autobootby dirkpitt74 - uBoot
Hi Bodhi, Now my Stora boot and load debian. I've follow your suggested step with some tweak. This is the complete log. pi@raspberrypi:~/kwboot-tool $ ./kwboot_1 -t -B 115200 /dev/ttyUSB0 -b uboot.2017.07-tld-1.netgear_ms2110.mtd0.kwb -p Sending boot message. Please reboot the target...- Sending boot image... 0 % [.................................................................by dirkpitt74 - uBoot
Hi Bodhi, this is the full bootlog pi@raspberrypi:~/kwboot-tool $ ./kwboot_1 -t -B 115200 /dev/ttyUSB0 -b uboot.2017.07-tld-1.netgear_ms2110.mtd0.kwb -p Sending boot message. Please reboot the target...- Sending boot image... 0 % [......................................................................] 1 % [......................................................................] 3 %by dirkpitt74 - uBoot
Hi, 1: Netgear Stora> setenv dtb_file /boot/dts/kirkwood-netgear_stora_ms2000.dtb Netgear Stora> setenv mtdparts 'mtdparts=orion_nand:4M(uboot),-(rootfs)' 2: [ 8.877633] 2 cmdlinepart partitions found on MTD device orion_nand [ 8.883958] Creating 2 MTD partitions on "orion_nand": [ 8.889134] 0x000000000000-0x000000400000 : "uboot" [ 8.895by dirkpitt74 - uBoot
Hi Bodhi, I was writing about my discovery and you had already found it. This is the uboot log Netgear Stora> help ? - alias for 'help' base - print or set address offset bdinfo - print Board Info structure boot - boot default, i.e., run 'bootcmd' bootd - boot default, i.e., run 'bootcmd' bootefi - Boots an EFI payload from memory bootelby dirkpitt74 - uBoot
Hi Bodhi, some progress.... I've make some search.. The nand partition must start and end up with a multiple of erase size. My stora have [ 8.840842] nand: device found, Manufacturer ID: 0xec, Chip ID: 0xda [ 8.847357] nand: Samsung NAND 256MiB 3,3V 8-bit [ 8.851997] nand: 256 MiB, MLC, erase size: 4096 KiB, page size: 4096, OOB size: 128 I've modify the mtdpart like tby dirkpitt74 - uBoot
Hi Bodhi, same issue... Hit any key to stop autoboot: 0 Netgear Stora> setenv dtb_file /boot/dts/kirkwood-netgear_stora_ms2000.dtb Netgear Stora> setenv mtdparts 'mtdparts=orion_nand:1M(uboot),4M@(kernel),-(rootfs)' Netgear Stora> printenv arcNumber=2743 baudrate=115200 bootcmd=run bootcmd_uenv; run scan_disk; run set_bootargs; run bootcmd_exec; reset bootcmd_exec=by dirkpitt74 - uBoot
Hi Bodhi, root@debian:~/tools# dmesg [ 0.000000] Booting Linux on physical CPU 0x0 [ 0.000000] Linux version 4.12.1-kirkwood-tld-1 (root@tldDebian) (gcc versio7 [ 0.000000] CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=000539f [ 0.000000] CPU: VIVT data cache, VIVT instruction cachby dirkpitt74 - uBoot
Hi Bodhi, I've perform a nand scrub and now no Bad eraseblock. dmesg | grep -i 'bad' [ 8.865697] Scanning device for bad blocks Strange thing because on uboot I've this output Netgear Stora> nand bad Device 0 bad blocks: 048a0000 076c0000 0b560000 I'm trying to flash the uboot having this issue root@debian:~/tools# ./flash_erase /dev/mtby dirkpitt74 - uBoot
I've try a reboot but nothing change. root@debian:~# cat /etc/fw_env.config # MTD device name Device offset Env. size Flash sector size Number of sectors /dev/mtd0 0xc0000 0x20000 0x20000 root@debian:~# cat /proc/mtd dev: size erasesize name mtd0: 00100000 00400000 "uboot" mtd1: 00400000 00400000 "kernel" mtd2: 0fb00000 00400000 "rootfs" rooby dirkpitt74 - uBoot
Hi, I've fix the issue.... 1: Create a new USB roots 2: Stop the u-boot and change the env dtb_file Netgear Stora> setenv dtb_file /boot/dts/kirkwood-netgear_stora_ms2000.dtb Now I'm on debian login Netgear Stora> boot starting USB... USB0: USB EHCI 1.00 scanning bus 0 for devices... 2 USB Device(s) found scanning usb for storage devices... Uby dirkpitt74 - uBoot
Hi Bohdi, this is the complete log. pi@raspberrypi:~/kwboot-tool $ ./kwboot_1 -t -B 115200 /dev/ttyUSB0 -b uboot.2017.07-tld-1.netgear_ms2110.mtd0.kwb -p Sending boot message. Please reboot the target...- Sending boot image... 0 % [......................................................................] 1 % [......................................................................] 3 %by dirkpitt74 - uBoot
Hi bodhi, Nice job!!! Whith the new kwboot my stora boot!! I've try to start linux with the rootfs Debian-4.12.1-kirkwood-tld-1-rootfs-bodhi.tar.bz2. Unfortunately the boot stop at this point .... .... Begin: Waiting for root file system ... done. Gave up waiting for root device. Common problems: - Boot args (cat /proc/cmdline) - Check rootdelay= (did the system wait long enoby dirkpitt74 - uBoot
Hi Bodhi, thanks for the reply. I've try to upload the latest uboot image and this is the output. pi@raspberrypi:~/kwboot-tool $ ./kwboot -t -B 115200 /dev/ttyUSB0 -b uboot.2017.07-tld-1.netgear_ms2110.mtd0.kwb -p Sending boot message. Please reboot the target...| Sending boot image... 0 % [......................................................................] 1 % [.........by dirkpitt74 - uBoot
Hi, in the last week my old Stora won't boot anymore. After that I've follow different tutorial and I've dump the u-boot log with a USB to TTL serial converter. __ __ _ _ | \/ | __ _ _ ____ _____| | | | |\/| |/ _` | '__\ \ / / _ \ | |by dirkpitt74 - uBoot