Rock64 4Gb variant bricked
#1
Hi there,

I had debian installed on the board for a few months and decided to run one of the scripts to update the u-boot spi.
After rebooting the board could not boot up anymore.
I tried to flush a new u-boot-flash-spi-rock64.img.xz image from the sd card but it could not get to the card at all.
I needed to short pins 20 and 21 to get to the card and the white light started flushing but keeps flashing for many hours without doing anything.
Used USB to TTL Serial UART RS232 Adaptor and I was able to see output on the screen but not anymore (connect black to 6, green to 8 and white to 10).
Looks like the board is bricked.

Any help would be greatly appreciated :-)

Cheers
#2
try reading this thread
https://forum.pine64.org/showthread.php?...=erase+spi
#3
(09-06-2018, 10:27 AM)dkryder Wrote: try reading this thread
https://forum.pine64.org/showthread.php?...=erase+spi
Thank you for the quick reply.

I have been through the details of this thread but nothing helped.

It looks like the device can't get to the SD card no matter what I do and the u-boot is corrupt and does not let me talking to the sd card.
When I short 20 and 21 the white LED flashes but it does not do anything. Stays like that for days (assuming going in a loop somewhere).
I tried to flash u-boot-erase-spi-rock64.img.xz, u-boot-flash-spi-rock64.img.xz, and the latest version of armbian without success.

Before the issue happened I tried to boot the device with NetBSD-evbarm-aarch64-201809020900Z-rock64.img flashed to the SD card and then the problem started. Sorry, initially I said I flashed dome u-boot SPI image and that is wrong. Got confused with another board.

Anyhow, someone said this board in unbrickable, hmmm I must be the first one :-)

Thanks for your time .....
#4
When pin 20 clamped to GND, "SPI-FLASH-ROM" can not be read.
Therefore, boot-loader skips "SPI-FLASH-ROM", and boot from SD-Card.

However, in the clamped state, virtually "SPI-FLASH-ROM" is disable (it can not be read), so probably can not erase it.
I think that it is necessary to release the clamp promptly, after boot starts from the SD-Card.

What is the procedure you performed?

Sorry, it was a mistake
x "pin 20" -> o "pin 21"
#5
(09-06-2018, 07:57 PM)t4_4t Wrote: When pin 20 clamped to GND, "SPI-FLASH-ROM" can not be read.
Therefore, boot-loader skips "SPI-FLASH-ROM", and boot from SD-Card.

However, in the clamped state, virtually "SPI-FLASH-ROM" is disable (it can not be read), so probably can not erase it.
I think that it is necessary to release the clamp promptly, after boot starts from the SD-Card.

What is the procedure you performe
Thanks for your help.
1. Power off the board
2. insert the SD card with either u-boot-erase-spi-rock64.img.xz or u-boot-flash-spi-rock64.img.xz loaded onto the card.
3. short pin 20 and 21
4. Power on the board
5. Remove the bridge from the pins in 5 seconds. I tried longer and shorter time and it was all the same.
6. White LED starts flashing with one second intervals. Keeps flashing for ever.
7. Power off the board.
8. insert an SD card with latest Armbian image on it.
9. Power on the board
10. All LED are on and nothing happened.
Hope the situation is a bit clearer.
Thanks for helping out !!!
Cheers.
#6
OK,
Then, please obtain OS-Image from url below and write it on SD-Card and try it.
https://github.com/ayufan-rock64/linux-build/releases
OS-Image can be small in size, for example the following one
 "bionic-minimal-rock64-0.7.9-1067-arm64.img.xz"

If you have eMMC, insert a clamp jumper and disable it.
You should be able to boot from SD-Card with Pin 21 clamped to GND.
Pin 21 does not need to release clamps on the way.
If you can boot it, you can erase the SPI by another means.

If it can not be started with this method,
Please check the connection of pin 21 & pin 20 again.
---
If there is no problem with connection but startup is impossible,
It may be in a serious condition.

If unfortunately the situation is above, I do not have any more useful information for you
#7
I haven't tried this by myself with spi nor, but it could unbrick your board. There is rockchip devtool. Get it. Install it on a linux host, which you will attach rock64 to. another SBC for example. You need to connect rock64 through usb-usb to the host, without SD and eMMC, holding some button when powering it on. I haven't done this with rock64, but I did so with a rk3368 settopbox. it's probably a reset button. you hold it and while holding, power the board on. for the host it's seen as a otg client. then use rkdevtool utility on the host. it kinda can (should be able to) erase the flash. read the commands on the page in the link.
#8
(09-07-2018, 05:27 AM)t4_4t Wrote: OK,
Then, please obtain OS-Image from url below and write it on SD-Card and try it.
https://github.com/ayufan-rock64/linux-build/releases
OS-Image can be small in size, for example the following one
 "bionic-minimal-rock64-0.7.9-1067-arm64.img.xz"

