• State Resolved
  • Locked Locked
  • Replies 1 reply
  • Subscribers 63 subscribers
  • Views 326 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.

BQ79600EVM: BQEVMs MSP430

Priya Nadathur
Intellectual 545 points
Part Number: BQ79600EVM
Other Parts Discussed in Thread: USB2ANY, BQ79616

I have been trying to talk to the BQ EVMs with the MSP430.

 

I have now come to understand the USB2ANY connector is the best point of connection. I did try other different ways to connect (the same pins used by the Hercules launchpad on the BQ79600 EVM). Some errors may have happened here.

 

In connecting the MSP430 to the BQ79600 EVM, I am able to generate a successful wake up of the BQ79600 device, the DVDD LED comes on indicating the BQ device enters ACTIVE mode. The signals being transmitted out of the BQ79600 EVM J15 connector are attached. This wakeup tone is not activating the BQ79616 EVM.

 

I then checked if the USB2ANY can talk directly to the BQ79616 EVM. I am not getting a response back. I have two BQ79616 EVMs. They are both not responsive. I made sure to use the BQ79616 EVM I have not used for past trials to connect directly to the MSP430. My past trial connecting MSP430 to the BQ79616EVM was not successful. Here I tried the FTDI connector as well.

 

Is it possible surges on the VIF interface between the BQ79600 EVM could have passed through to the BQ79616 EVM and caused damage?

 

Please see the attached schematic showing the entry point of the VIF signals. To use the onboard choke on the BQ79616 EVM user guide recommends depopulating resistors R69, R79, R72, and R74 (page 16, of the EVM user guide). Maybe this should be R69, R79, R68, R78 instead? The user guide also recommends populating a transformer on the EVM. I suspect diodes D2 and D5 may need replacing (if not populating the transformer), in addition to the BQ79616 chip.

 

The other problem I ran into when using the BQ79600 EVM is when connecting the 12V power supply adapter to the TP. There is no cap or regulator with this test point and there was a spark followed by burning smell. One of the two BQ79600 EVM is not responding anymore.

 

Appreciate your pointers. If we can rework the EVMs and get them working, it will help.

  • 0
    TI__Genius 14890 points

    Priya,

    Sorry for the delayed response. The team was out for the holiday.

    Please confirm that the BQ79616 boards are unmodified. If they are, most likely the BQ79616 EVM has been damaged. I suspect an improper connection during these trials may have put a high voltage or negative voltage on one of the communication pins. If this path is damaged, the device will no longer respond to wakeup commands. I recommend replacing the EVM - yes it may be possible to replace the chip and ESD diodes, but it will be difficult to debug if more components are damaged. On the new EVM please verify the BQ79616 EVM works correctly with the USB2ANY connection and the GUI before trying your other setup.

    If you have made changes to the BQ79616 EVM, then it is possible that you removed R72 and R74 without populating a transformer. In this case, the device will no longer receive VIF communication from lower in the stack (BQ79600 in this case). I recommend testing with cap isolation (without choke) for now and we can review the setup and modifications for CAP & choke or transformer isolation after we solve the communication issue.

    Related to the BQ79600 damage, it is possible that you had an incorrect jumper configuration when applying 12V - it could have been still set to 5V. Or you placed the supply on the incorrect test point. Or if the supply polarity was reversed, that can easily cause damage.