I need to protect my redpitaya custom application.
To do that I need to find in, redpitaya information, an univocal serial number
or alternatively external eeprom map to find free space in external i2c eeprom in which to save protection codes...
other method?
may you help me?
best regards,
Alessandro Maffei
how to protect my redpitaya custom application
-
- Posts: 10
- Joined: Fri Jun 05, 2015 10:49 am
-
- Posts: 799
- Joined: Sat May 23, 2015 5:22 pm
Re: how to protect my redpitaya custom application
The ZYNQ chip has a unique identifier called DNA. Here is how it's used by the Red Pitaya ecosystem:
https://github.com/RedPitaya/RedPitaya/ ... a_hk.v#L59
https://github.com/RedPitaya/RedPitaya/ ... n.cpp#L412
I also have a small IP core that can be also used to read the DNA identifier :
https://github.com/pavel-demin/red-pita ... eader_v1_0
https://github.com/RedPitaya/RedPitaya/ ... a_hk.v#L59
https://github.com/RedPitaya/RedPitaya/ ... n.cpp#L412
I also have a small IP core that can be also used to read the DNA identifier :
https://github.com/pavel-demin/red-pita ... eader_v1_0
-
- Posts: 1441
- Joined: Sat Jun 07, 2014 12:49 pm
- Location: Königswinter
Re: how to protect my redpitaya custom application
If your plan is to achieve access control on a per-device basis, the DNA value is the best option.
For the record, as of now not much of the space in the external eeprom is allocated. It contains the calibration settings from 0x0000 - 0x0040 and the factory calibration from 0x1c00 - 0x1c40.
For the record, as of now not much of the space in the external eeprom is allocated. It contains the calibration settings from 0x0000 - 0x0040 and the factory calibration from 0x1c00 - 0x1c40.
jadalnie klasyczne ekskluzywne meble wypoczynkowe do salonu ekskluzywne meble tapicerowane ekskluzywne meble do sypialni ekskluzywne meble włoskie
Who is online
Users browsing this forum: No registered users and 132 guests