Some troubles encountered when using CCS

Jacktang

Some troubles encountered when using CCS [Copy link]

1. Use SEED_XDS510PLUS in CCS simulation Problem: When using the routine simulation, because I was using CCS6.2 at the time, I couldn't find the 510 option. Solution: Later I searched the Internet and found that XDS510 supports up to 5.5. I downloaded the 5.5 version again. The relevant driver can be downloaded from the official website (XDS510). Select version 4.1.3above. After downloading, install it in the CCS related folder, that is, the ccs_base folder (it should be this folder). It can be recognized after plugging it in. Then create a .ccxml file under the project and configure it as SEED XDS510PLUS Emulator. 2. Connection sequence problem Solution: 1. Power on the board; 2. Connect to JTAG; 3. Connect the emulator to the USB interface The connection order has not been studied yet. The general recommendation is not the above one, but "connect the emulator and the target board first, and then power on the target board". However, sometimes the connection seems unsuccessful. You can try the above solution, but do not unplug it while it is powered on. 3. unresoved symbols remain Problem: After compiling the program, the prompt "unresoved symbols remain" appears Solution: 1. After searching on the Internet, I got the following answer: "When an assembler is needed in a project, please note that when creating a project, there is an output format that contains legacy coff and eabi ELF. If the old-fashioned method is used in the assembly, such as adding an underscore before the function name, you need to select legacy coff. If you do not want to add an underscore before the function name, you need to select eabi ELF, otherwise the following error will be reported: error #10234-D: unresolved symbols remain error #10010: errors encountered during linking; " **.out"” However, the option to change legacy coff is grayed out, so the author has no doubt that the change was successful. 2. It may be that the .c file is missing. For example, when using the CPU timer, an error will be reported if _CpuTimers.c is not added. The premise of this solution is that you can find the .h file in which you defined the error function. If you can't even find the .h file, the path may be wrong. 4. CCS5 and 6 Problem: The project that was successfully compiled in CCS6.2 fails when imported into CCS5.5 and cannot be imported. Solution: The author chose death... The reason was not found, and the project was rebuilt in CCS5. If you find the reason, please tell the author Smile. 5. Test Connection Problem: CCS5.5 and XDS510 PLUS are used. The drivers have been installed normally. However, when testing the connection, it shows Failure due to the controller command-finish taking too long. Solution: After checking a lot of information, I finally concluded that it does not affect the load and download of the program, as well as the debugging. I am not sure what the results will be for other versions. As for CCS5.5 and XDS510 PLUS, don't pay attention to the details. The main reason is that I can't find the cause. 6. Compilation succeeded but .out file was not generated Problem: After several successful compilations, the small beetle could not be clicked, and it was displayed C28xx: GEL: Encountered a problem loading file... and there was no error displayed next to it Solution: There will usually be red fonts indicating errors in the Console on the left, but Problems will not be displayed on the right. Generally, the .out file can be compiled after modifying them. Another possibility is that the path is incorrect. In this case, the corresponding path needs to be modified, usually under Debug. 7. C28xx: Error connecting to the target: (Error -171 @ 0x0) The wrong controller address value has been used. A controller cannot be detected even though the selected port does match the hardware configuration. Problem: Sometimes this prompt will appear when entering debugging Solution: After trying several times, it is better to restart the software 8. After entering Debug, the graph turns gray Problem: As above Solution: I can’t find why, or I can only keep entering debug to try, which is annoying. 9. JVM heap low detected Problem: When debugging a program, a message “JVM heap low detected” will pop up in the lower right corner of the computer Solution: When searching online, it is usually to create a new project for transplantation, or to modify a stack file, but nothing happened after seeing such a prompt, so I just ignored it. 10. I encountered a very strange thing Problem: After adding the instruction asm ("RPT #7 NOP") to the interrupt, the interrupt could not be turned off in the main function. 11. Here is a book for your reference: "Electromagnetic Compatibility Design of High-Speed DSP Systems" Thanh T.Tran