Firmware User Manual (AE-step)
76
Revision 1.02
2019-04-24
TLE984x Firmware User Manual
This user API function writes data to the configuration NVM,
address is relative inside the configuration NVM area (8x one
page, 1024 bytes). It stops writing at page boundary. The function
shall support partial page programming, preserving the page
data not passed as an input. The function shall perform an
implicit update of the page checksum and write counter. The
function does not allow the customer to change the page
checksum or write counter. In case the offset plus count is out of
range or if count is zero it returns an error and does not perform
any program operation. The function also returns an error in case
the NVM code segment is write protected. The write counter and
the page checksum are the last two bytes of the page.
This user API function sets the SCU_SYSCON0.NVMCLKFAC
divider
This user API function allows to gather the NVM configuration,
this is the number of sectors for user code, user data and user bsl.
This user API function triggers NVM FSM mapRAM update
sequence from mapped sector.
This user API function erases a given NVM page (address). This
function rejects with an error in case the accessed NVM page is
write protected. In case of an unsused (new) page in non-linear
sector, the function does nothing and returns success. In case of
erasing a page in linear sector, the function should always
perform the erase.
This user API function erases a given NVM page (address) and
branches to an address (branch_address) for code execution
during the NVM operation.
This user API function clears the NVM protection password for a
given NVM code or data segment (not supported for the BSL
segment). The password is only removed in case the correct
password is provided.
This user API function sets a read and/or write protection for any
NVM region individually. The API does not change the protection
state for a region where password protection is currently
installed.
This user API function clears a read and/or write protection for
any NVM region individually. The API changes the protection state
for a region, but does not update the installed password (config
sector).
This user API function checks for the hardware current applied
NVM protection status.
Table 6-2 User API Routines Function Overview
(cont’d)
Name
Description