J722SXH01EVM: didn't show any information in Disassembly view

Hi Maojiang,

MAOJIANG YAO said:

debugging the tiboot3 works fine for me on R5

R5 disassembly view is fine but A53 is not?

Assuming the above is correct, I suspect the issue could be related to 64-bit addressing. 12.7 is an older version of CCS so I will have to try the same device with that version and see if I can reproduce the issue. This may take a day. I will keep you posted.

Thanks

ki

Hi, Ki

thank you for your respone

I'm trying to debug the tispl by using the ccs20, doesn't find the u-boot-spl file but the file actually exists, however the same way is ok in the ccs12.7.reference the link 3.1.2.2. Debugging U-Boot and SPL — Processor SDK J722S Documentation,

Could you please to give some suggetsion ?

thanks

Maojiang

Which linux distro (and version) are you using? 

Also provide the exact CCS version.

re: ccs12 vs ccs20

the alternate steps to load uboot to memory "3.1.2.3.6. Step 6: Loading SPL" does mention filter in the file browser, can this be related?
("3." below)

> To load the symbols for the binary to allow source level debugging
>
> 1. Click Run -> Load -> Load Symbols…
> 2. In the dialog box, click the Browse button
> *3. Like before browse to the spl directory and change the filter to All
> 4. Select the u-boot-spl file which is the ELF executable that also contains the symbols and click OK
> 5. Ensure the Code Offset and Data Offset are blank

ccs：20.2.0.12

Linux：

MAOJIANG YAO said:

ccs：20.2.0.12

Your first screenshot for the disassembly view issue was with CCS 12.7. Do you see the same exact issue with CCS 20.2?

MAOJIANG YAO said:

I'm trying to debug the tispl by using the ccs20, doesn't find the u-boot-spl file but the file actually exists, however the same way is ok in the ccs12.7.reference the link 3.1.2.2. Debugging U-Boot and SPL — Processor SDK J722S Documentation,

This looks like a bug with CCS 20.2.0. I can reproduce the issue. The dialog seems to not show files without a file extension. To workaround the issue you will need to give the file some extension.

I filed a bug for this issue. Tracking link: https://sir.ext.ti.com/jira/browse/EXT_EP-12838

Thanks

ki