Using NUCLEO-G071RB evaluation board via embedded ST-Link.
Started with a new project from scratch.
This is my main():
#include <cmsis_os.h> // ARM::CMSIS:RTOS:Keil RTX int main (void) { osKernelInitialize(); osKernelStart(); osDelay(osWaitForever); while (1) ; }
After some time debugger crashes.
Uncommenting RTX related calls, the while(1) runs ok.
What is such fundamental wrong here ?CMSIS core is 5.3.0, RTX is 4.82.0 , device stratup is 1.3.0, device is STM32G071RBTx, DFP is 1.2.0.
Some additional action...
Installed V5.27 (32k limit) on first Workstation (WS1). added G0 support for my STM32G071: Debugger crashes.Changed Nucleo board from STM32G071 to STM32F091, added F0 support: Crashes.
Went with STM32F091 to another workstation (WS2).Unfortunately three params change: V5.27 -> V5.24a, Win 7 Prof -> Win 10 Prof and PC hardware.STM32F091 runs without error for more than one hour...but not allowed to install V5.28 on this WS2...
Back to WS1. Installed V5.24a (32k limit). Added F0 and G0 support.Debugger crashes with both Nucleo boards.
Back to V5.28 with Nucleo STM32G071 on WS1.Oscilloscope at Pins CN6.2 (+3.3V) and CN6.7 (GND), trigger at 3.00V, falling edge.Debugger crashes without trigger.Next:Oscilloscope at Pins JP2.7 (+5V_USB_CHG) and CN6.7 (GND), trigger at 4.72V, falling edge.Debugger crashes without trigger.Still running...
Oscilloscope at Pins JP2.7 (+5V_USB_CHG) and CN6.7 (GND), trigger at 4.72V, falling edge.Debugger crashes without trigger (no more running...).Add. info: In case of crash, Nucleo COM LED (LD1) has red and green LED on..
Back to first workstation, with V5.28.Managed to catch USB communicationwith USB analyser (ITIC 1480A) at such a crash.Stopped code execution for some long time (~10 minutes), then pressed F5 to continue, then immediately got the crash (Cannot access...).See attached PDF file.STM32G071 DbgStop-F5-Cannot-Stop.pdf