EG915U-EU eUICC chip appears to be in factory-virgin state

IoT Modules LTE Standard Module
1

Model: EG915U
Firmware: EG915UEUABR03A01M08

AT+QDSIM=10 works (eUICC slot accessible)
AT+QESIM=“eid” returns: +QESIM: “eid”,1,“2”,“FFFF”

The eUICC appears present but returns FFFF instead of
a 32-character EID.

Questions:

  1. Does this unit need eUICC activation/provisioning?
  2. Is there a specific firmware or NV item to enable it?
  3. Is the EID pre-programmed or does it need factory setup?
2

Dear @Jenildo,

Thank you for reaching out.

The EID is a unique hardware identifier stored inside the eUICC itself. It is pre-programmed by the eUICC manufacturer during production and it does not depend on network activation or profile provisioning. Provisioning only affects downloading and managing profiles, not whether an EID exists.

If AT+QESIM=eid returns FFFF, it means the module did not obtain a valid EID response from the eUICC on the selected slot. This is typically caused by one of the following:

  • the eUICC component is not actually populated on that unit or the selected slot is not routed to a real eUICC
  • the eUICC interface is not communicating correctly (contact, routing, or electrical signaling on VCC/CLK/RST/IO)
  • the platform you are using has an eSIM slot option but does not include a programmed eUICC by default

There is no NV item that would create an EID. If a real eUICC is present and reachable, it will return a valid 32-character EID regardless of whether any profile is downloaded.

To confirm the situation, please share the full outputs below:
ATI
AT+QGMR
AT+QDSIM?
AT+QCCID
AT+QESIM=?
AT+QESIM=list,0
AT+QINISTAT

Also please confirm whether you are using an EVB or a third-party board, and whether an actual eUICC (MFF2 eSIM chip) is physically populated on the hardware.

Once we have these, we can confirm whether the eUICC is present and responding, or whether the hardware does not have a programmed eUICC installed.

Best Regards,
Aghelan