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.

EV2400: win11无法识别ev2400

Part Number: EV2400
Other Parts Discussed in Thread: BQSTUDIO

春节放假回来后Battery Management Studio就无法识别到ev2400

  • 您好,请将BQStudio驱动删除再重新安装一下

  • 如何删除呢

  •  只发现在里面有

  • 您好,卸载bqStudio,然后删除c:\ti\BatteryManagementStudio文件夹,然后重新安装

  • 你好问题依旧存在

  • 您好,卸载BQStudio以后重新安装还有问题,建议您换个EV2400

  • 你好,已验证所有硬件ev2400,电脑pc都没有问题,我重装过系统后能正常识别到,但是不知道有安装了什么软件导致Battery Management Studio又无法正常识别到ev2400,以下为Battery Management Studio的log信息,

    !ENTRY org.eclipse.ui.workbench 4 2 2024-03-03 18:11:56.134
    !MESSAGE Problems occurred when invoking code from plug-in: "org.eclipse.ui.workbench".
    !STACK 0
    java.lang.NullPointerException
    at org.eclipse.ui.internal.WorkbenchWindow.hardClose(WorkbenchWindow.java:1967)
    at org.eclipse.ui.internal.WorkbenchWindow.busyClose(WorkbenchWindow.java:1600)
    at org.eclipse.ui.internal.WorkbenchWindow.access$16(WorkbenchWindow.java:1542)
    at org.eclipse.ui.internal.WorkbenchWindow$11.run(WorkbenchWindow.java:1628)
    at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
    at org.eclipse.ui.internal.WorkbenchWindow.close(WorkbenchWindow.java:1625)
    at org.eclipse.ui.internal.Workbench$14.run(Workbench.java:1184)
    at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
    at org.eclipse.ui.internal.Workbench.busyClose(Workbench.java:1171)
    at org.eclipse.ui.internal.Workbench.access$22(Workbench.java:1113)
    at org.eclipse.ui.internal.Workbench$19.run(Workbench.java:1454)
    at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
    at org.eclipse.ui.internal.Workbench.close(Workbench.java:1451)
    at org.eclipse.ui.internal.Workbench.close(Workbench.java:1424)
    at com.ti.evswsdk.ApplicationWorkbenchWindowAdvisor.closeProgram(Unknown Source)
    at com.ti.evswsdk.ApplicationWorkbenchWindowAdvisor.preWindowOpen(Unknown Source)
    at org.eclipse.ui.internal.WorkbenchWindow.fireWindowOpening(WorkbenchWindow.java:1654)
    at org.eclipse.ui.internal.WorkbenchWindow.setup(WorkbenchWindow.java:654)
    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.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:56)
    at org.eclipse.e4.core.internal.di.InjectorImpl.processAnnotated(InjectorImpl.java:898)
    at org.eclipse.e4.core.internal.di.InjectorImpl.inject(InjectorImpl.java:121)
    at org.eclipse.e4.core.internal.di.InjectorImpl.inject(InjectorImpl.java:86)
    at org.eclipse.e4.core.contexts.ContextInjectionFactory.inject(ContextInjectionFactory.java:73)
    at org.eclipse.ui.internal.Workbench.createWorkbenchWindow(Workbench.java:1526)
    at org.eclipse.ui.internal.Workbench.getActiveWorkbenchWindow(Workbench.java:1500)
    at org.eclipse.ui.internal.services.WorkbenchSourceProvider.updateActiveShell(WorkbenchSourceProvider.java:944)
    at org.eclipse.ui.internal.services.WorkbenchSourceProvider.getCurrentState(WorkbenchSourceProvider.java:138)
    at org.eclipse.ui.internal.services.WorkbenchSourceProvider$6.handleEvent(WorkbenchSourceProvider.java:704)
    at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
    at org.eclipse.swt.widgets.Display.filterEvent(Display.java:1266)
    at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1112)
    at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1137)
    at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1122)
    at org.eclipse.swt.widgets.Decorations.WM_ACTIVATE(Decorations.java:1673)
    at org.eclipse.swt.widgets.Shell.WM_ACTIVATE(Shell.java:2193)
    at org.eclipse.swt.widgets.Control.windowProc(Control.java:4673)
    at org.eclipse.swt.widgets.Canvas.windowProc(Canvas.java:339)
    at org.eclipse.swt.widgets.Decorations.windowProc(Decorations.java:1633)
    at org.eclipse.swt.widgets.Shell.windowProc(Shell.java:2117)
    at org.eclipse.swt.widgets.Display.windowProc(Display.java:5050)
    at org.eclipse.swt.internal.win32.OS.BringWindowToTop(Native Method)
    at org.eclipse.swt.widgets.Decorations.bringToTop(Decorations.java:230)
    at org.eclipse.swt.widgets.Shell.open(Shell.java:1244)
    at org.eclipse.e4.ui.workbench.renderers.swt.WBWRenderer.postProcess(WBWRenderer.java:694)
    at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:658)
    at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:746)
    at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.access$0(PartRenderingEngine.java:717)
    at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$2.run(PartRenderingEngine.java:711)
    at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
    at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.createGui(PartRenderingEngine.java:695)
    at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1057)
    at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
    at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1018)
    at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156)
    at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:694)
    at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
    at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:606)
    at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
    at com.ti.evswsdk.Application.start(Unknown Source)
    at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
    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)

  • 您好,正在询问更了解这款芯片的TI工程师, 稍后回复。

  • 您好,您使用什么版本的 bqStudio和什么版本的 EV2400 固件?

  • BQ软件用的1.3.101很多版本都试过,ev2400版本0.32和0.28都使用过,都不行

  • 您好,正在查询,稍后回复。

  • 您好,

    This version of bqStudio is an outdated version, the latest version is 1.3.124 and can be found under BQSTUDIO-TEST

  •  你好已经验证了还是不行,但是没插ev2400居然识别到ev2300,还是有问题

  • 您好,已经在E2E英文论坛发帖,请继续关注

    e2e.ti.com/.../ev2400-bqstudio-can-not-identify-the-ev2400

  • 您好,您是否打开了另一个 bqStudio ?此外,EV2400 是否显示在设备管理器下?

  • 你好就打开了一个bqStudio,EV2400在设备管理下面

  • 您好,已经在E2E英文论坛回复,请继续关注。

  • 你好这个问题能解决吗·

  • 您好,是否可以使用另一台计算机测试 EV2400 以排除对 EV2400 可能造成的损坏?

  • 你好已经测试过了换一台电脑就可以,我这台台式电脑,已经换过CPU,主板,内存条,EV2400也有两个测试结果一样的,所以判断是软件问题

  • 您好,换一台电脑EV2400可以正常使用说明EV2400是好的。如果怀疑是软件的问题建议卸载以后重新安装。如果还是不能使用,建议换一台电脑。

  • 你好两台电脑的差异在,运行bqStudio在任务管理器界面看到连接不上ev2400这台电脑没有运行·TI Communication Manager(32位)