Did ST break SysTick in the last update? It used to work. Now it crashes because I think the interrupt vector is not set. Is this one of those known errors? How do I fix it?

[KiptonM]

When the SysTick interrupt fires the debugger quits.

I cannot figure out where the NVIC_SetVector statement is for the SysTick. I think it is not set. But I can not find the vector table in the debugger to know for sure.

This used to work, But when I updated to the 1.10.1 IDE and 6.6.1-RC2 Build.20220706-1420. It crashes when the systick interrupt happens.

I am using the STM32G051K8T

[KiptonM]

Could it be it booted into the system because I am running the debugger?

[Piranha]

That CubeProgrammer description of nBOOT0 and nBOOT1 options is a nonsense. Again a blind trust without checking the real thing - reference manual...

Look at the RM0444 Rev 5, 2.5 Boot configuration, Table 8. Boot modes.

@Houda GHABRI​ 

[KiptonM]

Thanks for the pointer. And yes I should be wary of ST software.

Looking at Table 8 the 4th line is a way to get to Main Flash Memory.

nBOOT_SEL bit needs to be 1

nBOOT0 bit needs to be 1

nBOOT1 bit does not matter

BOOT0 pin does not matter.

I thought that is what I started with before I started changing the fuses!

It must not have been, because the PC Changed and the test code works.

Download verified successfully 

 ------ Switching context ----- 

COM frequency = 4000 kHz

Target connection mode: Under reset

Reading ROM table for AP 0 @0xf0000fd0

Hardware watchpoint supported by the target 

ST-LINK Firmware version : V2J40S7

Device ID: 0x456

PC: 0x8000430

And it works on my code with all the setup files commented out

And it works on my full code.

Thanks everyone for the help. This one is solved.

[KiptonM]

I also have to thank KnarfB for the pointer to the fuses. I have no idea how they got changed. I had to load the programmer into my computer to change them. I looked at fuses a long time ago, but have not changed them in a long time.

Unfortunately I can only have 1 best answer. And that is the one that fixed the problem.

[Piranha]

Probably related to this topic:

https://community.st.com/s/question/0D53W00001Uz40QSAR/what-causes-halflashobunlock-to-call-hardfaulthandlerit-calls-writeregflashoptkeyr-flashoptkey1-and-jumps-directly-to-hardfaulthandler

Read my latest post there!