winIDEA HelpMicrochip ATSAML1x
Chip Erase removes security on the chip (if not permanently secured). Script is executed manually. In cases where device is secured or possibly a malfunctioning application is loaded on the device the Chip Erase command allow to erase memories of the device and provide secure transitions between the different Debug Access Levels.
Devices are:
•SAM L10 - Chip Erase command does not require a key.
•SAM L11 - Chip Erase commands are protected with keys (CEKEYx) defined in the NVM BOCOR row.
Depending on security configuration the keys can be automatically read from FLASH. If security prevents reading the keys from FLASH the user must enter correct key as a parameter of the script.
|
If the key is set at “All 0s”, the corresponding Chip Erase command is disabled and it will be impossible for the debugger to use it. If both the ChipErase_ALL (CE2) key is set at "All 0s" and BOCOR.BCWEN=0, full chip erase is permanently disabled. |
 1. Perform Debug / Prepare to Attach. |
 2. Perform Hardware / Scripts / Chip Erase. |
|
To execute Chip Erase script with custom keys you need to run ATSAML1x_ChipErase.cpp (located in %LocalAppData%\iSYSTEM\winIDEA\SFR\ARM) with key values as parameters. See EVE Scripts Help for instruction on how to run EVE script from a command line. |
RAM Execute Protection removal script
RAM Execute protection is automatically erased during debug session initialization. RAM execute enable (to be able to run application from RAM) is achieved by modifying RXN bit in User Row bytes.
ATSAML11 can have execution from RAM and Data Flash prevented by an authorization logic on the device. When establishing debug session the connection script checks for execution authorization and alerts the user. When execution from RAM is prevented the script will automatically attempt to enable execution. This will allow the user to run and execute application from RAM.
No action is required by user. Script enables RAM execution authorization automatically.
