• State Resolved
  • Replies 14 replies
  • Subscribers 30 subscribers
  • Views 245 views
  • Users 0 members are here
Support feedback
Options
Options
Related

AM2612: AM2612 Using CCS 12.8.1 JATG Error and Build Error

Li Robert
Prodigy 70 points
Part Number: AM2612
Other Parts Discussed in Thread: LP-AM261, SYSCONFIG

Tool/software:


Hello, I encountered the following problem


CCS 12.8.1


B:\ti\ccs1281\ccs/utils/cygwin/rm -f B:/Robert_Li/Desktop/Root/ARG8000/AM2612_Code/rti_led_blink_am261x-lp_r5fss0-0_nortos_ti-arm-clang/Release/rti_led_blink_am261x-lp_r5fss0-0_nortos_ti-arm-clang.rprc_tmp
Boot multi-core ELF image: am261x:r5fss0-0:nortos:ti-arm-clang B:/Robert_Li/Desktop/Root/ARG8000/AM2612_Code/rti_led_blink_am261x-lp_r5fss0-0_nortos_ti-arm-clang/Release/rti_led_blink_am261x-lp_r5fss0-0_nortos_ti-arm-clang.mcelf ...
python B:/ti/mcu_plus_sdk_am261x_10_02_00_15/tools/boot/multicore-elf/genimage.py --core-img=0:Release/rti_led_blink_am261x-lp_r5fss0-0_nortos_ti-arm-clang.out --output=B:/Robert_Li/Desktop/Root/ARG8000/AM2612_Code/rti_led_blink_am261x-lp_r5fss0-0_nortos_ti-arm-clang/Release/rti_led_blink_am261x-lp_r5fss0-0_nortos_ti-arm-clang.mcelf --merge-segments=true --tolerance-limit=0 --ignore-context=false --xip=0x60000000:0x68000000 --xlat=none --max-segment-size=8192
makefile_ccs_bootimage_gen:87: recipe for target 'all' failed
Traceback (most recent call last):
File "B:\ti\mcu_plus_sdk_am261x_10_02_00_15\tools\boot\multicore-elf\genimage.py", line 40, in <module>
from modules.otfaecc_structs import *
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "B:\ti\mcu_plus_sdk_am261x_10_02_00_15\tools\boot\multicore-elf\modules\otfaecc_structs.py", line 35, in <module>
from construct import Struct, Int16ul, Int16ub, \
ModuleNotFoundError: No module named 'construct'
gmake[3]: *** [all] Error 1
gmake[2]: [post-build] Error 2 (ignored)
makefile:168: recipe for target 'post-build' failed

  • 0
    TI__Mastermind 44834 points

    Hi,

    This error is occuring as the dependent pythion module construct is not installed.

  • 0 in reply to Nilabh Anand
    TI__Mastermind 44834 points

    Please follow this e2e for the required fix:

    Resolve post-build errors for AM261x MCU+ SDK

  • 0 in reply to Nilabh Anand
    Prodigy 70 points

    OK~I’ve fixed part of the problem.

    C:\Windows\system32>python -m pip install construct

    C:\Windows\system32>python -m pip install pyelftools

    C:\Windows\system32>python -m pip install cryptography


    I read the information in
    mcu_plus_sdk_am261x_10_02_00_15/docs/api_guide_am261x/SDK_DOWNLOAD_PAGE.html,
    but I still encounter a JTAG error:

    Cortex_R5_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 20.0.0.3178) Cortex_R5_0: File Loader: Verification failed: Target failed to write 0x00000000 Cortex_R5_0: GEL: File: B:\Robert_Li\OneDrive\Root\ARG8000\AM2612_Code\rti_led_blink_am261x-lp_r5fss0-0_nortos_ti-arm-clang\Release\rti_led_blink_am261x-lp_r5fss0-0_nortos_ti-arm-clang.out: Load failed.



  • 0 in reply to Li Robert
    Prodigy 70 points

    I checked the documentation at mcu_plus_sdk_am261x_10_02_00_15/docs/api_guide_am261x/CCS_SETUP_PAGE.html and updated the Sitara device support. I also tried changing TCK to 1 MHz, which solved some issues, but I’m still getting the following error:

    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 20.0.0.3178)


    Thank you very much.
  • 0 in reply to Li Robert
    TI__Mastermind 44834 points

    Hi LI,

    By any chance do you have any another LP which you can test?

    Another suggestion is to test once with CCS 12.8.1, but also make sure you have done the steps mentioned here after you install CCS 12.8.1

    e2e.ti.com/.../faq-am2612-device-cortex-r-am261x-is-not-currently-recognized-ccs-is-not-detecting-am261x

  • 0 in reply to Nilabh Anand
    Prodigy 70 points

    Dear Nilabh,
    I don’t have another LP board to test with. This is a newly received board, model LP-AM261 PROC193E2.

    Regarding the installation steps, the links you provided are the same as (or even more detailed than) the instructions in the SDK:

    As a side note, my Sitara MCU Device Support for Windows version is 1.5.0.

    Also, with CCS 20 I did not encounter the JTAG error (Error -1170 @ 0x0) Unable to access the DAP). However, debugging felt sluggish — for example, when pressing Ctrl to jump through variables, sometimes the variables could not be selected or copied. This is why I strongly want to use CCS 12.8.1 instead.

    Moreover, the SDK documentation itself also uses CCS 12.8.1.

  • 0 in reply to Li Robert
    TI__Mastermind 44834 points

    Robert, Apologies that you are facing these issues:

    1. Can you restart your PC once and try? Sometimes, XDS drivers refresh after a restart?

    2. Can you once try updating the XDS firmware as mentioned on this thread e2e.ti.com/.../lp-am261-unable-to-flash-with-jtag-error--1170

    Let me know your observation.

  • 0 in reply to Nilabh Anand
    Prodigy 70 points

    Dear Nilabh,

    First item: I tried it already.
    The same error pops up:

    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 20.0.0.3178)

    Second item: I tried updating to 3.0.0.32 and 3.0.0.38.
    ccs1281\ccs\ccs_base\common\uscif\xds110\firmware_3.0.0.32.bin

    Current version is:

    xdsdfu.exe -e
    Device Name: XDS110 Embed with CMSIS-DAP
    Version: 3.0.0.38
    Manufacturer: Texas Instruments
    Serial Num: S26G0014
    Mode: Runtime Configuration: Standard

  • 0 in reply to Li Robert
    TI__Mastermind 44834 points

    Hi Robert,

    I think this might be related to power, I am seeing this issue only when power is unstable,

    Could you please recheck the power supply.

  • 0 in reply to Nilabh Anand
    Prodigy 70 points

    Dear Nilabh,

    I have tried both 20W PD and 65W PD, but the results are the same.

    Here is a summary of the two cases:
    Using LP-AM261 PROC193E2.
    XDS110 Version: 3.0.0.38

    Case 1:

    • CCS12.8.1

    • SysConfig 1.23.0

    • MCU+SDK for AM261x 10.2.0.15

    • Compiler TI Clang v4.0.1.LTS

    • Sitara MCU Device Support File (Windows) v1.5.0

    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 20.0.0.3178)

    Case 2:

    • CCS 20.2.0

    • SysConfig 1.23.0

    • MCU+SDK for AM261x 10.2.0.15

    • Compiler TI Clang v4.0.3.LTS

    • AM2x Arm(R)-based MCU Device Support 1.5.0

    When creating a new project for the first time, the Debug configuration file cannot be found.
    After restarting CCS, JTAG works normally, but it often disconnects during use.
    Additionally, using Ctrl + left mouse click on a variable often causes the variable to become unselectable/unable to copy.

    According to the SDK documentation, CCS12.8.1 is recommended, and I also prefer to use 12.8.1 for development since it has fewer bugs.
    https://software-dl.ti.com/mcu-plus-sdk/esd/AM261X/10_02_00_15/exports/docs/api_guide_am261x/CCS_SETUP_PAGE.html

  • 0 in reply to Li Robert
    TI__Mastermind 44834 points
    Li Robert said:

    Case 1:

    • CCS12.8.1

    • SysConfig 1.23.0

    • MCU+SDK for AM261x 10.2.0.15

    • Compiler TI Clang v4.0.1.LTS

    • Sitara MCU Device Support File (Windows) v1.5.0

    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 20.0.0.3178)

    Hi Robert,

    Could you please try to re install the CCS 12.8.1 and restart your PC and try again,

    Seems like this is specific to your PC or CCS installation,Please let me know your observations.

  • 0 in reply to Nilabh Anand
    Prodigy 70 points

    Dear Nilabh,
    I tried reinstalling CCS 12.8.1 and rebooting the PC, as well as changing the board connection.
    The situation is still the same.

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

  • 0 in reply to Nilabh Anand
    Prodigy 70 points

    Dear Nilabh,
    Today I tried installing CCS on another computer, and the same issue occurred.

    • First computer: Windows 10 Professional

    • Second computer: Windows 11 Professional

    Versions used:

    • CCS 12.8.1

    • SysConfig 1.23.0

    • MCU+SDK for AM261x 10.2.0.15

    • Compiler TI Clang v4.0.1.LTS

    • Sitara MCU Device Support File (Windows) v1.5.0

  • 0 in reply to Li Robert
    Prodigy 70 points

    Dear Nilabh,
    I found the issue. The root cause of the DAP error is that the core cannot be read. I discovered that the M4 core cannot be accessed, so unchecking this option before starting allows debugging to proceed. I tried the same situation on CCS20, and the R1 core could not be read. Thank you.