deep

a Cross Development Platform for Java

User Tools

Site Tools

You are here: start » firstexample » first_example_microzed_deploy
firstexample:first_example_microzed_deploy

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revisionBoth sides next revision
firstexample:first_example_microzed_deploy [2021/12/28 15:42] – [Step by Step Instructions] ursgraffirstexample:first_example_microzed_deploy [2021/12/28 15:48] – ursgraf
Line 12: Line 12:
   - Running the configuration will create two flash files. Its location is given by the image file setting in the configuration. They carry the names //*.ExternalFlash.mcs// and //BOOT.bin//. Running the configuration will try to open a connection to the target if a programmer is chosen, such as //OpenOCD//. Make sure to remove the programmer, if you have no programmer present.     - Running the configuration will create two flash files. Its location is given by the image file setting in the configuration. They carry the names //*.ExternalFlash.mcs// and //BOOT.bin//. Running the configuration will try to open a connection to the target if a programmer is chosen, such as //OpenOCD//. Make sure to remove the programmer, if you have no programmer present.  
   - Now, you have to choose between using a SD card or the QSPI flash.   - Now, you have to choose between using a SD card or the QSPI flash.
 + 
 ==== Using the SD Card ==== ==== Using the SD Card ====
 +  - Copy the above generated file //BOOT.bin// onto a SD card. The card must be formatted with FAT32. 
 +  - Set the jumpers on your MicroZed board as follows \\ {{ qspiboot.png?200 |}}. \\ This will boot the device from the QSPI flash. 
 +  - Cycle the power. The settings of the jumpers will be read only at power-on! Hence, make sure to cycle the supply power after changing the jumper settings. A soft reset (through the JTAG or by pressing the reset button on the board will reset the board but will not sample the boot mode pins connected to the jumpers.
  
 ==== Using the QSPI Flash ==== ==== Using the QSPI Flash ====
- 
   - Switch the driver for your JTAG-HS3 adapter to //FTDI CDM//, see [[https://wiki.bu.ost.ch/infoportal/embedded_systems/jtaghs3/start]]. IMPORTANT: You must close OpenOCD before switching the driver, else the //WinUSB// cannot be unloaded.   - Switch the driver for your JTAG-HS3 adapter to //FTDI CDM//, see [[https://wiki.bu.ost.ch/infoportal/embedded_systems/jtaghs3/start]]. IMPORTANT: You must close OpenOCD before switching the driver, else the //WinUSB// cannot be unloaded.
-  - The program to download can be found in the binaries of //Vivado// or the //Xilinx SDK//. You have to either install //Vivado// or //Xilinx SDK// which doesn't require a license. As //Vivado// uses lots of disk space we strongly recommend to install //Xilinx SDK//. For the installation see [[https://wiki.bu.ost.ch/infoportal/embedded_systems/zynq7000/xsdk|Installing Xilinx SDK]]. After installation, open a command shell and run the command (Change the command so that the right configuration file is loaded, see [[https://wiki.bu.ost.ch/infoportal/embedded_systems/zynq7000/microzed]]). The corresponding files can be found in your target runtime library in the directory ///rsc//. Please make sure that the paths in the following command does not include spaces! <code shell>cmd /C C:\Xilinx\SDK\2019.1\bin\program_flash -f MyProject\App.ExternalFlash.mcs -offset 0 -flash_type qspi-x4-single -fsbl M:\EUser\JCC\org.deepjava.trglib\rsc\FSBL.elf -cable type xilinx_tcf url TCP:127.0.0.1:3121 </code> Make sure that the programming was successful with the program printing <code>Flash Operation Successful</code>+  - The program to download can be found in the binaries of //Vivado// or the //Xilinx SDK//. You have to either install //Vivado// or //Xilinx SDK// which doesn't require a license. As //Vivado// uses lots of disk space we strongly recommend to install //Xilinx SDK//. For the installation see [[https://wiki.bu.ost.ch/infoportal/embedded_systems/zynq7000/xsdk|Installing Xilinx SDK]]. After installation, open a command shell and run the command (Change the command so that the right configuration file is loaded, see [[https://wiki.bu.ost.ch/infoportal/embedded_systems/zynq7000/microzed]]). The corresponding files can be found in your target runtime library in the directory ///rsc//. Please make sure that the paths in the following command does not include spaces! <code shell>cmd /C C:\Xilinx\SDK\2019.1\bin\program_flash -f MyProject\App.ExternalFlash.mcs -offset 0 -flash_type qspi-x4-single -fsbl \\ost.ch\dfs\bsc.sys\public-programme\deep\lib\rsc\FSBL.elf -cable type xilinx_tcf url TCP:127.0.0.1:3121 </code> Make sure that the programming was successful with the program printing <code>Flash Operation Successful</code>
   - Switch the driver for the JTAG-HS3 back to //WinUSB//, see [[https://wiki.bu.ost.ch/infoportal/embedded_systems/jtaghs3/start]].   - Switch the driver for the JTAG-HS3 back to //WinUSB//, see [[https://wiki.bu.ost.ch/infoportal/embedded_systems/jtaghs3/start]].
   - Set the jumpers on your MicroZed board as follows \\ {{ qspiboot.png?200 |}}. \\ This will boot the device from the QSPI flash.    - Set the jumpers on your MicroZed board as follows \\ {{ qspiboot.png?200 |}}. \\ This will boot the device from the QSPI flash. 
firstexample/first_example_microzed_deploy.txt · Last modified: 2022/11/17 15:03 by ursgraf

Page Tools

Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
CC Attribution-Share Alike 4.0 International Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki