_frank_ Community Member

Not sure if this is the right place, because responsibilities seem somewhat mixed. Anyway, I a m having trouble creating proper output of the SPI peripheral on a stm32C031C6 - the one on the ST Nucleo C031 (MB1717B). I am configuring the SPI for 8-bit…

The problems seems to be gone now. What I have done was the usual update routine on a Ubuntu/Mint PC (apt-get update, apt-get upgrade, apt-get dist-upgrade). I can see all avaiable packages now, and install them from the manager. Most probably was really…

As far as I understand it, Rowley/Crossworks only shares the GUI and some tool interfaces with SES (like the package manager GUI). The actual toolchain (compiler, assember, linker) are different, and package format (and thus packages) are different. As a…

I didn't try an "external built" project yet, but I don't quite understand the purpose. If you build it with a make file inside your IDE and want to debug it afterwards in the IDE, you could do a normal "C/C++" project. I view it as an option for…

I recently reanimated an older laptop, installing Linux Mint Mate 21.1 (the 64-bit version). One of the first applications I installed was the latest SES version (V7.12a), which went smoothly as well. Only the package manager fails to download any…

As Nino posted, sleep modes and wake-up are a known source of trouble for debugging. Though this seems not to apply in your case. Quote from Eqqman: “Everything craps out at the function prologue assembly for HAL_UART_Transmit() : ldr r0, =0x200007D8…

Now this was a pure assumption on my side. My next step would be to step into the "offending" code on instruction level, and watch relevant port and RCC registers. The latter one's are where the power to the individual peripherals are enabled. In my…

Reading up on openOCD and GDB, I (hopefully) understand that point a bit better. Up to now, I usually preferred native support within the IDE/Debugger, or readily configured GDB server setups (like the one's Eclipse-based IDEs come with). And checking…

Check your exact target MCU, and the datasheet. I had a similiar effect when I accidentally tried to reconfigure the SWD pins of the target. The debugger/JLink "screwed up" immediately.

> Completely understandable. We will add native support to our wishlist but no promises. > You could try openOCD/pyOCD. Both support a big variety of different debug probes and can be used in Embedded Studio via the universal GDB interface. > It might…

Thanks for the quick response. And to respond in reverse order ... > You can change the default new project folder under: Tools->Options->New Project Directory This is exactly what I needed. I overlooked this property until now - but to my defense, the…

I understood that SES basically supports only the J-Link debugger, which is ok for. Though I have some questions related to J-Link conversion firmware for other debug pods. The ICDI (from TI, e.g. used on their Launchpad boards) is not and probably will…

Ok, thank you for the clarification.

I'd like to add some information, but the original thread is closed now ([Solved] Bug report: STM32F3xx CPU support package has incorrect memory map). Checking the current package status, this package installed is at version 2.04, and no update…

> Unfortunately the RAM size for some of the subfamilies was set incorrectly, meaning larger than actually available on the device. > Because of this memory addresses were used which are not actually available on the device. > As the stack is usually…

There seem to be more issues with the STM32F3xx support package. First I tried to create an application for the F3 discovery (F303VCT6), using the provided startup and vector files, and replacing everything else with ported SPL code. This application…

I would still check the documentation/tutorials for Ozone, it needs to derive information about Flash sector locations and sizes of the target MCU from somewhere. And the flashing modus, depending on the ELF contents. I use the debugger integrated in…

Which sounds more like a problem with the debugger settings. Perhaps your project contains a "mass erase" setting for the flashing process, or a script the toolchain/debugger uses. By the way, are you sure the bootloader and the application are not…

Quote from nibbly78: “Eclipse does not know about the bootloader either... Eclipse is settup to only call "make clean" and "make app_debug" (so no access to compiler/linker etc to my knowledge) ” This is not related. "Make clean" only affects the…