EV2400: EV2400 not working with Windows 10

Erich Studer

Part Number: EV2400
Other Parts Discussed in Thread: BQSTUDIO

I just bought an EV2400 because my EV2300 wasn't working anymore with Windows 10.
Now i just realized that EV2400 isn't working with Windows 10 aswell!
The EV2400 has all lights on and when I try to update the FW is says: "Error: No Free EV2400s Detected...".
I have no unrecognized devices in the device manager. The EV2400 is recognized as a HID.

What I tried:
- Restarting the PC several times
- Disconnect the original USB cable and reconnect
- Tried a different USB cable
- Tried it on a Windows 7 PC => working (FW-update possible and visible in Battery Management Studio)
- Tried it on another Windows 10 PC => not working
- tried all the things that are recommended here: https://e2e.ti.com/support/power-management/f/196/t/781882?tisearch=e2e-sitesearch&keymatch=BQ76930EVM

I also downgraded to v0.20 by using a Windows 7 PC but it didn't change anything: https://e2e.ti.com/cfs-file/__key/communityserver-discussions-components-files/196/3007.EV2400_5F00_Updater_5F00_v0020.zip

Does anybody have a suggestion how to solve this problem? (Using Windows 7 is not an option)
What else could i try?
Is there another box to communicate with TI gas gauges that you recommend?
We are a bit concerned about that because Windows 7 will only be supported until 14. January 2020.
So we would be really happy if it was possible to make it work with Windows 10.

Regards
Erich Studer

over 5 years ago

0 Matt Sunna over 5 years ago

TI__Guru* 80843 points

Hi Erich,

Did you upgrade the firmware to v0.27 using the Windows 7 PC and then try the EV2400 on a Windows 10 PC with the new firmware? v0.28 of the firmware addresses an issue where the device is sometimes not detected.

Regards,

Matt

0 Erich Studer over 5 years ago in reply to Matt Sunna

Prodigy 115 points

Hi Matt

Thanks for your hint.

No I didn't try that, but I would like to give it a try.

Unfortunately I don't know where to get v0.27 from.

The product page of the EV2400 only llists v0.28 and v0.18.

Any ideas where to get v0.27 from?

Regards

Erich

0 Matt Sunna over 5 years ago in reply to Erich Studer

TI__Guru* 80843 points

Erich,

Sorry, that was a typo. I meant v0.28 - that is the one with the fix to the USB detection issue. There was no release of v0.27

0 Erich Studer over 5 years ago in reply to Matt Sunna

Prodigy 115 points

Matt,

Then yes, I have upgraded to v0.28.

All I have explained so far is with v0.28.

0 Erich Studer over 5 years ago in reply to Erich Studer

Prodigy 115 points

I have an update:

I have found 2 Windows 10 PCs where the EV2400 with v0.28 is finally recognized!

Also the Battery Management Studio finds the EV2400.

Looks like there is something wrong with the two Windows 10 PCs that do not recognize the EV2400.

I compared the windows build number and they are identical. So it seems not to depend on that.

So for the moment it is just luck whether it works on a Windows 10 PC or not.

Again I've checke whether the EV2400 is found as a device by the Windows itself "Systemsteuerung\Hardware und Sound\Geräte und Drucker". => It looks the same on all PCs that I've tried (working or not). So the EV2400 is found by Windows 10 itself.

What else could I try? Any Hints?

Is there any possibility to have more verbosity in the "EV2400_Updater_v0028.exe" to further investigate the problem?

On what system or software components does the updater and the Battery Management Studio rely to find the EV2400?

Thank you in advance

Erich

0 WM5295 over 5 years ago in reply to Erich Studer

TI__Guru 54715 points

Hi Erich,

Thanks for looking on e2e for a solution.

The EV2400 uses HID drivers.

There is not a verbose option known.

0 Erich Studer over 5 years ago in reply to WM5295

Prodigy 115 points

Good Morning

I received an E-Mail asking me whether I believe the issue has been solved by the answer above.

I must say: NO.

We still have Windows 10 PCs where it is just not working and we don't know why.

So it's just luck whether it works or not.

I would be very happy if you could give more assistance to find the problem.

0 WM5295 over 5 years ago in reply to Erich Studer

