SROM APIs are executed by Arm® Cortex®-M0+ core in interrupt context using IRQ0 and IRQ1. So, proper interrupt handler addresses and priorities need to be configured for IRQ0 and IRQ1.The required interrupt handler addresses reside in ROM memory and can be found at locations 0x40 and 0x44, respectively.
For more details, see section 3.1 Setting Up IRQs for System Calls in AN220242 Flash Rewriting Procedure for Traveo II Family.
The following are the required configurations:
Follow these steps to check if the configuration is correct:
You can program the eFuse memory using the ‘Blow Fuse Bit’ system call. See Section 33.6, “eFuse Memory” in the Traveo™ II Automotive Body Controller Entry Family Architecture Technical Reference Manual (TRM) (002-19314 Rev. *E). This should be used only on the customer bits (AddressOffset 0x68 to 0x7F). You need to pass the following three parameters to this system call:
EFUSE_NR is ‘4’ for CYTx devices.
The Erase Suspend can used to suspend only in non-blocking mode. In the blocking mode, the system call will exit only after the completion of erase; so it cannot be suspended. If EraseSector is called on a sector other than the suspended one, the new sector will be erased and the suspended sector will be in an unknown state. EraseSector can be called on the suspended sector to restore to blank state.
Program Row system does not have suspend mechanism similar to erase operation. In the blocking mode, the system call will exit only after the completion of programming. In non-blocking mode, the programming will happen in the background and cannot be suspended.
Bootloadable application start address must be within a valid RAM memory length - [RAM_START + 3 KB, RAM_END – 6 KB]. Bootloadable application length must be a value for which the bootloadable application image fits into a RAM address range [RAM_START + 3 KB, RAM_END – 6 KB].
Yes, it is possible to authenticate the application in the NORMAL protection state using CySAF and configuring TOC2_FLAGS.APP_AUTH_CTL as 2 Though the authentication is disabled, the valid public key should be programmed to SFlash.
Cy_FB_VerifyApplication is part of Flash Boot Shared Functions, so it can be used without SLLD. See the section 34.2.1 Flash Boot Shared Functions of the Traveo II Architecture TRM.
Also, the Public key is same as the key used in Flash boot.