ST recently released STM32CubeProgrammer, a software tool allowing users to flash STM32 devices through the SWD/JTAG debug interface and via the UAR/USB bootloader interface. STM32CubeProgrammer can be integrated with Atollic TrueSTUDIO. This is how and why!
We made a promise in December 2017 to release a TrueSTUDIO for STM32 in early 2018. Today we are happy to announce that, after weeks of refactoring efforts, we have released a free TrueSTUDIO for STM32 tool with the full Pro feature set unlocked to all STM32 users!
Atollic TrueSTUDIO Pro (v.8.1.0 and later version) have extended kernel-aware debugging support by allowing to visualise FreeRTOS run-time statistics. FreeRTOS can optionally be configured to collect information about each tasks execution time. In Atollic TrueSTUDIO the execution time for each task can be visualised as the percentage of the total execution time for the application using the kernel-aware debug views for FreeRTOS.
In this article we describe how to make the run-time statistics work in Atollic TrueSTUDIO Pro 8.1.0.
Iot devices are being trusted to handle more critical data all the time, making it vital for the data not to become corrupted. This has increased the need for reliable file systems that protect data in the case of unexpected power loss, which is common in these devices.
Embedded system complexity has reached the point where many systems require a real-time operating system. In this free webinar, attendees will become familiar with the design methodologies necessary to properly schedule tasks in addition to understanding when and where to use mutexes, semaphores and message queues.
Important concepts such as preventing priority inversions, deadlock and thread starvation will be examined. The webinar will provide hands-on demonstrations using the STMicrolectronics STM32F7 Nucleo Board which uses an ARM Cortex-M7 processor with the Atollic TrueSTUDIO toolchain. Learn more!
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.
Have you heard about the ITRON (aka microITRON) project in Japan? ITRON is a Japanese open standard for real-time operating systems. The project started back in 1984 and was initiated by Ken Sakamura.
TOPPERS (Toyohashi Open Platform for Embedded Real-time Systems) is one flavour of ITRON RTOSes. It is open-source, and the documentaiton is released as open educational content.
Atollic TrueSTUDIO supports kernel-aware debugging of TOPPERS. The Atollic appointed distributor in Japan, AI Corporation, has written guides and created example projects, simplifying the getting started process with TOPPERS.
Update: This joint webinar with ST and Atollic can now be streamed from our website
Do you have any idea about how many questions the Atollic support team get on a weekly basis on the topic of using STM32CubeMX and Atollic TrueSTUDIO? ... well, neither do I, but the answer is somewhere between quite many and too many.
You don't know what STM32CubeMX is? Click here to get an overview! Do you want to learn more?
Atollic and ST are co-hosting a webinar on how to use STM32CubeMX and Atollic TrueSTUDIO...
How does a Atollic TrueSTUDIO user debug an mbed device equipped with an on-board OpenSDA debugger? There are several ways and it depends on which firmware that is loaded on to the OpenSDA debugger.
Three widely used OpenSDA firmware choices are: CMSIS-DAP, P&E Micro, SEGGER
This blog article will provide an instruction on getting started with OpenSDA/CMSIS-DAP using TrueSTUDIO and the open-source PyOCD GDB-server.
How much do you know about the editing capabilities available in Atollic TrueSTUDIO? Are you the type of user who uses the menu and toolbars or do you prefer using keyboard shortcuts?
Have you many times thought about setting up your own version control and issue management server but have not yet found enough time? Getting these services up and running on a server is probably not your core competency. And if you are a consultant, setting up the server environment is not something you can easily charge your customer for. Yet not having these tools available will probably effect your product time-to-market, system quality and the overall project costs.
This is a dilemma for start-up companies, individual consultants, small companies, or anyone who does not have an IT-department supporting the project with serverconfigurations.
In this blog-post we are going to teach you how to get your subversion and trac server stack setup and running in less than one hour. The stack is running inside a virtualised environment simplifying backups and enabling it to run on many different host operating systems.
All components are open-source and free to use for anyone. This setup is going to run in a virtualized environment using Virtualbox and Bitnami stacks. As you probably are aware of, Atollic TrueSTUDIO integrates both version control clients and issue management clients. So let's make all these tools play together.
Atollic technical support team are often asked how to make Atollic TrueSTUDIO connect to a running target in order to troubleshoot a crashed CPU. This article shows, step-by-step, how to connect to a running target without restting it.
This approach is useful when trying to resolve problems which occur at rare occasions, often after several days of running your embedded application, by connecting Atollic TrueSTUDIO debugger via JTAG/SWD the embedded target using a SEGGER J-Link.
Finding the root cause of the problem in case of a CPU crash is further simplified by learning how to use the Fault Analyzer view. White paper and Video tutorial is provided!