TI__Guru 54715 points

Hi Erich,

I agree, I can't explain why one Windows 10 installation will work and another will not. The hardware (EV2400) is the same, the drivers are from the Windows system.

0 Erich Studer over 5 years ago in reply to WM5295

Prodigy 115 points

Dear Ti Supporters

For me it looks like I have the same or at least a similar problem like other users aswell:

https://e2e.ti.com/support/power-management/f/196/t/778671

I'm sorry but I also must admit that this situation is not satisfying for me.

I feel left alone with this problem.

Nobody is perfect and problems occure from time to time in most systems.

I am willing to further investigate the problem but I need your assistance!

As far as I understand the problem the Firmware-Updader and also the Battery-Management-Studio have in my case problems to connect to the EV2400.

Wouldn't it be possible that you give me a reduced open-source part of the software that maybe only tries to find or connect the EV2400?

Depending on the technology you use that could give me the ability the debug the problem. (Depending my time)

We all could benefit from that.

Regards and let's solve that problem together!

Erich Studer

0 Bryce Leach over 5 years ago in reply to Erich Studer

TI__Prodigy 30 points

Hi Erich,

The EV2400 presents itself to a system as a HID device so there isn't a specific TI driver required for the EV2400 to work. There are no open source software components to offer to assist in debug. My suggestion is to focus on enumeration first.

Is the EV2400 device enumerating as a USB device? On my (working) system, it shows up as:

The other way I check is to use Start -> Run and type devmgmt.msc. Look for a HID-compliant vendor-defined device. Mine looks like:

With the EV2400 enumerated, my bqStudio connects to the EV2400, collects the firmware version and displays:

If the EV2400 is successfully enumerating, then the debug focus needs to be elsewhere.

0 Erich Studer over 5 years ago in reply to Bryce Leach

Prodigy 115 points

Hello Bryce,

I have checked and a have exactly the same Devie Information images (except mine are in german).

But when I start Battery Management Studio I have the following Problems:

When I try to start battery management studio version 1.3.93 then I get the following error log. How could I resolve this error?

I didn't find the package to download.

1571056931682.log

!SESSION 2019-10-14 14:42:11.462 -----------------------------------------------
eclipse.buildId=unknown
java.version=1.8.0_74
java.vendor=Oracle Corporation
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=de_CH
Framework arguments:  -clearPersistedState -persistState false
Command-line arguments:  -os win32 -ws win32 -arch x86 -clearPersistedState -persistState false

!ENTRY com.ti.evswsdk 4 0 2019-10-14 14:42:11.992
!MESSAGE FrameworkEvent ERROR
!STACK 0
org.osgi.framework.BundleException: Could not resolve module: com.ti.evswsdk [190]
  Unresolved requirement: Import-Package: com.ti.evswsdk.dashboard
    -> Export-Package: com.ti.evswsdk.dashboard; bundle-symbolic-name="com.ti.evswsdk.dashboard"; bundle-version="1.2.0.201909131701"; version="0.0.0"
       com.ti.evswsdk.dashboard [218]
         Unresolved requirement: Import-Package: com.ti.evswsdk.gpcpackager.views

	at org.eclipse.osgi.container.Module.start(Module.java:434)
	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1582)
	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1561)
	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1533)
	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1476)
	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1)
	at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
	at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340)

!ENTRY com.ti.evswsdk.authentication 4 0 2019-10-14 14:42:12.000
!MESSAGE FrameworkEvent ERROR
!STACK 0
org.osgi.framework.BundleException: Could not resolve module: com.ti.evswsdk.authentication [193]
  Unresolved requirement: Import-Package: com.ti.evswsdk.dashboard
    -> Export-Package: com.ti.evswsdk.dashboard; bundle-symbolic-name="com.ti.evswsdk.dashboard"; bundle-version="1.2.0.201909131701"; version="0.0.0"
       com.ti.evswsdk.dashboard [218]
         Unresolved requirement: Import-Package: com.ti.evswsdk.gpcpackager.views

	at org.eclipse.osgi.container.Module.start(Module.java:434)
	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1582)
	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1561)
	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1533)
	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1476)
	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1)
	at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
	at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340)

