Skip to content

No MAC address in boot_out.txt #10777

Description

@Jerzeek

CircuitPython version and board name

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.

Code/REPL

print("hello world")

Behavior

hello world

Description

No response

Additional information

No response

Activity

  1. dhalbert commented on Jan 14, 2026

    @dhalbert
    Collaborator

    Please point us to the repo code for your board, so we can compare the board-specific files.

  2. added this to the Support milestone on Jan 14, 2026
  3. Jerzeek commented on Jan 14, 2026

    @Jerzeek
    Author

    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

  4. dhalbert commented on Jan 14, 2026

    @dhalbert
    Collaborator

    If I comment out

    //#define MICROPY_HW_NEOPIXEL (&pin_GPIO2)
    

    in mpconfigboard.h, then it works (!). Investigating further.

  5. modified the milestones: Support, 10.1.0 on Jan 14, 2026
  6. Jerzeek commented on Jan 15, 2026

    @Jerzeek
    Author

    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.

  7. Jerzeek commented on Jan 15, 2026

    @Jerzeek
    Author

    Let me know if you want me to test anything on the device.

  8. dhalbert commented on Jan 15, 2026

    @dhalbert
    Collaborator

    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.

  9. Jerzeek commented on Jan 15, 2026

    @Jerzeek
    Author

    Makes sense,
    This was the response:

    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.

  10. dhalbert commented on Jan 15, 2026

    @dhalbert
    Collaborator

    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.

  11. modified the milestones: 10.1.0, 10.x.x on Feb 10, 2026
  12. modified the milestones: 10.x.x, 11.0.0 on Sep 28, 2026
  13. self-assigned this
    on Nov 5, 2026
  14. mikeysklar commented on Nov 16, 2026

    @mikeysklar
    Collaborator

    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?

  15. Jerzeek commented on Nov 16, 2026

    @Jerzeek
    Author

    Interesting: I am getting a valid mac address on 10.3.1, but not on 11.0.0

    image image
  16. Jerzeek commented on Nov 16, 2026

    @Jerzeek
    Author

    version 11.0.0-alpha.2 does work!
    image

  17. mikeysklar commented on Nov 16, 2026

    @mikeysklar
    Collaborator

    Thank you for testing.

  18. dhalbert commented on Nov 16, 2026

    @dhalbert
    Collaborator

    It worked in alpha.2 but not alpha.3, so there's a regression, so reopening.

  19. mikeysklar commented on Nov 18, 2026

    @mikeysklar
    Collaborator

    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?

  20. added a commit that references this issue on Nov 19, 2026
    11092db
  21. Jerzeek commented on Nov 19, 2026

    @Jerzeek
    Author

    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.

  22. added a commit that references this issue on Nov 20, 2026
    fd7fc83
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions