Code image or the IQRF OS change file must be stored in the external EEPROM using a series of Extended Write commands.
When Custom DPA Handler should be uploaded using LoadCode command then a .hex file containing the handler code must be stored in the external EEPROM. See LoadCode and Custom DPA Handler Code at .hex File for more details about decoding the file.
When IQRF plug-in containing an e.g. newer version of DPA or IQRF OS patch is to be loaded then the content of the .iqrf file has to be stored in the external EEPROM. See LoadCode for more details about decoding the file.
If IQRF OS change is to be executed then a special handler must be active and the corresponding .bin file containing the IQRF OS change data must be stored in the external EEPROM. See IQRF OS Change for more details.
When storing the data in the external EEPROM make sure that other data are not overwritten. That could be another upload data, handler operation data, or IO Setup. Precise planning of the external EEPROM content is recommended.
It is also recommended to plan the whole upload or change process in the way that all required data (active handler, IQRF OS change handler, IQRF plug‑in DPA, IQRF OS change file) are first stored in the external EEPROM and then used to minimize the code upload time. Some of the items at the external EEPROM may take up to a few kilobytes and it takes a considerable time to store them in the even small network.