ChibiOS Free Embedded RTOS

Giovanni wrote:Hi,

There is a single exception routine (_unhandled_exception) for all exceptions, you need to declare your own handler, see vectors.c for names.

void name(void) {
}

Alternatively you can inspect the SPR register (Status), the lower bits are the vector number.

Giovanni

i dont see what good this will do if the debugger as already lost control and cant read anything ???

I see there is already a _unhandled_exception handler with a while(1) loop, so if this was catching in there and if the debugger was working it would loop in the loop.

Once the debugger as lost control the only way to get the MCU back under control is to use ST-Link Flasher and reset / Halt under reset and then erase the flash

So it is not an exception, the PLL settings are simply wrong and the CPU crashes, maybe for overclocking.

You need to inspect the RCC registers before the PLL is enabled and see if the content is correct and expected.

Giovanni

Giovanni wrote:So it is not an exception, the PLL settings are simply wrong and the CPU crashes, maybe for overclocking.

You need to inspect the RCC registers before the PLL is enabled and see if the content is correct and expected.

Giovanni

This is what we have...... the only ive got is what refence manual to use to check, its got F030CCT6 on it but the silicon inside in F091, its a complete mess lol



so you can see we have x12 mulitpler, but if the incoming clock is 8Mhz that means we will overclock at 96Mhz. But does the silicon have a div2 in hardware ??