STM32cubeide program uploads but doesn't run

[RogerMc]

I have successfully built and run 20 lessons in a tutorial series with a Nucleo STM32F767NI board but suddenly, on the 21st tutorial, programs would upload but not run.

I went back to the previous tutorial and then to the first tutorial, a simple blinking LED program, which also appeared to upload OK but refused to run even after pressing the board's reset button.

After much experimenting, including reinstalling STMCubeID, I installed STM packages in my Arduino IDE.

Using Arduino, a flashing LED program uploaded and ran without problem, so the board seems to be OK.

The problem may have occurred after I did an ST-Link upgrade. But this shouldn't be a problem as the Arduino code worked OK.

 

[RogerMc]

I can't get Edit Message to work.

I installed the GPIO_IOToggle GPIO IO Toggle example which builds, uploads and runs OK but my other projects still refuse to run.

[mƎALLEm]

Hello,

From your first statement it came to mind that in your 21st tutorial you handled boot address in option bytes or you modified the boot pin. But when you said a simple blinking example loaded with Arduino IDE is running well, this makes me perplex!

[RogerMc]

Thanks.

I am using STM32Cube IDE 1.15.0 on a Mac under OSX 14.4.1.

In addition to Arduino, under STM32Cube two STM32F767xx-Nucleo examples also work properly. Perhaps I accidentally, without knowing it, handled boot address in option bytes or modified the boot pin?

Could you tell me how to check boot address in option bytes and boot pin settings?

Also, there must be something different in the examples that enables them to work properly? But I haven't been able to spot the specific difference.

My tutorial lessons are bare metal lessons, unlike the examples.

 

[RogerMc]

Could this problem be related to an upgrade from STMCubeIDE version 13 to version 15?

[RogerMc]

I built a new project using version 15 and the original main.c but the problem remained.

I then found another project that runs OK.

The difference is that the OK project uses GPIOB whereas the ones that don't work use GPIOA.

[AScha.3]

Tip:

Always set in Cube (at first ! ) the debug connection you want to use enabled :

because this is on GPIOA :

So if you not do this, and use these pins for anything else - you stop any debug connection at this moment.

:)

 

[RogerMc]

Changing all occurrences  of GPIOA to GPIOB has all other problematic lessons working.

Thanks all for good advice.