NFC中的主题 Re: OM27160 raspberry i2c NfcService Init Failed

OM27160 raspberry i2c NfcService Init Failed

paweljasinski — Mon, 11 Mar 2024 14:26:39 GMT

I have a OM27160A1HN connected to raspberry pi.

I have followed the instructions for i2c from https://www.nxp.com/docs/en/application-note/AN12991.pdf

When I run "nfcDemoApp poll", I get the "NfcService Init Failed".

What I tried so far:

I have double checked the board and it is i2c and not spi.

Scanning of the i2c with "i2cdetect -y 1" does not show anything.

I have tried with 2 different raspberries, which are knows to work with other i2c devices.

I have enabled debug, log is attached.

Any idea what should I check now?

Re: OM27160 raspberry i2c NfcService Init Failed

EduardoZamora — Tue, 12 Mar 2024 01:42:18 GMT

Hello @paweljasinski,

Hope you are doing well.

Could you please refer to the PN7160 Linux porting guide? This document describes in detail how to add support for a PN7160 controller to a generic GNU/Linux system.

Regards.
Eduardo.

Re: OM27160 raspberry i2c NfcService Init Failed

Tomas_Parizek — Tue, 12 Mar 2024 07:59:04 GMT

Hello Pawel,

Can you check the libnfc-nxp.conf, please?

You need to set the I2C alternative driver also here:

So for I2C -> NXP_TRANSPORT=0x02

Tomas

Re: OM27160 raspberry i2c NfcService Init Failed

paweljasinski — Tue, 12 Mar 2024 09:05:57 GMT

The setting are correct. I will attach strace log which shows opening /dev/i2c-1

Re: OM27160 raspberry i2c NfcService Init Failed

paweljasinski — Tue, 12 Mar 2024 09:19:41 GMT

here is the relevant snipped from the config. The config was changed before building.

NXP_TRANSPORT=0x02

###############################################################################
# Nfc Device Node name
NXP_NFC_DEV_NODE="/dev/i2c-1"

The strace file shows that the correct file is open. I have selected only the log from interesting thread.

The command was: "strace -ff -o strace.log nfcDemoApp poll"

Re: OM27160 raspberry i2c NfcService Init Failed

paweljasinski — Tue, 12 Mar 2024 09:18:32 GMT

Is it possible that the 7160 is missing firmware or has a wrong firmware?

Would trying with SPI help?

Re: OM27160 raspberry i2c NfcService Init Failed

Tomas_Parizek — Thu, 14 Mar 2024 11:02:17 GMT

Hello Pawel,

Ok, I see. Let me grab one Raspberry Pi and check with PN7160 on my side.

BTW. Are you using a raspberry Pi "shield" or are you using a cable connection?

Tomas

Re: OM27160 raspberry i2c NfcService Init Failed

Tomas_Parizek — Tue, 19 Mar 2024 16:12:02 GMT

Hello Pawel,

I just tested with the Raspberry Pi on my side

I exactly followed the instructions listed in the App. Note you have mentioned.

Here is the result:

You can see that for the first time, I also got the "NfcService Init Failed" error message as you.

So I removed the PN7160 from the socket and put it back + I checked if the I2C was enabled.

Then the NFC application started to work as you can see in the picture.

Here is the information about HW that I am using:

Also, one more thing I did at the beginning. I enabled the I2C in preferences:

Tomas

Re: OM27160 raspberry i2c NfcService Init Failed

paweljasinski — Mon, 29 Apr 2024 12:53:07 GMT

guys, I had no time to perform the full install and try to use the driver which I believe can change something.
At the same time what is marked as solution, does not solve anything. If you read my description, I have no problem talking to different devices using I2C. So the marked solution solves only the problem it created itself by disabling I2C.

Re: OM27160 raspberry i2c NfcService Init Failed

Stephan_B — Wed, 26 Jun 2024 08:20:11 GMT

Hi @Tomas_Parizek

I have the same issue. I've checked the I2C, unplugged and rebooted multiple times but I always get the "NfcService Init Failed". Do you have any more suggestions I could try to get my setup running?

The error message is the same whether the OM27160 is plugged in or not. Is there a easy way to verify whether the PN7160 is responding? Maybe my hardware has some defect?

Thanks

Stephan

Re: OM27160 raspberry i2c NfcService Init Failed

Tomas_Parizek — Thu, 27 Jun 2024 11:41:27 GMT

Hello Stephan_B,

