Difference between revisions of "UHD Device Eraser and Certificates of Volatility"
(→UHD Device Eraser Utility: add info from README) |
(→USRPs: add X440 LOV) |
||
| (10 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
| − | ==Application Note Number== | + | ==Application Note Number and Author== |
| − | '''AN-111''' | + | '''AN-111''' by Michael Dickens |
| − | + | ||
<!-- Internal use only: please do keep this updated! | <!-- Internal use only: please do keep this updated! | ||
==Revision History== | ==Revision History== | ||
| Line 19: | Line 18: | ||
==UHD Device Eraser Utility== | ==UHD Device Eraser Utility== | ||
| − | The ''uhd_device_eraser'' utility overwrites all non-volatile memory from any Ettus | + | The ''uhd_device_eraser'' utility overwrites all non-volatile memory from any Ettus device supported by it: most USRPs, OctoClock, and daughterboards. |
| − | Note that any ''volatile'' memory on the | + | Note that any ''volatile'' memory on the device is cleared simply by removing all power from the device. This utility overwrites information that persist after removing all power, that stored in ''non-volatile'' memory. |
The utility is provided as source code, and requires UHD (headers and library) to be installed as well as the UHD source code be available on the build computer. It uses CMake to build (just like UHD does) and works with any version of UHD from 3.7.2 through 3.15. | The utility is provided as source code, and requires UHD (headers and library) to be installed as well as the UHD source code be available on the build computer. It uses CMake to build (just like UHD does) and works with any version of UHD from 3.7.2 through 3.15. | ||
| − | This utility will be provided per your specific request via an email to [support@ettus.com] . Ettus support will first require you to note receipt of our standard warnings in a first email, then once noted will provide a tarball of the utility. | + | This utility will be provided per your specific request via an email to [mailto:support@ettus.com support@ettus.com] . Ettus support will first require you to note receipt of our standard warnings in a first email, then once noted will provide a tarball of the utility. |
| − | NOTE: This utility, because it erases settings used by your USRP for runtime functionality, will render your | + | NOTE: This utility, because it erases settings used by your USRP for runtime functionality, will render your Ettus device unusable ("bricked"). It is entirely possible to make your Ettus device usable again ("unbrick" it), details of which are provided by Ettus support in emails as well as the top-level README of the utility tarball. |
==Certificates of Volatility== | ==Certificates of Volatility== | ||
| + | |||
| + | ===OctoClock=== | ||
| + | |||
| + | [https://kb.ettus.com/OctoClock_CDA-2990#Certificate_of_Volatility OctoClock] | ||
| + | |||
| + | ===USRPs=== | ||
| + | |||
| + | [https://kb.ettus.com/B200/B210/B200mini/B205mini#Certificate_of_Volatility B200 / B210] | ||
[https://kb.ettus.com/Ettus_USRP_E300_Embedded_Family_Hardware_Resources#Certificate_of_Volatility E310 / E312 / E313] | [https://kb.ettus.com/Ettus_USRP_E300_Embedded_Family_Hardware_Resources#Certificate_of_Volatility E310 / E312 / E313] | ||
| + | [https://kb.ettus.com/E320#Certificate_of_Volatility E320] | ||
| + | |||
| + | [https://kb.ettus.com/N200/N210#Certificate_of_Volatility N200 / N210] | ||
| + | |||
| + | [https://kb.ettus.com/N300/N310#Certificate_of_Volatility N300 / N310] | ||
| + | |||
| + | [https://kb.ettus.com/N320/N321#Certificate_of_Volatility N320 / N321] | ||
| + | |||
| + | [https://kb.ettus.com/X300/X310#Certificate_of_Volatility X300 / X310] | ||
| + | |||
| + | [https://kb.ettus.com/X410#Certificate_.2F_Letter_of_Volatility X410] | ||
| + | |||
| + | [https://kb.ettus.com/X440#Certificate_.2F_Letter_of_Volatility X440] | ||
| + | |||
| + | ===Daughterboards=== | ||
| + | |||
| + | [https://kb.ettus.com/BasicTX/BasicRX#Certificate_of_Volatility BasicRX / BasicTX] | ||
| + | |||
| + | [https://kb.ettus.com/CBX#Certificate_of_Volatility CBX] | ||
| + | |||
| + | [https://kb.ettus.com/LFTX/LFRX#Certificate_of_Volatility LFRX / LFTX] | ||
| + | |||
| + | [https://kb.ettus.com/SBX#Certificate_of_Volatility SBX] | ||
| + | |||
| + | [https://kb.ettus.com/TwinRX#Certificate_of_Volatility TwinRX] | ||
| + | |||
| + | [https://kb.ettus.com/UBX#Certificate_of_Volatility UBX (40 / 160 / 160-LP)] | ||
| + | |||
| + | [https://kb.ettus.com/WBX#Certificate_of_Volatility WBX] | ||
| + | |||
| + | ====End-Of-Life Daughterboards==== | ||
| + | |||
| + | [https://www.ni.com/pdf/manuals/377300a.pdf DBSRX2] | ||
| + | |||
| + | [https://www.ni.com/pdf/manuals/377300a.pdf TVRX2] | ||
[[Category:Application Notes]] | [[Category:Application Notes]] | ||
Latest revision as of 14:24, 22 September 2023
Contents
Application Note Number and Author
AN-111 by Michael Dickens
Abstract
This Application Note provides an overview of the UHD Device Eraser utility as well as links to the Certificates of Volatility for all Ettus products.
UHD Device Eraser Utility
The uhd_device_eraser utility overwrites all non-volatile memory from any Ettus device supported by it: most USRPs, OctoClock, and daughterboards.
Note that any volatile memory on the device is cleared simply by removing all power from the device. This utility overwrites information that persist after removing all power, that stored in non-volatile memory.
The utility is provided as source code, and requires UHD (headers and library) to be installed as well as the UHD source code be available on the build computer. It uses CMake to build (just like UHD does) and works with any version of UHD from 3.7.2 through 3.15.
This utility will be provided per your specific request via an email to support@ettus.com . Ettus support will first require you to note receipt of our standard warnings in a first email, then once noted will provide a tarball of the utility.
NOTE: This utility, because it erases settings used by your USRP for runtime functionality, will render your Ettus device unusable ("bricked"). It is entirely possible to make your Ettus device usable again ("unbrick" it), details of which are provided by Ettus support in emails as well as the top-level README of the utility tarball.
