BQ40Z50: Programming in mass production

Stephanie Sahm

Part Number: BQ40Z50
Other Parts Discussed in Thread: BQSTUDIO

Hello,

i already recognized that many other developers have the same problem.

We want to program the BQ40Z50 (for example) with our own SW Tool because transfer the srec in mass production with Battery Management Studio is not convenient.

I did not find a clear documentation to transfer a golden image (srec file) to the bq with own software tools. There are still many questions open.

I have learned that address: 0x4000-0x5FFF is the content of the DF. We can write these bytes with MAC access. But the problem is that we can not verify that the write process was successful because there are some bytes which can not be overwritten.
Question 1: Is there a list with all bytes in DF which cannot be overwritten? Our idea is to write the complete DF and then read the complete DF and compare the bytes.

Question 2: Where can I find a documentation to update the firmware with a srec file (from address 0x100000) and SM bus?

Question 3: What is the content of the srec from address 0x140000? I have learned that I can find there for example the password for unseal und full access. Are there any other data, that we have to transfer during production?

Thanks in advance

Stephanie

over 4 years ago

0 Andy Liu (BMS) over 4 years ago

TI__Guru 52115 points

I would suggest you create a FlashStream (*.dt.fs or *.bq.fs) file in the bqStudio and then you can use your host to program a FlashStream file to bq40z50 devices.

It is a new feature and available in this test build below.

https://www.ti.com/tool/download/BQSTUDIO-TEST

0 Stephanie Sahm over 4 years ago in reply to Andy Liu (BMS)

Prodigy 235 points

Hi,

Thanks for your reply. I cannot run the latest version (1.3.101.1) of battery management studio (see attached log File). I have installed BQSTUDIO-TEST_1.3.100.1 instead.

Is there any documentation available about the content and structure of the df.fs File and the bq.fs file. What is the difference between these both files?

Best regards

Steffi

1594725101004.log

!SESSION 2020-07-14 13:11:40.737 -----------------------------------------------
eclipse.buildId=unknown
java.version=1.8.0_74
java.vendor=Oracle Corporation
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=de_DE
Framework arguments:  -clearPersistedState -persistState false
Command-line arguments:  -os win32 -ws win32 -arch x86 -clearPersistedState -persistState false

!ENTRY com.ti.evswsdk 4 0 2020-07-14 13:11:41.296
!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.202005080856"; version="0.0.0"
       com.ti.evswsdk.dashboard [219]
         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 2020-07-14 13:11:41.297
!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.202005080856"; version="0.0.0"
       com.ti.evswsdk.dashboard [219]
         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 2020-07-14 13:11:41.298
!MESSAGE FrameworkEvent ERROR
!STACK 0
org.osgi.framework.BundleException: Could not resolve module: com.ti.evswsdk.calbq769x2 [200]
  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.202005080856"; 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 [253]
         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.202005080856"; version="0.0.0"
              com.ti.evswsdk.dashboard [219]
                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 2020-07-14 13:11:41.298
!MESSAGE FrameworkEvent ERROR
!STACK 0
org.osgi.framework.BundleException: Could not resolve module: com.ti.evswsdk.cmdsequence [216]
  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.202005080856"; version="0.0.0"
       com.ti.evswsdk.dashboard [219]
         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 2020-07-14 13:11:41.299
!MESSAGE FrameworkEvent ERROR
!STACK 0
org.osgi.framework.BundleException: Could not resolve module: com.ti.evswsdk.dashboard [219]
  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 2020-07-14 13:11:41.299
!MESSAGE FrameworkEvent ERROR
!STACK 0
org.osgi.framework.BundleException: Could not resolve module: com.ti.evswsdk.dataflashview [220]
  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.202005080856"; version="0.0.0"
       com.ti.evswsdk.fsexport [228]
         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.202005080856"; version="0.0.0"
              com.ti.evswsdk.dashboard [219]
                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 2020-07-14 13:11:41.300
