Firmware User Manual (AE-step)
24
Revision 1.02
2019-04-24
TLE984x Firmware User Manual
Boot Strap Loader (BSL)
4.1.6
Command Execution
The command data is checked and validated after all the message data is received. This includes that the
message parameters are checked for boundaries, any hardware-applied protection (e.g. NVM protection) and
if this message is supported for this boot mode.
The following command classes are supported:
•
RAM access
– RAM accesses are directly done by the BSL protocol without the use of any other submodule.
•
NVM access
– NVM accesses (read/write) are performed using the NVM API.
•
100TP access
– 100TP accesses are performed using the NVM CS (Configuration Sector) API.
•
NVM CS (Configuration Sector) access
– NVM CS (Configuration Sector) accesses are performed using the
NVM CS (Configuration Sector) API.
4.1.7
Timing Constraints
The host needs to add a delay between all sent BSL command header and EOT messages. Same delay must
be add between EOT and DATA block messages.
The BootROM also requires an additional waiting time to process the full received BSL command. The
BootROM is not able to provide the response messages or able to receive new commands before this period
expires. The host must wait this length of time before sending a new command or requesting the command
response (e.g. by sending a LIN slave response header).
To give BootROM time to process each byte and CMD/DATA/EOT frame, byte and frame timing must comply to
the values shown in
.
* There are certain BSL commands that need longer processing time. These involve NVM write/erase
operations. The host waiting time is longer before a command response can be requested or before a result is
sent back. Changing a value in an already programmed NVM page, which happen if a setting is changed,
requires the following NVM steps:
- Read the full page into the HW buffer
- Update the HW buffer with new data
- Program the page from the HW buffer
- Erase the old page
Table 4-1 BSL Byte and Frame Timing Limits and Highest Transfer Rate
Delay type
LIN (min.)
FastLIN (min.)
Between bytes
4.1 µs
3.7 µs
Between end of CMD to
start of DATA or EOT frame
20 µs
20 µs
Interframe Timeout
280 ms
280 ms
Host waiting time for
message processing before
asking for response
100 µs *
n/a
Host waiting time after
response is received until a
new frame can be sent
20 µs
20 µs
