SPRUI33H November 2015 – June 2024 TMS320F280040-Q1 , TMS320F280040C-Q1 , TMS320F280041 , TMS320F280041-Q1 , TMS320F280041C , TMS320F280041C-Q1 , TMS320F280045 , TMS320F280048-Q1 , TMS320F280048C-Q1 , TMS320F280049 , TMS320F280049-Q1 , TMS320F280049C , TMS320F280049C-Q1
The no-response error occurs when any node expecting a response waits for TFRAME_MAX time and the message frame is not fully completed within the maximum length allowed, TFRAME_MAX. After this time, a no-response error (NRE) is flagged in the NRE bit of the SCIFLR register. An interrupt is triggered, if enabled.
As specified in the LIN 1.3 standard, the minimum time to transmit a frame is:
where N = number of data fields.
And the maximum time frame is given by:
The timeout value TFRAME_MAX is derived from the N number of data fields value, see Table 27-10. The N value is either embedded in the header ID field for messages or is part of the description file. In the latter case, the 3-bit CHAR value in SCIFORMAT register indicates the value for N.
N | TDATA_FIELD | TFRAME_MIN | TFRAME_MAX |
---|---|---|---|
1 | 10 | 54 | 76 |
2 | 20 | 64 | 90 |
3 | 30 | 74 | 104 |
4 | 40 | 84 | 118 |
5 | 50 | 94 | 132 |
6 | 60 | 104 | 146 |
7 | 70 | 114 | 160 |
8 | 80 | 124 | 174 |