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.

BP-ADS7128: BP-ADS7128: Hardware not connected

Part Number: BP-ADS7128
Other Parts Discussed in Thread: MSP432E401Y, ADS7128, BOOSTXL-DAC-PORT, DAC53401

Hi, TI folks,

I have the same problem as discussed in https://e2e.ti.com/support/data-converters-group/data-converters/f/data-converters-forum/1136823/bp-ads7128-failed-to-connect-to-msp432e401y-device?tisearch=e2e-sitesearch&keymatch=ads7128%20device%20not%20connected#

After I installed the device driver following the last comments from Bob B, I was able to flash the device. There was a success flag when done. 

Now the problem is that after I disconnect from debug port, and reconnect to USB data port, I got the following error. 

"Hardware not Connected. Please plug your Target Device into your Computer's USB port ..." 

The problem is that I can't see any new USB device detected in my Windows device manager after I plugged in the USB cable. Is there jumpers I need to move, or new drivers to install? 

A screen shot is shown below. Please help!  

William Xie

  • Hi William,

    Welcome to the E2E forum!  The BP-ADS7128 is powered from the MSP432E LaunchPad.  The Launchpad powers from the USB and the default power connection is from the debug port connection.  You can either plugin in two USB cables (one to each USB connector) or you can reconfigure USB power by following the directions in section 3.2 of the user's guide.  I have included the section below.

    Once the jumper is moved you should be able to power the boards from the USB data port connection.  The driver is a native MS-CDC driver that should install automatically and should show up in Device Manager under Ports (COM & LPT).

    Best regards,

    Bob B

  • Hi, Bob,

    Thank for the reply. I followed the step in the user's guide, and switched the jumper from JP6 to the middle of JP1 OTG location. Unfortunately, I still get the "Hardware not Connected" msg. My co-worker and I tried the process on anther LaunchPad/Dev module combo with a different laptop, and we still have the same error msg. 

    Attached is the setup for your reference. Any suggestions on what else I should try?

    Thanks!

    William

  • Hi William,

    The board is now being powered.  Have you checked device manager?  You should see something like:

    Do you see something like this?  If you do, then try to connect manually through the Options dropdown and select Serial Port.  From the Ports drop down you should see something like this:

    Let me know what you see or don't see.

    Best regards,

    Bob B

  • Hi, Bob,

    No new COM port showing up in the Device Manager. Below is the screen shot. 

    On the Serial Port Config, no option is available as a result. 

    Thanks!

    William

  • Hi William,

    Did you check to see if there are any 'unknown' devices showing up in Device Manager?  It is possible that the board has not enumerated properly.  If you have a spare micro B USB cable you could try plugging both connectors in at the same time and attempt to reprogram the micro on the LaunchPad.

    Let me know after you have checked Device Manager again for unknown devices and attempting to reprogram the LP.

    Best regards,

    Bob B

  • Hi, Bob,

    No new device is detected or Device Manager shows any changes when I plug the USB cable to the LaunchPad in and out multiple times. 

    As I mentioned in the first post, I was able to flash the device from the debug port. XDS110 side. I re-flashed it again, and then switch back to the data port side, the USB-OTG side. Unfortunately, still no new USB devices detected. 

    I also tried with both USB cables connected, but no success.

    Do I need to install any device driver for the MSP432E401Y? I am on Windows 11 Pro. 

    Thanks!

    William 

  • Hi William,

    This is very interesting.  The firmware uses a virtual COM port, so I find it interesting that the debug port is found but the data (OTG) port is not found or even attempts to enumerate.  If there were a driver issue (both ports use the same driver) I would expect that an enumeration would be attempted, but the device would show as an 'unknown' device.

    I have seen issues where the LP was damaged and the USB port doesn't connect.  But if you tried another LP that would seem to indicate the LP is probably ok and something else is happening.  What we do know is you are getting the flash successful message, and that connecting the cable to the USB data (OTG) port the power LED lights.  We also know that the LP enumerates using the debug port, but doesn't enumerate on the data port.  I have not verified operation using Win11 (TI only has Win10), but I have no reason to believe this is the problem especially if the download to the flash is working.

    So at this time I am at a loss as to what is happening.  You could try verifying that the 3V3 supply is at the correct voltage on the LP when connected to the data (OTG) port.  You could also verify that the red LED flashes when programming the LP.

    I can try running on Win11 at home but I will not be able to have the results until tomorrow.

    Best regards,

    Bob B

  • Hi, Bob,

    I did verify that there is 3.3V on the BP_ADS7128 board between one of the 3V3 and GND pins with a volt meter. So I will infer that there is 3.3v on both the booster board, as well as on the LaunchPad board when the board is pluuged on the OTG port. 

    Yes, when I was flashing the image on the debug port side, the RED LED was flashing.  

    I noticed that there are other reported cases that people had similar issue, like below. But unfortunately, there is no update on the final solution. Please do let me know the test result on your home Win11. 

    https://e2e.ti.com/support/microcontrollers/msp-low-power-microcontrollers-group/msp430/f/msp-low-power-microcontroller-forum/740418/msp432e401y-usb-not-connecting-to-computer

    https://e2e.ti.com/support/data-converters-group/data-converters/f/data-converters-forum/965480/bp-dac11001evm-hardware-not-connected

    Regards!

    William

  • Hi William,

    I had no issues running the BP-ADS7128/MSP432E401Y LP on my Win11 machine.  It does appear that the MSP432E is getting flashed correctly and as the green power LED comes on when the data (OTG) port is connected this leaves one option and that is the communication is not taking place as it should.

    I have used dozens of these LPs in the past and I only had one that had an issue with the USB data (OTG) port.  I could certainly believe that you have a board with an issue, but I would think the possibility of 2 boards having the same issue would be highly unlikely.

    All that said, from the links you provided it does appear that the failure of the USB port does happen.  You could take a look at the test points above the USB connector to see if there are any shorts on the pins.  There is also an ESD protection U2 that could be misaligned creating an issue.  There could also be a solder issue at the MSP432E as well.  It is a pretty straightforward connection and I have included a portion of the schematic from the LP user manual  below:

    If the issue is with the LP, which it does appear to be, then this is as far as I can take you as I support the ADC devices and not the microcontroller/LP.  The LP is handled by a different group and belongs to Microcontrollers forum.  When contacting the forum, I would suggest that you also add a link to this thread for background.  I wish I could do more, and I'm very sorry that you are having these issues.

    Best regards,

    Bob B

  • Hi, Bob,

    I have some update on the BP-ADS7128 issue, and would like to get your suggestions. 

    I received another two LP boards to experiment with. On both boards, I can see the ACCtrl COM ports after connecting to the USB ORG port, like below.  

    I installed the DAC53401 EVM and its Booster board (BOOSTXL-DAC-PORT) on the two new LPs. After launching the DAC53401 GUI, I can successfully connect to the DAC53401, and manipulate its registers. 

    But again, if I install BP-ADS7128 on both boards, I have the "Hardware not Connected" error msg again. This time, the new COM ports are still present on my laptop, but the ADS7128 GUI can't detect them, shown below. 

    Can you check the version of the ADS7128 GUI I downloaded against the version of what you are using? The SW tool versions is shown below. 

    Thanks!

    William

  • Hi William,

    If we take a step back and go through the steps, I think we can discover what is going on.  Without changing any jumpers on the LaunchPad (or return them to the original positions if you moved them) plug two cables into the board (one to each USB connector).

    Open the GUI (you are using the most current as shown in your last post) and select FIle->Program Device.  You will need the firmware that is included with the GUI.  The DAC booster pack uses a different firmware and the GUI will not recognize it.

    Once the program is downloaded the firmware should now be recognized and automatically connect.  If it does not not, check the Serial Port Selection to see if you can locate the correct COM port:

    If you do not see this selection from the drop-down menu, check Device Manager.  You should see both the ACCtrl and XDS110 showing up similar to as shown below:

    If you are still having issues, then press F12 in the GUI which should show the GUI debug console. Press the hardware connect link at the bottom left side of the GUI and then take a screen shot of the console and attach here so that I can review the response.

    Best regards,

    Bob B

  • Hi, Bob,

    Before I start the test, I want to confirm it's OK for me to have jumpers on both the 5V-OTG and 5V-XDS, along with USB cables on both the debug port and data port since I will be connecting the XDS_VBUS and TARGET_VBUS together. 

    Thanks!

    William

  • Hi William,

    As I stated in my last post, put all jumpers in the original position.  This means only one jumper should be connected and be placed on the 5V-XDS only.

    Best regards,

    Bob B

  • Hi, Bob,

    Did the experiment as suggested. Please review the attached screen shots. In short, the COM port is still not showing up in the ADS7128 GUI, even though the laptop device manager shows it. 

    Regards!

    William

  • Attached is the debug console output. I did a few round of trying to find out whether or not a COM port might be visible from the GUI, an follow with hitting the connect icon. 

  • Hi William,

    At this point the most likely issue is related to the EEPROM on the BoosterPack not properly programmed.  With the LP connected and powered attempt to properly program the board EEPROM by using the following steps:

    • Connect a shunt on J4 on BP-ADS7128, the write protected jumper on the BoosterPack.
    • Open EEPROM loader https://dev.ti.com/gallery/view/PADC/EEPROM_Loader/ver/1.4.1/ . Once opened, the landing page of EEPROM loader should show as connected on the bottom left
    • In the first drop down menu, Choose Controller: select “AEVM”.
    • In the second drop down menu, Choose device: select ADS7128.
    • Click on the Write and Verify button, you should see write successful message  
    • Remove shunt between pins of jumper J4.
    • Close EEPROM loader and retry the ADS7128 application GUI.

    Best regards,

    Bob B

  • Hi, Bob,

    Please see the attached screen capture with EEPROM loader.

    When I try to "Write & Verify", it will show "No Devices" at the lower left corner. The jumper is placed on J4. 

    Regards!

    William

  • Hi William,

    That is a response when the program cannot find the EEPROM.  There is a similar response with the GUI as shown from the console screen capture you showed as the I2C bus is timing out.  Make sure that the BoosterPack is making the correct contact with the LaunchPad connector.  It is very easy to misalign the header/socket and either get off by a row or a column.

    You can also verify that the voltages are correct to the board.  You should be able to measure 3.3V and 5V at the BoosterPack header with a digital multimeter.  Without communication you should also be able to measure 3.3V at the SCL and SDA testpoints at the middle of the BoosterPack.  If either SCL or SDA are showing logic low, then there may be a shorted device pin on the pathway for the I2C communication or there could be an issue with the DVDD supply.  You should also check and verify the voltages at TP1 (AVDD) and TP2 (DVDD) near the top of the BoosterPack.  Both of these voltages should be 3.3V.  Let me know what you find.

    Best regards,

    Bob B

  • Hi, Bob,

    I checked the 5V and 3.3V input on the BP-ADS7128 board, and I can see 5V, not the 3.3V. But the corresponding pin on the LP side does have 3.3V. A little wiggle on the BP board seems do the trick to make the contact between BP and LP boards. So it looks like the header pin contact is sketchy. 

    Then I proceed to program the EEPROM contact. This time it's successful!

    After I removed the J4 jumper, and close the EEPROM Flasher to release the COM port, now I can finally connect to the BP-ADS7128, and I can manipulate the registers. 

    Here is a short summary for what we went through to get it work so that other folks can reference in their debug process.

    1. LP board could be defective. I had two bad ones from TI directly. The two other brough from Mouser works.

    2. BP and LP header contact could be flaky. 

    3. BP EEPROM content could be un-initialized, or not initialized correctly.

    4. Only one jumper at JP1 for 5V_XDS or 5V_OTG on the LP board

    A final screen shot below to show the successful Hardware connection. 

    Bob, thank you very much for the debug guide. Really appreciate your help!

    William

     

  • Jumpers on 5V-OTG and 5V-XDS with USB plugged in the data port side works. 

  • Hi William,

    I'm glad you finally made some progress.  Most likely you didn't need to program the EEPROM as the 3.3V was missing and I2C pullups were ineffective.  On the positive side, you were able to increase your troubleshooting skills.

    Best regards,

    Bob B