Why cannot properly see opcodes on memory browser ?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2024-06-08 12:58 PM - edited ‎2024-06-08 4:05 PM
I can see the addresses when I hover over them, but I can't see the opcodes. Is there a setting to fix this or is it broken?
Starting server with the following options:
Persistent Mode : Disabled
Logging Level : 1
Listen Port Number : 61234
Status Refresh Delay : 15s
Verbose Mode : Disabled
SWD Debug : Enabled
InitWhile : Enabled
Waiting for debugger connection...
Debugger connected
Waiting for debugger connection...
Debugger connected
Waiting for debugger connection...
-------------------------------------------------------------------
STM32CubeProgrammer v2.16.0
-------------------------------------------------------------------
Log output file: C:\Users\Shichaz\AppData\Local\Temp\STM32CubeProgrammer_a18664.log
ST-LINK SN : 0671FF575377524867053453
ST-LINK FW : V2J45M30
Board : STM32F4DISCOVERY
Voltage : 2.91V
SWD freq : 4000 KHz
Connect mode: Under Reset
Reset mode : Hardware reset
Device ID : 0x413
Revision ID : Rev Y
Device name : STM32F405xx/F407xx/F415xx/F417xx
Flash size : 1 MBytes
Start Address : 8000000
Device type : MCU
Device CPU : Cortex-M4
BL Version : 0x91
Memory Programming ...
Opening and parsing file: ST-LINK_GDB_server_a18664.srec
File : ST-LINK_GDB_server_a18664.srec
Size : 4.93 KB
Address : 0x08000000
Erasing memory corresponding to segment 0:
Erasing internal memory sector 0
Download in Progress:
File download complete
Time elapsed during download operation: 00:00:00.372
Verifying ...
Download verified successfully
Solved! Go to Solution.
- Labels:
-
STM32CubeIDE
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2024-06-09 12:28 AM
Just to mention : memory can only be read, when debug stop core, at a breakpoint or click "suspend" .
While running, only last readed values or "????" shown.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2024-06-08 2:22 PM
Which STM32 ?
Erased FLASH, or content expected?
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
‎2024-06-08 2:32 PM
I am using the STM32F407-DISC and trying to see the content of memory. I am a newbie so sorry for missing info.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2024-06-08 3:25 PM
Suggests this is a connectivity issue with the ST-LINK/V2 on the STM32F407-DISCO, make sure it has most current firmware. Check it is readable in STM32 Cube Programmer
The F4 doesn't have ECC (error correction / checking) so reading blank memory shouldn't fault, which could be the case for H7 parts, say. Those devices might reflect unreadable memory with '????' displays.
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
‎2024-06-08 3:41 PM - edited ‎2024-06-08 3:57 PM
Thanks a lot. After your suggestion, I tried a different USB port on my computer. It works now.
Edit: It returned to the "????????" view. I tried all the USB ports of the computer.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2024-06-09 12:28 AM
Just to mention : memory can only be read, when debug stop core, at a breakpoint or click "suspend" .
While running, only last readed values or "????" shown.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2024-06-09 4:15 AM
Yes, I found out later that I was trying to read without clicking "suspend" (embarrassing :d). Thanks for the answers.
