• State Resolved
  • Locked Locked
  • Replies 17 replies
  • Subscribers 49 subscribers
  • Views 763 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.

INA239: EVM/SCB Connect Fail

Steve Mauch
Prodigy 10 points
Part Number: INA239

The system routed "INA239" to the Amplifiers forum.  Since it's actually a power (current/voltage) monitoring sensor, apologies if that's not correct forum. 

The TI items are:

     Sensor Control Board SENS077
     Evaluation Module SENS064-002, INA239EVM

I am unable to get the link working between SCB and EVM. Hangup appears to be the firmware update.

Drivers were downloaded from link in manual: www.ti.com/.../sbac253. Downloads sbac253a.zip.

The PC OS is Win 10 Pro 22H2 (64 bit). The GUI & browsers tried are:
     dev.ti.com/.../
     Firefox 110.0 (64-bit)
     Chrome Version 110.0.5481.104 (Official Build) (64-bit)

Have tried both USB ports on laptop, using USB cable supplied w/ evaluation kit.

TIA Cloud Agent (tiacloudagent_2) and the respective browser extensions installed through the GUI prompts on 1st access (only installed Cloud Agent once).

The 2 green lights on SCB and power light on EVM come on when plugged in to USB port. Driver creates COM 4 115200 port.

Then, along with "Firmware Update needed" popup, black box appears above the bottom GUI status bar w/ message:

     Connected to SCB Controller, but failed to connect to SCB w/ INA239EVM, FW: v0.0.1.0 on DEFAULT

Have been able to get the Program Device menu item active. Clicking Program Device shows a Firmware Updating message, shows the circling-dot chaser, the green and red lights flanking the main chip on SCB flash once, then GUI says Flash failed. The GUI also loses contact with the SCB, although its power light is still lit.

I have also been able to get the green light to go off on the SCB by shorting the DFU test points + press reset. However, trying to update after that has same fail results.

The manual also mentions “Send the command 'bsl' on the SCB's USB Serial (COM) port.”. The GUI Scripting Window didn’t produce anything, so I tried TeraTerm on the COM port. I couldn’t get it into an interactive command mode, so was unable to try that.


The GUI log file of an attempt is attached.

Thanks

     Steve


eventlog.csv

  • 0
    TI__Mastermind 30540 points

    Hello Steve,

    Today is a holiday.  We will have the expert on this look at this tomorrow.  Thanks for your patience.  

    Regards,

    Javier

  • 0
    TI__Mastermind 23900 points

    Hello Steve,

    Thank you for using the TI forum. If a firmware update fails for any reason, then the MCU will need to be power cycled before it will work again. Can you please try the following:

    1. Before launching the GUI, plug in the SCB (with EVM connected) and enter DFU mode with the test points (ensure the LEDs stay off).
    2. Then launch the GUI and close the README.md popup.
      1. You should see a box that says "No SCB controller detected". Close this box.
      2. The homepage should say "DEVICE DISCONNECTED" and have a red icon.
    3. Go to File -> Program Device...

    This should update the firmware successfully. If it does not work then please try it in Chrome to see if that works. If you are still unable to update after this, let me know.

    Regards,

    Mitch

  • 0 in reply to Mitch M
    Prodigy 10 points

    Green LED originally on at connection is off after shorting DFU + reset.  After 2 + 2a + 2b, Program Device... is grayed out.  D5 SCB LED is green, EVM power LED is lit. 

    A Generic Bulk USB device is shown in Device manager, and a COM4 port appears when the SCB/EVM is initially connected. The driver details say it's a Microsoft driver.  I did not try re-installing a TI driver because I could not identify which one to use based on previous instructions.   

  • 0 in reply to Steve Mauch
    Prodigy 10 points

    Reviewed Device manger more closely.  Found the Device ID under "Parent Device"..  Updated to driver for USB\VID_1CBE&PID_00AB&MI_01.

    Dev Mgr now shows TI driver for a bulk device.

    Shorted DFU points + reset, in DFU mode (light off).  After 2 + 2a + 2b + 2c, Program Device... still grayed out. 

    Looking back at Device Manager, it now shows an item under Other Devcies:  Tiva Device Firmware Update.   

    Next step?

  • 0 in reply to Steve Mauch
    Prodigy 10 points

    Noticed there was a driver in previous info for Tiva DFU, so know need to load "boot_usb.inf".  However, when doing Update Driver & manually picking driver, system asks for type of device.  

    What is correct type of device for Tiva DFU?

  • 0 in reply to Steve Mauch
    TI__Mastermind 23900 points

    Hey Steve,

    What version of windows are you on? If you are on windows 10 or above, can you try using the default windows driver instead? (so that when in DFU mode you see "Stellaris Device Firmware Upgrade"

    Regards,

    Mitch

  • 0 in reply to Mitch M
    Prodigy 10 points

    Per original post, Win 10 Pro 22H2 (64 bit).  

    I have NOT completed the attempt using Tiva DFU, pending question regarding type of that device..  


    Confirm you now want me to NOT use the Tiva DFU, and try to get it to use Stellaris?  If so, will work to figure out how to roll back to Win 10 default driver.

    When I do roll it back, question will still remain what type of device do I tell Windows for the Stellaris DFU?

  • 0 in reply to Steve Mauch
    TI__Mastermind 23900 points

    Oh, sorry, I missed the windows version. Yes, Tiva should also work, I was just thinking you may want to try Stellaris if Tiva was not working.

  • 0 in reply to Mitch M
    Prodigy 10 points

    So when asked what is device type for Tiva DFU during the driver install for that, what's my best/correct choice?

  • 0 in reply to Steve Mauch
    TI__Mastermind 23900 points

    What options is it giving you?

  • 0 in reply to Mitch M
    TI__Mastermind 23900 points

    Oh, I may have got a couple things backwards in the comments above. It should say Stellaris after you update per the FAQ above. Here is what I recommend:

    First, put the device in DFU mode. I believe you will see the Tiva device at your stage in the device manager.

    Then update the driver per the FAQ instructions by associating it with the "boot_usb.inf" file from the driver (if you do the DFU mode driver this way, you shouldn't have to manually do the other two drivers). When you are done with this, it should say Stellaris instead of Tiva

    Then, go to the GUI and update the firmware. 

    Regards,

    Mitch

  • 0 in reply to Mitch M
    Prodigy 10 points

    The DFU is unknown device type in manager.  What type of device is the DFU to pick in driver update?

    I'm given the entire menu of device types, alphabetcal from "61883 devices" thru  "XBox Peripherals".

  • 0 in reply to Steve Mauch
    TI__Mastermind 23900 points

    oh, I see what you are saying now. I don't believe you should be picking any of those. The driver should be manually associated with the boot_usb.inf file (while in DFU mode), as shown in the instructions for the FAQ that Javier posted (e2e.ti.com/.../faq-how-do-i-resolve-pamb-evm-connectivity-and-or-driver-installation-issues).

  • 0 in reply to Mitch M
    TI__Mastermind 23900 points

    If it makes you select anyway, are there options for tiva/stellaris device firmware update?

  • 0 in reply to Mitch M
    Prodigy 10 points

    Success!  The key was ignoring the type of device input form and installing the "boot_usb.inf" driver while in DFU mode.  It identified as TivaWare DFU once installed (not Stellaris), but it worked.  Now seeing INA_239 as it should.

    First time have had to do a 2-phase manual driver install, with no guidance in documentation.  Thanks for patience & the assist!   

  • 0 in reply to Steve Mauch
    TI__Mastermind 23900 points

    Glad it worked!