This page contains a Flash digital edition of a book.
Page 52


www.us-tech.com


Complex Serialization: An Approach for Today


By Nader Shehad, BPM Microsystems, Houston, TX


customer-supplied data patterns such as Intel HEX, Motorola S- record, POF and other file formats into blank semiconductor devices. Traditionally, a data pattern is loaded into the device programming software by an operator and is subse- quently transferred into all devices during a programming session. This method quickly programs a large number of devices with identical data content and satisfies the requirements of the majority of pro- gramming applications. But what if each device requires unique data?


D


Serialization is a difficult challenge, but the novel approach of using an external management application can make serialization manageable and reliable.


In the device programming


industry, serialization is the process of writing unique data to each pro- grammed device. It can be used to program basic numeric serial num- bers to a single device address and can be used to program more com- plex data such as MAC addresses,


evice programming systems are a key resource in the elec- tronics industry for writing


encryption keys, GUIDs and random- ization seeds to several device addresses on each device.


Serialization Data Because of the unique nature of


the serialization data, one of the


that only require a single numeric serial number that is incremented for each device, the programming application itself can be the source of the serialization content. An opera- tor can specify the starting serial number, the serial number address,


ated by proprietary customer algo- rithms or stored on third-party cus- tomer databases located on remote servers that cannot be embedded into the programming application. Security is often a concern as the serialization data could be sensitive intellectual property (IP) that must be encrypted to prevent unautho- rized access and copying. For these reasons, there needs to be a mecha- nism whereby the device program- ming application can invoke an external customer-written applica- tion to obtain the serialization data for each programmed device in a secure and flexible way.


Traditional Approach The traditional approach to


Model 2800 programmer.


major challenges of such program- ming is obtaining the correct data for each device. Any standard device programming software is readily able to program static data patterns into a Device Under Test (DUT), however injecting the serialization data into the data pattern “on the fly” on a per device basis requires a more sophisticated approach. For serialization applications


as well as other parameters to ensure that each device attains a unique serial number programmed at the correct device address. A simple approach might suffice


for the simplest of serialization appli- cations, but quickly breaks down when multiple unique pieces of data or non-numeric data must be pro- grammed into each DUT. Complex serialization data is typically gener-


complex serialization has been to allow the programming application to invoke an External Serialization Program (ESP) to obtain the seriali- zation data required for each device. The ESP is a customer-written appli- cation that could potentially gener- ate serial numbers algorithmically, communicate with remote systems/ databases, maintain a log of its oper- ations, and have various user options to configure how it behaves. The pro- gramming application is not aware how the ESP generates the serializa- tion data, but only knows how to retrieve the data in a fixed, agreed-


Continued on page 54


December, 2012


Page 1  |  Page 2  |  Page 3  |  Page 4  |  Page 5  |  Page 6  |  Page 7  |  Page 8  |  Page 9  |  Page 10  |  Page 11  |  Page 12  |  Page 13  |  Page 14  |  Page 15  |  Page 16  |  Page 17  |  Page 18  |  Page 19  |  Page 20  |  Page 21  |  Page 22  |  Page 23  |  Page 24  |  Page 25  |  Page 26  |  Page 27  |  Page 28  |  Page 29  |  Page 30  |  Page 31  |  Page 32  |  Page 33  |  Page 34  |  Page 35  |  Page 36  |  Page 37  |  Page 38  |  Page 39  |  Page 40  |  Page 41  |  Page 42  |  Page 43  |  Page 44  |  Page 45  |  Page 46  |  Page 47  |  Page 48  |  Page 49  |  Page 50  |  Page 51  |  Page 52  |  Page 53  |  Page 54  |  Page 55  |  Page 56  |  Page 57  |  Page 58  |  Page 59  |  Page 60  |  Page 61  |  Page 62  |  Page 63  |  Page 64  |  Page 65  |  Page 66  |  Page 67  |  Page 68  |  Page 69  |  Page 70  |  Page 71  |  Page 72  |  Page 73  |  Page 74  |  Page 75  |  Page 76  |  Page 77  |  Page 78  |  Page 79  |  Page 80  |  Page 81  |  Page 82  |  Page 83  |  Page 84  |  Page 85  |  Page 86  |  Page 87  |  Page 88  |  Page 89  |  Page 90  |  Page 91  |  Page 92  |  Page 93  |  Page 94  |  Page 95  |  Page 96