I have a OM27462CDK which comes with a PN7462 microcontroller. Currently, I am studying the user manuals and analyzing the firmware examples provided by NXP.
It seems the firmware uses some parameters stored in EEPROM. I had to flash a binary file into the EEPROM, so the examples could work.
Do I really need to use these parameters from EEPROM? I noticed they're used by firmware to initialize peripherals. Can't I initialize all the microcontroller's peripherals just by code (like we do in a STM32)? I also read somewhere the EEPROM have specific layout to set the parameters, and its version must be compatible with firmware. So it seems to me this whole EEPROM thing is just an arbitrary scheme made up by some NXP's developer(s), but is not REALLY necessary for the chip to work.
Thank you in advance. Best regards.
Solved! Go to Solution.
Hi @lucasj
I agree with you. If the parameters are fixed values, you can get the actual values directly. The reader library is for general purpose with many EEPROM values. cockpit can modify them very easily.
NFC Cockpit is an intuitive graphical user interface that lets you configure and adapt IC settings without writting a single line of software codes
Regards
Daniel
hello DANIELCHEN
how to modify the rom bin files of PN7462? is NFC-COCKPIT okay? we want to modify vid .
Hi @kevin15
You can modify EE.bin with cockpit. Please refer to the quick start guider for more details.
Regards
Daniel
hello Danielchen
Excuse me, I need to write CRP_00.BIN and DRP_00.DAT files for pn7462 in large quantities. Is there any quick way?
Thank you!
Hi @lucasj :
PN7462 EEPROM is composed by 6 pages. Pages 1 to 5 are reserved for PN7462 IC configuration and can be updated by user.
As you can see from the above picture, lots of key data stored in EEPROM. ROM BOOT depends on the EEPROM parameters, RF configuration data.... all saved in it. Some important develop tool, such as cockpit tool, also depends on the EEPROM data.
The EEPROM parameters can save in a xml file, users can modify the xml file, and xml file can also be turned into a Bin file, and burn into the EEPROM.
So this structure is very convenient to use. I think it is necessary to work.
Regards
Daniel
@danielchen, thank you for your answer, you made some valid points. I do believe now some EEPROM parameters are necessary. But I'm still uncertain that ALL the hardware configuration must be in EEPROM (like GPIO, serial interfaces, etc), because most of them are used by software APIs. For instance, the example PN7462AU_ex_phExHif initializes the HSU interface as shown below. The gpkphCfg_EE_HW_HIF structure takes the values directly from EEPROM.
Since the EEPROM parameters are passed to the APIs by software, couldn't I just replace them for the actual values I want to use (as shown below)? Do I really need to generate a new EEPROM binary everytime I want to change some peripheral's configuration?
Hi @lucasj
I agree with you. If the parameters are fixed values, you can get the actual values directly. The reader library is for general purpose with many EEPROM values. cockpit can modify them very easily.
NFC Cockpit is an intuitive graphical user interface that lets you configure and adapt IC settings without writting a single line of software codes
Regards
Daniel