slau358q.pdf - 第50页

Status Messages www.ti.com 50 SLAU358Q – September 2011 – Revised October 2019 Submit Documentation Feedback Copyright © 2011–2019, Texas Instruments Incorporated Operation Executing Main Process... ............. 2 : ini…

www.ti.com

Status Messages

SLAU358Q–September 2011–Revised October 2019

Submit Documentation Feedback

Operation

2.3 Status Messages

The current status is always displayed at the bottom of the progress bar, as shown in Figure 2-1, and

previous status and error messages are shown in the history window in the bottom left corner. are

displayed in the report window.

All procedures in the MSP Gang Programmer are divided into small tasks to be executed in series. When

first task is finished successfully, then the next task is started. Each task has is own consecutive number

assigned by the task manager when the image is created. The most commonly executed tasks are listed

below:

• Initialization

• Open Target Device

• Close Target Device

• Erase

– Segment

– Main memory

– Info memory

– BSL memory

• Blank check

• Program

• Gang Program (program unique data to each target)

• Write RAM

• Write GANG RAM (write unique data to each target)

• Verify

• Read memory

• Save Info-A

• DCO calibration

• Retain Info-A

• SetPC and run

• Capture PC and Stop

• Stop PC

• Secure device

• Finish

For example, the operations Erase, Program ,and Verify execute the following tasks:

• Initialization

• Open Target Device

• Erase

• Blank check

• Program

• Verify

• Close target and finish.

These tasks execute the easiest programming process in small MCU devices. The aforementioned tasks

can be divided into smaller tasks that only erase one segment, erase info segment, or erase one block of

the main memory. For that reason, many more tasks are displayed in the report window than are

described above. For example, when programming the MSP430F5438 the following information would be

displayed in the report window:

Status Messages

www.ti.com

SLAU358Q–September 2011–Revised October 2019

Submit Documentation Feedback

Operation

Executing Main Process...

.............

2 : init target

3 : erasing-Info

4 : erasing-Info

5 : erasing-Info

6 : erasing-Main

7 : erasing-Main

8 : erasing-Main

9 : erasing-Main

10 : erasing-Main

11 : erasing-Main

12 : erasing-Main

13 : erasing-Main

14 : erasing-Main

15 : Blank-1800

16 : Blank-1880

17 : Blank-1900

18 : Blank-5C00

19 : Blank-10000

20 : Blank-20000

21 : Blank-30000

22 : Blank-40000

23 : Write-FC00

24 : Write-FC90

25 : Write-FD10

26 : Write-FD80

27 : Write-FFE2

28 : Verify-FC00

29 : Verify-FC90

30 : Verify-FD10

31 : Verify-FD80

32 : Verify-FFE2

33 : Gl.Verify-1800

34 : Gl.Verify-5C00

35 : Gl.Verify-10000

36 : Gl.Verify-20000

37 : Gl.Verify-30000

38 : Gl.Verify-40000

39 : closing target

40 : Done

0 : Finished

This report indicates that sectors INFO-B, INFO-C, INFO-D, and the main memory block have been

erased (tasks 2 to 14) blank checked (tasks 15 to 22), programmed (tasks 23 to 27) and verified (tasks 28

to 38). Finally, access to target devices is closed and the programming process is finished. Length of task

description (including consecutive task number) is limited to 16 characters to be able display this

information on the third line of the MSP Gang Programmer LCD display.

The MSP Gang Programmer can process up to 1000 tasks per one image saved in internal memory.

Having that number of available tasks and one or more code files saved in internal memory (total memory

footprint of up to 512KB in one image), the MSP Gang Programmer gives the user significant flexibility to

perform custom programming procedures. If for any reason the code files and task scripts require more

than 512KB of memory, then the next image memory can be taken and combined with the first one for one

larger image block (1Mbyte or more). The MSP Gang Programmer has internal flash memory of 8Mbyte

that can, if desired, all be used to form one image with a memory footprint of 8Mbyte.

