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.

CCS/CC3100: Uniflash 3.4.1 crashes after Windows 10 updated to version 1709

Part Number: CC3100
Other Parts Discussed in Thread: UNIFLASH

Tool/software: Code Composer Studio

It began crashing after Windows 10 updated to version 1709 (Version 10.0.16299.64)

When I try to flash CC3100 via UART it crashes with following error:

"c:\TI\uniflash_3.4\eclipse\command_line\..\jre\bin\java" -Djna.library.path="c:/TI/uniflash_3.4/eclipse/plugins/com.ti.uniflash.common.libs_1.0.0.201602120704/libs/" -DUniFlashPluginsDir="c:/TI/uniflash_3.4/eclipse/plugins/" -cp "c:/TI/uniflash_3.4/eclipse/command_line/com.ti.uniflash.commandline.jar";"c:/TI/uniflash_3.4/eclipse/plugins/*";"c:/TI/uniflash_3.4/eclipse/plugins/com.ti.jna_1.0.0.201602120704/libs/*";"c:/TI/uniflash_3.4/eclipse/plugins/com.ti.jna_1.0.0.201602120704/*";"c:/TI/uniflash_3.4/eclipse/plugins/com.ti.uniflash.common.libs_1.0.0.201602120704/libs/*";"c:/TI/uniflash_3.4/eclipse/plugins/com.ti.uniflash.common.libs_1.0.0.201602120704/*";"c:/TI/uniflash_3.4/eclipse/plugins/com.ti.uniflash.common.libs_1.0.0.201602120704/libs/" com.ti.uniflash.commandline.CommandLine -dependencyPath "c:/TI/uniflash_3.4/eclipse/plugins/com.ti.uniflash.wireless.files_1.0.0.201602120706/" -config "C:/FlashCC3100/CC3100.usf" -setOptions com=5 spPath="C:/FlashCC3100/servicepack_1.0.1.11-2.9.0.0.bin" capacity=16MB -operations format servicePackUpdate program

***** Texas Instruments Universal Flash Programmer *****

> Configuring UniFlash with the following configuration: C:/FlashCC3100/CC3100.usf

> Device: SimpleLink Wifi CC3100/CC3200
> Interface: CC3x Serial(UART) Interface

> Template XML: C:\FlashCC3100\CC3100_session\templates\CC3xxx_template.xml
> Token XML: C:\FlashCC3100\CC3100_session\templates\CC3xxx_token.xml
> User setting [com]: 5
> User setting [capacity]: 16MB
> User setting [spPath]: C:/FlashCC3100/servicepack_1.0.1.11-2.9.0.0.bin

> Executing operation: format
> Relevant settings:
        Capacity: 16MB
INFO: > Executing Operation: Connect
INFO: setting break signal
INFO: detecting FTDI for device reset
INFO: > Executing Operation: Disconnect
Exception in thread "main" java.lang.Error: Invalid memory access
        at com.sun.jna.Native.invokeInt(Native Method)
        at com.sun.jna.Function.invoke(Function.java:383)
        at com.sun.jna.Function.invoke(Function.java:315)
        at com.sun.jna.Library$Handler.invoke(Library.java:212)
        at com.sun.proxy.$Proxy0.ExecuteOperation(Unknown Source)
        at com.ti.uniflash.cc3xx.integrationlayer.IntegrationLayerLibraryProxy.ExecuteOperation(IntegrationLayerLibraryProxy.java:43)
        at com.ti.uniflash.cc3xx.controlflow.UserOperationsHandler.ExecuteOperationHandler(UserOperationsHandler.java:272)
        at com.ti.uniflash.cc3xx.controlflow.UserOperationsHandler.executeTargetOp(UserOperationsHandler.java:325)
        at com.ti.uniflash.cc3xx.controlflow.UserOperationsHandler.ExecuteOp(UserOperationsHandler.java:368)
        at com.ti.uniflash.cc3xx.commands.base.BaseExecuteCommand.execute(BaseExecuteCommand.java:18)
        at com.ti.uniflash.cc3xx.commands.base.GenericCommandHandler.execute(GenericCommandHandler.java:16)
        at com.ti.uniflash.commandline.CC3xCommandLineHandler.executeOperation(Unknown Source)
        at com.ti.uniflash.commandline.CommandLine.executeOperations(Unknown Source)
        at com.ti.uniflash.commandline.CommandLine.main(Unknown Source)

I use the last version of JRE (1.8.0.151)

On Windows 10 Pro 1703 it worked properly.

  • Hello George,
    This is currently under investigation. I need to update my Windows 10 installation and try an reproduce. I will keep you posted of my progress.

    Thanks
    ki
  • Hello,
    I updated one of my lab machines to Windows 10 version 1709. Uniflash 3.4.1 still works fine with my CC31xx target via UART interface.

    Can you try programming via the GUI and see what the result is?

    Thanks
    ki
  • Hello!
    I have made some investigation. I installed Windows 10 1709, Windows 10 1703, Windows 7 SP1 on VirtualBox and got the same result. Also i tried to use different versions of JRE (both of x86 and x64, old versions such as 1.7.80). Result is the same.

    Here are screenshots of Uniflash 3.4.1
    Windows 10 1709 on VirtualBox:

    Windows 10 1703 on VirtualBox:

    Windows 7 SP1 on VirtualBox:

    Windows 7 SP1 console on VirtualBox:

    Windows 7 SP1 on another PC (works well):

    Also i noticed that driver of USB Hub 3.0 on my host PC also has been updated with Windows:

    I think the problem is in this driver, because it's once common thing for all guest OS' on VirtualBox, that may influence.

  • Interesting. Everything works on my native Win 10-64 machine (1709). What kind of USB port are you connected to on your Win 10 machine? 2.0 or 3.0? And are you connected to a hub or direct?

    Thanks
    ki
  • Hello!

    I have tried both of ports USB 2.0 and USB 3.0. Have tried to connect to USB hub and directly to PC (motherboard and front panel).

    Result is the same.

    My colleague has PC with Windows 10 1703, there it still runs well

    I use CP2102 as USB-UART converter. Used driver is the same for all tests.

    In accordance with documentation on MS Dev Center here are two separated USB Driver Stacks.

    I will try to rollback both of them to version 10.0.15063.x and let you know if it helps

  • After installed update KB4054517, that was released on December 12, 2017, windows version became 16299.125. With this update Uniflash works well again.

    I'm not sure if problem was with USB drivers. But here's no issue anymore and topic may be closed.

    Thank you for support

  • Glad to hear the update resolved your problem.

    I just noticed that I have 16299.98 installed while previously, you have 16299.64. Since my version still worked for me, perhaps it was an issue with the .64 version and they released a fix in the .98 version.

    Anyway, thanks for the update

    ki