Error while debug

Rituraj · ‎2024-08-23

WHile debugging for a custom board this is what I am facing Break at address "0x1fff4080" with no debug information available, or outside of program code.

This is the code that I am trying to run . What is the reason for this error and how it can be curated . I have already verified the most common reason i.e. BOOT0 pin which has been pulled low.

I have attached the main.c file to this post

TDK · ‎2024-08-27

In your system file, uncomment this line:

/* #define USER_VECT_TAB_ADDRESS */

so it looks like this:


#define USER_VECT_TAB_ADDRESS

Register values can be viewed when debugging in the SFRs window. Window -> Show View -> SFRs or by adding them as expressions. For example, when your code is paused, add "SCB->VTOR" as an expression.

If you feel a post has answered your question, please click "Accept as Solution".

View solution in original post

Andrew Neil · ‎2024-08-23

you need to provide more information - please see the posting tips:

https://community.st.com/t5/community-guidelines/how-to-write-your-question-to-maximize-your-chances-to-find-a/ta-p/575228

@Rituraj wrote:
WHile debugging for a custom board this is what I am facing Break at address "0x1fff4080" with no debug information available

When/where, exactly, does this occur?

A complex system that works is invariably found to have evolved from a simple system that worked.
A complex system designed from scratch never works and cannot be patched up to make it work.

Rituraj · ‎2024-08-23

It starts as soon as I enter superwhile at time of debugging. I have already attached the main.c file

TDK · ‎2024-08-23

Looks like it's in the bootloader.

Is BOOT0 tied low?

If you feel a post has answered your question, please click "Accept as Solution".

Rituraj · ‎2024-08-23

Yes it has been tied low via a 10k resistor

TDK · ‎2024-08-23

Perhaps the vector table isn't being set. Check that SCB->VTOR points to 0x08000000. If not, edit system_*.c and uncomment the define for USER_VECT_TAB_ADDRESS.

Can also check VECTACTIVE field in SCB->ICSR to see if the chip is currently in an interrupt. If it's not in the bootloader.

Can also check AN2606 for other reasons it may be in the bootloader. Option byte settings, for example. Shouldn't be relevant here for a new chip.

If you feel a post has answered your question, please click "Accept as Solution".

Rituraj · ‎2024-08-26

#define SCB_ICSR_VECTACTIVE_Pos 0U /*!< SCB ICSR: VECTACTIVE Position */

#define SCB_ICSR_VECTACTIVE_Msk (0x1FFUL /*<< SCB_ICSR_VECTACTIVE_Pos*/) /*!< SCB ICSR: VECTACTIVE Mask */

This is what I found looking for VECACTIVE.
I also modified the code to be SCB->VTOR points to 0x08000000 but could not solve.

Rituraj · ‎2024-08-26

While debugging everytime I cliick on step over I get this on console ' Error: Failed to set more breakpoints".
I also commented the part for USART Interrupt so if there is an issue due to interrupt it could be curated but after I commented it I am still getting same issue, just the register changes

Break at address "0x1fff4cf8" with no debug information available, or outside of program code.

Rituraj · ‎2024-08-26

I checked the document and tried to apply it . I use this clock configuration

as I looked into this part of the document AN2606

The error is still the same .

Break at address "0x1fff40a2" with no debug information available, or outside of program code.

Rituraj · ‎2024-08-27

This is a link to the complete project , I am really unable to undersatnd whats wrong as I can not even debug. I have already shared what I have tried . Looking for some immediate guidance .

Here is the link PROJECT