Thanks for sharing your experience! Now I see how you traced uart lines wink.gif
Yes. Exactly.
Whoever did that had real nerve! I wish someone do the same to C1K/C3K, cause I'm afraid that pcb layout is different. However, it might be very helpful for folks who have 7x0/860 devices.
You may try to trace it another way: take devmem2 utility )from for example here
http://2x4ever-vpn.compot.ru/zaurus/devmem2/devmem2 - compiled for arm) and write a little scipt to trigger a necessary GPIO pins while zaurus is running and oscilloscoping a PCB around CPU.
This shoud trigger TX/RX up and down ever second (for PXA250):
# while true; do devmem2 0x40E0001C 0xC00; sleep 1; devmem2 0x40E00028 0xC00; done
What do you mean under "not stable"? At what baud rate? You may want to try to short flying leads, or maybe even better - shield them to avoid interference. I'm not an electric engineer, but do you have an o'scope to check the signal?
Dongle is configured to use CTS/RTS at 230400 speed and works a second or two after that dongle is stops sending anything. When i'm reseting dongle it continues. While it is works for hcitool it doesn't works for PSKEY utility. I'm able to read a length of the PS key but not a contained info. Now i'm soldering dongle to a FFUART to use CTS/RTS and will try to change PS keys.
It seems weird that TX/RX BTUART lines are used in C700. Are you sure in this? You may want to grep for relevant register addresses on the kernel source to see where it gets used.
I'm sure. In the picture i've provided you can see that BTRXD is going to the chip named 2149 282 JRC. Googling on this gives me the folowing datasheet
http://www.njr.co.jp/pdf/de/de05035.pdf. This is an amplifier for a zaurus buzzer.
While i can't trace where BTTXD goes, grepping source of the linux 2.6 kernel for zaurus gives the folowing defines wich are used in a battery charge code:
#define CORGI_GPIO_DISCHARGE_ON (42) /* Enable battery Discharge */
#define CORGI_GPIO_CHRG_UKN (43) /* Unknown Charging (Bypass Control?) */