CCS/PROCESSOR-SDK-AM437X: AM437x RTOS Uart Communication Issue

Hi,

There are two issues reported by you:

1) No source available for "0x35a7e" is described in detail at the section "Debugging Library code" of the Debug User's Guide below:
downloads.ti.com/.../ccs_debug-main.html

2) Error:Unable to read. In general these errors are caused by two scenarios:
- Core is not halted. All the views in CCS are updated when the core/device is halted or, depending on the device, when Real-time mode is used. When the device is put to run, some registers may try to be updated (by scrolling the screen, for example) and thus cause partial errors. These are not critical errors and the registers should update normally when the core is halted.
- Powred off peripherals that also prevent the main core from accessing their registers. If you power up the peripheral, the registers should become visible.

In the screenshot you sent, the first scenario is the most plausible.

Hope this helps,
Rafael

Hi,

The reference I sent you explains the message but it leaves to the developer the task of finding the missing source code. Unfortunately the wide variety of software development kits, libraries, custom code, etc. does not give room for a document to be fully comprehensive. In this case, you can use the linker map file (extension .map) to try to find the location of the library or object file that is placed in the memory address indicated by the debugger and then add the source file path to the  Debug Configuration.

To illustrate the scenario, check the short clip below.

As shown in the video above, the first project can find the source file - also, just like your second screenshot, it shows the source code intertwined with the assembly instructions. (this may be a problem of the CCS version you are using*).

The second project I load above belongs to the AM437x Processor SDK and you can see there are no symbols at the address 0x80000000 - no source file is found and no source code is shown in the Disassembly view. Also, when I try to load the path to find the source code, it still fails to properly show it.

Since both projects are built with Debug Symbols (the -g option), this tells me the library <boot.aa9fg> that is  used by the second project was built without symbols.

This is what may be happening with your projects - a given library may not have been built with symbols at all, leaving CCS with no option other than display the message.

Hope this helps,

Rafael

*Back in the CCSv6 days, there were several issues (fixed in later releases) between the debugger and GCC-based code, which caused a range of issues including the lack of proper symbol correlation. Given you are using CCSv6.2, I suspect you may be running into one of these issues. In your second screenshot you seem to have the proper debug symbols loaded but CCS can't find the source file. This brings me to another possible problem.