Help installing 2015.10 U-Boot for Pogoplug V3 (OXNAS OX820)

Sorry to keep bothering , but when i run :
/tmp # ./fw_printenv > current_envs.txt
Cannot read bad block mark: Invalid argument
i must be doing something wrong , but i have no idea.

any clues?
best regards
Martin



Edited 1 time(s). Last edit at 07/21/2018 05:04PM by bodhi.

hi i have a pogoplug pro, and i am trying to install a new uboot (has the stock one).
when in the process i do this :
/tmp # cat /proc/mtd
dev: size erasesize name
mtd0: 08000000 00020000 "NAND 128MiB 3,3V 8-bit"
mtd1: 00e00000 00020000 "boot"
mtd2: 07200000 00020000 "rootfs"

appears mtd0,mtd1 and mtd2 , i only expected two mtd's .
is this normal?



Edited 1 time(s). Last edit at 07/21/2018 05:05PM by bodhi.

Martin Etcheverry,

> /tmp # cat /proc/mtd
> dev: size erasesize name
> mtd0: 08000000 00020000 "NAND 128MiB 3,3V 8-bit"
> mtd1: 00e00000 00020000 "boot"
> mtd2: 07200000 00020000 "rootfs"
>
> appears mtd0,mtd1 and mtd2 , i only expected two
> mtd's .
> is this normal?

It is normal, since stocks defines mtd0 is the entire NAND, mtd and mtd2 are inside mtd0 (like overlay).

However, when you install new u-boot, you need to look at the instruction and adjust the mtd numbers. You are basically deal with mtd1 only (while the instruction specifying mtd0).

If in doubt, post your commands you are about to run here first so I can verify them for you.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Martin,

Quote

Sorry to keep bothering , but when i run :
/tmp # ./fw_printenv > current_envs.txt
Cannot read bad block mark: Invalid argument
i must be doing something wrong , but i have no idea.

any clues?
best regards
Martin

Did you flash u-boot image and u-boot envs image?

If you did, please post the log of the session (copy/paste whats in your terminal) from the beggining when you start the installation, until this error.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)



Edited 1 time(s). Last edit at 07/21/2018 05:11PM by bodhi.

no i didn't flash anything.

the only thing that i did diferent is decomplres the files :
linux-tools-installation-bodhi.tar.gz and
uboot.2015.10-tld-2.ox820.bodhi.tar

in my linux machine and copy to /tmp via scp to the pogoplug
i did this via serial:

/ # /etc/init.d/dropbear.sh start
Starting dropbear:           Success

and i did this via ssh:

/ # cd /tmp
/tmp # ls
hbplug.log   resolv.conf  var
/tmp # ls
busybox                                    hbplug.log                                 uboot.2013.10-tld-5.ox820.environment.img  uboot.spl.2013.10.ox820.850mhz.mtd0.img
e2fsck                                     nanddump                                   uboot.2015.10-tld-1.ox820.mtd0.img         var
flash_erase                                nandwrite                                  uboot.2015.10-tld-2.ox820.environment
fw_env.config                              resolv.conf                                uboot.2015.10-tld-2.ox820.environment.img
fw_printenv                                uboot.2013.10-tld-5.ox820.environment      uboot.2015.10-tld-2.ox820.mtd0.img
/tmp # cat /etc/fw_env.config 
# Configuration file for fw_(printenv/saveenv) utility.
# Up to two entries are valid, in this case the redundant
# environment sector is assumed present.
# Notice, that the "Number of sectors" is ignored on NOR.

