It is indeed aarch64 rpi0_2
tyoc213
0
undeadko
Hello guys, I have started a small project on R-Pi Zero 2 W and I am facing the same problems. I am just checking if there is anything new on this topic?
For the record, I do know that the cable I am using is a proper one. I have SSH-ed into the Pi when it has a Raspbien on. I have 2 SD cards. One with Nerves and one with Raspbien. So the Raspbien things work properly, and I know everything I am doing is working. I do the same things for Nerves but I can’t seem to SSH.
I have plugged a monitor through the mini HDMI port and all I can see is a cursor at the top left. I have plugged a keyboard - nothing on the monitor.
I am about to try the WiFi configuration before burning Nerves on the SD card, but this seems like a very roundabout way of making this work and honestly it doesn’t feel right. Same with the USB to TTL approach, which I might try next.
Any help on this topic would be greatly appreciated!
0
fhunleth
Co-author of Nerves
The RPi Zero 2 images don’t use HDMI by default. The console goes through the UART pins on the header. You should still be able to ssh to an IEx prompt via the USB cable. The main thing to check is that the USB cable is plugged into the USB port that’s closer to the middle of the board since that one supports data transfers. On your laptop, you should see a new Ethernet connection on the USB show up in a few seconds after the device boots.
If all else fails, could you please double check with a pre-built Nerves firmware image like one from Circuits Quickstart?
0
undeadko
Hi and thank you for the quick response!
Yes, the cable is plugged into the correct port. The cable also transfers data. I have made sure that it works by SSH connecting on the Raspbian OS beforehand.
I have tried downloading a Circuits Quickstart .fw file for rpi3a, and when I try to ssh this is the result:
ssh nerves.local
ssh: Could not resolve hostname nerves.local: Name or service not known
With the hello_nerves project that I configured the WiFi with I reached the IP through PuTTy. Unfortunately, it then asked me for an account and password which I couldn’t find any defaults anywhere? I think that is a dead end for me as well.
Any other suggestions would be awesome! In the meantime I might try and test the USB to TTL option, however undesirable it is for me 
.
0
fhunleth
Co-author of Nerves
Oh, it sounds like you’re on Windows.
I think what’s happening is that multicast DNS isn’t enabled on your machine and that’s why nerves.local doesn’t resolve. Unfortunately, I don’t know the right way to enable mDNS support these days. It used to be to install Apple’s Bonjour package.
However, if you can get the IP address of the virtual USB Ethernet coming from the Pi Zero, you’ll be able connect - just subtract 1 from the last part. For example, if your computer’s IP address is 172.31.216.239, then ssh 172.31.216.238.
For the issue where PuTTy was asking for account and password, there are two solutions. Nerves uses public/private key authentication by default. If you look at the config/target.exs, you’ll see the configuration. Once you load the private key into PuTTy, it should work. Alternatively, you can change the ssh config to use password auth as shown in NervesSSH — nerves_ssh v1.3.1.
0
undeadko
Hello,
I was using a Windows machine and an Ubuntu VM. Both failed. Today I have tried with an Ubuntu machine. Same results. ssh nerves.local does not work for some reason 
.
I was not having any success with the USB to TTL also. This leads me to thinking that maybe I am doing something fundamentally wrong.
I follow this guide here - Getting Started — nerves v1.14.3 (except the test with Circuits Quickstart) Is there a chance it is outdated? For example, should I still do export MIX_TARGET=rpi3a? I have seen a suggestion using export MIX_TARGET=rpi0_2. Is that a valid tag?
Another explanation I can think of is if my SD card is somehow the problem. However, I do get a flashing underscore _ on my monitor if I connect the HDMI. Naturally, this doesn’t do me any good, but it would suggest that the SD card is OK and I have successfully burned Nerves on it, no?
I will try digging through the config/target.exs as you have suggested. Honestly, however, I am very unwilling to get it working with a roundabout way as this and call it a day. I would prefer if I get it working with straight SSH connection through the USB
Cheers!
0