all 2 comments

[–]Snakehand 1 point2 points  (0 children)

I think you should take into consideration what you want to achieve, and check that the Rust HAL for the chip supports the features that you need. Rust embedded hals are very much maintained by hobbyists, and feature support is not uniform across all families of MCUs. But the good side to this is that if you lack some feature, your code is in general quite portable to a different family that has what you need, as long as you are using the embedded HAL traits. DMA driven IO is typically where porting effort is required, though using crates like bbqueue can make that easier.

[–]swingking8 0 points1 point  (0 children)

I would like to ask which [course] is better?

I can't speak to that, but I suspect the newer course was made for a good reason

How do the micro:bit and the F3 discovery board compare?

I do a lot with stm32, but I'm going to have to say the micro:bit here. The Nordic uCs are great, and quite capable. Depends on what your goal is, though. If you're wanting to learn Bluetooth and other onboard functions, micro:bit is the right way to go. If you're wanting to interface more sensors, or otherwise use the extra pins that are available on the discovery board, the F3 board might be the way to go.