DM3730 UART

Hi Shlomi,

The issue comes from the incorrect signal name "uart3_cts.uart3_cts". You should use omap_mux_init_signal for signals: uart3_cts_rctx, uart3_rts_sd, uart3_rx_irrx and uart3_tx_irtx.

You can find description of signal names in the DM3730 TRM table 13-4 and table 13-26.

The initialization of pinmux for uart3 also should be made in the uboot. Look at the link for more details:

According the kernel version you should choose how to proceed. Therefore could you specify which kernel version you are using?

BR

Tsvetolin Shulev

im using kernel 3.0.8..

Ok, I initiated the signals for uart3 for all 4 lines (cts, rts, tx, rx).
now, how do i set this exit to be used for a BT chip?

It was previously used for IR control and i want it to be used for BT and i have no idea what code controls it..:/

Shlomi,

There are many source examples for UART send/receive data and I port a link to a simple user space example:

You should pay attention that using UART3 and make changes if necessary. Also you should connect a terminal application on the PC to visualize the date.

BR

Tsvetolin Shulev

thanks for the link,

Ok, Im getting :

<6>[ 0.944793] omap_uart.0: ttyO0 at MMIO 0x4806a000 (irq = 72) is a OMAP UART0
<6>[ 2.301727] omap_uart.1: ttyO1 at MMIO 0x4806c000 (irq = 73) is a OMAP UART1
<6>[ 2.324371] omap_uart.2: ttyO2 at MMIO 0x49020000 (irq = 74) is a OMAP UART2

in the log, ..so where can i find the OMAP UART X config?
did TI set UART2 for BT or is it changeable?

Shlomi,
If I understand your environment correctly the bluetooth adapter is connected to uart. Therefore the uart should be set to uart mode and it no need to know what kind of hardware is connected (BT adapter or something else).

BR
Tsvetolin Shulev

Yes, but the system is programmed to work with the BT connected to uart1 (which is ttyO1) and
now the BT is on uart2 and i need to initialize the hci_uart protocol to ttyO2 instead,

so far i have'nt been successful.

i can see in the init.rc (assuming its the omap3env/init.rc..) the code that does that:

service btpwr /wl1271bt_enable /dev/ttyO1
disabled
oneshot

service hciattach /system/bin/hciattach -n /dev/ttyO1 texas 3000000
user root

when im changing it to ttyO2 nothing changes (the hcitool still goes to ttyO1).

what am i missing?