Pogoplug Mobile no light/ssh/serial connection May 02, 2017 10:52PM |
Registered: 6 years ago Posts: 6 |
Re: Pogoplug Mobile no light/ssh/serial connection May 03, 2017 03:08AM |
Admin Registered: 13 years ago Posts: 18,555 |
Quote
Important Note: If possible, try to test this boot image with UART booting before flashing to NAND. See davygravy's UART booting using kwboot instruction here in this thread. The latest u-boot image released here should be used for UART booting, if your box is the type that supports it (these do not: Dockstar, Pogo E02, iConnect).
Quote
To download ARM kwboot binary for UART booting at Dropbox
kwboot-2016.05.tar
md5:
76977c5a61544a5707dfa17ae832a3ad
sha256:
25ee4fa8a94372d2d398cac4704e9ee3ca87585c29e72e18323209b7f163209d
kwboot (this is an older version)
md5:
0efd011bdb244436e432a8de33e639a1
Re: Pogoplug Mobile no light/ssh/serial connection May 03, 2017 08:39AM |
Registered: 6 years ago Posts: 6 |
./kwboot -t -B 115200 /dev/ttyUSB0 -b uboot.goflexnet-IDEpatched-netconsoleON.kwb -p
Re: Pogoplug Mobile no light/ssh/serial connection May 03, 2017 12:24PM |
Admin Registered: 13 years ago Posts: 18,555 |
./kwboot -t -B 115200 /dev/ttyUSB0 -b uboot.2016.05-tld-1.pogo_v4.mtd0.kwb -p
Re: Pogoplug Mobile no light/ssh/serial connection May 06, 2017 09:35AM |
Registered: 6 years ago Posts: 6 |
Re: Pogoplug Mobile no light/ssh/serial connection May 06, 2017 01:36PM |
Registered: 6 years ago Posts: 6 |
Sending boot message. Please reboot the target...\ Sending boot image... 0 % [......................................................................] 1 % [......................................................................] 3 % [......................................................................] 99 % [....................................] [Type Ctrl-\ + c to quit] U-Boot 2016.05-tld-1 (Jun 12 2016 - 13:41:47 -0700) Pogoplug V4 SoC: Kirkwood 88F6192_A1 DRAM: 128 MiB WARNING: Caches not enabled NAND: 128 MiB MMC: kwsdio: 0 In: serial Out: serial Err: serial Net: egiga0 No link on egiga0 ping failed; host 192.168.1.100 is not alive Hit any key to stop autoboot: 0 ## Error: "bootcmd_usb" not defined ## Error: "bootcmd_mmc" not defined ## Error: "bootcmd_sata" not defined mtdids not defined, no default present Error initializing mtdparts! resetting ...
Booting the Pogo V4 with the default envs using uEnv.txt May 07, 2017 12:09PM |
Admin Registered: 13 years ago Posts: 18,555 |
su cp -a uboot.2016.05-tld-1.environment /media/sdb1/boot/uEnv.txt
devices=usb mmc ide dtb_file=/boot/dts/kirkwood-pogoplug_v4.dtb
sync umount /media/sdb1
Re: Pogoplug Mobile no light/ssh/serial connection May 07, 2017 04:18PM |
Registered: 6 years ago Posts: 6 |
Re: Pogoplug Mobile no light/ssh/serial connection May 08, 2017 01:12AM |
Admin Registered: 13 years ago Posts: 18,555 |
Re: Pogoplug Mobile no light/ssh/serial connection May 10, 2017 05:57PM |
Registered: 6 years ago Posts: 6 |
Re: Pogoplug Mobile no light/ssh/serial connection May 11, 2017 01:10PM |
Admin Registered: 13 years ago Posts: 18,555 |
Quote
Updated 20 Feb 2016:
This Debian-4.4.0-kirkwood-tld-1-rootfs-bodhi.tar.bz2 is to keep in sync with kernel Linux-4.4.0-kirkwood-tld-1
Quote
B. Flashing default u-boot envs image
This default envs image supports booting with multiple disk drives (and hubs) attached. The disk drives could be any type (usb, sata, sd card). The scanning logic and default envs were set to automatically boot the box with the following required configuration:
For whatever reason, if you can't set up your configuration to satisfy the following 4 requirements, then don't flash this defaut envs image. It might not boot properly. In this case, section C below can be used to tailor the envs to your specific configuration.
r1. There must be only one partition among all partitions from all drives that contains the kernel files. The 2 kernel files are /boot/uImage and /boot/uInitrd.
r2. The partition that contains the 2 kernel files must be partition 1 in a disk drive
r3. The partition that contains the rootfs must be labeled rootfs
r4. The rootfs partition is recommended to be type Ext3 (this is not a hard requirement, ext4 should boot OK, but Ext3 will ensure no problem).
So the bottom line is if you have only one rootfs in a single Ext3 partition, which is labeled as rootfs, then you're all set.
a. Download the default u-boot envs at Dropbox:
uboot.2016.05-tld-1.environment.bodhi.tar
md5:
3823eef10011b864859d31a76470e0e3
sha256:
c8db95a4225e8d78bdaaaa372bd5a87e4b98f3448dd9c62fc96c72b2df1a997c
This tarball includes 3 files:
uboot.2016.05-tld-1.environment.img (the default envs image to be flashed)
uboot.2016.05-tld-1.environment (the content of the default envs in text format)
uboot.2016.05-tld-1.environment.64K.img (small envs image to be flashed on HP T5325 only).