• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 33 subscribers
  • Views 263 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.

TPS65988EVM: Customer Use regsiter is not set

AlexZ
Prodigy 140 points

Part Number: TPS65988EVM

Hi.

I am using the Application Customization v6.1.1 tool to set some byte value in the Customer Use register. I then save the full bin (I can detect those bytes inside the raw binary), re-flash and reset the EVM. When I connect with the FTDI Debug option, the Customer Use registers do not have those values anymore. Am I missing something?

Thanks,

Alex

  • 0
    TI__Prodigy 350 points

    Alex,

    This is something that we have just started noticing. It appears the FTDI driver can be somewhat flaky when flashing a device. Both TIVA and Aardvark are far more robust. 

    When you see this occur please try reflashing the EVM again and power cycling the EVM. The changes should now be there.

    We are looking into seeing if there's any way we can comprehend this within the tool and work around the the FTDI driver limitations.

  • 0 in reply to Robert Almendarez
    Prodigy 140 points

    Hi Robert,

    Thanks for the explanation. I think we are actually facing a different issue, because I tried the same scenario with setting the Customer Use registers on both ports from the app. What I got on reboot was actually the value that I originally configured for port 2 on both ports. So for me it seems like it is an issue with the actual firmware running on the PD chip. Reading register 0x06 form both ports returns the value configured for port 2. Could you please verify this on your end?

    Thanks,

    Alex

  • 0 in reply to AlexZ
    TI__Prodigy 350 points

    Alex,

    Thanks for the update. Let me look into this and see if I can reproduce on my end as well.

    Please save and upload the pjt file that you were using when you see this issue. That'll help me with the reproduction of the problem.