How do you know this is an EMC issue and not a logical/protocol level one?
NFC is involved in MagSafe, and I believe it’s actually the same chip (just different antenna interfaces) that’s also used for Apple Pay, even the non-contactless/in-app version.
> wireless chargers from “temporarily” disabling iPhone 15 NFC chips.
Wireless charging is high power. NFC is low power. They both operate in the same frequency range. When charging, the NFC receiver shall be turned off or disconnected from the antenna so that it does not get saturated.
At least my MagSafe wallet uses NFC to be identified by my iPhone.
Apple’s contactless (car/building) key format also seems to be using the Secure Element to some extent (which lives in the contactless chip), so I wouldn’t be surprised if there’s a pretty direct connection between these two subsystems that has a logic bug somewhere.
In other words, I don’t think that the ISO 14443 chip is physically getting fried, but rather that the car does some low-level handshake that gets some hardware element of the phone into a persistent bad state.
The Secure Element runs its own firmware and software and has its own storage, unlike the Secure Enclave, which is under much more direct control by Apple and loads its software from the main CPU/flash memory, so is harder to persistently “brick” logically.
The antenna for the NFC and for the wireless charger are different, and not even close to the same frequency. NFC is 13.56 MHz; wireless charging (which is standard Qi, not MagSafe, as far as I can tell on the BMW) is sub 300 kHz (it varies).
Apple (based also on the SAR issue) seems to be cutting corners big in this area.
Why not BMW ? Because there are norms which tell you how much you can transmit and the transmitter usually has maximum power.