www.ti.com
11.2.3.4 Host Utility Timing Requirements
⑥
⑤
①
④
③
②
BOOTME
ACK
External
HOST
DM350
DONE
CRC32 table
UBL
DONE
⑦
ARM ROM Boot Modes
Table 11-7. Host Utility Data Format
"^^^^ACK/0" Transfer
D0
D1
D2
D3
D4
D5
D6
D7
Start Byte
"^"
"^"
"^"
"^"
"A"
"C"
"K"
"/0"
——
→
Checksum "9af944c9" Transfer
D0
D1
D2
D3
D4
D5
D6
D7
9
a
f
9
4
4
c
9
——
→
Table 11-8. CRC32 Table Transfer
crc32_table[1024] = {0x01234567L, 0x89ABCDEFL....}
D0
D1
D2
D3
D4
D5
D6
D7
Start Byte
"0"
"1"
"2"
"3"
"4"
"5"
"6"
"7"
——
→
D0
D1
D2
D3
D4
D5
D6
D7
"8"
"9"
"A"
"B"
"C"
"D"
"E"
"F:
——
→
0x67 + 0x45 + 0x32 + 0x01 + 0xFE + 0xCD + 0xAB + 0x89 + ...
=>checksum8
The UART host utility must allow the RBL time to process commands and data. When sending characters
from the host to the DM355 UART RBL, the host utility must insert a delay between each byte character
equal to 1 ms. Furthermore, 5 ms delay must be inserted for each of the timing parameters shown in
.
(1)
The delay time from "BOOTME" received until "^^^ACK" sent.
(2)
The delay time from "ACK" sent to CRC32 table data sent.
(3)
The delay time from CRC32-table data sent to next CRC32-table data sent.
(4)
The delay time from final CRC32-table data sent to "DONE" or "CORREPT" received.
(5)
The delay time from "DONE" or "CORREPT" received until UBL data sent.
(6)
The delay time from UBL data sent until next UBL data sent.
(7)
The delay time from final UBL data sent until "DONE" or "CORREPT" received.
Figure 11-14. Host Utility Timing
170
Boot Modes
SPRUFB3 – September 2007