This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

NCS/Zephyr support of Micro:bit V2 - lack of enthousiasm?

Hello,

given that the Micro:bit V2 (Nrf52833 based) has been promoted in Webinars, I am surprised on the lack of enthousiasm in getting it to work properly under NCS/Zephyr.

What is the problem : Zephyr contains since quite some time Code and samples for the micro:bit V1 (Nrf51822 based).

We agree, it's a "toy" nevertheless a toy with extremely nice features as an educational development card.

- Integrated DAPLink programmer with PyOCD support.

- Nice integrated peripherals : buttons, a LED matrix that can also serve as a light sensor, motion and magnetic sensors, touch sensors, a microphone, a buzzer

- A connector for add-on cards, e.g. for toy robots and the like.

From an educational point of view, this card is a killer as it is cheap (20EUR) yet soo full of toys. And it is popular for graphical programming frameworks for beginners (Scratch).

In short, this card is an ambassador for Nordic! The question is, can it also be an ambassador for NCS/Zephyr?!

Here is what is frustrating about this: There are several pull requests by external contributers out there that try to improve the support of this card in Zephyr, but they never get reviewed, not even negatively. The reaction to these pull requests reads much like indifference. Is this due to low priority compared to other issues? If so, why not eliminate exotic card support from the Zephyr main repository in the first place? That would make things clear.

Thank you for your opinion.

Parents Reply Children
No Data
Related