CC3100MOD: Filesystem and UniFlash programming error

Thomas Thomas1

Part Number: CC3100MOD
Other Parts Discussed in Thread: UNIFLASH, CC3100, CC3200, , TPS54336A

Hi,

My customer recently received quite a number of RMA for their CC3100MOD-based product.
It is found that while calling sl_WlanPolicySet( ... ), the SimpleLinkGeneralEventHandler( ) return the following 2 errors:

pDevEvent->Event=1，
pDevEvent->EventData.deviceEvent.status=-77，( SL_ERROR_FS_FILE_TABLE_LOAD_FAILED )
pDevEvent->EventData.deviceEvent.sender=6

pDevEvent->Event=1，
pDevEvent->EventData.deviceEvent.status=-78，( SL_ERROR_PREFERRED_NETWORKS_FILE_LOAD_FAILED )
pDevEvent->EventData.deviceEvent.sender=2

While using UNIFlash to re-format and program the device, UNIFlash gives the Flash erase error as shown in the UNIFlash log below.

Please advise what could be the possible cause of error? Note that all these failure devices were working perfectly before.

UNIFlash log:

[18:55:07] Begin Format operation.
[18:55:08] INFO: > Executing Operation: Connect
[18:55:08] DEBUG: waiting and clearing uart rx buffer
[18:55:10] INFO: setting break signal
[18:55:10] DEBUG: wait for ack
[18:55:11] DEBUG: UART timeout
[18:55:11] DEBUG: --- COM Port timeout on ACK read
[18:55:11] INFO: detecting FTDI for device reset
[18:55:11] DEBUG: got 0 devices connected
[18:55:11] ERROR: No device USB ports were found
[18:55:11] INFO: --- please restart the device ---
[18:55:11] DEBUG: wait for ack
[18:55:12] INFO: connection succeeded
[18:55:12] INFO: getting storage list
[18:55:12] DEBUG: wait for ack
[18:55:12] INFO: > Executing Operation: Init
[18:55:12] INFO: reading version info
[18:55:12] DEBUG: wait for ack
[18:55:12] INFO: DEVICE CC3100 ES1.33
[18:55:12] INFO: reading version info
[18:55:12] DEBUG: wait for ack
[18:55:12] DEBUG: Bootloader version is 2, 0, 4, 0
[18:55:12] DEBUG: raw storage write
[18:55:12] DEBUG: wait for ack
[18:55:12] DEBUG: status request
[18:55:12] DEBUG: wait for ack
[18:55:12] DEBUG: BlockSize is 4096, number of blocks is 16
[18:55:12] DEBUG: erasing 13 blocks starting from 0
[18:55:13] DEBUG: wait for ack
[18:55:13] DEBUG: status request
[18:55:13] DEBUG: wait for ack
[18:55:13] DEBUG: wait for ack
[18:55:13] DEBUG: status request
[18:55:13] DEBUG: wait for ack
[18:55:13] DEBUG: wait for ack
[18:55:13] DEBUG: status request
[18:55:13] DEBUG: wait for ack
[18:55:13] DEBUG: wait for ack
[18:55:13] DEBUG: status request
[18:55:13] DEBUG: wait for ack
[18:55:13] DEBUG: wait for ack
[18:55:13] DEBUG: status request
[18:55:13] DEBUG: wait for ack
[18:55:13] DEBUG: wait for ack
[18:55:13] DEBUG: status request
[18:55:13] DEBUG: wait for ack
[18:55:13] DEBUG: wait for ack
[18:55:13] DEBUG: status request
[18:55:13] DEBUG: wait for ack
[18:55:13] DEBUG: wait for ack
[18:55:13] DEBUG: status request
[18:55:13] DEBUG: wait for ack
[18:55:13] DEBUG: wait for ack
[18:55:13] DEBUG: status request
[18:55:13] DEBUG: wait for ack
[18:55:13] DEBUG: wait for ack
[18:55:13] DEBUG: status request
[18:55:13] DEBUG: wait for ack
[18:55:13] DEBUG: wait for ack
[18:55:13] DEBUG: status request
[18:55:13] DEBUG: wait for ack
[18:55:13] DEBUG: wait for ack
[18:55:13] DEBUG: status request
[18:55:13] DEBUG: wait for ack
[18:55:14] DEBUG: wait for ack
[18:55:14] DEBUG: status request
[18:55:14] DEBUG: wait for ack
[18:55:14] DEBUG: wait for ack
[18:55:14] DEBUG: status request
[18:55:14] DEBUG: wait for ack
[18:55:14] DEBUG: status request
[18:55:14] DEBUG: wait for ack
[18:55:14] DEBUG: 0
[18:55:14] DEBUG: wait for ack
[18:55:14] DEBUG: wait for ack
[18:55:14] INFO: > Executing Operation: Format
[18:55:14] INFO: Erase storage SFLASH
[18:55:14] DEBUG: wait for ack
[18:55:20] DEBUG: status request
[18:55:20] DEBUG: wait for ack
[18:55:20] DEBUG: Error 74 : Fail
[18:55:20] INFO: erase storage failed
[18:55:20] INFO: erase storage completed
[18:55:20] INFO: > Executing Operation: Disconnect
[18:55:20] DEBUG: disconnecting from device . . .
[18:55:20] DEBUG: wait for ack
[18:55:20] Operation Format returned.
[18:56:09] Begin ServicePackProgramming operation.
[18:56:09] INFO: > Executing Operation: Connect
[18:56:09] DEBUG: waiting and clearing uart rx buffer
[18:56:11] INFO: setting break signal
[18:56:11] DEBUG: wait for ack
[18:56:12] DEBUG: UART timeout
[18:56:12] DEBUG: --- COM Port timeout on ACK read
[18:56:12] INFO: detecting FTDI for device reset
[18:56:12] DEBUG: got 0 devices connected
[18:56:12] ERROR: No device USB ports were found
[18:56:12] INFO: --- please restart the device ---
[18:56:12] DEBUG: wait for ack
[18:56:13] INFO: connection succeeded
[18:56:13] INFO: getting storage list
[18:56:14] DEBUG: wait for ack
[18:56:14] INFO: > Executing Operation: ServicePackProgramming
[18:56:14] INFO: Path to the service pack file: D:/ti/CC3100_CC3200_ServicePack_1.0.1.11-2.9.0.0/servicepack_1.0.1.11-2.9.0.0.bin
[18:56:14] INFO: reading version info
[18:56:14] DEBUG: wait for ack
[18:56:14] INFO: CC3100R Device detected.
[18:56:14] INFO: NWP/MAC/PHY Version from Service Pack:
[18:56:14] INFO: NWP Patch version: 2.8.99.0
[18:56:14] INFO: MAC Patch version: 1.4.0.1
[18:56:14] INFO: PHY Patch version: 1.0.3.37
[18:56:14] INFO: reading version info
[18:56:14] DEBUG: wait for ack
[18:56:14] INFO: DEVICE CC3100 ES1.33
[18:56:14] INFO: reading version info
[18:56:14] DEBUG: wait for ack
[18:56:14] DEBUG: Bootloader version is 2, 0, 4, 0
[18:56:14] DEBUG: raw storage write
[18:56:14] DEBUG: wait for ack
[18:56:14] DEBUG: status request
[18:56:14] DEBUG: wait for ack
[18:56:14] DEBUG: BlockSize is 4096, number of blocks is 16
[18:56:14] DEBUG: erasing 13 blocks starting from 0
[18:56:14] DEBUG: wait for ack
[18:56:14] DEBUG: status request
[18:56:14] DEBUG: wait for ack
[18:56:14] DEBUG: wait for ack
[18:56:14] DEBUG: status request
[18:56:14] DEBUG: wait for ack
[18:56:14] DEBUG: wait for ack
[18:56:14] DEBUG: status request
[18:56:14] DEBUG: wait for ack
[18:56:14] DEBUG: wait for ack
[18:56:14] DEBUG: status request
[18:56:14] DEBUG: wait for ack
[18:56:14] DEBUG: wait for ack
[18:56:14] DEBUG: status request
[18:56:14] DEBUG: wait for ack
[18:56:14] DEBUG: wait for ack
[18:56:14] DEBUG: status request
[18:56:15] DEBUG: wait for ack
[18:56:15] DEBUG: wait for ack
[18:56:15] DEBUG: status request
[18:56:15] DEBUG: wait for ack
[18:56:15] DEBUG: wait for ack
[18:56:15] DEBUG: status request
[18:56:15] DEBUG: wait for ack
[18:56:15] DEBUG: wait for ack
[18:56:15] DEBUG: status request
[18:56:15] DEBUG: wait for ack
[18:56:15] DEBUG: wait for ack
[18:56:15] DEBUG: status request
[18:56:15] DEBUG: wait for ack
[18:56:15] DEBUG: wait for ack
[18:56:15] DEBUG: status request
[18:56:15] DEBUG: wait for ack
[18:56:15] DEBUG: wait for ack
[18:56:15] DEBUG: status request
[18:56:15] DEBUG: wait for ack
[18:56:15] DEBUG: wait for ack
[18:56:15] DEBUG: status request
[18:56:15] DEBUG: wait for ack
[18:56:15] DEBUG: wait for ack
[18:56:15] DEBUG: status request
[18:56:15] DEBUG: wait for ack
[18:56:15] DEBUG: status request
[18:56:15] DEBUG: wait for ack
[18:56:15] DEBUG: 0
[18:56:15] DEBUG: wait for ack
[18:56:16] DEBUG: wait for ack
[18:56:16] INFO: Downloading file "/sys/servicepack.ucf" with size 31348
[18:56:16] DEBUG: sending start download command
[18:56:16] DEBUG: Granularity conversion: G(1024) * N(128) = 131072
[18:56:16] DEBUG: Access code is 3
[18:56:16] DEBUG: wait for ack/nack
[18:56:16] DEBUG: receive nack
[18:56:16] ERROR: Open operation failed
[18:56:16] DEBUG: status request
[18:56:16] DEBUG: wait for ack
[18:56:16] DEBUG: Error 66 : Invalid command
[18:56:16] INFO: > Executing Operation: Disconnect
[18:56:16] DEBUG: disconnecting from device . . .
[18:56:16] DEBUG: wait for ack
[18:56:16] Operation ServicePackProgramming returned.

