UPGRADE YOUR BROWSER

We have detected your current browser version is not the latest one. Xilinx.com uses the latest web technologies to bring you the best online experience possible. Please upgrade to a Xilinx.com supported browser:Chrome, Firefox, Internet Explorer 11, Safari. Thank you!

cancel
Showing results for 
Search instead for 
Did you mean: 
Visitor dagucas
Visitor
2,967 Views
Registered: ‎08-26-2014

Device DNA uniqueness

Jump to solution

Hello all,

I've read in the ug470_7Series_Config document the following paragraph:

The 7 series FPGA contains an embedded, device identifier (device DNA). The identifier is nonvolatile, permanently programmed by Xilinx into the FPGA, and is unchangeable making it tamper resistant. Each device is programmed with a DNA value that is most often unique. However, up to 32 devices within the family can contain the same DNA value.

 

Does it means that this number maybe unique within a family but Xilinx doesn't guarantee it o are they really unique? In case DNAs are not unique, is it possible to have a track of them when you buy Zynq devices so that you can be sure that there are not two devices in our products sharing this DNA?

 

Thanks in advance!

 

0 Kudos
1 Solution

Accepted Solutions
Scholar austin
Scholar
3,727 Views
Registered: ‎02-27-2008

Re: Device DNA uniqueness

Jump to solution

d,

 

Contact your local Xilinx distributor or sales office to discuss custom screen requests.  If the volume is there, then that may be considered.


There is also a customer use, unprogrammed set of efuses that you could use to uniquefy the DNA (use an addition set of efuses programmed at a hash+n of the part -- read the dna, calculate a has, and a rolling value incremented for each part, regardless of the DNA value...)

 

 

Austin Lesea
Principal Engineer
Xilinx San Jose
0 Kudos
12 Replies
Scholar austin
Scholar
3,728 Views
Registered: ‎02-27-2008

Re: Device DNA uniqueness

Jump to solution

d,

 

Contact your local Xilinx distributor or sales office to discuss custom screen requests.  If the volume is there, then that may be considered.


There is also a customer use, unprogrammed set of efuses that you could use to uniquefy the DNA (use an addition set of efuses programmed at a hash+n of the part -- read the dna, calculate a has, and a rolling value incremented for each part, regardless of the DNA value...)

 

 

Austin Lesea
Principal Engineer
Xilinx San Jose
0 Kudos
662 Views
Registered: ‎03-03-2017

Re: Device DNA uniqueness

Jump to solution

Wow, I just got a batch of Kintex 7 xc7k160tffg676-1 devices and have found 2 so far with the same device DNA value.   I didn't think this was possible.   I could use some help in another way to uniquely identify these fpgas.

 

Thanks.

Tim

0 Kudos
651 Views
Registered: ‎09-17-2018

Re: Device DNA uniqueness

Jump to solution

Well,

Untill you use the other user efuses as suggested, you could just not use the part with the duplicate DNA.  Not an elegant solution, and not free (as you lose the use of a device), but certainly quick to implement, and simple.

Out of curiousity, how many devices were delivered that resulted in two identical DNA codes?  The whole problem with anything like this is what I refer to as the tyrany of small numbers - too few samples and the statistics are meanigless.  But even one datapoint is useful to establish a bound.

l.e.o.

0 Kudos
647 Views
Registered: ‎03-03-2017

Re: Device DNA uniqueness

Jump to solution

I am in the process of getting them programmed now and I have found 2 so far. 

I wasn’t aware of the user efuse bits.   I like the idea of using these.   What I can’t seem to find through google is how to access these fuse bits in RTL so I can read it back when the fpga is configured and in the field.  

Do you know how to do this?

Thanks

Tim

0 Kudos
640 Views
Registered: ‎03-03-2017

Re: Device DNA uniqueness

Jump to solution

Oh wait, I see that there are 8 LSB bits that are different between the FPGAs, but in my RTL where I use a DNA_PORT instance to read the device DNA I don't seem to have access to those bits.   I think I remember reading about this issue when I first developed a way to read the device DNA values.

0 Kudos
637 Views
Registered: ‎09-17-2018

Re: Device DNA uniqueness

Jump to solution

ug470 and,

Fuse_user, page 311 of ug953

l.e.o.

0 Kudos
633 Views
Registered: ‎03-03-2017

Re: Device DNA uniqueness

Jump to solution

@lowearthorbit ,

   Thanks, I see.

   Out of curiosity have you ever found a way to read the last 7 LSBs of the device DNA during run-time (i.e. without using JTAG)?   Or is this not allowed?

Thanks.

Tim

0 Kudos
631 Views
Registered: ‎09-17-2018

Re: Device DNA uniqueness

Jump to solution

Not supported is more accurate,

So basically, no, I have not.

l.e.o.

 

0 Kudos
618 Views
Registered: ‎03-03-2017

Re: Device DNA uniqueness

Jump to solution

I see thanks.

Just to let you know, 8 out of 12 FPGAs are not unique for these 57 bits.   Seems like this should not have happened.

Tim

0 Kudos
615 Views
Registered: ‎09-17-2018

Re: Device DNA uniqueness

Jump to solution

I think you should file a service request,

Sounds like a failure to process these devices properly.  Of course, Xilinx has an out, based on their official response (it is not guaranteed to be unique), but the code is supposed to identify the lot, wafer, xy die, as well as other information.  Looks like these devices would not be traceable, and that should bother Xilinx.

(as a customer, it sure bothers me)

l.e.o.

 

0 Kudos
138 Views
Registered: ‎03-03-2017

Re: Device DNA uniqueness

Jump to solution

Interestingly we just got in a batch of 25 boards that each have a XC7A75TFGG676 device on them, and I am seeing full on all 64 bits being the same between various FPGAs.   I thought this for sure wasn't supposed to be possible.

0 Kudos
136 Views
Registered: ‎03-03-2017

Re: Device DNA uniqueness

Jump to solution

Disregard that, I was looking at DNA_PORT, not FUSE_DNA.

0 Kudos