Part Number: CC3301MOD
Other Parts Discussed in Thread: CC3301
Hi,
We are trying to bring up the CC3301MODENIAMOZR module with a custom AM6234 board. There is a pull-up resistor on the nReset pin of the CC33xx, and presently, the slow_clk_in is not mounted, while all power pins are enabled by default at boot time. I seen Host_IRQ_WL line is high with in 2 second of power.
Earlier, without explicitly asserting the nReset pin, we were able to load the firmware and use Wi-Fi. Now, we are trying to handle the nReset pin going low for around 20 ms, but we have started getting errors like :
cc33xx_sdio mmc2:0001:2: Using SDIO in-band IRQ
cc33xx_driver cc33xx.4.auto: firmware: direct-loading firmware ti-connectivity/cc33xx-nvs.bin
cc33xx_driver cc33xx.4.auto: firmware: direct-loading firmware ti-connectivity/cc33xx-conf.bin
cc33xx: asserting nRESET for 20 ms
cc33xx: deasserted nRESET
cc33xx_driver cc33xx.4.auto: firmware: direct-loading firmware ti-connectivity/cc33xx_2nd_loader.bin
cc33xx: ERROR boot IRQ timeout
cc33xx: ERROR ti-connectivity/cc33xx_2nd_loader.bin boot signal timeout
cc33xx: ERROR FW download failed
first tried to add reset logic at different function like "cc33xx_sdio_power_on",
then added at cc33xx_probe beore nvs firmware load, still getting same error
cc33xx_sdio mmc2:0001:2: Using SDIO in-band IRQ
cc33xx: asserting nRESET for 20 ms
cc33xx: deasserted nRESET
cc33xx_driver cc33xx.4.auto: firmware: direct-loading firmware ti-connectivity/cc33xx-nvs.bin
cc33xx_driver cc33xx.4.auto: firmware: direct-loading firmware ti-connectivity/cc33xx-conf.bin
cc33xx_driver cc33xx.4.auto: firmware: direct-loading firmware ti-connectivity/cc33xx_2nd_loader.bin
cc33xx: ERROR boot IRQ timeout
cc33xx: ERROR ti-connectivity/cc33xx_2nd_loader.bin boot signal timeout
cc33xx: ERROR FW download failed
dts for reference
&sdhci2 {
status = "okay";
vmmc-supply = <&vcc_3v3_sys>;
pinctrl-names = "default";
pinctrl-0 = <&main_mmc2_pins_default>;
bus-width = <4>;
non-removable;
ti,fails-without-test-cd;
cap-power-off-card;
keep-power-in-suspend;
ti,driver-strength-ohm = <50>;
assigned-clocks = <&k3_clks 157 158>;
assigned-clock-parents = <&k3_clks 157 160>;
#address-cells = <1>;
#size-cells = <0>;
wifi@2 {
compatible = "ti,cc3301";
reset-gpios = <&main_gpio0 38 GPIO_ACTIVE_LOW>;
reg = <2>;
};
btti@1 {
compatible = "ti,cc33xxbt";
reg = <1>;
};
};
Please give suggestion.
Regards,
Gireesh Hiremath
