bodhi, Yes, Debian is working well from the HDD. The only thing still needed: to be able to boot to Debian without the need of serial cable connected to my laptop. :)by garagoyun - Debian
bodhi, I am aware that you have limited time in general , just wanted to know if this is not forgotten :) Thanks for your help!!!by garagoyun - Debian
bodhi Wrote: ------------------------------------------------------- > In the mean time, boot with serial console and try > the HDD rootfs with these commands: > > > setenv bootcmd_sata 'ide reset; ext2load ide 0:1 > 0x800000 /boot/uImage; ext2load ide 0:1 0x2100000 > /boot/uInitrd' > setenv bootcmd_exec 'run set_bootargs; run > bootcmd_sataby garagoyun - Debian
bodhi Wrote: ------------------------------------------------------- > Will be back tomorrow with a new test :) Thanks! Appreciated.by garagoyun - Debian
bodhi Wrote: ------------------------------------------------------- > garagoyun, > > > Sadly still booting to Stock. > > That's certainly not expected :) I'll need to read > that patch again, then. Perhaps bootargs_root is > not the right place to insert the commands. It was > taken literally, instead of being in the commands > chain buffer. &by garagoyun - Debian
bodhi Wrote: ------------------------------------------------------- > Cool! please go ahead, do reset and let it boot > all the way. > > > reset > bodhi, Sadly still booting to Stock: Marvell>> printenv bootargs_root bootargs_root=root=/dev/ram0 rootfstype=cramfs init=/etc/rc.preroot initrd=0x800000,0x1000000; echo Booting Debian...; if run bootcmd_exec;by garagoyun - Debian
bodhi Wrote: ------------------------------------------------------- > Awesome :) so it works. > > > > setenv bootargs_root 'root=/dev/ram0 > rootfstype=cramfs init=/etc/rc.preroot > initrd=0x800000,0x1000000; echo Booting Debian...; > if run bootcmd_exec; then; fi; echo Booting Stock > ...; ' > saveenv > reset > > > > Inby garagoyun - Debian
bodhi Wrote: ------------------------------------------------------- > garagoyun, > > Look like my procedure was incorrect. Let's try > again. > > > Power up, interrupt serial console and > > > setenv bootargs_root 'root=/dev/ram0 > rootfstype=cramfs init=/etc/rc.preroot > initrd=0x800000,0x1000000; echo Booting Stock ...; >by garagoyun - Debian
bodhi, Output from the first test as requested: > > setenv bootargs_root 'root=/dev/ram0 > rootfstype=cramfs init=/etc/rc.preroot > initrd=0x800000,0x1000000; echo Booting Stock ...; > ' > boot > __ __ _ _ | \/ | __ _ _ ____ _____| | | | |\/| |/ _` | '__\ \ / / _ \ | | | | | | (_| | |by garagoyun - Debian
bodhi, I have tried with the mtd0 for NSA325. As you mentioned it did not go too far, however at the end it states some info regarding U-Boot 2017.07-tld-1. I assume it is on its own a success :) ~/kwboot-tool$ ./kwboot -t -B 115200 /dev/ttyUSB0 -b uboot.2017.07-tld-1.nsa325.mtd0.kwb -p Sending boot message. Please reboot the target...| Sending boot image... 0 % [................by garagoyun - Debian
bodhi Wrote: ------------------------------------------------------- > garagoyun, > > 1. bootcmd issue: let's see if bootcmd was reset > by stock. Sometime they intentionally do that in > stock u-boot. > > mtdparts=mtdparts=orion_nand:0x000a0000@0x0(uboot),0x00040000@0x000a0000(param),0x00280000@0x000e0000(preroot),0x00380000@0x00360000(uimage),0x076e0000@0x006by garagoyun - Debian
bodhi Wrote: ------------------------------------------------------- > garagoyun, > > You can use the nanddump mtd0 to kwboot it. > Remember to use -p option on the kwboot command. > > > nanddump --noecc --omitoob -f > mtd0.silverstore.stock /dev/mtd0 > > > The kwboot command would be: > > > kwboot -t -B 115200 /dev/ttyUSB0 -b >by garagoyun - Debian
bodhi, Good thing I have asked. I was a bit confused. I will test that shortly, but first wanted to inform you that I have tried saving the env to boot automatically from USB with saveenv command. Strangely, it would still boot to stock kernel after reboot. __ __ _ _ | \/ | __ _ _ ____ _____| | | | |\/| |/ _` | '__\ \ / / _ \ | |by garagoyun - Debian
bodhi Wrote: ------------------------------------------------------- > garagoyun, > > You can use the nanddump mtd0 to kwboot it. > Remember to use -p option on the kwboot command. > > > nanddump --noecc --omitoob -f > mtd0.silverstore.stock /dev/mtd0 > > > The kwboot command would be: > > > kwboot -t -B 115200 /dev/ttyUSB0 -b >by garagoyun - Debian
bodhi Wrote: ------------------------------------------------------- > 2. The next thing to do is: > > a. Set up envs to boot with HDD rootfs. Let me > know when you are ready. Yes, anytime. I have managed to kill already 4 USB memory sticks :) > b. Try kwboot this box with serial console. It's > an exercise to see if it can be used to rescue the > box wby garagoyun - Debian
bodhi Wrote: ------------------------------------------------------- > Here is the new DTB. Hope this is the one! > > > I would like you to do 2 tests. > > 1. Append this DTB as you did. And boot into > Debian and > > > cat /proc/cmdline > cat /proc/mtd > cat /etc/fw_env.config > fw_printenv > root@silverdebian:~# cat /proc/cmdlinby garagoyun - Debian
bodhi Wrote: ------------------------------------------------------- > garagoyun, > > That's a little odd. I'd expected to see something > like this using hexedit. > > On the right handside, it shows the textual > representation of the hex. i.e this NAND area > contains u-boot envs, as we can see. Sorry, I used hexdump without ASCII. I have attacby garagoyun - Debian
bodhi Wrote: ------------------------------------------------------- > garagoyun , > > It looks as though the Debian mtd0 partition has > nothing on it! Please a hex dump/editor on both > stock's and Debian's mtd nanddump files to see if > that is true, and we can see the envs reside in > flash a little bit better. > > It might be a bug. But we neeby garagoyun - Debian
bodhi, Stock: ~ # nanddump --noecc --omitoob -f mtd1.silverstore.stock /dev/mtd1 Block size 131072, page size 2048, OOB size 64 Dumping data starting at 0x00000000 and ending at 0x00040000... ~ # ls -l mtd1.silverstore.stock -rw------- 1 root root 262144 Oct 5 13:06 mtd1.silverstore.stock Debian: root@silverdebian:~# nanddump --noecc --omitoob -f mtd1.silverstoreby garagoyun - Debian
bodhi, Thanks! Corrected now. root@silverdebian:~# cat /etc/fw_env.config # MTD device name Device offset Env. size Flash sector size Number of sectors /dev/mtd1 0x0 0x20000 0x20000 root@silverdebian:~# fw_printenv Warning: Bad CRC, using default environment bootargs= bootcmd= bootdelay=2 baudrate=115200 arch=sandbox cpu=sandbox board=sandbox boarby garagoyun - Debian
bodhi Wrote: ------------------------------------------------------- > Please get the output of these in stock and in > Debian. > > dmesg > cat /proc/mtd > cat /etc/fw_env.config > Please see attached. /etc/fw_env.config are the same as I have amended in debian to match the stock I also just now run fw_printenv command on the debian and received the followiby garagoyun - Debian
bodhi Wrote: ------------------------------------------------------- > > That's what I expected. But I thought it's worth a > conformation. > > To set u-boo envs in Debian, we would need solve > that CRC checksum error (basically your u-boot > envs are not accessible in Linux right now). Let me know if you would need any tests and info provided. Itby garagoyun - Debian
bodhi Wrote: ------------------------------------------------------- > garagoyun, > > Boot back to stock OS, and > > > which blparam > > > If that did not find blparam, then search for it > > cd / > find . -name '*blparam*' > The output is not from the device I am testing, as I have wiped the hard disk on it. Anyway there is nby garagoyun - Debian
bodhi, I assume I would need the latest U-Boot for Kirkwood if I want to use Ext4? Also, currently I am executing the following setenv commands via serial port at every boot. How do I make those permananet in uboot? Using fw_setenv? setenv mtdparts 'mtdparts=orion_nand:0x000a0000@0x0(uboot),0x00040000@0x000a0000(param),0x00280000@0x000e0000(preroot),0x00380000@0x00360000(uimage),0xby garagoyun - Debian
Tests seem to be successful. Sys and Power leds turn off and on respectively: root@debian:~# ls -l /sys/class/leds/ total 0 drwxr-xr-x 2 root root 0 Oct 2 14:47 . drwxr-xr-x 41 root root 0 Oct 2 14:43 .. lrwxrwxrwx 1 root root 0 Oct 2 14:47 hncn2:green:power -> ../../devices/platform/gpio-leds/leds/hncn2:green:power lrwxrwxrwx 1 root root 0 Oct 2 14:47 hncn2:green:sys -> ../.by garagoyun - Debian
Removed the post. The faults were due to "blk_update_request: I/O error, dev sda, sector 3715408". 3 usb stick memories failed until now.by garagoyun - Debian
Quotebodhi Did you test both buttons with POWER:/usr/bin/logger -s -i "POWER button pushed" RESTART:/usr/bin/logger -s -i "RESTART button pushed" Those commands are not triggered when I press the buttons. Nothing in the syslog. I need to replace POWER and RESTART with KEY_116 and KEY_408 respectively. Which results in the following output: root@silverdebian:~# taiby garagoyun - Debian
bodhi Wrote: ------------------------------------------------------- > garagoyun, > > Cool :) That has definitely made this box fully > functional to the point we want it to be. The rest > is icing on the cake. > Haha I am so chuffed! > > 1. The HDD rootfs is not difficult at all. What > you need to do is just remove the HDD, back it up > somewhere,by garagoyun - Debian
bodhi, That new DBT works beautifully. The satisfaction of success haha. Thanks very much for your immense help! Really appreciated. __ __ _ _ | \/ | __ _ _ ____ _____| | | | |\/| |/ _` | '__\ \ / / _ \ | | | | | | (_| | | \ V / __/ | | |_| |_|\__,_|_| \_/ \___|_|_| _ _ ____ _ | | |by garagoyun - Debian
bodhi, I had some spare time today to mess a bit with the device. Relying on the information from https://wikidevi.com/wiki/Freecom_SilverStore I did research which other devices have the same ETH chip: ETH chip1: Marvell 88F6282 ETH chip2: Marvell 88E1318 LAN speed: 10/100/1000 LAN ports: 1 Apparently, there are two other: Iomega StorCenter ix2-dl and Netgear ReadyNAS RND2000 v2 (Dby garagoyun - Debian