STMicroelectronics’ Post

STM32 Software Development Hey everyone, if you are into embedded programming and you are using a STM32 chip in your application, here are some resources to aid you in your project. Check them out!

#FreeRTOS FreeRTOS (pronounced "free-arr-toss") is an open source real-time operating system (RTOS) for embedded systems. FreeRTOS supports many different architectures and compiler toolchains, and is designed to be "small, simple, and easy to use". https://lnkd.in/diPe-t-A

Did you know that any given color is most likely Lime Green 🍋🟢? New project: Nearest Color 🌈 Given 3 8-bit RGB values, the program displays the nearest named color. It's written in #Rust and it uses EGui to drive the UI. The GUI is immediate, responsive and rudimentary. The non-GUI version uses Rayon (#multithreaded #mapreduce) to find the nearest color for all 16777216 8-bit RGB colors and ranks the named colors by the number of colors that are nearest to them. Execution time on my machine is ~55 seconds, using 700MB of RAM and 100% of my 8-core CPU. Update: I found the bug in the code that was preventing me from implementing a fully multi-threaded solution; execution now takes the same amount of time, but only uses 2.5MB of RAM (comfortably fits in L2 cache!). More details and source code: https://lnkd.in/eTQVt4t9 https://lnkd.in/e4AsKdBq

Another reason why IAR is different and better than an open source compiler. Plus when it's done building, you want maximum visibility into your code so you can avoid be relegated to the lowest common denominator debugging: simple code breakpoints or worse... printf debugging.

New blog post about DbgRs, where I talk about adding a disassembler to the debugger! x86 instruction decoding is complex, but it's not as scary as you might think. https://lnkd.in/g_kwRkwx

In my opinion, every software developer should study the basics of C and Assembly (x86/x64 architecture) at some point. Why? Learning how a CPU executes instructions makes you think a bit more on what exactly your code is doing, because sometimes we don't know 100%. More thought is put into optimizing, making the code more effective, thus better. Especially with some bloated software/frameworks today. Knowing very well the internals of the language/framework/cpu is always a plus. Imagine two car mechanics: one relies 70% on manuals to fix problems and the other only 20%. Who would be a more efficient mechanic? Do you think this makes sense? #softwaredevelopment #software

Not having your ducks in a row, or rather your #embeddedsystems stack and heap management in order is a surefire way to run into problem that might have your system crash and burn in a very spectacular fashion. That is probably not a good thing... It also potentially opens up for security exploits that can have just as serious consequences. Both scenarios can become quite ugly in terms of both commercial and legal consequences, depending on your market. It can often seem a bit farfetched that what I do when I code something this morning might have economical or even legal consequences for my employer further down the line, but with the plethora of new and updated legal requirements coming into effect around the world, this will be more and more apparent. A very good place to start is to look at how you manage dynamic memory, including the stack, as this is a fundamental thing to get right if you want to build stable and secure products. #C #C++ #embeddedsystems #embeddedsecurity

Recently, I came across with this post https://lnkd.in/epEHzRGj, this post remember me when I was making applications at low level and required to take in consideration microprocessor cycles and memory usage. As mobile developer, always need to think in users who has low device specifications, where performance and memory are points to have in consideration. What are you experience with performance when you develop your applications? I read you on the comments

I've been working on a new cpu architecture for a little while now, with the goal of using it for a capture the flag (CTF) challenge platform. It's definitely not complete, but I thought I'd share with with y'all if you're interested in it. The main novelty of it is that its "binary" format is completely ASCII, so you can modify the binaries in a text editor rather than an hex editor. I still have some other tooling to complete, such as the disassembler, debugger, and perhaps a C compiler, but the virtual machine and assembler are complete (bug free of course). If you're interested, take a look here: https://lnkd.in/eY7Wc63U

SweetAda (https://www.sweetada.org) now runs on an FPGA-based RISC-V softcore. The DE10-Lite board, equipped with an Intel(R) MAX10, implements the free NEORV32 full-VHDL softcore (https://neorv32.org). This is a fundamental achievement because now you have a complete Ada system on silicon, with a span covering from elementary digital logic up to object oriented programming.