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.

Getting start with CC3200

Other Parts Discussed in Thread: CC3200, CC1310, CC3200MOD, UNIFLASH

Hi All,

I'm starting to use the CC3200, I've read and see the various PDF about Getting Start etc but I'm a little confused, too many informations, I'll try to explain:

1 )The getting start talk about the Project 0 (wlan_station), importing into a  workspace various projects , bulding them (I don't understand why I have to build all the projects and not only the wlan_station one) and flashing the result file by using the serial over usb interface. Now, if I didn't see wrong, this project is linked to the other ones cointained into the workspace in some way, and, if I have to change some parameters like access point name, I have to change a common.h file that is common to the other example. But if I want to create an empty and independent project, which is the correct way ? I have to import always all the others project like simplilink, os_lib etc ???

2) Another page on CC3200 SDK talk about various projects, but many of them are developed on FreeRTOS or NO-OS, how are they imported into CCS ? Why they are not designed with the official TI-RTOS?

3) Why the SDK examples aren't show in the CCS examples tree view? I can see only Driver, Instrumental and Kernel examples

4) Can you explain me exactly which is the criteria about importing CC3200 SDK folder from "Import CCS project" instead using an integrated solution inside the CCS like CC13xx or CC26xx series about the code examples?

I found a little complicated the CC3200 SDK implementation into the CCS. 

Thanks!

Riccardo

  • Hello Riccardo and thanks for the feedback,

    1) with getting started with Project 0, the intention was to show all details to address all type of audiences. It is still possible to run the example with less effort. For example, you can program the already existing binary of the project and test it against your local AP. You can also modify the code without importing or compiling the driver lib and simplelink. These steps are presented in case you want to debug and step into these projects. The mandatory project is the tirtos config that is common to all examples.

    2) We wanted to show several options for OS, With no OS, you do not have to import anything other than the project itself as there is no OS library needed. For freeRTOS, the source is under third_party/FreeRTOS and the oslib is using it when it is set to FreeRTOS.

    3) the SDK is a standalone one, meaning it is not uploaded to official TIRTOS and thus does not appear as part of the resource explorer. We do intend to change it with next device generation.

    4) I am not I understand what you mean, please elaborate.

    Regards,

    Shlomi

  • 1- The way it is done like this is for code re-use. The projects are linked together using the arm linker settings. You do not have to import all the projects every time and rebuild, but what you need to do is to point the arm linker to the required "dependencies" compiled project files.

    For example all the projects require the simplelink project since all of them use the simplelink API (Device - Filesystem - NetApp ...). You do not have to import and rebuild the simplelink project everytime. But in each project that uses it, you should go to Project->Properties->ARM Linker->File Search Path and make sure the "simplelink.a" file is there. You will only need to rebuild the simplelink project only if you make code changes inside it. This is the same for other core projects such as MQTT and others.

    2- The projects are imported the same way. Once inside eclipse right click on the required project -> Build Configurations -> Set Active and choose the flavor you want. FreeRTOS, TIRTOS or nonos. This is only available for project that support multiple os.

    3- The SDK examples are shown inside the "Resource Explorer" but you need to choose from the root folder "CC3200 Simplelink Wifi". At least they are in my CCSv6.2.

    I am also starting new with the CC3200 so I hope the above is somehow helpful

  • Hi all,

    thanks for our replies. Shlomi, about the point number 4, you replied me already in the point number 3, thanks.

    Currently I'm developing another project using the CC1310 and the CCS version 6.1.2, about the CC3200 examples into the Resourse explorer how Hisham told, I don't remember if in my CCS version they appear, but I'm sure there aren't, if I'm not wrong, I can try to update to the 6.2 but only if the upgrade is compatible with the project developed using the previuos version.

    With respect to all points discussed, if I'm not wrong, the criteria of  the CC3200 examples projects, is to include the compiled dependecies (simplilink.a for example) instead include and compile the API from sources (like easylink API for CC1310, where the sources are include inside the single project), is this correct ?

    About the RTOS, I prefer to use TI-RTOS cause I've already used it to develop for CC1310, freeRTOS would be totally new for me, while no RTOS solution 

    would not work for me cause I need power management.

    Now, about my use of the CC3200, my target is develop an end device that can connect to an AP sending events like button press and sensor measure, receive command to turn on and off and dimming leds, all working with power management (TI-RTOS).

    Which could be the best way to start a basic project for me ? Use the Project 0 or use the examples into the CCS CC3200 examples (like TCP or UDP Echo) ?

    Which are the differencies between the SDK examples and the CC3200 examples included into CCS?

    About WIFI Direct, is implementable? (I'd like use it to execute the first configuration  on my device).

    Does CC3200 support a low power mode where can receive packet from wifi ? a sort of WOR.

    About the flashing, I saw that is used the UniFlash tool on serial port, this programming mode is hardware implemented on the CC3200 or is a preprogrammed bootloader? I'm using the CC3200MOD.

    Sorry for my questions but I'm try to collect the maximum number of information not to lose too much time in the development.

    Thanks again!

    Riccardo

  • Resource Explorer was introduced in CCSV6.2, it was not available on earlier versions. 

    You are correct the SDK uses compiled libraries .a files. The source for these compiled files is available, so you can make changes if you need and then recompile.

    If you want to make changes to the TI-RTOS configuration, you need to import the ti_rtos_config project as it contains the .cfg file used by the applications. The oslib project offers an abstraction layer so it will be easier to switch between TI-RTOS and FreeRTOS.

    For the power management you will need to implement it yourself inside the TI-RTOS Idle task. I am trying to implement myself now but I haven't finished with it yet. more information here 

    processors.wiki.ti.com/.../CC32xx_Idle_Profile_Application

    The SDK examples and the ones inside CCS are the same if not mistaken.

    This document explains the power modes of the CC3200 

    www.ti.com/.../swra462.pdf

    The CC3200 has an internal bootloader in ROM, you can call it hardware implemented if you want. A secondary "software" bootloader is required for the OTA applications.

    Peace 

  • Hello,

    Did the above post answer your query? please verify the answer.

    Shlomi

  • Hi,

    yes I get answer from it, I'll do tests in the next days.

    Thanks

    Riccardo