AnsweredAssumed Answered

JTAG ICE stop.

Question asked by Takashi Takahashi on Jun 23, 2015
Latest reply on Sep 13, 2016 by niranjanbc

Hi community.

 

Our costomer developing Use the BSP of "imx_3.10.53_1.1.0_ga" .
When it is activated by connecting the J-TAG ICE (PARTNER-Jet), and will stop at always the same place during the startup of the Kernel.

platform caam_sm: restored 192-bit black key:
platform caam_sm: [0000] 26 60 31 8e d0 79 45 22
platform caam_sm: [0008] 06 f6 69 1f d6 7c 33 e5
platform caam_sm: [0016] 4c 7e 75 3e 45 bd 9a 40
platform caam_sm: [0024] ab eb 2b cd 04 92 4f cf
platform caam_sm: restored 256-bit black key:
platform caam_sm: [0000] 0a 96 77 6a 38 0c a1 2e
platform caam_sm: [0008] bd 99 ea 54 32 aa 51 75
platform caam_sm: [0016] 76 c9 27 41 9d ee 80 80
platform caam_sm: [0024] 01 77 c6 ae 2a 86 1a 29
← sure it stops here
snvs-secvio 20cc000.caam-snvs: violation handlers armed - non-secure state
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver

It stops near the log of the CAAM disabled Module below CAAM-related Kernel Config from where to start now.

CONFIG_CRYPTO_DEV_FSL_CAAM
CONFIG_CRYPTO_DEV_FSL_CAAM_SM
CONFIG_CRYPTO_DEV_FSL_CAAM_SM_TEST
CONFIG_CRYPTO_DEV_FSL_CAAM_SECVIO

In addition, a similar event even sabresd (using rel_imx_3.10.53_1.1.1) occurred.

In the appropriate BSP,there are restrictions concerning the use of ICE?

Outcomes