3 replies to this topic

[charliebrown]

Hi,

 

I have replaced the nand in my machine (due to too many bad blocks) and have compiled a custom spin of OpenPLI so that I can recover my box.

 

According to this spansion document, it should be a drop in replacement

 

http://www.spansion....34ML01G1_AN.pdf

 

Its not a drop in replacement and I had to tweak the buildscript (why????), I am able to build a fully working image by tweaking the vu inc file  (conf/machine/include/vuxxo.inc) like so

 

#MKUBIFS_ARGS = "-m 2048 -e 126976 -c 4096 -F"

#UBINIZE_ARGS = "-m 2048 -p 128KiB"

 

MKUBIFS_ARGS = "-m 2048 -e 520192 -c 228 "

UBINIZE_ARGS = "-m 2048 -p 512KiB -s 2048 "

 

I've manged to dump the following from the box with some luck and am creating the new images based on this info

 

mtdinfo

 

mtd0

Name:                           rootfs

Type:                           nand

Eraseblock size:                524288 bytes, 512.0 KiB

Amount of eraseblocks:          228 (119537664 bytes, 114.0 MiB)

Minimum input/output unit size: 2048 bytes

Sub-page size:                  2048 bytes

OOB size:                       64 bytes

Character device major/minor:   90:0

Bad blocks are allowed:         true

Device is writable:             true

Default UBI VID header offset:  2048

Default UBI data offset:        4096

Default UBI LEB size:           520192 bytes, 508.0 KiB

Maximum UBI volumes count:      128

 

 

root@vuuno:/sys/devices/virtual/mtd/mtd0# ubinfo -a

UBI version:                    1

Count of UBI devices:           1

UBI control device major/minor: 10:59

Present UBI devices:            ubi0

 

ubi0

Volumes count:                           1

Logical eraseblock size:                 520192 bytes, 508.0 KiB

Total amount of logical eraseblocks:     228 (118603776 bytes, 113.1 MiB)

Amount of available logical eraseblocks: 0 (0 bytes)

Maximum count of volumes                 128

Count of bad physical eraseblocks:       0

Count of reserved physical eraseblocks:  5

Current maximum erase counter value:     3

Minimum input/output unit size:          2048 bytes

Character device major/minor:            253:0

Present volumes:                         0

 

Volume ID:   0 (on ubi0)

Type:        dynamic

Alignment:   1

Size:        219 LEBs (113922048 bytes, 108.6 MiB)

State:       OK

Name:        rootfs

Character device major/minor: 253:1

 

 

The default values dont work for me, even though this replacement nand SHOULD have been a drop in replacement for the old nand (which is EOL). What I'm finding is the image compiles fine, mkubfs makes the image. The machine FULLY boots, but after booting up the nand is corrupted by some process (the nand resize perhaps?). I dont know how to proceed from here

 

brcmnand_handle_false_read_ecc_unc_errors: Uncorrectable error at offset 3bee000

 

 

I've attached a full log of the boot captured from the serial port and would REALLY appreciate it if someone who understands nand layout can tell me what's wrong. There are two logs, one that shows me flashing (without issue) and one of the boot showing the machine boots and then something bombs out and corrupts the nand. I have to flash with USB again to recover to allow box to boot

 

 

 

Attached Files

•  flash.log   3.34KB   1 downloads
•  boot_after_flash.log   64.35KB   1 downloads

[charliebrown]

I think I cant edit the post (time limit?). I got the new chips factory fresh and programmed the CFE using BroadCom Studio3.

 

Once the CFE is programmed I use the front USB to program the box, although I've tried older NFI images, they all failed to boot. All except 2 REALLY old images, one was a custom Blackhole 1.6 and another was a vu nfi image from vu themselves. Both of these old images boot and function fine with no nand corruption, BUT they dont seem to work with the DVB card or I would use them.

 

In the past I've found that old images are hit and miss and when the box worked sticking to new images allowed me to always use the box, must be old drivers.

[MiLo]

Maybe the "-F" option, you've removed it from the ubi params. I think it was related to the flashing by the bootloader.

[charliebrown]

Maybe the "-F" option, you've removed it from the ubi params. I think it was related to the flashing by the bootloader.

 

I'm pretty sure I tried it with that and it didn't help. I'll add now and reflash and report back.

 

I just checked the config, looks like I added it back but it was AFTER i captured that log. It didn't help, it was late and I was tired so I didn't recapture the log but it didn't help

 

This is how it looks right now (i.e. with the F)

 

MKUBIFS_ARGS = "-m 2048 -e 520192 -c 228 -F"

UBINIZE_ARGS = "-m 2048 -p 512KiB -s 2048 "

Edited by charliebrown, 9 September 2015 - 14:59.