Closed sowbug closed 6 months ago
What do you get when you run
uname -a
on the Raspberry Pi 3B?I think it will be You already posted; it is armv71
.armv7l
Here's a suggested change to the architecture detection code in frameos/backend/apps/tasks/deploy_frame.py
-- if arch == "aarch64":
++ if arch == "aarch64" or arch == "armv7l":
cpu = "arm64"
elif arch == "armv6l":
cpu = "arm"
elif arch == "i386":
cpu = "i386"
else:
cpu = "x86_64"
I reimaged with the 64-bit lite OS choice (which I now see the instructions suggested), and uname -m
now reports aarch64
. I'm still waiting for the setup to complete, but I bet this was the problem.
Unless there's a reason why the other architectures can't work, it would be really nice to be more flexible about them (as I see @alexrudd2 has already done!).
Aw, heck, and now I just did this:
Ouch, that hurts :(.
I'm following the setup instructions. I ran into the issue that the controller's generated RSA keys don't work, but I manually worked around it. When I tried to deploy to my RPi 3 Model B with a Waveshare 7.5 display, I got this in the logs:
As you can see, things go off the rails at
Error: unknown CPU: 'x86_64'
, or maybe earlier when it sends thenim compile --os:linux --cpu:x86_64
command, which doesn't seem to make sense if it's compiling on the rpi for the rpi.Is this because I am using a Raspberry Pi 3 Model B?