GNU MCU Eclipse is an open source project that includes a family of Eclipse plug-ins and tools for multi-platorm embedded ARM & RISC-V development, based on GNU toolchains. Related projects (µOS++, xPacks) are also supported via separate categories. All these projects are hosted on GitHub.
Hello, For the tutorial of Create a Blinky ARM test project, https://gnu-mcu-eclipse.github.io/tutorials/blinky-arm/ I've got error message " Cannot load image file 'C:\XXX\QEMU\2.8.0-3-20180523-0703\graphics\STM32F4-Discovery.jpg' " Does anyone knows what I'm missing??
I use the GNU-MCU-Eclipse plugin (on Windows). When I started using STM32CubeMX, I had to develop a Windows app to import the STM32CubeMX projects into Eclipse. The app works, but in the development process, I noticed that the XML coded Eclipse .cproject file contains a lot of 8, 9, 10 digit numerical strings. I know very little about XML, but…(Show moreShow less)
Hi, I have a problem when i download using eclipse & gdb, the problem does not occur using Seggers tools like Ozone. Basically even though the download speed is set to 10000Khz, something sets it to 1000Khz. Log file captured from JLinkGDBServerCL.exe attached. …(Show moreShow less)
I am very interested in using uOS++ as a wrapper for FreeRTOS. Is it possible to use the generic FreeRTOS zip and integrate that with CMSIS++? If so, do you have some developer notes published? Thanks Allen
this eCos test is the most extensive RTOS benchmark I know of: https://sourceware.org/viewvc/ecos/packages/kernel/current/tests/tm_basic.cxx?hideattic=0&revision=1.31&view=markup the output of this test looks like: https://doc.ecoscentric.com/ref/cortexm-stm32f429i-disco-port.html#tm_basic_stm32f429i_disco (eCos is one of the…
I just pushed the first version of a demo project that blinks the LEDs on a STM32F4DISCOVERY board. it is a proposal on how to organise projects using the µOS++ IIIe / CMSIS++ and also a proposal on how to integrate CubeMX initialisations. Since the XCDL utility is not yet available, the xpacks repository and the maintenance of the project…(Show moreShow less)
I have been mucking about in the startup files and linker scripts, decreasing the size of a project's flash memory footprint, and was able to make a serial downloader with less than 1 kbyte size. This was made using a new C project with the "Use system calls" choice of Freestanding. I have also used the choice of "POSIX (system calls implemented…(Show moreShow less)
I would copy/paste the build configuration and later try to change the toolchain. > eclipse and segger debug didn’t work well with clang. Has a this been fixed? with Eclipse it is tricky, but somehow it can be managed, I don't remember the details. but I definitely ran successful debug sessions with µOS++ apps on my mac, that's how I…
SEGGER does great tools, and they'll probably always have more tools than I can integrate into Eclipse... as for integration with µOS++, I started to write a plugin for the SEGGER GDB server, to show the µOS++ threads and possibly other objects separately durring debugging. it is functional, but there were some details to polish, it'll…
I've installed the GNU ARM Eclipse plugin and managed to get everything working with the STM32F407 discovery board. I've generated the blinky projects for both C and C++ and have run them successfully on the board using a J-Link debugger and a Mac. Nice work. I've looked through the documentation on the GNU ARM Eclipse github pages and the…(Show moreShow less)
right now I'm working on the xPacks project. the new xmake is mostly functional, it allows to build complex projects and tests. for now it may use either make or ninja for the actual build, but I also plan to write the internal builder, to run the build itself. xPacks are not part of the CMSIS Pack standard, and serve quite different purposes.…
Hey guys I wonder if it would be possible to allow QEMU to write to the .text section somehow just like as if we would emulate real microprocessor flash memory? Out of curiosity I've tried a naive *(__IO uint32_t*)Address = Data; but unfortunately that does not work, even if I mark the flash memory region as (xrw) inside the linker…(Show moreShow less)
So when I create a new C project using the Blink example, I change only the parameters for the MCU/Development board only to ensure I have the correct board. Then in the project properties, Settings section, I chose the STM32F411VE which is the development board MCU. After that, I use the guide for OpenOCD debug as the base and only change what is…(Show moreShow less)