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.

IWR1443: problem with XDS110 debug probe

Expert 6460 points
Part Number: IWR1443
Other Parts Discussed in Thread: UNIFLASH, IWR1642

Team,

While debugging using the XDS110 Debug Probe on IWR1443, I've encountered strange behaviour after including I2C driver to the project.

After adding I2C initialization to the code, debugger execution stops inside the function call I2C_open, and the following error is reported and execution ends in loader_exit:

ti.sysbios.family.arm.v7r.vim.Hwi: line 271: E_undefined: Hwi undefined, intnum: 66

xdc.runtime.Error.raise: terminating execution

data: ti.sysbios.family.arm.v7r                                           

.vim.Hwi: line 271: E_undefined: Hwi undefined, intnum: 66

xdc.runtime.Error.raise: terminating execution

Another version of the error intnum: 95. These errors appear almost interchangeably, although intnum: 66 appears more often. When I generate .bin file using the same .out file and load it onto the board everything works as intended, meaning the problem is somewhere in the debugger.

These are repositories that I'm using:

SYS/BIOS: 6.73.0.12
System Analyzer (UIA): 2.20.0.02
mmWave SDK: 2.0.0.04

XDCtools: 3.50.7.20_core 

All versions of the project work well when loaded onto our board using Uniflash. There are no problems with any peripherals nor RSS, including I2C, and everything works as intended. Problems occur only when trying to debug project in CCS.

Thank you in advance for assistance in this matter.

Kind regards,
TI Customer

  • Hi,

    Will get back to you early next week

    thank you
    Cesar
  • Hi Bartosz,

    From the description, the customer is using SDK 2.0.0.4 which does not support IWR1443. SDK 2.0.0.4 supports only IWR1642.

    Can you confirm which version of the the IWR1443 device are they using as they'll need to use the appropriate version of mmWave SDK as mentioned below.

    ES2.0 devices - mmWave SDK 1.2.0.5

    ES3.0 devices - mmWave SDK 2.1.0.4

    Adiditonally, please also check the following:

    1. Is the customer flashing ccs_debug.bin to prepare the board for CCS based debugging as mentioned in the mmWave SDK user guide - section CCS development mode? This is required to be done one time (or again after another binary was flashed) before loading the code through CCS for debugging.

    2. The correct version of CCS is used including making sure that the desktop version is used and not the Cloud version.

    Regards

    -Nitin

  • Hi Bartosz,

    We have not heard back from you on this thread. Do you still need support on this question?

    Regards
    -Nitin
  • Closing this thread due to lack of activity. Please feel free to create a new post if further support is needed.

    Thanks
    -Nitin