- Thomas

over 8 years ago

0 Vincent Rodriguez over 8 years ago

TI__Mastermind 28285 points

Hey Thomas,

When you are selecting your service pack, are you using the .bin or the .ucf file?

Thanks,

Vince Rodriguez

0 Thomas Thomas1 over 8 years ago in reply to Vincent Rodriguez

Prodigy 170 points

Hello Vince,

It's confirmed the customer was using the bin file. And you can see that from Uniflash log:

[18:56:14] INFO: > Executing Operation: ServicePackProgramming
[18:56:14] INFO: Path to the service pack file: D:/ti/CC3100_CC3200_ServicePack_1.0.1.11-2.9.0.0/servicepack_1.0.1.11-2.9.0.0.bin

In fact, the format operation at the beginning already gave errors:

[18:55:14] INFO: > Executing Operation: Format
[18:55:14] INFO: Erase storage SFLASH
[18:55:14] DEBUG: wait for ack
[18:55:20] DEBUG: status request
[18:55:20] DEBUG: wait for ack
[18:55:20] DEBUG: Error 74 : Fail
[18:55:20] INFO: erase storage failed
[18:55:20] INFO: erase storage completed

- Thomas

0 Shlomi Itzhak over 8 years ago in reply to Thomas Thomas1

TI__Guru 64475 points

