CC3100MOD: Error in Lab_cc3100 example.

i'm not sure what is lab20 for cc3100. Can you share a link?

-100 means that the NWP got an abort().

Can you provide the NWP  log? (/cfs-file/__key/communityserver-discussions-components-files/968/CC3100-_2600_-CC3200-Capture-NWP-Logs-_2D00_-Texas-Instruments-Wiki.pdf)  

Please check if you are getting any of the simplelink async event prior to the abort and check the sequence within configureSimpleLinkToDefaultState  to see which call actually returned the -100.

Hi Kobi.

Here's the log file from customer:

���������������������������������������������������������������������������

Thanks and Regards,

Nick

The file is empty. Please double check the capturing instructions.

and please provide more details on the use case as I'm not familiar with lab20.

Hi Kobi,

Customer can't find the file, can you provide the specific folder path?

Thanks and Regards,

Nick

it can be called from anywhere (add it to the main thread with all the other peripherals init).

He will to include the following headers:

#include <ti/devices/cc32xx/inc/hw_types.h>
#include <ti/devices/cc32xx/driverlib/rom_map.h>
#include <ti/devices/cc32xx/driverlib/pin.h>
#include <ti/devices/cc32xx/driverlib/prcm.h>

Hi Kobi,

Customer is using CC3100mod and the code below should be added to Uart.c or Uart.h?

Thanks and Regards,

Nick

if you are using CC3100 - you don't need this. It is only for the MCU devices to mux the output lines.

Hi Kobi,

There are always garbled characters in the binary log recorded by teraterm, so customer changed a serial port tool, but only recorded the hex log.

SaveWindows2023_3_21_10-51-26.TXT

Thanks and Regards,

Nick

Hi Nick,

Nop, NWP log is still not correct.

Can your customer provide drawing (schematic of connection of MSP432 + CC3100 and where is UART pin for NWP log connected).

Have your customer done porting of host driver from TM4C chip to MSP432P? Because CC3100 SDK does not support MSP432P by default. Some porting effort may to be needed. If your customer want to use MSP432, it is common way go to CC3120 or CC3135 which are supported via SDK plugin.

What I know from previous experiences there is many reasons for error -100, common are:

• not properly ported host driver
• usage of CC3100 / CC3200 device without uploaded service pack (especially when preproduction silicone is used)

I think your customer should:

1. If is is possible, move to CC3120 (CC3120MOD or BOOSTXL-CC3120MOD)
2. If not, review its hardware connection between MSP432P4 and CC3100
3. Make sure that host driver is properly ported for MSP432 (see driver architecture at SWRU368c appendix A)
4. Make sure that latest SDK with latest ServicePack are used

btw ... lab20 means this, I think.

Jan

The provided log is not valid and can't be parsed.

Not sure what are the "garbled characters" but the may be needed.

Hi Jan，

The lab20 link you given is the project customer is working on.

Thanks and Regards,

Nick

As Jan mentioned, it is not clear how the lab expects to use MSP432 with CC3100.

Since we don't have native support for this host, it requires porting and if this is a new project then CC3120 is the the recommended device to use.