CCS/AM6548: CCS crashes when loading specific OUT-file

Thomas Dorsch

Part Number: AM6548
Other Parts Discussed in Thread: SYSBIOS,

Tool/software: Code Composer Studio

Hello,

I followed the steps to create a project for A53 with RTOS:
software-dl.ti.com/.../index_examples_demos.html

When I connect to the first A53 core, and load the .out-file, CCS closes immediatly after the load was complete.

This is reproducable.

Build log from outfile which closes ccs

**** Clean-only build of configuration Debug for project Host_A53_0 ****

/home/thomas/ti/ccsv8/utils/bin/gmake -k -j 8 clean -O

rm -rf "Host_A53_0.hex" "configPkg/linker.cmd" "configPkg/compiler.opt" "Host_A53_0.out"
rm -rf "InitMmu.o" "main.o"
rm -rf "InitMmu.d" "main.d"
rm -rf "configPkg/"
Finished clean

**** Build Finished ****

**** Build of configuration Debug for project Host_A53_0 ****

/home/thomas/ti/ccsv8/utils/bin/gmake -k -j 8 all -O

Building file: "../sysbios_a53.cfg"
Invoking: XDCtools
"/home/thomas/ti/xdctools_3_50_08_24_core/xs" --xdcpath="/home/thomas/ti/bios_6_73_01_01/packages;" xdc.tools.configuro -o configPkg -t gnu.targets.arm.A53F -p ti.platforms.cortexA:AM65X -r debug -c "/home/thomas/ti/gcc-linaro-7.2.1-2017.11-x86_64_aarch64-elf" "../sysbios_a53.cfg"
making package.mak (because of package.bld) ...
generating interfaces for package configPkg (because package/package.xdc.inc is older than package.xdc) ...
configuring sysbios_a53.xa53fg from package/cfg/sysbios_a53_pa53fg.cfg ...
generating custom ti.sysbios library makefile ...
Starting build of library sources ...
making /home/thomas/workspace_v8_ipc/Host_A53_0/src/sysbios/sysbios.aa53fg ...
gmake[1]: Entering directory `/home/thomas/workspace_v8_ipc/Host_A53_0/src/sysbios'
gmake[1]: Nothing to be done for `all'.
gmake[1]: Leaving directory `/home/thomas/workspace_v8_ipc/Host_A53_0/src/sysbios'
Build of libraries done.
cla53fg package/cfg/sysbios_a53_pa53fg.c ...
Finished building: "../sysbios_a53.cfg"

Building file: "../main.c"
Invoking: GNU Compiler
"/home/thomas/ti/gcc-linaro-7.2.1-2017.11-x86_64_aarch64-elf/bin/aarch64-elf-gcc" -c -mcpu=cortex-a53 -mtune=cortex-a53 -fno-exceptions -Dam6548 -Dcore0 -DAARCH64 -DSOC_AM6X -I"/home/thomas/workspace_v8_ipc/Host_A53_0" -I"/home/thomas/ti/gcc-linaro-7.2.1-2017.11-x86_64_aarch64-elf/aarch64-elf/include" -Og -g -gdwarf-2 -Wall -specs="nosys.specs" -MMD -MP -MF"main.d" -MT"main.o" @"configPkg/compiler.opt" -o"main.o" "../main.c"
Finished building: "../main.c"

Building file: "../InitMmu.c"
Invoking: GNU Compiler
"/home/thomas/ti/gcc-linaro-7.2.1-2017.11-x86_64_aarch64-elf/bin/aarch64-elf-gcc" -c -mcpu=cortex-a53 -mtune=cortex-a53 -fno-exceptions -Dam6548 -Dcore0 -DAARCH64 -DSOC_AM6X -I"/home/thomas/workspace_v8_ipc/Host_A53_0" -I"/home/thomas/ti/gcc-linaro-7.2.1-2017.11-x86_64_aarch64-elf/aarch64-elf/include" -Og -g -gdwarf-2 -Wall -specs="nosys.specs" -MMD -MP -MF"InitMmu.d" -MT"InitMmu.o" @"configPkg/compiler.opt" -o"InitMmu.o" "../InitMmu.c"
Finished building: "../InitMmu.c"

Building target: "Host_A53_0.out"
Invoking: GNU Linker
"/home/thomas/ti/gcc-linaro-7.2.1-2017.11-x86_64_aarch64-elf/bin/aarch64-elf-gcc" -mtune=cortex-a53 -fno-exceptions -Dam6548 -Dcore0 -DAARCH64 -DSOC_AM6X -Og -g -gdwarf-2 -Wall -specs="nosys.specs" -mcpu=cortex-a53 -Wl,-Map,"Host_A53_0.map" -nostartfiles -Wl,--defsym,CORE0=1 -Wl,--defsym,STACKSIZE=0x10000 -Wl,--defsym,HEAPSIZE=0x400 -o"Host_A53_0.out" "./InitMmu.o" "./main.o" -Wl,-T"../linker_a53.lds" -Wl,-T"configPkg/linker.cmd" -Wl,--start-group -lgcc -lrdimon -lc -Wl,--end-group
Finished building target: "Host_A53_0.out"

**** Build Finished ****

Project and Outfile:

3441.Host_A53_0.zip

over 6 years ago

0 Yordan Kovachev over 6 years ago

TI__Guru**** 161600 points

Hi,

You have created a target configuration file & connected to the board as explained here:
software-dl.ti.com/.../index_how_to_guides.html

right?

Then it is important to connect to the DMSC_Cortex_M3 first in order for the GEL file to initialize the board properly. Then you can connect to the arm core or cortex R5 core and run your code.

Best Regards,
Yordan

0 Thomas Dorsch over 6 years ago in reply to Yordan Kovachev

Expert 2601 points

Hi,

Yes, I have created target configuration file & connected as explained.

I do connect first to the DMSC_Cortex_M3. The issue stays the same.

Best regards,
Thomas

0 Yordan Kovachev over 6 years ago in reply to Thomas Dorsch

TI__Guru**** 161600 points

Sorry, I misunderstood your question.

Are you running linux or windows on your host PC? If this is linux, can you share the dmesg log immediately after CCS closes?

Best Regards,
Yordan

0 Yordan Kovachev over 6 years ago in reply to Yordan Kovachev

TI__Guru**** 161600 points

Also which CCS & Processor SDK RTOS version are you using?

0 Thomas Dorsch over 6 years ago in reply to Yordan Kovachev

Expert 2601 points

I run Windows 8 as Host System and use Lubuntu 17.10 as guest system in Vmware.
I use CCS v.8.2 (Version: 8.2.0.00007) on Lubuntu.
SDK RTOS: ti-processor-sdk-rtos-am65xx-evm-05.02.00.10-Linux-x86-Install

Here is my complete dmesg output after CCS crashed:
https://pastebin.com/9EztD3bG

Thank you for your support!

0 Yordan Kovachev over 6 years ago in reply to Thomas Dorsch

TI__Guru**** 161600 points

Ok, sorry but neither of these environments is tested with Processor SDK RTOS 05.02 & CCSv8.2.

The recommended host OS is: Ubuntu 16.04 & Windows 10 (possibly Windows 7). So please transfer to Ubuntu 16.04 as your virtual machine.

Best Regards,
Yordan

0 Thomas Dorsch over 6 years ago in reply to Yordan Kovachev

Expert 2601 points

All the provided examples for AM65X in Chip Support Library do work. I honestly doubt that a *buntu 17.10 is responsible for that effect.
Is your CCS not crashing when you load the provided out-file to the first A53 core of the AM6548 IDK?

0 Thomas Dorsch over 6 years ago in reply to Yordan Kovachev

Expert 2601 points

Hi Yordan,

I spend another couple of hours and installed a fresh Ubuntu 16.04.

I installed a fresh CCSv8.2 and followed the instructions at

I installed a fresh Processor SDK RTOS 05.02.00.10.

I created a target configuration to connect succesfully to my AM6548 IDK.

I followed step by step the RTOS A53 Guide:

When I load the outfile onto the first A53 core, CCS immeditaly closes without any message.

Everything behave exactly the same as I observed it with my first Lubuntu setup.

Can you reproduce this on your side?

0 Yordan Kovachev over 6 years ago in reply to Thomas Dorsch

TI__Guru**** 161600 points

Hi,

Your project crashes CCS in exactly the same manner on my side. I've notified the CCS team to take a look at this (attaching the crash log for their reference):

log

Best Regards,

Yordan

0 Thomas Dorsch over 6 years ago in reply to Yordan Kovachev

Expert 2601 points

HI Yordan,

thank you for confirming the issue and redirecting it.

Is there any possible workaround, to get a RTOS running on the A53 with CCS debugging?

Is there a estimate schedule when this issue could be fixed?

Best Regards and thanks in advance!

Thomas

0 Ki over 6 years ago in reply to Thomas Dorsch

TI__Guru**** 463471 points

Hi Thomas,
Thank you for the executable. Your issue appears related to a known issue with corrupted DWARF information in the generated executable. The Bug ID is: PRSDK-4654. On CCS Windows, the debugger complains that the symbols in the *.out file are corrupted and debug visibility is reduced. On CCS Linux, the debugger (along with the CCS IDE) crashes. I filed an additional bug regarding the crashing on Linux. Tracking ID: CCBT-2401

Thanks
ki

0 Thomas Dorsch over 6 years ago in reply to Ki

Expert 2601 points

Thank you for your detailed answer!

Processors

Processors forum

CCS/AM6548: CCS crashes when loading specific OUT-file