00139802 vendor-specific NVM parameter for BTS4025 PCM loopb

[admin]

Subject [David Lan] vendor-specific NVM parameter for BTS4025 PCM loopback test mode
Description Dear QCT,
We need to verify the PCM input/output port between host and BTS4025.
What HCI vendor-specific command packet can enable BTS4025 the PCM loopback test mode in which data read from the PCM input port is written back out again via the PCM output port after delay?
Thanks
David Lan

[admin]

Comment

Created By: David Lan (4/27/2009 1:42 AM)
No problem.



Created By: Prudvidhar Thangella (4/24/2009 1:45 AM)
Dear Customer,
Can you please raise a new case with all the details. I will look into those? There might be variation based on the MSM and other things and I want to deal that separately. Is that ok?

Thanks,
-Pruthvi



Created By: RDD2 SW (4/24/2009 1:36 AM)
Dear Prudvidhar,
Sincerely thank you for your kind information.
We will check to see the document of 80-VP860-1, then.
By the way, does QRCT support the target QCT device which with Linux BSP 3120/2100 for the BT FTM mode?
And, please kindly inform me where and how we can get the newest version of QRCT.
Thanks
David



Created By: Prudvidhar Thangella (4/23/2009 2:21 AM)
Dear Customer,
We are preparing the doc we are going to publish by end of this week or by next week. The no is 80-VP860-1.

For your information here is the outline on how you can verify the physical connection between BTS402x and MSM.

***************************************************************************************
* Physical Connectivity test between MSM and SoC
The Bluetooth Connectivity test code will be a part of the modem image and would get invoked by the FTM BT driver on receiving the Start test command (0x0A).

* Starting the test (BT connectivity test)
An end user can type 0x0A in HCI Command text box on QRCT and click on “Send Command” to kick start the test. The SoC would be re-initialized before starting the test.

*Interpreting the Test Results (BT connectivity test)
Any failure in BT connectivity test would be reported as a failure event to FTM. After the execution of test, the BT driver would report the status of the test. Refer to the ftm_bt_drv.c/h Implementation details section above. If the test passes it will have error code of FTM_BT_DRV_NO_ERR, if it fails it will have error code of FTM_BT_DRV_CONN_TEST_FAILS.
On QRCT BT log screen the event packets would show up as follows:
Fail: 0x0F, 0x01
Pass: 0x0F, 0x00
***************************************************************************************

Thanks,
-Pruthvi



Created By: Prudvidhar Thangella (4/21/2009 7:23 AM)
Dear Customer,
I am working with our team to find the info. I will update you once I got the info...

Thanks,
-Pruthvi



Created By: RDD2 SW (4/19/2009 7:26 PM)
Dear Pruthvi,
We will test path1 at the same time, please help to clarify the solution for path1 after clarified the HCI vendor-specific command packet for path2, thank you.
Thanks
David



Created By: RDD2 SW (4/19/2009 6:44 PM)
Dear Pruthvi,
The path is the item2 : MSM-->BTS4025-->MSM (here the SCO data sent from MSM and loopback within BTS4025.
What HCI vendor-specific command enable BTS4025 into PCM loopback test mode in which data read from the BTS4025 PCM input port is written back out again via the BTS output port after delay?
Thanks
David



Created By: Prudvidhar Thangella (4/17/2009 5:19 AM)
Dear customer,
Can you please clarify which path actually you want to test..

1. BT HS-->BTS4025->BT HS (here the BT HS connected/Tester and the data is looped back from DSP DMA buffers in the MSM)
2. MSM-->BTS4025->MSM (here the SCO data sent from MSM and loopback within BTS4025)
3. Or is there any other scenario that you want to test?

Thanks,
-Pruthvi