This was verified using a Raspberry Pi Pico W & CircuitPython 8.1
Earlier this year the team did a wonderful job of allowing our campus network, which approves devices based on MAC address, not password, to work properly. Campus requires the MAC address to be registered. This works great, but when taking devices from my home network to the campus network, I need to first modify the settings.toml file remotely, otherwise when plugging the device into the campus network it seems to repeatedly reboot over & over again WITHOUT mounting as CIRCUITPY. Sometimes when I unplug & plug the device in RPI-RP2 will show, other times the device seems to be trying to run something - perhaps code.py that contains code to connect to the network, but is never allowed to mount. I was able to nuke all of these devices & reinstall software. If I update code on a device that hasn't had its MAC address proved yet, I can see in Mu that the connection is not being made - it's only when the code tries to run outside of Mu that this "never shows CIRCUITPY" issues shows up. After nuking the device, running code to get the MAC address, registering the MAC address, the adding back working lib, code, and settings.toml file, things work normally.
dhalbert
commented
1 year ago
CircuitPython version
This was verified using a Raspberry Pi Pico W & CircuitPython 8.1 Earlier this year the team did a wonderful job of allowing our campus network, which approves devices based on MAC address, not password, to work properly. Campus requires the MAC address to be registered. This works great, but when taking devices from my home network to the campus network, I need to first modify the settings.toml file remotely, otherwise when plugging the device into the campus network it seems to repeatedly reboot over & over again WITHOUT mounting as CIRCUITPY. Sometimes when I unplug & plug the device in RPI-RP2 will show, other times the device seems to be trying to run something - perhaps code.py that contains code to connect to the network, but is never allowed to mount. I was able to nuke all of these devices & reinstall software. If I update code on a device that hasn't had its MAC address proved yet, I can see in Mu that the connection is not being made - it's only when the code tries to run outside of Mu that this "never shows CIRCUITPY" issues shows up. After nuking the device, running code to get the MAC address, registering the MAC address, the adding back working lib, code, and settings.toml file, things work normally.
Code/REPL
Any of the connection code using WiFi that's in this repo should produce those results: https://github.com/gallaugher/disco-button/tree/main Verified specifically with https://github.com/gallaugher/disco-button/blob/main/disco_subscriber_just_lights.py
Behavior
mentioned above - board never mounts as CIRCUITPY, lights on board flash every few seconds.
Description
see above
Additional information
Thanks for all of your help!