pico-examples VS wg

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.

Inspired by James Munns's call, and as 2023 is coming to an end, I figure it's a good opportunity to reflect and look forward to 2024. It's been a bit over 1.5 years since I embarked on my embedded Rust journey and it's been nothing less than exciting since. So here it goes.

Because you are an embedded guy. There is the https://github.com/rust-embedded/wg working-group. Rust on embedded is really on a got track forward. There are many chips/vendors that are supported both in no std / std rust world, but still there is a lot of niche things where you can actively help to be the first to get it run in Rust.

To specifically answer your question, here:

* <http://www.areweembeddedyet.com/>

It currently redirects to:

* <https://rust-embedded.org>

Which doesn't really contain anything other than a link to <https://github.com/rust-embedded>.

(via <https://github.com/rust-embedded/wg/issues/15>)

Then the Rust Embedded workgroup provides: - Direction on how to using generics and zero-sized types to achieve functional safety - svd2rust, which provides safe abstractions to peripheral access from SVD files and achieves this functional safety - The embedded HAL spec, which makes porting to different vendors/hardware easy - Peripheral access controllers and HALs for various vendors & hardware

The Rust Embedded Devices Working Group curates a list of useful embedded Rust resources, including Peripheral Access Crates (autogenerated from SVD files), embedded-hal Implementation Crates (hand-written libraries implementing the traits (interfaces) specified by the embedded-hal), and Board Support Crates.

You should also look at https://github.com/rust-embedded/wg/issues/41 and https://github.com/rust-lang/rust/pull/55011#issuecomment-429336055.

Here's an interesting discussion, consolidated here. My view is you should use a restricted scope atomic (as best as can be supported) and interact with that through a handler struct. I.e. no global state.

Most of the issues are explained in EWG RFC 419. The TL;DR is that some resources need to implement Send to be usable from interrupts, but they must not be sent across cores.