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.

TSW1400EVM: Error Dialogs

Part Number: TSW1400EVM

Hello, I'm getting an error dialog when bringing up High Speed Data Converter Pro application.  It is the first one below (the top one). The software is running on 64 bit Windows 10 Enterprise.  What is this dialog telling me and is it a problem?  Another dialog that I'm getting is shown below (the second one from the top).  It occurs when I select the ADC.  It looks like the TSW1400 FPGA isn't getting completely programmed.  Can anyone tell me why this is happening?

Thank you.

  • Roger,

    Some of these errors are usually caused by insufficient power supply on the 5V supply. Can you ensure that the 5V current limit is at 2.5-3A? What we have seen is that there is an inrush current on the FPGA once the firmware is loaded that causes the 5V to limit and resets the FPGA.

    Let me know if this helps.

    Ken.
  • Ken,

    Thank you for your response.  I set the 5 V power supply current limit to 4 A.  I'm still getting these error dialogs.  I tried to do an acquisition and I got this dialog (below),  I'm not sure if it is related to what looks like a bad FPGA load.

  • Roger,

    When you load the firmware do the status LEDs light up or change in anyway?

    What ADC or DAC are you trying to run with TSW1400? Can you send a picture of the TSW1400 with firmware loaded?

    Usually the errors we see stem from the FTDI drivers not getting installed correctly (Admin issues), power issues, clocking issues.

    Ken.
  • No, Ken, the status lights do not change in any way.  The board that I'm using with the TSW1400 is the ADC3244EVM.  

    Here (below) are photos of the board(s)..

  • Roger,

    Those pictures are quite blurry. One thing that is obvious is that the ADC EVM needs a clock. Have you followed section 3.2+ in the EVM users guide?
    www.ti.com/.../slau579c.pdf

    You need to inject a clock into J9 CLKP - this is missing in your pictures. You will also need to ensure HSDC Pro has this frequency in the datarate section.

    Where in the users guide steps does it stop/error out?

    Ken.
  • Roger,

    One other note, when you install HSDC Pro please run the installer as admin - this will ensure it can install all of the drivers properly.
    Also when you run HSDC Pro, please run it as administrator (right click).

    Ken.
  • I did read that. I also read the TSW1400 data sheet that talked about clocks on the board to board connector. It sounded like the TSW1400 was providing the clocks. So it was clear that the ADC 3244EVM needed a clock when operating alone but it was not clear if it still needed a clock when paired with the TSW1400.
  • Let us know if providing a clock helps.

    Ken.
  • I put a 125 MHz, +10 dBm clock on the ADC3244EVM clock port. I ran the program as an administrator (it was installed as an administrator). I selected the ADC. I got the same load error dialog. In fact, I'm getting all the same dialogs. I tried to do a capture. I got the same error dialog. Nothing has changed.
  • Roger,

    If the firmware is programmed and none of the LEDs come on then there is something fundamentally wrong with the system.  If the firmware is not loaded properly, then nothing else in HSDC Pro will work right as it will try to interact with the firmware via the USB.

    Let me power this up in the lab and see if there are some things to check to debug what is going on.

    Ken.

  • Well, I de-installed the software and then reinstalled as an administrator. Then I ran it as an administrator. Nothing changed. Same result. Same error dialogs.
  • Well, Ken I did get rid of the first error dialog by logging in as an administrator. Our IT department saw the word "LabView" in the dialog and remembered that LabView won't run "as" an administrator, it will only run when logged in as an administrator. It has something to do with running a 32 bit LabView on a 64 bit machine. So, I'm guessing that first dialog error is irrelevant for the operation of the board and software.
    Unfortunately the other two dialogs are still occuring, that is, the bad FPGA load dialog and the other dialog.
  • Roger,

    Can you follow the attach PDF and see if this works for you?  Where does it no longer track?  Does device manage show the 4 serial ports?

    I just tried this and took some snap shots and everything works as expected.

    If you cannot get this to work, can you please give me the following info:

    HSDC Pro version

    TSW1400 rev

    Windows version/service pack/32 or 64b

    Also, can you check underneath the TSW1400 near one of the corners of the FPGA, R55 should be removed - some earlier versions had this installed and it could pose a problem.  R55 is located under the FPGA footprint across from pin2 of the JTAG connector underneath the board.

    ADC3244 + TSW1400 bringup.pdf

    Ken.

  • Well, there is no new information in this pdf file. First the A, B, C, D USB ports do show up in the device manager. Second when I first bring up HSDC Pro there is immediate deviation if I execute "as administrator". The deviation is that that first dialog talking about LabView appears if I bring up the software "as administrator" but if I am logged in as an administrator then that first dialog doesn't show up. Then there is no deviation until I select the "OK" button on the "Do you want to update the Firmware for ADC" dialog box. Instantly after I click this I get that second dialog talking about a bad FPGA load. The lights on the board do not change. The single LED is on and stays on and no other LEDs come on.

    HSDC Pro Version:
    GUI Version - 4.5
    DLL Version - 0.1
    Firmware Version - 15.5
    No Patch Applied

    TSW1400 rev: D

    Windows 10 Enterprise
    Version 1703
    64 Bit
    No mention of a service pack found
  • Oh, yeah and R55 is removed.
  • Roger,

    Can you confirm these set of resistors matches on your TSW1400 board?  If this TSW1400 is new from distribution then it should match - we have customers who share TSW1400 in the same lab and have modified the JTAG port to work directly with Quartus.

    The only other thing I can suggest if this resistor setup is the same is that you try HSDC Pro on another machine that is not running Windows 10 Enterprise.  We have tested HSDC Pro extensively with Win 7 and only a few laptops with Windows 10 (not Enterprise version).

    Let me know if you have access to a win 7 machine and if this works better.  If not we may need to swap out your TSW1400 hardware.

    Ken

  • The resistors in your photo match the resistors on our board.  All our Windows operating systems for all computers in our organization are Enterprise versions.  It is a top level organizational policy.  One of our local IT guys says that there is very little difference between Enterprise and Pro.  Did you test these boards on Windows 7 & 10 Pro?  I can bring a Windows 10 Pro from home.  Also, I have a Red Hat Enterprise Linux box available.  Do you have a Linux version?

    So, now what are the options?

    Thanks.

    Roger

  • Roger,

    We have extensively tested on Win7 as that is what a majority of our machines are here as well as with most of our customers. We recently started adding win 10 regression testing as well since we are starting to see this deployed both here and with some of our customers and have been fixing any discrepancies in our software as they come up. However our coverage of win 10 versions is a bit limited to due to availability of test platforms and OS versions.

    In most cases we have had driver issues due to window 10 having issues with drivers as well as some compatibility issues with the Labview RTE. Linux is not supported at this time.

    Currently we still don't know if there is a hardware issue or if this is a windows OS issue. If you can try HSDC Pro on win7 or maybe 10 pro we could at least confirm the hardware is ok and then we can focus on the win 10 enterprise issue. If the hardware also doesn't work right on win 7 then I can send you a replacement.

    I will also have the software team see if they can find an enterprise machine to try this on. Let me know if you can try this on a win7 or win 10 pro machine.

    Ken
  • Roger,

    After speaking with the software team, it seems there are some issues with the FTDI driver and Win 10. A new version of HSDC Pro should be going live in the next day or 2 that will address this - the current release is 4.50, the new release will be 4.70. Please try this out with your Win 10 Enterprise and let me know if this fixes things.

    Ken.
  • Ken,

    I found a 64 bit Windows 7 Enterprise notebook in the lab. I installed your software on it. First difference I noticed was LabView installation dialogs appearing. This didn't happen on the Windows 10 install. So, I ran the app and everything worked with no dialogs. Since the problem is clearly with Windows 10, I'm wondering why no one at TI caught such an obvious shortcoming right up front???? Well, only a week wasted.
  • Roger,

    I'm glad your hardware is working. Please download HSDC Pro 4.70 and give it a try once it goes live tomorrow. We would appreciate your feedback to help make the software more robust with Win 10.

    Ken.