06-02-2018, 09:40 PM
(06-02-2018, 05:07 PM)p3ntium Wrote: Always it's hard like this? I mean, I have a lot of raspberries pi 3 and all boot at first time after burn the image with etcher.
With this board (Rock64), after my experience and other posts I've read, it seems that the Rock64 is hard to get a stable boot...
It's very frustrating...
No, not always. Just when people use the development images when there are changes being tested which result in their boards not working, or use cards that the rock64 doesn't like (neither of which issues the raspberry pi are immune to... just they don't happen as often as it's a more mature board and community), things don't work well
So, like rockcklobster suggested, if you can, check and make sure your power supply is working properly - the right voltage is between 5.0 & 5.2 volts (it should drop nearer to 5.0 under load). And also as Z80 said, double check the microSD socket to make sure it is going in properly.
If you've got your usb serial set at 1.5M (1500000) baud, and are not getting any output with 6 (GND) and 8 (usbserial-RX) (don't worry about 10/TX for now - especially as power from the TX connection can stop the rock64 booting cleanly) and an image such as bionic-minimal-rock64-0.6.44-239-arm64.img.xz doesn't work or give any output at all, then it's most likely 1) a microSD card mismatch (have you tried a Samsung EVO card yet?) 2) a power supply fault 3) your usbserial can't cope with a 1.5M baud rate or 4) the board is DOA and needs to be replaced.