!ENTRY com.ti.evswsdk.calbq769x2 4 0 2019-10-14 14:42:12.004
!MESSAGE FrameworkEvent ERROR
!STACK 0
org.osgi.framework.BundleException: Could not resolve module: com.ti.evswsdk.calbq769x2 [199]
  Unresolved requirement: Import-Package: com.ti.evswsdk.programming769x2
    -> Export-Package: com.ti.evswsdk.programming769x2; bundle-symbolic-name="com.ti.evswsdk.programming769x2"; bundle-version="1.0.0.201909131701"; version="0.0.0"; uses:="org.osgi.framework,  org.eclipse.swt.graphics,  org.eclipse.jface.resource,  org.eclipse.swt.widgets,  org.eclipse.jface.dialogs,  org.eclipse.ui.plugin"
       com.ti.evswsdk.programming769x2 [252]
         Unresolved requirement: Import-Package: com.ti.evswsdk.dashboard
           -> Export-Package: com.ti.evswsdk.dashboard; bundle-symbolic-name="com.ti.evswsdk.dashboard"; bundle-version="1.2.0.201909131701"; version="0.0.0"
              com.ti.evswsdk.dashboard [218]
                Unresolved requirement: Import-Package: com.ti.evswsdk.gpcpackager.views

	at org.eclipse.osgi.container.Module.start(Module.java:434)
	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1582)
	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1561)
	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1533)
	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1476)
	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1)
	at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
	at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340)

!ENTRY com.ti.evswsdk.cmdsequence 4 0 2019-10-14 14:42:12.008
!MESSAGE FrameworkEvent ERROR
!STACK 0
org.osgi.framework.BundleException: Could not resolve module: com.ti.evswsdk.cmdsequence [215]
  Unresolved requirement: Import-Package: com.ti.evswsdk.dashboard
    -> Export-Package: com.ti.evswsdk.dashboard; bundle-symbolic-name="com.ti.evswsdk.dashboard"; bundle-version="1.2.0.201909131701"; version="0.0.0"
       com.ti.evswsdk.dashboard [218]
         Unresolved requirement: Import-Package: com.ti.evswsdk.gpcpackager.views

	at org.eclipse.osgi.container.Module.start(Module.java:434)
	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1582)
	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1561)
	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1533)
	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1476)
	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1)
	at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
	at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340)

!ENTRY com.ti.evswsdk.dashboard 4 0 2019-10-14 14:42:12.012
!MESSAGE FrameworkEvent ERROR
!STACK 0
org.osgi.framework.BundleException: Could not resolve module: com.ti.evswsdk.dashboard [218]
  Unresolved requirement: Import-Package: com.ti.evswsdk.gpcpackager.views

	at org.eclipse.osgi.container.Module.start(Module.java:434)
	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1582)
	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1561)
	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1533)
	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1476)
	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1)
	at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
	at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340)

!ENTRY com.ti.evswsdk.dataflashview 4 0 2019-10-14 14:42:12.016
!MESSAGE FrameworkEvent ERROR
!STACK 0
org.osgi.framework.BundleException: Could not resolve module: com.ti.evswsdk.dataflashview [219]
  Unresolved requirement: Import-Package: com.ti.evswsdk.fsexport
    -> Export-Package: com.ti.evswsdk.fsexport; bundle-symbolic-name="com.ti.evswsdk.fsexport"; bundle-version="1.0.0.201909131701"; version="0.0.0"
       com.ti.evswsdk.fsexport [227]
         Unresolved requirement: Import-Package: com.ti.evswsdk.dashboard
           -> Export-Package: com.ti.evswsdk.dashboard; bundle-symbolic-name="com.ti.evswsdk.dashboard"; bundle-version="1.2.0.201909131701"; version="0.0.0"
              com.ti.evswsdk.dashboard [218]
                Unresolved requirement: Import-Package: com.ti.evswsdk.gpcpackager.views

	at org.eclipse.osgi.container.Module.start(Module.java:434)
	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1582)
	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1561)
	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1533)
	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1476)
	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1)
	at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
	at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340)

