You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We made a custom .uf2 file for our board (https://circuitpython.org/board/studiolab_picoexpander/) but when we upload this .uf2 file to the board the MAC address in the boot_out.txt prints 00:00:00:00:00:00, when I upload the Pico 2W .uf2 file to the board, it does print the right MAC address.
Fascinating,
I did ask Gemini, and it also suggested this fix, and for my it was so wild that I didn't even try it, i thought it was hallucinating.
When I run code.py to print the MAC address it works fine however.
Interesting behaviour.
I did ask Gemini, and it also suggested this fix, and for my it was so wild that I didn't even try it, i thought it was hallucinating.
Well, I did it without AI, but as something that varied between the working and non-working boards. That is my usual debugging strategy in cases like this: see what's different, and then try undoing the differences. Did Gemini say why?
Thinking about this further: using the NeoPixel causes some delays, and it also uses PIO to send the data to the NeoPixel. If I remember right, the communication with the CYW43 is also via partly via PIO, to simulate an SPI peripheral, due to the pins that were chosen that did not allow use of a regular PIO peripheral. There may not be proper mediation between these uses.
I will modify circuitpython/ports/raspberrypi/boards/studiolab_picoexpander/mpconfigboard.h to comment out the MICROPY_HW_NEOPIXEL definition, as this is the most likely cause of the WiFi driver failure due to potential PIO resource conflicts. I will leave the SPI definitions untouched for now.
So it seems like a PIO problem. I guess there is no direct solution for this, we will have the students grab the MAC address from code.
Thanks anyways for the deep dive.
I think it's fixable -- if we cannot manage the access to the PIO we may just need to delay using the NeoPixel until after the CYW43 is set up and the initial data (like MAC address) is read from it. Or maybe we can just set up one of them on a different PIO.
I tried this on a Pico 2 W with the ide_tudelft_realpicoexpander build. I couldn't reproduce it.
The MAC was correct in boot_out.txt on 3 of 3 cold boots each on 10.1.0-rc.1, 10.1.4 and current main (11.0.0-alpha.3+). I had nothing connected to GPIO2, though.
@Jerzeek, do you still see it on 10.3.2, or better yet 11.0.0-alpha.3, with the NeoPixel connected?
Fix is in #11890. The MAC was printed before the WiFi chip was switched on, which only shows up with no WiFi credentials in settings.toml and a NeoPixel as the status LED.
@Jerzeek, could you try the build from that PR on your board once CI finishes?
Hey, I tried a couple of the latest builds from the S3 bucket but I cant get our board to work, the circuitpython drive does not show up.
Let me know when I can test again.
Activity
dhalbert commentedon Jan 14, 2026
Please point us to the repo code for your board, so we can compare the board-specific files.
Jerzeek commentedon Jan 14, 2026
Hi Dan,
Thanks for the quick reply, here are the board specific files:
https://github.com/adafruit/circuitpython/tree/main/ports/raspberrypi/boards/studiolab_picoexpander
It uses a complete PICO 2W.
The PCB files are published here: https://github.com/id-studiolab/PicoExpander
dhalbert commentedon Jan 14, 2026
If I comment out
in
mpconfigboard.h, then it works (!). Investigating further.Jerzeek commentedon Jan 15, 2026
Fascinating,
I did ask Gemini, and it also suggested this fix, and for my it was so wild that I didn't even try it, i thought it was hallucinating.
When I run code.py to print the MAC address it works fine however.
Interesting behaviour.
Jerzeek commentedon Jan 15, 2026
Let me know if you want me to test anything on the device.
dhalbert commentedon Jan 15, 2026
Well, I did it without AI, but as something that varied between the working and non-working boards. That is my usual debugging strategy in cases like this: see what's different, and then try undoing the differences. Did Gemini say why?
Thinking about this further: using the NeoPixel causes some delays, and it also uses PIO to send the data to the NeoPixel. If I remember right, the communication with the CYW43 is also via partly via PIO, to simulate an SPI peripheral, due to the pins that were chosen that did not allow use of a regular PIO peripheral. There may not be proper mediation between these uses.
Jerzeek commentedon Jan 15, 2026
Makes sense,
This was the response:
So it seems like a PIO problem. I guess there is no direct solution for this, we will have the students grab the MAC address from code.
Thanks anyways for the deep dive.
dhalbert commentedon Jan 15, 2026
I think it's fixable -- if we cannot manage the access to the PIO we may just need to delay using the NeoPixel until after the CYW43 is set up and the initial data (like MAC address) is read from it. Or maybe we can just set up one of them on a different PIO.
mikeysklar commentedon Nov 16, 2026
I tried this on a Pico 2 W with the ide_tudelft_realpicoexpander build. I couldn't reproduce it.
The MAC was correct in boot_out.txt on 3 of 3 cold boots each on 10.1.0-rc.1, 10.1.4 and current main (11.0.0-alpha.3+). I had nothing connected to GPIO2, though.
@Jerzeek, do you still see it on 10.3.2, or better yet 11.0.0-alpha.3, with the NeoPixel connected?
Jerzeek commentedon Nov 16, 2026
Interesting: I am getting a valid mac address on 10.3.1, but not on 11.0.0
Jerzeek commentedon Nov 16, 2026
version 11.0.0-alpha.2 does work!

mikeysklar commentedon Nov 16, 2026
Thank you for testing.
dhalbert commentedon Nov 16, 2026
It worked in alpha.2 but not alpha.3, so there's a regression, so reopening.
mikeysklar commentedon Nov 18, 2026
Fix is in #11890. The MAC was printed before the WiFi chip was switched on, which only shows up with no WiFi credentials in settings.toml and a NeoPixel as the status LED.
@Jerzeek, could you try the build from that PR on your board once CI finishes?
raspberrypi: power up the CYW43 before printing the MAC in boot_out.txt
Jerzeek commentedon Nov 19, 2026
Hey, I tried a couple of the latest builds from the S3 bucket but I cant get our board to work, the circuitpython drive does not show up.
Let me know when I can test again.
raspberrypi: don't print MAC in boot_out.txt