5. FAQ

5.1. Why Does the Tool Indicate a Version Mismatch When Opening the Debug Data File?

When the tool opens the debug data file, it will check the version information in the file, and an example of the version information is shown below.

Fig. 5.1 Version information in the debug data file

If the version information within the debug data file does not match the tool version, there are three prompt conditions:

1. If the file does not contain version information, the following message will be prompted:

[Suggested handling method] Read the default data of the current SDK version, and then open the debug data file, so that it can contain the default data of the difference parameters, and also keep the debug data of the file.

Fig. 5.2 Prompt message of no version information

2. If the SoC information inside the file does not match the debug tool, the following message will be prompted.

[Suggested handling method] Check whether the file and the SoC to which the debug tool works are the same.

Fig. 5.3 SoC mismatch prompt message

3. If the parameter version information within the file does not match, the following message will be prompted.

[Suggested handling method] Read the default data of the current SDK version, and then open the debug data file, so that it can contain the default data of the difference parameters, and also keep the debug data of the file.

Fig. 5.4 Prompt message for parameter version mismatch

5.2. Why Does the Tool Prompt SoC Mismatch When Connecting To the Board?

When the tool connects to the board, it will check if the board’s SoC matches the tool? If it does not match, the following error message will be displayed and the connection will be interrupted.

Fig. 5.5 SoC mismatch prompt message

[Suggested handling method] Confirm whether the SoC shown on the top left of the tool is the same as the board.

Fig. 5.6 Tool SoC information