Welcome! Log In Create A New Profile

Advanced

Installing OpenWRT onto PogoPlug E02?

Posted by rynax 
Installing OpenWRT onto PogoPlug E02?
September 04, 2016 07:09PM
Hi,

Just updated the uboot to 2016.05 U-Boot Kirkwood
Anyone has experience with installing OpenWRT onto the box's nand flash or external USB?

I've tried the instruction for installing op onto pogoplug mobile,
http://blog.qnology.com/2015/02/openwrt-on-pogoplug-mobile.html

by replacing the rootfs, zImage and dtb file using the Pogoplug E02's one,
it seems to boot fine but I can't get access to the box either via dhcp or static ip.
Here's the boot log:

Trying to boot from NAND ...
invalid partition number 2 for device nand0 (orion_nand)
no such partition
ubi0: attaching mtd1
ubi0: scanning is finished
ubi0: attached mtd1 (name "mtd=1", size 127 MiB)
ubi0: PEB size: 131072 bytes (128 KiB), LEB size: 129024 bytes
ubi0: min./max. I/O unit sizes: 2048/2048, sub-page size 512
ubi0: VID header offset: 512 (aligned 512), data offset: 2048
ubi0: good PEBs: 1014, bad PEBs: 2, corrupted PEBs: 0
ubi0: user volume: 1, internal volumes: 1, max. volumes count: 128
ubi0: max/mean erase counter: 3/1, WL threshold: 4096, image sequence number: 1535965568
ubi0: available PEBs: 0, total reserved PEBs: 1014, PEBs reserved for bad PEB handling: 18
Loading file '/boot/zImage' to addr 0x00800000...
Done
Loading file '/boot/openwrt-15.05-kirkwood-pogo_e02.dtb' to addr 0x01c00000...
Done
Unmounting UBIFS volume rootfs!
Booting from nand ...
Kernel image @ 0x800000 [ 0x000000 - 0x181e40 ]
## Flattened Device Tree blob at 01c00000
Booting using the fdt blob at 0x1c00000


Starting kernel ...


Thanks in advance.



Edited 1 time(s). Last edit at 09/04/2016 07:12PM by rynax.
Re: Installing OpenWRT onto PogoPlug E02?
September 04, 2016 08:47PM
Just checking with you, hope not to offend you, but did you see this?

"
At this point, we're ready to boot into OpenWRT. Note that by default, OpenWRT will default to 192.168.1.1 and will act as a DHCP Server. Plug a network cable from your computer directly into the Pogoplug and power it on. You should now be able to Telnet into the Pogoplug at 192.168.1.1 (username and password not required). Note that SSH is disabled and will automatically start after a root password is set.
"

I got OpenWRT going on a PogoPro-v3, but until I did Telnet straight from computer to Pogo it wouldn't work.
Pretty cool though once it works!

=========
-= Cloud 9 =-



Edited 1 time(s). Last edit at 09/04/2016 08:49PM by JoeyPogoPlugE02.
Re: Installing OpenWRT onto PogoPlug E02?
September 04, 2016 10:52PM
JoeyPogoPlugE02 Wrote:
-------------------------------------------------------
> Just checking with you, hope not to offend you,
> but did you see this?
>
> "
> At this point, we're ready to boot into OpenWRT.
> Note that by default, OpenWRT will default to
> 192.168.1.1 and will act as a DHCP Server. Plug a
> network cable from your computer directly into the
> Pogoplug and power it on. You should now be able
> to Telnet into the Pogoplug at 192.168.1.1
> (username and password not required). Note that
> SSH is disabled and will automatically start after
> a root password is set.
> "
>
> I got OpenWRT going on a PogoPro-v3, but until I
> did Telnet straight from computer to Pogo it
> wouldn't work.
> Pretty cool though once it works!


Yes I did that, but can't get access to the box either via dhcp or static ip
Re: Installing OpenWRT onto PogoPlug E02?
September 04, 2016 11:53PM
rynax Wrote:
-------------------------------------------------------
> Yes I did that, but can't get access to the box
> either via dhcp or static ip

Sorry about that! I was just passing by, but would expect someone who knows the answer to say something. At least we ruled-out one. Anyway congratulations for having twice the RAM as everyone else's OpenWRT :-)

=========
-= Cloud 9 =-
Re: Installing OpenWRT onto PogoPlug E02?
September 12, 2016 02:30PM
I had similar issues http://forum.doozan.com/read.php?3,29780

Your kernel does not even boot. That log is about uboot only.

the build system screws up the zimages it places in the /bin/target/bla/bla by adding some hex to them.

you need to take the zImage from inside the build system, not from the /bin/target/bla/bla

Do a file search in the source folders after compilation for zimage, and use that.
Author:

Subject:


Spam prevention:
Please, enter the code that you see below in the input field. This is for blocking bots that try to post this form automatically. If the code is hard to read, then just try to guess it right. If you enter the wrong code, a new image is created and you get another chance to enter it right.
Message: