• Resolved

DS90UB913A-CXEVM: Source for cables for the DS90UB913A and DS90UB914 eval boards

Part Number: DS90UB913A-CXEVM

I ended up thrashing around for the cable to connect the '913 and '914 eval boards. In the interest of saving time && ... helping .. TI improve their User Guide:

cable '913 to '914 Water Blue, FAKRA Jack to FAKRA Jack Cable, 60-inch length, using RG174 Coax cable part number price
pasternack.com Pasternack - 12-in PE38750Z-12 26.06
Pasternack - 24-in PE38750Z-24 26.46
Pasternack - 36-in PE38750Z-36 26.86
Pasternack - 48-in PE38750Z-48 27.26
Pasternack - 60-in PE38750Z-60 27.67

Obviously, prices may change. This is accurate as of may 2018

bandit  Gangwere

505-228-8197

  • In reply to Mike Leister:

    I have a deeper problem.

    I have the 913 and 914 eval boards mounted on a piece of plywood. Cable between them. Both powered at 5v via a power supply.

    I have a USB2ANY to the 913. Unfortunately, the USB2ANY is bricked. I have tried a number of things to try to reload the firmware.  Tried codeLader4, but it does not see the USB, only LPT. Tried the USB2ANY explorer, but it needs proper FW in the USB2ANY. Tried pressing the button && releasing it. Tried the "Gary Pajer" in "Motor Drivers" forum (//531779??) to no avail.

    The firmware loader splash screen is

    It then does the below screen (but not with the text) and says "waiting.." with the "..." as progress.

    It then shows

    I would point out the text is COMPLETELY USELESS AND INCOMPLETE.

    Line #1 does not tell me what to do with the USB cable. Line #2 does not tell me what to connect.

    I have tried the FW download tools I have been able to find. They all agree the FW is wrong. The closest is one thinks the FW version is 255.255.255.255, which is clearly wrong.

    I would post this to another forum, but the few posts for USB2ANY failures are in forums connected with specific products. I AM STUCK.

    bandit  Gangwere

    505-228-8197

  • In reply to bandit gangwere:

    I finally figured it out. You need to go thru the above sequence, get the second screen, unplug the USB cable - the above will then show the USB is disconnected - push the little button, plug the USB back in, release the button, and now the tool can see the USB2ANY and do *some* download. After, run USB2ANY explorer, which will offer to download a better version of FW - let it - it should work.

    PLEASE WRITE A SEQUENCE ON HOW TO RESTORE A BRICKED USB2ANY AND PUT IT ON A FORUM WITH THE TITLE SO PEOPLE CAN FIND IT. THIS IS 5 HOURS OF MY LIFE I WILL NEVER GET BACK.

    AND INCLUDE THIS SEQUENCE WITH THE DOWNLOADS TO THE FW LOAD TOOL AND CORRECT THE DOCUMENT "Instructions for Updating USB2ANY Firmware" IN THE DOWNLOAD "TI USB2ANY FW.zip"

    OY.

    bandit  Gangwere

    505-228-8197

  • In reply to Mike Leister:

    Mike:

    I have a more simple problem now: I cannot get LaunchPad to work. I always get "MainGui.exe has stopped working".
    I have re-installed LaunchPad to the default location C:\Program Files (x86)\Texas Instruments\Analog LaunchPAD v1.57.0010\

    If I run USB2ANY Explorer, it can see the USB2ANY dongle.
    If the USB2ANY explorer is running (the 5/3.3v on or off doesn't seem to matter), LP comes up, reports it cannot see ant boards, and goes into emulation mode.
    If U2A is not running, MainGui.exe fails with the only option to exit.

    I cannot find a log for MainGui.exe (C:\Program Files (x86)\Texas Instruments\Analog LaunchPAD v1.57.0010\MainGui.log is empty).
    I have re-installed ALP - still no joy.
    Next try is a complete reboot, but I am forced into that because of an upgrade by the client. Joy.

    BTW, the U2A FW version is 2.8.2.0
    \\us01fs01p\FS_ASW_MobBackup\S0072312\USB2ANY\Logs
    (this is on a network server a long way off because I installed it using he default values/choices)

    There is a time lag between starting the launch due to the network lag......

    MainGUI API Debug.log:
    2018-06-18 13:57:54.846 Logging enabled.
    2018-06-18 13:57:54.846
    2018-06-18 13:57:54.846 ################################ SESSION START ################################
    2018-06-18 13:57:54.846 Loading C:\Program Files (x86)\Texas Instruments\Analog LaunchPAD v1.57.0010\Drivers\i2c_controllers\usb2any\python\USB2ANY.dll (v2.5.2.0)
    2018-06-18 13:57:55.426
    2018-06-18 13:57:55.426 u2aFindControllers() [703, TI_USB2ANY.cpp]
    2018-06-18 13:57:57.146 Found controller S/N 21AE996F15001800 [689, TI_USB2ANY.cpp]
    2018-06-18 13:57:57.146 Returning value 1 [698, TI_USB2ANY.cpp]
    2018-06-18 13:57:57.146
    2018-06-18 13:57:57.146 u2aFindControllers() [703, TI_USB2ANY.cpp]
    2018-06-18 13:57:57.156 Found controller S/N 21AE996F15001800 [689, TI_USB2ANY.cpp]
    2018-06-18 13:57:57.166 Returning value 1 [698, TI_USB2ANY.cpp]
    2018-06-18 13:57:57.166
    2018-06-18 13:57:57.166 u2aGetSerialNumber(index=0, szSerialNumber=0x04FCAA68) [761, TI_USB2ANY.cpp]
    2018-06-18 13:57:57.166 Returning serial number 21AE996F15001800 [776, TI_USB2ANY.cpp]
    2018-06-18 13:57:57.166 Return code set to 0 [777, TI_USB2ANY.cpp]
    2018-06-18 13:57:57.176 Returning value 0 [781, TI_USB2ANY.cpp]
    2018-06-18 13:57:57.176
    2018-06-18 13:57:57.176 u2aOpen(szSerialNumber='21AE996F15001800') [827, TI_USB2ANY.cpp]
    2018-06-18 13:57:57.186 HIDReceiverThreadProc thread starting... [288, U2A_ApiClass.cpp]
    2018-06-18 13:57:57.296 Logging packets to \\us01fs01p\FS_ASW_MobBackup\S0072312\USB2ANY\Logs\PacketLog.log [107, U2A_ApiClass.cpp]
    2018-06-18 13:57:57.416 Packet logging enabled. [128, U2A_ApiClass.cpp]
    2018-06-18 13:57:57.876 Timeout waiting for response packet [919, U2A_ApiClass.cpp]
    2018-06-18 13:57:57.876 Error: variable 'err' set to -2 (Receive buffer is empty) [924, U2A_ApiClass.cpp]

    Hmm....
    2018-06-18 13:57:57.876 Timeout waiting for response packet [919, U2A_ApiClass.cpp]
    2018-06-18 13:57:57.876 Error: variable 'err' set to -2 (Receive buffer is empty) [924, U2A_ApiClass.cpp]

    I put profiles under C:\Program Files (x86)\Texas Instruments\Analog LaunchPAD v1.57.0010\Profiles\ && the "C:\Program Files\Texas Instruments\Analog LaunchPAD v1.57.0010\Profiles\

    (BTW, the documentation says to put the profiles under "program files" ??? huh ??? Path?? Root dir??? what about "program files (x86)"??
    And now I cannot find the "installing ALP" doc.. Oy.

    I originally installed ALP under c:\alp
    When I ran it && had the same (I assume) failure (the behavior was the same), I was able to get a "c:\alp\MainGUI.exe.log".

    The log:


    Traceback (most recent call last):
    File "C:\Analog LaunchPAD v1.57.0010\Utils.py", line 55, in OnToolClick
    alpHyperlinkHandlers[name]()
    File "MainGUI.py", line 879, in OnLPTClick
    File "C:\Analog LaunchPAD v1.57.0010\LPTGUI.py", line 48, in __init__
    if map & 0x01:
    UnboundLocalError: local variable 'map' referenced before assignment
    Traceback (most recent call last):
    File "C:\Analog LaunchPAD v1.57.0010\Utils.py", line 55, in OnToolClick
    alpHyperlinkHandlers[name]()
    File "MainGUI.py", line 879, in OnLPTClick
    File "C:\Analog LaunchPAD v1.57.0010\LPTGUI.py", line 48, in __init__
    if map & 0x01:
    UnboundLocalError: local variable 'map' referenced before assignment
    Traceback (most recent call last):
    File "MainGUI.py", line 870, in OnExitClick
    File "C:\Analog LaunchPAD v1.57.0010\PyAUI.py", line 2513, in UnInit
    self._frame.RemoveEventHandler(self)
    File "wx\_core.pyc", line 9118, in RemoveEventHandler
    wx._core.PyAssertionError: C++ assertion "wxAssertFailure" failed in ..\..\src\common\wincmn.cpp(1016): where has the event handler gone?
    Traceback (most recent call last):
    File "MainGUI.py", line 870, in OnExitClick
    File "C:\Analog LaunchPAD v1.57.0010\PyAUI.py", line 2513, in UnInit
    self._frame.RemoveEventHandler(self)
    File "wx\_core.pyc", line 9118, in RemoveEventHandler
    wx._core.PyAssertionError: C++ assertion "wxAssertFailure" failed in ..\..\src\common\wincmn.cpp(1016): where has the event handler gone?
    Traceback (most recent call last):
    File "MainGUI.py", line 870, in OnExitClick
    File "C:\Analog LaunchPAD v1.57.0010\PyAUI.py", line 2513, in UnInit
    self._frame.RemoveEventHandler(self)
    File "wx\_core.pyc", line 9118, in RemoveEventHandler
    wx._core.PyAssertionError: C++ assertion "wxAssertFailure" failed in ..\..\src\common\wincmn.cpp(1016): where has the event handler gone?
    Traceback (most recent call last):
    File "MainGUI.py", line 870, in OnExitClick
    File "C:\Analog LaunchPAD v1.57.0010\PyAUI.py", line 2513, in UnInit
    self._frame.RemoveEventHandler(self)
    File "wx\_core.pyc", line 9118, in RemoveEventHandler
    wx._core.PyAssertionError: C++ assertion "wxAssertFailure" failed in ..\..\src\common\wincmn.cpp(1016): where has the event handler gone?



    I think I have heard that song before:

    where has the event handler gone?
    many milliseconds passing..
    where has the event handler gone?
    many milliseconds ago..
    where has the event handler gone?
    To the great bit bucket in the sky everyone...



    Please advise.
    I will keep trying....

    Thanks .. bandit

    bandit  Gangwere

    505-228-8197

  • In reply to bandit gangwere:

    bandit,

    Sorry about the issues with USB2ANY dongle. Thanks for getting the debug log on this issue.

    I think this issue is related to USB2ANY firmware version loaded on your board. I have enclosed here USB2ANY firmware version 2.7. Could you please update USB2ANY dongle to this version of the firmware and let me know if you still face "MainGUI.exe has stopped working" issue. Also, you should be able to run without USB2ANY explorer running (it holds the USB port otherwise and ALP would not be able to see it)

    I see you already figured out updating USB2ANY firmware: Switch S1 is used to put the MCU firmware into bootstrap loader (BSL) mode. The BSL mode is used to load or update the USB2ANY firmware and is entered whenever the board is powered-up while Switch S1 is depressed.

    Thanks,

    Vishy

    USB2ANY_2_7_0_0.txt