OpenWRT on Pogoplug Pro / V3 - Need Help Making U-boot Work
Posted by LeggoMyEggo
|
OpenWRT on Pogoplug Pro / V3 - Need Help Making U-boot Work March 31, 2015 04:53PM |
Registered: 9 years ago Posts: 429 |
Anybody daring out there can you figure out how to get OpenWRT and a stable u-boot working on the Pro / V3 ? See my contribution here: https://forum.openwrt.org/viewtopic.php?pid=270503#p270503 You see I've tried but am not skilled enough to get around the u-boot issues. Hoping someone could figure it out as I think the Pro / V3 with built in mPCI-e wifi with Atheros 300M card would make a perfect router / AP: Not taking anything away from this site, I've got my other plugs running bodhi's Debian :)
|
Re: OpenWRT on Pogoplug Pro / V3 - Need Help Making U-boot Work March 31, 2015 06:06PM |
Admin Registered: 13 years ago Posts: 18,997 |
LeggoMyEggo,
1. How far did you go in booting with NAND u-boot? pls post serial console log.
2. If you've already doing that what are the show stoppers now?
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
1. How far did you go in booting with NAND u-boot? pls post serial console log.
2. If you've already doing that what are the show stoppers now?
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: OpenWRT on Pogoplug Pro / V3 - Need Help Making U-boot Work March 31, 2015 08:52PM |
Registered: 9 years ago Posts: 429 |
Here is what I get when I try to boot unsupervised
Notice I have overlapping u-boots.
Despite saving the boot environment to boot from the OpenWRT firmware, it doesn't appear to "stick" so the Pro does not boot properly into OpenWRT.
Edited 1 time(s). Last edit at 03/31/2015 08:53PM by LeggoMyEggo.
U-Boot SPL 2013.10-tld-4 (Sep 07 2014 - 14:10:12) Boot device: NAND Attempting to set PLLA to 850 MHz ... plla_ctrl0 : 0000020a plla_ctrl1 : 00330000 plla_ctrl2 : 0065008b plla_ctrl3 : 000000f1 PLLA Set U-Boot 2013.10-tld-5 (Mar 07 2015 - 16:50:17) for OXNAS DRAM: 128 MiB NAND: 128 MiB In: serial Out: serial Err: serial Net: Led: GREEN mii0 Main Loop Waiting for PHY auto negotiation to complete... done ENET Speed is 1000 Mbps - FULL duplex connection Using mii0 device ping failed; host 192.168.1.2 is not alive Hit any key to stop autoboot: 0 NAND read: device 0 offset 0x440000, size 0x90000 589824 bytes read: OK ## Starting application at 0x64000000 ... U-Boot 2014.10 (Mar 28 2015 - 05:38:44) for OXNAS DRAM: 128 MiB NAND: 128 MiB UBI: attaching mtd1 to ubi0 UBI: scanning is finished UBI: attached mtd1 (name "mtd=1", size 114 MiB) to ubi0 UBI: PEB size: 131072 bytes (128 KiB), LEB size: 129024 bytes UBI: min./max. I/O unit sizes: 2048/2048, sub-page size 512 UBI: VID header offset: 512 (aligned 512), data offset: 2048 UBI: good PEBs: 912, bad PEBs: 0, corrupted PEBs: 0 UBI: user volume: 1, internal volumes: 1, max. volumes count: 128 UBI: max/mean erase counter: 2/0, WL threshold: 4096, image sequence number: 0 UBI: available PEBs: 0, total reserved PEBs: 912, PEBs reserved for bad PEB handling: 9 Volume ubootenv not found! ** Unable to read env from ubi:ubootenv ** Volume ubootenv2 not found! ** Unable to read redundant env from ubi:ubootenv2 ** *** Warning - bad CRC, using default environment In: serial Out: serial Err: serial Net: dwmac.40400000 Error: dwmac.40400000 address not set. IDE: SATA PHY not ready for device 0 SATA PHY not ready for device 1 ide_preinit failed Hit any key to stop autoboot: 0 Wrong Image Format for bootm command ERROR: can't get kernel image! Saving Environment to UBI... UBI: detaching mtd1 from ubi0 UBI: mtd1 is detached from ubi0 UBI: attaching mtd1 to ubi0 UBI: scanning is finished UBI: attached mtd1 (name "mtd=1", size 114 MiB) to ubi0 UBI: PEB size: 131072 bytes (128 KiB), LEB size: 129024 bytes UBI: min./max. I/O unit sizes: 2048/2048, sub-page size 512 UBI: VID header offset: 512 (aligned 512), data offset: 2048 UBI: good PEBs: 912, bad PEBs: 0, corrupted PEBs: 0 UBI: user volume: 1, internal volumes: 1, max. volumes count: 128 UBI: max/mean erase counter: 2/0, WL threshold: 4096, image sequence number: 0 UBI: available PEBs: 0, total reserved PEBs: 912, PEBs reserved for bad PEB handling: 9 Writing to redundant UBI... Volume ubootenv2 not found! ** Unable to write env to ubi:ubootenv2 ** Read 0 bytes from volume kernel to 62000000 Volume kernel not found! NAND read: device 0 offset 0x4e0000, size 0x400000 4194304 bytes read: OK Wrong Image Format for bootm command ERROR: can't get kernel image! dwmac.40400000 Waiting for PHY auto negotiation to complete......... TIMEOUT ! Waiting for PHY realtime link. done Speed: 1000, full duplex *** ERROR: `ethaddr' not set Speed: 1000, full duplex
Notice I have overlapping u-boots.
Despite saving the boot environment to boot from the OpenWRT firmware, it doesn't appear to "stick" so the Pro does not boot properly into OpenWRT.
Edited 1 time(s). Last edit at 03/31/2015 08:53PM by LeggoMyEggo.
|
Re: OpenWRT on Pogoplug Pro / V3 - Need Help Making U-boot Work April 01, 2015 12:44AM |
Admin Registered: 13 years ago Posts: 18,997 |
LeggoMyEggo,
>
> Notice I have overlapping u-boots.
>
Why would you have overlaping u-boot?
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
>
> Notice I have overlapping u-boots.
>
Why would you have overlaping u-boot?
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: OpenWRT on Pogoplug Pro / V3 - Need Help Making U-boot Work April 01, 2015 05:51AM |
Registered: 9 years ago Posts: 429 |
|
Re: OpenWRT on Pogoplug Pro / V3 - Need Help Making U-boot Work April 01, 2015 06:37AM |
Admin Registered: 13 years ago Posts: 18,997 |
LeggoMyEggo,
> Per the above, two u-boots are loaded in
> sequence.
Ah! sorry I did not read the log closely, you are chainloading the OpenWrt u-boot from my u-boot, both were flashed to NAND. I don't think this chainloading is needed. Have you tried to boot without chainloading?
Or you could have just coppied the OpenWrt u-boot envs and put that in uEnv.txt, and boot. I have not seen the OpenWrt envs, so can't be sure if it will need adjustment, though. But that's should be easy. In fact, I think we just need to examine it to make sure there is nothing peculiar about the setup. But the booting setup for a box should be the same (with-and-without-uInitrd options taken care of).
>
> Do you think the OpenWRT u-boot could be written
> to a sata drive and dd'ed as stage 1 similar to
> the rescue technique?
No, I don't think it will work. The SATA version needs to be built with SATA option (instead of NAND option).
If you can point me to where to download the OpenWRT rootfs tarball, I'll take a look.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
> Per the above, two u-boots are loaded in
> sequence.
Ah! sorry I did not read the log closely, you are chainloading the OpenWrt u-boot from my u-boot, both were flashed to NAND. I don't think this chainloading is needed. Have you tried to boot without chainloading?
Or you could have just coppied the OpenWrt u-boot envs and put that in uEnv.txt, and boot. I have not seen the OpenWrt envs, so can't be sure if it will need adjustment, though. But that's should be easy. In fact, I think we just need to examine it to make sure there is nothing peculiar about the setup. But the booting setup for a box should be the same (with-and-without-uInitrd options taken care of).
>
> Do you think the OpenWRT u-boot could be written
> to a sata drive and dd'ed as stage 1 similar to
> the rescue technique?
No, I don't think it will work. The SATA version needs to be built with SATA option (instead of NAND option).
If you can point me to where to download the OpenWRT rootfs tarball, I'll take a look.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: OpenWRT on Pogoplug Pro / V3 - Need Help Making U-boot Work April 01, 2015 07:58AM |
Registered: 9 years ago Posts: 429 |
Here are the downloads: https://downloads.openwrt.org/snapshots/trunk/oxnas/generic/
I chainloaded the u-boots because I wasn't sure how to erase yours and not risk bricking the plug. Plus even if I had erased yours, I wasn't sure where to put the uboot environment file (for the OpenWRT u-boot) and what to even name it. And even if I figured these out, what to include in the environment file? I noticed some slight differences in the OpenWRT forum posts regarding environment variables.
The openwrt-oxnas-ox820-u-boot.bin is what I thought I could put as stage 1 using dd to a sata drive. But you say it has to be a specially prepared file for this (to be used as stage 1)?
Edit: OK, I thought more about your comment about using uEnv.txt to boot the OpenWRT uImage file. If that were the case, do I even need to flash the OpenWRT u-boot file to nand? In other words, could I just use your u-boot and through uEnv.txt load the OpenWRT uImage file into memory and boot that?
Edited 3 time(s). Last edit at 04/01/2015 08:47AM by LeggoMyEggo.
I chainloaded the u-boots because I wasn't sure how to erase yours and not risk bricking the plug. Plus even if I had erased yours, I wasn't sure where to put the uboot environment file (for the OpenWRT u-boot) and what to even name it. And even if I figured these out, what to include in the environment file? I noticed some slight differences in the OpenWRT forum posts regarding environment variables.
The openwrt-oxnas-ox820-u-boot.bin is what I thought I could put as stage 1 using dd to a sata drive. But you say it has to be a specially prepared file for this (to be used as stage 1)?
Edit: OK, I thought more about your comment about using uEnv.txt to boot the OpenWRT uImage file. If that were the case, do I even need to flash the OpenWRT u-boot file to nand? In other words, could I just use your u-boot and through uEnv.txt load the OpenWRT uImage file into memory and boot that?
Edited 3 time(s). Last edit at 04/01/2015 08:47AM by LeggoMyEggo.
|
Re: OpenWRT on Pogoplug Pro / V3 - Need Help Making U-boot Work April 01, 2015 12:45PM |
Registered: 9 years ago Posts: 429 |
More rambling. So lets say I get the OpenWRT kernel to boot off of your u-boot. So I boot into OpenWRT and configure it to my liking. I also enable either the pivot root or ext-root function of OpenWRT which allows for the placement of rootfs on USB or IDE storage. So I am wondering when I go to shutdown, will OpenWRT attempt to save those changes and packages I loaded to USB storage or to NAND (which is the default)? If I booted from USB, obviously it's bad if it will only save to NAND. But if it saves to the USB, it will be just like your setup.
Here is some info on the ext-root: function:http://wiki.openwrt.org/doc/howto/extroot/extroot.theory. Notice the mention of this site : "The OEM bootloader of the dockstar is actually NOT capable of booting from USB, only the version provided by Jeff Doozan is! Hello, FOSS ;-) "
Edited 1 time(s). Last edit at 04/01/2015 12:48PM by LeggoMyEggo.
Here is some info on the ext-root: function:http://wiki.openwrt.org/doc/howto/extroot/extroot.theory. Notice the mention of this site : "The OEM bootloader of the dockstar is actually NOT capable of booting from USB, only the version provided by Jeff Doozan is! Hello, FOSS ;-) "
Edited 1 time(s). Last edit at 04/01/2015 12:48PM by LeggoMyEggo.
|
Re: OpenWRT on Pogoplug Pro / V3 - Need Help Making U-boot Work April 01, 2015 01:10PM |
Registered: 10 years ago Posts: 1,037 |
|
Re: OpenWRT on Pogoplug Pro / V3 - Need Help Making U-boot Work April 01, 2015 01:43PM |
Registered: 9 years ago Posts: 429 |
Gravelrash Wrote:
-------------------------------------------------------
> If you want another PPV3 to use as a test box - i
> have one running with an atheros based card that i
> will gladly use it to assist with testing
If you are running bodhi's latest u-boot (tld-5) for Oxnas, you can try this:
1) Format a USB drive ext2 and label it rootfs
2) Create a boot directory on that USB disk
3) Copy the openwrt-oxnas-pogoplug-pro-fit-uImage-initramfs.itb file from the OpenWRT site to /boot. While you are at it go ahead and copy the other files from OpenWRT except the compile sources.
4) Connect serial console to the V3. Turn on power and interrupt boot.
5) Use the following CLI instructions:
setenv bootargs 'console=ttyS0,115200 root=/dev/sda1 rootdelay=10'
usb start
ext2load usb 0:1 0x62000000 /boot/openwrt-oxnas-pogoplug-pro-fit-uImage-initramfs.itb
bootm 0x62000000
Now that should get you to the OpenWRT busybox CLI. Once there, you need to do three things; 1) set a passwd by using 'passwd' and that enables SSH 2) Google for how to set eth0 in OpenWRT to dhcp so you can then SSH to the Plug on your LAN. You have to use vi BTW which I hate :( 3) Mount /dev/tmp to /overlay so you have more storage space otherwise you won't be able to update via opkg.
Do an opkg update and you will also need to opkg the LuCi gui and usb kmod's to enable web access and usb storage (respectively).
LMK how that works.
Edited 3 time(s). Last edit at 04/01/2015 02:30PM by LeggoMyEggo.
-------------------------------------------------------
> If you want another PPV3 to use as a test box - i
> have one running with an atheros based card that i
> will gladly use it to assist with testing
If you are running bodhi's latest u-boot (tld-5) for Oxnas, you can try this:
1) Format a USB drive ext2 and label it rootfs
2) Create a boot directory on that USB disk
3) Copy the openwrt-oxnas-pogoplug-pro-fit-uImage-initramfs.itb file from the OpenWRT site to /boot. While you are at it go ahead and copy the other files from OpenWRT except the compile sources.
4) Connect serial console to the V3. Turn on power and interrupt boot.
5) Use the following CLI instructions:
setenv bootargs 'console=ttyS0,115200 root=/dev/sda1 rootdelay=10'
usb start
ext2load usb 0:1 0x62000000 /boot/openwrt-oxnas-pogoplug-pro-fit-uImage-initramfs.itb
bootm 0x62000000
Now that should get you to the OpenWRT busybox CLI. Once there, you need to do three things; 1) set a passwd by using 'passwd' and that enables SSH 2) Google for how to set eth0 in OpenWRT to dhcp so you can then SSH to the Plug on your LAN. You have to use vi BTW which I hate :( 3) Mount /dev/tmp to /overlay so you have more storage space otherwise you won't be able to update via opkg.
Do an opkg update and you will also need to opkg the LuCi gui and usb kmod's to enable web access and usb storage (respectively).
LMK how that works.
Edited 3 time(s). Last edit at 04/01/2015 02:30PM by LeggoMyEggo.
|
Re: OpenWRT on Pogoplug Pro / V3 - Need Help Making U-boot Work April 01, 2015 03:14PM |
Admin Registered: 13 years ago Posts: 18,997 |
LeggoMyEggo,
> In other words,
> could I just use your u-boot and through uEnv.txt
> load the OpenWRT uImage file into memory and boot
> that?
This is what I think you should try.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
> In other words,
> could I just use your u-boot and through uEnv.txt
> load the OpenWRT uImage file into memory and boot
> that?
This is what I think you should try.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: OpenWRT on Pogoplug Pro / V3 - Need Help Making U-boot Work April 01, 2015 04:40PM |
Registered: 9 years ago Posts: 429 |
It wouldn't boot unless I loaded the OpenWRT u-boot into memory. This time I didn't save the OpenWRT u-boot to nand and when I ended up at the OpenWRT busybox CLI, I couldn't load any packages even though I could update and ping the internet. I am thinking at this point to make this work permanently that the OpenWRT u-boot has to be the only one installed which leads to the same issue of how to do the boot environment file, what to name it and where does it go.
Here was my latest attempt:
Edited 1 time(s). Last edit at 04/01/2015 05:55PM by LeggoMyEggo.
Here was my latest attempt:
U-Boot 2013.10-tld-5 (Mar 07 2015 - 16:50:17) for OXNAS
DRAM: 128 MiB
NAND: 128 MiB
In: serial
Out: serial
Err: serial
Net:
Led: GREEN
mii0
Main Loop
Hit any key to stop autoboot: 0
OX820> setenv bootargs 'console=ttyS0,115200 root=/dev/sda1 rootdelay=10'
OX820> usb start
(Re)start 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
OX820> ext2load usb 0:1 0x62000000 /boot/openwrt-oxnas-pogoplug-pro-fit-uImage-initramfs.itb
3384756 bytes read in 353 ms (9.1 MiB/s)
OX820> bootm 0x62000000
Wrong Image Format for bootm command
Led: ORANGE (Failed)
ERROR: can't get kernel image!
OX820> bootm
Wrong Image Format for bootm command
Led: ORANGE (Failed)
ERROR: can't get kernel image!
OX820> usb start
(Re)start 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
OX820> ext2load usb 0:1 64000000 openwrt-oxnas-ox820-u-boot.bin
** File not found openwrt-oxnas-ox820-u-boot.bin **
OX820> ext2load usb 0:1 64000000 /boot/openwrt-oxnas-ox820-u-boot.bin
550144 bytes read in 144 ms (3.6 MiB/s)
OX820> setenv boot_openwrt nand read 0x64000000 0x440000 0x90000 \; go 64000000
OX820> setenv bootcmd run boot_openwrt
OX820> go 64000000
## Starting application at 0x64000000 ...
U-Boot 2014.10 (Mar 28 2015 - 05:38:44) for OXNAS
DRAM: 128 MiB
NAND: 128 MiB
UBI: attaching mtd1 to ubi0
UBI: scanning is finished
UBI: attached mtd1 (name "mtd=1", size 114 MiB) to ubi0
UBI: PEB size: 131072 bytes (128 KiB), LEB size: 129024 bytes
UBI: min./max. I/O unit sizes: 2048/2048, sub-page size 512
UBI: VID header offset: 512 (aligned 512), data offset: 2048
UBI: good PEBs: 912, bad PEBs: 0, corrupted PEBs: 0
UBI: user volume: 1, internal volumes: 1, max. volumes count: 128
UBI: max/mean erase counter: 2/0, WL threshold: 4096, image sequence number: 0
UBI: available PEBs: 0, total reserved PEBs: 912, PEBs reserved for bad PEB handling: 9
Volume ubootenv not found!
** Unable to read env from ubi:ubootenv **
Volume ubootenv2 not found!
** Unable to read redundant env from ubi:ubootenv2 **
*** Warning - bad CRC, using default environment
In: serial
Out: serial
Err: serial
Net: dwmac.40400000
Error: dwmac.40400000 address not set.
IDE: SATA PHY not ready for device 0
SATA PHY not ready for device 1
ide_preinit failed
Hit any key to stop autoboot: 0
Wrong Image Format for bootm command
ERROR: can't get kernel image!
Saving Environment to UBI...
UBI: detaching mtd1 from ubi0
UBI: mtd1 is detached from ubi0
UBI: attaching mtd1 to ubi0
UBI: scanning is finished
UBI: attached mtd1 (name "mtd=1", size 114 MiB) to ubi0
UBI: PEB size: 131072 bytes (128 KiB), LEB size: 129024 bytes
UBI: min./max. I/O unit sizes: 2048/2048, sub-page size 512
UBI: VID header offset: 512 (aligned 512), data offset: 2048
UBI: good PEBs: 912, bad PEBs: 0, corrupted PEBs: 0
UBI: user volume: 1, internal volumes: 1, max. volumes count: 128
UBI: max/mean erase counter: 2/0, WL threshold: 4096, image sequence number: 0
UBI: available PEBs: 0, total reserved PEBs: 912, PEBs reserved for bad PEB handling: 9
Writing to redundant UBI... Volume ubootenv2 not found!
** Unable to write env to ubi:ubootenv2 **
Read 0 bytes from volume kernel to 62000000
Volume kernel not found!
NAND read: device 0 offset 0x4e0000, size 0x400000
4194304 bytes read: OK
Wrong Image Format for bootm command
ERROR: can't get kernel image!
dwmac.40400000 Waiting for PHY auto negotiation to complete....... done
Speed: 1000, full duplex
*** ERROR: `ethaddr' not set
Speed: 1000, full duplex
OX820 # setenv bootargs 'console=ttyS0,115200 root=/dev/sda1 rootdelay=10'
OX820 # usb start
(Re)start 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
OX820 # ext2load usb 0:1 0x62000000 /boot/openwrt-oxnas-pogoplug-pro-fit-uImage-initramfs.itb
3384756 bytes read in 354 ms (9.1 MiB/s)
OX820 # bootm 0x62000000
## Loading kernel from FIT Image at 62000000 ...
Using 'config@1' configuration
Trying 'kernel@1' kernel subimage
Description: ARM OpenWrt Linux-3.18.9
Type: Kernel Image
Compression: uncompressed
Data Start: 0x620000e4
Data Size: 3376416 Bytes = 3.2 MiB
Architecture: ARM
OS: Linux
Load Address: 0x60008000
Entry Point: 0x60008000
Hash algo: crc32
Hash value: dbd80180
Hash algo: sha1
Hash value: bd1f8b51aabb3cc90b55e1b1d6e4808923fe0a30
Verifying Hash Integrity ... crc32+ sha1+ OK
## Loading fdt from FIT Image at 62000000 ...
Using 'config@1' configuration
Trying 'fdt@1' fdt subimage
Description: ARM OpenWrt pogoplug-pro device tree blob
Type: Flat Device Tree
Compression: uncompressed
Data Start: 0x6233873c
Data Size: 6993 Bytes = 6.8 KiB
Architecture: ARM
Hash algo: crc32
Hash value: 15dce0d6
Hash algo: sha1
Hash value: 08c70cb4db38f437b6000b26305b49052be3345a
Verifying Hash Integrity ... crc32+ sha1+ OK
Booting using the fdt blob at 0x6233873c
Loading Kernel Image ... OK
Loading Device Tree to 67e1d000, end 67e21b50 ... OK
Starting kernel ...
Uncompressing Linux... done, booting the kernel.
[ 0.000000] Booting Linux on physical CPU 0x0
[ 0.000000] Linux version 3.18.9 (thepeople@viasatpilot) (gcc version 4.8.3 (OpenWrt/Linaro GCC 4.8-2014.04 r45073) ) #2 SMP Sat Mar 28 16:24:40 CET 2015
[ 0.000000] CPU: ARMv6-compatible processor [410fb025] revision 5 (ARMv7), cr=00c5787d
[ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
[ 0.000000] Machine model: Pogoplug Pro
[ 0.000000] Memory policy: Data cache writealloc
[ 0.000000] DT missing boot CPU MPIDR[23:0], fall back to default cpu_logical_map
[ 0.000000] PERCPU: Embedded 9 pages/cpu @c7ee1000 s6880 r8192 d21792 u36864
[ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 32512
[ 0.000000] Kernel command line: console=ttyS0,115200 root=/dev/sda1 rootdelay=10
[ 0.000000] PID hash table entries: 512 (order: -1, 2048 bytes)
[ 0.000000] Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
[ 0.000000] Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
[ 0.000000] Memory: 119512K/131072K available (3260K kernel code, 179K rwdata, 904K rodata, 5728K init, 217K bss, 11560K reserved)
[ 0.000000] Virtual kernel memory layout:
[ 0.000000] vector : 0xffff0000 - 0xffff1000 ( 4 kB)
[ 0.000000] fixmap : 0xffc00000 - 0xffe00000 (2048 kB)
[ 0.000000] vmalloc : 0xc8800000 - 0xff000000 ( 872 MB)
[ 0.000000] lowmem : 0xc0000000 - 0xc8000000 ( 128 MB)
[ 0.000000] modules : 0xbf000000 - 0xc0000000 ( 16 MB)
[ 0.000000] .text : 0xc0008000 - 0xc04193fc (4165 kB)
[ 0.000000] .init : 0xc041a000 - 0xc09b2000 (5728 kB)
[ 0.000000] .data : 0xc09b2000 - 0xc09ded70 ( 180 kB)
[ 0.000000] .bss : 0xc09ded70 - 0xc0a15394 ( 218 kB)
[ 0.000000] Hierarchical RCU implementation.
[ 0.000000] NR_IRQS:160
[ 0.000017] sched_clock: 24 bits at 390kHz, resolution 2560ns, wraps every 42949670400ns
[ 0.000289] Calibrating delay loop... 339.14 BogoMIPS (lpj=1695744)
[ 0.050055] pid_max: default: 32768 minimum: 301
[ 0.050301] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
[ 0.050321] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
[ 0.050995] CPU: Testing write buffer coherency: ok
[ 0.051348] Setting up static identity map for 0x600115f8 - 0x60011630
[ 0.053396] CPU1: Booted secondary processor
[ 0.110182] Brought up 2 CPUs
[ 0.110205] SMP: Total of 2 processors activated (678.29 BogoMIPS).
[ 0.113661] pinctrl core: initialized pinctrl subsystem
[ 0.116254] NET: Registered protocol family 16
[ 0.116743] DMA: preallocated 256 KiB pool for atomic coherent allocations
[ 0.140052] cpuidle: using governor ladder
[ 0.160028] cpuidle: using governor menu
[ 0.165427] gpio-oxnas 44000000.gpio: at address c8848000
[ 0.165795] gpio-oxnas 44100000.gpio: at address c884a000
[ 0.166359] pinctrl-oxnas pinctrl: initialized OX820 pinctrl driver
[ 0.312496] oxnas-pcie 47c00000.pcie-controller: PCIe version/deviceID 0x82510b5
[ 0.312614] oxnas-pcie 47c00000.pcie-controller: link up
[ 0.312903] oxnas-pcie 47c00000.pcie-controller: PCI host bridge to bus 0000:00
[ 0.312939] pci_bus 0000:00: root bus resource [mem 0x48000000-0x49ffffff]
[ 0.312957] pci_bus 0000:00: root bus resource [mem 0x4a000000-0x4bdfffff pref]
[ 0.312975] pci_bus 0000:00: root bus resource [io 0x0000-0xfffff]
[ 0.312993] pci_bus 0000:00: root bus resource [bus 00-7f]
[ 0.313566] PCI: bus0: Fast back to back transfers disabled
[ 0.313676] pci 0000:00:00.0: BAR 0: assigned [mem 0x48000000-0x4807ffff 64bit]
[ 0.313715] pci 0000:00:00.0: BAR 6: assigned [mem 0x4a000000-0x4a00ffff pref]
[ 0.314542] SCSI subsystem initialized
[ 0.315266] usbcore: registered new interface driver usbfs
[ 0.315404] usbcore: registered new interface driver hub
[ 0.315543] usbcore: registered new device driver usb
[ 0.315786] pps_core: LinuxPPS API ver. 1 registered
[ 0.315804] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
[ 0.315898] PTP clock support registered
[ 0.317378] Switched to clocksource rps_clocksource_timer
[ 0.319646] NET: Registered protocol family 2
[ 0.320808] TCP established hash table entries: 1024 (order: 0, 4096 bytes)
[ 0.320860] TCP bind hash table entries: 1024 (order: 1, 8192 bytes)
[ 0.320898] TCP: Hash tables configured (established 1024 bind 1024)
[ 0.321011] TCP: reno registered
[ 0.321041] UDP hash table entries: 256 (order: 1, 8192 bytes)
[ 0.321100] UDP-Lite hash table entries: 256 (order: 1, 8192 bytes)
[ 0.321420] NET: Registered protocol family 1
[ 0.407457] futex hash table entries: 512 (order: 2, 16384 bytes)
[ 0.408750] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[ 0.408791] msgmni has been set to 233
[ 0.409561] io scheduler noop registered
[ 0.409587] io scheduler deadline registered (default)
[ 0.410872] Serial: 8250/16550 driver, 16 ports, IRQ sharing enabled
[ 0.415910] console [ttyS0] disabled
[ 0.415994] 44200000.uart: ttyS0 at MMIO 0x44200000 (irq = 55, base_baud = 390625) is a 16550A
[ 0.874672] console [ttyS0] enabled
[ 0.880512] nand: Could not find valid ONFI parameter page; aborting
[ 0.886876] nand: device found, Manufacturer ID: 0xad, Chip ID: 0xf1
[ 0.893219] nand: Hynix NAND 128MiB 3,3V 8-bit
[ 0.897640] nand: 128MiB, SLC, page size: 2048, OOB size: 64
[ 0.903293] Scanning device for bad blocks
[ 0.988403] 2 ofpart partitions found on MTD device 41000000.nand
[ 0.994508] Creating 2 MTD partitions on "41000000.nand":
[ 0.999882] 0x000000000000-0x000000e00000 : "boot"
[ 1.006005] 0x000000e00000-0x000008000000 : "ubi"
[ 1.012984] stmmaceth 40400000.ethernet: no reset control found
[ 1.018892] stmmac - user ID: 0x12, Synopsys ID: 0x35
[ 1.023966] Ring mode enabled
[ 1.027000] DMA HW capability register supported
[ 1.031528] Enhanced/Alternate descriptors
[ 1.035855] Enabled extended descriptors
[ 1.039833] RX Checksum Offload Engine supported (type 2)
[ 1.045324] TX Checksum insertion supported
[ 1.049566] Wake-Up On Lan supported
[ 1.053224] Enable RX Mitigation via HW Watchdog Timer
[ 1.061928] libphy: stmmac: probed
[ 1.065336] eth0: PHY ID 001cc914 at 0 IRQ POLL (stmmac-0:00) active
[ 1.071708] eth0: PHY ID 001cc914 at 3 IRQ POLL (stmmac-0:03)
[ 1.078100] TCP: cubic registered
[ 1.081461] NET: Registered protocol family 17
[ 1.085982] bridge: automatic filtering via arp/ip/ip6tables has been deprecated. Update your scripts to load br_netfilter if you need this.
[ 1.099566] Bridge firewalling registered
[ 1.103610] 8021q: 802.1Q VLAN Support v1.8
[ 1.110200] UBI: auto-attach mtd1
[ 1.113523] UBI: attaching mtd1 to ubi0
[ 1.262740] UBI: scanning is finished
[ 1.274176] UBI warning: print_rsvd_warning: cannot reserve enough PEBs for bad PEB handling, reserved 9, need 20
[ 1.285376] UBI: attached mtd1 (name "ubi", size 114 MiB) to ubi0
[ 1.291486] UBI: PEB size: 131072 bytes (128 KiB), LEB size: 129024 bytes
[ 1.298237] UBI: min./max. I/O unit sizes: 2048/2048, sub-page size 512
[ 1.304847] UBI: VID header offset: 512 (aligned 512), data offset: 2048
[ 1.311531] UBI: good PEBs: 912, bad PEBs: 0, corrupted PEBs: 0
[ 1.317419] UBI: user volume: 1, internal volumes: 1, max. volumes count: 128
[ 1.324531] UBI: max/mean erase counter: 2/0, WL threshold: 4096, image sequence number: 0
[ 1.332766] UBI: available PEBs: 0, total reserved PEBs: 912, PEBs reserved for bad PEB handling: 9
[ 1.341916] drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
[ 1.343503] UBI: background thread "ubi_bgt0d" started, PID 275
[ 1.362337] Freeing unused kernel memory: 5728K (c041a000 - c09b2000)
[ 1.383144] init: Console is alive
[ 1.395893] Button Hotplug driver version 0.4.1
[ 1.402165] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[ 1.409546] ehci-platform: EHCI generic platform driver
[ 1.670371] scsi host0: sata_oxnas
[ 1.723650] ata1: SATA max UDMA/133 irq 50
[ 1.727836] sata_oxnas: resetting SATA core
[ 2.090099] ata1: SATA link down (SStatus 0 SControl 300)
[ 2.096632] oxnas-ehci 40200100.ehci: EHCI Host Controller
[ 2.102210] oxnas-ehci 40200100.ehci: new USB bus registered, assigned bus number 1
[ 2.109969] oxnas-ehci 40200100.ehci: irq 39, io mem 0x40200100
[ 2.130035] oxnas-ehci 40200100.ehci: USB 2.0 started, EHCI 1.00
[ 2.137108] hub 1-0:1.0: USB hub found
[ 2.140956] hub 1-0:1.0: 2 ports detected
[ 2.400235] init: - preinit -
sh: write error: Invalid argument
[ 2.463726] usb 1-1: new high-speed USB device number 2 using oxnas-ehci
[ 2.469148] random: mktemp urandom read with 0 bits of entropy available
Press the [f] key and hit [enter] to enter failsafe mode
Press the [1], [2], [3] or [4] key and hit [enter] to select the debug level
[ 2.627276] hub 1-1:1.0: USB hub found
[ 2.631426] hub 1-1:1.0: 4 ports detected
[ 2.910420] usb 1-1.3: new high-speed USB device number 3 using oxnas-ehci
sh: write error: Invalid argument
[ 5.584839] procd: - early -
[ 6.214205] procd: - ubus -
[ 7.241200] procd: - init -
Please press Enter to activate this console.
[ 7.721116] device-mapper: ioctl: 4.28.0-ioctl (2014-09-17) initialised: dm-devel@redhat.com
[ 10.180899] eth0: device MAC
[ 10.189596] device eth0 entered promiscuous mode
[ 10.203084] br-lan: port 1(eth0) entered forwarding state
[ 10.208591] br-lan: port 1(eth0) entered forwarding state
[ 12.183651] stmmaceth 40400000.ethernet eth0: Link is Up - 1Gbps/Full - flow control rx/tx
[ 12.203476] br-lan: port 1(eth0) entered forwarding state
BusyBox v1.22.1 (2015-03-28 16:09:33 CET) built-in shell (ash)
Enter 'help' for a list of built-in commands.
_______ ________ __
| |.-----.-----.-----.| | | |.----.| |_
| - || _ | -__| || | | || _|| _|
|_______|| __|_____|__|__||________||__| |____|
|__| W I R E L E S S F R E E D O M
-----------------------------------------------------
CHAOS CALMER (Bleeding Edge, r45073)
-----------------------------------------------------
* 1 1/2 oz Gin Shake with a glassful
* 1/4 oz Triple Sec of broken ice and pour
* 3/4 oz Lime Juice unstrained into a goblet.
* 1 1/2 oz Orange Juice
* 1 tsp. Grenadine Syrup
-----------------------------------------------------
root@OpenWrt:/# passwd
Changing password for root
New password:
Bad password: too short
Retype password:
Password for root changed by root
root@OpenWrt:/# vi /etc/config/network
root@OpenWrt:/# vi /etc/config/network
root@OpenWrt:/# /etc/init.d/network reload
[ 143.896002] br-lan: port 1(eth0) entered disabled state
[ 143.902791] device eth0 left promiscuous mode
[ 143.907205] br-lan: port 1(eth0) entered disabled state
root@OpenWrt:/# [ 148.953681] stmmaceth 40400000.ethernet eth0: Link is Up - 1Gbps/Full - flow control rx/tx
[ 178.557432] random: nonblocking pool is initialized
[ 1956.314273] reboot: System halted
Edited 1 time(s). Last edit at 04/01/2015 05:55PM by LeggoMyEggo.
|
Re: OpenWRT on Pogoplug Pro / V3 - Need Help Making U-boot Work April 01, 2015 07:25PM |
Admin Registered: 13 years ago Posts: 18,997 |
LeggoMyEggo,
I see where you would have problem booting from the tld-5 u-boot .
This OpenWRT image is FIT image, not legacy image (i.e. uImage). Therefore the name is: openwrt-oxnas-pogoplug-pro-fit-uImage-initramfs.itb. And according to your boot log, it does not contain an initrd. But it does contain the DTB file. And the boot address is 0x62000000.
So the correct way to boot using tld-5 is to find the uImage and DTB for OpenWrt, and then boot with uImage method.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
I see where you would have problem booting from the tld-5 u-boot .
This OpenWRT image is FIT image, not legacy image (i.e. uImage). Therefore the name is: openwrt-oxnas-pogoplug-pro-fit-uImage-initramfs.itb. And according to your boot log, it does not contain an initrd. But it does contain the DTB file. And the boot address is 0x62000000.
So the correct way to boot using tld-5 is to find the uImage and DTB for OpenWrt, and then boot with uImage method.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: OpenWRT on Pogoplug Pro / V3 - Need Help Making U-boot Work April 01, 2015 09:51PM |
Registered: 9 years ago Posts: 429 |
bodhi Wrote:
-------------------------------------------------------
> LeggoMyEggo,
>
> I see where you would have problem booting from
> the tld-5 u-boot .
>
> This OpenWRT image is FIT image, not legacy image
> (i.e. uImage). Therefore the name is:
> openwrt-oxnas-pogoplug-pro-fit-uImage-initramfs.[b
> ]itb[/b]. And according to your boot log, it does
> not contain an initrd. But it does contain the DTB
> file. And the boot address is 0x62000000.
>
> So the correct way to boot using tld-5 is to find
> the uImage and DTB for OpenWrt, and then boot with
> uImage method.
So based on the names of the files from OpenWRT (below), which file(s) would you use to to do that?
I am thinking I should use openwrt-oxnas-uImage-initramfs based on it's size if I am only gonna boot off of one file. You mention including DTB which is a separate file. If I had to boot two files (uImage + dtb), I would use memory location 0x62000000 for uImage but what is a good guess for memory location for the dtb file?
Edited 1 time(s). Last edit at 04/01/2015 09:55PM by LeggoMyEggo.
-------------------------------------------------------
> LeggoMyEggo,
>
> I see where you would have problem booting from
> the tld-5 u-boot .
>
> This OpenWRT image is FIT image, not legacy image
> (i.e. uImage). Therefore the name is:
> openwrt-oxnas-pogoplug-pro-fit-uImage-initramfs.[b
> ]itb[/b]. And according to your boot log, it does
> not contain an initrd. But it does contain the DTB
> file. And the boot address is 0x62000000.
>
> So the correct way to boot using tld-5 is to find
> the uImage and DTB for OpenWrt, and then boot with
> uImage method.
So based on the names of the files from OpenWRT (below), which file(s) would you use to to do that?
openwrt-oxnas-pogoplug-pro.dtb 01-Apr-2015 21:24 6993 openwrt-oxnas-uImage 01-Apr-2015 21:25 1682760 openwrt-oxnas-uImage-initramfs 01-Apr-2015 21:25 3377656 openwrt-oxnas-zImage 01-Apr-2015 21:24 1682696 openwrt-oxnas-zImage-initramfs 01-Apr-2015 21:25 3377592
I am thinking I should use openwrt-oxnas-uImage-initramfs based on it's size if I am only gonna boot off of one file. You mention including DTB which is a separate file. If I had to boot two files (uImage + dtb), I would use memory location 0x62000000 for uImage but what is a good guess for memory location for the dtb file?
Edited 1 time(s). Last edit at 04/01/2015 09:55PM by LeggoMyEggo.
|
Re: OpenWRT on Pogoplug Pro / V3 - Need Help Making U-boot Work April 01, 2015 10:18PM |
Admin Registered: 13 years ago Posts: 18,997 |
LeggoMyEggo,
You can use the same addresses you are using right now to boot Debian for these images:
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 04/01/2015 10:22PM by bodhi.
You can use the same addresses you are using right now to boot Debian for these images:
openwrt-oxnas-pogoplug-pro.dtb 01-Apr-2015 21:24 6993 openwrt-oxnas-uImage 01-Apr-2015 21:25 1682760 openwrt-oxnas-uImage-initramfs 01-Apr-2015 21:25 3377656
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 04/01/2015 10:22PM by bodhi.
|
Re: OpenWRT on Pogoplug Pro / V3 - Need Help Making U-boot Work April 01, 2015 10:31PM |
Registered: 9 years ago Posts: 429 |
bodhi Wrote:
-------------------------------------------------------
> LeggoMyEggo,
>
> You can use the same addresses you are using right
> now to boot Debian for these images:
>
>
OK, thanks for the advice. I will rename those files to match what the Debian file names are with your u-boot so that I don't have to change the environment. I am using a specially prepared USB flash drive. Hoping for the best :)
-------------------------------------------------------
> LeggoMyEggo,
>
> You can use the same addresses you are using right
> now to boot Debian for these images:
>
>
> openwrt-oxnas-pogoplug-pro.dtb > 01-Apr-2015 21:24 6993 > openwrt-oxnas-uImage > 01-Apr-2015 21:25 1682760 > openwrt-oxnas-uImage-initramfs > 01-Apr-2015 21:25 3377656 >
OK, thanks for the advice. I will rename those files to match what the Debian file names are with your u-boot so that I don't have to change the environment. I am using a specially prepared USB flash drive. Hoping for the best :)
|
Re: OpenWRT on Pogoplug Pro / V3 - Need Help Making U-boot Work April 01, 2015 11:27PM |
Registered: 9 years ago Posts: 429 |
I renamed the openwrt files to the same as the Debian environment expected. Still no go :(
U-Boot SPL 2013.10-tld-4 (Sep 07 2014 - 14:10:12)
Boot device: NAND
Attempting to set PLLA to 850 MHz ...
plla_ctrl0 : 0000020a
plla_ctrl1 : 00330000
plla_ctrl2 : 0065008b
plla_ctrl3 : 000000f1
PLLA Set
U-Boot 2013.10-tld-5 (Mar 07 2015 - 16:50:17) for OXNAS
DRAM: 128 MiB
NAND: 128 MiB
In: serial
Out: serial
Err: serial
Net:
Led: GREEN
mii0
Main Loop
Hit any key to stop autoboot: 0
(Re)start 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
1682760 bytes read in 200 ms (8 MiB/s)
3377656 bytes read in 365 ms (8.8 MiB/s)
7029 bytes read in 247 ms (27.3 KiB/s)
## Booting kernel from Legacy Image at 60500000 ...
Image Name: ARM OpenWrt Linux-3.18.10
Created: 2015-04-01 21:25:19 UTC
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 1682696 Bytes = 1.6 MiB
Load Address: 60008000
Entry Point: 60008000
Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 60e00000 ...
Image Name: ARM OpenWrt Linux-3.18.10
Created: 2015-04-01 21:25:19 UTC
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 3377592 Bytes = 3.2 MiB
Load Address: 60008000
Entry Point: 60008000
Verifying Checksum ... OK
No Linux ARM Ramdisk Image
Led: ORANGE (Failed)
Ramdisk image is corrupt or invalid
stopping USB..
resetting ...
|
Re: OpenWRT on Pogoplug Pro / V3 - Need Help Making U-boot Work April 02, 2015 12:09AM |
Admin Registered: 13 years ago Posts: 18,997 |
LeggoMyEggo,
You can try booting without it, only with uImage and DTB, like their bootlog showed above.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
## Loading init Ramdisk from Legacy Image at 60e00000 ... Image Name: ARM OpenWrt Linux-3.18.10 Created: 2015-04-01 21:25:19 UTC Image Type: ARM Linux Kernel Image (uncompressed)This image not an initramfs image. I'd expect to see the gzip compressed image. Like this image:
## Booting kernel from Legacy Image at 60500000 ... Image Name: Linux-3.18.5-oxnas-tld-1 Created: 2015-02-12 19:53:28 UTC Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 4170000 Bytes = 4 MiB Load Address: 60008000 Entry Point: 60008000 Verifying Checksum ... OK ## Loading init Ramdisk from Legacy Image at 60e00000 ... Image Name: initramfs-3.18.5-oxnas-tld-1 Created: 2015-03-03 4:29:13 UTC Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size: 2201718 Bytes = 2.1 MiB Load Address: 60000000 Entry Point: 60000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 62c00000 Booting using the fdt blob at 0x62c00000 Loading Kernel Image ... OK Loading Ramdisk to 67c0f000, end 67e28876 ... OK Loading Device Tree to 67c0a000, end 67c0eb74 ... OK
You can try booting without it, only with uImage and DTB, like their bootlog showed above.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: OpenWRT on Pogoplug Pro / V3 - Need Help Making U-boot Work April 02, 2015 06:13AM |
Registered: 9 years ago Posts: 429 |
bodhi Wrote:
> You can try booting without it, only with uImage
> and DTB, like their bootlog showed above.
I had the same though and I did actually did try that. But that didn't work either. I am wondering if the DTB file is corrupted or was adapted from another devices DTB and the conversion didn't go right. Here is the project maintainers site (slow to come up BTW):
https://gitorious.org/openwrt-oxnas . As you can see, the oxnas adaptation was originally meant for the Medion/Aldi NAS as is shown on the install guide here: https://gitorious.org/openwrt-oxnas/pages/install
> You can try booting without it, only with uImage
> and DTB, like their bootlog showed above.
I had the same though and I did actually did try that. But that didn't work either. I am wondering if the DTB file is corrupted or was adapted from another devices DTB and the conversion didn't go right. Here is the project maintainers site (slow to come up BTW):
https://gitorious.org/openwrt-oxnas . As you can see, the oxnas adaptation was originally meant for the Medion/Aldi NAS as is shown on the install guide here: https://gitorious.org/openwrt-oxnas/pages/install
|
Re: OpenWRT on Pogoplug Pro / V3 - Need Help Making U-boot Work April 02, 2015 02:08PM |
Registered: 10 years ago Posts: 1,037 |
|
Re: OpenWRT on Pogoplug Pro / V3 - Need Help Making U-boot Work April 02, 2015 02:46PM |
Registered: 9 years ago Posts: 429 |
Gravelrash Wrote:
-------------------------------------------------------
> @Leggo
>
> im probably a bit late to the party with my
> feedback - having read the following posts after
> you instructions - followed your steps above and i
> get the same as you.
Bummer isn't it? I mean with the built-in wifi, albiet replaced with a 300M card for $5 delivered, and with the sata port this would be great router. I am using one with hostapd as an AP and it works fine. And as far as a router goes, it's got plenty of bits so to speak - dual core, 128Mb RAM and Nand, Sata and 4 USB ports. The only detriment is you need a USB ethernet adapter or managed switch to have proper VLAN provided WAN - LAN separation.
I have a feeling this might work on a stock Pogoplug Pro with the CE OS. Perhaps the OpenWRT u-boot and firmware count on and use some of the stock items either in place or copied (or moved). But I don't have a stock Pro unfortunately and I don't know a source and a method to put back the stock OS on a V3/Pro.
Edited 4 time(s). Last edit at 04/02/2015 02:57PM by LeggoMyEggo.
-------------------------------------------------------
> @Leggo
>
> im probably a bit late to the party with my
> feedback - having read the following posts after
> you instructions - followed your steps above and i
> get the same as you.
Bummer isn't it? I mean with the built-in wifi, albiet replaced with a 300M card for $5 delivered, and with the sata port this would be great router. I am using one with hostapd as an AP and it works fine. And as far as a router goes, it's got plenty of bits so to speak - dual core, 128Mb RAM and Nand, Sata and 4 USB ports. The only detriment is you need a USB ethernet adapter or managed switch to have proper VLAN provided WAN - LAN separation.
I have a feeling this might work on a stock Pogoplug Pro with the CE OS. Perhaps the OpenWRT u-boot and firmware count on and use some of the stock items either in place or copied (or moved). But I don't have a stock Pro unfortunately and I don't know a source and a method to put back the stock OS on a V3/Pro.
Edited 4 time(s). Last edit at 04/02/2015 02:57PM by LeggoMyEggo.
|
Re: OpenWRT on Pogoplug Pro / V3 - Need Help Making U-boot Work April 02, 2015 03:22PM |
Admin Registered: 13 years ago Posts: 18,997 |
Leggo & Gravelrash,
You can try the DTB from my release thread, if you think your DTB is not a correct one or corrupted. DTB should be the same regardless of kernel.
Can you interrupt serial console and post the OPenWRT u-boot envs after this:
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
You can try the DTB from my release thread, if you think your DTB is not a correct one or corrupted. DTB should be the same regardless of kernel.
Can you interrupt serial console and post the OPenWRT u-boot envs after this:
OX820> go 64000000 ## Starting application at 0x64000000 ... U-Boot 2014.10 (Mar 28 2015 - 05:38:44) for OXNAS DRAM: 128 MiB NAND: 128 MiB
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: OpenWRT on Pogoplug Pro / V3 - Need Help Making U-boot Work April 02, 2015 04:10PM |
Registered: 9 years ago Posts: 429 |
bodhi Wrote:
-------------------------------------------------------
> Leggo & Gravelrash,
>
> Can you interrupt serial console and post the
> OPenWRT u-boot envs after this:
>
>
You mean do a printenv right after the OpenWRT u-boot goes through it's first cycle? Sure.
> You can try the DTB from my release thread, if you
> think your DTB is not a correct one or corrupted.
> DTB should be the same regardless of kernel.
>
I recall trying that too but it still would not boot the kernel.
You know I went back and studied the posts prior to mine over at OpenWRT and some are kinda sketchy...statements like "it's from another site in another language" and "I am posting this not having tried it myself". Pondering on that is starting to lead me to believe there might be some issues that someone with more Linux skills might have to resolve.
Edited 1 time(s). Last edit at 04/02/2015 04:15PM by LeggoMyEggo.
-------------------------------------------------------
> Leggo & Gravelrash,
>
> Can you interrupt serial console and post the
> OPenWRT u-boot envs after this:
>
>
> OX820> go 64000000 > ## Starting application at 0x64000000 ... > > U-Boot 2014.10 (Mar 28 2015 - 05:38:44) for OXNAS > > DRAM: 128 MiB > NAND: 128 MiB >
You mean do a printenv right after the OpenWRT u-boot goes through it's first cycle? Sure.
> You can try the DTB from my release thread, if you
> think your DTB is not a correct one or corrupted.
> DTB should be the same regardless of kernel.
>
I recall trying that too but it still would not boot the kernel.
You know I went back and studied the posts prior to mine over at OpenWRT and some are kinda sketchy...statements like "it's from another site in another language" and "I am posting this not having tried it myself". Pondering on that is starting to lead me to believe there might be some issues that someone with more Linux skills might have to resolve.
Edited 1 time(s). Last edit at 04/02/2015 04:15PM by LeggoMyEggo.
|
Re: OpenWRT on Pogoplug Pro / V3 - Need Help Making U-boot Work April 02, 2015 04:43PM |
Registered: 10 years ago Posts: 1,037 |
|
Re: OpenWRT on Pogoplug Pro / V3 - Need Help Making U-boot Work April 02, 2015 05:00PM |
Admin Registered: 13 years ago Posts: 18,997 |
LeggoMyEggo,
> You mean do a printenv right after the OpenWRT
> u-boot goes through it's first cycle? Sure.
Yes.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
> You mean do a printenv right after the OpenWRT
> u-boot goes through it's first cycle? Sure.
Yes.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: OpenWRT on Pogoplug Pro / V3 - Need Help Making U-boot Work April 03, 2015 01:20PM |
Registered: 9 years ago Posts: 429 |
I had seen this before at the OpenWRT site but had forgotten about it:
I noticed the reference to the need to chain load u-boot.
All the issues are the same more or less referenced by Arch Linux on why they EOL'ed oxnas support, it was too proprietary which made development harder than it had to be. What a shame.
Also, see the reference to using the original u-boot which I am inferencing to mean the stock one from Cloud Engines. It must be that the OpenWRT u-boot assumes that is still in place. It also confirms bodhi's statement about ubi.
Edited 1 time(s). Last edit at 04/03/2015 01:27PM by LeggoMyEggo.
Known Limitations The OpenWrt oxnas target doesn't support all hardware features of the SoC. vendor's U-Boot doesn't support booting modern kernels chain-load a recent U-Boot which does This additional U-Boot stage uses UBI to load OpenWrt and stores it's environment in UBI In future, it may instead be feasible to replace the stock loader, kwboot-like serial recovery yet needs to be found… PLL and SDRAM setup is board specific and needs to be taken care of if we want that S-ATA core requires host-lock for port transfers S-ATA performance sucks when using both drivers simultanously e.g. for RAID-1 vendor's Linux SDK uses hardware-supported RAID and JBOD, OpenWrt doesn't (yet) reference code: https://github.com/kref/linux-oxnas/blob/reference/sdk/drivers/md/ox820hwraid.c no USB gadget support USB 1.1 isochronous transfers are broken. As a work-around an extra USB 2.0 hub between the oxnas box and USB 1.x devices making use of isochronous transfers (e.g. USB audio interfaces) can be used. Crypto engine undocumented/unsupported in all known GPL drops, no support in OpenWrt LEON microcode loading not yet implemented, thus no watchdog and wake-on-lan reference code: https://github.com/kref/linux-oxnas/blob/reference/sdk/arch/arm/plat-oxnas/leon.c The GPL tarball WD-GPL-v1.18 of the Western Digital "My Book World Edition II (blue rings)" contains toolchain and sources of some LEON programs meant to be used with older oxnas SoCs. Besides the addresses, this looks very much the same as on newer SoCs.
I noticed the reference to the need to chain load u-boot.
All the issues are the same more or less referenced by Arch Linux on why they EOL'ed oxnas support, it was too proprietary which made development harder than it had to be. What a shame.
Also, see the reference to using the original u-boot which I am inferencing to mean the stock one from Cloud Engines. It must be that the OpenWRT u-boot assumes that is still in place. It also confirms bodhi's statement about ubi.
Edited 1 time(s). Last edit at 04/03/2015 01:27PM by LeggoMyEggo.
|
Re: OpenWRT on Pogoplug Pro / V3 - Need Help Making U-boot Work April 03, 2015 04:17PM |
Admin Registered: 13 years ago Posts: 18,997 |
LeggoMyEggo,
> Also, see the reference to using the original
> u-boot which I am inferencing to mean the stock
> one from Cloud Engines. It must be that the
> OpenWRT u-boot assumes that is still in place. It
> also confirms bodhi's statement about ubi.
That's true. And I recall that the OpenWRT u-boot build and my u-boot build came from the same code (kref's GitHub), but not abosolutely sure about this. I don't think there is much difference between these 2 versions. The real differences are in the envs used to boot different kernels from different devices (NAND vs external storage).
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
> Also, see the reference to using the original
> u-boot which I am inferencing to mean the stock
> one from Cloud Engines. It must be that the
> OpenWRT u-boot assumes that is still in place. It
> also confirms bodhi's statement about ubi.
That's true. And I recall that the OpenWRT u-boot build and my u-boot build came from the same code (kref's GitHub), but not abosolutely sure about this. I don't think there is much difference between these 2 versions. The real differences are in the envs used to boot different kernels from different devices (NAND vs external storage).
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: OpenWRT on Pogoplug Pro / V3 - Need Help Making U-boot Work April 07, 2015 12:48PM |
Registered: 11 years ago Posts: 165 |
@LeggoMyEggo,
I looked into OpenWRT on the Pogoplug Pro (OXNAS) last night and the current instructions is crazy complex.
My thought is that we should be able to boot directly into OpenWRT using only bodhi's uboot, similar to how it's done on the Pogoplug V4 - http://blog.qnology.com/2015/02/openwrt-on-pogoplug-mobile.html.
The issue is there is no prebuilt openwrt oxnas rootfs tarball provided - https://downloads.openwrt.org/snapshots/trunk/oxnas/generic/.
I'm not familar with some of the files provided, but I'm wondering if we can extract the rootfs from one of those files.
I looked into OpenWRT on the Pogoplug Pro (OXNAS) last night and the current instructions is crazy complex.
My thought is that we should be able to boot directly into OpenWRT using only bodhi's uboot, similar to how it's done on the Pogoplug V4 - http://blog.qnology.com/2015/02/openwrt-on-pogoplug-mobile.html.
The issue is there is no prebuilt openwrt oxnas rootfs tarball provided - https://downloads.openwrt.org/snapshots/trunk/oxnas/generic/.
I'm not familar with some of the files provided, but I'm wondering if we can extract the rootfs from one of those files.
|
Re: OpenWRT on Pogoplug Pro / V3 - Need Help Making U-boot Work April 07, 2015 03:00PM |
Registered: 9 years ago Posts: 429 |
grayman4hire Wrote:
-------------------------------------------------------
> I'm not familar with some of the files provided,
> but I'm wondering if we can extract the rootfs
> from one of those files.
I still think someone needs to load it following the OpenWRT OP's instructions on a stock, fresh out of the box PP. If it successfully loads, then we will know at least that the kernel works. Otherwise there is no telling what the issue is, i.e. is it u-boot, trying to boot from nand vs. memory vs. external disk, etc. I see one other issue which may preclude putting rootfs on disk, that when you go to upgrade the "firmware" in OpenWRT, which is a .bin file, it (I think) default saves it to nand. I don't know what happens if you boot off of and have your rootfs on a disk and go to upgrade the "firmware". I wish I knew more about OpenWRT.
Edited 1 time(s). Last edit at 04/07/2015 03:02PM by LeggoMyEggo.
-------------------------------------------------------
> I'm not familar with some of the files provided,
> but I'm wondering if we can extract the rootfs
> from one of those files.
I still think someone needs to load it following the OpenWRT OP's instructions on a stock, fresh out of the box PP. If it successfully loads, then we will know at least that the kernel works. Otherwise there is no telling what the issue is, i.e. is it u-boot, trying to boot from nand vs. memory vs. external disk, etc. I see one other issue which may preclude putting rootfs on disk, that when you go to upgrade the "firmware" in OpenWRT, which is a .bin file, it (I think) default saves it to nand. I don't know what happens if you boot off of and have your rootfs on a disk and go to upgrade the "firmware". I wish I knew more about OpenWRT.
Edited 1 time(s). Last edit at 04/07/2015 03:02PM by LeggoMyEggo.
|
Re: OpenWRT on Pogoplug Pro / V3 - Need Help Making U-boot Work April 07, 2015 04:08PM |
Registered: 11 years ago Posts: 1,303 |
grayman4hire Wrote:
-------------------------------------------------------
> @LeggoMyEggo,
>
> I looked into OpenWRT on the Pogoplug Pro (OXNAS)
> last night and the current instructions is crazy
> complex.
>
> My thought is that we should be able to boot
> directly into OpenWRT using only bodhi's uboot,
> similar to how it's done on the Pogoplug V4 -
> http://blog.qnology.com/2015/02/openwrt-on-pogoplu
> g-mobile.html.
>
I just received my new PogoPlug P02 shipped from Adorama. I certainly would like it to boot (a selft-built) OpenWRT. TBH, I have no idea which 3rd party u-boot to use. Since you mentioned Bodhi's u-boot, I certainly don't mind to flash my PogoPlug P02 with Bodhi's u-boot. So, where can I download Bodhi's u-boot for a PogoPlug P02 along with its instruction? I don't know the stock u-boot has a support for UART to test Bodhi's and/or any 3rd party u-boot. Can anyone confirm this?
> The issue is there is no prebuilt openwrt oxnas
> rootfs tarball provided -
> https://downloads.openwrt.org/snapshots/trunk/oxna
> s/generic/.
>
I am going to try to build this to include FreeSWITCH and probably also FusionPBX. This will probably take me a day or two. Right now, my computer is building OpenWRT for Kirkwood platform and it keeps crashing in the middle of builds. So, I have to disable parallel mode and the compilation will be very slow. Anyway, when I finish building OpenWRT for my PogoPlug P02, I will try to upload it to 4share for anyone to download.
-------------------------------------------------------
> @LeggoMyEggo,
>
> I looked into OpenWRT on the Pogoplug Pro (OXNAS)
> last night and the current instructions is crazy
> complex.
>
> My thought is that we should be able to boot
> directly into OpenWRT using only bodhi's uboot,
> similar to how it's done on the Pogoplug V4 -
> http://blog.qnology.com/2015/02/openwrt-on-pogoplu
> g-mobile.html.
>
I just received my new PogoPlug P02 shipped from Adorama. I certainly would like it to boot (a selft-built) OpenWRT. TBH, I have no idea which 3rd party u-boot to use. Since you mentioned Bodhi's u-boot, I certainly don't mind to flash my PogoPlug P02 with Bodhi's u-boot. So, where can I download Bodhi's u-boot for a PogoPlug P02 along with its instruction? I don't know the stock u-boot has a support for UART to test Bodhi's and/or any 3rd party u-boot. Can anyone confirm this?
> The issue is there is no prebuilt openwrt oxnas
> rootfs tarball provided -
> https://downloads.openwrt.org/snapshots/trunk/oxna
> s/generic/.
>
I am going to try to build this to include FreeSWITCH and probably also FusionPBX. This will probably take me a day or two. Right now, my computer is building OpenWRT for Kirkwood platform and it keeps crashing in the middle of builds. So, I have to disable parallel mode and the compilation will be very slow. Anyway, when I finish building OpenWRT for my PogoPlug P02, I will try to upload it to 4share for anyone to download.
