Other Parts Discussed in Thread: AM623
Tool/software:
In our custom design we are using cc3301 with AM623.
- Interface used is SDIO and UART (for BLE)
- using SDIO in-band interrupt.
- cc33xx software version used is Version: 1.0.0.8
- Part Number: CC3301
- device tree details added below
main_uart6 {
status = "okay";
pinctrl-names = "default";
pinctrl-0 = <&wifible_pins_default>;
bluetooth {
compatible = "ti,cc33xx-bt";
cc33xx-supply = <&wlan_en>;
max-speed = <115200>;
};
};
&sdhci2 {
status = "okay";
vmmc-supply = <&wlan_en>;
pinctrl-names = "default";
pinctrl-0 = <&main_mmc2_wifi_pins_default>;
bus-width = <4>;
non-removable;
ti,fails-without-test-cd;
cap-power-off-card;
keep-power-in-suspend;
#address-cells = <1>;
#size-cells = <0>;
wlcore: wlcore@2 {
compatible = "ti,cc33xx";
reg = <2>;
};
};
But we are getting following error message some times
[20246.283982] wlcore: ERROR FW is stuck, triggering recovery
[20246.302320] wlcore: Recovery work
[20246.309141] wlcore: Turning off
[20246.311516] btti serial0-0: SM: Got EVENT_REGULATOR_DISABLE, moving from STATE_HW_READY to STATE_HW_OFF
[20246.833920] wlcore: Chip wakeup
[20246.862339] btti serial0-0: SM: Got EVENT_REGULATOR_ENABLE, moving from STATE_HW_OFF to STATE_HW_ON
[20247.125956] wlcore: Set BLKsize to 128
[20247.126176] wlcore: BOOT IRQs: 0x8
[20247.146115] wlcore: Reading control info
[20247.146198] wlcore: Processing message type 2, len 704
[20247.146225] wlcore: Response len 704, allocated buffer len 712
[20247.146235] wlcore: CMD# 35, len=712
[20247.146242] wlcore: CC33XX device info: PG version: 2, Metal version: 1, Boot ROM version: 1, M3 ROM version: 1, MAC address: 0xf8fb9017f202, Device part number: 0
[20247.146256] wlcore: Downloading ti-connectivity/cc33xx_2nd_loader.bin to device
[20247.149394] wlcore: Reading control info
[20247.149479] wlcore: Processing message type 2, len 4
[20247.150510] wlcore: Reading control info
[20247.150591] wlcore: Processing message type 2, len 4
[20247.151256] wlcore: Reading control info
[20247.151329] wlcore: Processing message type 2, len 4
what is the reason behind this error? once it occur the hci0 interface will disappear and we can't able to use Bluetooth.
