Closed
Bug 1165774
Opened 10 years ago
Closed 10 years ago
[Flame L] NFC not working
Categories
(Firefox OS Graveyard :: GonkIntegration, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 1153155
People
(Reporter: viralwang, Unassigned)
References
Details
No description provided.
Reporter | ||
Comment 1•10 years ago
|
||
Hi Dimi,
As our discussion, it looks like NFC failed comes from nxp abnormal.
Could you please help to check this part? Thank you :)
D/NxpTml ( 1547): Opening port=/dev/pn544
D/NxpTml ( 1547): phTmlNfc_i2c_reset(), VEN level 1
D/NxpTml ( 1547): phTmlNfc_i2c_reset(), VEN level 0
D/NxpTml ( 1547): phTmlNfc_i2c_reset(), VEN level 1
D/NxpTml ( 1547): PN547 - Tml Reader Thread Started................
D/NxpTml ( 1547): PN547 - Tml Writer Thread Started................
D/NxpTml ( 1547): PN547 - Tml Writer Thread Running................
D/NxpTml ( 1547): PN547 - Write requested.....
D/NxpTml ( 1547): PN547 - NFCSTATUS_INVALID_DEVICE != gpphTmlNfc_Context->pDevHandle
D/NxpTml ( 1547): PN547 - Tml Writer Thread Running................
D/NxpHal ( 1547): thread started
D/NxpTml ( 1547): PN547 - Read requested.....
D/NxpTml ( 1547): PN547 - NFCSTATUS_INVALID_DEVICE == gpphTmlNfc_Context->pDevHandle
Flags: needinfo?(dlee)
Comment 2•10 years ago
|
||
Hi Viral,
I found that in libnfc-nci
NFCSTATUS_INVALID_DEVICE is defined as 6 in phNfcStatus.h
And gpphTmlNfc_Context->pDevHandle is opened in function |phTmlNfc_i2c_open_and_configure| and the handle value returned by open function is also 6 in this case.
So it will treat gpphTmlNfc_Context->pDevHandle as an invalid device and then NFC cannot be enabled correctly. I have tried making open function return a "non 6" value then everything works fine.
I think the problem is that we should not treat "6" as invalid value because it is actually a valid handle value returned by open function, please check this with t2m, thanks!
Flags: needinfo?(dlee)
Updated•10 years ago
|
Blocks: Flame_L_PVT
Updated•10 years ago
|
No longer blocks: Flame_L_PVT
Reporter | ||
Comment 3•10 years ago
|
||
I think this bug no longer exist since bug 1153155 already landed.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•