Fix totally bricked vocore2

velo
 
Posts: 5
Joined: Mon Jan 30, 2017 8:02 am

Fix totally bricked vocore2

Tue Jan 08, 2019 8:33 pm

Hi! I'm trying to follow http://vonger.cn/?p=8054

I did flash http://vonger.cn/misc/vocore2/vocore2.fixbrick.zip first.

And I connected all wires. When connected via USB, I can see messages for spi:

Code: Select all
[    0.280000] spi-mt7621 10000b00.spi: sys_freq: 193333333
[    0.290000] m25p80 spi32766.0: found gd25q128, expected en25q64
[    0.300000] m25p80 spi32766.0: gd25q128 (16384 Kbytes)
[    0.310000] m25p80 spi32766.0: using chunked io
[    0.310000] 4 ofpart partitions found on MTD device spi32766.0
[    0.320000] Creating 4 MTD partitions on "spi32766.0":
[    0.320000] 0x000000000000-0x000000030000 : "u-boot"
[    0.330000] 0x000000030000-0x000000040000 : "u-boot-env"
[    0.330000] 0x000000040000-0x000000050000 : "factory"
[    0.340000] 0x000000050000-0x000000800000 : "firmware"
[    0.380000] 2 uimage-fw partitions found on MTD device firmware
[    0.380000] 0x000000050000-0x0000001682fe : "kernel"
[    0.390000] 0x0000001682fe-0x000000800000 : "rootfs"
[    0.390000] mtd: device 5 (rootfs) set to be root filesystem
[    0.400000] 1 squashfs-split partitions found on MTD device rootfs
[    0.410000] 0x0000006c0000-0x000000800000 : "rootfs_data"
[    0.420000] m25p80 spi32766.1: found mr25h256, expected en25q64
[    0.420000] m25p80 spi32766.1: mr25h256 (32 Kbytes)
[    0.430000] m25p80 spi32766.1: using chunked io
[    0.430000] 1 ofpart partitions found on MTD device spi32766.1
[    0.440000] Creating 1 MTD partitions on "spi32766.1":
[    0.440000] 0x000000000000-0x000001000000 : "attached"
[    0.450000] mtd: partition "attached" extends beyond the end of device "spi32766.1" -- size truncated to 0x8000


However, truncated size of spi32766.1 seems shorter than in the tutorial.

/proc/mtd seems different, too:
Code: Select all
root@vocore2:/# cat /proc/mtd
dev:    size   erasesize  name
mtd0: 00030000 00010000 "u-boot"
mtd1: 00010000 00010000 "u-boot-env"
mtd2: 00010000 00010000 "factory"
mtd3: 007b0000 00010000 "firmware"
mtd4: 001182fe 00010000 "kernel"
mtd5: 00697d02 00010000 "rootfs"
mtd6: 00140000 00010000 "rootfs_data"
mtd7: 00008000 00008000 "attached"

Now the flashing fails:
Code: Select all
root@vocore2:/# md5sum /tmp/ultimate.16m.img
f4c527a1e563d0ad7ef9ab0b5e0b35c6  /tmp/ultimate.16m.img
root@vocore2:/# mtd -e attached write /tmp/ultimate.16m.img attached
Unlocking attached ...
Erasing attached ...
Writing from /tmp/ultimate.16m.img to attached ...  [ ]
[e]Failed to erase block
root@vocore2:/# :(



Any idea what I may be missing? What can I do to test if my bricked vocore2 is totally dead silicon? I tested different voltage outputs, when normally powered, and those readings seemed okay.

Vonger
 
Posts: 711
Joined: Sun Oct 19, 2014 6:00 am

Re: Fix totally bricked vocore2

Wed Jan 09, 2019 12:12 pm

The flash id did not recognize correctly, so vocore do not attach it with correct size(only make it to 32KB)
Do you keep the bricked VoCore2 into reset mode?(connect RST pin to GND)
And cables might not correct, looks like some bit is lost, so it can not get correct flash chip id caused it can not show correct size.
If it is possible, take a photo of your connection.

velo
 
Posts: 5
Joined: Mon Jan 30, 2017 8:02 am

Re: Fix totally bricked vocore2

Wed Jan 09, 2019 9:32 pm

It worked!!!
spi_mtd.JPG
lots of orange cables
spi_mtd.JPG (233.38 KiB) Viewed 240 times

Thank you for making me try again, I forgot cable 1, 3V3 m( Had to do a few reboots, but then it showed the full size:
Code: Select all
[    0.420000] m25p80 spi32766.1: found w25q128, expected en25q64
[    0.420000] m25p80 spi32766.1: w25q128 (16384 Kbytes)
[    0.430000] m25p80 spi32766.1: using chunked io
[    0.430000] 1 ofpart partitions found on MTD device spi32766.1
[    0.440000] Creating 1 MTD partitions on "spi32766.1":
[    0.440000] 0x000000000000-0x000001000000 : "attached"

and I could flash
Code: Select all
root@vocore2:/# mtd -e attached write /tmp/ultimate.16m.img attached
Unlocking attached ...
Erasing attached ...

Writing from /tmp/ultimate.16m.img to attached ...     
root@vocore2:/# md5sum /tmp/ultimate.16m.img
f4c527a1e563d0ad7ef9ab0b5e0b35c6  /tmp/ultimate.16m.img


Unfortunately the brick stays a brick - no LED on power and no output in terminal :(

I guess that one has to rest in pieces...

Return to VoCore2/Lite/Ultimate

Who is online

Users browsing this forum: No registered users and 2 guests