New
Hi
Using Jlink probe with Visual Studio results in having inconsistent memory information during debug.
The jlink driver is always returning data from the cache on a read memory command. Not the real memory content from the device.
So it is impossible to use the jlink to debug issue related to flash memory content.
A read memory command should always access the real memory content and not use the driver cache whatever the memory type is.
Jlink driver version 8.10c.
Regards
Using Jlink probe with Visual Studio results in having inconsistent memory information during debug.
The jlink driver is always returning data from the cache on a read memory command. Not the real memory content from the device.
So it is impossible to use the jlink to debug issue related to flash memory content.
A read memory command should always access the real memory content and not use the driver cache whatever the memory type is.
Jlink driver version 8.10c.
Regards