If you have eMMC, insert a clamp jumper and disable it.
You should be able to boot from SD-Card with Pin 21 clamped to GND.
Pin 21 does not need to release clamps on the way.
If you can boot it, you can erase the SPI by another means.

If it can not be started with this method,
Please check the connection of pin 21 & pin 20 again.
---
If there is no problem with connection but startup is impossible,
It may be in a serious condition.

If unfortunately the situation is above, I do not have any more useful information for you

I don't have eMMC installed but somehow connecting 21 to ground makes difference (well used to).

The image you suggested did not manage to boot the board. I am not a 100% sure anymore if there is something else that I am missing.
The sd card is fine as it boots another rock64 board.
I have tried another card and it does not work either.

TTL serial to UART on 6,8,10 does not show anything. All LEDs are on when power on but no sign of life.

Probably should give up and not waste any more time on this.

Thanks for the help anyway.

Cheers

(09-07-2018, 06:39 AM)z4v4l Wrote: I haven't tried this by myself with spi nor, but it could unbrick your board. There is rockchip devtool. Get it. Install it on a linux host, which you will attach rock64 to. another SBC for example. You need to connect rock64 through usb-usb to the host, without SD and eMMC, holding some button when powering it on. I haven't done this with rock64, but I did so with a rk3368 settopbox. it's probably a reset button. you hold it and while holding, power the board on. for the host it's seen as a otg client. then use rkdevtool utility on the host. it kinda can (should be able to) erase the flash. read the commands on the page in the link.

I will have a look. Not sure what the USB to USB cable is but will google it.

Thanks for the suggestion.
#9
oh, I forgot totally to say that you need to attach USB cable into the OTG port! I told I did it with another rockchip board. and to my shame I cannot say now what exactly of them is OTG. you need to find it out. it's important.
But now when I looked into the rockchips' boot sequence, it doesn't look as optimistic as I thought. because USB OTG interface is tried at the end if nothing succeeded, oppositely to what I thought. Fortunately, for rk3328, but NOT for rk3399, ROM code tries eMMC first. So preparing a properly flashed eMMC module could save your board. If the problem is in the partially working/screwed up SPI NOR flash code.
For rk3399, spi is checked before eMMC and SD which is uh oh. because it can brick the board.
Forget about the rkdevtools, in short, :lol: use an eMMC module. if that doesn't work (but don't be hasty). that means the problem is not in SPI NOR flash.
#10
It sounds difficult.

In the state where the serial console is connected, there are the following disadvantages.

TX from the serial console becomes the voltage source ("rock 64" RX)
A small amount of voltage will remain even when the power is turned off.
Since the residual voltage value depends on the individual difference of "rock 64" and the driving ability of "TX"
There are reports that due to the above, reset does not work well and "boot" fails.

If you are lucky (unless it is broken), you still have the possibility of "booting" by removing the serial console TX.

For details, please refer to.
https://forum.pine64.org/showthread.php?tid=5008
- -
I do not have any more information that I know is useful to you.
I wish you good luck.


Possibly Related Threads…
Thread Author Replies Views Last Post
  Rock64 kernel panics clay 15 408 10-17-2021, 06:30 PM
Last Post: Rocklobster
  Pine Rock64 eMMC lifespan moonspell79 3 524 08-19-2021, 06:46 PM
Last Post: bcnaz
  Rock64 No Audio - Solved wbecks 12 17,756 08-13-2021, 01:23 PM
Last Post: blakeadam
Question Hardware issues with Rock64 grobbs 11 3,060 07-24-2021, 10:23 AM
Last Post: robinkyle11
  Trustzone support for Rock64 capablegh 1 420 07-17-2021, 10:15 AM
Last Post: capablegh
  Python GPIO Library for the Rock64 (R64.GPIO) Leapo 37 41,354 07-02-2021, 03:20 PM
Last Post: klausfelix
  rock64, compile problems "illegal instruction", "memory fault" -> ddr_333Mhz? klausfelix 0 365 07-02-2021, 03:13 PM
Last Post: klausfelix
Information Serial Console for the Rock64 MarkHaysHarris777 33 35,007 06-24-2021, 12:24 PM
Last Post: mikeklien
  lost eletronic component rock64 marvin1986 1 655 06-01-2021, 06:27 PM
Last Post: 8bit
Shocked Rock64 - Reboots after few minutes addezai 2 935 04-22-2021, 07:03 PM
Last Post: addezai

Forum Jump:


Users browsing this thread: 1 Guest(s)