It case of ST development boards (both EVAL, Discovery or NUCLEO series), there are on-board ST-link compatible JTAGs. To debug firmware, JTAG probe is required as well as remote dbg support for it. This could be done through the bootloader (USB, UART, I2C, SPI, OTA etc.) or through the hardware JTAG probe. In case of embedded, the program (firmware) should be downloaded into the target chip, and then run (in most cases the MCU is just reset after download). In case of desktop, the program is just run directly or under dbg for debugging.
#Segger embedded studio overlap text how to
The main difference between desktop and embedded programming is how to run or debug the program. Let’s use a Linux-based (Ubuntu 16.04) computer for this development. This is ARM Cortex M4+FPU MCU, 72MHz, 64(RAM)/512(ROM) kB of memory. Let’s try to program something for one of them with CLion.Ī good target platform is NUCLEO-F303RE – a development board for STM32f303RE MCU. Many of them are quite powerful and at the same time cheap and relatively easy-to-program. One of the most popular microcontrollers (MCU) nowadays is a huge family of ARM Cortex-M compatible processors, based on the 16/32bit ARM kernels, but made by different companies. Embedded programming here means no operating systems, clipboards or other processes. Although CLion in its current state is not targeted at embedded development, it’s still possible to use it for this purpose. IntroductionĬLion is a relatively new IDE for C/C++, based on very popular IntelliJ Platform, and hopefully it inherits most of the nice features of IntelliJ IDEA like code highlighting, autocompletion, refactoring, and analysis. DIY Electronics and Embedded Programming Enthusiast.
0 kommentar(er)
