• State
  • Locked Locked
  • Replies 7 replies
  • Subscribers 41 subscribers
  • Views 1011 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.

CC3220MODA: Unable to acces the DAP

Dave Bohan
Intellectual 330 points
Part Number: CC3220MODA
Other Parts Discussed in Thread: UNIFLASH, CC3220SF, CC3220SF-LAUNCHXL

I am trying to bring up a new board design which uses the CC3220MODASF module.  I am connecting to the module via JTAG (and TX/RX) from a LAUNCHCC3220MODASF board.

When trying to connect from CCSv7, I receive a "Unable to access the DAP" error.

I have also tried to program an image from Uniflash, where I received: "Operation failed: fs_programming error: ret: -10300, ex_err: 4071 -FS_SECURITY_ALLERT".

Suggestion?

  • 0
    TI__Guru 64455 points

    Hello,

    This is a security alert and the only way to overcome it is by reprogramming the device.

    So Uniflash indeed is the only way to go.

    What Uniflash version are you using?

    How do you connect Uniflash?

    Shlomi

  • 0 in reply to Shlomi Itzhak
    Intellectual 330 points

    I am using Uniflash Version: 4.2.1.1562.

    Uniflash is connected via USB to a CC3220SF LaunchXL board, which is then connected to my custom board through the JTAG connector.

    ~Dave

  • 0 in reply to Dave Bohan
    TI__Guru 64455 points

    Do you get "Error -1170" when you cannot access the board with Uniflash?

    If so, this is because the device is locked in production mode.

    The way to open it is to use Uniflash and open it.

    But, you claim you cannot connect via Uniflash.

    With the setup you built, have you also set the SOP lines on your custom board correctly?

  • 0 in reply to Shlomi Itzhak
    Intellectual 330 points
    I get "Error-1170" when trying to connect from CCSv7, not from Uniflash.

    I am able to *Connect* via Uniflash, but not able to program an image.

    SOP is set to "010", which is the same as the LAUNCH3220MODASF SOF setting.
  • 0 in reply to Dave Bohan
    TI__Mastermind 46501 points
    Dave,

    For debugging secure devices, the device must be formatted in 'development mode' as opposed to 'production mode' to enable the JTAG connectivity. This can be done using Uniflash in the General Settings menu.

    Regarding the error you are getting on Uniflash, please follow the instructions in the Getting Started Guide (www.ti.com/.../swru461.pdf) for creating your image.

    Are you trying to program an image from the SDK? Please specify the content of "User Files" and "Trusted Root-Certificate Catalog".

    Best regards,
    Seong
  • 0 in reply to Seong Kim
    Prodigy 130 points

    I'm working with Dave on this particular project, so perhaps I can answer a few of the questions...

    Here's what we've put on the board:

    • Service pack: sp_3.5.0.0_2.0.0.0_2.2.0.5.bin (from CC3220 SDK v1.50)
    • Firmware image: custom firmware (release, not debug), but originally based on the shadow_sample_console_echo_CC3220SF_LAUNCHXL_tirtos_ccs example program that talks to AWS. We checked FailSafe, Secure, and Public Write. We used the Trusted Cert Key from the SDK certificate playground for the Private Key File Name and the corresponding Trusted Certificate for the Certification File Name.
    • Trusted Root-Cert Catalog: We're not using the default (i.e. checkbox is unchecked). We are using the samples in <sdk-installation>\tools\certificate-playground. That includes the certcatalogPlayGround20160911 source file and signature source file, along with the Root CA certificate, the Trusted CA Certificate, and the Trusted Certificate.

    The image works properly with both the CC3220SF-LAUNCHXL and CC3220MODASF-LAUNCHXL boards.

    We appreciate your help,

    Ken

  • 0 in reply to SGW_Ken
    TI__Mastermind 46501 points
    Thank you for providing this information. I have just informed Dave of what could be causing this issue.

    -Seong