Andrew Scheller

Be aware that if you change the docs to say "must configure the pin" then you might run into problems like #1601

This seems to be a duplicate of #1788 ? (which was fixed on the `develop` branch by https://github.com/raspberrypi/pico-sdk/commit/424e21ec0793219e5b24f1566f3cbcf4263f5919 )

It might be a red herring, but are you able to boot successfully if you unplug the lan7801 ? ``` [ 7.151269] usb 1-1.5.4: New USB device found, idVendor=0424, idProduct=7801,...

I know this PR is still in draft, so you may already be planning this, but a brief `README.md` explaining what this example does, and how to use it (e.g....

Looking at https://github.com/georgerobotics/cyw43-driver/blob/main/src/cyw43_config.h , `CYW43_DEBUG`, `CYW43_INFO` and `CYW43_WARN` are all implemented by calls to `CYW43_PRINTF`. `CYW43_PRINTF` is itself declared as ```c #ifndef CYW43_PRINTF #include #define CYW43_PRINTF(...) printf(__VA_ARGS__) #endif ``` so...

...and #2490

_Perhaps_ people might be surprised that setting `CYW43_PRINTF_ENABLED` to 0 **also** stops `CYW43_DEBUG`, `CYW43_INFO` and `CYW43_WARN` from working? (i.e. perhaps we need a "more generic" name than `CYW43_PRINTF_ENABLED`, e.g. `CYW43_LOGGING_ENABLED`...

> * PICO_BTSTACK_PATH > * PICO_CYW43_DRIVER_PATH > * PICO_LWIP_PATH > * PICO_MBEDTLS_PATH > * PICO_TINYUSB_PATH These ones were added in #2405 🙂

> * PICO_FLASH_SIZE_BYTES This one has a `PICO_CONFIG:` entry [here](https://github.com/raspberrypi/pico-sdk/blob/develop/src/rp2_common/hardware_flash/include/hardware/flash.h#L53) i.e. it appears in section 5.1 of https://datasheets.raspberrypi.com/pico/raspberry-pi-pico-c-sdk.pdf > (SDK searched with regex `if.*NOT.*PICO_` ) I decided to use a...

> I wonder if it happened to more people. You could say that... 🤣 See #4150