PN7462 Current Measurement (Dev kit, DoorAccessFw)

cancel
Showing results for 
Search instead for 
Did you mean: 

PN7462 Current Measurement (Dev kit, DoorAccessFw)

Jump to solution
129 Views
Contributor III

Hi

We are currently evaluating/prototyping PN7462 for a battery powered application and a key requirement is to be able to achieve very low power consumption when only polling for cards (target is 30uA range when polling for cards which we believe is theoretically achieveable).

Firmware Configuration

We are using DoorAccess example firmware on PNE7462C evaluation board. Using default settings of the firmware which indicate that LPCD is enabled, the only change we have made is:

1. Defined PHFL_ENABLE_STANDBY to enable Standby mode

Hardware Modifications

Following changes have been made to the board to get rid of anything otehr than PN7462 driving current from the supply:

1. There are 3 leds on the supply lines of 3.3v, 5v, VBUS - these have been disconnected by removing corresponding resistors as shown below:

pastedImage_2.pngpastedImage_3.png

2. Also, L10 and L11 have been removed to disconnect the on board LDO and to be able to supply 5v and 3.3v externally and measure the current draws if needed:

pastedImage_4.png

Hardware Setup

1. Board is powered by providing external 5v to pin 2 of JP2 (JP2 can be seen in above image). Current drawn from this external 5v is measureed

2. VBUS is set to 5v by linking 5v and VBUS pins of JP5 through as shown below:

pastedImage_8.png

3. 3.3v is only provided when PN7462 firmware is programmed and is removed otherwise. This means all the current draw during testing is through the 5v supply

The firmware configuration used is the "Release" one, PN7462 is programmed and run without the debugger.

Issue/Observation

With the above setup, the average current draw seems to be about 365uA which of course is too high.

Please note that the average current through JP1 is about 37uA (Peak ~200mA). This is the current going into TVDD_IN for the RF transmitter which seems to be within specs.

The rest of about 325uA is the problem. Please could you let us know what needs to be done to bring this current down? We were hoping there would be a ready made example demonstrating low power consumption and it would be possible to test that on the devleopment kit.

Thanks

Tags (2)
0 Kudos
1 Solution
16 Views
Contributor III

While we await for the support, we have done some further investigation and here are details to share:

Hardware Changes

Continuing the setup as mentioned in the earlier post, we modified the PN7462C board to power it from 3.3v (instead of 5v) as per the instructions in the user manual. Basically, ended with the following power supply configuration:

pastedImage_1.png

Firmware Changes

This requried following macro to be defined in the DoorAccess example firmware:

#define PHFL_ENABLE_TVDD_3V_MON

Results

With these changes, we are seeing the following values for current draws @ 3.3v:

1. PVDD_IN, PVDD_M_IN combined: 108uA continuous

2. VUP_TX, TVDD_IN, TVDD_OUT combined: 25uA average

3. VBUS, VBUS_P combined: 123uA continuous

4. Total measured current: 250uA - 260uA average

Any help to resolve the current consumption issue willbe highly appreciated. This is a decisive factor whether or not to go for NXP NFC solution.

Thanks

View solution in original post

0 Kudos
3 Replies
17 Views
Contributor III

While we await for the support, we have done some further investigation and here are details to share:

Hardware Changes

Continuing the setup as mentioned in the earlier post, we modified the PN7462C board to power it from 3.3v (instead of 5v) as per the instructions in the user manual. Basically, ended with the following power supply configuration:

pastedImage_1.png

Firmware Changes

This requried following macro to be defined in the DoorAccess example firmware:

#define PHFL_ENABLE_TVDD_3V_MON

Results

With these changes, we are seeing the following values for current draws @ 3.3v:

1. PVDD_IN, PVDD_M_IN combined: 108uA continuous

2. VUP_TX, TVDD_IN, TVDD_OUT combined: 25uA average

3. VBUS, VBUS_P combined: 123uA continuous

4. Total measured current: 250uA - 260uA average

Any help to resolve the current consumption issue willbe highly appreciated. This is a decisive factor whether or not to go for NXP NFC solution.

Thanks

View solution in original post

0 Kudos
16 Views
NXP TechSupport
NXP TechSupport

Hi

you can check the following thread

PN7462AU -Hard Power Down Mode 

How to set LPCD ? 

Also please check the following application note

https://www.nxp.com/docs/en/application-note/AN11785.pdf 

Have a good day

take care

0 Kudos
16 Views
Contributor III

Hi

Thanks for the response.

I took alot of time & effort to present with logical details and explanation of the setup and the issues. You can imagine that in a week since I posted the query, I already have gone through every single post related to PN7462 on the forum.

My question was very specific about the ability to measure current on the development board. Provision of Gerber files and schematic PDF of the development board would have been the first and most important step to resolve this. Anyways I have sorted that out and would be happy to anyone else looking for the answers.

The issue now is the apparent inability of PN7462 LPCD to wake up the processor on card detection. Please help with that query https://community.nxp.com/message/1326059?commentID=1326059&et=watches.email.thread#comment-1326059  if you are able to.

Thanks

0 Kudos