The EEPROM is internal to the SIP module, so you cannot access it.
Are you talking about the SoC?
As far as I know, the minidriver and programming protocol which runs over HCI is the only way to load your image onto the EEPROM on the SIP.
I got it. Another question, if our EEPROM is empty, should we use recover procedure or normal download procedure ?
So you are using the SIP module.
The EEPROM is programmed automatically by the SDK and/or command line loader.exe process.
Essentially, the application will be automatically loaded to EEPROM initially, then to internal RAM on boot up for execution.
What happens is that the SDK downloads the minidriver to RAM and then runs it, it then pushes the code over the HCI uart to the minidriver which will then write to EEPROM.
There is no other way to write to EEPROM. All intial programming needs to occur over the HCI UART and use this process.