!MESSAGE FrameworkEvent ERROR
!STACK 0
org.osgi.framework.BundleException: Could not resolve module: com.ti.evswsdk.fieldprogrammer [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.202005080856"; version="0.0.0"
       com.ti.evswsdk.dashboard [219]
         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 2020-07-14 13:11:41.301
!MESSAGE FrameworkEvent ERROR
!STACK 0
org.osgi.framework.BundleException: Could not resolve module: com.ti.evswsdk.firmware [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.202005080856"; version="0.0.0"
       com.ti.evswsdk.dashboard [219]
         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 2020-07-14 13:11:41.307
!MESSAGE FrameworkEvent ERROR
!STACK 0
org.osgi.framework.BundleException: Could not resolve module: com.ti.evswsdk.fsexport [228]
  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.202005080856"; version="0.0.0"
       com.ti.evswsdk.dashboard [219]
         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 2020-07-14 13:11:41.307
!MESSAGE FrameworkEvent ERROR
!STACK 0
org.osgi.framework.BundleException: Could not resolve module: com.ti.evswsdk.gdk [230]
  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.202005080856"; version="0.0.0"
       com.ti.evswsdk.dataflashview [220]
         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.202005080856"; version="0.0.0"
              com.ti.evswsdk.fsexport [228]
                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.202005080856"; version="0.0.0"
                     com.ti.evswsdk.dashboard [219]
                       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 2020-07-14 13:11:41.308
!MESSAGE FrameworkEvent ERROR
!STACK 0
org.osgi.framework.BundleException: Could not resolve module: com.ti.evswsdk.goldenizing [233]
  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.202005080856"; version="0.0.0"
       com.ti.evswsdk.dashboard [219]
         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 2020-07-14 13:11:41.309
!MESSAGE FrameworkEvent ERROR
!STACK 0
org.osgi.framework.BundleException: Could not resolve module: com.ti.evswsdk.programming769x2 [253]
  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.202005080856"; version="0.0.0"
       com.ti.evswsdk.dashboard [219]
         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 2 0 2020-07-14 13:11:41.474
!MESSAGE Could not resolve module: com.ti.evswsdk.fsexport [228]
  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.202005080856"; version="0.0.0"
       com.ti.evswsdk.dashboard [219]
         Unresolved requirement: Import-Package: com.ti.evswsdk.gpcpackager.views


!ENTRY com.ti.evswsdk.gdk 2 0 2020-07-14 13:11:41.475
!MESSAGE Could not resolve module: com.ti.evswsdk.gdk [230]
  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.202005080856"; version="0.0.0"
       com.ti.evswsdk.dataflashview [220]
         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.202005080856"; version="0.0.0"
              com.ti.evswsdk.fsexport [228]
                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.202005080856"; version="0.0.0"
                     com.ti.evswsdk.dashboard [219]
                       Unresolved requirement: Import-Package: com.ti.evswsdk.gpcpackager.views


!ENTRY com.ti.evswsdk.calbq769x2 2 0 2020-07-14 13:11:41.475
!MESSAGE Could not resolve module: com.ti.evswsdk.calbq769x2 [200]
  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.202005080856"; 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 [253]
         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.202005080856"; version="0.0.0"
              com.ti.evswsdk.dashboard [219]
                Unresolved requirement: Import-Package: com.ti.evswsdk.gpcpackager.views


!ENTRY com.ti.evswsdk.dashboard 2 0 2020-07-14 13:11:41.476
!MESSAGE Could not resolve module: com.ti.evswsdk.dashboard [219]
  Unresolved requirement: Import-Package: com.ti.evswsdk.gpcpackager.views


!ENTRY com.ti.evswsdk.cmdsequence 2 0 2020-07-14 13:11:41.476
!MESSAGE Could not resolve module: com.ti.evswsdk.cmdsequence [216]
  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.202005080856"; version="0.0.0"
       com.ti.evswsdk.dashboard [219]
         Unresolved requirement: Import-Package: com.ti.evswsdk.gpcpackager.views


!ENTRY com.ti.evswsdk.dataflashview 2 0 2020-07-14 13:11:41.476
!MESSAGE Could not resolve module: com.ti.evswsdk.dataflashview [220]
  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.202005080856"; version="0.0.0"
       com.ti.evswsdk.fsexport [228]
         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.202005080856"; version="0.0.0"
              com.ti.evswsdk.dashboard [219]
                Unresolved requirement: Import-Package: com.ti.evswsdk.gpcpackager.views


!ENTRY com.ti.evswsdk.fieldprogrammer 2 0 2020-07-14 13:11:41.477
!MESSAGE Could not resolve module: com.ti.evswsdk.fieldprogrammer [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.202005080856"; version="0.0.0"
       com.ti.evswsdk.dashboard [219]
         Unresolved requirement: Import-Package: com.ti.evswsdk.gpcpackager.views


!ENTRY com.ti.evswsdk.firmware 2 0 2020-07-14 13:11:41.477
!MESSAGE Could not resolve module: com.ti.evswsdk.firmware [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.202005080856"; version="0.0.0"
       com.ti.evswsdk.dashboard [219]
         Unresolved requirement: Import-Package: com.ti.evswsdk.gpcpackager.views


!ENTRY com.ti.evswsdk.authentication 2 0 2020-07-14 13:11:41.477
!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.202005080856"; version="0.0.0"
       com.ti.evswsdk.dashboard [219]
         Unresolved requirement: Import-Package: com.ti.evswsdk.gpcpackager.views


!ENTRY com.ti.evswsdk.goldenizing 2 0 2020-07-14 13:11:41.478
!MESSAGE Could not resolve module: com.ti.evswsdk.goldenizing [233]
  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.202005080856"; version="0.0.0"
       com.ti.evswsdk.dashboard [219]
         Unresolved requirement: Import-Package: com.ti.evswsdk.gpcpackager.views


!ENTRY com.ti.evswsdk 2 0 2020-07-14 13:11:41.478
!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.202005080856"; version="0.0.0"
       com.ti.evswsdk.dashboard [219]
         Unresolved requirement: Import-Package: com.ti.evswsdk.gpcpackager.views


!ENTRY com.ti.evswsdk.programming769x2 2 0 2020-07-14 13:11:41.478
!MESSAGE Could not resolve module: com.ti.evswsdk.programming769x2 [253]
  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.202005080856"; version="0.0.0"
       com.ti.evswsdk.dashboard [219]
         Unresolved requirement: Import-Package: com.ti.evswsdk.gpcpackager.views


!ENTRY org.eclipse.osgi 4 0 2020-07-14 13:11:41.488
!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)

0 Stephanie Sahm over 4 years ago in reply to Stephanie Sahm

Prodigy 235 points

Hello,

I just would like to give you an update…

Am I right, that the df.fs file only writes the DF and the bq.fs file updates the firmware, writes the DF and the last part of the srec like keywords and so on?

I have found the pdf "Flash Stream File Format.pdf" and some explanations in the forum for bq with SM bus:

SWB: Write block command

SWW: Write word command

SCW and SCL: Compare command

But there are still questions open:

1) What is the difference between SCW and SCL?

2) Could you please give an explanation of the structure of the protocol for SM Bus

3) Is there a mechanism integrated to verify that all data are written properly?