!ENTRY com.ti.evswsdk.fieldprogrammer 4 0 2019-10-14 14:42:12.019
!MESSAGE FrameworkEvent ERROR
!STACK 0
org.osgi.framework.BundleException: Could not resolve module: com.ti.evswsdk.fieldprogrammer [225]
  Unresolved requirement: Import-Package: com.ti.evswsdk.dashboard
    -> Export-Package: com.ti.evswsdk.dashboard; bundle-symbolic-name="com.ti.evswsdk.dashboard"; bundle-version="1.2.0.201909131701"; version="0.0.0"
       com.ti.evswsdk.dashboard [218]
         Unresolved requirement: Import-Package: com.ti.evswsdk.gpcpackager.views

	at org.eclipse.osgi.container.Module.start(Module.java:434)
	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1582)
	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1561)
	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1533)
	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1476)
	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1)
	at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
	at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340)

!ENTRY com.ti.evswsdk.firmware 4 0 2019-10-14 14:42:12.023
!MESSAGE FrameworkEvent ERROR
!STACK 0
org.osgi.framework.BundleException: Could not resolve module: com.ti.evswsdk.firmware [226]
  Unresolved requirement: Import-Package: com.ti.evswsdk.dashboard
    -> Export-Package: com.ti.evswsdk.dashboard; bundle-symbolic-name="com.ti.evswsdk.dashboard"; bundle-version="1.2.0.201909131701"; version="0.0.0"
       com.ti.evswsdk.dashboard [218]
         Unresolved requirement: Import-Package: com.ti.evswsdk.gpcpackager.views

	at org.eclipse.osgi.container.Module.start(Module.java:434)
	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1582)
	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1561)
	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1533)
	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1476)
	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1)
	at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
	at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340)

!ENTRY com.ti.evswsdk.fsexport 4 0 2019-10-14 14:42:12.026
!MESSAGE FrameworkEvent ERROR
!STACK 0
org.osgi.framework.BundleException: Could not resolve module: com.ti.evswsdk.fsexport [227]
  Unresolved requirement: Import-Package: com.ti.evswsdk.dashboard
    -> Export-Package: com.ti.evswsdk.dashboard; bundle-symbolic-name="com.ti.evswsdk.dashboard"; bundle-version="1.2.0.201909131701"; version="0.0.0"
       com.ti.evswsdk.dashboard [218]
         Unresolved requirement: Import-Package: com.ti.evswsdk.gpcpackager.views

	at org.eclipse.osgi.container.Module.start(Module.java:434)
	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1582)
	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1561)
	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1533)
	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1476)
	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1)
	at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
	at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340)

!ENTRY com.ti.evswsdk.gdk 4 0 2019-10-14 14:42:12.030
!MESSAGE FrameworkEvent ERROR
!STACK 0
org.osgi.framework.BundleException: Could not resolve module: com.ti.evswsdk.gdk [229]
  Unresolved requirement: Import-Package: com.ti.evswsdk.dataflashview
    -> Export-Package: com.ti.evswsdk.dataflashview; bundle-symbolic-name="com.ti.evswsdk.dataflashview"; bundle-version="1.3.0.201909131701"; version="0.0.0"
       com.ti.evswsdk.dataflashview [219]
         Unresolved requirement: Import-Package: com.ti.evswsdk.fsexport
           -> Export-Package: com.ti.evswsdk.fsexport; bundle-symbolic-name="com.ti.evswsdk.fsexport"; bundle-version="1.0.0.201909131701"; version="0.0.0"
              com.ti.evswsdk.fsexport [227]
                Unresolved requirement: Import-Package: com.ti.evswsdk.dashboard
                  -> Export-Package: com.ti.evswsdk.dashboard; bundle-symbolic-name="com.ti.evswsdk.dashboard"; bundle-version="1.2.0.201909131701"; version="0.0.0"
                     com.ti.evswsdk.dashboard [218]
                       Unresolved requirement: Import-Package: com.ti.evswsdk.gpcpackager.views

	at org.eclipse.osgi.container.Module.start(Module.java:434)
	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1582)
	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1561)
	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1533)
	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1476)
	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1)
	at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
	at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340)

