AnsweredAssumed Answered

MKW30Z IAR 7.5 KSDK_1.3.0 How OTAP updating can preserves unit serial numbering

Question asked by Lucian Firan on Nov 4, 2016
Latest reply on Feb 8, 2017 by Lucian Firan
KW40Z_Connectivity_Software_1.0.1 (KSDK_1.3.0)
 
Programming a series of MKW30Z devices needs some sort of a serial number mechanism.

 

The Kinetis MKW30Z programmers implement this:
U-Cyclone -> AUTOMATIC SERIAL NUMBER MECHANISM -> 1 to 16 bytes in length
and
Segger ARM -> Serial number programming -> 1 to 4 bytes

 

Let's assume a 4 bytes SN works for both and the best way to store it is inside device_info BLE profile db.

 

The SN should be store to a specific address most likely i think.

 

When an OTAP update is done using external SPI flash either the:
- generic image data chunk (with that specific address) will be change in such a way to keep the specific device serial number
- or the boot loader will not erase the SN area at re-flash.

 

Witch one is the best approach ?

 

It is already implemented or how can this be done ?

Outcomes