AnsweredAssumed Answered

bogus default values in Init_NFC

Question asked by Marc Lindahl on May 18, 2014
Latest reply on Jun 9, 2014 by Marc Lindahl

The Init_NFC component defaults with some out of range values.  Naturally the user of these 'expert' components assumes that the default instantiation, while possibly not optimized, should at least function correctly.  Such is not the case here.  These parameters discussed below should have their defaults changed to valid values.  Further, this and all other PE components should be reviewed by the PE teams to insure there are no other invalid values.  In the case of the NFC, they are in a much better position to do so, due to the paucity of documentation on the actual functioning of the peripheral.

 

Settings->ECC SRAM address.  This defaults to 0x1FF, which is out of range of the NFC's SRAM buffer.  It might actually alias to another buffer, or to an empty area, it's impossible to tell from the chip documentation.  In any case, the maximum legal value is 0x11F.

 

Settings->Cache swap address 1/2.  These default to 0x7FF, which are out of range of the SRAM buffer.  Its not clear what effect it has when this is out of range, as there is very little about these settings in the documentation.  It could be that it aliases to another of the NFC's SRAM buffers.  The maximum legal value again is 0x11F, at least that's the best I can discern, as it appears from example code that this address is also a byte address divided by 8.

Outcomes