CC3100 does not answer anymore after update to 1.0.1.6-2.6.0.5 and SDK 1.2.0

It seems that it hangs in the following code:

    /*  2. Read 8 bytes (protocol aligned) - expected to be the sync pattern */
    NWP_IF_READ_CHECK(g_pCB->FD, &pBuf[0], 8);
    _SL_DBG_SYNC_LOG(SyncCnt,pBuf);

    /* read while first 4 bytes are different than last 4 bytes */
    while ( *(_u32 *)&pBuf[0] == *(_u32 *)&pBuf[4])
    {
    	 NWP_IF_READ_CHECK(g_pCB->FD, &pBuf[4], 4); // <--- loops endlessly here.
    }

hi Simon

I have exactly the same problem, do you have some more informations or solutions for this problem?

After updating to 1.0.1.6-2.6.0.5 and SDK 1.2.0, the first initialization steps works but after some configurations the initialization blocks.

sl_Start
sl_DevGet SL_DEVICE_GENERAL_VERSION
sl_WlanPolicySet 0
sl_WlanProfileDel
sl_WlanDisconnect -129
sl_NetCfgSet
sl_WlanPolicySet


Best regards
Sandro

Hi Sandro,

unfortunately not. I use SDK 1.1.0 for now which works ok (mostly...).

Sorry :(
Simon

Hi Simon

Thanks for your answer. Unfortunatelly i would like to implement the multi-threaded platform and this doesn't work with the sdk 1.1.0. So my hope was that it would work with the new sdk. but now i have much bigger issues.

Thank you.

Simon and  Sandro,

Are you seeing any error while programming the device?

Can you confirm you are working with production device?

BR,

Nir

Hi Simon

Just one more question. Do you have a custom board or are you using an evalboard?

Because i use an own custom board with a RTOS (eCos OS).

Hi Nir

No, there is no error occured. And yes, it is a production device, there is no evalboard.

We have formatted the device and installed the new service pack. Get Version gets pack the correct version number for the service pack.


There are more informations about my issue:

We're using a customboard with a RTOS(eCos OS) but in non-OS mode.

After updating the SDK and firmware for CC3100 to version 1.2.0 the initialization doesn’t work anymore and hangs after a few configuration steps. This issue is reproducible using the „getting_started_with_wlan_station“ example.

Below is the log output and spi communication from SDK 1.1.0 and 1.2.0.


The exactly same code is running without any problems with the old SDK (1.1.0). Here’s the log output and the SPI communication shown for the old SDK

www.dropbox.com/.../old sdk.png

>>>STARTING THE APPLICATION<<<
[INF @ 00:00:00.002] PowerOn: WiFi Power On
sl_Start
sl_DevGet SL_DEVICE_GENERAL_VERSION
sl_WlanPolicySet 0
sl_WlanProfileDel
sl_WlanDisconnect -129
sl_NetCfgSet
sl_WlanPolicySet
policy 0
sl_WlanSet
sl_WlanPolicySet
sl_NetAppMDNSUnRegisterService
sl_WlanRxFilterSet
sl_Stop
initializeAppVariables
Device is configured in default state
Device started as STATION
[INF @ 00:00:01.847] SimpleLinkWlanEventHandler: WiFi connected!
[INF @ 00:00:02.416] SimpleLinkNetAppEventHandler: IP Acquired!

After updating the SDK we get the following output and as you can see in the screenshot, the SPI communication stucks.

www.dropbox.com/.../new sdk.png

>>>STARTING THE APPLICATION<<<
[INF @ 00:00:00.002] PowerOn: WiFi Power On
sl_Start
sl_DevGet SL_DEVICE_GENERAL_VERSION
sl_WlanPolicySet 0
sl_WlanProfileDel
sl_WlanDisconnect -129
sl_NetCfgSet
sl_WlanPolicySet


During the second WlanPolicySet, the communication hangs and the initialization process is blocked. Is it possible that something is wrong with the SPI communication, because SPI CLK does not appear and so the communication is blocked.

Hi Nir, Sandro,

Yes I have a custom board running on FreeRTOS.

Our CC3100 devices are production devices.

Regards
Simon

Are you using SPI Little Endian or Big Endian?

I'm sending Big Endian. (MSB)

Hi Burn,

We have reporting on an issue with Big Endian and wlanSet command in the last formal release. you can see it in the release notes.
We are planning to provide a Beta version with a fix - the date hasn't been set yet.

processors.wiki.ti.com/.../CC31xx_Release_Notes

ID MCS00135767 - sl_WlanSet is not working on Big Endian systems
The command is not working well on Big Endian systems and will return an error. The command is used to set Tx power, Scan parameters,
regulatory domain.


BR,
Nir

Hi Nir

Unfortunatelly we do not call wlanSet at this moment, where the configuration crashes. We're using the example "getting_started_with_wlan_station" and the command sl_WlanPolicySet is blocking the connection.
But anyways, we are trying to set the communication to little endian to get sure this issue is not influence the other commands.

BR

Hi Nir

Our host CPU is little endian (STM32F4) - so your reported issue might not the one we're currently facing. Any chance to get access to the upcoming beta SDK to be sure?

Hi Michael,

I didn't see any post from you - which issue you are referring to?

BR,
Nir

I do have exactly the same error as Sandro - you wrote him that there is a known issue "ID MCS00135767 - sl_WlanSet is not working on Big Endian systems". however I run my code on a STM32F4 which runs Little Endian.

please provide details and more information on your issue.

We're using the example "getting_started_with_wlan_station" and the command sl_WlanPolicySet is blocking the connection.

happens after updating SDK to v1.2.0. Using CC3100. Let me know if you need more details.

Michael,


Can you read the FW version?
If you remark the sl_WlanPolicySet does everything work for you?
What do you mean by Blocking the connection? which of the policy set is it?

BR,
Nir