We tested the address 0x40D (FOPT Register) write 0x7F, after address 0x400 can not read
If 0xFF is written at address 0x40D (FOPT Register), it can be read correctly.
Kindly give us your advice. Thank you.
um, I'm lost a little bit. What you mean by after address 0x400 can not read?
In my case - there is 7F in FOPT, and memory can be read without any issue:
I programmed the hex file (address 0x40D write 0x7F), read back and found that address after 0x400 can not be read correctly.
But programming the same hex file (changing address 0x40D to write 0xFF or 0xDF) can be read correctly,
what software and debug probe are you using?
We are programmer manufacturer.
Currently encountered problems in the development of FS32K144 programming process，that is the picture of our software and we used J-Link in debug and verify.
I tried the same scenario with Segger J-Link - SEGGER J-Link GDB Server V6.42a - and there is no issue with memory read when FOPT contains 0x7F. There must be some issue with your SW.
I think that our software must set registers during initialization and avoid problems.
Can you help us with suggestions?
to be honest, I'm not familiar with debugger low level communication. But you can compare - for example - register content for PE micro (or segger) debug session with your debug session and try to find differences.
Retrieving data ...