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:
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:
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:
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
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:
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
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:
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
