2024-02-01, 10:13 AM
(This post was last modified: 2024-02-01, 10:18 AM by seandepagnier.)
I tried to reproduce this. I managed to connect as a client to 2 different networks, one encrypted the other not. Is there any chance you can try the default "mars" with given code? I will change this to openplotter for release.
What happens if you switch it to client mode, and power cycle a few seconds after and see if when it reboots it connects?
Also, try the AP + client mode. In this mode if you can, ssh in as a client and check the /var/log/dhcpcd/current and /var/log/wpa_supplicant/current log files for hints.
If you still cant get it to connect maybe try a keyboard and hdmi and check those log files for hints??
I was able to add a code to encrypt the network and it worked...
Finally, I did find an issue when changing to client and back to ap mode (not ap+client) and this too me about 3 hours to work out by editing /opt/networking.sh and adding the line:
route add -net 192.168.14.0 netmask 255.255.255.0 dev $INTERFACE
into the end of /opt/networking.sh before fi seemed to fix issues with AP mode
but must run "filetool.sh -b" to preserve it
Without this, you would have to power cycle to switch back to AP only mode.
I found a few other minor issues and fixed them (like the lease display and lcd menu for toggling ap/client mode if you are stuck), but not related to wifi working.
There is stelian's image, but it is getting old. I plan to switch to this and update everything. There will not be more development on picore 9, only bugfixs. It is just, many years has proven the reliability of picore 9 and so I want to make a final release on it. Also the infrared control doesnt work on it, and I never did figure out why, but the onboard arduino can at least decode it instead of the raspberry.
I am continuing the unstable branch and it will target this from there on. There are a lot of future developments planned.
What happens if you switch it to client mode, and power cycle a few seconds after and see if when it reboots it connects?
Also, try the AP + client mode. In this mode if you can, ssh in as a client and check the /var/log/dhcpcd/current and /var/log/wpa_supplicant/current log files for hints.
If you still cant get it to connect maybe try a keyboard and hdmi and check those log files for hints??
I was able to add a code to encrypt the network and it worked...
Finally, I did find an issue when changing to client and back to ap mode (not ap+client) and this too me about 3 hours to work out by editing /opt/networking.sh and adding the line:
route add -net 192.168.14.0 netmask 255.255.255.0 dev $INTERFACE
into the end of /opt/networking.sh before fi seemed to fix issues with AP mode
Code:
chpst -utc tce-load -i dnsmasq
mkdir -p /var/lib/misc
sv u dnsmasq
route add -net 192.168.14.0 netmask 255.255.255.0 dev $INTERFACE
fi
Without this, you would have to power cycle to switch back to AP only mode.
I found a few other minor issues and fixed them (like the lease display and lcd menu for toggling ap/client mode if you are stuck), but not related to wifi working.
(2024-01-27, 11:54 PM)MarineW29 Wrote:(2023-12-27, 10:11 PM)seandepagnier Wrote: I am still attempting a final release for pi zero boards (pi core 9) after which I will shortly be moving to pi core 13.
Hi Sean,
When do you plan to have a stable image of tinypilot based on piCore 13.1.0 or above, which can support Raspberry Pi Zero 2 W ?
I bought a Raspberry Pi Zero W, but they sent me the version 2, and it took me a while to understand why it didn't boot at all (same problem as described here).
Thanks
There is stelian's image, but it is getting old. I plan to switch to this and update everything. There will not be more development on picore 9, only bugfixs. It is just, many years has proven the reliability of picore 9 and so I want to make a final release on it. Also the infrared control doesnt work on it, and I never did figure out why, but the onboard arduino can at least decode it instead of the raspberry.
I am continuing the unstable branch and it will target this from there on. There are a lot of future developments planned.