LED... root@debian:~# ls -l /sys/class/leds total 0 drwxr-xr-x 2 root root 0 Jan 7 15:36 . drwxr-xr-x 47 root root 0 Jan 7 15:36 .. lrwxrwxrwx 1 root root 0 Jan 7 15:43 blue:cloud -> ../../devices/platform/leds/leds/blue:cloud lrwxrwxrwx 1 root root 0 Jan 7 15:43 green:disk-fail -> ../../devices/platform/leds/leds/green:disk-fail lrwxrwxrwx 1 root root 0 Jan 7 15:43 greeby daviddyer - Debian
Yes. The RTC error is gone now. U-Boot 2021.10-tld-0.3 (Jan 07 2022 - 15:08:00 -0800)Ctera C200 V1 SoC: Kirkwood 88F6281_A1 Model: Ctera C200 V1 DRAM: 512 MiB NAND: 256 MiB MMC: Loading Environment from NAND... OK In: serial Out: serial Err: serial Net: eth0: ethernet-controller@72000 88E1116 Initialized on ethernet-controller@72000 Hit any key to stop autoboot: 0by daviddyer - Debian
One problem about disk 1 / disk 2 LED (in debian). I think disk1 / disk 2 LED are supposed to light up when there's a drive installed. LED for disk 1 / disk 2 doesn't light up after debian is booted. Also, if I operate on disk 1 / disk 2, the LED for disk 1 / disk 2 doesn't flash. Disk 1 250GB rusty Disk 2 256GB SSD root@debian:~# dd if=/dev/sda of=/dev/null bs=4M cby daviddyer - Debian
One 250GB rusty disk in disk 1 position. One 256GB ssd in disk 2 position sata command Works... root@raspberrypi:~/c200# kwboot -t -B 115200 /dev/ttyAMA0 -b uboot.2021.10-tld-0.2.c200v1.mtd0.kwb -p Sending boot message. Please reboot the target.../ Sending boot image... 0 % [......................................................................] ====== 99 % [....................by daviddyer - Debian
One 250GB rusty disk in disk 1 position. sata command Works... root@raspberrypi:~/c200# kwboot -t -B 115200 /dev/ttyAMA0 -b uboot.2021.10-tld-0.2.c200v1.mtd0.kwb -p Sending boot message. Please reboot the target...| Sending boot image... 0 % [......................................................................] 1 % [.................................................................by daviddyer - Debian
Thoughts on the RTC: IMHO, we can just stick to the soft RTC. These kirkwood devices are about 10 years old, I guess most of the batteries died. Soft RTC should be a good solution.by daviddyer - Debian
Tested the new u-boot (250GB stat in its old place. Disk is in Disk 2 position of the box ) 1 Soft RTC works. 2 sata init / sata info takes a little longer than last version. And it seems working! 3 Debian booted fine. Functions OK. root@raspberrypi:~/c200# kwboot -t -B 115200 /dev/ttyAMA0 -b uboot.2021.10-tld-0.2.c200v1.mtd0.kwb -p Sending boot message. Please reboot the target...|by daviddyer - Debian
The good news: The new uboot booted openwrt fine... might be a good choice for rescue system C200_V1>printenv bootcmd=run bootcmd_uenv; run scan_disk; run set_bootargs; run bootcmd_exec bootcmd_exec=run load_uimage; if run load_initrd; then if run load_dtb; then bootm $load_uimage_addr $load_initrd_addr $load_dtb_addr; else bootm $load_uimage_addr $load_initrd_addr; fi; else if run loadby daviddyer - Debian
U-boot 2021 for C200_v1 seems sata command not working properly? I guess it should show some info after these commands. I connected a rusty 250GB to the system and one usb flash drive (boot drive) U-Boot 2021.10-tld-0.1 (Jan 06 2022 - 13:10:13 -0800)Ctera C200 V1 SoC: Kirkwood 88F6281_A1 Model: Ctera C200 V1 DRAM: 512 MiB NAND: 256 MiB MMC: Loading Environment from NANDby daviddyer - Debian
Well, I choose that name because the debian dts folder names other kirkwood boxes that way... And the source code file (from openwrt) name is kirkwood-c200-v1.dts Or, like the pogoplug v4, name it kirkwood-c200_v1.dtb ? Just tested one LED, seems fine. I have the usb boot drive on usb1, so LED for usb1 it is on. (green) root@debian:/sys/class/leds/green:usb1# echo 0 >brightnessby daviddyer - Debian
Will test the LEDs later... currently the box was disassembled and it is difficult to match the LED with its name. :P I guess we can name the dtb file kirkwood-c200-v1.dtb Will test the sata command in u-boot later.by daviddyer - Debian
Set debian to DHCP, kwboot again, also worked. Router gave the good old 192.168.7.248 to it. :-) Debian GNU/Linux 10 debian ttyS0 debian login: root Password: Last login: Thu Jan 6 15:13:08 PST 2022 on ttyS0 Linux debian 5.9.12-kirkwood-tld-1 #1.0 PREEMPT Sat Dec 5 14:05:39 PST 2020 armv5tel The programs included with the Debian GNU/Linux system are free software; the exact distby daviddyer - Debian
Great news... Looks like everything is working with the new u-boot root@raspberrypi:~/c200# kwboot -t -B 115200 /dev/ttyAMA0 -b uboot.2021.10-tld-0.1.c200v1.mtd0.kwb -p Sending boot message. Please reboot the target...\ Sending boot image... 0 % [......................................................................] 1 % [..............................................................by daviddyer - Debian
Now time to try openwrt route.... As I flashed flashed uboot.2017.07-tld-2.sheevaplug.mtd0.kwb to the box, I don't have the original uboot/firmware. So I did this way 1 Grab openwrt-kirkwood-ctera_c200-v1-initramfs-factory.firm from compiled file. 2 7zip it, got a kernel file from it. File size 4,446,109 bytes. 3 load the file, boot it. Looks like we still don't have networkby daviddyer - Debian
Static IP seems not working either. root@debian:/etc/network# cat interfaces auto lo eth0 iface lo inet loopback iface eth0 inet static address 192.168.7.222 netmask 255.255.255.0 gateway 192.168.7.1 hwaddress ether 00:25:25:00:6d:f2 reboot it... printenv first U-Boot 2017.07-tld-2 (Dec 04 2017 - 02:00:45 -0800) Marvell-Sheevaplug SoC: Kby daviddyer - Debian
Status.... root@debian:~# ifconfig eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 ether 00:25:25:00:6d:f2 txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 5 bytes 1710 (1.6 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device interrupt 3by daviddyer - Debian
To save the kwboot trouble, I actually flashed uboot.2017.07-tld-2.sheevaplug.mtd0.kwb to the box and also flashed / adjusted the environment parameters. Debian booted fine, but still no network connection. U-Boot 2017.07-tld-2 (Dec 04 2017 - 02:00:45 -0800) Marvell-Sheevaplug SoC: Kirkwood 88F6281_A1 DRAM: 512 MiB WARNING: Caches not enabled NAND: 256 MiB MMC: MVEBU_MMC: 0by daviddyer - Debian
Well, got another one from another seller. The original seller forgot to ship the replacement during the holidays... He refunded me instead. This one definitely has a working ethnet port. I can see the IP address of the Mac from the C200 Boot with the original firmware (It seems we can not stop the original u-boot) Bootlog below. It did get an ipaddress from DHCP. 192.168.7.248 I canby daviddyer - Debian
Go ahead. This box can do uart booting. We don't need to worry about bricking it.by daviddyer - Debian
Raw reading speed. The 16GB "SSD" is slower than the rusty drive. root@debian:~# dd if=/dev/sda of=/dev/null bs=4M count=512 512+0 records in 512+0 records out 2147483648 bytes (2.1 GB, 2.0 GiB) copied, 16.4944 s, 130 MB/s root@debian:~# dd if=/dev/sdb of=/dev/null bs=4M count=512 512+0 records in 512+0 records out 2147483648 bytes (2.1 GB, 2.0 GiB) copied, 23.641 s, 90.8 MBby daviddyer - Debian
Still waiting for the replacement... Meanwhile, I added two SATA hard drives to the system and both worked. One is the 16GB SSD from Dell Kace M300, the other is an old mechanical drive (250GB). Seems both of them worked. U-Boot 2017.07-tld-2 (Dec 04 2017 - 02:00:45 -0800) Marvell-Sheevaplug SoC: Kirkwood 88F6281_A1 DRAM: 512 MiB WARNING: Caches not enabled NAND: 256 MiB Mby daviddyer - Debian
http://www.yourwarrantyisvoid.com/2010/09/08/dead-dockstar-resurrected-with-jtag/ You don't need to make a perfect cable like the guy in the article. Just solder a few pins... and do it... I followed that instruction and revived my dockstar about 10 (?) years ago.by daviddyer - Debian
Well, since this box supports kwboot, I don't need to fear of bricking it. I just flashed the sheevaplug uboot / ubootenv to it. And it booted debian as expected.... Of course, network is still not OK. I added an usb-ethernet adapter to it and I can access the network now. This confirms the original ethernet error. Continue to wait for the replacement...by daviddyer - Debian
The most common problem for these boxes is the power supply. I experienced 3 failed power supply for goflexhome / dreamplug / external HD power supply. This is the first one to have a failed Ethernet.by daviddyer - Debian
Maybe there's hardware error on the box's ethernet. But the LEDs did flash... :-( However, when I booted the original firmware, I was NOT able to find an IP address of the box in my router's DHCP list Anyway, I reported this to the seller and seller told me he would send me a replacement. Now back to step 0..... waiting for the new shipment.by daviddyer - Debian
It's already in this thread. https://forum.doozan.com/read.php?2,128064,128204#msg-128204by daviddyer - Debian
you need to combine the kernel with the dtb into one file. this is required for old u-boot to boot new kernel. something like this cd /boot mv uImage uImage.orig mv uInitrd uInitrd.orig cp -a zImage-5.15.5-kirkwood-tld-1 zImage.fdt cat dts/kirkwood-dockstar.dtb >> zImage.fdt mkimage -A arm -O linux -T kernel -C none -a 0x00008000 -e 0x00008000 -n Linux-5.15.5-kirkwood-tldby daviddyer - Debian
This uboot is older. (U-Boot 2014.10+dfsg1-5). It doesn't support bootcmd_uenv command. Solution: 1 build a debian usb disk with embeded dtb file. 2 boot with that usb. 3 update uboot to 2017 then you can copy your experience.by daviddyer - Debian
C200 is connected to a switch. There's a PC on the same switch. PC and c200 can not ping each other. PC can ping other things, including the devices on other switches / router. I tried to replace the ethernet cable (used another cable on the same switch), same result. However, this showed up on the console root@debian:~# [ 93.218601][ C0] mv643xx_eth_port mv643xx_eth_port.0 eth0by daviddyer - Debian
I actually tried to use ifconfig and set eth0 to a static IP address before, about the same results as above.by daviddyer - Debian