4) Is there a list of commands in Rom Mode available in order to understand the content of a Flash Stream File in Detail?

Thanks in advance.

Steffi

0 Andy Liu (BMS) over 4 years ago in reply to Stephanie Sahm

TI__Guru 52115 points

You can find some details in Section 5 of the following app note.

https://www.ti.com/lit/an/slua801/slua801.pdf

Regarding other questions, I will take a look tomorrow and get back to you.

Andy

0 Stephanie Sahm over 4 years ago in reply to Andy Liu (BMS)

Prodigy 235 points

Dear Andy,

Do you have some news for me?

Best regards

Steffi

0 Andy Liu (BMS) over 4 years ago in reply to Stephanie Sahm

TI__Guru 52115 points

I'm checking with our software team regarding your questions. Will provide my updates once I receive their feedback.

Andy

0 Stephanie Sahm over 4 years ago in reply to Stephanie Sahm

Prodigy 235 points

Dear Andy,

During writing some code for parsing the fs file, I found another command: SWC.

It would be very helpful for me to get some detailed info about the commands in a fs file.

Thanks

Steffi

0 Stephanie Sahm over 4 years ago in reply to Andy Liu (BMS)

Prodigy 235 points

Ok. Thanks.

0 Andy Liu (BMS) over 4 years ago in reply to Stephanie Sahm

TI__Guru 52115 points

Understood. Will let you know once I get some feedback from our software team.

Andy

0 Stephanie Sahm over 4 years ago in reply to Andy Liu (BMS)

Prodigy 235 points