# MTD device name	Device offset	Env. size	Flash sector size	Number of sectors
/dev/mtd0		0xc001000000		0x20000		0x20000
/tmp # cat /proc/mtd
dev:    size   erasesize  name
mtd0: 08000000 00020000 "NAND 128MiB 3,3V 8-bit"
mtd1: 00e00000 00020000 "boot"
mtd2: 07200000 00020000 "rootfs"
/tmp # nanddump --noecc --omitoob -f mtd0  /dev/mtd0
-sh: nanddump: not found
/tmp # ./nanddump --noecc --omitoob -f mtd0  /dev/mtd0
Block size 131072, page size 2048, OOB size 64
Dumping data starting at 0x00000000 and ending at 0x08000000...
/tmp # dmesg | grep -i 'bad'
<6>[    5.240000] Scanning device for bad blocks
<5>[    5.790000] UBI: number of bad PEBs:         0
<5>[    5.820000] UBI: number of PEBs reserved for bad PEB handling: 9
/tmp # blparam >  current_envs.txt
-sh: blparam: not found
/tmp # ./fw_printenv > current_envs.txt
Cannot read bad block mark: Invalid argument
/tmp # ./fw_printenv                   
Cannot read bad block mark: Invalid argument

----
Mod edit: please use formatted code to post log.



Edited 1 time(s). Last edit at 07/21/2018 10:45PM by bodhi.

Martin,

> no i didn't flash anything.

Then blparam is the correct command to use.

> /tmp # blparam > current_envs.txt
> -sh: blparam: not found

> /tmp # ./fw_printenv > current_envs.txt
> Cannot read bad block mark: Invalid argument
> /tmp # ./fw_printenv
> Cannot read bad block mark: Invalid argument
> [/code]

The above erorrs are expected.

Look for blparam in stock rootfs and use it. Somewhere in cloudengines folder, iirc:

/usr/local/cloudengines/bin/

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Ok , good news i could install the new version of u-boot
this is my boot now:
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 2015.10-tld-2 (Oct 21 2017 - 22:00:02 -0700)
OXNAS OX820

DRAM: 128 MiB
NAND: 128 MiB
In: serial
Out: serial
Err: serial
Net: dwmac.40400000
Hit any key to stop autoboot: 0
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

Reset IDE: SATA PHY not ready for device 0
ide_preinit failed

Partition Map for USB device 0 -- Partition Type: DOS

Part Start Sector Num Sectors UUID Type
1 63 30202137 00000000-01 83 Boot
2 30202200 64260 00000000-02 82
loading envs from usb 0 ...
** File not found /boot/uEnv.txt **

no IDE devices available
running scan_disk ...
Scan device usb
device usb 0:1
** File not found /boot/uImage **
device usb 1:1
** Bad device usb 1 **
device usb 2:1
** Bad device usb 2 **
device usb 3:1
** Bad device usb 3 **
Scan device ide

Reset IDE: SATA PHY not ready for device 0
ide_preinit failed
device ide 0:1
** Bad device size - ide 0 **
device ide 1:1
** Bad device ide 1 **
device ide 2:1
** Bad device ide 2 **
device ide 3:1
** Bad device ide 3 **
loading uImage ...
** File not found /boot/uImage **
loading uInitrd ...
** File not found /boot/uInitrd **
loading DTB /boot/dts/ox820-pogoplug-pro.dtb ...
** File not found /boot/dts/ox820-pogoplug-pro.dtb **
Wrong Image Format for bootm command
ERROR: can't get kernel image!
resetting ...


I think , i make some mistake creating the usb pendrive with debian (Debian-3.17.0-oxnas-tld-1-rootfs-bodhi.tar.bz2) i will keep trying
Thank you for the support and the patience.

Martin,

> 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 2015.10-tld-2 (Oct 21 2017 - 22:00:02
> -0700)
> OXNAS OX820
>

Cool!



> ** File not found /boot/uImage **
> loading uInitrd ...
> ** File not found /boot/uInitrd **
> loading DTB /boot/dts/ox820-pogoplug-pro.dtb ...
> ** File not found /boot/dts/ox820-pogoplug-pro.dtb
> **
> Wrong Image Format for bootm command
> ERROR: can't get kernel image!
> resetting ...
>
>
> I think , i make some mistake creating the usb
> pendrive with debian
> (Debian-3.17.0-oxnas-tld-1-rootfs-bodhi.tar.bz2) i

Looks like it is indeed the problem.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Hey Bodhi , thanks for the help! i cant't buy you a beer (but you deserve it!) so i made a contribution to msf! thank yo to help me to have fun !! and also thanks for make me be aware of that noble cause! best regards Martin

Awesome! Thanks Martin.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)