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.

MSP-EXP432E401Y: board breakdown afrer program PMIC TPS65941213 and TPS65941111

Part Number: MSP-EXP432E401Y
Other Parts Discussed in Thread: TPS2052B, DRA829

Tool/software:

Hi,

I use the board MSP-EXP432E401Y to program NVM on PMIC TPS65941213 and TPS65941111(SCH is the same as TI PROC112A but VCCA is 5.0V).

For convenience, I short PIN3 and PIN5 on JP1, and program TPS65941111 successful on GUI.

But after this, I can not program the PMIC again and I find the COM on my computer is disappear. 

I re plug and unplug the USB(the power is down and on again), and I still can not see the COM on my computer.

Then I download MSP-EXP432E401Y again, I only see "Stellaris Device Firmware Upgrade" on my computer.

I download blinky_MSP_EXP432E401Y_nortos_ccs.projectspec in simplelink_msp432e4_sdk_4_20_00_12, than I find the code run normally and can run one-step mode, but the PIN state is error.

No mater the code set the PIN PN0 high or low, the voltage of the PIN PN0 is 0.8V,

When I change the code to set PIN PN1, and the voltage of PIN PN1 is still 1.7V(on one-step mode to set the PIN high or low).

By this I am sure the chip MSP432 on the MSP-EXP432E401Y is breakdown.

I want to know is there any wrong with short PIN3 and PIN5 on JP1?

How can I repair the board? Return the board to the factory or buy a new chip for replacement?

