b) SD Card image using ADRV9001 Disk Imaging Utility (SDK 13 or higher)

From SDK23.1, the recommended method to create a new SD card is described here . __________________________________________________________ This guide will instruct you on how to create a new SD card for version 0.13.0 and higher. There is a separate guide here on how to create an SD card for version 0.12.0 and lower. The minimum requirements for your SD card are 8 GB storage or higher and class 4 or higher. If you encounter any difficulty, please take note of the troubleshooting section . Step 1: Setup a) There is two pieces of software needed for this guide. Please download and install both : a. ADRV9001 Disk Imaging Utility b. dotNet Disk Imager b) Connect the SD card directly to your PC c) Open ADRV9001 Disk Image Utility only Step 2: Download Image File a) In ADRV9001 Disk Image Utility click the “Format SD Card” button. Note: Do not select “Legacy” option (This is for SDK 12 or lower. Refer to this document for more information) b) Utility will begin downloading a zip file to C:\Users\USERNAME\AppData\Local\Temp, Utility will display 'Downloading'. The download may take several minutes. c) Once Download is complete, Utility will open the dotNet DiskImager, user will need to enter their password to authorize the application Step 3: Format SD Card a) In the dotNet Disk Imager, ensure that the correct image file is selected i.e. C:\Users\USERNAME\AppData\Local\Temp\IMAGE_NAME.zip b) Ensure that Device selected is the SD card. c) Click “Write to Device”. You should see a progress bar. This may take several minutes. d) When write has completed successfully, close dotNet DiskImager and return to ADRV9001 Disk Imaging Utility Step 4: Download Files to SD Card a) Under “Step 2”, set “Select Drive” to your SD card and “Set Platform” to the relevant option (ZCU102 is not supported for SDK 13. Support will be added in later revisions.) b) Click “Download Files”. c) Once Finished, a “Finished” label will be shown d) Close the ADRV9001 Disk Image Utility e) Safely unmount the SD card, remove from your PC and insert into your FPGA. Troubleshooting This section is intended to help resolve any issues encountered while following the steps in the guide. Can’t locate image file in the dotNet disk imager in step 2 Navigate to C:\Users\USERNAME\AppData\Local\Temp and search for the .zip image file. If you cannot find this file, close dotNet disk imager and ADRV9001 Disk Image Utility and repeat step 1. Can’t write to SD card If at any stage you are having trouble writing to your SD card, please ensure that the switch on the SD card is set to unlocked. If it is set to lock, you will not be able to write to the SD card. “Network connection has files open or requests pending” in step 2 If the error message “This network connection has files open or requests pending” appears when trying to write to SD card, try closing any file explorer tabs you have open. If this is not sufficient, try closing other programs that may be interacting with the SD card. Can’t get “lock on volume” in dotNet disk imager in step 2 If the error message “error occurred when trying to get lock on volume” appears, try these steps: a. Right click on the SD card in file explorer and select “Format” b. Set “Volume label” to “BOOT” and click “Start” If the issue persists, try to: a. repeat these steps but deselect the “quick format” option b. reboot your PC c. check the “Can’t write to SD card” troubleshooting section Completed all steps successfully but can’t connect through TES. Check the TES GUI Connection Issues Debug Page The files written to your SD card may be encrypted. Contact your IT administrator about this.

a) Writing SD Card Image Manually (SDK23.1 and Higher)

