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.

F28M35H52C: Error 1170 after setting CSM Password and GRABSECT values

Other Parts Discussed in Thread: UNIFLASH

Tool/software:

 Master (M3) core. At some point after setting a Zone 1 password and the GRABSECT register to set sectors B-M to Zone 1, I am no longer able to access the device using the debugger, either with CCS or UniFlash.  I now have two chips that can't be accessed.

The OTPSEC values have NOT been set.  All other security values are default (0xFFFFFFFF).

I have a reviewed all the "Error 1170 - Unable to access the DAP" documentation I could uncover and none of the solutions have helped.  Also, none of the other solutions were related to setting the CSM values.

Is there a way to recover this part?

  • Hi Kieth,

    Have you referred to the ECSL section in the TRM?

    Let me know if either of these two solutions work for you.

    Thank you,

    Luke

  • There is no "Wait-In-Reset" option in the debugger configuration for the Blackhawk XDS200 debugger I am using.  I did try all the options related to holding the device in reset until the debugger is connected but no success.  This is a custom board so I don't have access to the boot option pins.  Unless there is another way to get to that boot option?

    Finally, I have NOT set a ECSL password.  Only a CSM password and the GRABSECT register settings.

    Next step?

    --Keith

  • Hi Keith,

    If the ECSL passwords are unprogrammed, it is still necessary to perform a read of the ECSL passwords for the ECSL unlock to occur. The two solutions listed in the excerpt from the TRM are the only way to bypass ECSL protection if the CSM is locked. Are you sure there's no way to access the boot pins?

    Thank you,

    Luke

  • Hi Luke,

    Thank you.  I was able to find a way to access the boot pins, however there is no "branch to boot check mode" boot option (per recommended action in section 1.10.1.1 in the TRM) listed in the TRM.

    Is there other documentation or process that I should be following.

    --Keith

  • Hi Keith,

    I've looped in our boot experts to help with this question. I'll get back to you as soon as I have more information.

    Thank you,

    Luke

  • Hi Keith,

    Do you see these options in the ccxml file when clicking the "Advanced" tab? If so, can you select the following options to emulate the behavior of wait-in-reset mode:

    Thank you,

    Luke

  • Hi Luke,

    I somehow got the debugger to get control prior to making this change.  Still don't know how.  I have captured this approach and will save it as I suspect I will need it again.  Thanks.  I'll consider this issue closed.

    --Keith