Hi,
We are working with i.MX 6SX and DS-5. We are connecting M4 core on Sabre board with uLink and DStream. In both cases the Linux booting halts after dumping of some CAAM keys. How can we prevent this? Or how to turn off CAAM in kernel config?
Thanks
Rene Kolarik
Original Attachment has been moved to: boot.log.zip
Please look at my comments below.
1.
According to section 52.18 (Release a Slot back to the Keystore) of
“i.MX_6_Linux_Reference_Manual.pdf” ” in documentation of L3.14.28 :
“Configuration of the Secure Memory Driver / Keystore API is dependent on the
following kernel configuration parameters:
CRYPTO_DEV_FSL_CAAM_SM
Turns on the secure memory driver in the kernel build.
CRYPTO_DEV_FSL_CAAM_SM_SLOTSIZE
Configures the size of a secure memory "slot".
…
CRYPTO_DEV_FSL_CAAM_SM_TEST
Enables operation of a captive test / example module”
You may try to disable CAAM SM TEST.
“i.MX 6 Series Software and Development Tool Resources”
< http://www.freescale.com/webapp/sps/site/prod_summary.jsp?code=IMX6_SW >
2.
From Table 20 (Known issues and workarounds for i.MX 6SoloX) of
“i.MX_Linux_Release_Notes.pdf :
“The system reboots after the CAAM RNG test is suspended and resumed.
There is hardware function conflict between the Mega/Fast mix off feature and CAAM.
To use CAAM after kernel bootup, the user should enable the CAAM wakeup function
to avoid Mega mix off in DSM.
Workaround:
echo enabled > /sys/bus/platform/devices/2100000.aips-bus/2100000.caam/2101000.jr0/
power/wakeup ”
Have a great day,
Yuri
-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------