cancel
Showing results for 
Search instead for 
Did you mean: 

LED won't toggle

emb_rf
Associate III

I am trying to toggle one of the LED lights of STM32 NUCLEO-L552ZE-Q board. I am working with the latest version of STM32CubeIDE 1.16.1. The steps I followed are given in the picture. However, I find this error when I debugg:

set *(int *)0xE000EDFC=*(int *)0xE000EDFC|0xFF0

Program received signal SIGINT, Interrupt.

0x080006bc in HAL_IncTick () at ../Drivers/STM32L5xx_HAL_Driver/Src/stm32l5xx_hal.c:303

303 }

 

Also, the pics show more. I tried many things to fix this issue but couldn't.

Has someone face the same issue and how did you solve it? Any help is highly appreciated.

23 REPLIES 23

Upload your IOC file

If smoke escapes your device, put the smoke back in. It'll still work as a conversation piece. If you find my answers useful, click the Accept as Solution button so that way others can see the solution.
Karl Yamashita
Lead III

The IOC file in your project

If smoke escapes your device, put the smoke back in. It'll still work as a conversation piece. If you find my answers useful, click the Accept as Solution button so that way others can see the solution.
 
Karl Yamashita
Lead III

Does the LED ever blink?

Or just errors during debugging?

 

If smoke escapes your device, put the smoke back in. It'll still work as a conversation piece. If you find my answers useful, click the Accept as Solution button so that way others can see the solution.

Just errors during debugging. 

None of these blink.

emb_rf_0-1727638768178.png

 

Karl Yamashita
Lead III

Not sure if it'll make a difference but you don't have debugging enabled.

KarlYamashita_0-1727639225043.png

 

I've tried on another Nucleo with Debug off and I don't run into errors. I have a counter variable that still counts up and updates in the Expressions. So that is why i say it may not make a difference if you do enable it.

If smoke escapes your device, put the smoke back in. It'll still work as a conversation piece. If you find my answers useful, click the Accept as Solution button so that way others can see the solution.

thank you, yes, I also have tried that, but no difference. Still I get the same problem. 

I think that might be a problem with the settings of my STM32Cube 1.16.1, but actually I did as advised in the internet everything.

Karl Yamashita
Lead III

I have a lot of Nucleo boards but unfortunately i don't have the one your have. Just out of curiosity, place a breakpoint on SystemClock_Config and MX_GPIO_Init and see if you can get past HAL_Init and SystemClock_Config functions without any errors?

If smoke escapes your device, put the smoke back in. It'll still work as a conversation piece. If you find my answers useful, click the Accept as Solution button so that way others can see the solution.

No, unfortunately, it gives the same error.

emb_rf_0-1727642310086.png

emb_rf_1-1727642352790.png