Error messages are displayed similarly to status messages, however, programming is terminated if the

error is related to all target devices. Subsequently, if the problem is resolved or the faulty target device is

disabled, then the programming procedure can be restarted to complete the programming process. The

result for all devices is reported in the results section (green or red icons). When the global status is

reported as FAIL, see the result section for details. Similarly, the MSP Gang Programmer uses red and

green LEDs to indicate the result of its operations (red indicates failure) and details are displayed on the

LCD display. Below is the list of errors reported in the MSP Gang Programmer.

www.ti.com

Status Messages

SLAU358Q–September 2011–Revised October 2019

Submit Documentation Feedback

Operation

==== Errors from the BOOT loader. ====

ERROR # 001 - BOOT Firmware only is in the MSP-GANG! The API Firmware should be downloaded.

ERROR # 002 - API Firmware CRC is not present! The API Firmware should be reloaded.

ERROR # 003 - API Firmware CRC error! The API Firmware should be reloaded.

ERROR # 004 - BOOT CRC error in the MSP-GANG!

==== Errors from the MSP-GANG Firmware. ====

ERROR # 010 - CRC Access key. Key corrupted. Access to programmer is blocked.

ERROR # 011 - Invalid programmer's access key. Access to programmer is blocked.

ERROR # 012 - Unknown interface.

ERROR # 013 - Vcc is too low.

ERROR # 014 - Vcc is too high.

ERROR # 015 - VtIO is too low.

ERROR # 016 - VtIO is too high.

ERROR # 017 - Header CRC. Image header is corrupted.

ERROR # 018 - Script CRC. Image script is corrupted.

ERROR # 019 - Exceed script number.

ERROR # 020 - Script command unknown.

ERROR # 021 - MCU Fetch synch failed.

ERROR # 022 - CPU JTAG synch failed.

ERROR # 023 - MCU device initialization failed.

ERROR # 024 - RAM firmware download failed.

ERROR # 025 - Flash blank check failed.

ERROR # 026 - Flash read verify failed.

ERROR # 027 - Flash write failed.

ERROR # 028 - Image flash write initialization failed.

ERROR # 029 - Image flash lock failed.

ERROR # 030 - Invalid script type/name.

ERROR # 031 - Script size too big.

ERROR # 032 - Used wrong MCU.

ERROR # 033 - IR communication failed.

ERROR # 034 - Page info number out of range.

ERROR # 035 - Address too high.

ERROR # 036 - Target number out of range.

ERROR # 037 - Address not even.

ERROR # 038 - Size not even.

ERROR # 039 - DCO calibration frequency out of range.

ERROR # 040 - DCO calibration failed.

ERROR # 041 - Gang flash write failed.

ERROR # 042 - SD Card - Read Response Error

ERROR # 043 - SD Card - Boundary Address Error

ERROR # 044 - SD Card - Initialization timeout

ERROR # 045 - SD Card - Read timeout

ERROR # 046 - SD Card - Initialization Error

ERROR # 047 - SD Card - CRC7 Error

ERROR # 048 - SD Card - CRC16 Error

ERROR # 049 - SD Card - Write CRC Error

ERROR # 050 - SD Card - Data Write Error

ERROR # 051 - SD Card - Write Timeout

ERROR # 052 - SD Card - MBR Sector Error

ERROR # 053 - SD Card - Volume Error

ERROR # 054 - SD Card - Address in File Error

ERROR # 055 - SD Card - Read File Error

ERROR # 056 - SD Card - File not found

ERROR # 057 - Hardware Rev-0. option not supported.

ERROR # 058 - Flash PSA verification failed.

ERROR # 059 - Flash read (Rx) data error.

ERROR # 060 - Vpp too low to secure fuse.

ERROR # 061 - Secure key incorrect.

ERROR # 062 - Secure device failed.

ERROR # 063 - Target not open, no access.

ERROR # 064 - BSL password wrong index.

ERROR # 065 - BSL read (Rx) timeout.

ERROR # 066 - BSL firmware download failed.