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.

TMS320F2800137: 0x3FD4D0 (no symbol are defined)

Part Number: TMS320F2800137
Other Parts Discussed in Thread: SFRA, TIDM-02010, , C2000WARE

Tool/software:

Dear Sir,

Please find the attached of below error.

i am using TI hardware (TIDM-02010E32)

Please find below flash memory file.

/*
// TI File $Revision: /main/3 $
// Checkin $Date: Agu 1, 2017   13:45:43 $
//
// FILE:    F2800137_FLASH_LIB.cmd
//
// TITLE:   Linker Command File For F2800137 examples that run out of RAM
//
//
//          Keep in mind that LS0, and LS1 are protected by the code
//          security module.
//
//          What this means is in most cases you will want to move to
//          another memory map file which has more memory defined.
//
*/

/*========================================================= */
/* Define the memory block start/length for the F280013x
   PAGE 0 will be used to organize program sections
   PAGE 1 will be used to organize data sections

   Notes:
         Memory blocks on F2800137 are uniform (ie same
         physical memory) in both PAGE 0 and PAGE 1.
         That is the same memory region should not be
         defined for both PAGE 0 and PAGE 1.
         Doing so will result in corruption of program
         and/or data.

         Contiguous SARAM memory blocks can be combined
         if required to create a larger memory block.
*/

MEMORY
{
   BEGIN            : origin = 0x00080000, length = 0x00000002
   BOOT_RSVD        : origin = 0x00000002, length = 0x00000126

/* RAMLS1           : origin = 0x0000A000, length = 0x00001FF8 */
   RAMLS1P          : origin = 0x0000A000, length = 0x00001FF8
// RAMLS1_RSVD      : origin = 0x0000BFF8, length = 0x00000008 /* Reserve and do not use for code as per the errata advisory "Memory: Prefetching Beyond Valid Memory" */

   RESET              : origin = 0x003FFFC0, length = 0x00000002

   /* Flash sectors */
/* FLASH_BANK0_SEC_0_7     : origin = 0x080002, length = 0x1FFE */ /* on-chip Flash */
   FLASHBANK0_BOOT	       : origin = 0x080002, length = 0x1FFE	 /* remote update */

/* FLASH_BANK0_SEC_8_15    : origin = 0x082000, length = 0x2000 */ /* on-chip Flash */
/* FLASH_BANK0_SEC_16_23   : origin = 0x084000, length = 0x2000 */ /* on-chip Flash */
   FLASHBANK0_FAST	       : origin = 0x082000, length = 0x04000

/* FLASH_BANK0_SEC_24_31   : origin = 0x086000, length = 0x2000 */ /* on-chip Flash */
   FLASHBANK0_DATA 	       : origin = 0x086000, length = 0x2000	   /* constant data */

/* FLASH_BANK0_SEC_32_29   : origin = 0x088000, length = 0x2000 */ /* on-chip Flash */
/* FLASH_BANK0_SEC_40_47   : origin = 0x08A000, length = 0x2000 */ /* on-chip Flash */
/* FLASH_BANK0_SEC_48_55   : origin = 0x08C000, length = 0x2000 */ /* on-chip Flash */
/* FLASH_BANK0_SEC_56_63   : origin = 0x08E000, length = 0x2000 */ /* on-chip Flash */
/* FLASH_BANK0_SEC_64_71   : origin = 0x090000, length = 0x2000 */ /* on-chip Flash */
/* FLASH_BANK0_SEC_72_79   : origin = 0x092000, length = 0x2000 */ /* on-chip Flash */
/* FLASH_BANK0_SEC_80_87   : origin = 0x094000, length = 0x2000 */ /* on-chip Flash */
/* FLASH_BANK0_SEC_88_95   : origin = 0x096000, length = 0x2000 */ /* on-chip Flash */
/* FLASH_BANK0_SEC_96_103  : origin = 0x098000, length = 0x2000 */ /* on-chip Flash */
/* FLASH_BANK0_SEC_104_111 : origin = 0x09A000, length = 0x2000 */ /* on-chip Flash */
/* FLASH_BANK0_SEC_112_119 : origin = 0x09C000, length = 0x2000  /* on-chip Flash */
/* FLASH_BANK0_SEC_120_127 : origin = 0x09E000, length = 0x1FF0  /* on-chip Flash */
   FLASHBANK0_CODE	  	   : origin = 0x088000, length = 0x18FF0 /* control code */

/* FLASHBANK0_CODE	  	   : origin = 0x09A000, length = 0x05FF0 */  /* control code */
/* FLASH_BANK0_SEC_127_RSVD : origin = 0x0A0FF0, length = 0x0010 */  /* Reserve and do not use for code as per the errata advisory "Memory: Prefetching Beyond Valid Memory" */

   RAMM0S          	  : origin = 0x00000128, length = 0x00000118	/* stack 0x00000118 */
   RAMM1D         	  : origin = 0x00000240, length = 0x000005B8	/* on-chip RAM block M1 */
   RAMM1_RSVD         : origin = 0x000007F8, length = 0x00000008    /* Reserve and do not use for code as per the errata advisory "Memory: Prefetching Beyond Valid Memory" */

   RAMLS0F        	  : origin = 0x00008000, length = 0x00000600	/* Reserve for FAST */
   RAMLS0D        	  : origin = 0x00008600, length = 0x00001A00
}


