• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 55 subscribers
  • Views 1084 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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/CC1352P: XDS110 Emulator debugging error!

sung keun lee
Intellectual 590 points
Part Number: CC1352P
Other Parts Discussed in Thread: SYSCONFIG,

Tool/software: Code Composer Studio

Hello sir!

I have a problem that debugging error use xds110

Below code is my test code

/* I2C Initialization -Added by sklee */
//I2CCC26XX_init(hI2CHande);
//I2C_init();
// I2C_Params_init(&pI2CParam);

// pI2CParam.bitRate = I2C_100kHz;


//hI2CHande = I2CCC26XX_open(Board_I2C0, &pI2CParam); // I2C Open Complete

// hI2CHande = I2C_open(Board_I2C0, &pI2CParam); // I2C Open Complete

//TIMMER_READ_DATA(SECCONDS_ADDR);

 

GPIO_write(Board_PIN_LED0, 0); // 이 함수는 동작 함
GPIO_write(Board_PIN_LED1, 0); // GPIO_write() is operating

I try commanded about I2C(I2C init, I2C open)

Debugging is no problem but no commanded about I2C

/* I2C Initialization -Added by sklee */
I2CCC26XX_init(hI2CHande);

hI2CHande = I2CCC26XX_open(Board_I2C0, &pI2CParam); // I2C Open Complete

TIMMER_READ_DATA(SECCONDS_ADDR); <- this is control function for Timer IC 

GPIO_write(Board_PIN_LED0, 0); // 이 함수는 동작 함

GPIO_write(Board_PIN_LED1, 0); // GPIO_write() is operating

 

 This is error operate like below 

Cortex_M4_0: Error: (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.2.0.00004)
Cortex_M4_0: Error: (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.2.0.00004)
Cortex_M4_0: Trouble Halting Target CPU: (Error -2064 @ 0x0) Unable to read device status. 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.2.0.00004)
Cortex_M4_0: Error: (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.2.0.00004)
Cortex_M4_0: Trouble Halting Target CPU: (Error -2064 @ 0x0) Unable to read device status. 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.2.0.00004)
Cortex_M4_0: Error: (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.2.0.00004)
Cortex_M4_0: Trouble Halting Target CPU: (Error -2064 @ 0x0) Unable to read device status. 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.2.0.00004)
Cortex_M4_0: Error: (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.2.0.00004)
Cortex_M4_0: Trouble Halting Target CPU: (Error -2064 @ 0x0) Unable to read device status. 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.2.0.00004)
Cortex_M4_0: Error: (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.2.0.00004)
Cortex_M4_0: Trouble Halting Target CPU: (Error -2064 @ 0x0) Unable to read device status. 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.2.0.00004)
Cortex_M4_0: Error: (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.2.0.00004)
Cortex_M4_0: Trouble Halting Target CPU: (Error -2062 @ 0x0) Unable to halt device. 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.2.0.00004)
Cortex_M4_0: Error: (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.2.0.00004)
Cortex_M4_0: Trouble Halting Target CPU: (Error -2064 @ 0x0) Unable to read device status. 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.2.0.00004)
Cortex_M4_0: Error: (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.2.0.00004)
Cortex_M4_0: Trouble Halting Target CPU: (Error -2064 @ 0x0) Unable to read device status. 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.2.0.00004)
Cortex_M4_0: Error: (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.2.0.00004)
Cortex_M4_0: Trouble Halting Target CPU: (Error -2064 @ 0x0) Unable to read device status. 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.2.0.00004)
Cortex_M4_0: Error: (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.2.0.00004)
Cortex_M4_0: Trouble Halting Target CPU: (Error -2062 @ 0x0) Unable to halt device. 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.2.0.00004)
Cortex_M4_0: Error: (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.2.0.00004)
Cortex_M4_0: Trouble Halting Target CPU: (Error -2062 @ 0x0) Unable to halt device. 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.2.0.00004)

I used sysconfig program for set I2C parameter in sdk(C:\ti\simplelink_cc13x2_26x2_sdk_3_20_00_68\examples\syscfg_preview\rtos\CC1352P1_LAUNCHXL\ti154stack\sensor)

And set xds110 jtag tclk is 5.5MHz

If not used I2C then no problem

I don't know why !

 

  • 0
    TI__Guru**** 171309 points

    Hi,

    Per your description it seems your I2C initialization or operation is not properly done. The consequence of this is the device's core is being locked and/or running completely uncontrolled - that is why the Debug Probe is reporting an error. 

    The main task is to perform a step-by-step debugging of your code to see what is the exact instruction that is causing the device to lock. 

    Another idea is to use one of the various I2C examples of the SimpleLink SDK to see how the initialization is performed. 

    I will also notify the device experts, as they will have better insights about the device intrinsics as well. 

    Regards,

    Rafael

  • 0 in reply to desouza
    TI__Guru** 106705 points

    Hi,

    As Rafael suggested, try to use the I2C example that comes with the SDK without any changes and see if that works.

    Regards,
    Fredrik

  • 0 in reply to desouza
    Intellectual 590 points

    Thank sir!

    My circuit is difficult with cc1352p_lunchxl edk so must changed i2c pin map(sda -> dio5, scl -> dio6, changed by syscfg tool in ccs) 

    I try that debugging step by step your suggest 

    And result is made word file, please the file

    Debugging result.pdf

    I test debugging step by step, used rfPacketTx example project

    int main(void)
    {
    pthread_t thread;
    pthread_attr_t attrs;struct sched_param priParam;
    int retc;
    int detachState;

    /* Call driver init functions */
    Board_initGeneral();

    /* Set priority and stack size attributes */
    pthread_attr_init(&attrs);
    priParam.sched_priority = 1;

    detachState = PTHREAD_CREATE_DETACHED;

    I2CCC26XX_init(hI2CHande);

    hI2CHande = I2CCC26XX_open(Board_I2C0, &pI2CParam);

    And start debugging used by step into function

     

    After run I2CCC26XX_init(hI2CHande) function, debugging is run unlimited loop 

    /*
    * ======== Error_policyMin ========
    */
    Void Error_policyMin(Error_Block *eb, Types_ModuleId mod, CString file,
    Int line, Error_Id id, IArg arg1, IArg arg2)
    {
    if (eb == NULL || (UInt)Error_policy == (UInt)Error_TERMINATE) {
    for(;;) {    ---> unlimited rutin
    }
    }
    else if (eb != &xdc_runtime_Error_IgnoreBlock) {
    eb->id = id;
    }
    return;
    }

     

     

  • 0 in reply to sung keun lee
    TI__Guru** 106705 points

    Hi Sung,

    I assume this is the same as what we are discussing here: https://e2e.ti.com/support/wireless-connectivity/sub-1-ghz/f/156/t/842777 I will therefore close this thread.

    Regards,
    Fredrik