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?
