17-09-2024, 05:53 PM
I am working with a STM32H563ZI currently.
This device also has a high-cycle flash.
The memory region for the high-cycle flash is located from 0x09000000 and can only be accessed by 16-bit or by 32-bit.
8-bit reads to this addresses are not allowed.
Now the problem is, I cant examine this memory via eblink. I tested the exact same configuration with eblink and with stlink-gdbserver.
eblink:
stlink-gdbserver:
As you can see, stlink-gdbserver is able to examine the memory as long as I dont make it read only one byte.
But eblink is not able to examine it at all. I suspect eblink treats every memory access as byte reads?
Is this the intended behavior?
This is not an important bug to me, I can fall back on stlink-gdbserver, I just stumbled over it.
This device also has a high-cycle flash.
The memory region for the high-cycle flash is located from 0x09000000 and can only be accessed by 16-bit or by 32-bit.
8-bit reads to this addresses are not allowed.
Now the problem is, I cant examine this memory via eblink. I tested the exact same configuration with eblink and with stlink-gdbserver.
eblink:
Code:
x/1xb 0x09000000
0x9000000:
Cannot access memory at address 0x9000000
x/1xh 0x09000000
0x9000000:
Cannot access memory at address 0x9000000
x/1xw 0x09000000
0x9000000:
Cannot access memory at address 0x9000000
x/1xg 0x09000000
0x9000000:
Cannot access memory at address 0x9000000
stlink-gdbserver:
Code:
x/1xb 0x09000000
0x9000000:
Cannot access memory at address 0x9000000
x/1xh 0x09000000
0x9000000: 0x1e0f
x/1xw 0x09000000
0x9000000: 0x3c2d1e0f
x/1xg 0x09000000
0x9000000: 0x78695a4b3c2d1e0f
As you can see, stlink-gdbserver is able to examine the memory as long as I dont make it read only one byte.
But eblink is not able to examine it at all. I suspect eblink treats every memory access as byte reads?
Is this the intended behavior?
This is not an important bug to me, I can fall back on stlink-gdbserver, I just stumbled over it.