• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Answers 1 answer
  • Subscribers 102 subscribers
  • Views 371 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.

Original question:

SK-AM64: Error connecting to the target from CCS 10.3.1

SK-AM64: AM64x-SK (HS-FSversion): Error connecting to the target: (Error -1170 @ 0x0) Unable to access the DAP.

Guenter Egle
Prodigy 110 points

Part Number: SK-AM64

Hello, 

I am using SK-AM64B board which is red in colour and is marked with a "M2" sticker (the user guide in the website mentions M1 sticker).

I am trying SOC Initialization using CCS Scripting by following this link: https://software-dl.ti.com/mcu-plus-sdk/esd/AM64X/latest/exports/docs/api_guide_am64x/EVM_SETUP_PAGE.html

CCS version:  12.2.0

MCU+ SDK version: AM64x 08.05.00.24

I have created a target configuration by selecting Connection as "Texas Instruments XDS110 USB Debug Probe" and Board or Device as "AM64x". 

After launching the target configuration when I execute the command "loadJSFile C:\ti\mcu_plus_sdk_am64x_08_05_00_24\tools\ccs_load\am64x\load_dmsc_hsfs.js", I get the following error:

I have tried connecting JTAG cable after powering up the board, as mentioned in the EVM SETUP PAGE but it doesn't work. I have also ensured that my board switches are in NOBOOT MODE, and the cores are disconnected. The environment variable path is also set as mentioned in the instructions.

Interestingly, when i change the bootmode switches to OSPI mode (leaving all other settings the same as above), the error doesn't occur, the script starts running but then times out. Here is the scripting console output:

There is no output on the CCS console.

I am able to do the SOC Initialization using UART uniflash method. I just wanted to try the CCS scripting method as well.

Thanks in advance

  • 0
    TI__Mastermind 27581 points

    Hello Guenter,

    To initialize a HS-FS board using CCS, we have to boot the board in DEVBOOT mode. Please refer to the following for the detailed guide

    Application boot using CCS + GELs

    Regards,

    Prashant

  • 0 in reply to Prashant Shivhare
    Prodigy 110 points

    Hello, 

    I tried switching the board to DEVBOOT mode and trying to run the load_dmsc_hsfs.js script. I am still getting the below output in the scripting console:

    js:> loadJSFile C:\ti\mcu_plus_sdk_am64x_08_05_00_24\tools\ccs_load\am64x\load_dmsc_hsfs.js
    Connecting to MCU Cortex_R5_0!
    Writing While(1) for R5F
    Running the board configuration initialization from R5!
    Error loading "C:\ti\mcu_plus_sdk_am64x_08_05_00_24/tools/ccs_load/am64x/sciclient_ccs_init.release.out": File: C:\ti\mcu_plus_sdk_am64x_08_05_00_24/tools/ccs_load/am64x/sciclient_ccs_init.release.out: Load failed. (C:\ti\mcu_plus_sdk_am64x_08_05_00_24\tools\ccs_load\am64x\load_dmsc_hsfs.js#148)

    The CCS console has the following output:

    MAIN_Cortex_R5_0_0: GEL Output: CPU reset (soft reset) has been issued through GEL.
    MAIN_Cortex_R5_0_0: Trouble Writing Memory Block at 0x0 on Page 0 of Length 0x40: (Error -1065 @ 0x40) Unable to access device memory. Verify that the memory address is in valid memory. If error persists, confirm configuration, power-cycle board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 9.11.0.00128)
    MAIN_Cortex_R5_0_0: File Loader: Verification failed: Target failed to write 0x00000000
    MAIN_Cortex_R5_0_0: GEL: File: C:\ti\mcu_plus_sdk_am64x_08_05_00_24/tools/ccs_load/am64x/sciclient_ccs_init.release.out: Load failed.

    I have a doubt, that the picture in the HSFS Migration Guide shows the picture of AM64x-EVM, but I am working on AM64x-SK. Could you please confirm whether the DEVBOOT mode switch positions are the same for both the boards? And if thats not the case then what else can I try to resolve this issue?

    Thanks in advance

  • +1 in reply to Guenter Egle
    TI__Mastermind 27581 points

    Hello Guenter,

    The Switches (SW2 & SW3) positions may differ from board to baord. But, the bootmode pins (B0-B15) values (on/off) remains the same across the different boards. The exact setting for DEVBOOT mode is:

    SW2 (B0-B7): 11011110

    SW3 (B8-B15): 00000000

    The bootmode pins (B0-B15) are labeled on the board. Please make sure to set them according to the above setting. You may also share the screenshot of the bootmode switch settings on your board. I will see and confirm if they are right.

    Regards,

    Prashant

  • 0 in reply to Guenter Egle
    TI__Genius 13783 points

    Hi Guenter,

    Please follow this E2E where you will find the desired answer. (e2e.ti.com/.../sk-am64b-ipc-failed-on-sk-am64b-hs-fs-version)

    BR Vaibhav

  • 0 in reply to Prashant Shivhare
    Prodigy 110 points

    Thank you Prashant and Vaibhav. My issue has been solved.