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.

CC3301: CC3301 bring up

Part Number: CC3301
Other Parts Discussed in Thread: CC3350

Tool/software:

Hi WiFi team, 

Project Context

  • MCU: H5 ARM Cortex-M33
  • Wi-Fi Module: CC3301, on a module: BDE-BW3301AP1
  • Network Stack: NetX
  • Operating System: ThreadX
  • File System: FileX

Note: goal is to use a BDE module with CC3350. 

 

We are developing a firmware for a product using the CC3301 Wi-Fi module. The first hardware prototype (HW-V1) used an early version of the CC3301 silicon, along with the R3 driver. This setup was nearly stable with only minor issues.

 

After moving to a second hardware prototype (HW-V2) with a more recent version of the CC3301 silicon, multiple issues have been encountered depending on the driver version used:

 

HW-V2 with R3 Driver (legacy)

  • The same firmware used successfully on HW-V1 fails during binary upload on HW-V2.
  • The upload process stalls midway, preventing proper initialization of the CC3301.

 

HW-V2 with R5 Driver

  • Binary upload and boot sequence succeed.
  • The CC3301 operates initially but becomes unstable, crashing after some time.

 

HW-V2 with R7 Driver (latest, current)

  • Binary upload and boot sequence succeed.
  • However, the module crashes immediately after a Wi-Fi scan command is issued.

 

Summary of Current Status

  • HW-V1 (early silicon, R3): Nearly stable operation.
  • HW-V2 (updated silicon):
    • R3 driver: Upload fails.
    • R5 driver: Upload works, but system crashes after some runtime.
    • R7 driver: Upload works, but system crashes almost immediately (after scan).

 

Can you please provide some guidance on how to proceede? 

Thank you, 

Marinus