• State
  • Locked Locked
  • Replies 4 replies
  • Subscribers 83 subscribers
  • Views 197 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.

F29H850TU: Debug Probe Insufficient Privileges

Robert Quinn
Intellectual 730 points

Part Number: F29H850TU

Tool/software:

I was working with an XDS110 debug probe to connect to an F29 board. To troubleshoot a flashing issue the F29 board was swapped for another one. However, after the swap, the following debug probe error message displays:

The probe and the code are the same. Can you provide some help resolving this issue?

Thanks.

  • 0
    TI__Mastermind 18515 points

    Hi Robert,

    Few questions here… Are you using the SSU to develop code? I would be curious to know what the SSUGenRegs.SSUMODE / BANKMODE reads. 

    Have you seen this error before? Would you be able to provide reproducible steps for this issue including what code was executed during this process? Which F29x board are you referring to? Are you using a XDS110 ISO probe as well? 

    Best Regards,

    Aishwarya 

  • 0 in reply to Aishwarya Rajesh
    Intellectual 730 points

    I haven't been able to reproduce this error message recently. It is part of our effort to resolve:  F29H850TU: Invalid Address Provided to Flash which is an ongoing issue that we are still struggling with.

  • 0
    TI__Mastermind 18515 points

    Robert,

    Understood. To completely rule out code issues, can you confirm this point below? The error in the image can happen when the device is in SSUMODE3. 

    Aishwarya Rajesh said:
    Are you using the SSU to develop code? I would be curious to know what the SSUGenRegs.SSUMODE / BANKMODE reads. 

    Some other pointers with F29x development that comes to mind is when switching BANKMODEs, you must issue an XRSN to the device. The order is to switch the bank mode, issue physical XRSn (or SIM Reset from the Scripts window), and load code. If this XRSN isn't issued, you will not be in the proper bank mode, and it can cause the first issue you are seeing in the other thread. When you see the error connecting to target in the other thread, try a CPU reset and connect to the CPU again. 

    In general, can you confirm that the power LEDs on the XDSISO and the board itself are all turned on to indicate good power supply? This info is in the related documentation but for a quick verification, just compare the LED state when using the working vs not working XDSISO. 

    Best Regards,

    Aishwarya

  • 0
    TI__Mastermind 18515 points

    Robert,

    Checking in to see if there are any updates from your end on this issue.

    Best Regards,

    Aishwarya