• State Resolved
  • Locked Locked
  • Replies 13 replies
  • Answers 2 answers
  • Subscribers 52 subscribers
  • Views 1417 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/CC2642R: Code Composer Studio™ forum

POTHIRAJAN KANDASAMY
Intellectual 600 points

Part Number: CC2642R
Other Parts Discussed in Thread: BLE-STACK

Tool/software: Code Composer Studio

Hi

I am developing blue-tooth application on CC2642. Working with an example project named "project_zero" in BLE5 folder of the examples.

While trying to down the run "project zero" in my launch pad I got following problem. Please refer to the console window output shown below. I see that the last line of the below error message keeps repeating non-stop.

I thought of bringing the launchpad back to factory default condition by following the below link suggested by TI(shown below), but the problem persists. Please suggest me about how to recover from this issue. Thanks in advance.

Link to bring back factory image: http://software-dl.ti.com/simplelink/esd/simplelink_cc26x2_sdk/2.10.00.44/exports/docs/thread/html/ble-stack-oad/revert-to-factory.html

Environment details:

SDK version is simplelink_cc13x2_26x2_sdk_4_10_00_78

Development Studio: CCS10.0

Host is: Windows10 laptop.

Host interface: USB port of Launchpad CC2642

TARGET HW:  LAUNCHXL - CC26X2 REV B, SDK 2.40

 

;*************************************************************

Cortex_M4_0: GEL Output: Memory Map Initialization Complete.
Cortex_M4_0: GEL Output: Board Reset Complete.
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 9.1.0.00001)
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 9.1.0.00001)
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 9.1.0.00001)

;**************************************************************

Regards,

Pothirajan.K

  • 0
    TI__Guru**** 483351 points

    Hello,

    Please see the below link on more details on the error and some suggestions on how to resolve it.

    https://software-dl.ti.com/ccs/esd/documents/ccs_debugging_jtag_connectivity_issues.html#cannot-access-the-dap

    Thanks

    ki

  • 0 in reply to Ki
    Intellectual 600 points

    Hello Ki,

    Thanks for the input.

    I have tried to work on links that you have provided. Attempted to check DAP. I was able to see flash memory contents without any issue. 

    Then tried to single step into code. It goes smoothly until ProjectZero_init entry. After that it generates the said error. Does it give any clue?

    Then I have taken totally alternate approach, wanted to flash the image and do the testing. Using "flash programer 2" tried it out. 

    It gave an error  after completing erase operation ">Failed to read last page". 

    Any clues to share with me? Should I try some other example code? 

    Thanks,

    Pothirajan.K

  • 0 in reply to POTHIRAJAN KANDASAMY
    TI__Guru**** 483351 points

    POTHIRAJAN KANDASAMY said:
    Then tried to single step into code. It goes smoothly until ProjectZero_init entry. After that it generates the said error. Does it give any clue?

    Is this pretty consistent in that the error always occurs in the same spot mentioned above and otherwise there is no issue?

    Thanks

    ki

  • 0 in reply to Ki
    Intellectual 600 points

    Hello Ki,

    This is the first function invoked inside that newly created. I have tried at least 4 times to check the consistency of behavior at the time of writing previous mail. This is where it shows up initially. Thanks in advance.

    Regards,

    Pothirajan.K

  • 0 in reply to POTHIRAJAN KANDASAMY
    TI__Guru**** 483351 points

    I will move this thread to the device forum. The experts there can assist you further.

    Thanks

    ki

  • 0 in reply to POTHIRAJAN KANDASAMY
    TI__Guru* 83821 points

    Hi Pothirajan,

    Project Zero is an OAD-enabled project. To make sure it runs as expected please follow the instructions in the BLE Fundamentals SimpleLink Academy lab:

     

    I would also recommend you the Debugging part of the OAD SimpleLink Academy lab:

     

  • 0 in reply to Marie H
    Intellectual 600 points

    Hi Marie,

    I have followed the suggestions that is given in the first HTML. While trying to run project_zero using  CCS environment I have faced the below problem(which is same as that of what I have reported at the beginning of the thread. I am providing it for easy reference.

    ;*************************************************************

    Cortex_M4_0: GEL Output: Memory Map Initialization Complete.
    Cortex_M4_0: GEL Output: Board Reset Complete.
    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 9.1.0.00001)
    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 9.1.0.00001)
    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 9.1.0.00001)

    ;**************************************************************

     While loading the built image into target, I could see it stops at main. Then I use play button to run. Immediately after than I get into the above said error. It happens after thread creation.

    ;------------------------------- Background information ----------------------------------------

    After receiving the board newly from Texas Instruments, we have tried to flash the board with hex file(project_zero hex file). That flashing operation failed with the statement ">Failed to read last page". 

    We have used HEX file generated by CCS while building project_zero. Any thing wrong? Should we not use hex file as it is for flashing?

    ;--------------------------------------------------------------------------------------------------------- 

    Regards,

    Pothirajan.K

  • 0 in reply to POTHIRAJAN KANDASAMY
    TI__Guru* 83821 points

    Hi,

    You are using CCS 10 but the error message refers to emulation package 9.1.0. Maybe there is something wrong with your installation. 

    Did you test running any other BLE-Stack examples, e.g. simple peripheral?

  • 0 in reply to Marie H
    TI__Guru**** 483351 points

    Hi Marie,

    Marie H said:
    You are using CCS 10 but the error message refers to emulation package 9.1.0

    This is actually correct. CCS IDE version 10.0 comes with TI Emulator Pack component version 9.1.0.00001

    ki

  • 0 in reply to Ki
    Intellectual 600 points

    Hi Marie,

    Sure I will get back with results of running other program suggested by you. As the target board is not with me, I have co-ordinate with some one else and get the result some time on 20th May. Based on Ki's suggestion I am keeping my installation same.

    Based on my flashing error (I have provided in my previous description) do you get any clue?.

    Regards,

    Pothirajan.K

  • 0 in reply to Ki
    Intellectual 600 points

    Hi,

    I have tried to work with simple peripheral. We have started in a new workspace. After building the code while trying to download, it has started downloading then reported that debugger needs to be updated. Usually I just say ok.  Today I have stopped and cancelled download. Then finished debugger upgrade. After that downloaded new build. It started working. No usual errors were found. Then we have gone back to all our old code, other projects, everything seems to work fine. It is bit strange experience.Consolidation is "The way debugger upgrade was done is different than my earlier attempts". 

    I consider this issue as closed. Thanks Marie and Ki for your support. 

    Regards,

    Pothirajan.K

  • 0 in reply to POTHIRAJAN KANDASAMY
    TI__Guru**** 483351 points

    Glad to hear that it is working now. The debugger update you refer to is the firmware for the on-board XDS110 debug probe used by the LaunchPad. We did make changes to the update process, but the changes should have made for a better experience. I'm not sure what happened in your case. If you do see this happen again, please let us know.

    Thanks

    ki