I confirm this is a bug, and have filed SDSCM00050227 to track it. If possible (I don't know the semantics of IFR), work around the bug by splitting the write of IFR into two parts:
IFR |= 0xff00; IFR |= 0x00ff;
I confirm this is a bug, and have filed SDSCM00050227 to track it. If possible (I don't know the semantics of IFR), work around the bug by splitting the write of IFR into two parts:
IFR |= 0xff00; IFR |= 0x00ff;