I have a NanoPi NEO Air running the FriendlyCore Xenial 3.4.39_20171102 image from eMMC. Last thing I did was "sudo turn-wifi-into-apmode yes" and now I don't get a shell after boot using a USB-TTL cable connected to UART0. It just hangs after "systemd[1]: Started Journal Service"...

I noticed that if I interrupt u-boot and issue the "shutdown" command, the current drops to around 11mA.

The 3.3 and 5V pins also stay live after "shutdown -P now". Is FriendlyCore is leaving hardware powered after shutdown by design?

I have a NanoPi Neo Air running the FriendlyCore Xenial 3.4.39_20171102 image. The board continues to draw about 40mA after "shutdown -P now". I've measured this both with a USB power meter connected to a 3.0 port, and an external power supply with an inline multimeter. As far as I can tel...

KotCzarny helped me out. The wakeup pin needs to be active low. Thanks!

I believe I was mistaken - apparently there is a quick current drop, and based on uptime when I log back in I think it's actually rebooting the Air. Uptime shouldn't reset when waking up from suspend, I would think.

Thank you for the reply. I haven't been able to get this to work; I ran it as below and it just sits there after the last line. I get kicked off the ssh session if I type anything. I have an inline USB power meter on the board and the current never drops, and I can ping it successfully from another ...

Hello, I have a NanoPi Neo Air running the FriendlyCore Xenial 3.4.39_20171102 image. I can put the board into a suspend state using pm-suspend, but cannot wake it back up. Ideally I'd like to be able to wake it up using a GPIO pin as an input. Is this possible? I'm not sure where to start.

Thank you