Magic4g 夢幻國度的虛幻世界

Subject

[David][BT] QRCT Bluetooth FTM



Description

Dear Qualcomm Team,
Refer to 80-WL300-27_QRCT_USER_GUIDE_FOR_WCN3660_WLAN-BT-FM_IN_FTM_MODE.pdf, we follow below SOP to enable BT FTM mode.

Run QRCT
A.Select the Viewmenu > Debug Message.
B.Click the center of the COM Port button (do not select the drop-down menu), then wait a few seconds for QRCT to scan for an available com port.
C.Next, click the menu arrow on the COM Port button and select the COM<XX> port that is assigned to the MSM8960-enabled device by QPST.
D.Click FTMcommand menu and select:
BT > HCIcommands or BT > EPTMcommands for BT test.
Please refer to the attachment for its error log and advise us how to enter Bluetooth FTM mode. Thank you.
By the way, DUT entered download mode finally.
BR
David

Comment



Created By: Erin Yueh (9/25/2012 1:53 AM)
Hi David,

For QCN file, pleas create a new case and assign to Modem team.

For LE in QRCT, you can choose "FTM Command" --> Bluetooth --> LE.
If you have any further question about BLE, please create a new case and describe your question with more details.

Thanks,
Erin




Created By: David Lan (9/25/2012 1:20 AM)
Hi Erin,
Is there specific QRCT Bluetooth FTM for BT 4.0?
Sincerely,
David




Created By: David Lan (9/25/2012 1:08 AM)
Hi Erin,
Thank you for your declaration.
I had attached you all the QCN files.
Before close this SR, could you kindly direct us those necessary NV items in QCN for Bluetooth FTM mode? Thank you.
Sincerely,
David




Created By: Erin Yueh (9/25/2012 12:32 AM)
Hi David,

As I know, there is no difference in Bluetooth between WCN3660 and WCN3680.

Thanks,
Erin




Created By: David Lan (9/25/2012 12:14 AM)
Hi Erin,
Thank you for your incoming call.
We happen to find out that this is a QCN issue.
Hence we are supposed to close this SR right after you have clarified our last question adhere.
Is there any difference between WCN3660 and WCN3680 if we happen to use them to process our FTM?
Again, thank you for your kind support.
Sincerely,
David




Created By: David Lan (9/24/2012 6:56 PM)
Hi Erin,
Despite below information, here is my mobile phone number - 0928881161 - for your reference.
Sincerely,
David




Created By: David Lan (9/24/2012 3:14 AM)
Hi Erin,
Sorry for my responding late.
(David)
It seems SURF8960(0) means that DUT failed into FTM mode, yet SURF8960(7415B01F) can enter FTM mode.
Do you happen to know the reason why their value in parentheses are different?
(Erin)
You were using the SAME steps on both of them, right? Click DUT mode button, then send HCI command manually, right?
(David)
Yes, we were using the SAME steps on both them.
We click DUT mode button, then send HCI command manually.
(Erin)
I check the log file and found you sent this command to disable USB charging. Could I know why you'd like to disable it?
adb shell "echo 1 > /sys/module/pm8921_charger/parameters/disabled"
(David)
"echo 1 > /sys/module/pm8921_charger/parameters/disabled".
It disables DUT the USB charging feature.
No matter echo it or not, we have the same result.
(Erin)
Could you leave your contact phone here?
(David)
Sure, no problem.
(03)2700000 Ext.2721.
Sincerely,
David




Created By: Erin Yueh (9/24/2012 1:25 AM)
Hi David,

From your screen video files, I cannot tell why it's failed on unworkable case. You were using the SAME steps on both of them, right? Click DUT mode button, then send HCI command manually, right?

Looks like initially phone booted, stayed powered on for some time and then crashed/rebooted. Reason we are thinking that phone crashed/rebooted because QMSL/QRCT last log is “No Phone Connected” and adb logs (video+ log file) ftmdaemon crashed.

Could you leave your contact phone here?

Thanks,
Erin




Created By: Erin Yueh (9/24/2012 1:19 AM)
Hi David,

I check the log file and found you sent this command to disable USB charging. Could I know why you'd like to disable it?

adb shell "echo 1 > /sys/module/pm8921_charger/parameters/disabled"

Thanks,
Erin




Created By: Erin Yueh (9/19/2012 2:03 AM)
Hi David,

Thanks for the log files. We will investigate this issue and feed back to you later.

Regards,
Erin




Created By: David Lan (9/19/2012 1:58 AM)
Hi Erin,
Please refer to the attached rar files - including recording files and logs - and help to correct our improper operations.
Yours sincerely,
David




Created By: Erin Yueh (9/18/2012 8:39 PM)
Hi David,

I cannot see any bluetooth message in QXDM log, did you use that *.dmc file to retrieve log from QXDM? Also, from other log files, i cannot find you tried to send HCI commands in QRCT either. Could you try below TWO steps in QRCT?

1. click DUT mode button
2. after you see "QLIB_FTM_BT_Enable_Bluetooth Failed" in QRCT debug message
3. send HCI commands in QRCT
QRCT->FTM Command->BT->HCI commands ->HCI user cmd
---input---
01,03,18,00
---end---

Please provide us with QXDM (with bluetooth log), QRCT debug, QMSL debug and ftmdaemon output log files to analyse the problem.

Thanks,
Erin




Created By: David Lan (9/18/2012 8:33 PM)
Hi Erin,
We prioritize this SR.
Please let us know if any update.
Thank you for your attention to this SR.
Yours sincerely,
David




Created By: David Lan (9/16/2012 8:17 PM)
Hi Erin,

