• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 101 subscribers
  • Views 557 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

CCS/AM6548: Can not connect to MCU_PULSAR_Cortex_R5_1

Thomas Dorsch
Expert 2570 points
Part Number: AM6548
Other Parts Discussed in Thread: AM5748

Tool/software: Code Composer Studio

Hello,

I try to connect via JTAG to MCU_PULSAR_Cortex_R5_1. It fails with the message
"Error connecting to the target:
(Error -1170 @ 0x0)
Unable to access the DAP. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK).
(Emulation package 8.0.903.4)"

I setup my CCS followed instructions by

1. Connection to M3 is successfull

2. Connection to MCU_PULSAR_Cortex_R5_0 is succesfull

3. Connection to CortexA53_0_0 is successfull

4. Connection to MCU_PULSAR_Cortex_R5_1 fails like described above.

I try to to some IPC-stuff and would like to use both R5F-Cores independently.

Can you help me out, or point me into a direction where to dig deeper, to get a JTAG connection to the second R5?

Best regards,

Thomas

  • 0
    TI__Guru** 115100 points

    Thomas,

    The device used on the EVM is an AM5748  part with R5F configured to come out of reset in Lockstep mode and not split mode.  The default setting for where the device comes in lockstep mode or split mode if controlled by an efuse on the device. Typically all devices that need safety would have the R5F come up in lockstep mode by default and non-safety enabled part will come with R5f in split mode. 

    As you may know, when the  R5F is in lockstep R5_1 acts like a diagnostic core and runs in the lockstep from timing perspective to the R5_0. In this mode, emulation to R5F_1 is not enabled independent of the core0 so CCS doesn`t let you connect to it. 

    Dual Cortex R5F in lockstep mode can be configured to run in split mode. On AM654x the processor configuration control. We have a GEL script for the M3, that can configure the R5F in split mode and also have provided the ability in the bootloader source to the R5F core in split mode.

    GEL script:

    The script that configures split mode is called "Change_MCUSS_to_SplitMode"

    Using bootloader: 

    http://software-dl.ti.com/processor-sdk-rtos/esd/docs/latest/rtos/index_Foundational_Components.html#am65x 

    Since you are running IPC examples and using CCS Advanced setup, you may need to add the GEL script function in the script launch_am65xx.js. I have provided you the updated script from my setup for reference . Line 99 has the update that invokes the split mode configuration.

    launch_am65xx.zip

    Regards,

  • 0 in reply to Rahul Prabhu
    Expert 2570 points

    Hi Rahul,

    thank you very much, I appreciate your detailed answer!

    Regards,

    Thomas