LAUNCHXL-F28P65X: LAUNCHXL-F28P65X

Hello Arun,

Thank you for the in-depth explanation of the issue.

A few clarifying questions to ensure everything is connected properly:

1. What is the state of GPIO42 (CC3135 nHIB) ? Per the UG of CC3135, this pin must not be left floating. Refer to Figure 9-7. CC3135 Engine Area on page 59. 
   1. 
      
      
2. What is the implementation in the code of GPIO57 (CC3135 IRQ) ? I am more familiar with the F28P65x side of things, so I am uncertain whether a pending interrupt from the CC3135 could block attempted write commands to the peripheral device.
   
   

Regards,
Jason Osborn

NOTE: As a side note which is not necessarily relevant to your problem, but may be useful, it is also possible to avoid the requirement to manually adjust the CS pin by utilizing SPIA_PTE. Because SPIA_PTE is not routed to GPIO84 by default, this would require a bit of side routing.

1. Route SPIA_PTE to the CLB
2. Route CLB to Output XBAR
3. Route Output XBAR to GPIO84

Hi Jason,

Thank you for your reply, We checked the state of GPIO42 (CC3135 nHIB) is high, and GPIO57 also we have configured in the code and sending the AT command over the SPI and trying to get communicate with the WiFi module and waiting for the response but no response from the Wi-Fi module.

Thanks,

Arun,

Thank you for confirming. Do you have a signal analyzer you can use to monitor the SPI data lines to verify that data is being sent properly? If not, are you able to test one of the C2000 SPI loopback examples available in {C2000Ware_Install}/driverlib/f28p65x/examples/c28x/spi/ ?

While you look into this, I will also look further into the CC3135 side of things.

Regards,
Jason Osborn

Hello Jason,

Arun and me working on same project.

Thanks for the response, We tested SPI loopback example using SPIA as peripheral and SPID as controller with C2000 and it is working fine.

If we search for the CC3135 SDK, then we found "SIMPLELINK-SDK-WIFI-PLUGIN" sdk, we installed it and found this installed in "C:/ti/" folder.
We are imported SPI project from "{C2000Ware_Install}/driverlib/f28p65x/examples/c28x/spi/" for C2000(F28P65x), in this we initalized the SPIA with GPIO pin 16(PICO), 17(POCI), 18(CLC). For CC3135, copied the simplelink.h file from "C:\ti\simplelink_sdk_wifi_plugin_4_20_00_10\source\ti\drivers\net\wifi" to our C2000 project path and include other necessary header files.

But in this we are not found "C:\ti\simplelink_sdk_wifi_plugin_4_20_00_10\source\ti\drivers" folder, from this some header files are included in other C files of the simplelinks header and source files.

More information, in {C2000Ware_Install} we not found the source folder.
So, are we following the right track? How we can use CC3135 wifi module with C2000(F28P65x) via SPI? 

Thanks Jason for reply, I also want to clarify and confirm, Does CC3135 module support AT commands for UART or SPI is used? If not what are the ways to communicate with CC3135 module. In our case we are trying with AT commands.

Regards,
Arun S

Arun,

Thank you for confirming the SPI loopback test is functional.

For the CC3135, a few things:

1. Refer to the following e2e thread re: CC3135 AT commands https://e2e.ti.com/support/wireless-connectivity/wi-fi-group/wifi/f/wi-fi-forum/867197/cc3135mod-at-commands-over-spi
   1. Essentially, no, the CC3135 utilizes a TI proprietary protocol, NOT AT commands. However, the thread suggests an alternative device which does support AT commands and how to use them with SPI.
      
      
2. As described in the SIMPLELINK-SDK-WIFI-PLUGIN product page, it is a plugin designed to work along with other device-specific SimpleLink SDKs. If the expected SDKs are not available, the projects will not work as expected.
   
   
3. I reached out to a CC3135 expert, and they confirmed that the proprietary comms protocol for the CC3135 has NOT been ported to support the C28x core, meaning that it may not currently be possible to utilize the CC3135 and the LAUNCHXL-F28P65x together. I'm still looking into what effort may be required to do that.

Regards,
Jason Osborn

Thanks Jason for your reply, Is TI team can support us in this issue Our team stuck at this moment need urgent support on this.

Regards,
Arun S

Apologies for the delay in response, I'm reaching out internally.

Regards,
Jason Osborn

Jason,

Is there any update on this?

We are porting the SimpleLink Wi-Fi SDK to C2000. We have added the header and source files and made some progress after resolving several errors and warnings.

We have completed the following steps:
1. Copied the source/ folder from the SimpleLink Wi-Fi SDK to the C2000Ware SDK.
2. Included 'simplelink.h' and 'slnetifwifi.h', resolving some errors.
3. Added mutex and semaphore files from the SimpleLink_CC32xx SDK.
4. Currently, we are facing a conflict with two 'device.c' files and are unable to add them.

There are a total of 28 errors related to '_sldevice', '_slsocket', and more.

Please help us resolve this issue.

Regards,
Omkar

Omkar,

Apologies for the delays in response. The person you need for this particular problem is currently on PTO, and I've been waiting for them to get back. It's my understanding they should be back next week.

I can provide some more general guidance, though. Device.c files are effectively intended to control the system parameters of the C2000 MCU, so only 1 device.c file should be present. If 2 device.c files appear to be required, include only one of them, and determine what each of them has and why to evaluate whether you need to merge any code from the two files.

Apologies again,
Jason Osborn

Jason,

I have renamed SimpleLink device.c with other name, and copied this file in Project location. After that there are few minor errors we resolved but still there were all errors which I have mentioned in previous message.

Please let us know once the team will back and we need urgent help in this. If anyone from TI can look in to personally.

Thanks,
Omkar