!ENTRY com.ti.evswsdk.goldenizing 4 0 2019-10-14 14:42:12.034
!MESSAGE FrameworkEvent ERROR
!STACK 0
org.osgi.framework.BundleException: Could not resolve module: com.ti.evswsdk.goldenizing [232]
  Unresolved requirement: Import-Package: com.ti.evswsdk.dashboard
    -> Export-Package: com.ti.evswsdk.dashboard; bundle-symbolic-name="com.ti.evswsdk.dashboard"; bundle-version="1.2.0.201909131701"; version="0.0.0"
       com.ti.evswsdk.dashboard [218]
         Unresolved requirement: Import-Package: com.ti.evswsdk.gpcpackager.views

	at org.eclipse.osgi.container.Module.start(Module.java:434)
	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1582)
	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1561)
	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1533)
	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1476)
	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1)
	at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
	at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340)

!ENTRY com.ti.evswsdk.programming769x2 4 0 2019-10-14 14:42:12.038
!MESSAGE FrameworkEvent ERROR
!STACK 0
org.osgi.framework.BundleException: Could not resolve module: com.ti.evswsdk.programming769x2 [252]
  Unresolved requirement: Import-Package: com.ti.evswsdk.dashboard
    -> Export-Package: com.ti.evswsdk.dashboard; bundle-symbolic-name="com.ti.evswsdk.dashboard"; bundle-version="1.2.0.201909131701"; version="0.0.0"
       com.ti.evswsdk.dashboard [218]
         Unresolved requirement: Import-Package: com.ti.evswsdk.gpcpackager.views

	at org.eclipse.osgi.container.Module.start(Module.java:434)
	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1582)
	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1561)
	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1533)
	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1476)
	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1)
	at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
	at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340)

!ENTRY com.ti.evswsdk.dataflashview 2 0 2019-10-14 14:42:12.216
!MESSAGE Could not resolve module: com.ti.evswsdk.dataflashview [219]
  Unresolved requirement: Import-Package: com.ti.evswsdk.fsexport
    -> Export-Package: com.ti.evswsdk.fsexport; bundle-symbolic-name="com.ti.evswsdk.fsexport"; bundle-version="1.0.0.201909131701"; version="0.0.0"
       com.ti.evswsdk.fsexport [227]
         Unresolved requirement: Import-Package: com.ti.evswsdk.dashboard
           -> Export-Package: com.ti.evswsdk.dashboard; bundle-symbolic-name="com.ti.evswsdk.dashboard"; bundle-version="1.2.0.201909131701"; version="0.0.0"
              com.ti.evswsdk.dashboard [218]
                Unresolved requirement: Import-Package: com.ti.evswsdk.gpcpackager.views


!ENTRY com.ti.evswsdk.fsexport 2 0 2019-10-14 14:42:12.219
!MESSAGE Could not resolve module: com.ti.evswsdk.fsexport [227]
  Unresolved requirement: Import-Package: com.ti.evswsdk.dashboard
    -> Export-Package: com.ti.evswsdk.dashboard; bundle-symbolic-name="com.ti.evswsdk.dashboard"; bundle-version="1.2.0.201909131701"; version="0.0.0"
       com.ti.evswsdk.dashboard [218]
         Unresolved requirement: Import-Package: com.ti.evswsdk.gpcpackager.views


!ENTRY com.ti.evswsdk.gdk 2 0 2019-10-14 14:42:12.223
!MESSAGE Could not resolve module: com.ti.evswsdk.gdk [229]
  Unresolved requirement: Import-Package: com.ti.evswsdk.dataflashview
    -> Export-Package: com.ti.evswsdk.dataflashview; bundle-symbolic-name="com.ti.evswsdk.dataflashview"; bundle-version="1.3.0.201909131701"; version="0.0.0"
       com.ti.evswsdk.dataflashview [219]
         Unresolved requirement: Import-Package: com.ti.evswsdk.fsexport
           -> Export-Package: com.ti.evswsdk.fsexport; bundle-symbolic-name="com.ti.evswsdk.fsexport"; bundle-version="1.0.0.201909131701"; version="0.0.0"
              com.ti.evswsdk.fsexport [227]
                Unresolved requirement: Import-Package: com.ti.evswsdk.dashboard
                  -> Export-Package: com.ti.evswsdk.dashboard; bundle-symbolic-name="com.ti.evswsdk.dashboard"; bundle-version="1.2.0.201909131701"; version="0.0.0"
                     com.ti.evswsdk.dashboard [218]
                       Unresolved requirement: Import-Package: com.ti.evswsdk.gpcpackager.views