SECTIONS
{
   .reset           : > RESET,  		    TYPE = DSECT /* not used, */
   codestart		: > BEGIN,     			ALIGN(4)

   GROUP
   {
   	.TI.ramfunc {
#if defined(MOTOR1_FAST) || defined(MOTOR2_FAST)
       -l est_trajState_coff.lib<est_setupTrajState.obj> (.text)
#endif

#if defined(SFRA_ENABLE)
       -l sfra_f32_tmu_coff.lib<sfra_f32_tmu_collect.obj> (.text)
       -l sfra_f32_tmu_coff.lib<sfra_f32_tmu_inject.obj> (.text)
#endif
   			   }
   	dclfuncs
    dcl32funcs
   }                          LOAD >  FLASHBANK0_CODE,
                              RUN  >  RAMLS1P,
				              LOAD_START(RamfuncsLoadStart),
				              LOAD_SIZE(RamfuncsLoadSize),
				              LOAD_END(RamfuncsLoadEnd),
				              RUN_START(RamfuncsRunStart),
				              RUN_SIZE(RamfuncsRunSize),
				              RUN_END(RamfuncsRunEnd),
                              ALIGN(8)

    ctrlfuncs            :    LOAD >  FLASHBANK0_CODE,
                              RUN  >  RAMLS1P,
                              LOAD_START(loadStart_ctrlfuncs),
                              LOAD_END(loadEnd_ctrlfuncs),
                              LOAD_SIZE(loadSize_ctrlfuncs),
                              RUN_START(runStart_ctrlfuncs),
                              RUN_END(runEnd_ctrlfuncs),
                              RUN_SIZE(runSize_ctrlfuncs),
                              ALIGN(8)

   .text            : > FLASHBANK0_CODE,	ALIGN(4)
   .cinit           : > FLASHBANK0_CODE,	ALIGN(4)
   .switch          : > FLASHBANK0_CODE,	ALIGN(4)
   .cio				: > FLASHBANK0_CODE
   .pinit           : > FLASHBANK0_CODE,	ALIGN(4)
   .const           : > FLASHBANK0_CODE,  	ALIGN(4)
   .init_array      : > FLASHBANK0_CODE,	ALIGN(4)

   .stack           : > RAMLS0D //RAMM0S
   .bss             : > RAMM1D
   .bss:output      : > RAMM1D
   .bss:cio         : > RAMM1D
   .data            : > RAMM1D
   .sysmem          : > RAMM1D

    fastCode 		: > FLASHBANK0_FAST
    {
         --library=fast_pmsm_lib.lib (.text)
    }

          /*  Allocate IQ math areas: */
   IQmath           : > FLASHBANK0_CODE, 	ALIGN(8)
   IQmathTables     : > FLASHBANK0_CODE,	ALIGN(8)

   	prms_data 		     : > FLASHBANK0_DATA

    est_data             : >  RAMLS0F,
                              LOAD_START(loadStart_est_data),
                              LOAD_END(loadEnd_est_data),
                              LOAD_SIZE(loadSize_est_data)
    user_data            : >  RAMLS0D,
                              LOAD_START(loadStart_user_data),
                              LOAD_END(loadEnd_user_data),
                              LOAD_SIZE(loadSize_user_data)
    sys_data             : >  RAMLS0D,
                              LOAD_START(loadStart_sys_data),
                              LOAD_END(loadEnd_sys_data),
                              LOAD_SIZE(loadSize_sys_data)
    pfc_data             : >  RAMLS0D,
                              LOAD_START(loadStart_pfc_data),
                              LOAD_END(loadEnd_pfc_data),
                              LOAD_SIZE(loadSize_pfc_data)
    foc_data             : >  RAMLS0D,
                              LOAD_START(loadStart_foc_data),
                              LOAD_END(loadEnd_foc_data),
                              LOAD_SIZE(loadSize_foc_data)
    motor_data           : >  RAMLS0D,
                              LOAD_START(loadStart_motor_data),
                              LOAD_END(loadEnd_motor_data),
                              LOAD_SIZE(loadSize_motor_data)
    dmaBuf_data          : >  RAMLS0D,
                              LOAD_START(loadStart_dmaBuf_data),
                              LOAD_END(loadEnd_dmaBuf_data),
                              LOAD_SIZE(loadSize_dmaBuf_data)
    vibc_data            : >  RAMLS0D,
                              LOAD_START(loadStart_vibc_data),
                              LOAD_END(loadEnd_vibc_data),
                              LOAD_SIZE(loadSize_vibc_data)
    sfra_data            : >  RAMLS0D,
                              LOAD_START(loadStart_sfra_data),
                              LOAD_END(loadEnd_sfra_data),
                              LOAD_SIZE(loadSize_sfra_data)
    datalog_data         : >  RAMLS0D,
                              LOAD_START(loadStart_datalog_data),
                              LOAD_END(loadEnd_datalog_data),
                              LOAD_SIZE(loadSize_datalog_data)
    dbgc_data            : >  RAMLS0D,
                              LOAD_START(loadStart_dbgc_data),
                              LOAD_END(loadEnd_dbgc_data),
                              LOAD_SIZE(loadSize_dbgc_data)
}

