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.

CC3300MOD: Require basic information about various folders from CC3300 SDK - cc33xx_rtos_mcu_package_R8.1

Part Number: CC3300MOD
Other Parts Discussed in Thread: CC3300

Hi All,

We are working CC3300 SDK porting on STM32F412ZG.

Initial porting we have ported various folder from SDK and it is working.

In order to finalize the SDK porting, we will like to understand the purpose of specific folder and whether it is really required for porting.

We listed various folder in below table and our understanding in "Description" folder.

Please provide detail for folder marked as '?' and also confirm whether it is required to be ported or not.

Please also suggest any missing folder from below list.

SDK main folder = cc33xx_rtos_mcu_package_R8.1

SDK Folder

File present

Description

SDK main folder \ source\ti\net\ wifi_interface\app_entry

Wlan_if.c, init_host,c, wlan_commands.c

etc

Wlan_if.c provide all Wi-Fi apis like ‘Wlan_Start’, ‘Wlan_Stop’, etc

SDK main folder \examples\ CC3xx_thick_mac_network_terminal\ WiFi_adaptation_layer

osi_filesystem.c

osi_filesystem.c

wlan_irq_adapt.c

etc.

This files important to be port on target microcontroller

SDK main folder \source\ti\net\wifi_interface\ fw_control_cmd

control_cmd_fw

?

SDK main folder \source\ti\net\wifi_interface\ inc_common

?

SDK main folder \source\ti\net\wifi_interface\ inc_common_fw

?

SDK main folder \source\ti\net\wifi_interface\lib\ ticlang

?

SDK main folder \source\ti\drivers\net\wifi

?

SDK main folder \source\third_party

 

 

 

This include lwIP library

Thanks....

  • Hi,

    Porting is mainly concentrated on the 3 files under \examples\ CC3xx_thick_mac_network_terminal\ WiFi_adaptation_layer. Rest are all driver agnostic. For details on other directories:

    • \source\ti\net\wifi_interface\ fw_control_cmd - lower layer driver of how a command gets to the host interface and then to the chip
    • \source\ti\net\wifi_interface\ fw_control_cmd - just header files for the .c implementation
    • \source\ti\net\wifi_interface\ inc_common_fw - again, just header files. You do not need to import these. Just compile
    • \source\ti\net\wifi_interface\lib\ ticlang - this is the precompiled library. If you recompile your own with a different compiler or flags, this is where the output library would reside
    • \source\ti\drivers\net\wifi - includes the host driver folder which does not need any porting and wifi_platform that includes wrappers that make use of the adaptation layers I mentioned before. For example, the bus_spi.c calls to actual spi transaction via spi_WriteSync(), spi_ReadSync(), etc that are implemented on spi_adapt.c

    Regards,

    Shlomi