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/CC3200-LAUNCHXL: Uniflash 4.x can't get cc3200 visible on COM Port

Part Number: CC3200-LAUNCHXL
Other Parts Discussed in Thread: UNIFLASH, CC3200, , CC3220SF-LAUNCHXL

Tool/software: Code Composer Studio

Hi TI Development,

It very hard time to get uniflash visible on COM Port on windows 10 see below error receiving. I do have COM Port visible on device Manager but showing hardware device is not connected to the computer. (Code 45) 

Please help! 

 

  • Hi,

    It seems you are using Uniflash 3.4.1, which is the last version to support CC3200 devices. 

    That said, can you be sure the SOP jumpers on your Launchpad are properly configured for Flashing? Consult the board's documentation for details.

    Hope this helps,

    Rafael

  • Hi Rafael,

    Thanks for your response. I am following exactly per guide, using all the SOP2, J6 and J7 jumpers are set correctly(do you have suggestion or link to double check). Even after that I am not able to get device visible on system , I am thinking its windows 10 version not compatible. Looks like I wasted money on buying this CC3200 device

    Regards,

    Amit

  • Hi Amit,

    Please make sure that you have selected correct COM port number. Please provide screenshot from device manager with list of you COM ports.

    Uniflash version 3.4.1 works with Windows 10 without any issue. I have tested version 3.4.1 with following builds of Win 10:

    • Win 10 Home 64bit ... 1507, 1511, 1703, 1709, 1803, 1809
    • Win 10 Pro 32bit ... 1703, 1709, 1803

    Jan

  • COM port number 1 does not look as correct value.
    Check device manager. It should say like this: CC3200LP Dual Port (COMxx)

  • Hi,

    As Tom and Jan mentioned, check for the following in your system.

    Also, the board should be populated with the UART signals set to Flash and a single jumper on SOP2. This is mentioned on sections 2.4.4 and 2.4.5 of the CC3200-LAUNCHXL User's Guide:

    http://www.ti.com/lit/ug/swru372b/swru372b.pdf  

    Hope this helps,

    Rafael

  • Thanks my device able to connect to COM port now but is there any way to bump up the flash memory? I am seeing below issue. Please suggest.

    I want to show customer a simple demo for IIoT using cc3200 and cc5650 but till no success, do you suggest any demo IoT sensor device works with Google IoT? 

    *** Out of space, tried to write 25586 bytes ***
    make: *** [/data/fwbuild-volumes/latest/apps/app3/cc3200/build_contexts/build_ctx_133522072/build/objs/spiffs.img] Error 1
    make: *** Waiting for unfinished jobs....
    /data/fwbuild-volumes/latest/apps/app3/cc3200/build_contexts/build_ctx_133522072/deps/modules/mongoose-os/platforms/cc3200/Makefile.build:238: recipe for target '/data/fwbuild-volumes/latest/apps/app3/cc3200/build_contexts/build_ctx_133522072/build/objs/spiffs.img' failed
    "/data/fwbuild-volumes/latest/apps/app3/cc3200/build_contexts/build_ctx_133522072/deps/modules/mongoose-os/platforms/cc3200/ld/cc3200.cmd", line 24: error #10099-D:
    program will not fit into available memory. placement with alignment fails
    for section "GROUP_1" size 0x49bbc . Available memory ranges:
    SRAM size: 0x40000 unused: 0x3fafc max hole: 0x3fafc
    error #10010: errors encountered during linking;
    "/data/fwbuild-volumes/latest/apps/app3/cc3200/build_contexts/build_ctx_1335
    22072/build/objs/app3.elf" not built

    >> Compilation failure
    /data/fwbuild-volumes/latest/apps/app3/cc3200/build_contexts/build_ctx_133522072/deps/modules/mongoose-os/platforms/cc3200/Makefile.build:325: recipe for target '/data/fwbuild-volumes/latest/apps/app3/cc3200/build_contexts/build_ctx_133522072/build/objs/app3.elf' failed
    make: *** [/data/fwbuild-volumes/latest/apps/app3/cc3200/build_contexts/build_ctx_133522072/build/objs/app3.elf] Error 1
    make: Leaving directory '/app'
    Error: exit status 2
    /go/src/github.com/mongoose-os/mos/mos/build_local.go:679:
    /go/src/github.com/mongoose-os/mos/mos/build_local.go:666:
    /go/src/github.com/mongoose-os/mos/mos/build_local.go:431:
    /go/src/github.com/mongoose-os/mos/mos/build.go:223:
    /go/src/github.com/mongoose-os/mos/mos/build.go:166:
    /go/src/github.com/mongoose-os/mos/mos/main.go:196: build failed
    Error: /go/src/github.com/mongoose-os/mos/mos/build_remote.go:326: build failed
    /go/src/github.com/mongoose-os/mos/mos/build.go:223:
    /go/src/github.com/mongoose-os/mos/mos/build.go:166:
    /go/src/github.com/mongoose-os/mos/mos/main.go:196: build failed

  • Hello Amit, 

    my understanding is that your initial issue has been resolved.
    Please, close this thread as resolved and start a new one with a subject like:
    program will not fit into available memory.

    Section "GROUP_1" size 0x49bbc is equal to 302 012.  
    SRAM size: 0x40000 unused: 0x3fafc max hole: 0x3fafc is equal to 260 860. 

    CC3200 version on a LaunchPad offers 248 KB of RAM for all custom code and data including stack and heap spaces. 

    Your program does not fit into available memory. 
    I see the following options for you: 
    - reduce demo size
    - place some static data into external flash memory like in case of out-of-box demo
    - move your design to CC3220SF-LAUNCHXL.

  • Thanks Tom,

    I am going to close this incident -

    place some static data into external flash memory like in case of out-of-box demo  (Is there any how to guide for it?)
    - move your design to CC3220SF-LAUNCHXL. (Where I can return this CC3200 device and re-order this device?)

    Thank you,

    Amit

  • amit lal said:
    place some static data into external flash memory like in case of out-of-box demo  (Is there any how to guide for it?)


    I do not know.

    amit lal said:
    - move your design to CC3220SF-LAUNCHXL. (Where I can return this CC3200 device and re-order this device?)


    Ask a local TI representative.