On 10. 06. 22 13:47, Fabio Estevam wrote:
[EXTERNAL EMAIL]
Hi Michal,
On Fri, Jun 10, 2022 at 7:02 AM Michal Vokáč michal.vokac@ysoft.com wrote:
Hi Fabio, I had the very same problem/error on i.MX6 and figured out that CONFIG_ARCH_MISC_INIT=y must be enabled otherwise the caam_jr driver is not initialized.
Yes, correct. There is a patch from Gaurav to address this: https://lists.denx.de/pipermail/u-boot/2022-June/485959.html
OK, thanks for the reference. It took me some time to reply to the thread and this patch came in the meantime.
Hash algo: sha256 Hash value: 13e0b23bd49f9e86a0425080fc788db67bf318d6f103f217d5705a455737e91c Verifying Hash Integrity ... sha256CACHE: Misaligned operation at range [122c4604, 122ce684]
- OK Loading fdt from 0x122c4604 to 0x18000000 Booting using the fdt blob at 0x18000000 Loading Kernel Image Using Device Tree in place at 18000000, end 1800d04d
On a imx6sabresd the board simply hangs in SPL, when CONFIG_IMX_HAB=y: https://lists.denx.de/pipermail/u-boot/2022-June/485993.html
Does your board use SPL?
Normally it does but I am not that far yet. We are in a process of upgrade from v2019.07 to the latest version and moving everything from the legacy support to the driver model etc. is quite challenging.
So far I am building just the non-SPL version and loading it over the NXP uuu tool to fail-fast.
I expect ton of new problems once I move to the SPL version :)
Regards, Michal