Welcome! Log In Create A New Profile

Advanced

Oxnas Box bricked?

Posted by dietgert 
Forum List Message List New Topic
dietgert
Oxnas Box bricked?
July 25, 2017 04:23PM
Hello,

my STG212-Box became rather hot with 850Mhz SPL-Uboot.
So i tried a "downgrade" to 700Mhz , flashing uboot.spl.2013.10.ox820.mtd0.img.
After a reboot the system shows the following output: 

U-Boot SPL 2013.10 (Apr 27 2014 - 19:08:27)
  Boot device: NAND
Attempting to set PLLA to 800 MHz ...
  plla_ctrl0 : 0000030a
  plla_ctrl1 : 00400000
  plla_ctrl2 : 007f0068
  plla_ctrl3 : 00000193

PLLA Set

Then nothing happens.

The first question is: has the spl stage finished succesfully - or is this a problem of the SPL stage itself?

BR
dietgert
Reply Quote
bodhi
Re: Oxnas Box bricked?
July 25, 2017 05:01PM
dietgert,

> U-Boot SPL 2013.10 (Apr 27 2014 - 19:08:27)

Looks like it did finish. The next thing should happen is u-boot starts executing.

If you can't get past this to load u-boot, then it's time to use the internal SATA port to rescue it.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Reply Quote
dietgert
Re: Oxnas Box bricked?
March 13, 2018 05:16PM
Well, a little bit time again...

Internal sata is able to load the uboot.
However, it is not possible to write the images/environment as described in the thread: Unbrick a Pogoplug Pro (v3/OXNAS?) on page 2. However there is also no failure displayed/outputted.

A boot from the hdd is not possible: 

U-Boot SPL 2013.10-g3a0f380-dirty (Jul 26 2014 - 14:31:34)
  Boot device: SATA
Attempting to set PLLA to 850 MHz ...
  plla_ctrl0 : 0000020a
  plla_ctrl1 : 00330000
  plla_ctrl2 : 0065008b
  plla_ctrl3 : 000000f1

PLLA Set
Bus 0: OK 
  Device 0: 
** File not found /boot/bootargs.bin **


U-Boot 2013.10-g3a0f380-dirty (Jul 26 2014 - 10:18:57) for OXNAS

DRAM:  128 MiB
IDE:   Bus 0: OK 
  Device 0: Model: ST1500LM006 HN-M151RAD Firm: 2BC10008 Ser#: S34QJ9FG508340
            Type: Hard Disk
            Supports 48-bit addressing
            Capacity: 1430799.3 MB = 1397.2 GB (-1364690128 x 512)
NAND:  128 MiB
In:    serial
Out:   serial
Err:   serial
Net:   
Led:	GREEN
mii0
Main Loop
Hit any key to stop autoboot:  0 

Reset IDE: Bus 0: OK 
  Device 0: Model: ST1500LM006 HN-M151RAD Firm: 2BC10008 Ser#: S34QJ9FG508340
            Type: Hard Disk
            Supports 48-bit addressing
            Capacity: 1430799.3 MB = 1397.2 GB (-1364690128 x 512)
4628891 bytes read in 732 ms (6 MiB/s)
4594376 bytes read in 686 ms (6.4 MiB/s)
7075 bytes read in 22 ms (313.5 KiB/s)
## Booting kernel from Legacy Image at 60500000 ...
   Image Name:   Linux-4.4.54-oxnas-tld-1
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    4628827 Bytes = 4.4 MiB
   Load Address: 60008000
   Entry Point:  60008000
   Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 60e00000 ...
   Image Name:   initramfs-4.4.54-oxnas-tld-1
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    4594312 Bytes = 4.4 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 679c6000, end 67e27a88 ... OK
   Loading Device Tree to 679c1000, end 679c5ba2 ... OK

Led:	GREEN

Starting kernel ...

Uncompressing Linux... done, booting the kernel.

Then nothing further happens.
Probably some entry is missing: 


