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.

SK-AM62: CCS Link failed

Part Number: SK-AM62

Hi, TI Expert

I follow this page to start CCS M4 core programming, but I found CCS link failed to each core.

https://software-dl.ti.com/mcu-plus-sdk/esd/AM62X/09_00_00_19/exports/docs/api_guide_am62x/GETTING_STARTED.html#autotoc_md7

Error message as below.

Already follow this link, section "Troubleshooting EVM issues", try to connect the JTAG cable after board is powered on, but it does not work for me

https://software-dl.ti.com/mcu-plus-sdk/esd/AM62X/09_00_00_19/exports/docs/api_guide_am62x/EVM_SETUP_PAGE.html#BOOTMODE_NOBOOT

My board :

1. AM62x SKEVM PROC142A

2. debug Boot mode : switch to No boot mode

3. Environment  : CCS 12.4 + ubuntu

4. Already check XDS110 connect success

Do I miss some thing? 

Need suggestion.

Many Thanks

Gibbs

  • Hello Gibbs,

    Thanks for reaching out to Texas Instruments E2E support forum.

    As of now, development using NOBOOT mode on AM62x devices are not supported. Can you please try the other methods of initializing the SOC?

    To initialize SOC using SBL, please refer SBL Initialization.

    To initialize SOC using SPL, please refer SPL Initialization.

    Regards,

    Tushar

  • Hi, Tushar

    Thanks replies

    I already finish SBL initialization, and try to connect CCS got error as below.

    Not sure the reason, May you give me suggesstion

    Many Thanks

    Gibbs

  • Hello Gibbs,

    Thanks for your response.

    I already finish SBL initialization, and try to connect CCS got error as below.

    After initializing the EVM, Are you able to see the logs similar to below provided screenshot.

    Have you made any changes to the default hello_world example?

    Can you please share the example.syscfg and linker.cmd file of the project?

    Regards,

    Tushar

  • Hi, Tushar

    Show my uart log, same as yours.

    Welcome to minicom 2.7.1
    
    OPTIONS: I18n 
    Compiled on Dec 23 2019, 02:06:26.
    Port /dev/ttyUSB0, 13:43:04
    
    Press CTRL-A Z for help on special keys
    
    
    Starting NULL Bootloader ... 
    
    DMSC Firmware Version 9.0.5--v09.00.05 (Kool Koala)
    DMSC Firmware revision 0x9
    DMSC ABI revision 3.1
    
    INFO: Bootloader_runCpu:162: CPU m4f0-0 is initialized to 400000000 Hz !!!
    INFO: Bootloader_runCpu:162: CPU a530-0 is initialized to 1250000000 Hz !!!
    INFO: Bootloader_runCpu:162: CPU a530-1 is initialized to 1250000000 Hz !!!
    INFO: Bootloader_loadSelfCpu:215: CPU r5f0-0 is initialized to 400000000 Hz !!!
    INFO: Bootloader_JumpSelfCpu:234: All done, jumping self ...

    I do not change any setting, import default project

    PLS check attachment file

    7848.linker.cmd1663.example.syscfg

    CCS error as below.

    ortexA53_0: File Loader: Verification failed: Values at address 0x0000000000000000 do not match Please verify target memory and memory map.
    CortexA53_0: GEL: File: /home/gibbs/ti/CCS_workspace_v1240/hello_world_am62x-sk_m4fss0-0_nortos_ti-arm-clang/Debug/hello_world_am62x-sk_m4fss0-0_nortos_ti-arm-clang.out: a data verification error occurred, file load failed.

    Thanks

    Gibbs

  • Hello Gibbs, 

    Thanks for sharing the additional details. Let me check this and revert back. 

    Meanwhile I am also providing the hello world binary below. Can you please try loading this once and let me know the results?

    Binary - hello_world_am62x_r5fss0-0_nortos.out

    Regards,

    Tushar

  • Hi, Tushar

    I direct replace your *.out in my binary debug folder. Result is the same.

    So, I think it should be environment setting problems, not sure the reason.

    My CCS version: 12.4.0.00007 

    I will leave office until 2/15, replies will be delay.

    Many Thanks

    Gibbs

  • Hello Gibbs,

    Can you please tell on which core are you loading the binary?

    From the GEL logs shown in above screenshot, it seems that you are loading the M4F core binary on A53 core. Please load the binary on M4F_1 core.

    Please let me know if this works.

    Thanks & Regards,

    Tushar

  • Hi, Tushar

    Problem solved, base on concept of view, you need to make sure two things.

    1. Does m4f0_0 already init?

    * SBL sample code include m4 core init, so you need to flash SBL into OSPI flash and switch to OSPI boot for CCS debugging.

    * SPL (Linux kernel) will load  "am62-mcu-m4f0_0-fw", it (FW) includes M4 core init, so you must wait linux boot complete for CCS debugging.

    2. How to make sure you load correct FW to correct core (M4) in CCS?

    When you import default sample project, do not use default setting, you need modify check box as below.

    You must connect one of each core (for example : M4) first, and then success connect to R5 or A53 by CCS JTAG

    By the way, another question. How to load "am62-mcu-m4f0_0-fw" in u-boot?

    Because we may face Linux kernel boot failed, but we still need to debug another core when u-boot complete.

    Thanks

    Gibbs

  • Hello Gibbs,

    Thanks for your response.

    By the way, another question. How to load "am62-mcu-m4f0_0-fw" in u-boot?

    Because we may face Linux kernel boot failed, but we still need to debug another core when u-boot complete.

    Can you please create a separate thread for above query? It will be helpful for the future readers who will face similar kind of issue.

    It will also help us assign the thread to domain expert. 

    Regards,

    Tushar