!ENTRY com.ti.evswsdk.goldenizing 2 0 2019-10-14 14:42:12.227
!MESSAGE Could not resolve module: com.ti.evswsdk.goldenizing [232]
  Unresolved requirement: Import-Package: com.ti.evswsdk.dashboard
    -> Export-Package: com.ti.evswsdk.dashboard; bundle-symbolic-name="com.ti.evswsdk.dashboard"; bundle-version="1.2.0.201909131701"; version="0.0.0"
       com.ti.evswsdk.dashboard [218]
         Unresolved requirement: Import-Package: com.ti.evswsdk.gpcpackager.views


!ENTRY com.ti.evswsdk.dashboard 2 0 2019-10-14 14:42:12.229
!MESSAGE Could not resolve module: com.ti.evswsdk.dashboard [218]
  Unresolved requirement: Import-Package: com.ti.evswsdk.gpcpackager.views


!ENTRY com.ti.evswsdk.authentication 2 0 2019-10-14 14:42:12.233
!MESSAGE Could not resolve module: com.ti.evswsdk.authentication [193]
  Unresolved requirement: Import-Package: com.ti.evswsdk.dashboard
    -> Export-Package: com.ti.evswsdk.dashboard; bundle-symbolic-name="com.ti.evswsdk.dashboard"; bundle-version="1.2.0.201909131701"; version="0.0.0"
       com.ti.evswsdk.dashboard [218]
         Unresolved requirement: Import-Package: com.ti.evswsdk.gpcpackager.views


!ENTRY com.ti.evswsdk.calbq769x2 2 0 2019-10-14 14:42:12.236
!MESSAGE Could not resolve module: com.ti.evswsdk.calbq769x2 [199]
  Unresolved requirement: Import-Package: com.ti.evswsdk.programming769x2
    -> Export-Package: com.ti.evswsdk.programming769x2; bundle-symbolic-name="com.ti.evswsdk.programming769x2"; bundle-version="1.0.0.201909131701"; version="0.0.0"; uses:="org.osgi.framework,  org.eclipse.swt.graphics,  org.eclipse.jface.resource,  org.eclipse.swt.widgets,  org.eclipse.jface.dialogs,  org.eclipse.ui.plugin"
       com.ti.evswsdk.programming769x2 [252]
         Unresolved requirement: Import-Package: com.ti.evswsdk.dashboard
           -> Export-Package: com.ti.evswsdk.dashboard; bundle-symbolic-name="com.ti.evswsdk.dashboard"; bundle-version="1.2.0.201909131701"; version="0.0.0"
              com.ti.evswsdk.dashboard [218]
                Unresolved requirement: Import-Package: com.ti.evswsdk.gpcpackager.views


!ENTRY com.ti.evswsdk.cmdsequence 2 0 2019-10-14 14:42:12.240
!MESSAGE Could not resolve module: com.ti.evswsdk.cmdsequence [215]
  Unresolved requirement: Import-Package: com.ti.evswsdk.dashboard
    -> Export-Package: com.ti.evswsdk.dashboard; bundle-symbolic-name="com.ti.evswsdk.dashboard"; bundle-version="1.2.0.201909131701"; version="0.0.0"
       com.ti.evswsdk.dashboard [218]
         Unresolved requirement: Import-Package: com.ti.evswsdk.gpcpackager.views


!ENTRY com.ti.evswsdk.programming769x2 2 0 2019-10-14 14:42:12.243
!MESSAGE Could not resolve module: com.ti.evswsdk.programming769x2 [252]
  Unresolved requirement: Import-Package: com.ti.evswsdk.dashboard
    -> Export-Package: com.ti.evswsdk.dashboard; bundle-symbolic-name="com.ti.evswsdk.dashboard"; bundle-version="1.2.0.201909131701"; version="0.0.0"
       com.ti.evswsdk.dashboard [218]
         Unresolved requirement: Import-Package: com.ti.evswsdk.gpcpackager.views


