Hello,
I am trying to use the PN7150 with a Silicon Lab Thunderboard BG12 as a device host. For the moment I am using evaluation boards (Silabs Thunderboard and OM5578/PN7150 Kit for Raspberry Pi)
But the end product will be a custom board.
The VBAT / PVDD is powered by the Thunderboard's VMCU and I also connected the GND and SDA / SCL pins with a pull-up resistor.
I'm assuming my I2C is working, when I spy on the bus trying to send an NCI command I can see the start / stop condition and the destination address.
Following the PN7150 user manual (User Manual 10936) I tried to send CORE_RESET_CMD then CORE_INIT_CMD to address 0x28 but I still get a NACK which ends the communication.
My packets look like : CORE_RESET_CMD[] = {0x20, 0x00, 0x01, 0x00}
CORE_INIT_CMD[] = {0x20, 0x01, 0x00}
As I said when I spy the I2C bus I can see the targeted ADDR then a NACK and a stop condition. My data corresponding to NCI commands never shows up.
I'm pretty sure I miss something, it's the first time I have to use NCI protocol and NXP device, so I'm still a bit lost.
I guess I need to flash the NFCC with the NXP NCI Library.
But how can I do it with my custom board ? Is it mandatory to use MCUXPresso IDE ? Am I missing something else ?
I apologize if my questions are answered in NXP documentation.
Thanks in advance,
Vincent B
Thank you for your interest in our products, we really appreciate it.
My apologies for this but, I'm afraid the support of this is out of our scope.
Our PN7150 board support is only for our boards listed in the NXP-NCI MCUXpresso example (AN11990)
I'm sorry for the issues this may cause.
My recommendation is to be sure, the current sent by the Thunderboard's VMCU pin. This is to ensure the board is working properly. For this, you can check the PN7150 Datasheet Check the Quick Reference Data (Section 5).
Also, be sure the required pins are properly connected. Check HW Setup, Section 2 from AN11990. According to User Manual 10936 , it is mandatory to know the state of the IRQ pin.
MCUXpresso is designed only to work with NXP products, including MCUs. The migration of the Library has to be performed by the development team.