Please refer to the attachments for necessary QXDM (with bluetooth log), QRCT debug, QMSL debug and ftmdaemon output log files.

BR
David




Created By: Erin Yueh (9/14/2012 9:03 AM)
Hi David,

Please use the new attachment to retrieve QXDM log again and it would enable bluetooth debug message in QXDM.

When you use QRCT, you may click "DUT MODE" button. Then type hci command to enter into DUT mode manually. Our Tool team is looking at this issue. They need related log files to investigate the problem.

(1) click DUT MODE button
(2) type HCI command
QRCT->FTM Command->BT->HCI commands ->HCI user cmd
---input---
01,03,18,00
---end---

They need QXDM (with bluetooth log), QRCT debug, QMSL debug and ftmdaemon output log files.

Thanks,
Erin




Created By: Erin Yueh (9/14/2012 1:23 AM)
Hi David,

I am checking this issue with our QRCT tool team. If I have any update, I will let you know.

Thanks,
Erin




Created By: David Lan (9/14/2012 1:20 AM)
Hi Erin,
Do you happen to have any update for this Diag request timeout?
Refer to the QPST Connfiguration, we can see SURF8960(0) - DIAG reqeust timeout and SURF8960(7415B01F) pass.
Do you happen to know what meaning does 7415B01F stand for?
BR
David




Created By: David Lan (9/12/2012 1:41 AM)
Hi Erin,
AMSS build ID:
M8960AAAAANLYA2003
Thank you.
BR
David




Created By: Erin Yueh (9/12/2012 1:31 AM)
Hi David,

What is your current AMSS build ID?

Thanks,
Erin




Created By: Erin Yueh (9/12/2012 1:29 AM)
Hi David,

From QXDM log, we can see something wrong on DIAG side.
05:58:39.658 Timeout/error on DIAG request

I will pass it to our DIAG team.

Thanks,
Erin




Created By: David Lan (9/11/2012 11:46 PM)
Hi Erin,
Please refer to the attachment for QXDM log. Thank you.
BR
David




Created By: Erin Yueh (9/11/2012 8:48 PM)
Hi David,

The QXDM log you provided is not right. Please reference to below documents to retrieve correct logs.

1) 80-V4036-1_F_QXDM_Overview
2) 80-V1241-21_YJ_QXDM_Pro_User_Guide: check "2.5 Item Store Format (.ISF) files", it shows how to retrieve QXDM log.

From QRCT log, it looks like you can send HCI commands to enter into DUT mode without problem.

Thanks,
Erin




Created By: David Lan (9/11/2012 7:21 PM)
Hi Erin,
Please refer to the attached log2 file.
BR
David




Created By: Erin Yueh (9/11/2012 5:07 AM)
Hi David,

There is no QXDM log from the attachment. One is QRCT debug message and the other is QMSLlog message. Could you upload QXDM log again? How about FTM daemon log? Did you try to send HCI command from QRCT?

Thanks,
Erin




Created By: David Lan (9/11/2012 3:37 AM)
Hi Erin,
Please refer to the attached QXDM & QRCT log.
The QMSL is empty hence no log.
BR
David




Created By: David Lan (9/11/2012 3:36 AM)
Hi Erwin,
Please refer to the attached QXDM & QRCT log.
The QMSL is empty hence no log.
BR
David




Created By: David Lan (9/11/2012 2:36 AM)
Hi Erin,
Always thank you for yoru kind support.
Yes, we are glad to share the result with you.
And provide you QXDM, QRCT, QMSL, ftmdaemon debug message if we still have problem on entering DUT mode.
BR
David




Created By: Erin Yueh (9/11/2012 2:11 AM)
Hi David,

Please download our latest QRCT 3000 from support site. Also, reference to the new attachment image file. ( it's the screenshot of QRCT, shows how to save QMSL, QRCT debug message).

You can try below command to enter into DUT mode. Could you share the result?

QRCT->FTM Command->BT->HCI commands ->HCI user cmd
---input---
01,03,18,00
---end---

If you still have problem on entering DUT mode, please provide QXDM, QRCT, QMSL, ftmdaemon debug message.

Thanks,
Erin




Created By: David Lan (9/11/2012 2:04 AM) | Last Modified By: David Lan (9/11/2012 2:04 AM)
Hi Erin,
Please refer to the QRCT & AMSS version adhere.
QDART:
Version: 4.5.21
CM DCN: 72-VB981-43
ECO: C245394

AMSS:
M8960AAAAANLYA2003

Yes, citing the attached QCRT picture, we clicked HCI DUT MODE button in QRCT to enable into DUT mode.
BR
David




Created By: Erin Yueh (9/11/2012 12:31 AM)
Hi David,

Please provide your AMSS build ID. Were you trying to enter into DUT mode by clicking DUT MODE button in QRCT? What is your QRCT version?

Thanks,
Erin




Created By: David Lan (9/11/2012 12:17 AM)
Hi Erin,
Please refer to attachment for related information.Thank you.
It seems SURF8960(0) means that DUT failed into FTM mode, yet SURF8960(7415B01F) can enter FTM mode.
Do you happen to know the differences between them?
BR
David




Created By: David Lan (9/10/2012 10:37 PM)
Hi Erin,
Thank you for your responding.
Yes, we run ftmdaemon from adb shell.
The debug message supposed to be attached later on.
BR
David




Created By: Erin Yueh (9/10/2012 8:52 PM)
Hi David,


Did you run ftmdaemon from adb shell? Could you provide the full QRCT debug message and ftmdaemon output to analyse the problem.

Thanks,
Erin

add Qualcomm attached files