J-Link RAM initialization: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
==J-Link Working RAM== | ==J-Link Working RAM== | ||
For most devices the working RAM of the J-Link is not equivalent to the whole RAM of the Target. <br> | |||
J-Link is designed to work with the "default" RAM that is enabled after a reset to keep the MCU in as close to a virgin state as possible. <br> | |||
The reason for this is that enabling additional RAM could cause issues for customers who might not want it activated, for example, to optimize energy efficiency. <br> | |||
Therefore, the responsibility of enabling additional RAM lies with the customer, depending on their specific requirements. | |||
==Initialize additional RAM areas== | ==Initialize additional RAM areas== | ||
It is the user's responsibility to initialize additional RAM areas when needed. <br> | It is the user's responsibility to initialize additional RAM areas when needed. <br> | ||
Examples can be found [[J-Link_script_files#Init_ECC_work_RAM | here]]. | Examples can be found [[J-Link_script_files#Init_ECC_work_RAM | here]]. | ||
Latest revision as of 11:56, 2 January 2025
J-Link Working RAM
For most devices the working RAM of the J-Link is not equivalent to the whole RAM of the Target.
J-Link is designed to work with the "default" RAM that is enabled after a reset to keep the MCU in as close to a virgin state as possible.
The reason for this is that enabling additional RAM could cause issues for customers who might not want it activated, for example, to optimize energy efficiency.
Therefore, the responsibility of enabling additional RAM lies with the customer, depending on their specific requirements.
Initialize additional RAM areas
It is the user's responsibility to initialize additional RAM areas when needed.
Examples can be found here.