Strange problem when using Keil and debugging STM32H747 Discovery. Concerning RAM address
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2019-07-27 6:07 PM
Hi, there, I am not sure this is the right place to ask if it's concerning IDE.
Just got my new STM32H747 Discovery kit, running CubeMX examples,
All running well, except for debugging:
(I am using MDK Keil (V5.27 / V5.28) and on-board STLink V3)
I found that while debugging, if the data memory is outside DTCM (0x20000000~0x2001FFFF), Keil's watch window and memory window
just don't update as program executes.
That is, I can still see the data variable address in the watch window
but the data just don't update as the code execues.
So far I've seen that if data are in AXI SRAM or SRAM4, the data just don't update.
I am not sure if this is ST-Link setting problems or Keil IDE problem.
I would like to know if anyone faces the same issues,
if so , is there any solution?!
Thanks for reading this post, :)
Zt.
Solved! Go to Solution.
- Labels:
-
Keil
-
RAM
-
STM32H7 series
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2019-07-27 7:19 PM
Okay, I am so silly, I need to turn off the cache. :grinning_face_with_sweat:
The default cache policy for SRAM is write-back, so the up-to-date data is still in cache not in the SRAM. Same for other cached data.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2019-07-27 7:19 PM
Okay, I am so silly, I need to turn off the cache. :grinning_face_with_sweat:
The default cache policy for SRAM is write-back, so the up-to-date data is still in cache not in the SRAM. Same for other cached data.
