FriendlyELEC-Forum

(I'm making a best guess on where to post this. Let me know if it should be elsewhere.)

I received my NanoPi NEO 2 last week. First FriendlyARM, but not first Pi. I was able to copy the image on to a 32GB card and booted it with the UART connected and got to a shell. The green LED was on and the blue was (single) blinking as it should, and connecting the Ethernet got an IP. All good.

Today I connected it up the same way and no joy. No response on the UART, and no DHCP request. The green power LED is on but the blue is now double blinking (blink-blink-pause).

I've tried re-formatting and imaging the SD card with no luck. I can substitute my Raspberry Pi 2 B in the setup and it works fine so it isn't a power or connection problem. When I connect the NEO's SD card to the RPi with an USB reader I can mount and read the partitions just fine. Ive also tried giving it about an hour to "Get Going" but it just double flashes.

Is there anything I'm missing or do I have a bum device?

-Bion

Hi,
Could you give the dmesg information to me ? Do the terminal show any information when booting the NEO2?

Thank you!

NorthpassKid wrote:
Today I connected it up the same way and no joy. No response on the UART, and no DHCP request. The green power LED is on but the blue is now double blinking (blink-blink-pause).

I've tried re-formatting and imaging the SD card with no luck. I can substitute my Raspberry Pi 2 B in the setup and it works fine so it isn't a power or connection problem. When I connect the NEO's SD card to the RPi with an USB reader I can mount and read the partitions just fine. Ive also tried giving it about an hour to "Get Going" but it just double flashes.

Is there anything I'm missing or do I have a bum device?

-Bion

Hi,
well (blink-blink-pause) is the way my neo air works. it's called heartbeat and indicates everything is fine...almost.
please check your connections and if you are using putty or gtkterm (or whatever) make sure the proper uart or usb-to-uart device is selected and bound-rate is 115200 and parity is none,bits are 8 and stop bit is 1.
after connecting and powering the board press an enter in the terminal.

Thanks for the replies, but not yet useful. I'm using a TTL-to-USB for the UART and it worked the first time and continues to work when connected to a full RPi 2 B. I've rechecked settings and made sure it was RX->TX,TX->RX but the NanoPi NEO 2 gives nothing. Similarly, since the NEO never gets an IP there is no SSH'ing into it, as I was able to do the first time. I can with the RPi.

Needles to say, without any terminal connection (the only way the NEO can communicate without display) there is no dmesg to know what it is doing.

What has just occurred to me is I haven't tried booting the NEO from a refreshed SD card, having the boot fail, pull the SD and mount it on a working system and looking for logs. If this yields any information I'll post it here.

-B

I tried searching for logs after the boot but the only thing added to /var/log was btmp, wtmp and lastlog. Viewing lastlog gave only this:



So it is doing something, just not enough. At this point I think it it bad hardware and I'll see it FriendlyARM will swap it out.

-B

Hello

I have a similar problem.
I'm trying to flash an image to the emmc of my NanoPi Neo Plus 2 with no success.
I use the eflasher image from the downloads section. I unzip it and burn onto an sd card with Win32Diskimager and then boot from the sd and run sudo eflasher. The process finishes with no errors but when I remove the sd and boot from the emmc, the NanoPi fails. The kernel Led will flash twice, then will stabilise for a few seconds and then will fall into endless loop doing the same thing over and over again. While this happens there is no way to ssh to it as Ethernet does not seem to load.

I flashed eflasher onto 2 different sd's and repeated the process over 5 times and every time I get the same result unfortunately. I also downloaded the eflasher image 2 times in case there was an error with the first download or unzip.

I have now flashed a fresh image onto an sd and use the nanopi booted from an sd card which obviously is not ideal...

Any ideas anyone?

I figured what the problem was.
I was flashing the images using an already installed version of Win32DSiskimager I had on my Windows Computer. When I downloaded and used the version included in the download-tools section here, I had no problem to flash the image properly onto the emmc of the NeoPlus2.

That's quite strange as I have never had problems with the version of Win32Diskimager I had been using, plus I used that exact same (problematic?) version to flash the sd with which I had been booting my NeoPlus2 while I could't figured how to use my emmc. Very strange.