Power & Source of Big Ideas

NanoPi Fire3 does not boot

Moderators: chensy, FATechsupport

Hi together,

i bought a nanopi fire 3 board and i am struggling with getting it running. I seem unable to boot it at all. The FriendlyElec shows up but nothing more happens.
I do not have any USB-Debug device around. I tried sandisk ultra micro sd hc class 10 cards from 16-64gb, transcend 16gb micro sd hc class 10, as well as SanDisk Ultra 64GB xc.
Nothing seems to work.

Process is: Insert SD Card into PCB - plug power in... FriendlyElec Logo shows. Both LEDS light up. Screen goes black.

Would really appreciate your help!
Hello FriendlyElec,

maybe any response? Ideas? Tipps?
For the low cost of a serial debug board, it will be money well spent as it will show you clearly what is happening during the boot cycle. Without this, we have no way of helping you with this.

Any cheap USB to TTL (3.3V) converter will do the job. Just connect up GND, RX, and TX from the board to the USB converter and you can then use any Terminal Program to see what is happening to the board. Set the baud rate for 115200.
PS. The fact you see the FriendlyElec logo indicates that the board is attempting to boot.

Go get that USB to TTL serial converter and tell us what you found.
dvoeckler wrote:
Hello FriendlyElec,

maybe any response? Ideas? Tipps?


Perhaps try https://www.armbian.com/nanopi-fire3/
It comes with more recent kernel and many additional fixes.
so i figured it out - the micro hdmi is the problem - with a s430 screen it boots totally fine. but the micro hdmi does not deliver a picture as soon as the system is booting.
Are you using a kernel that supports the HDMI output?
v8dave wrote:
Are you using a kernel that supports the HDMI output?


yes dtb file quotes microhdmi to be okay and the bootlogo is showing in the end. Problem occures with all OS - friendlyelec, lubuntu and co.
Just spotted another important difference between NanoPi M3 and Fire3: 'AXP288 PMIC is gone, and replaced by an STM32 Cortex M0 MCU'. So DVFS implementation is different which also explains why with Armbian there's no difference in idle consumption/temperature when clocking with 400 vs. 1400 MHz. droidmoda.com

Who is online

In total there is 1 user online :: 0 registered, 0 hidden and 1 guest (based on users active over the past 5 minutes)
Most users ever online was 106 on Tue Jun 04, 2019 5:48 pm

Users browsing this forum: No registered users and 1 guest