This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

CC3120MOD: How to detect the formatting process in progress after Direct SPI Programming

Part Number: CC3120MOD
Other Parts Discussed in Thread: CC3120

Hi, TI experts,

My customer is developing with CC3120MOD.

They would like to know how to detect the formatting process in progress after Direct SPI Programming.

Because they want to not be able to power off during the formatting process.

They are running Direct SPI Programming from the host MCU.

The circuit design has already been completed and it is not possible to change to UART Programming.

Would you please give me some advice ?

Best Regards,
Yojiro

  • Hi Yojiro,

    Is the customer loading a gang image over the external SPI flash interface? Are you talking about the formatting that occurs during the device's first boot?

    Best regards,

    Sarah

  • Hi, Sarah-san,

    Sarah P said:
    Is the customer loading a gang image over the external SPI flash interface? Are you talking about the formatting that occurs during the device's first boot?

    Yes, they are using the external SPI flash interface when loading a gang image.

    They are asking about the first boot.

    Thank you.

    Best Regards,

    Yojiro

  • Hi Yojiro,

    The CC3120MOD has timing requirements for the first boot that are explained in section 8.12.1 Power-Up Sequencing of the datasheet: https://www.ti.com/lit/swrs205. The formatting that is part of unpacking the gang image occurs during the FW init (T3).

    Best regards,

    Sarah

  • Hi, Sarah-san,

    We received comments from our customer.

    After writing the flash with the External SPI Interface, they waited at least T3 (1.35 seconds) after turning on the power, and then executed sl_Start and sl_DeviceGet to get the version.
    They say that on the first boot after writing, sl_Start will be successful immediately, but it will take more than 10 seconds for sl_DeviceGet to respond. From the second time onwards, sl_DeviceGet will respond immediately.
    If it is started for the first time after writing the flash with the External SPI Interface, is the CC3120 finished with all the processing related to writing the service pack?

    Could you confirm it ?

    Best Regards,

    Yane

  • Hi Yane,

    What servicepack version is flashed to the CC3120MOD? What host driver version?

    Best regards,

    Sarah

  • Hi, Sarah-san,

    They are using the following versions:
    - Service Pack : sp_3.16.0.1_2.0.0.0_2.2.0.7
    - Host driver : 4.20.00.10

    There seems to be no version dependency on the first boot time after flash writing.

    Best Regards,

    Yane

  • Hi Yane,

    A delay on sl_DeviceGet() is not related to the flashing procedure. By the time sl_Start() completes, the filesystem is already created.

    Can your customer capture NWP logs and use a logic analyzer to capture their host interface?

    Best regards,

    Sarah

  • Hi, Sarah-san,

    They can not capture NWP logs.

    I'm sorry to give you incorrect information.

    Their procedure when powering on the module is as follows:
    1. Operate nRESET and nHIB according to section 8.12.1 Power-Up Sequencing of the data sheet.
    2. Wait 2 seconds and then call sl_Start.
    3. When sl_Start finishes normally, call sl_DeviceGet to read the version.

    At the first startup after writing the service pack, it takes about 10 seconds for sl_Start to finish normally.
    There is no problem with the operation after sl_Start ends normally.

    Is it okay to call sl_Start at the above timing after writing the service pack?

    Thank you.

    Best Regards,
    Yane

  • Hi Yane,

    There is no issue delaying calling sl_Start, but I'm concerned that sl_Start takes so long to return. Why are they not able to capture NWP logs? Can they capture the communication between the CC3120MOD and the host MCU using a logic analyzer?

    Best regards,

    Sarah