Differences

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

--- firstexample:first_example_microzed_deploy [2021/12/30 09:44] – ursgraf
+++ firstexample:first_example_microzed_deploy [2021/12/30 09:44] – ursgraf
@@ Line 19: / Line 19: @@
 ==== Using the QSPI Flash ====
-  - Follow the steps given in [[firstexample:boot_loader#flashing_a_new_boot_loader|Flashing a new Boot Loader]]. However, instead of loading the configuration file <code shell>-f \\ost.ch\dfs\bsc.sys\public-programme\deep\lib\rsc\BOOTflink2.mcs</code>, you have to load your own binary image <code shell>-f MyProject\App.ExternalFlash.mcs</code>.
+  - Follow the steps given in [[firstexample:boot_loader#flashing_a_new_boot_loader|Flashing a new Boot Loader]]. However, instead of loading the configuration file <code shell>-f \\ost.ch\dfs\bsc.sys\public-programme\deep\lib\rsc\BOOTflink2.mcs</code>you have to load your own binary image <code shell>-f MyProject\App.ExternalFlash.mcs</code>.
   - 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.

deep