• State TI Thinks Resolved
  • Locked Locked
  • Replies 10 replies
  • Answers 4 answers
  • Subscribers 31 subscribers
  • Views 306 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.

MMWAVEICBOOST: IWR6843ISK Debugging Inconsistencies

Keith Sponsler
Prodigy 40 points
Part Number: MMWAVEICBOOST
Other Parts Discussed in Thread: IWR6843ISK

Tool/software:

I've been debugging an IWR6843ISK with the MMWAVEICBOOST. I'm running into inconsistencies while debugging. First I'll describe my set-up and then I'll describe the issue.


Set-up
IWR6843ISK mounted on the MMWAVEICBOOST board
IWR6843ISK has been flashed with CCS debug firmware (from mmwave_sdk_03_06_02_00-LTS/packages/ti/utils/ccsdebug)
IWR6843ISK switches S1.1-S1.6 = [0, 0, 0, 0, 1, 0]
MMWAVEICBOOST switches S1.1-S1.12 = [1, 1, 1, 1, 1, 1, 1, 0, 0, 1, 1, 1]
MMWAVEICBOOST J1 is used as CANbus, which goes to a desktop CAN analyzer
MMWAVEICBOOST jumpers SOP0 - SOP2 = [1, 0, 1]
MMWAVEICBOOST's 5V power jack is powered by a variable power supply set to 5.00V (max current 0.8 A)
MMWAVEICBOOST J11 and J12 (XDS110 and FTDI) micro USBs are both connected to PC

The issue
Occasionally, I won't be able to connect to the target configuration. Other times I won't be able to load code onto the cores. Since I use a power supply to power the MMWAVEICBOOST, I can read the power usage of the board. In normal operation, the board will draw ~2W. However, sometimes when I power on the board, it will only draw 0.7W. Whenever the board powers on and only draws 0.7W, I am unable to connect to my target debug configuration. I power the board through the 5V barrel jack before connecting any USB cables.

If the board powers on normally and is drawing ~2W, I am reaching an issue when loading code onto the cores. When connecting to the C674X_0, I get this error in the Console:

CS_DAP_0: GEL Output: --->> DSS is under application controlled reset.  Prior to connecting this reset must be released.
CS_DAP_0: GEL Output: --->> The debugger will enable "Halt On Reset" and release the application-extended reset
CS_DAP_0: GEL Output: --->> "Halt On Reset" has been enabled on the C674X_0CS_DAP_0: GEL Output: --->> DSS application extended reset released

Additionally, there is this error when I attempt to load a program onto the Cortex_R4_0:
Cortex_R4_0: Trouble Writing Memory Block at 0x0 on Page 0 of Length 0x3c: (Error -1065 @ 0x3C) 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_R4_0: File Loader: Verification failed: Target failed to write 0x00000000
Cortex_R4_0: GEL: File: D:\Dode\hylio_radar\hylio_isk_radar_mss\Debug\hylio_isk_radar_mss.xer4f: Load failed.

I've tried re-flashing the IWR6843ISK with CCS debug firmware and it did not resolve the issue. Any suggestions to fix these issues and avoid them in the future would be appreciated.

  • 0
    TI__Genius 11900 points

    Hi

    Thanks for your query. Please allow us a couple of days to respond

    Regards

  • 0 in reply to Abhishek Karkisaval
    TI__Mastermind 19700 points

    Hello.

    Are you loading the DSS(C674x) core image before loading the MSS(Cortex R4F) image?

    Sincerely,

    Santosh

  • 0 in reply to Santosh Krishnan
    Prodigy 40 points

    Yes and no. I generally alternate between loading the Cortex_R4 and the C674X first. Is there a proper order to 1) connect to and 2) load programs? I generally have the Cortex_R4 and the C674X cores grouped. And after loading programs once I use Alt + Shift + R to reload.

  • 0 in reply to Keith Sponsler
    TI__Mastermind 19700 points

    I've seen this issue before, and it usually seems to occur when you load the Cortex R4 first.  In the debug flow we recommend that you load the C674x first and then you load the Cortex_R4 image next.

    Sincerely,

    Santosh

  • 0 in reply to Santosh Krishnan
    Prodigy 40 points

    I will make that part of my flow. DSS before MSS.
    I still get this error often when I try to launch the target configuration:

    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)

    On a random reboot, the error will go away. I disconnect all cables, power the board through the 5V barrel jack, then plug in the USB cables. This error used to not happen, but now it takes a dozen or more reboots to get debugging. Additionally, the error will re-appear sometimes after pressing the NRST button on the MMWAVEICBOOST board.

  • 0 in reply to Keith Sponsler
    TI__Mastermind 19700 points

    That error usually happens when the device gets locked out and will take a power cycle to unlock it.  I would not reset during debugging, if you want to reset end the debugging session before performing a reset.  In addition, the reset will disconnect the JTAG.

    Sincerely,

    Santosh

  • 0 in reply to Santosh Krishnan
    Prodigy 40 points

    1) open CCS
    2) power the MMWAVEICBOOST board with 5V through the barrel jack
    3) connect the XDS110 and FTDI USBs
    4) Target Configurations -> Launch Configuration
    5) Group 1 -> Connect Target

    That is when I this 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)

    To reboot, I remove the USB cables, turn off the power, and start again at step 2. After rebooting the board N times (today N = 7), I am able to connect to the cores. But then this error appears:

    CS_DAP_0: GEL Output: --->> DSS is under application controlled reset.  Prior to connecting this reset must be released.
    CS_DAP_0: GEL Output: --->> The debugger will enable "Halt On Reset" and release the application-extended reset
    CS_DAP_0: GEL Output: --->> "Halt On Reset" has been enabled on the C674X_0CS_DAP_0: GEL Output: --->> DSS application extended reset released

    I get better results if I connect to each core in the group individually (instead of connecting to the group). That will get rid of the previous error. Then, as Santosh suggested, I load the DSS first. Then I load the MSS. I can start debugging my code after that.

    For rapid debugging, I have typically followed the suggestions under Section 4, "Helpful CCS Debug Tips," from the Using CCS Debug resource [Resource Explorer / mmWave radar sensors / Embedded Software / Documentation / Software Guides / Using CCS Debug]. However, after pressing the reset button on the EVM (in section 4.2), I'm back at square one with the following errors

    1) CS_DAP_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)

    2) IcePick_M_0: Error connecting to the target: (Error -2131 @ 0x0) Unable to access device register. 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)

    1) appears when connecting to the Cortex R4 and 2) appears when connecting to the C674X. Then I'm back to rebooting the system until it decides to work. Is there anything I can debug on the system to get it to work more consistently?

  • 0 in reply to Keith Sponsler
    TI__Mastermind 19700 points

    Hello.

    These rapid debug features were not tested for the newest versions of CCS, so it may be a new feature or new implementation of that feature that may behave differently than on the older versions of CCS that these tips were tested on.  For the 6843 device, if you are using the newer versions of CCS(CCS 20 > ), I would recommend going through the flow as stated in the debugging with CCS Theia guide, as Theia was the name of the new version of CCS prior to CCS 20.

    Sincerely,

    Santosh

  • 0 in reply to Santosh Krishnan
    Prodigy 40 points

    I'm currently using CCS 12.8.1.00005. I have briefly tested CCS Theia 1.5.1.3, but I still primarily use old CCS

  • 0 in reply to Keith Sponsler
    TI__Mastermind 19700 points

    Understood.

    If you are running into this issues I would recommend you use the flow that is followed for normal debugging procedure.  This will resolve any inconsistencies you see with the shortcuts.  

    Sincerely,

    Santosh