LPC55Sxx Debug Authentication
The LPC55Sxx family of devices includes many possibilities to configure the debug port and a possibility to debug the firmware. The fundamental principles of debugging, which require access to the system state and system information, conflict with the principles of security, which require the restriction of access to assets. Thus, many products disable the debug access completely before deploying the product. This causes challenges for product design teams to do a proper Return Material Analysis (RMA). To address these challenges, the LPC55Sxx offers the Debug Authentication Protocol (DAP) as a mechanism to authenticate the debugger (an external entity) which has the credentials approved by the product manufacturer before granting the debug access to the device. Figure 1 shows an example usage of the debug authentication. The OEM is the owner of the root key pairs. The root key hash is programmed into the device during manufacturing. When the end customer faces an issue, the device is shipped to a repair center. The field technician can send a request to the OEM to provide the Debug Credential certificate (DC), which is signed by a private root key. The field technician uses this DC to provide debug access.
LPC55Sxx 、 LPC55Sxx family 、 LPC55S6x 、 LPC55S2x 、 LPC552x 、 LPC55xx 、 LPC55S69 、 LPC55S1x 、 LPC55S0x |
|
|
|
|
|
Application note & Design Guide |
|
|
|
Please see the document for details |
|
|
|
|
|
|
|
English Chinese Chinese and English Japanese |
|
06 October 2021 |
|
Rev. 1 |
|
AN13037 |
|
850 KB |
- +1 Like
- Add to Favorites
Recommend
All reproduced articles on this site are for the purpose of conveying more information and clearly indicate the source. If media or individuals who do not want to be reproduced can contact us, which will be deleted.