TPS650860EVM-116: Device Description File Not Working

Thanks for the update. I ended up finding the instructions above and successfully loaded my configuration from the OTP generator.

I have a seperate issue (can open another forum post if necessary) where I cannot put the PMIC into "Test Mode" / Programming Mode. Following Step 8 in the "Programming Steps" section of the BOOSTXL-TPS650861 EVM User’s Guide.

Receive 2 messages:

1. Programming state enabled

2. USB2ANY Failure: -44 ERR_I2C_ADDR_NAK
According to USB2ANY spec: Address not acknowledged (NAK)

In the "Device Controls" section the Test Mode description text (quoted below) refers to the BOOSTXL-TPS650861 board, while I am using a TPS650860EVM-116. Is there different device support that needs to be installed for this EVM? If not, than how can I enter Programming Mode on my EVM?

Test Mode description in "Device Controls" menu:

(1) Test Mode: Enables programming state. This button sets GPIO_12 of MSP430F5529 to output 3.3 V, resulting in 7V on PMIC CTL4 pin on BOOSTXL-TPS650861 board. After 400 ms, it sets the PROGRAMMING_STATE bit = 1b so 7V on CTL4 of PMIC can be removed. After 400 additional ms, it sets GPIO_12 of MSP430F5529 to output 0 V, returning CTL4 to normal. If not using BOOSTXL-TPS650861, 7V must be applied to CTL4 first or else the write will fail.

Hi Helios,

Are you providing power to the EVM board in any way? I have seen this NAK error when power is not sufficiently provided. 
Please ensure the sufficient VSYS is being provided.

I also want to confirm that even though you are using the TPS650860EVM-116, have you swapped the main IC with the User Programmable TPS650861 ?

Helios Lyons said:

If not using BOOSTXL-TPS650861, 7V must be applied to CTL4 first or else the write will fail.

For programming, a stable 7V needs to be provided to CTL4 pin. The BOOSTXL-TPS650861 accomplishes this internally with a MUX
For your case, you would just need to ensure that you can provide 7V to this pin. 

Best Regards, 
Sarah

1. I was providing 8V to VSYS, which falls above the minimum 5.4V indicated on the TPS65086x EVM User's Guide

2. What do you mean swapped the main IC? The IC on the EVM is a TPS650860A0. My design uses a TPS65086100, and this is the sequence and OTG values that I am attempting to validate - is this the incorrect kit?

3. I'm unable to find the external CTL4 pin on which to provide 7V exposed on the EVM -- I can only see the related TP49 / DIG_1P8V. 

Considering that the datasheet also states that 7V should only be provided for under a minute or so, how would you recommend testing this? 

Thank you,
Helios

Hi Helios, 

The IC TPS650860A0 , that comes on the TPS650860EVM-116 is not user-programmable.

The TPS650861 is the user-programmable version, and is the intended device for the TPS65086100 OTP Generator.

I believe you may be using the wrong kit for your design. You would need a TPS650861, and this would be more convenient to program it with the BOOSTXL-TPS650861 EVM. 

Apologies for the confusion. Hope this helps to clarify.

Best Regards. 
Sarah Lao 

Hi Sarah,

To be clear, there is no way to test our program / desired startup sequence and PMIC parameters on the TPS650860A0 PMIC (as part of the TPS650860EVM-116)? Can you help me understand the difference between them, and what it means to be user-programmable? 

I ask because using the IPG-UI I seem to be able to modify register values in the TPS650860A0 PMIC currently on the board.

Thanks,
Helios

Hi Sarah,

Thank you for the clarification, we will move forward with testing on the TPS650860A0 as best possible.

I work for Disguise that is using the PMICs for products currently in development -- would it be possible to get a point of contact in order to receive information like this ahead of time for future development? This would be very useful, and I am happy to escalate. 

Looking forward to hearing from you,
Helios

Hi Helios, 

Of course, I've reached out to the marketing team for a point of contact I can direct you towards.
I'm still waiting to hear back, but I will let you know as soon as I get that information for you. 

Thanks, 
Sarah

Afternoon Sarah, 

I am reviving this thread as we are having further issues using standard I2C hardware to write to the TPS65086100 PMIC on our development board. Are there any particularities with timing that should be adhered to? The issues are quite unusual, as the registers can be read (inconsistently) and not written to. Considering the PMIC is on our board with an exposed I2C header, would you recommend any TI hardware for interfacing with it?

Thank you,
H.

Hi Helios, 

Here are the expected timing values for the I2C interface:

