Hi all,
I am trying to bring up OM27160A1 eval kit on our board. I ported linux_libnfc-nci. But run "nfcDemoApp poll" will get "NFCC rejects discover CMD".
From source code: nfa_dm_discover.cc, function: nfa_dm_disc_sm_idle():
解決済! 解決策の投稿を見る。
After modify the source code, disable NFA_TECHNOLOGY_MASK_KOVIO in the RF discover. Tag can be detected now.
Thanks
After modify the source code, disable NFA_TECHNOLOGY_MASK_KOVIO in the RF discover. Tag can be detected now.
Thanks
How to do? ths.
Hello.
I'm stuck on same situation with OM27160A1HN Board.
I executed "./nfcDemoApp poll" and the last logs are stated below.
2023:06:22-15:11:32.350 NfcAdaptation::HalDeviceContextDataCallback: len=5
2023:06:22-15:11:32.350 NFC received rsp gid:0
2023:06:22-15:11:32.350 nci_proc_core_rsp opcode:0x2
2023:06:22-15:11:32.350 NFC_SET_CONFIG_REVT(0x5002)
2023:06:22-15:11:32.350 NfcAdaptation::HalPrediscover
2023:06:22-15:11:32.350 PN54X - Read requested.....
2023:06:22-15:11:32.350 PN54X - Invoking I2C Read.....
2023:06:22-15:11:32.350 NfcAdaptation::HalWrite
2023:06:22-15:11:32.351 [NCIHAL] > Polling Loop Started
2023:06:22-15:11:32.351 PN54X - Write requested.....
2023:06:22-15:11:32.351 PN54X - Invoking I2C Write.....
2023:06:22-15:11:32.353 len = 20 > 2103110800010101020103018001810106017401
2023:06:22-15:11:32.353 PN54X - I2C Write successful.....
2023:06:22-15:11:32.353 PN54X - Posting Fresh Write message.....
2023:06:22-15:11:32.353 PN54X - Tml Writer Thread Running................
2023:06:22-15:11:32.353 [NCIHAL] write successful status = 0x0
2023:06:22-15:11:32.354 PN54X - I2C Read successful.....
2023:06:22-15:11:32.354 len = 4 > 41030105
2023:06:22-15:11:32.354 PN54X - Posting read message.....
2023:06:22-15:11:32.354 [NCIHAL] read successful status = 0x0
2023:06:22-15:11:32.354 NfcAdaptation::HalDeviceContextDataCallback: len=4
2023:06:22-15:11:32.354 PN54X - Read requested.....
2023:06:22-15:11:32.354 PN54X - Invoking I2C Read.....
2023:06:22-15:11:32.354 NFC received rsp gid:1
2023:06:22-15:11:32.355 p2p priority is running under bail out mode ONLY.
2023:06:22-15:11:32.355 event:0x4000
2023:06:22-15:11:32.355 state: IDLE (0), event: DISCOVER_RSP(1) disc_flags: 0x31
2023:06:22-15:11:32.355 NFC_Deactivate 4 (IDLE) deactivate_type:0
2023:06:22-15:11:32.355 new state: IDLE (0), disc_flags: 0x31
2023:06:22-15:11:32.355 NfcAdaptation::HalWrite
2023:06:22-15:11:32.355 PN54X - Write requested.....
2023:06:22-15:11:32.355 PN54X - Invoking I2C Write.....
2023:06:22-15:11:32.356 len = 4 > 21060100
2023:06:22-15:11:32.356 PN54X - I2C Write successful.....
2023:06:22-15:11:32.356 PN54X - Posting Fresh Write message.....
2023:06:22-15:11:32.356 PN54X - Tml Writer Thread Running................
2023:06:22-15:11:32.356 [NCIHAL] write successful status = 0x0
2023:06:22-15:11:32.357 PN54X - I2C Read successful.....
2023:06:22-15:11:32.357 len = 4 > 41060106
2023:06:22-15:11:32.357 PN54X - Posting read message.....
2023:06:22-15:11:32.357 [NCIHAL] read successful status = 0x0
2023:06:22-15:11:32.357 NfcAdaptation::HalDeviceContextDataCallback: len=4
2023:06:22-15:11:32.357 PN54X - Read requested.....
2023:06:22-15:11:32.358 PN54X - Invoking I2C Read.....
2023:06:22-15:11:32.358 NFC received rsp gid:1
2023:06:22-15:11:32.358 p2p priority is running under bail out mode ONLY.
2023:06:22-15:11:32.358 nfc_set_state 4 (IDLE)->4 (IDLE)
2023:06:22-15:11:32.358 nfa_dm_disc_data_cback
2023:06:22-15:11:32.358 event:0x4005
2023:06:22-15:11:32.358 state: IDLE (0), event: DEACTIVATE_RSP(7) disc_flags: 0x31
2023:06:22-15:11:32.358 new state: IDLE (0), disc_flags: 0x11
2023:06:22-15:11:34.327 nfa_sys_ptim_timer_update expired: 0x7eb160a6d0
2023:06:22-15:11:34.327 ptim timer stop
2023:06:22-15:11:34.328 NFA got event 0x021A
2023:06:22-15:11:34.328 Event NFA_EE_DISCV_TIMEOUT_EVT(0x21a), State: INIT_DONE(1)
Would you share the solution you found?
Thanks for reading!
If I run NfcFactoryTestApp, rf discovery can start:
Select the test to run:
1. Continuous RF ON mode
2. Functional mode
3. PRBS mode
4. Standby mode
5. Dump RF settings
6. Set RF setting
7. Get NCI parameter value
8. Set NCI parameter value
9. Get proprietary parameter value
10. Set proprietary parameter value
enter 0 to leave the application
Your choice: 2
Functional test mode, starting discovery loop ...
(tml_transceive)(105)
(tml_send)(53)
len->12: handle:3 0x21 0x3 0x9 0x4 0x0 0x1 0x1 0x1 0x2 0x1 0x6 0x1
(tml_send)(63) retry
NFC Controller is now in functional mode - Press Crtl^Z to stop
- tag discovered, restarting discovery loop ...
(tml_transceive)(105)
(tml_send)(53)
len->4: handle:3 0x21 0x6 0x1 0x3
- tag discovered, restarting discovery loop ...
(tml_transceive)(105)
(tml_send)(53)
len->4: handle:3 0x21 0x6 0x1 0x3
- tag discovered, restarting discovery loop ...
(tml_transceive)(105)
(tml_send)(53)
==========================
cmd is: {0x21, 0x03, 0x09, 0x04, 0x00, 0x01, 0x01, 0x01, 0x02, 0x01, 0x06, 0x01};
Compare with "nfcDemoApp poll":
len = 22 > 21031309000101010201030180018101060174017001
What's the difference? why doesn't second work?
Thanks
I print out debug info, can see nfc_discover.status is 5(NCI_STATUS_SYNTAX_ERROR). linux library source code is from "git clone https://github.com/NXPNFCLinux/linux_libnfc-nci.git -b NCI2.0_PN7160" according to AN13287.