| 03:49.07 | *** join/#openezx EuroTrash (~rtrsh@82-169-3-152.ip.telfort.nl) |
| 05:30.56 | *** join/#openezx l403 (~l@85.132.159.231) |
| 06:58.13 | *** join/#openezx ao2 (~ao2@cl-35.trn-01.it.sixxs.net) |
| 09:12.21 | *** join/#openezx marex (~marex@vasut.kolej.mff.cuni.cz) |
| 09:31.40 | *** join/#openezx toi (~toi@d54C2AA76.access.telenet.be) |
| 09:35.32 | *** join/#openezx Sleep_Walker (~Sleep@nat/novell/x-cjkyireerccjnwxr) |
| 11:57.10 | *** join/#openezx lclaudio (~lclaudio@189.4.55.17) |
| 12:10.56 | *** join/#openezx mickeyl (~mickey@80.81.242.146) |
| 12:17.22 | *** join/#openezx LoneStar (~xinzhen@116.237.223.182) |
| 12:18.14 | *** join/#openezx janneg (~janne@chybek.jannau.net) |
| 12:18.14 | *** join/#openezx agd5f (~alex@static-74-96-105-7.washdc.fios.verizon.net) |
| 12:18.14 | *** join/#openezx mpurcell (~mpurcell@97.107.138.93) |
| 12:59.39 | *** join/#openezx marex (~marex@vasut.kolej.mff.cuni.cz) |
| 13:44.39 | *** join/#openezx Sleep_Walker (~Sleep@nat/novell/x-dbrcmyxrxqiktooj) |
| 14:16.39 | *** join/#openezx toi (~toi@d54C2AA76.access.telenet.be) |
| 17:49.32 | *** join/#openezx CIA-19 (cia@208.69.182.149) |
| 18:37.43 | *** join/#openezx flo_lap (~fuchs@Maemo/community/contributor/florian) |
| 19:35.00 | *** join/#openezx panicking_mike (~michael@77.224.194.88) |
| 19:35.04 | panicking_mike | Hi all |
| 19:35.09 | panicking_mike | I have seen the kernel source |
| 19:35.14 | panicking_mike | and some variant of ezx |
| 19:35.19 | panicking_mike | talk with bcm2045 |
| 19:35.23 | panicking_mike | bluetooth |
| 19:35.24 | panicking_mike | module |
| 19:35.33 | panicking_mike | I don't understand how is performed |
| 19:35.38 | panicking_mike | the reset sequence |
| 19:35.40 | panicking_mike | of the device |
| 19:35.47 | panicking_mike | I give power |
| 19:36.09 | panicking_mike | put wakeup to 1 |
| 19:36.13 | panicking_mike | put reset to 0 |
| 19:36.16 | panicking_mike | for 20ms |
| 19:36.20 | panicking_mike | and then go up to 1 |
| 19:36.28 | panicking_mike | I don't find any documentation about timing |
| 19:36.37 | panicking_mike | anyone have some info about the bcm2045 reset |
| 19:36.44 | panicking_mike | after reset phase |
| 19:37.00 | panicking_mike | I was thinking that I can talk with him using the h4 |
| 19:37.01 | panicking_mike | serial protocol |
| 19:37.14 | panicking_mike | but hciattach /dev/ttyS2 csr |
| 19:37.17 | panicking_mike | go in timeout |
| 19:37.24 | panicking_mike | I have tried using the bcm2035 |
| 19:37.27 | panicking_mike | profile |
| 19:37.30 | panicking_mike | but noway |
| 19:37.44 | panicking_mike | seems that it's of |
| 19:37.54 | panicking_mike | the initializaition is invalid |
| 19:37.56 | panicking_mike | any idea? |
| 19:47.16 | tmzt | powered off with pmic? |
| 19:47.47 | tmzt | pretty much everything with bt is done from userspace, probably through sysfs |
| 19:49.43 | panicking_mike | gpio |
| 19:49.46 | panicking_mike | on a regulator |
| 19:49.49 | panicking_mike | voltage output |
| 19:49.52 | panicking_mike | and I have |
| 19:49.58 | panicking_mike | a BT_RESET gpio |
| 19:50.02 | panicking_mike | and a BT_WAKE |
| 19:50.03 | panicking_mike | gpio |
| 19:51.02 | panicking_mike | reset is active low |
| 19:51.02 | panicking_mike | so 1 0 1 reset the device |
| 19:51.02 | panicking_mike | and BT_WAKE is not described |
| 19:51.02 | panicking_mike | seems to be active high |
| 19:51.10 | panicking_mike | I suppose that the firmware is inside |
| 19:51.14 | panicking_mike | the bcm eprom |
| 19:51.29 | panicking_mike | oadcomÂs BCM2045 B2 Version |
| 19:51.37 | panicking_mike | this is the firmware |
| 19:53.29 | tmzt | this isn't an ezx device? |
| 19:53.43 | tmzt | I don't think we use any of the signal lines, just power off/on the chip |
| 19:53.48 | tmzt | and do init over serial |
| 19:53.56 | tmzt | make sure you get the initial baud rate correct |
| 19:54.53 | panicking_mike | What is the init over the serial just send the init command on it |
| 19:55.02 | panicking_mike | bluez initialization |
| 19:55.06 | tmzt | it's in the bluez source |
| 19:55.13 | panicking_mike | yes I see |
| 19:55.18 | tmzt | kernel isn't really involved in any of this |
| 19:55.22 | panicking_mike | yes I know |
| 19:55.26 | tmzt | what hardware? |
| 19:55.26 | panicking_mike | I was thinking |
| 19:55.55 | panicking_mike | maruta bluetooth device |
| 19:56.03 | panicking_mike | it's a mobile phone |
| 19:56.05 | panicking_mike | pxa320 |
| 19:56.06 | panicking_mike | board |
| 19:56.44 | tmzt | http://www.murata.com/nproduct/06c_e2c2.html |
| 19:56.51 | tmzt | and you run linux on the device? |
| 19:57.44 | tmzt | is this broadcom based? |
| 20:07.54 | *** join/#openezx Sleep_Walker (~Sleep@193.179.96.131) |
| 20:13.52 | marex | panicking_mike, do I hear pxa320 ? |
| 20:13.59 | marex | in a phone? how perverse |
| 20:14.41 | panicking_mike | yes |
| 20:14.42 | panicking_mike | mobile |
| 20:15.00 | panicking_mike | not mass production |
| 20:15.04 | panicking_mike | but industrial mobile |
| 20:15.35 | marex | panicking_mike, ah industrial ... that explains it |
| 20:15.45 | marex | panicking_mike, if you have interest in pxa3xx ... join #openpxa |
| 20:20.31 | panicking_mike | I have seen the ezx has a brodcom chip in the ezx.c in kernel |
| 20:20.53 | panicking_mike | this is the reason that I'm here |
| 20:20.58 | panicking_mike | just to know how ezx |
| 20:21.08 | panicking_mike | talk with the bcm |
| 20:29.12 | marex | panicking_mike, 2035 has UART and USB |
| 20:29.19 | marex | and a RESET and POWER GPIO pins |
| 20:30.06 | panicking_mike | we are talking about uart connection |
| 20:30.16 | panicking_mike | but I don't find timing |
| 20:30.21 | panicking_mike | 10 20 100 ms |
| 20:30.23 | panicking_mike | or more |
| 20:31.01 | panicking_mike | power -> reset |
| 20:31.08 | panicking_mike | tosa-bt is an exaple |
| 20:31.14 | panicking_mike | in how reset a bluetooth device |
| 20:41.04 | ao2 | panicking_mike, on some openezx phones there is a strange setup, the BT power state is controlled from the Baseband Processor, and we control that with some AT commands... on some other phones power is controlled via a PMIC regulator |
| 20:42.05 | ao2 | the uart attach is done simply with hciattach, I can search for the exact command if this can be useful to you |
| 20:42.57 | ao2 | hciattach /dev/ttyS1 bcm2035 460800 flow 01:02:03:04:05:06 |
| 20:43.23 | panicking_mike | CONFIG_BT_HCIUART_H4 |
| 20:43.28 | panicking_mike | this the important config |
| 20:43.32 | panicking_mike | at kernel level |
| 20:43.38 | ao2 | I have no experience with the bcm2045 yet |
| 20:45.09 | ao2 | ah, I am not sure about the kernel config, if you say that is it, I simply trust you, sorry |
| 20:47.04 | panicking_mike | hciattach /dev/ttyS2 bcm2035 460800 flow 01:02:03:04:05:06 |
| 20:47.05 | panicking_mike | Baud rate parameters: DHBR=0x22,DLBR=0xfd |
| 20:47.05 | panicking_mike | Device setup complete |
| 20:47.07 | panicking_mike | is this good |
| 20:47.11 | panicking_mike | ? |
| 20:53.59 | panicking_mike | good |
| 20:58.03 | panicking_mike | thanks to all |
| 20:58.05 | panicking_mike | I have reduce |
| 20:58.11 | panicking_mike | reset sequnece |
| 20:58.17 | panicking_mike | and increse reset time |
| 21:04.35 | panicking_mike | Now it works |
| 21:10.38 | ao2 | panicking_mike, that's good. |
| 21:26.05 | panicking_mike | yes |
| 21:26.12 | panicking_mike | I need to test tomorrow in android |
| 21:26.15 | panicking_mike | and that's it |
| 21:26.21 | panicking_mike | but scan |
| 21:26.27 | panicking_mike | it's ok |
| 21:56.54 | panicking_mike | bye all |
| 22:53.58 | *** join/#openezx marex (~marex@vasut.kolej.mff.cuni.cz) |