fjouen Community Member
- Member since May 31st 2024
- Last Activity
- , Reading thread Jlink flash programming interface does not take memory changes from CPU/code into account
This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.
-
fjouen -
Replied to the thread Jlink flash programming interface does not take memory changes from CPU/code into account.
PostAdditionnal information : The exception occurs for all exit conditions so for "step into" too. Exceptions occurs when attempting to execute flash loader code that should be loaded into RAM memory. mcause register indicates an illegal instruction at… -
fjouen -
Replied to the thread Jlink flash programming interface does not take memory changes from CPU/code into account.
PostHello Simon, I've just tried the new version. It does not work on my side. When using the memory viewer to modify the memory, it looks the flash loader is not loaded into RAM memory before calling it, resulting in having an illegal instruction error with… -
fjouen -
Replied to the thread Jlink flash programming interface does not take memory changes from CPU/code into account.
PostHi Alex, Any news about the solution ? Regards, Fred -
fjouen -
Replied to the thread Jlink flash programming interface does not take memory changes from CPU/code into account.
PostMore information about the issue: When using the memory viewer of embedded studio to modify some bytes of the memory, only modified characters are updated into the cache used for flashing. That is visible in the jlink control panel and llink log… -
fjouen -
Posted the thread Jlink flash programming interface does not take memory changes from CPU/code into account.
ThreadWhen Jlink performs flash updates, it looks that its cache is not up-to-date if the memory content has been modified by code execution. It results in having wrong memory content at the end. My use is case is the following : My application is…