!ENTRY com.ti.evswsdk.firmware 2 0 2019-10-14 14:42:12.246
!MESSAGE Could not resolve module: com.ti.evswsdk.firmware [226]
  Unresolved requirement: Import-Package: com.ti.evswsdk.dashboard
    -> Export-Package: com.ti.evswsdk.dashboard; bundle-symbolic-name="com.ti.evswsdk.dashboard"; bundle-version="1.2.0.201909131701"; version="0.0.0"
       com.ti.evswsdk.dashboard [218]
         Unresolved requirement: Import-Package: com.ti.evswsdk.gpcpackager.views


!ENTRY com.ti.evswsdk 2 0 2019-10-14 14:42:12.250
!MESSAGE Could not resolve module: com.ti.evswsdk [190]
  Unresolved requirement: Import-Package: com.ti.evswsdk.dashboard
    -> Export-Package: com.ti.evswsdk.dashboard; bundle-symbolic-name="com.ti.evswsdk.dashboard"; bundle-version="1.2.0.201909131701"; version="0.0.0"
       com.ti.evswsdk.dashboard [218]
         Unresolved requirement: Import-Package: com.ti.evswsdk.gpcpackager.views


!ENTRY com.ti.evswsdk.fieldprogrammer 2 0 2019-10-14 14:42:12.253
!MESSAGE Could not resolve module: com.ti.evswsdk.fieldprogrammer [225]
  Unresolved requirement: Import-Package: com.ti.evswsdk.dashboard
    -> Export-Package: com.ti.evswsdk.dashboard; bundle-symbolic-name="com.ti.evswsdk.dashboard"; bundle-version="1.2.0.201909131701"; version="0.0.0"
       com.ti.evswsdk.dashboard [218]
         Unresolved requirement: Import-Package: com.ti.evswsdk.gpcpackager.views


!ENTRY org.eclipse.osgi 4 0 2019-10-14 14:42:12.264
!MESSAGE Application error
!STACK 1
java.lang.RuntimeException: Application "com.ti.evswsdk.evswsdk" could not be found in the registry. The applications available are: org.eclipse.e4.ui.workbench.swt.E4Application, org.eclipse.e4.ui.workbench.swt.GenTopic, org.eclipse.equinox.app.error, org.eclipse.help.base.infocenterApplication, org.eclipse.help.base.helpApplication, org.eclipse.help.base.indexTool.
	at org.eclipse.equinox.internal.app.EclipseAppContainer.startDefaultApp(EclipseAppContainer.java:248)
	at org.eclipse.equinox.internal.app.MainApplicationLauncher.run(MainApplicationLauncher.java:29)
	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:380)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
	at java.lang.reflect.Method.invoke(Unknown Source)
	at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:669)
	at org.eclipse.equinox.launcher.Main.basicRun(Main.java:608)
	at org.eclipse.equinox.launcher.Main.run(Main.java:1515)

When I start battery management studio version 1.3.86 then I get the following image (allthough the ev2400 is connected and recognized as on your system):

Any ideas?

Regards

Erich Studer

0 Erich Studer over 5 years ago in reply to Erich Studer

Prodigy 115 points

Looks like the upload of the screen shot of version 1.3.86 didnt work. So next try:

0 Erich Studer over 5 years ago in reply to Erich Studer

Prodigy 115 points

Update:

I got 1.3.93 to work. I had to uninstall the prior version and ADDITIONALLY delete all the remaining folders in C:\ti. The installing version 1.3.93

But the EV2400 is still not recognized. I have the same problem as with version 1.3.86:

The EV2400 is still greyed out in the battery management studio allthough recognized by the windows.

Any ideas?

Note: Version 1.3.93 is probably mistakely named 1.3.92 here http://www.ti.com/tool/BQSTUDIO

Regards

Erich

0 WM5295 over 5 years ago in reply to Erich Studer

TI__Guru 54715 points

Hi Erich,

I have sent you a friend request to try to get connected with someone who can help with windows.

Other readers please look for updates in the future.

Because of the holidays, TI E2E™ design support forum responses will be delayed from Dec. 25 through Jan. 2. Thank you for your patience.

Power management

Power management forum

EV2400: EV2400 not working with Windows 10