Thanks.

  • Hello Huang,

    You shorted the Target VBUS and Debug VBUS pins by doing so if you have a voltage applied to the Debug VBUS by having a USB cable plugged into the Debug port, then you can create a situation where both VBUS pins are being powered at once which will cause a conflict in power supply and could damage the board. That connection really should not be made or if it is, it has to be done with utmost care and understanding of what you can / can't power.

    I would not consider this board eligible for return as that was an ill-advised action taken to tie two voltage pins together.

    Best Regards,

    Ralph Jacobi

  • The board only provides one USB cable, so it is impossible that Target VBUS and Debug VBUS powered at the same time. This is why I short the Target VBUS and Debug VBUS.

  • Hello Huang,

    That is not a correct understanding of the board at all.

    The Target VBUS is generated on the LaunchPad based on the USB peripheral of the device. There is an IC that is enabled when the TM4C device is in a state where it is intended to be a USB Host that may need to provide VBUS.

    Therefore by shorting these pins together while the Debug VBUS port is connected, it is possible that the 5V input from the Debug VBUS port can conflict with the 5V Target VBUS that is generated on the LaunchPad.

    Furthermore I didn't think of this case last night but even if the TM4C is not enabling the IC that generates the 5V VBUS, you would now be injecting a 5V signal into the output of an IC and would cause undefined behavior for that IC and the system as a whole.

    Best Regards,

    Ralph Jacobi

  • Thank you for your reply.

    I check the power path but can not find any path and any IC which will be conflicted. 

    JP1 is jump PIN3 and PIN5. USB101 do not connect anything and U7 connect USB cable.

    The power path is U7(TARGET_VBUS)->JP1(DEBUG_VBUS)->J101(XDS_VBUS), than it creat XDS_VCC and return to +3.3V/MCU_3V3 from J101 and JP2.

    I only find VBUS is used for chip U4, but it do not work because PIN2(VCC) is no power. So there will be no conflict between VBUS, DEBUG_VBUS and TARGET_VBUS

    Otherwise, I need a tool that can progam the NVM of PMIC(TPS65941213 and TPS65941111).It is troublesome to use MSP-EXP432E401Y if it needs two USB cable. Do you have any recommended tools?

  • For convenience, I short PIN3 and PIN5 on JP1, and program TPS65941111 successful on GUI.
    I want to know is there any wrong with short PIN3 and PIN5 on JP1?

    Hi, 

      Please refer to the user's guide. There are three positions for JP1. There is no position to connect between pin 3 and pin 5. Why are you connecting between 3 and 5? I'm not familiar with TPS65941111 or any TPS products. Is this what TPS65941111 user's guide or demo ask you to do? If not, you should just leave it in the default position which uses Debug USB port to provide power to the board. 

  • Hi,

    For using the board as a tool which can program PMIC for factory, I need it only use one cable.

    So I review the SCH of the board, than I see I can short PIN3 and PIN5 on JP1 and put the cable into the U7.

    For the beginning, it works well. But than it gets problem and I can not see any wrong with it.

    So I have two questions:

    1) What is wrong with this using?

    2) Is there a tool that can progam the NVM of PMIC for factory?

  • Hi,

    Do you have another MSP-EXP432E board that you can try? As I mentioned I don't really see a reason for you to change the jumper setting if you simply just want to download some TPS firmware onto the target device on the LaunchPad. 

     Are you trying to provide power to the MSP-EXP432E board through the boosterPack connector perhaps  from your TPS board in which case you should change the jumper setting to connect between pin 1 and 2. Please note that when you are sourcing power from a 5V source from the boosterpack connector, the on board TPS2052B does not have current limiting. You could potentially damage the target device if overcurrent. 

    So I have two questions:

    1) What is wrong with this using?

    2) Is there a tool that can progam the NVM of PMIC for factory?

    I'm not familiar with the TPS65941111 product but I think you are just using the MSP-EXP432E LaunchPad to program the TPS via either the I2C or the SPI bus. I think any MCU with the I2C or SPI capability can be used to program the NVM on the PMIC. Since I'm not an expert on the TPS products, I will forward your question to the TPS support on how to program the NVM. 

    Are you using some type of TPS65941111 EVM board or you own custom board?

    As far as the MSP-EXP432E launchpad, I don't really see a reason for you to change any jumper setting. You should only need to download the TPS firmware through JTAG onto the MSP432E MCU device on the board and connect either I2C or SPI bus between the LaunchPad and the TPS. But if you are trying to supply power to the TPS board or taking power from the TPS board then you should change the jumper setting to pin1 and 2 as I mentioned above.  Again, I will let the experts in the TPS support team assist your questions. 

  • Hello Huang,

    The TPS65941213 & TPS65941111 are form this guide: User’s Guide Optimized TPS65941213-Q1 and TPS65941111-Q1 PMIC User Guide for JacintoTm 7 J721E, PDN-0C

    There are no mentions of this pair being set for 5V0 on VCCA, so how is it able to be 5V0?

    I am assuming that on this board are the factory used TPS65941213 & TPS65941111 which relies on 3V3 and it's trying to be flashed to 5V0 on VCCA which is where the problems start coming up correct?

    Other assumptions are I2C connection from the MSP board to the TDA board.

    Best Regards,

    Nicholas

  • Hi, 

    I replace the mcu and the board works well.

    I use the board to program self-made board.

    I will use two cable which one for power from USB101 and the other for USB connect from U7.

    The next problem I will ask TPS group and DRA829 group.

    Thanks.

  • Hi,

    I can see VCCA supports 5V power supply from the datasheet  and the register of VCCA_PG_WINDOW.

    My own board is high power, so I can not use 3.3V for the input power of PMIC.

    The next problem I will ask TPS group and DRA829 group.

    Thanks.

  • Hello Huang,

    while the device can support 5V from the datasheet, it needs to be programmed in order to do.

    As it currently stands the TPS65941213 + TPS65941111 expect 3V3 on the VCCA PIN, it's comparators for what is considered safe is relative to this level.

    This is mentioned in the User's guide I had selected below:

    Setting 5V on the input of the PMIC on the input side of the safety FET will trigger the OVP protection and dead lock the PMIC until it's power cycled again.

    VSYS_DEAD_LOCK_EN is enabled on this device and from the datasheet excerpt below when set to 3V3 the deadlock triggers around 4V:

    Please be aware of this, as this could be the source of your issues.

    BR,

    Nicholas McNamara