OX820 # printenv
autoload=no
baudrate=115200
bootargs=console=ttyS0,115200n8
bootcmd=run dt_bootcmd_ide
bootdelay=3
console=console=ttyS0,115200n8
dt_bootcmd_ide=ide reset; run dt_ide_bootcmd; reset
dt_bootm=bootm $uimage_addr $uinitrd_addr $dtb_addr
dt_ide_boot=run dt_load_uimage; run dt_load_initrd; run dt_load_dtb; run dt_bootm
dt_ide_bootcmd=run ide_set_bootargs; run dt_ide_boot
dt_load_dtb=ext2load ide 0:1 $dtb_addr /boot/dts/ox820-pogoplug-classic.dtb
dt_load_initrd=ext2load ide 0:1 $uinitrd_addr /boot/uInitrd
dt_load_uimage=ext2load ide 0:1 $uimage_addr /boot/uImage
dtb_addr=0x62c00000
ethact=mii0
ethaddr=00:25:31:xx:xx:xx
ide_set_bootargs=setenv bootargs console=ttyS0,115200 root=/dev/sda1 rootdelay=10
ipaddr=192.168.178.101
keypressed=1
mtdids=nand0=41000000.nand
mtdparts=mtdparts=41000000.nand:14m(boot),-(data)
serialcon=echo switch to serial console;setenv stderr serial;setenv stdin serial;setenv stdout serial;echo switch to serial console
serverip=192.168.178.13
stderr=serial
stdin=serial
stdout=serial
uimage_addr=0x60500000
uinitrd_addr=0x60e00000

Environment size: 1117/16380 bytes
OX820 #

Any hint ?

BR
dietgert
Reply Quote
bodhi
Re: Oxnas Box bricked?
March 13, 2018 09:34PM
dietgert,

1. Moun the disk in a diffent Linux box and get some info. Assuming this HDD was mount at /media/sdb1. If there is more than 1 partition on the disk then make sure they are all mounted. 

mount
fdisk -l /dev/sdb


2. At u-boot countdown, 

U-Boot 2013.10-g3a0f380-dirty (Jul 26 2014 - 10:18:57) for OXNAS

DRAM:  128 MiB
IDE:   Bus 0: OK 
  Device 0: Model: ST1500LM006 HN-M151RAD Firm: 2BC10008 Ser#: S34QJ9FG508340
            Type: Hard Disk
            Supports 48-bit addressing
            Capacity: 1430799.3 MB = 1397.2 GB (-1364690128 x 512)
NAND:  128 MiB
In:    serial
Out:   serial
Err:   serial
Net:   
Led:	GREEN
mii0
Main Loop
Hit any key to stop autoboot:  0

Press enter or any key to interrupt u-boot. And 

printenv
boot
And post the entire serial console log here.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Reply Quote
dietgert
Re: Oxnas Box bricked?
March 14, 2018 03:23PM
ok, my fault.
False dtb-file, changed to stg212. made new image in boot directory on mounted linux-box.
Kernel now at least starts a short booting up ...
Failure below is probably still dtb-related . 

U-Boot SPL 2013.10-g3a0f380-dirty (Jul 26 2014 - 14:31:34)
  Boot device: SATA
Attempting to set PLLA to 850 MHz ...
  plla_ctrl0 : 0000020a
  plla_ctrl1 : 00330000
  plla_ctrl2 : 0065008b
  plla_ctrl3 : 000000f1

PLLA Set
Bus 0: OK 
  Device 0: 
** File not found /boot/bootargs.bin **


U-Boot 2013.10-g3a0f380-dirty (Jul 26 2014 - 10:18:57) for OXNAS

DRAM:  128 MiB
IDE:   Bus 0: OK 
  Device 0: Model: ST1500LM006 HN-M151RAD Firm: 2BC10008 Ser#: S34QJ9FG508340
            Type: Hard Disk
            Supports 48-bit addressing
            Capacity: 1430799.3 MB = 1397.2 GB (-1364690128 x 512)
NAND:  128 MiB
In:    serial
Out:   serial
Err:   serial
Net:   
Led:	GREEN
mii0
Main Loop
Hit any key to stop autoboot:  0 
OX820 # 
OX820 # 
OX820 # 
OX820 # printenv
autoload=no
baudrate=115200
bootargs=console=ttyS0,115200n8
bootcmd=run dt_bootcmd_ide
bootdelay=3
console=console=ttyS0,115200n8
dt_bootcmd_ide=ide reset; run dt_ide_bootcmd; reset
dt_bootm=bootm $uimage_addr $uinitrd_addr $dtb_addr
dt_ide_boot=run dt_load_uimage; run dt_load_initrd; run dt_load_dtb; run dt_bootm
dt_ide_bootcmd=run ide_set_bootargs; run dt_ide_boot
dt_load_dtb=ext2load ide 0:1 $dtb_addr /boot/dts/ox820-stg212.dtb
dt_load_initrd=ext2load ide 0:1 $uinitrd_addr /boot/uInitrd
dt_load_uimage=ext2load ide 0:1 $uimage_addr /boot/uImage
dtb_addr=0x62c00000
ethact=mii0
ethaddr=00:25:31:xx:xx:xx
ide_set_bootargs=setenv bootargs console=ttyS0,115200 root=/dev/sda1 rootdelay=10
ipaddr=192.168.0.100
mtdids=nand0=41000000.nand
mtdparts=mtdparts=41000000.nand:14m(boot),-(data)
root=/dev/sda1
rootfstype=ext3
serialcon=echo switch to serial console;setenv stderr serial;setenv stdin serial;setenv stdout serial;echo switch to serial console
stderr=serial
stdin=serial
stdout=serial
uimage_addr=0x60500000
uinitrd_addr=0x60e00000