Dear Andy,

Would it be possible for you to provide me contact information of your software team so that I could ask them directly?

Best regards

Steffi

0 Andy Liu (BMS) over 4 years ago in reply to Stephanie Sahm

TI__Guru 52115 points

See the feedback I have got so far.

“SCW”- indicates the line is a command to read and compare a SMBus word (2 bytes)

“SCL:” - indicates the line is a command to read and compare a SMBus block of one of more bytes of data and validate the block length

"SWC:” - indicates the line is a command to write a SMBus command (0 bytes)

“SWW:” - indicates the line is a command to write a SMBus word (2 bytes)

“SWB:” - indicates the line is a command to write a SMBus block of one of more bytes of data

Andy

0 Stephanie Sahm over 4 years ago in reply to Andy Liu (BMS)

Prodigy 235 points

Dear Andy,

Thanks, that helps me to implement the commands of the fs File.

But there is still a question concerning the commands: The SCW and the SCL command read data to compare. But what should happen, if the given data in the fs file and the read data of SMBus are not equal?

Best regards

Steffi

0 Andy Liu (BMS) over 4 years ago in reply to Stephanie Sahm

TI__Guru 52115 points

If data returned by the gauge don't match the byte sequence given, it basally means the flash is not properly programmed. I think you have to stop the current programming and start over again.

If you follow the sequence and timing correctly, I think that kind of mismatch should occur pretty rarely.

Andy

0 Stephanie Sahm over 4 years ago in reply to Andy Liu (BMS)

Prodigy 235 points

Dear Andy,

Thanks for all the information.

There are some of my older questions open:

1) Is there a mechanism integrated to verify that all data are written properly and how does it works?

2) Is there a list of commands in Rom Mode available in order to understand the content of a Flash Stream File in Detail?

Best regards

Steffi

0 Kalman Huang over 4 years ago

Prodigy 60 points

Hi Stephanie,

I am facing the same problem. Is this what you are looking for? https://e2e.ti.com/support/power-management/f/196/t/851756. In Matt Sunna's reply, he said he will send a python demo can be used to program the srec directly using an EV2400.

Kalman

0 Stephanie Sahm over 4 years ago in reply to Kalman Huang

Prodigy 235 points

Dear Kalman,

Thanks for your hint.

that exactly is my problem. I solved this for bq40z50 with bq.fs file. That works fine. But I have to realize it for bq 78350 too. So I still have the problem…

Best reagrds

Steffi

0 Kalman Huang over 4 years ago in reply to Stephanie Sahm

Prodigy 60 points

Dear Stephanie,

By solving the problem, did you writing your own code to parse bq.fs file and follow the command line to program bq40z50?

I am thinking of implementing it on an MCU, communicate with the chip directly.

According to the command definition given by Ti:

“SCW”- indicates the line is a command to read and compare a SMBus word (2 bytes)

“SCL:” - indicates the line is a command to read and compare a SMBus block of one of more bytes of data and validate the block length

"SWC:” - indicates the line is a command to write a SMBus command (0 bytes)

“SWW:” - indicates the line is a command to write a SMBus word (2 bytes)

“SWB:” - indicates the line is a command to write a SMBus block of one of more bytes of data

I have some assumption about the bq.fs file, please correct me if I am wrong:

1. The first and second byte is the command.

2. It seems the 3rd and 4th byte is the address, because I found it matches the data memory address.

3. A readback is needed after SWB command, to get the checksum reported by the client for verification.

4. No need to figure out the exact meaning of all the commands(the first and second byte), just follow the command lines.

BTW:

I found this might also be helpful:

training.ti.com/gauge-programming-fundamentals

0 Stephanie Sahm over 4 years ago in reply to Kalman Huang

Prodigy 235 points

Dear Kalman,

I wrote own code to parse.

I used this 6136.Flash Stream File Format.pdf and the information Andy has given.

Best regards

Stephanie

0 Kalman Huang over 4 years ago in reply to Stephanie Sahm

Prodigy 60 points

Dear Stephanie,

Thanks for the info!

Best regards

Kalman

The TI E2E™ design support forums will undergo maintenance from July 11 to July 13. If you need design support during this time, open a new support request with our customer support center.

Power management

Power management forum

BQ40Z50: Programming in mass production