Skip to main content
Version: Next

3.4.8.1N32G4xx Series UID Reading Specification

tip

Affected Chip Models:

  • N32G401 Series
  • N32G430 Series
  • N32G432 Series
  • N32G435 Series

Latest SDK Versions at the Time of Document Compilation:

  • N32G401 Series: Nations.N32G401_Library.2.1.0
  • N32G430 Series: Nations.N32G430_Library.2.1.0
  • N32G432 Series: Nations.N32G43x_Library.2.3.0
  • N32G435 Series: Nations.N32G43x_Library.2.3.0

1.Reason for Modifying the UID Reading Method​

Based on the implementation of the UID acquisition API in the latest official SDK released by Nations Technology, as well as confirmation from communications with the chip manufacturer, the UIDs of currently supplied chips may reside at different memory addresses depending on chip revisions.

This adjustment is implemented to ensure normal operation of UID-dependent functions such as Matrix Authorization.

53a3b341b203fc0837b34c6a830ee101

2.Details about the reading method​

Original UID Reading Method (Before Adjustment):

For all chips in the above series, UID data was retrieved from a fixed memory address: 0x1FFF_F710, with a data length of 12 bytes.

2.1Processing details for specific chip models​

Updated UID Reading Method (After Adjustment)

N32G401 Series​

  1. First read 12 bytes of data from address 0x1FFF_F510.
  2. If all 12 bytes read are 0xFF, the UID at 0x1FFF_F510 is deemed invalid.
  3. The programmer tool will then read 12 bytes of data from address 0x1FFF_F710. Data from this address is treated as valid UID regardless of its content and used for all UID-related functions.
  4. c8998ef67bf47c238fd3aaccfab680cf

N32G430 Series​

The UID reading procedure is identical to the N32G401 Series.

N32G432 Series​

  1. First read 4 bytes of data from address 0x1FFF_F270.

  2. If all 4 bytes read are 0xFF,,the UID at 0x1FFF_F270 is deemed invalid.

    • The programmer tool will read 12 bytes of data from address 0x1FFF_F710. This data is treated as valid UID and adopted for UID-related functions, with no further reads from 0x1FFF_F270.

  3. If the 4-byte data read from 0x1FFF_F270 contains any value other than 0xFF.

    • The address 0x1FFF_F270 is recognized as holding a valid UID. The tool reads a full 12-byte UID from this address for all UID-related functions, and skips reading 0x1FFF_F710.

N32G435 Series​

The UID reading procedure is identical to the N32G432 Series.

caution

Recommendations for Developers on UID Retrieval in Firmware

To guarantee compatibility with programmer tool functions relying on UID (e.g., Matrix Authorization), developers are strongly advised to take one of the following actions:

  1. Update your SDK to the latest version specified above, and leverage the native UID acquisition functions provided within the SDK to retrieve UID data; OR
  2. Revise the implementation of UID-related logic in your firmware to align with the updated UID reading rules adopted by the programmer tool.