Stuck in RFST_IDLE state after power on

[fredldotme]

When powering on the nfcd adapter based on the pn54x plugin the plugin resets NCI and transitions the NCI state to RFST_IDLE but doesn't enter discovery mode thereafter as opposed to binder-based devices.

Log: https://paste.ubuntu.com/p/r5kxkXt3Ds/

EDIT: I did power on the adapter using: dbus-send --system --dest=org.neard --print-reply /nfc0 org.freedesktop.DBus.Properties.Set string:org.neard.Adapter string:Powered variant:boolean:true

Device: Sony Xperia X
OS: Ubuntu Touch
Kernel: 4.4
Arch: arm64

[monich]

Which version of nfcd are you running?

[fredldotme]

Version 1.0.41, slightly patched to allow building without libdbusaccess and disabling the dbus_log plugin: https://github.com/ubports/nfcd/commits/xenial_-_android9_-_nfcd

[monich]

Correct me if I'm wrong - you don't have anything like nfcd-mce-plugin installed, and plan to use neard D-Bus interface to switch NFC on, right?

[fredldotme]

That's the current plan, yes. We don't use mce on UT.

[fredldotme]

What we could do though is integrate it into our repowerd which takes care of screen on/off states, using a UT specific plugin.

[monich]

Try also dbus-send --system --dest=org.neard --print-reply /nfc0 org.neard.Adapter.StartPollLoop string:Initiator in addition to setting the Powered property.

[fredldotme]

Ok, that transitions it to the discovery state, but no tags are detected, not even those unsupported ones from other bug reports

[monich]

This should make that StartPollLoop thing unnecessary.

[fredldotme]

Works as advertised, will test if NFC tags are actually detected now (probably not) in a few hours. Will report back.

[fredldotme]

Ok, so neither supported tags (Jolla 1 backcover Other Half with empty NDEF entry) nor unsupported ones trigger anything in nfcd.
I guess technically the bug is closed but it still doesn't seem to work properly atm, at least on UT/kernel 4.4.

[monich]

Is it not working because of mer-hybris/libncicore#21 or is it something else?

[fredldotme]

I doubt it would work without reverting the change but I can try later just to be sure.

[fredldotme]

Is it possible that on SailfishOS the Android adaptation does load firmware to the device? Could you please verify that via dmesg | grep pn54?

[monich]

This plugin doesn't load any firmware, it just opens the device and talks more or less directly to the NFC chip. I guess firmware loading somehow needs to be done before booting up Sailfish OS (or before starting nfcd).

Binder plugin, on the other hand, may cause the firmware to be loaded to the chip, if it's done by the Android service which the plugin is talking to (and that's very likely to happen if all necessary files are present).

[fredldotme]

I don't have an Xperia X with SailfishOS ready atm, so I can't test it myself. So does the kernel driver claim firmware to be uploaded by the adaptation?

[monich]

Actually, #3 fixes one of the scenarios when pn54x I/O could get stuck.