Can you clarify what mircocontroller/hardware you are currently using on your development board to perform I2C read/writes?

And is there a specific register(s) which you are having trouble writing to? The inconsistent reading is strange,
but are you able to cross-reference your registers with the register map listed in section 5.11 of the datasheet,
to ensure they are on the list of registers that can be accessed without being in programming mode?

Best Regards, 
Sarah

We are using a Raspberry Pi 4 for I2C comms, which has worked with many other devices. We can read registers correctly, including those at address 0x38 when CTL4 is set to 7V (programming mode) but cannot write to most registers. The IRQ mask register is writable, but the BUCK1CTRL register remains unchanged despite attempts to write to it. 

We also just received the MSP430F5529 board and flashed it with the USB2ANY firmware. It recognises the PMIC, and we can use IPG-UI to read register values, but exhibits the same write issues. 

We suspect that there is something like a GPIO line that needs to be driven in order to entire programming mode, or there is a correct series of operations. It essentially seems to be write-protected, but there is no indication this should be the case in the documentation. We are finding the quantity of documentation between the same range of products to be problematic, and would appreciate guidance in navigating this to program our PMIC.

Looking forward to hearing from you,
H.

Hi Helios, 

Are you following the steps in the TPS65086100 Non-Volatile Memory Programming Guide:

Specifically, the writing to the OTP_CTRL1 register, PROGRAMMING_STATE bit? This could be preventing the writes to the 0x38 registers. 

"In order to access the registers in device address 0x38 the TPS65086100 must first be put into programming mode by writing the PROGRAMMING_STATE bit in the OTP_CTRL1 register to 1b. In order to access this register, 7V must be placed on the CTL4 pin. Once the PROGRAMMING_STATE bit in the OTP_CTRL1 register is set to 1b, remove the 7V from the CTRL4 pin. Once this is done all of the registers in the device can be accessed."

I apologize for the inconvenience in the documentation, and I agree that it is difficult to navigate.
I will push for getting our document library cleaned up and organized better.

Let me know if you are still unable to write to these registers.

Best Regards, 
Sarah 

Hi Sarah,

Apologies for the delay. I have secured a copy of the PSU dev board and am indeed unable to write these registers. My setup is IP-GUI on laptop <-> USB2ANY interface adapter <-> PMIC (on PSU dev board). I cannot follow the official procedure as the PMIC is already soldered to the board. That said I have made an external switch board to ground the CTL pins and apply 7V to CTL4. The current issue is I am not getting any I2C comms out of the USB2ANY interface adapter I2C lines. Do I need to use it in conjunction with the BOOSTXL-TPS650861 or some related part? 

As a brief update, I am currently using a Raspberry Pi and able to see the device at 0x5e, and the device at 0x38 when 7V is applied to CTL4. However the programming state is not persistent, and when I write the value 0x80h to the OTP_CTRL1 register in order to set the PROGRAMMING_STATE bit I cannot get the value to persist, and thus the device to stay in programming mode.

Looking forward to hearing from you,
Helios

Hi Helios, 

The programming setup is easier with a BOOSTXL-TPS650861 or socketed board, rather than a soldered-on board.
But the USB2ANY / IPG-UI setup should also be able to work on your custom board.
Is the GUI recognizing the device as Hardware Connected?

From there, using the IPGUI steps should follow the same as listed in section 4.4 of the BOOSTXL-TPS650861 EVM User’s Guide, particularly paying attention to the Device Controls tab instructions in Step8.

Are you able to see if using the "Test Mode" button has more success in setting the PROGRAMMING_STATE bit ? 

Best Regards, 
Sarah

IP-GUI is recognising the USB2ANY as "Hardware Connected". When I hook up my logic analyser to the I2C output of the USB2ANY nothing is being written through, which means it cannot be used to program the PMIC. For some reason I can read values from the USB2ANY.

Hi Helios, 

When you say that "nothing is being written", are you seeing absolutely no toggles on the logic analyzer when attempting to write?
This may be an indicator of issues with the host device, not the PMIC. 

Can you clarify if this is the issue?

Best, 
Sarah

Apologies if I was unclear, yes I confirm I am seeing no toggles on the USB2ANY I2C lines when writing values with IP-GUI (verified with external Salae logic analyser). I can also "read" from the USB2ANY device (not the PSU board connected via I2C) -- it is as if there is a buffer in USB2ANY that contains some relevant register values.

Hi Helios, 

Glad to hear that the I2C is now working properly. Thank you for the update!

Best,
Sarah