Forums » Software Development »
A CCS Debug issue occurred.
Added by Kyungguk Bok 16 days ago
Currently, the ARM kernel is not booted.
setenv bootcmd ""
saveenv
It is in progress.
I am trying to upload a .out file through CCS.
jtag is using the XDS 200 Blackhawk.
When you proceed with Connect Target,
No source available for "0x80000000"
The above text is generated and the file upload does not proceed.
Do you by any chance know the answer to this question???
P.S The same thing happens when I boot the kernel.
If you think it has been uploaded, proceed and press suspend, the following text will be displayed.
Can't find a source file at "/db/vtree/library/trees/cuda/cuda-u44x/src/ti/bios/src/bcache/bcache_wait.c"
Locate the file or edit the source lookup path to include its location.
Source files such as bcache_wait.c are output differently each time.
| picture316-1.png (48.6 KB) picture316-1.png |
Replies (7)
RE: A CCS Debug issue occurred. - Added by Jonathan Cormier 16 days ago
How are you launching the debug session? How are you trying to load the DSP?
If you click the Debug button (F11), it should build the DSP project and then load it over the JTAG.
RE: A CCS Debug issue occurred. - Added by Kyungguk Bok 15 days ago
Is there another way to load the DSP?
I am using version 7.3.0 of CCS, and after proceeding with the build project, press debug (Scarab button?) or enter the debug window through Target Configurations. When you press the debug button, the .out file is automatically loaded, but it is not executed. (Checking with GPIO toggle) After that, when you press the suspend button, the phrase "/db/vtree/library/trees/cuda/cuda-u44x/src/ti/bios/src/bcache/bcache_wait.c" is displayed.
When you enter the debug window through Target Configurations and click Connect Target, the message No source available for "0x80000000" is displayed.
I suspect that ARM and DSP have the same starting address.
RE: A CCS Debug issue occurred. - Added by Jonathan Cormier 15 days ago
This wiki covers the different ways to load the dsp. https://support.criticallink.com/redmine/projects/arm9-platforms/wiki/DSP_Quick_Start
I suspect that ARM and DSP have the same starting address.
This shouldn't happen. Unless your DSP project is setup wrong.
Note per the L138 datasheet: https://www.ti.com/lit/ds/symlink/omap-l138.pdf?ts=1692811393052&ref_url=https%253A%252F%252Fwww.ti.com%252Fproduct%252FOMAP-L138
0x8000 0000 is mapped to internal shared RAM and the top 128B is used for the ARM reset vectors. The DDR memory region starts at 0xC000 0000
RE: A CCS Debug issue occurred. - Added by Kyungguk Bok 13 days ago
Yes, I know all of the above.
What can happen if I set up my DSP project incorrectly?
I am
https://support.criticallink.com/redmine/projects/arm9-platforms/wiki/DSP_Hello_World
I followed the instructions above and proceeded.
Is there another way to set up the project?
RE: A CCS Debug issue occurred. - Added by Jonathan Cormier 13 days ago
Hi, I feel in the dark about what you have tried and are trying to do. And what works and where you are stuck. If you followed the DSP Hello World, did it work as written? And you are now trying to update it to work without the ARM?
RE: A CCS Debug issue occurred. - Added by Kyungguk Bok 12 days ago
Yes, that's right.
I am planning to experiment only with the DSP part using CCS JTAG without ARM.
So, as mentioned above, the error occurs regardless of whether the kernel part is running, so it is not possible to work with DSP alone.
RE: A CCS Debug issue occurred. - Added by Jonathan Cormier 9 days ago
Could you share your current project?
