4d80a9d1c3
The RP2040 MicroPython loader always fetched the plain RPI_PICO build, which
ships no `network` module and no CYW43 WiFi driver. Every Pico W WiFi/MQTT
example therefore failed at `import network` ("no module named 'network'"),
which surfaced as a compile/run error in the editor.
- getFirmware()/loadUserFiles() are now variant-aware. pi-pico-w boards load
RPI_PICO_W-20230426-v1.20.0 (network/socket/ssl + the CYW43439 driver) and
write the LittleFS at the W board's flash offset (0x12c000, 212 blocks)
instead of the plain Pico's 0xa0000/352. The W firmware spans flash to
~0xab000 and would otherwise be clobbered by the filesystem. Each variant
gets its own IndexedDB cache key.
- The variant is selected by the presence of the already-wired CYW43 emulator
(attachCyw43 runs for pi-pico-w boards only).
- loadMicroPython swaps in a fresh RP2040 each run, so the CYW43 PIO-FIFO hooks
are re-installed on the new instance; otherwise the driver's gSPI traffic
never reaches the emulator and WiFi never comes up.
- Bundle micropython-rp2040w.uf2 as the offline fallback.
- Point the ThingsBoard example at the simulator's Velxio-GUEST network.
|
||
|---|---|---|
| .. | ||
| .well-known | ||
| boards | ||
| component-svgs | ||
| components | ||
| examples-thumbs | ||
| firmware | ||
| fonts | ||
| marketing | ||
| wasm/ngspice-interactive | ||
| android-chrome-192.png | ||
| android-chrome-512.png | ||
| apple-touch-icon.png | ||
| components-metadata.json | ||
| favicon-16x16.png | ||
| favicon-32x32.png | ||
| favicon-48x48.png | ||
| favicon.ico | ||
| favicon.svg | ||
| image.png | ||
| image.webp | ||
| llms.txt | ||
| manifest.webmanifest | ||
| og-image.png | ||
| og-image.svg | ||
| robots.txt | ||
| sitemap.xml | ||
| vite.svg | ||
