Other Parts Discussed in Thread: WL1837MOD, WL1837
hi:
Software version: ti-processor-sdk-linux-rt-am57xx-evm-05.03.00.07, hardware version: AM5708-ES2.0, custom board,
When using the bluez protocol stack in wl1837mod, an initialization timeout error occurs when using hciattach. What should I do to solve this problem and help me.
The steps I took were:
1、Modify uboot mux_data.h file
{GPMC_A0, (M8 | PIN_INPUT | MANUAL_MODE)}, /* uart5_rxd */
{GPMC_A1, (M8 | PIN_OUTPUT | MANUAL_MODE)}, /* uart5_txd */
{GPMC_A2, (M8 | PIN_INPUT | MANUAL_MODE)}, /* uart5_ctsn */
{GPMC_A3, (M8 | PIN_OUTPUT | MANUAL_MODE)}, /* uart5_rtsn */
{SPI1_D0, (M14 | PIN_OUTPUT_PULLDUP)}, /* gpio7_9 wl1837 BT_EN pin */
2、Modify the kernel device tree file
&uart5 {
status = "okay";
};
3、Compile u-boot with device tree
4、Enter the following command in the board terminal
root@am57xx-evm:~# echo 201 > /sys/class/gpio/export
root@am57xx-evm:~# echo "out" > /sys/class/gpio/gpio201/direction
root@am57xx-evm:~# echo 1 > /sys/class/gpio/gpio201/value
root@am57xx-evm:~# echo 0 > /sys/class/gpio/gpio201/value
hciattach -t 30 -s 115200 /dev/ttyS4 texas 3000000 flow
hciattach -s 115200 /dev/ttyS4 texas 3000000 flow
hciattach -s 115200 /dev/ttyS4 texas 3000000
They are all prompts Initialization timed out
I refer to the following related posts：
e2e.ti.com/.../1233825
e2e.ti.com/.../831978
e2e.ti.com/.../860869
