Hard fault occur stm32 imprecise data access violation true studio.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2019-10-05 6:03 AM
my application code running some time inside mcu then suddenly hard fault occur so i debug my application found hard fault occur inside mcu how to solve this.
- Labels:
-
DEBUG
-
TrueSTUDIO
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2019-10-05 6:33 AM
Inspect the faulting code. There is likely a write instruction a few instructions earlier that is failing, thus the "imprecise" tag.
Up vote any posts that you find helpful, it shows what's working..
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2019-10-05 4:06 PM
See this document: Cortex M3/M4,M7 Faults tutorial
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2019-10-07 6:50 AM
problem solved i change interrupt priority high and low not same priority of both interrupt
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2021-12-04 3:15 AM
how can i change the priority in stm32cube ide?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2021-12-04 10:16 AM
In the .ioc (device configuration) view > System Core > NVIC. There are also tbas for the individual periperals.
hth
KnarfB
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2024-01-25 2:58 PM
I know I'm several years late, but could you elaborate on this solution? I am running an RTOS and I am getting the same error. I have enabled various ISR's (UART, ETH, GPIO, DAC etc) and they currently all have the same priority. What would you change based on this knowledge?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2024-01-25 3:09 PM - edited ‎2024-01-25 3:10 PM
Could be something entirely different.
Just diagnose WHY your situation is faulting rather than blindly shot-gunning.
Look at what's faulting, more likely to be bad pointer or misaligned write, or an insufficiently large stack.
Dump some useful / actionable data about what the system is objecting too.
https://github.com/cturvey/RandomNinjaChef/blob/main/KeilHardFault.c
NVIC has priorities and preemption levels and you can split how the bits are allocated.
Up vote any posts that you find helpful, it shows what's working..