Hello Vincent,

From the logs it seems that you can connect to the device over UART but the network processor is unable to communicate with the serial flash.

Are you using the CC3100 module as you mentioned on the thread (meaning the serial flash is on the module)?

Did it work before or is it brand new?

have you soldered it on your PCB or are you working on TI's Boosterpack?

Regards,

Shlomi

0 Thomas Thomas1 over 8 years ago in reply to Shlomi Itzhak

Prodigy 170 points

Hello Shlomi,

The customer is using the CC3100MOD module with built in serial Flash.

The module work well previously on the field.

It was mounted on a customer board, not the boosterpack.

- Thomas

0 Shlomi Itzhak over 8 years ago in reply to Thomas Thomas1

TI__Guru 64475 points

Hello Thomas,

Since it is a module, all passive components (capcitors, inductors), slow clock, serial flash are internal.

So it seems like the module got broken for some reason but I will let an hardware engineer verify it.

Shlomi

0 Charles Oladimeji over 8 years ago in reply to Shlomi Itzhak

TI__Mastermind 33805 points

Hi,

What is the operating environment and voltage during normal operation in the field?

Regards,

Charles O

0 Thomas Thomas1 over 8 years ago in reply to Charles Oladimeji

Prodigy 170 points

Hi Charles,

Customer has confirmed the modules were used in in-door environment. Temperature will not exceed 50 degC, and the supply voltage is stable at 3.3V provided by TPS54336A.

- Thomas

0 Charles Oladimeji over 8 years ago in reply to Thomas Thomas1

TI__Mastermind 33805 points

Hi,

Seems like the SFlash got corrupted.

Was there any reprogramming or software updates prior to failures?

Regards.

Charles

0 Thomas Thomas1 over 8 years ago in reply to Charles Oladimeji

Prodigy 170 points

Hi,
There was no reprogramming nor update prior to failures.
We had help customer submit the failure samples for FA.
Thanks for your support.

- Thomas

0 Vincent Rodriguez over 8 years ago in reply to Thomas Thomas1

TI__Mastermind 28285 points

Thomas,

I'm going to close this thread. Please open a new thread if you have any more questions.

Regards,

Vince Rodriguez

Wi-Fi

Wi-Fi forum

CC3100MOD: Filesystem and UniFlash programming error