• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 51 subscribers
  • Views 175 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.

CC2651R3SIPA: CC2651R3SIPA - Error -1170 DAP access problem

Kacper Cyrocki
Prodigy 10 points
Part Number: CC2651R3SIPA
Other Parts Discussed in Thread: UNIFLASH

Hello,

I'm currently struggling an issue with CC2651R3SIPA programming using CCS. I've my own custom designed board with this MCU but I've problem that after programming the board I've got -1170 error "Unable to access DAP". This error occurs when code try to execute BIOS_start function (I'm using TIRTOS system). Strange thing that I've got 3 the same prototypes and one of them works completly fine, but other two have issue described above. What may cause this issue? 

I already tested by uploading example code from CC2651 SDK, same issue, I was checking debug probe connections and it is the same on all boards, power supply was also tested. I'm using XDS110 probe from LaunchPad.

  • 0
    TI__Guru**** 216717 points

    Hello Kacper,

    The issue you've described could either be an indicator of an unstable JTAG connection or faulty firmware.  You can review the recommendations from the Debugging JTAG Connection Issues page and submit your design to SIMPLELINK-2-4GHZ-DESIGN-REVIEWS for further review.  What SimpleLink SDK example are you using to evaluate your hardware?  Have any changes been made to the default project?  Here are similar E2E threads which point to incorrect project or BIM configurations.  Does the firmware operate as expected when outside of the debugger?

    Regards,
    Ryan

  • 0 in reply to Ryan Brown1
    Prodigy 10 points

    I was using Simple_Peripheral example project from SDK without any modification. It's also worth mention that my code execute only if just after the upload. When I detaching debugger and reset power supply code won't start it again. 

    I will check threads which you sent, I seems that it is some kind of configuration problem but I cannot find the solution. One thing which I notice is, that sometimes after I upload simple_peripheral example thru UniFlash and reset the power I'm able to program my own code to the board thru CCS. 

  • 0 in reply to Kacper Cyrocki
    TI__Guru**** 216717 points

    Please ensure that you are erasing all flash memory before programming, and not using the OAD on-chip/off-chip versions of simple_peripheral.  Some of the behavior you've described could be attributed to missing a BIM application which only applies to OAD-enabled projects.

    Otherwise, the example project has been thoroughly tested and should work on any properly designed custom board.  You can also check SWRA640 and the Custom Hardware section of the BLE5-Stack User's Guide.

    Regards,
    Ryan