[Solved] Orange Pi Zero Powering issues

[Akula]

Anyway, so here is another i can't log in my Orange Pi Zero, tried both images with Etcher, 

 

So where am i?

 

It's a bit weird, i try various USB wall chargers and sd cards, but it always get to the same point:

Permission denied, please try again.

root@192.168.1.19's password:

 

So let me ask you guys something, am i doing something Stupid, if i plug this into my modem, i can ssh to it yeah? there nothing i need to do? So i Nmaped it and sore that the vnc port is open, so password for that is 1234 as well? Like i went through the source, and i can see that the password is 1234, so the only thing that i can put it to is the setup of the sdcard but Etcher verifies the image right? So really i must have some bad powered usb ports?

 

How correct would you say my analysis is?

[riskable]

If you're seeing that a VNC port is listening you probably installed the wrong OS image.  When I boot a fresh Armbian Ubuntu Xenial image the ethernet port will use DHCP to get IPv4 only (which is a bug I think--should also be getting IPv6) and the only thing listening is SSH.  Wifi isn't enabled by default (since it doesn't know which SSID to connect to).
 
I recommend trying today's beta image:
 
http://image.armbian.com/betaimages/Armbian_5.24.161130_Orangepizero_Ubuntu_xenial_3.4.113.7z(taken from here: http://image.armbian.com/betaimages/)
 
I also recommend connecting to the serial console over UART (http://linux-sunxi.org/File:OPi_Zero_UART.jpg):


You can pick up a cable that will work here: http://a.co/78ua1Pa

[rajprakash]

Sounds strange.  I downloaded the Armbian_5.24_Orangepizero_Debian_jessie_3.4.113.7z image straight from the armbian site.  Double checked the sha256sum.  I used WinDiskImager32 to write the image to a Transcend Premium 400x 16GB UHS-1 microSD card.  Put it in my OPi0 (I have both a 256MB and a 512MB version, and the same thing worked for each), plugged in Ethernet, plugged in a 2A microusb power supply, checked my router DHCP list for the IP, and ssh connected to that IP immediately with root:1234.  I had no issues on either of my OPi Zeros.

[chris021]

I had no issues getting going with my OPi Zero-512 with the Armbian Jessie.

 

The Armbian install process is really slick

 

I have noticed however both eth0 and wifi have high ping times eth0 is around the 50ms mark and the wifi is all over the place. Is this a known issue or have I got something wrong?

[chris021]

Found my issue. I needed to disable the wireless. Once wireless was disabled the LAN worked fine. 

[Akula]

Thanks for all the responses guys, after playing around with it, i found out my cable was fault, and when i was trying to ssh to it, i was actually getting another ubuntu device.

 

For anybody else, as soon as you plug the power in the ether lights should blink, and a green light should light on the board when it's fully powered.

[tkaiser]

i found out my cable was fault

 

Which cable exactly? The one between an USB PSU and the Micro USB jack?

[Akula]

Which cable exactly? The one between an USB PSU and the Micro USB jack?

 

For me it was the micro usb power cable that was funky

[tkaiser]

Thank you for confirming the issue. I adopted thread title and start to wonder why we don't get these reports with the various NanoPi (maybe since FriendlyARM ships every board with a Micro USB cable? At the least the cables they sent out with developer samples are of superior quality)

[CursedPotato]

I also recommend connecting to the serial console over UART (http://linux-sunxi.org/File:OPi_Zero_UART.jpg):

 

You can pick up a cable that will work here: http://a.co/78ua1Pa

 

 

Anyone know why I cant get serial out of those three pins?  Is it not enabled by default?   Running Armbian_5.24_Orangepizero_Ubuntu_xenial_3.4.113

Below is my dmesg output. 

 

 

dmesg | grep tty

[    0.000000] Kernel command line: root=UUID=7dd0c931-6f7e-4fbd-83f6-544d0e1b2765 rootwait rootfstype=ext4 console=tty1 console=ttyS0,115200 cgroup_enable=memory swapaccount=1 hdmi.audio=EDID:0 disp.screen0_output_mode=1920x1080p60 panic=10 consoleblank=0 enforcing=0 loglevel=7 ubootpart=4f870cf7-01   sunxi_ve_mem_reserve=0 sunxi_g2d_mem_reserve=0 sunxi_fb_mem_reserve=16

[    0.000000] console [tty1] enabled

[    0.994431] uart0: ttyS0 at MMIO 0x1c28000 (irq = 32) is a SUNXI

[    1.131383] console [ttyS0] enabled

[    2.681640] uart1: ttyS1 at MMIO 0x1c28400 (irq = 33) is a SUNXI

[    2.697283] uart2: ttyS2 at MMIO 0x1c28800 (irq = 34) is a SUNXI

[   10.071093] systemd[1]: Created slice system-serial\x2dgetty.slice.

 

[martinayotte]

It is enabled by default as you can see with "console=ttyS0"

If you don't see any output, you should suspect your USB-TTL.

Be aware that your USB-TTL dongle should be 3.3V compatible.