Nand replacement

D

duggy

Vu+ Newbie
Unfortunately the nand has gone bad in my GENUINE Uno :(

i know this because of the messages on the RS232 port. "relocation failed" "repartition nand" etc etc

So, given that I have a genuine box and dont really want a clone, can I rescue the box?. If i was to get a new nand chip fitted, would that keep my box genuine? (from the perspective of s/w updates). Is the uniqueness of the box stored on the nand?.

I have the serial number of the box if someone from VU+ needs it to prove my box is no clone, and can take any pictures anyone needs to see etc no issue, if thats req'd for me to get an answer.

Seems silly to spend hundreds on a new box when all i need is a new nand for a few pounds.
 
a911

a911

The BH Lover
duggy said:
Unfortunately the nand has gone bad in my GENUINE Uno :(

i know this because of the messages on the RS232 port. "relocation failed" "repartition nand" etc etc

So, given that I have a genuine box and dont really want a clone, can I rescue the box?. If i was to get a new nand chip fitted, would that keep my box genuine? (from the perspective of s/w updates). Is the uniqueness of the box stored on the nand?.

I have the serial number of the box if someone from VU+ needs it to prove my box is no clone, and can take any pictures anyone needs to see etc no issue, if thats req'd for me to get an answer.

Seems silly to spend hundreds on a new box when all i need is a new nand for a few pounds.
Click to expand...

Contact Vuplus directly for hardware support:-

http://vuplus.com/sub/main.php
 
D

duggy

Vu+ Newbie
I'll fire them off an email but tbh I doubt they'll be interested in helping me. Its an old box (out of production), and they already have the sale. Would be suprised if they would be interested.

I'm trying to understand if replacing the nand will make the box a clone because new flash chips are cheap (around £18 on ebay). However, if I replace the chip and try flashing via serial cable will that work?.

I might have to program with a programming now that i think about it.

perhaps better to abandon this and buy another box?. Such a shame such a cheap part can render the (expensive) device useless :(

Anyone want a used (genuine) UNO that boots part way but cant be flashed (bad blocks) :haha:
 
D

duggy

Vu+ Newbie
right I sent them a message anyway (vu), no harm trying I suppose.. in the meantime can somene tell me if its possible to flash a blank flash ic and if doing so will make my box a clone ?
 
angelofsky1980

angelofsky1980

BlackHole Driver Specialist
duggy said:
right I sent them a message anyway (vu), no harm trying I suppose.. in the meantime can somene tell me if its possible to flash a blank flash ic and if doing so will make my box a clone ?
Click to expand...

You have two possibilities:
1. ask Vu for repair
2. ask official Vu retailer for repair

Ontly these two possibilities give you the truth of not catch a clone issue.
Take a look to the complete mainboard replacement (some German retailers have them on their catalogue).
 
D

duggy

Vu+ Newbie
thanks everyone for your help. I'll look to getting another box. perhaps the Zero as that might be the only choice (that's cheap)
 
D

duggy

Vu+ Newbie
Right I have made progress. I replaced the nand, took ages for parts to arrive and it was a hard job (for me but it's done).

problem is its not working... lol

it looks like I am missing something. I flashed back the dump I made of the nand but as expected that's not working, that image was expected to fail as it went bad part through a flash so image was bad. However the reason I flashed it was to get my cfe which had worked. Also no error about Mac address on boot so that's all good

the issue is that no matter what image I flash I get an error. perhaps my dump (full 128 mb) is missing something? . googling the message seems to imply I need a bootloader but is not that the cfe?. Before I flashed blank if box was dead, I flashed via bbs3 7mb and dumped back and checksum matched my of both so that's fine and proves I can flash.

I've flashed via usb and serial using vu until and it always completes with issue so what gives?

This is how it always stops booting


ight (C) Broadcom Corporation.

writing vfd
New NAND flash at 18000000 offset 00000000 size 116736KB
New NAND flash at 18000000 offset 07200000 size 4096KB
New NAND flash at 18000000 offset 07600000 size 4096KB
New NAND flash at 18000000 offset 07A00000 size 2048KB
New NAND flash at 18000000 offset 07C00000 size 1024KB
New NAND flash at 18000000 offset 07D00000 size 512KB
New NAND flash at 18000000 offset 07D80000 size 512KB
New NAND flash at 18000000 offset 07E00000 size 1024KB
New NAND flash at 18000000 offset 07F00000 size 1024KB

DDR Freq: 396MHz
CPU speed: 405MHz
Memory Config: 64-bit UMA
Device Tech: 1Gb
Total memory: 512MB
Boot Device: NAND
Total flash: 128MB

Initializing USB.
Initialize First USB Controller
USB OHCI start : Power Switching Mode Changed from 2000902 to 2000b02
USB: Locating Class 09 Vendor 0000 Product 0000: USB Hub
Try to Initialize Second USB Controller
Initialize Second USB Controller
USB OHCI start : Power Switching Mode Changed from 2000902 to 2000b02
USB: Locating Class 09 Vendor 0000 Product 0000: USB Hub

CFE initialized.

checking usb
ACK :
writing vfd
Starting splash screen.
nand_erase_block 0x1fb20000 0x20000 doneLoader:elf Filesys:raw Dev:flash0.kernel File: Options:mem=48M mem=256M@0x20000000 rootfstype=jffs2 root=/dev/mtdblock0 rw
Loading: !!!!! UNC read error occurred, while reading from NAND flash
nand_erase_block 0x1f200000 0x20000 doneFailed.
Could not load : I/O error
 
D

duggy

Vu+ Newbie
took almost 2 hours to dump out the contents of the nand but doing
md5sum shows its identical to the one it replaced. very confused I see that error above as I didn't see that with the band nand installed (didn't boot but had different error)


both files are 134217728 bytes

[root@server tocompare]# md5sum *
e17d2748813058ec566744ac97934ba7 new _ nand dumped.bin
e17d2748813058ec566744ac97934ba7 old_nand_dumped.bin
[root@server tocompare]#
 
Last edited:
D

duggy

Vu+ Newbie
I think I found the problem. The chip I was sent is K9F1G08U0E but the original chip was K9F1G08U0D, now its one letter off and you wouldn't think it matters, but it does I think.

Here is an example of where someone tried to use it but it didnt work the same when writing to nand

Code: 
http://e2e.ti.com/support/dsp/davinci_digital_media_processors/f/100/t/347989

What's interesting is that BBS3 was able to program the CFE into the blank chip, so it must have the smarts to deal with the chip, only my "full" dump was corrupt and so my box cant ever work with that image, even though the first 1MB was the CFE and allowed the machine to boot, subsequent flashes via CFE dont work as it doesnt appear to deal with K9F1G08U0E too well. So I can either try and source the right chip somehow, OR try and do a FULL dump from a working machine and program that via BBS3.

Glad to hear your thoughts?
 
Last edited by a moderator:
M

mooo

Vu+ Newbie
interesting thread duggy, my solo is getting dusty in a cupboard with what I think is the same issue as your Uno

please update if you make any progress, I'd be tempted to attempt this also
 
D

duggy

Vu+ Newbie
well replaced the nand with a spansion one thats supposed to be compatible and its not... machine flashes fine but not working I think the CFE is the problem based on log output on serial console.
 
D

duggy

Vu+ Newbie
cant edit the above comment ...


right I have compiled from src openvuplus... same issue when booting. I think I need to tweak ubinize.cfg (currently looks like this)

[user@server tmp]$ cat ./deploy/images/ubinize.cfg
[ubifs]
mode=ubi
image=/tmp/openvuplus/build/vuuno/tmp/deploy/images/vuplus-image-vuuno-20150831154945.rootfs.ubifs
vol_id=0
vol_type=dynamic
vol_name=rootfs
vol_flags=autoresize
[user@server tmp]


This is what happens when I try and boot from this image (i compiled it myself).

(see attachment for full log)

UBI: scanning is finished
UBI error: vtbl_check: too large reserved_pebs 572, good PEBs 228
UBI error: vtbl_check: volume table check failed: record 0, error 9
Volume table record 0 dump:
reserved_pebs 572
alignment 1
data_pad 0
vol_type 1
upd_marker 0
name_len 6
name rootfs
crc 0x7089bf6d
UBI error: ubi_attach_mtd_dev: failed to attach mtd0, error -22
UBI error: ubi_init: cannot attach mtd0
ALSA device list:
No soundcards found.
ata2: SATA link down (SStatus 4 SControl 300)
UBIFS error (pid 1): ubifs_mount: cannot open "ubi0:rootfs", error -19
VFS: Cannot open root device "ubi0:rootfs" or unknown-block(8,1): error -19
Please append a correct "root=" boot option; here are the available partitions:
1f00 116736 mtdblock0 (driver?)
1f01 4096 mtdblock1 (driver?)
1f02 4096 mtdblock2 (driver?)
1f03 2048 mtdblock3 (driver?)
1f04 1024 mtdblock4 (driver?)
1f05 512 mtdblock5 (driver?)
1f06 512 mtdblock6 (driver?)
1f07 1024 mtdblock7 (driver?)
0800 117220824 sda driver: sd
0801 117218268 sda1 00000000-01
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(8,1)
Rebooting in 180 seconds..
 

Attachments

  • latest_vu_fromsrc.txt
    13.2 KB · Views: 12
angelofsky1980

angelofsky1980

BlackHole Driver Specialist
duggy said:
cant edit the above comment ...


right I have compiled from src openvuplus... same issue when booting. I think I need to tweak ubinize.cfg (currently looks like this)

[user@server tmp]$ cat ./deploy/images/ubinize.cfg
[ubifs]
mode=ubi
image=/tmp/openvuplus/build/vuuno/tmp/deploy/images/vuplus-image-vuuno-20150831154945.rootfs.ubifs
vol_id=0
vol_type=dynamic
vol_name=rootfs
vol_flags=autoresize
[user@server tmp]


This is what happens when I try and boot from this image (i compiled it myself).

(see attachment for full log)

UBI: scanning is finished
UBI error: vtbl_check: too large reserved_pebs 572, good PEBs 228
UBI error: vtbl_check: volume table check failed: record 0, error 9
Volume table record 0 dump:
reserved_pebs 572
alignment 1
data_pad 0
vol_type 1
upd_marker 0
name_len 6
name rootfs
crc 0x7089bf6d
UBI error: ubi_attach_mtd_dev: failed to attach mtd0, error -22
UBI error: ubi_init: cannot attach mtd0
ALSA device list:
No soundcards found.
ata2: SATA link down (SStatus 4 SControl 300)
UBIFS error (pid 1): ubifs_mount: cannot open "ubi0:rootfs", error -19
VFS: Cannot open root device "ubi0:rootfs" or unknown-block(8,1): error -19
Please append a correct "root=" boot option; here are the available partitions:
1f00 116736 mtdblock0 (driver?)
1f01 4096 mtdblock1 (driver?)
1f02 4096 mtdblock2 (driver?)
1f03 2048 mtdblock3 (driver?)
1f04 1024 mtdblock4 (driver?)
1f05 512 mtdblock5 (driver?)
1f06 512 mtdblock6 (driver?)
1f07 1024 mtdblock7 (driver?)
0800 117220824 sda driver: sd
0801 117218268 sda1 00000000-01
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(8,1)
Rebooting in 180 seconds..
Click to expand...
Interesting post.
I've took a look into your log and I'm happy to read that your box with a new NAND boots but not mount correctly the root filesystem due to this error:
Code: 
UBI: scanning is finished
UBI error: vtbl_check: too large reserved_pebs 572, good PEBs 228
UBI error: vtbl_check: volume table check failed: record 0, error 9
Volume table record 0 dump:
        reserved_pebs   572
        alignment       1
        data_pad        0
        vol_type        1
        upd_marker      0
        name_len        6
        name            rootfs
        crc             0x7089bf6d
UBI error: ubi_attach_mtd_dev: failed to attach mtd0, error -22
UBI error: ubi_init: cannot attach mtd0

I've never replaced a NAND but can be interesting to learn how you have changed it.
I'll mention here my colleague @dpeddi that hope can help you.
 
D

dpeddi

Administrator
Interesting... I think you should check linux sources ...perhaps cfe support spansion but linux needs to be patched or enabled to do so
 
D

duggy

Vu+ Newbie
Thanks for replying guys, appreciate it!, even if this never works the ride has been interesting. More so now as we are close to getting this working! :)

Right, the reason why I used the spansion chip is that its supposed to be a drop in replacement for the original samsung nand K9F1G08U0D which is discontinued.

See this advisory on the matter.

http://www.spansion.com/Support/Application Notes/Migrate_Samsung_K9F1G08U0D_to_S34ML01G1_AN.pdf

Its pin compatible and same instruction set, also unlike the K9F1G08U0E which I tried first, this is supposed to be 100% instruction set compatible too.

The only thing I had to do was change one part of the BBS config to get it to be picked up so I could program the CFE (i used the CFE from the original nand).

As for the source code, i'm unsure how to proceed as I'm a Java guy and the C/C++ code is alien to me. Any guidance would be gratefully received, I have download the openvu src code and am able to compile it without issue. I've been testing things by serial flashing the NFI file thats output. Although the USB flash erases and programs without issue, I get kernal panic on boot so I think the USB stack in the CFE chokes, the NFI route seems to work 99%, just the mount of the rootfs dies :(

That arabic image i used had an old version of meaboot 0.9X which I thought might be a way to get a new version of BH to work, but its a very old version and i didnt have much luck with it even working with the tuner (setup right but a scan found nothing), I suspect the drivers on that image (from BH 1.6.9 are too old), thats also why I want to use a newer image, nothing newer than working with src code from the git repo :)

@angelofsky1980

Getting original nand off and installing the Spansion or the other Samsung nands I tried (E variant) was just with a hotair rework station, considering I'm no expert and an amateur I'm impressed it worked too, but its worked fine a few times so I'm either really lucky or with patience anyone can do it (I believe this is more likely).
 
D

duggy

Vu+ Newbie
Right I see some interesting things in ./meta-bsp/vuduo2/recipes/linux/linux-vuplus-3.3.8/nand_base.patch

Thing is i cant find nand_base.c anywhere. This looks like it should be part of the kernal source that I I think I should have got from the git clone i did to setup the environment?

git clone git://code.vuplus.com/git/openvuplus.git

Where does nand_base.c come from if not from the git clone?
 
You must log in or register to reply here.
Top