We are running a custom bootloader on our LS1046ARDB - The code performs authentication of an image and passes control. With SB_EN disabled in RCW and the system in SECMON in Check State, the SEC is initialized successfully and can process jobs through the Job Ring Interface. However, when we enable secure boot and execute the same boot code with SECMON in Trusted State, the SEC is not getting initialized and any jobs passed through input JR gives an error code 0x13 (DECO Source) in JRSTAR_JR0 register [ Header Error (Invalid length or parity, or certain other problems.) ]
What could be the reason here - are we missing some key differences in SEC behavior and initialization steps when Secure Boot is enabled vs. when Secure Boot is Disabled?