Copyright ©

Mongoose OS Forum


Problems with TI CC3220SF Dev Board Google IoT Quick Start Tutorial

Hi, everyone. I'm working through the TI CC3220SF quick start tutorial, as described here:

First question: my TI CC3220SF dev board seems to be associated with \dev\ttyACM0 and \dev\ttyACM1 and these two ports are listed in the dropdown menu in the Mongoose UI --- is this a problem? Is there a way to get the OS to recognize the two \ttyACM ports as a single USB or serial port? As you can see on the image I've attached, I selected \dev\ttyACM0, but in the tutorial video (which is for an Espressif board) there is a single \dev\ttyUSB port that the is selected...

When I try to put the Mongoose example program onto flash, the "Flash" icon just spins indefinitely after the following device log is put out:

[Jan 8 18:08:24.258] E0108 18:08:24.258712 2202 ui.go:537] Calling: Sys.GetInfo
[Jan 8 18:08:27.296] E0108 18:08:27.296310 2202 ui.go:561] Call complete, error: context deadline exceeded
[Jan 8 18:08:50.002] Repository "/home/stephen/.mos/apps-1.23/demo-js" is dirty, leaving it intact
[Jan 8 18:08:50.002]
[Jan 8 18:08:51.505] Fetching
[Jan 8 18:09:04.896] Loaded demo-js/cc3220 version 1.0 (20171229-091433/???)
[Jan 8 18:09:05.060] Found BPI binary: /home/stephen/ti/uniflash_4.2.1/simplelink/gen2/bin/BuildProgrammingImage
[Jan 8 18:09:05.062] Using XDS110 debug probe to control the device...
[Jan 8 18:09:05.066] XDS110 HW 39 S/N E0071009
[Jan 8 18:09:05.066] Opening /dev/ttyACM0...
[Jan 8 18:09:05.067] Connecting to boot loader..
[Jan 8 18:09:07.698] CC3220SF boot loader v0.1.0.3, storage 0x86
[Jan 8 18:09:07.698] Switching to NWP...
[Jan 8 18:09:09.138] NWP boot loader v1.1.0.3, storage 0x84
[Jan 8 18:09:09.198] MAC: 98:84:e3:f7:18:67
[Jan 8 18:09:09.198] Applying boot loader patches...
[Jan 8 18:09:10.018] RAM patch applied, new version:
[Jan 8 18:09:10.618] Flash patch applied
[Jan 8 18:09:10.618] Generating UCF image for 98:84:e3:f7:18:67 (flash size: 4194304)
[Jan 8 18:09:10.622] Running /home/stephen/ti/uniflash_4.2.1/simplelink/gen2/bin/BuildProgrammingImage -i /tmp/demo-js_cc3220_1.0_751042323 -x /tmp/demo-js_cc3220_1.0_751042323/ImageConfig.xml
[Jan 8 18:09:13.306] Uploading UCF image (615600 bytes)
[Jan 8 18:09:37.411] Upload finished, image is being extracted...
[Jan 8 18:10:02.326] Rebooting device...
[Jan 8 18:10:02.378] All done!
[Jan 8 18:10:05.389] E0108 18:10:05.389925 2202 ui.go:537] Calling: Sys.GetInfo
[Jan 8 18:10:07.674]
[Jan 8 18:10:07.686] cc32xx_init demo-js 1.0 (20171229-091433/???)
[Jan 8 18:10:07.694] cc32xx_init Mongoose OS 2017122909 (20171229-091433/???)
[Jan 8 18:10:07.700] cc32xx_init RAM: 251792 total, 238204 free
[Jan 8 18:10:08.520] E0108 18:10:08.520380 2202 ui.go:561] Call complete, error: context deadline exceeded

When I restart MOS, it claims that the program has been successfully loaded, but then there are problems further down in the tutorial with connecting to the Google Cloud, so I thought I would start here.

Any thoughts? Thanks and regards.


  • I guess those /dev/ttyACM0 and /dev/ttyACM1 ports are unrelated to the cc3220 board; if you unplug the board, will these ports still be present?

  • edited January 12

    Sorry, if I didn't write clearly before. The /dev/ttyACM0 and /dev/tty/ACM1 ports seem to be how my CC3220SF board is registered in the Ubuntu log.

    When I use the dmesg command in the terminal I get this after just plugging the board in:

    [ 8949.318313] usb 1-14: new full-speed USB device number 5 using xhci_hcd
    [ 8949.459648] usb 1-14: New USB device found, idVendor=0451, idProduct=bef3
    [ 8949.459652] usb 1-14: New USB device strings: Mfr=1, Product=2, SerialNumber=3
    [ 8949.459654] usb 1-14: Product: XDS110 ( Embed with CMSIS-DAP
    [ 8949.459657] usb 1-14: Manufacturer: Texas Instruments
    [ 8949.459659] usb 1-14: SerialNumber: E0071009
    [ 8949.461653] hid-generic 0003:0451:BEF3.0003: hiddev0,hidraw2: USB HID v1.11 Device [Texas Instruments XDS110 ( Embed with CMSIS-DAP] on usb-0000:00:14.0-14/input5
    [ 8949.474418] cdc_acm 1-14:1.0: ttyACM0: USB ACM device
    [ 8949.474596] cdc_acm 1-14:1.3: ttyACM1: USB ACM device
    [ 8949.474716] usbcore: registered new interface driver cdc_acm
    [ 8949.474717] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters

    I don't suppose you guys could post a video quickstart for how to use get the CC3220SF started with Google Cloud? You guys have posted one for the Espressif ESP32 and a CC3220SF would be nice, especially after the issues I've had with the quickstart.

    For your reference, when I tried to connect to the Google CLoud with your quickstart using the CC3220SF board (after a possibly unsuccessful FLASH attempt), I got this from the print out:

    17:53:02.110] Tock uptime: 1465.973357 {"free_ram":213676,"total_ram":251792}
    [Jan 8 17:53:03.110] Tick uptime: 1466.974357 {"free_ram":213676,"total_ram":251792}
    [Jan 8 17:53:04.111] Tock uptime: 1467.976357 {"free_ram":213676,"total_ram":251792}
    [Jan 8 17:53:04.870] mgos_mqtt_global_con MQTT connecting to
    [Jan 8 17:53:04.996] sl_set_ssl_opts CA_FILE_NAME ca-equifax.crt.der -> 0
    [Jan 8 17:53:05.105] Tick uptime: 1468.969357 {"free_ram":213492,"total_ram":251792}
    [Jan 8 17:53:05.304] mgos_mqtt_ev MQTT TCP connect error (-688)
    [Jan 8 17:53:05.310] mgos_mqtt_ev MQTT Disconnect
    [Jan 8 17:53:05.313] mqtt_global_reconnec MQTT connecting after 64439 ms
    [Jan 8 17:53:06.107] Tock uptime: 1469.971357 {"free_ram":213676,"total_ram":251792}

    According to some of the TI documentation, after flashing a program, you're supposed to remove a jumper that connects two pins, so maybe if I do that it'll work....

    TI docs:

    EDIT: copied and pasted the wrong device logs...

  • Hmmm... now I can't seem to reset the dev board to its factory settings. I also can't flash to the dev. board from Code Composer Studio. This has not been a good experience.

  • Hi, I am facing the same issue with cc3220sf launchpad. Were you able to figure out any solution to the above mentioned problem?

Sign In or Register to comment.