MAN, I LovE U so mUCh. just kidding….
the bluetooth headset killed me tons of time.
[quote author=“bushman”]The mystery why sony’s internal bluetooth module can’t handle bluetooth headset is solved.
The bad news is that the software needed is hard-to-get. :-(
First some background how I find the info:
Search on the net found that ipaq people had the same problem
as we:
http://handhelds.org/pipermail/ipaq/2002-September/015525.html
Problem was, is TR using the same chipset as Ipaq?
Gr00vy0ne have some great pictures of the module on this website:
http://www.siliconpopculture.com/review/59_0_2_0_C/
You can clearly see the fcc number (CWTUGPZ3), and there is a search engine for FCC:s
https://gullfoss2.fcc.gov/prod/oet/cf/eas/reports/GenericSearch.cfm
Grantee Code is: CWT
Product code is: UGPZ3
Here is a link to all documentation:
https://gullfoss2.fcc.gov/prod/oet/cf/eas/reports/ViewExhibitReport.cfm?mode=Exhibits&RequestTimeout=500&calledFromFrame=N&application_id=961025&fcc;_id=‘CWTUGPZ3’
Not much info here, but the “module-on-the-module” (marked Z2) must be designed before 01/23/2003.
You can also see that there is a CSR chip inside on the pictures.
Needed more info, and went to a search engine for bluetooth certified products:
http://qualweb.bluetooth.org/Template2.cfm?LinkQualified=QualifiedProducts&SortCat=QualifiedDate
The most likely I found was UGXZ2 (as the module had a “Z2” marking),
and a search found that this looks like the one on the module:
http://www.alps.co.jp/e/press/new2002/f0228-e.htm
Here is the link to the information:
http://qualweb.bluetooth.org/Template2.cfm?LinkQualified=QualifiedProducts&Details=Yes&ProductID=681
There documentations tells that
the chipset (or chip) is a “CSR BC02-EXT”, and it has a 4Mbit flash onboard.
Yep, the same chipset as ipaq (very common), good news!
CSR:s chipset is used in headsets aswell, and in that case they are sending the audiodata to an external codec using a four wire interface.
However, In the TR we don’t have any codec (just an USB interface) and would like the sound to be passed via USB.
It is “incorrectly” programmed in the delivered bluetooth module, but as there is no support in bluespace they probably missed it.
There is hundreds of parameters, so it’s easy to miss one. :-(
The parameter in question is:
#427 (0x1ab) PSKEY_HOSTIO_MAP_SCO_PCM what should be 0 instead of 1
The ipaq people use pskey as mentioned in the link above to set this parameter:
http://www.soft.uni-linz.ac.at/~vogl/bluez/pskey-0.1.tar.gz
Unfortuntly pskey is using a UART to talk to the chipset and we need a software that talks via USB.
The wanted tool is “pstool” (included in blueSuiite) mentioned in this faq:
http://www.csr.com/media/news_faq0203.txt
You must be registed to have access to this software on, and perhaps
even buy hardware from CSR. :-(
http://www.csrsupport.com/
Pstool is a _REALLY_ dangerous tools, so don’t alter anything except for the mentioned paramter, this is also why they don’t let end user get this tool.
But if there’s a will there’s a way, and I used pstool to edit this parameter.
To test the complete link I used bluesolei,
http://www.bluesoleil.com/update/index.asp
Bluesoleil is not working with the ALPS modules without modification,
you must edit some textfiles to get it to work:
Change in “btcusb.inf” and “bttl.ini” and replacing all occurances of “3001” with “3003”.
pstool works nicely with the driver included in the bluesoleil packages, so installing this first is probably a good idea.
Don’t have the bluesoil.exe running when running pstool as pstool and bluesoil can’t have access to the bluetooth module at the same time.
Probably any stack (except the Microsoft XP SP2 BT-stack) will have a working headset profile.
It is also possible that newer bluetooth modules that mine have this parameter “correctly” set.
I hope this information can be of any use, and that someone can make a USB version of the pskey program to eleminate the need for pstool.
/Bushman
