In a previous post I explained how to getting started with STM32 with classical Eclipse or Keil environments. These environments are very cool for starting from scratch in designing firmware. That said, you have to recreate a lot of basic functions and libraries to create your firmware.
On the other hand, the Arduino community is proposing a lot a existing libraries and a development framework with a large number of supported features. The STM32 community looks active and that’s a good way to quickly create advanced firmware.
That said there is different point blocking in my point of view for using Arduino as a professional environment:
- Outside of the core libs and some nice one, most of the lib are badly written
- The official editor is a mess if you manage more than 3 files…
- Writing libraries with official editor is… “impossible”
For this reason, in this tuto, I’ll use Visual Code Studio to see if the 2 last point can be solved. Regarding the first point, there is nothing better than using well coded libraries and rewrite (and share) the badly written one.
After making some post on
This is a Frequent question I received from many hackers or companies: How can I get a Sigfox subscription for my IoT device?
Since I’m using Sigfox backend there are a lot of operations I’m regularly manually doing. Thanks to the
Since a long time I’m trying to understand how the Sigfox right (ACL) works and stop affecting all the rights to my API access every time I’m creating a new one. More than that, when I’m working with clients or other LPWAn passionates I do not like requesting full access to the Sigfox backend to help them or integrate them in my backend.
As a backend developer, the Sigfox API is not a really good experience. This for multiple reasons and it is a good example on how a really good product can get a developer push-back just because of the interaction layer.