Tool/software: Code Composer Studio
Now our program can run at debug and release mode,but when we download it into the chip it can't run. Why this happen ? is it because i havn't deploy something? or it is a problem of hardware.
This thread has been locked.
If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.
Tool/software: Code Composer Studio
Now our program can run at debug and release mode,but when we download it into the chip it can't run. Why this happen ? is it because i havn't deploy something? or it is a problem of hardware.
Hello,
long gao said:Now our program can run at debug and release mode,but when we download it into the chip it can't run.
Can you explain in more detail? Are you saying that the program runs well when loading and running from CCS debug but when you try burning your program to flash and running standalone, it does not?
Thanks
ki
thank you very much. now i have another questions. 1. if i have a hardware can run a program correctly, but they other can't , does it means the problem is belong to the hardware? 2. i have a hardware have a problem that when i download it by the xds100v3, it run immidately, why this happen?
long gao said:1. if i have a hardware can run a program correctly, but they other can't , does it means the problem is belong to the hardware?
Assuming everything else is equal (same exact CCS version, same GEL files used, same CCS setting, same program, etc), then yes, all signs would point to some kind of hardware issue.
long gao said:2. i have a hardware have a problem that when i download it by the xds100v3, it run immidately, why this happen?
Note that the default behavior of the CCS debugger when you load a program is:
-load program
-set program counter to entry point (usually cint00)
-auto-run to main (this option can be turned off in the debugger options)
If there is a main, the program will be halted there. If there is no main, or the main cannot be reached, then the target will just remain running unless it encounters some other halt point.
Thanks
ki
thanks again. about question i have sure it is a hardware problem. And about the question 2, now i know it is a problem of a DDR. because when i change the memory from ddr to shram in my .cmd file ,my program works. i think it is a problem of DDR or it's peripheral circuit.