NOTICE: The Processors Wiki will End-of-Life in December of 2020. It is recommended to download any files or other content you may need that are hosted on processors.wiki.ti.com. The site is now set to read only.

CC3100 Summary of Known Issues

From Texas Instruments Wiki
Jump to: navigation, search
{{#switchcategory:MSP430=<McuHitboxHeader/>|C2000=<McuHitboxHeader/>|Stellaris=<McuHitboxHeader/>|TMS570=<McuHitboxHeader/>|MCU=<McuHitboxHeader/>|MAVRK=<MAVRKHitboxHeader/>|<HitboxHeader/>}}
Cc31xx cc32xx return home.png
Cc32xx return sample apps.png



Overview[edit]

This page contains all the known issues/limitations of CC31xx SDK release.

Summary[edit]

SDK Version Known Issues
1.1.0 SDK 1.1.0 known issues
1.0.0 SDK 1.0.0 known issues

SDK 1.1.0 Known issues[edit]

changes[edit]

Issue # Issue Detail Impact Workaround/Fix Remarks
1 Mismatch in datatype of file descriptor when UART interface is used on MSP430F5529LP and Tiva-c-Launchpad. Compilation warning/error while using the uart interface. Modify the FD datatype in "msp430f5529lp/uart.h" and "tiva-c-launchpad/uart.h"

    // typedef unsigned int Fd_t;
    typedef short* Fd_t;

2 Enabling Pull up on PB1 of Tiva-c platform before enabling the peripheral clock. Tiva-c platform application project. Comment out the code enabling the pull up on PB1 under function "spi_open()" in "tiva-c-launchpad/spi.c"

    /* Enable pull up on PB1, CC3100 UART RX */     // GPIOPadConfigSet(GPIO_PORTB_BASE, GPIO_PIN_1, GPIO_STRENGTH_4MA, GPIO_PIN_TYPE_STD_WPU);

3 Delay isn't required between two packets while sending the data over transceiver mode. User application using transceiver mode. N/A transceiver_mode and sls_transceiver_mode examples in SDK point out a requirement of minimum 50ms delay while sending the data over transceiver mode socket which is not required.
4 CW (carrier wave) mode not working during transceiver mode RadioTool CW mode testing will not work. Change the following statement at line 805 of cc3200-sdk\simplelink\source\driver.c from:

<syntaxhighlight lang="c">if (pCmdExt && pCmdExt->RxPayloadLen < 0 && pCmdExt->TxPayloadLen)</syntaxhighlight> to <syntaxhighlight lang="c">if (pCmdExt && pCmdExt->RxPayloadLen < 0)</syntaxhighlight>

This fix will enable the CW to function correctly. However, since the change applies directly to the Simplelink Host Driver and this change hasn't been tested throughly by TI, the potential side effect of this change is unknown.

If the application doesn't use CW mode, this change is not needed.

5 Missing packet ID while sending the data over UDP socket Iperf may recognize the packet as Out of Order. Modify "<cc3100-sdk>/examples/udp_socket/main.c" as per below:

@line 568 <syntaxhighlight lang="c">- _u16 LoopCount = 0; + _u32 LoopCount = 0;</syntaxhighlight>

@line 587 <syntaxhighlight lang="c">

   while (LoopCount < NO_OF_PACKETS)
   {

+ uBuf.BsdBuf[0] = LoopCount >> 24 & 0xFF; + uBuf.BsdBuf[1] = LoopCount >> 16 & 0xFF; + uBuf.BsdBuf[2] = LoopCount >> 8 & 0xFF; + uBuf.BsdBuf[3] = LoopCount & 0xFF;

       Status = sl_SendTo(SockID, uBuf.BsdBuf, BUF_SIZE, 0,
                              (SlSockAddr_t *)&Addr, AddrSize);
       if( Status <= 0 )
       {
           Status = sl_Close(SockID);
           ASSERT_ON_ERROR(BSD_UDP_CLIENT_FAILED);
       }
       LoopCount++;
   }</syntaxhighlight>
This fix is needed due to specific UDP packet format required by the Iperf.
More details @ http://e2e.ti.com/support/wireless_connectivity/f/968/p/401434/1429326#1429326

SDK 1.0.0 Known issues[edit]

E2e.jpg {{
  1. switchcategory:MultiCore=
  • For technical support on MultiCore devices, please post your questions in the C6000 MultiCore Forum
  • For questions related to the BIOS MultiCore SDK (MCSDK), please use the BIOS Forum

Please post only comments related to the article CC3100 Summary of Known Issues here.

Keystone=
  • For technical support on MultiCore devices, please post your questions in the C6000 MultiCore Forum
  • For questions related to the BIOS MultiCore SDK (MCSDK), please use the BIOS Forum

Please post only comments related to the article CC3100 Summary of Known Issues here.

C2000=For technical support on the C2000 please post your questions on The C2000 Forum. Please post only comments about the article CC3100 Summary of Known Issues here. DaVinci=For technical support on DaVincoplease post your questions on The DaVinci Forum. Please post only comments about the article CC3100 Summary of Known Issues here. MSP430=For technical support on MSP430 please post your questions on The MSP430 Forum. Please post only comments about the article CC3100 Summary of Known Issues here. OMAP35x=For technical support on OMAP please post your questions on The OMAP Forum. Please post only comments about the article CC3100 Summary of Known Issues here. OMAPL1=For technical support on OMAP please post your questions on The OMAP Forum. Please post only comments about the article CC3100 Summary of Known Issues here. MAVRK=For technical support on MAVRK please post your questions on The MAVRK Toolbox Forum. Please post only comments about the article CC3100 Summary of Known Issues here. For technical support please post your questions at http://e2e.ti.com. Please post only comments about the article CC3100 Summary of Known Issues here.

}}

Hyperlink blue.png Links

Amplifiers & Linear
Audio
Broadband RF/IF & Digital Radio
Clocks & Timers
Data Converters

DLP & MEMS
High-Reliability
Interface
Logic
Power Management

Processors

Switches & Multiplexers
Temperature Sensors & Control ICs
Wireless Connectivity

{{#switchcategory:MSP430=<McuHitboxFooter/>|C2000=<McuHitboxFooter/>|Stellaris=<McuHitboxFooter/>|TMS570=<McuHitboxFooter/>|MCU=<McuHitboxFooter/>|MAVRK=<MAVRKHitboxFooter/>|<HitboxFooter/>}}