Thank you very much...pogo is booting again. What about step B. Flashing default u-boot envs image and C. Add uEnv.txt to /boot directory, which I left out when I updated u-boot. Do I have to do this?by sambo - Debian
1. sorry, here the beginning: U-Boot 2016.05-tld-1 (Jun 12 2016 - 13:23:43 -0700) Pogo E02 SoC: Kirkwood 88F6281_A0 DRAM: 256 MiB WARNING: Caches not enabled NAND: 128 MiB In: serial Out: serial Err: serial Net: egiga0 Using egiga0 device ping failed; host 192.168.1.100 is not alive Hit any key to stop autoboot: 0 starting USB... 2. I think I did step 4a and theby sambo - Debian
1. starting USB... USB0: USB EHCI 1.00 scanning bus 0 for devices... 3 USB Device(s) found scanning usb for storage devices... 1 Storage Device(s) found 10446 bytes read in 215 ms (46.9 KiB/s) 3267550 bytes read in 504 ms (6.2 MiB/s) 6766192 bytes read in 332 ms (19.4 MiB/s) ## Booting kernel from Legacy Image at 00800000 ... Image Name: Linux-4.6.0-kirkwood-tld-1 Creatby sambo - Debian
Hi, I've been using my pogo quite a while. Yesterday I decided to update kernel to 4.6.0. Before that I updated uboot to 2016.05, but unfortunately forgot to do step B. Flashing default u-boot envs image and step C. Add uEnv.txt to /boot directory. Nevertheless I continued to update kernel. Now the pogo doesn't boot. This is my uboot env: printenv baudrate=115200 bootargsby sambo - Debian