• State Resolved
  • Locked Locked
  • Replies 19 replies
  • Answers 4 answers
  • Subscribers 64 subscribers
  • Views 1858 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

LED171596A: Was LED171596A EVM version changed recently?

Kazuya Nakai59
Guru 20100 points
Part Number: LED171596A

 Hello guys,

 One of our customers is evaluating LED171596A using the device EVM. They bought  the EVM in last month (March) and the EVM worked without any problem with GUI control software and MSP430 launch pad. According to the silk printing on the EVM PCB, the EVM version they boght in March is Rev.E1 and the board color is green.

 They bought 3 EVMs of LED171596A as additional this month (April). But all of those EVM didn't work with same GUI control software and launch pad for Rev.E1. All EVMs version are Rev.A and All PCB color are red.

  Could you please give me your answer to the following questions?

1. Which version is the official EVM at this moment?

2. Can both versions work correctly with same version of control software and MSP430 launch pad?

3. When the answer for No.2 is No, how they can use the EVM correctly? Do they need another version of control software and lauch pad?

 Your answer would be much appreciated.

 Best regards,

 Kazuya Nakai.

  • 0
    TI__Intellectual 2090 points

    Hello Kazuya,

    EVM Revision A (red) is the latest version of the EVM and both E1 (green) and A (red) work with GUI and TIVA4G123 Launchpad.

    Best regards,
    Randy

  • 0 in reply to Randy Dahl
    Prodigy 40 points

    Where is the GUI located? I can't seem to find it.

  • 0 in reply to Diarra Anderson
    Guru 20100 points
    Hello Randy,

    Thank you for your reply. I asked the customer to check the board connection and jumper position again but all of REV.A EVMs didn't work. They confirmed REV.E worked well. they just replaced REV.E with REV.A after the confirming but all of REV.As didn't work.
    Do you have any idea about the cause? Is there any check point the customer should do? For example, to check whether VDD is powered up to 3.3V or not? Also is I2C signals (SDA,SCL) are supplied from TIVA launch pad?

    Thank you and best regards,
    Kazuya Nakai.
  • 0 in reply to Kazuya Nakai59
    TI__Intellectual 2090 points
    Hello Kazuya,

    Can you provide more detail on what is not working? No SPI/I2C communication or LED not turning on? It would be most helpful if you could take a photo of teh REV.A EVM so I can see the jumper configuration.

    thanks,
    Randy
  • 0 in reply to Randy Dahl
    Guru 20100 points
    Hello Randy,

    Thank you for your reply.
    The customer problem is that they can not turn on LEDs using Rev.A.

    The jumpper positions are the follows.
    IVDD: 1-2 short
    VLED_SEL: 2-3 short
    BEN: 1-2 short
    VIN_SEL: 1-2 short
    ISET: 2-3 short
    SEL*: 1-2 short

    Also they confirmed the following points by oscilloscope.
    1. VDD(No.31) pin of LED171596A is supplied by 3.3V.
    2. VLED(No.38) pin is supplied by 5V.
    3. SCLK_SCL(No.44) is clocking H/L level.

    And they found that flashing pattern of LEDs on TIVA Launch Pad are conpletly different between Rev.E connection case and Rev.A connection case. Of course, TIVA Lauch Pad is same to drive Rev.A and Rev.E.

    Do you have any idea about the cause of the problem?

    Best regards,
    Kazuya Nakai.
  • 0 in reply to Kazuya Nakai59
    Prodigy 40 points

    Hi Kazuya,

    I have a rev. A board (red) and I can't get it to work with the gui either. Let me know if you find a solution.

    Thanks

    Diarra Anderson

  • 0 in reply to Diarra Anderson
    TI__Intellectual 2090 points

    Hi Kazuya,

    I have a rev. A board (red) from same lot and don't see any issue.

    The jumper settings look okay, can you send a screenshot of the GUI?

    I need to verify the GUI and FW version the customer is using.

    I have attached the latest version of the GUI software (the link is under LED171596A instead of LED171596AEVM).

    thanks,

    Randysnvc215.zip

  • 0 in reply to Randy Dahl
    Guru 20100 points
    Hello Randy,

    Our customer tried to control LED171596A EVM after the GUI software (snvc215.zip) installed but they could n't control the EVM. Their PC model is Dell Latitude 5490 which works with Windows10 Pro OS. Can the GUI software work correctly with the OS?

    Thank you very much and best regards,
    Kazuya Nakai.
  • 0 in reply to Kazuya Nakai59
    TI__Intellectual 2090 points
    Hello Kazuya,

    I will need to look into this, in the mean time please confirm that the Green board works with GUI and Windows 10 Pro but only Red board does not work. Also please confirm that both are using same TIVA4G123 Launchpad board.

    Best regards,
    Randy
  • 0 in reply to Randy Dahl
    TI__Intellectual 1985 points

    Hi Kazuya,

    It is crucial  to confirm if the SAME launchpad working on the SAME computer(OS) is having problem with different EVM (red and green). 

    On some computer, there is a problem with ICDI driver installation that cause the GUI not to work under windows 10. 

    First step is to check if the driver for Tiva Launchpad is installed correctly on the system. If the driver is installed correctly, you should see the virtual com port show up in Device Manager when you expand the item "Ports(COM &LPT1) "as shown below. The actual COM number will differ. If the COM port show up as “USB Serial Device (COMX)”, the ICDI driver is not installed correctly,, it should be “Stellaris Serial Virtual Port (COMX)”.

    If you are running in Windows 10; go to the folder where the driver is downloaded, right click on the file stellaris_icdi_com.inf, and select install. If this works, the name of the virtual com port should change from “USB Serial Device (COMX)” to “Stellaris Virtual Serial Port (COMX)”; and GUI should work after this change if the firmware on Tiva Launchpad is programmed correctly. 

    Regards

    H L

  • 0 in reply to Hak-Leong Ng
    Guru 20100 points
    Hi Hak, Randy,

    Thank you very much for your help.

    I comfirmed the followings.

    1. please confirm that the Green board works with GUI and Windows 10 Pro but only Red board does not work.
    Also please confirm that both are using same TIVA4G123 Launchpad board.
    >>> Yes. They are using same TIVA4G123. When the green EVM board is connected to the TIVA4G123,
    the EVM can be conrolled by GUI on windows 10 PC. But when the RED EVM board is connected to
    the same TIVA4G123(exchanged EVM only), the EVM can not be conrolled. When red EVM is connected to
    TIVA4G123, "Hardware Disconnected" is shown on the bottom of LED171596A EVM control GUI screen.
    They have 3 piecies of Red EVM and all of the red EVM don't work on the TIVA4G123.

    2. "Ports(COM &LPT1) "and "Stellaris In-Circuit Debug Interface" in Device Manager.
    >>> They confirmmed that "Stellaris Virual Serial Port (COMx) is in "Ports(COM &LPT1) "
    and "Stellaris ICDI DFU Device Interface" and "Stellaris ICDI JTAG/SWD Interface"
    are in "Stellaris In-Circuit Debug Interface".

    Is there any circuit difference between Green EVM and RED EVM?

    Thank you very much and best regards,
    Kazuya Nakai.
  • 0 in reply to Kazuya Nakai59
    Guru 20100 points
    Hi Hak, Randy,

    I forgot one thing I wanted to tell you. When the Red EVM is connected to TIVA4G123, LED on the TIVA4G123 is changing color to many colors. But Green EVM is connected, the LED color is blue only. Is thhis any clue to find the cause. The customer want to resolve this issue because they need to start LED171596A evaluation as soon as possible for next projects.

    Thank you and best regards,
    Kazuya Nakai.
  • 0 in reply to Kazuya Nakai59
    TI__Intellectual 1985 points
    Hi Kazuya,


    This is very strange. A brand new TIVA4G123 Launchpad comes with a demo program which will change the color of the LED gradually, if you are seeing all colors including green, most likely the Launchpad is not programmed.

    If the firmware is programmed correctly on the Launchpad , the LED should be solid blue when there is no communication between GUI and Launchpad; it will blink with the mix of two colors (red and blue) when GUI is communicating with the Launchpad.

    You can try the following,

    1. Connect the Launchpad (No EVM) to the computer, run the GUI, you should see "Hardware Connected" at left bottom corner of GUI, and the LED should be solid blue.
    2. Close GUI, connect the green EVM, run GUI, check the status on hardware connection.
    3. Close GUI, disconnect green EVM, run GUI, check the status on hardware connection and LED color.
    3. Close GUI, connect the red EVM to the same Launchpad, run the GUI, check the status again.

    Try to do all these steps on the SAME computer so we can have a clearer picture on what is going on. Close GUI when swapping the hardware. Sometimes, disconnect/connect the hardware while GUI is running takes longer for the GUI to re-sync with the hardware.

    I cannot understand why the LED on Launchpad can behave differently when connect to different EVM... Please confirm it is the exact same physical Launchpad they are using.

    Regards
    H L
  • 0 in reply to Hak-Leong Ng
    TI__Intellectual 1985 points
    Hi Kazuya,

    Need to clarify something in previous post. When I mentioned "the Launchpad is not programmed", I meant to say "the Launchpad is not programmed with the correct firmware to work with the GUI".

    Regards
    H L
  • 0 in reply to Hak-Leong Ng
    TI__Intellectual 1985 points

    Hi Kazuya,

    Any update on this issue? Did you get a clearer picture on the failure mode with those experiment I suggested?

    Regards
    H L

  • 0 in reply to Hak-Leong Ng
    Guru 20100 points
    Hi H L,

    I asked the customer to check those experiment last week but I have not get the result yet. I will ask again and I will inform you the result as soon as I get it. Could you please wait for the result for a few days?

    Thank you and best regards,
    Kazuya Nakai.
  • 0 in reply to Kazuya Nakai59
    TI__Intellectual 1985 points
    Hi Kazuya,

    Just checking, any updates?

    Regards
    H L
  • 0 in reply to Hak-Leong Ng
    Guru 20100 points
    Hi H L,

    Thank you for your checking and I'm sorry for my late update.

    We asked them to check the check items you told. But they didn't check those and they programmed FPGA they to control the EVM. As the result, according to the customer report, the EVM is working well by FPGA.

    Thank you very much again and best regards.
    Kazuya Nakai.
  • 0 in reply to Kazuya Nakai59
    Guru 20100 points
    Hi H L,

    I forgot to tell you that this issue is resolved.

    Thank you and best regards,
    Kazuya Nakai.