
ROM Code Generation Flow
B-7
Submitting ROM Codes to TI
-
“Customer-OTP” area, including the D-number. Addresses
0x3D7BFE and 0x3D7BFF, which are eventually used to store
the checksum are not used in the computation.
-
TI-OTP area containing TI test code. Addresses 0x3D7FFE and
0x3D7FFF, which are eventually used to store the checksum are
not used in the computation.
-
“Customer ROM” area, including the ROM entry-point and CSM
passwords. Addresses 0x3F7FF4 and 0x3F7FF5, which are
eventually used to store the checksum are not used in the com-
putation.
The computed checksum is written into the corresponding locations
(see Table B
1). The image of the ROM is now ready in the PC
memory.
Table B
−
1. Checksum Computation Memory Locations
Address
Content
0x3D7800
…
.
0x3D7BFB
1K OTP for customer code.
(referred to in this document as Customer-OTP)
0x3D7BFC
†
Low-word of D-number
0x3D7BFD
†
High-word of D-number
0x3D7BFE
†
Low-word of checksum (for Customer-OTP)
0x3D7BFF
†
High-word of checksum (for Customer-OTP)
0x3D7C00
…
.
0x3D7FFD
1K OTP for TI test code.
(referred to in this document as TI-OTP)
0x3D7FFE
Low-word of checksum (for TI-OTP)
0x3D7FFF
High-word of checksum (for TI-OTP)
0x3D8000
‡
…
.
0x3F7FF1
Start address for customer code in ROM (referred to in this document as Customer-
ROM)
End address for customer code in ROM
0x3F7FF2
†
Low-word of D-number
0x3F7FF3
†
High-word of D-number
0x3F7FF4
†
Low-word of checksum (for Customer-ROM)
Summary of Contents for TMS320C28x
Page 30: ...1 12...
Page 80: ...This page intentionally left blank 2 50 This page intentionally left blank...
Page 269: ...IN loc16 PA 6 112 MOV AL 0 AL 0 UOUT IORegC AL IOspace IORegC AL 10...
Page 308: ...MAXCUL P loc32 6 151 Saturate MOVL Var64 2 ACC Store result into Var64 MOVL Var64 P...
Page 509: ...SUBL ACC P PM 6 352 SUBL ACC P PM ACC S B 11 M X 4 MOVH Y ACC 5 Store Q15 result into Y...
Page 585: ...This page intentionally left blank 7 32 This page intentionally left blank...