Connecting 2_CCS to the simulator in the 335 project development record

Connecting 2_CCS to the simulator in the 335 project development record

In actual use, the connection between the simulator and the CCS may have one or another problem. Maybe your connection is successful and you haven't encountered any problems, but I do have many problems, it may be related to computer configuration, or personality;

Some of the following errors and solutions are not necessarily correct, but they are also a solution. I would like to share with you:

Problem:
1.
The jtag cannot be connected, and an error is returned:
The controller has detected a dead JTAG clock.
The user must turn-on or connect the JTAG clock for the target.
The connection to dm8147 is normal. This problem occurs when the dsp f28335 is connected;
Through the test without the simulator, it is found that the reset pin 11 of the jtag continuously emits a low level. This pin inputs the WID signal and the WID signal inputs are faulty;
Therefore, it is still the hardware 28335 problem. The final result is that the 28335 watchdog is continuously reset, which may be related to the empty flash chip. (Because no program exists in the Flash)

2.
The controller has detected a target power loss.
The user must turn-on or connect the power supply for the target.
Check whether the Board is powered on.

3.
Device is held in reset. Take the device out of reset, and retry the operation.
Unknown reason...

4.
The requested tclk pll frequency option is invalid.
The utility or debugger has requested a selection
The jtag pll frequency or clock source that is invalid.
The value of USCIF. TCLK_FREQUENCY is probably bad.
If the jtag frequency is set to 0 manually, an error is returned.

5.
Failure due to the controller command-finish taking too long.
Restart ccs or watch it out

6.
Error connecting to the target:
(Error-233 @ 0x0)
The jtag ir and DR scan-paths cannot circulate bits, they may be broken.
An attempt to scan the JTAG scan-path has failed.
The target's JTAG scan-path appears to be broken
With a stuck-at-ones or stuck-at-zero fault.
(Emulation package 5.0.747.0)
Restart ccs or take a look at the board, generally can solve.

7. the chosen operation is not currently available error occurs when graph is used or the window to observe the waveform;
Delete the. metadata folder.

8. When a file in any project is opened, the following error occurs: error retrieving content description for resource.
The corresponding header file is not included. Check the compilation prompt.

9. During debugging simulation, A required dynamic library cocould not be located.
Check whether the ccxml file is deleted or the correct ccxml file is used !! Sometimes I tried to solve this problem for half a day before I found that the ccxml file was wrong. It was a very painful error...

10. During debugging simulation, the system keeps stuck and there is no error prompt;
Ccs, after the simulator driver is installed, run the USBorPCI SEED-XDS560PLUS Version two desktop files again.

11. After burning the program to flash, unplug the plug between the simulator and the board. Note that it is not the connection plug between the computer and the simulator. The phenomenon can be observed after power-on;

After the cmd file is configured correctly and burned to Flash, how to perform online simulation, breakpoint settings, and so on correctly indicates that the Flash is not successfully burned or the startup mode is not changed to Flash boot.

12. The controller has detected a cable break far-from itself.
The user must connect the cable/pod to the target. (Emulation package 5.0.747.0)
The interface between the simulator and the Board is not inserted =;

13. Many other problems with unknown causes;
Try to delete the work interval. metadata folder;