For large HDDs, I guess there will be no problem. I used 3TB & 4TB SATA in goflex home with the 2017 uboot and debian, no problem. I don't think there will be any problem with the 2021 version here. For netconsole, I did not test it yet since I dug a hole in the box and kept the uart wires. :P I always prefer wired version. :Pby daviddyer - Debian
https://e2e.ti.com/support/sensors-group/sensors/f/sensors-forum/935680/lm63-pwm-setting-question Looks like I can control the fan speed (I can tell it by noise). Install i2c-tools i2cset -f -y 0 0x4c 0x4D 0x07 i2cset -f -y 0 0x4c 0x4c 0x0B ==> PWM is %75 i2cset -f -y 0 0x4c 0x4D 0x07 i2cset -f -y 0 0x4c 0x4c 0x07 ==> PWM is %50 Therefore,by daviddyer - Debian
On lm-sensors root@debian:~# sensors-detect # sensors-detect revision $Revision$ # DMI data unavailable, please consider installing dmidecode 2.7 # or later for better results. # Kernel: 5.9.12-kirkwood-tld-1 armv5tel # Processor: Feroceon 88FR131 rev 1 (v5l) (//) This program will help you determine which kernel modules you need to load to use lm_sensors most effectively. It is genby daviddyer - Debian
> However, it is better to use lsblk. It does not > probe deeply to ECC, but basically the options > give same info about block devices). Example: > > # lsblk En, I will use lsblk instead. I can live with the errors as long as the system did not crash.by daviddyer - Debian
bodhi Wrote: ------------------------------------------------------- > One last thing. Did you save the stock mtds before > flashing new u-boot? I did not save them.... I used to save them (for dockstar, goflex home, etc) , but I never used them, so I don't save them any more. :Pby daviddyer - Debian
blkid showed some uncorrectable ECC error. root@debian:~# blkid [ 4016.614907][ T1692] __nand_correct_data: uncorrectable ECC error [ 4016.621046][ T1692] __nand_correct_data: uncorrectable ECC error [ 4016.627538][ T1692] blk_update_request: I/O error, dev mtdblock0, sector 1024 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0 [ 4016.639697][ T1692] __nand_correct_data: uncorrectaby daviddyer - Debian
Let me post some pictures of the setup. I used Rpi 0 with an usb-ethernet adapter. Used Rpi0's hardware serial port to connect to the c200 board. The cheap CH341 usb-ttl adapter I got from eBay sucks! So I did not use it.by daviddyer - Debian
Thanks. Changed.by daviddyer - Debian
Just installed lm-sensors. Hope the fan will not be that loud later. It used to run at full speed. :Pby daviddyer - Debian
Now added these to /etc/rc.local, LED for HDD will flash when HDD is accessed. Also, after booting, the Ready/Status will be green after booting. It does have a lot of LEDs to play with. if [ -d /sys/class/leds/green:disk1 ]; then echo ide-disk1 > /sys/class/leds/green:disk1/trigger fi if [ -d /sys/class/leds/green:disk2 ]; then echo ide-disk2 > /sys/class/leds/grby daviddyer - Debian
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