Hardware issue overheating while booting and fail to boot

[dukla2000]

This is all intriguing and I wish we could resolve what is wrong. But I would figure a warranty claim on your vendor is the pragmatic route. My reason for coming to this conclusion is the success/failure of the serial connection: success in that you are getting output, failure because it is gibberish. You can aim them at this thread to prove what has been tried!

Re: Bullet64 and dukla2000:
So, I found the serial connection (just to be clear, it is a usb-TTL adapter), and some interesting results were encountered.
First, I followed the the guide from the wiki here (https://forum.pine64.org/showthread.php?tid=6387 ).

I have not done a serial connection myself but everything I have read around the ROCKPro64 indicates that is the best guide and 1.5M is absolutely the correct setting.

I then tried to enter OTG mode, and it looks like the recovery button and the LEDs work. However, the I don't see anything when connected via a usb (tried it in linux and windows) and according to the wiki "In all cases the USB device made available at the host has device ID 18d1:d00d. " That ID does not appear when I use "lsusb" to search the attached usb devices. (If there is a different command I should be using please let me know)

I did this myself last night and then wrote that section in the wiki - yup I did a plain lsusb. Again a success/fail result!! For completeness I used the USB-C connector on my ROCKPro64 so I know that works. But I cannot confirm the top USB2 actually works - I copied that into the wiki from elsewhere and it could be wrong.

On the 1-flash option I also had pcmanfm open, and a few  seconds after the red LED came on the boot and linux-root partitions from my ROCKPro64 appeared in pcmanfm (same as if I plug in a USB disk). Nothing appeared in pcmanfm on the 2, 3 and 4 blink options.

I did have 2nd thoughts afterwards that the 4 blink LED options may only work if you have a ayufan bootable image on either the eMMC or an SDcard when powering on. My to-do list includes a trial with only a blank SDcard - in particular to test if I can get rkflash to work directly for a laugh.

Just in case, I will attempt to erase the spi boot flash as you suggested (as soon as a clean up one of my other sd cards to use during that process), and will update on the results when I have them.

As I was writing the wiki and learning from the schematic and trying to phrase it simply, I think my conclusion is (as per the wiki) that the 2 jumpers are perfectly legit suppression options. If you can try with first disable SPI, then with both could be an option?


A last check: a chap on IRC last night seemed to have a duff ROCKPro64 that would not boot. His observation was that the ethernet transceiver chip (between the RJ45 socket and the CPU, has no number on the wiki exploded diagram) was getting too hot to touch after a few seconds. That is at odds with mine (generally just warm), but may be a common symptom of failure?