Environment size: 1099/16380 bytes
OX820 # boot

Reset IDE: Bus 0: OK 
  Device 0: Model: ST1500LM006 HN-M151RAD Firm: 2BC10008 Ser#: S34QJ9FG508340
            Type: Hard Disk
            Supports 48-bit addressing
            Capacity: 1430799.3 MB = 1397.2 GB (-1364690128 x 512)
4629048 bytes read in 748 ms (5.9 MiB/s)
4594376 bytes read in 717 ms (6.1 MiB/s)
7224 bytes read in 14 ms (503.9 KiB/s)
## Booting kernel from Legacy Image at 60500000 ...
   Image Name:   Linux-4.4.54-oxnas-tld-1
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    4628984 Bytes = 4.4 MiB
   Load Address: 60008000
   Entry Point:  60008000
   Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 60e00000 ...
   Image Name:   initramfs-4.4.54-oxnas-tld-1
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    4594312 Bytes = 4.4 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 679c6000, end 67e27a88 ... OK
   Loading Device Tree to 679c1000, end 679c5c37 ... OK

Led:	GREEN

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
[    0.000000] Booting Linux on physical CPU 0x0
[    0.000000] Linux version 4.4.54-oxnas-tld-1 (root@tldDebian) (gcc version 4.9.2 (Debian 4.9.2-10) ) #2 SMP PREEMPT Sat Mar 18 23:09:58 PDT 2017
[    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: MitraStar Technology Corp. STG-212
[    0.000000] bootconsole [earlycon0] enabled
[    0.000000] Memory policy: Data cache writealloc
[    0.000000] Kernel panic - not syncing: ERROR: Failed to allocate 0x2000 bytes below 0x0.
[    0.000000] 
[    0.000000] CPU: 0 PID: 0 Comm: swapper Not tainted 4.4.54-oxnas-tld-1 #2
[    0.000000] Hardware name: PLXTECH NAS782X SoC (Flattened Device Tree)
[    0.000000] [<c0010c6c>] (unwind_backtrace) from [<c000cf8c>] (show_stack+0x10/0x14)
[    0.000000] [<c000cf8c>] (show_stack) from [<c02cf840>] (dump_stack+0x84/0xa0)
[    0.000000] [<c02cf840>] (dump_stack) from [<c0091c78>] (panic+0x8c/0x1ec)
[    0.000000] [<c0091c78>] (panic) from [<c0835b7c>] (memblock_alloc_base+0x34/0x40)
[    0.000000] [<c0835b7c>] (memblock_alloc_base) from [<c082cf44>] (early_alloc_aligned+0xc/0x2c)
[    0.000000] [<c082cf44>] (early_alloc_aligned) from [<c082dfe0>] (paging_init+0x764/0xa1c)
[    0.000000] [<c082dfe0>] (paging_init) from [<c082ae54>] (setup_arch+0x508/0x8f8)
[    0.000000] [<c082ae54>] (setup_arch) from [<c0828940>] (start_kernel+0x80/0x3ac)
[    0.000000] [<c0828940>] (start_kernel) from [<60008074>] (0x60008074)
[    0.000000] ---[ end Kernel panic - not syncing: ERROR: Failed to allocate 0x2000 bytes below 0x0.
[    0.000000]

BR
dietgert



Edited 2 time(s). Last edit at 03/14/2018 03:27PM by dietgert.
Reply Quote
bodhi
Re: Oxnas Box bricked?
March 15, 2018 03:10PM
dietgert,

I am not familiar with this u-boot version. Were it built by you? or where did you download it from?

> U-Boot SPL 2013.10-g3a0f380-dirty (Jul 26 2014 -
> 14:31:34)
> U-Boot 2013.10-g3a0f380-dirty (Jul 26 2014 -
> 10:18:57) for OXNAS

But looks like the cause is right here

> ** File not found /boot/bootargs.bin **

> [ 0.000000] Kernel panic - not syncing: ERROR:
> Failed to allocate 0x2000 bytes below 0x0.

Most likely it means that this u-boot does not tell the kernel about the menory, it is your bootargs that specified the memory region for this box. And it is missing.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Reply Quote
dietgert
Re: Oxnas Box bricked?
March 16, 2018 07:41PM
Hello Bodhi,

was downloaded by a link in your forum.
Also a second (even older) uboot - made by warhead from arch linux arm - was included.
With both of them - and a 3rd one linked in your forum - there was no success.
Tried with all of them a flashing via tftp.
Warheads uboot at least generated failures during the erase/write process.
The other 2 never gave back any failure message.
Found "Schnee"s file-system package, many nand errors during the first boot, not so many
after upgrading to 4.1 kernel. Many thanks to "Schnee" from here !
Then the flashing as provided by your uboot-oxnas 2015.10 thread went through without problems.
System is now up again.
So this brings me back to the original point: which spl-file could be safely used for operation
below 850Mhz frequency ?

BR

dietgert
Reply Quote
bodhi
Re: Oxnas Box bricked?
March 17, 2018 04:08AM
dietgert,

> System is now up again.
> So this brings me back to the original point:
> which spl-file could be safely used for operation
>
> below 850Mhz frequency ?
>

This SPL is below 850 Mhz:

Quote
https://forum.doozan.com/read.php?3,16017,16017#msg-16017

Updated 16 May 2014

I've uploaded the 2013.10 u-Boot image for Pogoplug V3 Oxnas

......

Download U-Boot image at Dropbox:

uboot.2013.10-tld-3.ox820.bodhi.tar
md5
c916498ff7396cc81c9c9aa0a2d714d3

This archive contains the following 3 files:

uboot.spl.2013.10.ox820.mtd0.img
uboot.2013.10-tld-3.ox820.mtd0.img
pogopro_uboot_env.img

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Reply Quote
dietgert
Re: Oxnas Box bricked?
March 18, 2018 02:37PM
Hmm,

with the additional use of the uboot-file: uboot.2013.10-tld-3.ox820.mtd0.img the system works.
The splfile: uboot.spl.2013.10.ox820.mtd0.img with an actual uboot.2015.10-tld-2.ox820.mtd0.img
did not work. Brought the same behaviour as in the first post.
So i think the (actual) uboot is not independent from the spl-stage.
Brought back uboot.spl.2013.10.ox820.850mhz.mtd0.img - and the system is working again.

BR

dietgert



Edited 1 time(s). Last edit at 03/18/2018 03:50PM by dietgert.
Reply Quote
bodhi
Re: Oxnas Box bricked?
March 18, 2018 04:14PM
dietgert,

I recall testing the new u-boot with older SPL and it was fine.


Quote

Updated 22 Nov 2015

I've uploaded the uboot.2015.10-tld-1 u-Boot image for Pogoplug V3 Oxnas.

Warning: netconsole does not start automatically in this version. If you don't have serial console and therefore need netconsole to see the boot progress, please use previous u-boot version (uboot.2013.10-tld-3.ox820.bodhi.tar - Updated 16 May 2014). And follow the instruction in that section.


There are only minor changes in functionality from 2013.10 version. The major change in this version is to modernize and this code base now is back to tracking the mainline branch.

This u-boot supports the following latest U-Boot features (among others):

- Ability to customize u-boot envs in a script (uEnv.txt) during boot, without committing changes to NAND (see section A below for instruction). This feature also can be used for rescue purpose where the u-boot envs were messed up, or when the NAND envs block is bad.
- both FDT and non-FDT kernel booting
- supports EFI/GPT partition > 2TB (SATA and USB) either for booting or just attached.
- boot Ext4 rootfs
- SNTP (Simple NTP to set date time during U-Boot booting)
- bootz (boot with zImage).
- Run the Pogo V3 at 850mhz (for whatever reason, if you wish to run at 700Mhz as previous version did, then use the old u-boot SPL version uboot.spl.2013.10.ox820.mtd0.img
in previous version). U-boot image proper is independent of the SPL, so it can still be updated to uboot.2015.10-tld-1.


But in any case, if the temperature in running 850Mhz causes you problem (or you just try to save energy), please let me know and I will attempt to build new SPL. It is a little bit of a hassle, because I used an older gcc version back in 2013.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Reply Quote
dietgert
Re: Oxnas Box bricked?
March 19, 2018 02:35PM
Hello Bodhi,

no it`s ok now:
I removed the metall-cover over the 3,5" HDD, replaced it with a 2,5" HDD and cut away some plastics on the bottom
of the housing. Temperature is now decent - because much more air circulation is now possible inside the housing.
So i`ll keep the actual uboot.

Thank You.

BR

dietgert
Reply Quote
Newer Topic Older Topic
Author:

Your Email:


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: