• State TI Thinks Resolved
  • Locked Locked
  • Replies 6 replies
  • Answers 1 answer
  • Subscribers 40 subscribers
  • Views 360 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

CC3300: CC330 WIFI ONLY, AM625, TI-SDK10

John Tobias
Intellectual 325 points
Part Number: CC3300
Other Parts Discussed in Thread: AM625,

Tool/software:

Hi,

We have a CC3300 chip (Wifi only) in our custom board AM625 and it is running the latest TI SDK10

The linux able to bring-up the wlan0 interface during boot

[ 19.235492] wlan_ap.sh: checking wlan ap status
[ 19.281577] wlan_ap.sh: configuring wlan ap
[ 19.338906] config_wlan_ap.sh: setting PSK to private token
[ 19.353343] config_wlan_ap.sh: creating hostapd.conf config file
[ 19.379539] config_wlan_ap.sh: setting PSK key
[ 19.430764] wlan_ap.sh: running enable_wlan_ap.sh
[ 19.464120] enable_wlan_ap.sh: running hostapd
[ 19.641114] enable_wlan_ap.sh: adding wlan0 to bridge0
[ 19.658868] bridge0: port 1(wlan0) entered blocking state
[ 19.664486] bridge0: port 1(wlan0) entered disabled state
[ 19.670868] cc33xx_driver cc33xx.4.auto wlan0: entered allmulticast mode
[ 19.679906] cc33xx_driver cc33xx.4.auto wlan0: entered promiscuous mode
[ 19.691074] bridge0: port 1(wlan0) entered blocking state
[ 19.696549] bridge0: port 1(wlan0) entered forwarding state

Then, after few minutes or hours I've seen an error in the logs:

[ 546.674437] cc33xx: ERROR FW is stuck, triggering recovery
[ 546.679972] cc33xx: CC33xx driver attempting recovery
[ 548.907602] ieee80211 phy1: Hardware restart was requested
[ 750.219200] cc33xx: ERROR FW is stuck, triggering recovery
[ 750.224724] cc33xx: CC33xx driver attempting recovery
[ 752.459579] ieee80211 phy1: Hardware restart was requested
[ 1376.637666] cc33xx: ERROR FW is stuck, triggering recovery
[ 1376.643188] cc33xx: CC33xx driver attempting recovery
[ 1378.891581] ieee80211 phy1: Hardware restart was requested
[ 1586.351111] cc33xx: ERROR FW is stuck, triggering recovery
[ 1586.356633] cc33xx: CC33xx driver attempting recovery

Using the wireshark, I captured the wifi debug and saw this error:



I attached is the wireshark logs

wifi-logs.zip

We don't know if this is a configuration issue or firmware issue and we need your help to fix the issue.

Regards,

John

  • 0
    TI__Mastermind 31350 points

    Hi John,

    This is a known issue with the PSDK 10. Currently we have very outdated driver and firmware in the PSDK 10.In order to resolve this we will have to update both the driver and firmware from 1.0.0.6 CC33xx SDK. 

    Can you let me know what your time line is so that I can have some time to make ports to PSDK 10 (kernel 6.6)? 

  • 0 in reply to Sabeeh Khan1
    Intellectual 325 points

    Hi Sabeeh,

    According to my boss, we need it ASAP like a week from now.

    Regards,

    John

  • 0 in reply to John Tobias
    TI__Mastermind 31350 points

    Hi John,

    Sorry for the delay. I have patch available for updating the PSDK 10 to recently released 1.0.0.7 firmware package. Please pull the firmware and utilities from CC33xx SDK 1.0.0.7.

    https://e2e.ti.com/cfs-file/__key/communityserver-discussions-components-files/968/0001_2D00_drivers_2D00_cc33xx_2D00_update_2D00_to_2D00_1.0.0.7.patch

  • 0 in reply to Sabeeh Khan1
    Intellectual 325 points

    Hi Sabeeh,

    Thanks. I will try it today.

    Regards,

    John

  • 0 in reply to John Tobias
    Intellectual 325 points

    Hi Sabeeh,

    We are using yocto to build our image and the current cc33xx-fw_git.bb script is not recent as well as the https://git.ti.com/git/cc33xx-wlan/cc33xx-fw - the latest firmware is not there.

    I'd like to know the timeline when you guys will update the yocto recipes for the latest cc33xx support?

    Regards,

    John

  • 0 in reply to John Tobias
    TI__Mastermind 31350 points

    Hi John,

    The primary intention of that repository was for initial Yocto integration. Customers should take the drivers and firmware from the CC33xx SDK that corresponds to the same driver.

    We are currently working on upstreaming the CC33xx driver. Once the driver is accepted, the cc33xx-fw repo will likely be dropped in support of the larger, more supported linux-firmware repository. We don't have a plan to update the current driver in ti-linux-kernel -6.6.y, for example, until the mainline driver is accepted.

    So until then, TI will likely have to create patches for customers on various kernel versions; which is why I provided the patch above.