• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Answers 1 answer
  • Subscribers 82 subscribers
  • Views 311 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.

TMS320F28062: Uniflash report -1135 error connecting to target issue

Joe Ji
Expert 3920 points
Part Number: TMS320F28062
Other Parts Discussed in Thread: UNIFLASH

Tool/software:

Hi expert

Customer reports in the mass production projects, once they program the firmware with uniflash to a brand new device, there are some chances that uniflash reports the -1135 issue during the program process. 
Once the issue is reported, they cannot access to the device flash with JTAG, but the dsp can run properly, and can be accessed through UART boot. 
So I think the JTAG is locked accidentally, my question and support needs are:

Is it a known issue in f28062?

How to avoid this issue by adjust the flash programming process?

thanks

Joe

  • 0
    TI__Mastermind 36526 points

    Hi Joe,

    Joe Ji said:
    Once the issue is reported, they cannot access to the device flash with JTAG

    Is the customer using any security features? 

    Joe Ji said:
    Once the issue is reported, they cannot access to the device flash with JTAG, but the dsp can run properly, and can be accessed through UART boot. 

    TDI,TDO,TMS, and TCK can be used as GPIOs. Are they using them as GPIOs in their flashed program? This would disable the JTAG functionality when their application code is running. 

    Can they try putting the device in a boot mode such that the MCU will not boot to flash? Can they connect then? 

    Thanks,

    Ben Collier

  • 0 in reply to Benjamin Collier
    TI__Expert 3920 points

    Hi Ben

    Benjamin Collier said:
    Is the customer using any security features? 

    No they do not use security feature.

    Benjamin Collier said:
    Can they try putting the device in a boot mode such that the MCU will not boot to flash? Can they connect then? 

    they do not reuse the debug port as gpio, it is the occasional issue, not 100% reproduced. we try that on wait boot mode the debug port still cannot be connected.

    Thanks

    Joe

  • 0 in reply to Joe Ji
    TI__Mastermind 36526 points

    Joe,

    Joe Ji said:
    they do not reuse the debug port as gpio, it is the occasional issue, not 100% reproduced. we try that on wait boot mode the debug port still cannot be connected.

    The issue cannot be reproduced consistently? How often does the issue occur? Is the frequency the same with all boot modes? 

  • 0 in reply to Benjamin Collier
    TI__Expert 3920 points

    Hi Ben

    Benjamin Collier said:
    The issue cannot be reproduced consistently?

    Yes,

    Benjamin Collier said:
    How often does the issue occur? Is the frequency the same with all boot modes? 

    I'm not sure the frequency but two of my customers are meet the same JTAG lock issue with F28062.

    one more question:

    I see in F28335 datasheet, there is a requirement on XRS pin, is there the same requirement on F28062 ?

  • +1 in reply to Joe Ji
    TI__Mastermind 36526 points

    Hi,

    Joe Ji said:
    I see in F28335 datasheet, there is a requirement on XRS pin, is there the same requirement on F28062 ?

    No, this requirement does not exist for F28062.

    Also I want to bring to your attention: 

    If the MCU is reset during flash programming, it is possible to program a password by mistake. Please verify that no accidental reset occurs during programming. 

    Best Regards,

    Ben Collier