pico-examples VS cortex-m

Navigate to the Pico Examples repository.

I'm experimenting with the "pico/wifi/tcp_server/". It works as expected with a WPA2 secured network, however I can't figure out how to access a WP3 secured network. According to the Pico W datasheet the device supports WPA3. However the function cyw43_arch_wifi_connect_async doesn't seem to have the option to select WPA3. The supported options are CYW43_AUTH_WPA_TKIP_PSK, CYW43_AUTH_WPA2_AES_PSK, or CYW43_AUTH_WPA2_MIXED_PSK.

I connected the MPU6050 and Pico as shown in the wiring guide for the example code here and have also tried using a level shifter with this wiring setup.

https://github.com/raspberrypi/pico-sdk/ links to a PDF about connecting to the interwebs with a pi pico.

micropython/micropython//ports/rp2/boards/RPI_PICO_W: https://github.com/micropython/micropython/tree/master/ports...

raspberrypi/pico-sdk /lib: btstack, cyw43-driver, lwip, mbedtls, tinyusb https://github.com/raspberrypi/pico-sdk/tree/master/lib

raspberrypi/pico-examples//pico_w/wifi/access_point/picow_access_point.c:

https://github.com/raspberrypi/pico-examples/blob/master/pic...

There's an iperf opkg pkg, or is it just netperf (which works with fluent)?

raspberrypi/pico-examples//pico_w/wifi/iperf/picow_iperf.c:

Okay I abandoned both of those libraries and tried the simpler WS2812 example in the Pico SDK and I did get it working....finally.

For C++, you could look at the pico-examples on Github https://github.com/raspberrypi/pico-examples

I don't know what you mean. There are dozens of tutorials on the frontpage of google. And just straight up a bt folder of projects for the pico w in the rpi github at https://github.com/raspberrypi/pico-examples/tree/master/pico_w/bt. have you tried that? If you haven't, then you need to work on learning how to use google because people aren't here to do work for you. If you have tried this and it didn't work then reread my previous post and ask better questions.

I'm sorry I don't use the pico-sdk so I'm not 100% sure of which method it'd be. A short lookup in the pico-examples repository brought me to this.

The LED is controlled by a GPIO pin on the radio, not the RP2040. See https://github.com/raspberrypi/pico-examples/blob/master/pico_w/wifi/blink/picow_blink.c.

I do not have as strong of feelings as your parent, but:

1. A lot of the APIs make use of the typestate pattern, which is nice, but also very verbose, and might turn many people off.

2. The generated API documentation for the lower level crates relies on you knowing the feel for how it generates the various APIs. It can take some time to get used to, especially if you're used to the better documentation of the broader ecosystem.

3. A bunch of the ecosystem crates assume the "I am running one program in ring0" kind of thing, and not "I have an RTOS" sort of case. See the discussion in https://github.com/rust-embedded/cortex-m/issues/233 for example.

For cortex-m support, check out the cortex-m crate

See https://github.com/rust-embedded/cortex-m/tree/master/panic-semihosting

I don't think so. Once a function is compiled, it basically becomes a black box with a type signature so unless sleeping in a function affects its signature, that information is erased. If you pass in some kind of a sleep token that has to be used to sleep, then yeah I think you could enforce it by only being able to get that token in a non-atomic context and making it leak proof.

The Cortex-M crate does something similar, but for proving that you are in an atomic context. Another function that expects a CriticalSection type is then assured that it's running without interrupts enabled.

https://github.com/rust-embedded/cortex-m/blob/master/src/in...