This guide will instruct you on how to manually image an SD card for use on the evaluation platform for ADRV9001. If you encounter any difficulty, please take note of the troubleshooting section at the end of this document . Step 1: Downloads Firstly, you will need to download two things: 1) SD card image zip file for your target platform: Wideband RF Transceiver Evaluation Software | Analog Devices 2) dotNet Disk Imager (Or your preferred SD card imaging software) Step 2: Imaging a) Unzip the zip file downloaded in step 1. There should be a single .img file inside. a) Connect the SD card directly to your PC b) Open the dotNet disk imager, select the unzipped .img file and the device to write to. Write to the device. If the SD card has been used previously, you might need to 'wipe device' first. d) Safely unmount the SD card and insert into FPGA. Troubleshooting This section is intended to help resolve any issues encountered while following the steps in the guide. Files potentially corrupted If you believe that your file may have been corrupted somewhere in the process, try to check the SHA1 checksum of the file. If the checksum matches the table below, there is a high degree of confidence that the files are not corrupted. File SHA1 Checksum navassa_zc706.img 1cd777e2a0d83bc1e7a9a2004afab3cb8a9904d6 navassa_zc706.zip fc2635e9f0e1f8ad7a353b124c9aeedbff610a73 navassa_zcu102.img d68bcc127e3161ef9666e5e906388500fccdddad navassa_zcu102.zip d80cefd1c10992974514dd197db64a748dab7cf5 To get the SHA1 checksum of the file, open dotNet disk imager and select the file you want to check. Select 'SHA1' in the checksum section and press 'calculate'. Can’t write to SD card If at any stage you are having trouble writing to your SD card, please ensure that the switch on the SD card is set to unlocked. If it is set to lock, you will not be able to write to the SD card. “Network connection has files open or requests pending” in step 2 If the error message “This network connection has files open or requests pending” appears when trying to write to SD card, try closing any file explorer tabs you have open. If this is not sufficient, try closing other programs that may be interacting with the SD card. Can’t get “lock on volume” If the error message “error occurred when trying to get lock on volume” appears, try these steps: a. Right click on the SD card in file explorer and select “Format” b. Set “Volume label” to “BOOT” and click “Start” If the issue persists, try to: a. repeat these steps but deselect the “quick format” option b. reboot your PC c. check the “Can’t write to SD card” troubleshooting section Completed all steps successfully but can’t connect through TES. Check the TES GUI Connection Issues Debug Page The files written to your SD card may be encrypted. Contact your IT administrator about this.

c) SD Card image using ADRV9001 Disk Imaging Utility (Legacy - SDK 12 or lower)

This guide will instruct you on how to create a new SD card for version 0.12.0 and lower. There is a separate guide here on how to create an SD card for version 0.13.0 and higher. ZCU102 is not supported for SDK 12 and below. The minimum requirements for your SD card are 16 GB storage or higher and class 4 or higher. If you encounter any difficulty, please take note of the troubleshooting section . Step 1: Setup a) There is two pieces of software needed for this guide. Please download and install both: a. ADRV9001 Disk Imaging Utility b. dotNet Disk Imager b) Connect the SD card directly to your PC c) Open ADRV9001 Disk Image Utility only Step 2: Download Image File a) In ADRV9001 Disk Image Utility click the “legacy” button and then the “Format SD Card” button. Note: (Refer to this document to create a SD card for SDK version 13 or higher) b) Utility will begin downloading a zip file to C:\Users\USERNAME\AppData\Local\Temp, Utility will display 'Downloading'. The download may take several minutes. c) Once Download is complete, Utility will open the dotNet DiskImager, user will need to enter their password to authorize the application Step 3: Format SD Card a) In the dotNet Disk Imager, ensure that the correct image file is selected i.e. C:\Users\USERNAME\AppData\Local\Temp\IMAGE_NAME.zip b) Ensure that Device selected is the SD card. c) Click “Write to Device”. You should see a progress bar. This may take several minutes. d) When write has completed successfully, close dotNet DiskImager and the ADRV9001 Disk Image Utility e) Safely unmount the SD card, remove from your PC and insert into your FPGA. Troubleshooting This section is intended to help resolve any issues encountered while following the steps in the guide. Can’t locate image file in the dotNet disk imager in step 2 Navigate to C:\Users\USERNAME\AppData\Local\Temp and search for the .zip image file. If you cannot find this file, close dotNet disk imager and ADRV9001 Disk Image Utility and repeat step 1. Can’t write to SD card If at any stage you are having trouble writing to your SD card, please ensure that the switch on the SD card is set to unlocked. If it is set to lock, you will not be able to write to the SD card. “Network connection has files open or requests pending” in step 2 If the error message “This network connection has files open or requests pending” appears when trying to write to SD card, try closing any file explorer tabs you have open. If this is not sufficient, try closing other programs that may be interacting with the SD card. Can’t get “lock on volume” in dotNet disk imager in step 2 If the error message “error occurred when trying to get lock on volume” appears, try these steps: a. Right click on the SD card in file explorer and select “Format” b. Set “Volume label” to “BOOT” and click “Start” If the issue persists, try to: a. repeat these steps but deselect the “quick format” option b. reboot your PC c. check the “Can’t write to SD card” troubleshooting section Completed all steps successfully but can’t connect through TES. The files written to your SD card may be encrypted. Contact your IT administrator about this.

SD Card Image: FAQ

In this tab we will show a step-by-step guide to image or re-image SD the FPGA SD card for releases up to version 12 and for version 13 and beyond.

These guides can be used to create a new SD card or fix a corrupted SD card.

As a guide for knowing whether you are using Pre-Release Silicon (B0) vs. Released Silicon (C0), here's a list of the Evaluation Board and SD card labels for each revision*: