Firmware User Manual (AE-step)
75
Revision 1.02
2019-04-24
TLE984x Firmware User Manual
6.8
User API Routines
These routines are exported by the BootROM to the customer user mode software.
User API Routines support features like accessing memory resources like NVM and 100TP pages. They also
support to configure some protection mechanism and BSL parameters. The API functions check the valid
parameter range, which is depending on the device.
Table 6-2 User API Routines Function Overview
Name
Description
This user API function reads the user BSL interface selection
value.
This user API function writes the user BSL interface selection
value. This function returns an error in case the NVM code
segment is write protected.
This user API function checks for single and double ECC checking
over the entire NVM (all NVM linear and NVM non-linear sectors).
Any existing ECC errors are cleared before the read starts.
This user API function checks if any single or double ECC events
have occurred during runtime. It reports any single or double ECC
event coming from NVM. The corresponding last double ECC
failure address is returned via modified pointer.
This user API function enables a separate MBIST for all possible
reset sources, except POR reset and pin reset. The MBIST is
always performed for POR reset and pin reset. This function
rejects with an error in case the NVM code segment is write
protected.
This user API function reads out the NAC value that is currently
configured in the non volatile device configuration memory.
This user API function configures the NAC value in the non volatile
device configuration memory.
This user API function reads out the LIN NAD value that is
currently configured in the non volatile device configuration
memory.
This user API function configures the LIN NAD value in the non
volatile device configuration memory.
This user API function reads data from the customer accessible
configuration pages (100TP), address is relative inside the
configuration NVM area (8x one page, 1024 bytes). It stops
reading at page boundary. In case the offset plus count is out of
range or if count is zero it returns an error and does not perform
any read operation.