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.

Linux/WL1835MOD: Bluetooth Initialization Timeout

Part Number: WL1835MOD

Tool/software: Linux

When running hciattach, I receive the message 'Initialization timed out.'

I am running on UART1, (/dev/ttymxc0). 

Device tree snippets:

&uart1 {
	pinctrl-names = "default";
	pinctrl-0 = <&pinctrl_uart1>;
	status = "okay";
	fsl,uart-has-rtscts;
};
pinctrl_uart1: uart1grp {
	fsl,pins = <
		MX6SX_PAD_ENET2_COL__UART1_RX		0x1b0b1
		MX6SX_PAD_ENET2_CRS__UART1_TX		0x1b0b1
		MX6SX_PAD_ENET2_TX_CLK__UART1_RTS_B	0x1b0b1 /* RTS */
		MX6SX_PAD_ENET2_RX_CLK__UART1_CTS_B	0x1b0b1 /* CTS */
		MX6SX_PAD_ENET1_RX_CLK__GPIO2_IO_4	0x1b0b0	/* BT_EN */
	>;
};

I am not trying to use the shared transport driver, simply verify hardware using hciattach and similar tools. 

When I run the command: 

echo 0 > gpio36/value; sleep 1; echo 1 >gpio36/value; hciattach /dev/ttymxc0 texas 115200

I see the output: 'Initialization timed out.'

This is what is seen on the UART lines:

Also, the voltage measured on CTS is only 1.5V. 

The host processor is an i.MX6SX running Linux version 4.1.10. According to the NXP reverse naming scheme, CTS is connected to CTS, and RTS is connected to RTS.

Are there any ideas of what I am missing?