I have tried this suggestion:
Three observations:
- The 2nd core does indeed start, both CPU’s in HYP mode.
- If I only update my board with the .mender file the u-boot config does not get updated. So on reboot the old u-boot config still applies. I need to replace the bootloader and SPL with dfu to the new version. Is this behaviour expected? I was expecting the new u-boot to get updated with the .mender file as well.
- caam behaves differently depending on CONFIG_ARMV7_BOOT_SEC_DEFAULT
CONFIG_ARMV7_BOOT_SEC_DEFAULT=y: (so single core active)
root@imx7d-pico:/lib# dmesg | grep caam
[ 2.444686] caam 30900000.caam: Entropy delay = 3200
[ 2.450039] caam 30900000.caam: Instantiated RNG4 SH0
[ 2.509452] caam 30900000.caam: Instantiated RNG4 SH1
[ 2.514527] caam 30900000.caam: device ID = 0x0a16030000000000 (Era 8)
[ 2.521108] caam 30900000.caam: job rings = 3, qi = 0
[ 2.672765] caam algorithms registered in /proc/crypto
[ 2.687239] caam_jr 30901000.jr0: registering rng-caam
[ 2.694308] caam 30900000.caam: caam pkc algorithms registered in /proc/crypto
CONFIG_ARMV7_BOOT_SEC_DEFAULT not defined: (dual core active)
[ 2.515625] caam 30900000.caam: Entropy delay = 3200
[ 2.551627] caam 30900000.caam: failed to acquire DECO 0
[ 2.556969] caam 30900000.caam: failed to instantiate RNG
The rescue image from Technexion does boot up the board with the two CPU’s in SVC mode, but it is unclear for me how they do that.