Error while debug
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2024-08-23 4:02 AM - edited ‎2024-08-23 4:06 AM
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
Solved! Go to Solution.
- Labels:
-
Bug-report
-
STM32G4 Series
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2024-08-27 6:03 AM
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2024-08-23 4:21 AM
you need to provide more information - please see the posting tips:
@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 designed from scratch never works and cannot be patched up to make it work.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2024-08-23 4:47 AM
It starts as soon as I enter superwhile at time of debugging. I have already attached the main.c file
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2024-08-23 6:24 AM
Looks like it's in the bootloader.
Is BOOT0 tied low?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2024-08-23 7:49 AM
Yes it has been tied low via a 10k resistor
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2024-08-23 8:19 AM
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2024-08-26 10:12 PM
#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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2024-08-26 10:50 PM - last edited on ‎2024-08-27 2:00 AM by Andrew Neil
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2024-08-26 11:45 PM
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2024-08-27 2:15 AM
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
