Thank you for the information.
I have set RST_N pull-down value to 0 using the phhalSysSer_OTP_SecrowConfig() as below
phhalSysSer_OTP_SecrowConfig (PH_SYSRV_SET_DATA, &SecRow);
And for the RST_N pin value I was thinking to use a GPIO from our external Host to be given to the RST_N pin value so that when we make it LOW it will go to HPD mode and when we make it high it will come out of HPD.
It can be done right?
As long as the timing is respected, I do not see any problem. Please refer to table 77 of the datasheet for this information: https://www.nxp.com/docs/en/data-sheet/PN7462.pdf
Hope it helps.
Thank you for the reply.
Its given that RST_N Low pulse width time should be minimum 10 micro seconds. that means i need to make it low for a minimum of 10 micro seconds for it to go to the HPD mode right?
In our custom PN7462 board,
Normal active mode its taking around 32mA and when we make RST_N pin value low its taking still 14mA which says that its not going to HPD mode where it should take around 12uA as per datasheet.
I will check it in evaluation board.
Before that a quick question
Earlier i had tried putting my application in standby mode there it had gone to stand by mode and current consumption was very low as expected but the issue i faced there was my High speed UART peripheral stopped working .
i will explain my application briefly
when i tried putting my application in stand by mode by using PHFL_ENABLE_STANDBY and i flashed the code.
once i flash the code i am unable to flash the code once again using the my LPCLink-2 programmer.
what is the issue there? once we put the code in standby mode does it permanently disable the programming interface?
According to the documentation, only some modules are working to maintain the operation of the Power Control Unit, a set of registers and LFO (which operates in the KHz range). Nevertheless, it can be woken up by a corresponding source, such as a host interface (HSUART, SPI, I²C).