Our friend Jacob Beningo is a well-known lecturer in the embedded space. This month he will host a webinar sharing his experiences on designing secure bootloaders for MCUs. He will use an STM32 Nucleo board and Atollic TrueSTUDIO develoment tools.
Atollic now has a new Project Import Converter supporting IAR® EmbeddedWorkbench® for ARM® (EWARM) projects. The new Project Import Converter automatically updates EWARM projects to Atollic TrueSTUDIO format during import.
Topics: Atollic TrueSTUDIO
Our free MSP432 development and debugging whitepaper outlines professional tool support for MSP432 development, with a particular focus on advanced debugging including SWV/SWO/ITM event- and data tracing and kernel aware RTOS debugging. Stack and memory usage analysis as well as hard fault crash analysis are covered too.
Have you ever wondered what the key icon appearing on a specific file or folder in the project explorer actually means? If you don't know what it means, it could indicate you are in trouble. The key icon indicates one or several build settings for the related file or folder differs from the project's overall build settings. If you have set specific build settings for the file or folder, then the key icon is just a friendly reminder so you do not forget this.
If you are not aware of specific build settings for the file or folder, then this could lead to frustration and problems as the project may not build or execute as intended. In this blog post, I will explain how to resolve these problems.
A few days ago, Atollic opened a web shop that makes it super-simple to purchase recurring Atollic TrueSTUDIO subscription licenses! You can now get a seamless upgrade to TrueSTUDIO Pro in just a couple of minutes using your credit card - the free TrueSTUDIO Lite immediately upgrades itself to a powerful Pro version right after the purchase.
The whole process couldn't be simpler. And it is very cost-effective, too. In this blog post, I explain how you can upgrade to a TrueSTUDIO Pro subscription license in just a few minutes!
Topics: Atollic TrueSTUDIO
Will you go to the Embedded World exhibition in Nuremberg (Germany) next week? If so, be sure to come by our booth and see the latest tools for professional ARM Cortex development!
We will showcase TrueSTUDIO v7.1 and the new innovative static stack usage analyzer, as well as the build and memory usage analyzer, and much more!
Debuggers are obviously created to help developers look inside the application as it executes in the target system. The whole point is to create an interactive, or semi-interactive, execution environment where the developer largely control the execution. But what if you want to completely automate the debugger? There are many use-cases where that is convenient.
In fact, this is possible using Atollic TrueSTUDIO. You can write script files that completely control the execution of the debugger. In effect, you can completely automate certain repetitive debugger tasks.
STMicroelectronics has done a good job of creating example projects for their STM32 devices. A great job, in fact. At least if you ask me. There are well over 4000 different STM32 example projects to be downloaded from the STM32Cube page, which is a whole lot. Many of these are nontrivial, using feature-rich middleware too. I think it is safe to say they are a popular starting point for many new STM32 designs.
All of these example projects have not been ported to the Atollic TrueSTUDIO IDE, unfortunately. But thanks to the project importer, TrueSTUDIO can import almost all of these example projects automatically. Learn how in this blog post!
A few days ago, we released Atollic TrueSTUDIO v7.1. The new version is a major new release, with significant improvements that many ARM Cortex-M developers will benefit from. In fact, many developers have already taken TrueSTUDIO v7.1 for a test flight!
In addition to extended and improved target support, the new release adds a static stack usage analyzer, as well as a project importer that makes it super-easy to import ARM Cortex-M projects from the System Workbench for STM32 IDE. Read this blog post to learn more!
Topics: Atollic TrueSTUDIO
Embedded systems often include bugs developers have a hard time to find. One common cause of such tricky bugs are stacks that grow beyond their dedicated memory area, thus causing unpredictable behavior and a malfunctioning system.
This is because the stack can overwrite important variable values, that thus inadvertently get the wrong value. Alternatively, a variable overwrite the stack, as the stack has expanded into the memory area dedicated to that variable. Upon the next function call return, the software crashes as it returns to the wrong location (the return address is stored on the overwritten stack and execution continues on a random location). Due to these reasons, stack related bugs often appear to be completely random, in most cases making them incredibly difficult to find.
If you use an RTOS running parallel tasks, these problems can multiply. Each task has its own stack, and with more tasks, you get more stacks that can cause stack related bugs. The stack depth analyzer in TrueSTUDIO Pro can help resolve such problems and help develop more robust systems. Read this blog post to learn more on analyzing the stack usage on Cortex-M systems developed with the GNU GCC compiler in TrueSTUDIO!
Migrating projects from one embedded IDE to another can be a time-consuming task. But an automated project importer can make the migration a breeze. No need to postpone the move due to the migration efforts anymore!
Moving an STM32 project from one IDE to another can include difficulties on many levels. But with the Atollic TrueSTUDIO project importer, STM32 projects can be imported from System Workbench for STM32 very easily indeed. Read this blog post to learn more!
The embedded systems market in general is transforming quickly, and the RTOS market more specifically is no different. Not too many years ago, only forward-thinking development teams with a certain level of skills and budget used real-time operating systems in their designs. But in this day and time, using an RTOS is pretty much a requirement if you want to use middleware stacks (TCP/IP and USB comes to mind, for example).
At the same time, the traditional RTOS vendors are under strong pressure from free and open alternatives. On large high-end systems, EmbeddedLinux is almost the norm these days. Since EmbeddedLinux is too large to run on smaller embedded systems, other alternatives are a better fit for Cortex-M developers. FreeRTOS, developed by Richard Barry, is the shining star in this segment. FreeRTOS have a huge user base, as it is free, stable and easy to use. But with RTOS power comes debug problems. How do you debug a system based on FreeRTOS?