Can you share more details about your setup.... what Raspberry and OS are you using, please?

It seems that the latest Raspberry has an issue with our PN7160, our SW team is already checking that.

Tomas

Re: OM27160 raspberry i2c NfcService Init Failed

Stephan_B — Mon, 08 Jul 2024 11:50:27 GMT

Hello @Tomas_Parizek
I used a tried with a Raspberry Pi 5 as well as with a Raspberry Pi 3 B+. I tested both 32 and 64bit versions. Though when compiling for the 64bit version I needed to correct some of the code as I later found in the 64bit patch file.
I then assumed, that it is a HW problem, as I can see the I2C signals being sent with the oscilloscope. So I bought another EvalBoard, but it still not working.
"NfcService Init Failed"
"Leaving ..."
is all i get. As for the OS, I am working with Rasbian. I use the Raspberry Shield, that came with the Developmentkit and setup/installed everything via the Terminal (SSH/Putty)

Regards Stephan

Re: OM27160 raspberry i2c NfcService Init Failed

Stephan_B — Tue, 09 Jul 2024 08:11:12 GMT

Hello @Tomas_Parizek

Today, I got my setup working. I had to install an old Rasbian version (bullseye) and then it compiled without error and it works.

Would have been nice to have some pointers in the "get started guide" concerning which OS / HW versions this has been tested with.

Regards

Stephan

Re: OM27160 raspberry i2c NfcService Init Failed

Tomas_Parizek — Tue, 11 Feb 2025 12:38:02 GMT

***UPDATE***

--> See the fix

https://community.nxp.com/t5/NFC-Knowledge-Base/Porting-PN7160-NCI2-stack-to-Raspberry-Pi-5-OS-Bookworm/ta-p/1977521

We see that the PN7160 returns "NfcService Init Failed" for latest Raspian Linux version 12 (Bookworm).

For Linux version 11 (bullseye), the issue should not occur.

NXP is working to fix it as as soon as possible.

Re: OM27160 raspberry i2c NfcService Init Failed

KennyG — Tue, 05 Nov 2024 16:24:12 GMT

Has this been resolved to work on the latest Pi releases?

Thanks!

--Ken

Re: OM27160 raspberry i2c NfcService Init Failed

Tomas_Parizek — Mon, 02 Dec 2024 11:21:18 GMT

Hello KennyG and Stephan_B,

The solution is already in place. My colleague will share it via NXP NFC Knowladge base.

I will also update the link here soon.

Tomas

Re: OM27160 raspberry i2c NfcService Init Failed

mikytron98 — Sat, 23 Aug 2025 02:16:01 GMT

Hello @Tomas_Parizek

I am in a similar position as the above. I found the patch file and still running into issues when I run nfcDemoApp poll. When I run sudo i2cdetect -y 1 it shows none of the pins are detected. I determined the raspberry pi is not fried because I am using with other setups and it worked. So what other things can I try to patch to get the pi to detect the NFC controller?

Re: OM27160 raspberry i2c NfcService Init Failed

mikytron98 — Sat, 23 Aug 2025 02:27:54 GMT

For context, I am getting the same:

NfcService Init Failed

and have been following the Elechouse Quick start guide.

I am access the Pi via SSH from my mac that has M2 chip. Some additional context that can help pinpoint what is going on here.

Re: OM27160 raspberry i2c NfcService Init Failed

Tomas_Parizek — Wed, 27 Aug 2025 06:05:04 GMT

Hello @mikytron98 ,

Can you share more details about your setup? Which Raspberry Pi and Linux version are you using?

Tomas

Re: OM27160 raspberry i2c NfcService Init Failed

mikytron98 — Tue, 09 Sep 2025 15:25:54 GMT

Setup Details:

Raspberry Pi 5 running Debian (kernel 6.12.25+rpt-rpi-2712, aarch64)
Using linux_libnfc-nci library for NXP NFC chips
I2C enabled with buses at /dev/i2c-1, /dev/i2c-13, /dev/i2c-14

Current Issue:

sudo i2cdetect -y 1 shows no devices (all "--")
nfcDemoApp compiles but fails with "NfcService Init Failed"
Also getting C++ std::out_of_range exception in strings.cpp

The I2C scan suggests no NFC hardware is detected on bus 1. Either the module isn't connected properly or I2C isn't configured correctly for the NFC chip.

I made progress when I used a forked branch of the source code but it seems you guys have a version of the source code that works saved privately somewhere based on another conversation I saw @danielchen reply in