/*
//===========================================================================
// End of file.
//===========================================================================
*/

Please resolved above issue on priority.

  • Without further information on the context in which this issue is happening, I cannot help.

    1. Was the code working prior to this?
    2. What happened immediately prior to this error?
    3. What pre-defined symbols are you using?

    Regards,
    Jason Osborn

  • Dear Jason,

    ISSUE :code Not free run TI board(TIDM-02010E32) to test the functionality

    build process is ok

    if i press F8 button(free run) then again stuck & there is mention no symbol are define.

     

    Upon connection of debugger to target hardwware & checking TEST CONNECTION. The debug connection is becoming successful.

    Considering debug connection are correct, Every time it should no symbols are define. 

    What pre-defined symbols are you using?

    i will check all hardware connections many times & it is OK.

    for any information is required then used above video, attached files & below Texas code.

    AC_ODU_Project_28022024.rar

    Please resolved this issue why this code not run free?? 

    because our project is at last stage.

  • Hello,

    Thank you for the additional details.

    • Are there any warnings in the build process at all?
    • What is the ISR frequency?
    • Please put a breakpoint in sys_main.c at the following lines:
      • runMotor1OffsetsCalculation(-)
      • HAL_enableGlobalInts(-)

    When you hit 'run', let me know if it reaches the first breakpoint. If it does, hit run again, and let me know if it hits the second. This will help in tracking down the root cause of the issue.

    Regards,
    Jason Osborn

  • Dear Sir,

    • Are there any warnings in the build process at all?

    • What is the ISR frequency?:

    When you hit 'run', let me know if it reaches the first breakpoint. If it does, hit run again, and let me know if it hits the second. This will help in tracking down the root cause of the issue. : press F8 agaain stop and again stop.

    • No warnings, understood.
    • Please show the PWM frequency as well.
    • To clarify, you're saying that the code was stopped at each breakpoint?
      • If you hit 'run' again after the second breakpoint, does the code hit the ESTOP0 again? (The issue reported in the first post of this thread)

    Regards,
    Jason Osborn

  • Dear Sir,

    To clarify, you're saying that the code was stopped at each breakpoint?
    • If you hit 'run' again after the second breakpoint, does the code hit the ESTOP0 again? (The issue reported in the first post of this thread)

    Please see above video as of your refrence

    Please show the PWM frequency as well.

    Please find code.

    8203.AC_ODU_Project_28022024.rar

  • The video appears to begin with the system already in the error state. Is it in this state from the moment that you hit the Debug button (or the F11 key, which is also Debug) ?

    Regards,
    Jason Osborn

  • Dear Sir,

    After pressing F11 key then debug get terminate & shows below attached error for your reference.

    Please find video.

    Please check error.

    C28xx_CPU1: Trouble Reading Register ST1: (Error -1137 @ 0x6) Device is held in reset. Take the device out of reset, and retry the operation. (Emulation package 9.13.0.00201)
    C28xx_CPU1: Trouble Reading Register PC: (Error -1137 @ 0x0) Device is held in reset. Take the device out of reset, and retry the operation. (Emulation package 9.13.0.00201)
    C28xx_CPU1: Trouble Reading Register ST1: (Error -1137 @ 0x6) Device is held in reset. Take the device out of reset, and retry the operation. (Emulation package 9.13.0.00201)
    C28xx_CPU1: Trouble Reading Register PC: (Error -1137 @ 0x0) Device is held in reset. Take the device out of reset, and retry the operation. (Emulation package 9.13.0.00201)
    C28xx_CPU1: Trouble Reading Register ST1: (Error -1137 @ 0x6) Device is held in reset. Take the device out of reset, and retry the operation. (Emulation package 9.13.0.00201)
    C28xx_CPU1: Trouble Reading Register PC: (Error -1137 @ 0x0) Device is held in reset. Take the device out of reset, and retry the operation. (Emulation package 9.13.0.00201)
    C28xx_CPU1: Trouble Reading Register ST1: (Error -1137 @ 0x6) Device is held in reset. Take the device out of reset, and retry the operation. (Emulation package 9.13.0.00201)
    C28xx_CPU1: Can't Run Target CPU: (Error -1137 @ 0x27D) Device is held in reset. Take the device out of reset, and retry the operation. (Emulation package 9.13.0.00201)
    C28xx_CPU1: Trouble Reading Register PC: (Error -1137 @ 0x0) Device is held in reset. Take the device out of reset, and retry the operation. (Emulation package 9.13.0.00201)
    C28xx_CPU1: Trouble Reading Register ST1: (Error -1137 @ 0x6) Device is held in reset. Take the device out of reset, and retry the operation. (Emulation package 9.13.0.00201)
    C28xx_CPU1: Can't Run Target CPU: (Error -1137 @ 0x269) Device is held in reset. Take the device out of reset, and retry the operation. (Emulation package 9.13.0.00201)
    C28xx_CPU1: Trouble Reading Register PC: (Error -1137 @ 0x0) Device is held in reset. Take the device out of reset, and retry the operation. (Emulation package 9.13.0.00201)
    C28xx_CPU1: Trouble Reading Register ST1: (Error -1137 @ 0x6) Device is held in reset. Take the device out of reset, and retry the operation. (Emulation package 9.13.0.00201)

  • Dear Sir,

    After pressing F11 key then debug get terminate & shows below attached error for your reference.

    Please find video.

    Please check error.

    C28xx_CPU1: Trouble Reading Register ST1: (Error -1137 @ 0x6) Device is held in reset. Take the device out of reset, and retry the operation. (Emulation package 9.13.0.00201)
    C28xx_CPU1: Trouble Reading Register PC: (Error -1137 @ 0x0) Device is held in reset. Take the device out of reset, and retry the operation. (Emulation package 9.13.0.00201)
    C28xx_CPU1: Trouble Reading Register ST1: (Error -1137 @ 0x6) Device is held in reset. Take the device out of reset, and retry the operation. (Emulation package 9.13.0.00201)
    C28xx_CPU1: Trouble Reading Register PC: (Error -1137 @ 0x0) Device is held in reset. Take the device out of reset, and retry the operation. (Emulation package 9.13.0.00201)
    C28xx_CPU1: Trouble Reading Register ST1: (Error -1137 @ 0x6) Device is held in reset. Take the device out of reset, and retry the operation. (Emulation package 9.13.0.00201)
    C28xx_CPU1: Trouble Reading Register PC: (Error -1137 @ 0x0) Device is held in reset. Take the device out of reset, and retry the operation. (Emulation package 9.13.0.00201)
    C28xx_CPU1: Trouble Reading Register ST1: (Error -1137 @ 0x6) Device is held in reset. Take the device out of reset, and retry the operation. (Emulation package 9.13.0.00201)
    C28xx_CPU1: Can't Run Target CPU: (Error -1137 @ 0x27D) Device is held in reset. Take the device out of reset, and retry the operation. (Emulation package 9.13.0.00201)
    C28xx_CPU1: Trouble Reading Register PC: (Error -1137 @ 0x0) Device is held in reset. Take the device out of reset, and retry the operation. (Emulation package 9.13.0.00201)
    C28xx_CPU1: Trouble Reading Register ST1: (Error -1137 @ 0x6) Device is held in reset. Take the device out of reset, and retry the operation. (Emulation package 9.13.0.00201)
    C28xx_CPU1: Can't Run Target CPU: (Error -1137 @ 0x269) Device is held in reset. Take the device out of reset, and retry the operation. (Emulation package 9.13.0.00201)
    C28xx_CPU1: Trouble Reading Register PC: (Error -1137 @ 0x0) Device is held in reset. Take the device out of reset, and retry the operation. (Emulation package 9.13.0.00201)
    C28xx_CPU1: Trouble Reading Register ST1: (Error -1137 @ 0x6) Device is held in reset. Take the device out of reset, and retry the operation. (Emulation package 9.13.0.00201)

  • That is definitely not typical behavior. 

    1. Replace the USB-C cable used to connect to the ISOXDS110. A bad cable can cause connection failure for a variety of reasons.
    2. Remove and replace the ISOXDS110 from the TIDM-02010, ensuring the connection is solid.
    3. Does the C2000 MCU have 3.3V supplied to it? Using a multimeter, verify the 3.3V test point on the TIDM-02010.

    If you're using the TIDM-02010 TI reference design, then this error is very unusual. If the prev. 3 debug steps do not help, also try the following:

    • Delete the "HVAC_REV3P2_3SC_LIB" folder and/or the "HVAC_REV3P2_1SC_LIB" folder, whichever is present, and rebuild the project.
      • Alternatively, you could build a new, empty workspace and import this project from your old one. This performs the same task, while also avoiding any potentially corrupted metadata in the CCS workspace.
    • Restart your computer.

    This step is rarely able to resolve problems, but it's an important sanity check for lingering, unusual issues, to ensure that nothing is wrong with the workspace.

    Regards,
    Jason Osborn

  • Delete the "HVAC_REV3P2_3SC_LIB" folder and/or the "HVAC_REV3P2_1SC_LIB" folder, whichever is present, and rebuild the project.

    I have deleted but after building then again "HVAC_REV3P2_1SC_LIB" folder generate, still having same issue.

    another workspace have below error & here i have change new data USB-C cable but still issue not resolved:

    C28xx_CPU1: Error connecting to the target: (Error -1015 @ 0x0) Device is not responding to the request. Device may be locked, or the debug probe connection may be unreliable. Unlock the device if possible (e.g. use wait in reset mode, and power-cycle the board). If error persists, confirm configuration and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 9.13.0.00201)

    as Below i used New XDS110 tool , New USB-C cable & New OK Workspace only Same is TI Board(TIDM-02010E32).

    This board i have change New MCU like TMS320F2800137.

    But still below error occur: 

    Error connecting to the target:
    (Error -1015 @ 0x0)
    Device is not responding to the request. Device may be locked, or the debug probe connection may be unreliable. Unlock the device if possible (e.g. use wait in reset mode, and power-cycle the board). If error persists, confirm configuration and/or try more reliable JTAG settings (e.g. lower TCLK).
    (Emulation package 9.13.0.00201)

    Remove and replace the ISOXDS110 from the TIDM-02010, ensuring the connection is solid.

    Yes i can do as you said above.

    Does the C2000 MCU have 3.3V supplied to it? Using a multimeter, verify the 3.3V test point on the TIDM-02010

    Yes, i have check with multimeter & having 3.3V correct.

    So please resolved issue as early as possible.

    Dear jason,

    If i used our own custom pcb then program Load successfully & i am not connected IPM in custom PCB,so i can't not try to run motor in our own custom PCB.

    So what issue in TI Board i.e.TIDM-02010E32 board

  • I'm reaching out to a colleague regarding this issue- please give them a day to respond.

    Regards,
    Jason Osborn

  • Babaji,

    I have attached the user guide for ISOXDS emulator. Could you please quickly cross check if connection/switches and target config settings are done as per the user guide?

     User Guide - ISOXDS110DACE3.pdf 

    Regards,

    Sumit

  • Dear Sumit,

    Please find below pic.

    Please find above setting & check it is correct or not?

    few day ago i was same setting & program load successfully.

  • Babaji,

    Thanks for sending screenshot, couple of think need to be cross check

    1. Did you change/save configuration recently by any chance? In the setting that you shared, you can keep JTAG TCLK Frequency as 1.0MHz. You just have to change setting for Power Selection as "Target supplied power". Please try save that with following and see if problem persists.

    Could you also also check if emulator is connected in right orientation to TIDM02010E32 as shown below?

    Regards,

    Sumit

  • Dear Sumit,

    Same Error occure as above.

    Setting is same as above please check.

    Emulator orientation is same as above but still problem is occur.

  • Babaji,

    I see you have not saved after changing the configuration. Please save the target config. by pressing button shown in green circle and press test connection button to see if it successfully connects.

    Sumit

  • Dear Sumit,

    I have save the configuration but still problem remains same.

    Configuration pic as below.

    After Test connection file as below

    [Start: Texas Instruments XDS110 USB Debug Probe_0]
    
    Execute the command:
    
    %ccs_base%/common/uscif/dbgjtag -f %boarddatafile% -rv -o -S integrity
    
    [Result]
    
    
    -----[Print the board config pathname(s)]------------------------------------
    
    C:\Users\ADMIN\AppData\Local\TEXASI~1\CCS\
        ccs1250\0\0\BrdDat\testBoard.dat
    
    -----[Print the reset-command software log-file]-----------------------------
    
    This utility has selected a 100/110/510 class product.
    This utility will load the adapter 'jioxds110.dll'.
    The library build date was 'Sep  6 2023'.
    The library build time was '09:57:39'.
    The library package version is '9.13.0.00201'.
    The library component version is '35.35.0.0'.
    The controller does not use a programmable FPGA.
    The controller has a version number of '5' (0x00000005).
    The controller has an insertion length of '0' (0x00000000).
    This utility will attempt to reset the controller.
    This utility has successfully reset the controller.
    
    -----[Print the reset-command hardware log-file]-----------------------------
    
    The scan-path will be reset by toggling the JTAG TRST signal.
    The controller is the XDS110 with USB interface.
    The link from controller to target is direct (without cable).
    The software is configured for XDS110 features.
    The controller cannot monitor the value on the EMU[0] pin.
    The controller cannot monitor the value on the EMU[1] pin.
    The controller cannot control the timing on output pins.
    The controller cannot control the timing on input pins.
    The scan-path link-delay has been set to exactly '0' (0x0000).
    
    -----[Perform the Integrity scan-test on the JTAG IR]------------------------
    
    This test will use blocks of 64 32-bit words.
    This test will be applied just once.
    
    Do a test using 0xFFFFFFFF.
    Scan tests: 1, skipped: 0, failed: 0
    Do a test using 0x00000000.
    Scan tests: 2, skipped: 0, failed: 0
    Do a test using 0xFE03E0E2.
    Scan tests: 3, skipped: 0, failed: 0
    Do a test using 0x01FC1F1D.
    Scan tests: 4, skipped: 0, failed: 0
    Do a test using 0x5533CCAA.
    Scan tests: 5, skipped: 0, failed: 0
    Do a test using 0xAACC3355.
    Scan tests: 6, skipped: 0, failed: 0
    All of the values were scanned correctly.
    
    The JTAG IR Integrity scan-test has succeeded.
    
    -----[Perform the Integrity scan-test on the JTAG DR]------------------------
    
    This test will use blocks of 64 32-bit words.
    This test will be applied just once.
    
    Do a test using 0xFFFFFFFF.
    Scan tests: 1, skipped: 0, failed: 0
    Do a test using 0x00000000.
    Scan tests: 2, skipped: 0, failed: 0
    Do a test using 0xFE03E0E2.
    Scan tests: 3, skipped: 0, failed: 0
    Do a test using 0x01FC1F1D.
    Scan tests: 4, skipped: 0, failed: 0
    Do a test using 0x5533CCAA.
    Scan tests: 5, skipped: 0, failed: 0
    Do a test using 0xAACC3355.
    Scan tests: 6, skipped: 0, failed: 0
    All of the values were scanned correctly.
    
    The JTAG DR Integrity scan-test has succeeded.
    
    [End: Texas Instruments XDS110 USB Debug Probe_0]
    

    Dear sumit ,

    if i have change our custom pcb then program load successfully.

    only program load issue in TI-Board i.e.TIDM-02010E32.

    in TI Board i have change MCU 2-3 times but still program not load in TI Board.

    So please resolved issue as early as possible.

    for other details find above TI code & other details in above.

  • Babaji,

    From test connection file, it seems that debugger is able to connect to target MCU. So connection is fine. No issue with debugger or the target MCU. Could please you try remove other target config file (right click on file) from the project and keep only the active one as shown in image below and retry loading the program?

    Regards,

    Sumit

  • Dear Sumit,

    I have removed those but still problem remains same.

    Please resolved issue.

  • Babaji, 

    Could you please you try loading other example from C2000 ware for F280013x device on TIDM02010 board? Lets take simple LED blinking program (...\ti\c2000\C2000Ware_5_02_00_00\driverlib\f280013x\examples\led) which boots from RAM to rule out possibility if this is related to on-chip flash. You can add same .ccxml file from your current project to cross check the same.

    Regards,

    Sumit

  • Dear Sumit,

    I am using serial communication example but having same problem occur.

    target setting is corrected as per above.

    i have used many workspace & those are correct because this serial communication used few day ago & it is correct one.

    for more details serial com example code.

    Serial_com_example_12032024.rar

    Also I have changed mcu & below all component but still issue not resoved.

    Dear Sumit,Please resolved this issue as early as possible.

  • Please note that Sumit is OOO for US holiday. You can expect a reply next week.

  • Dear All,

    Any Update??

  • Apologies for the delay- a hurricane hit the city, causing a lot of delays over here. I'll check on getting you a response to this thread, or I will provide an ETA before end of day.

    Regards,
    Jason Osborn

  • I have that update for you. Due to the hurricane, please expect a response from our subject matter expert early next week.

    Regards,
    Jason Osborn

  • Babaji, 

    With this new projects target configuration (.ccxml file), what does it shows when you press Test Connection as shown in image below?

    Does it shows successful connection ?

    Regards,

    Sumit

  • Does it shows successful connection ?

    Yes

  • Babaji,

    So this shows that debugger connection with device is okay. No need to change any component. 

    Please try manually launching target configuration as shown in process in link below - 

    https://dev.ti.com/tirex/explore/content/c2000_academy_2_06_00_52/_build_c2000_academy_2_06_00_52/source/c2000_get_started/c2000_getstarted.html#option-2-manually-launching-target-configuration

    Let us know if any issue occurs following the process or if this solves the issue.

    Regards,

    Sumit

  • Dear Sumit,

    As per above ,i have do all above things but still problem is same.

    Test Connection is successfully connected.

  • Dear Sumit,

    Any update regarding above query.?

  • Babaji,

    Considering test connection is successful and no issue on the HW, at this point could you please downloadre-install the latest MCSDK, import the project and try loading code using TIDM-02010user guide. Let me known if that solves your issue. I think some setting may have got altered in parent directory.

    Regards,

    Sumit

     

  • Dear Sumit,

    Any Update ??

  • Please respond to Sumit's most recent post on 7/29/24 and confirm the outcome of these actions.