Differences
This shows you the differences between two versions of the page.
| add-ons:dmm-shield:webserverdemouserguide [2021/05/14 23:04] – ↷ Page moved from reference:add-ons:dmm-shield:webserverdemouserguide to add-ons:dmm-shield:webserverdemouserguide Arthur Brown | add-ons:dmm-shield:webserverdemouserguide [2022/10/04 11:38] (current) – external edit 127.0.0.1 | ||
|---|---|---|---|
| Line 3: | Line 3: | ||
| Digilent provides a Webserver demo for DMM Shield Zynq library for Digilent' | Digilent provides a Webserver demo for DMM Shield Zynq library for Digilent' | ||
| It accesses the DMM Shield hardware in order to implement some basic DMM Shield functionality. \\ | It accesses the DMM Shield hardware in order to implement some basic DMM Shield functionality. \\ | ||
| - | It uses DMM Shield library, see [[https:// | + | It uses DMM Shield library, see [[/ |
| - | The demo is based on Xilinx Webserver demo (included in [[https://www.xilinx.com/ | + | The demo is based on Xilinx Webserver demo (included in [[https://docs.xilinx.com/ |
| The demo uses a Xilinx Memory File System (xilmfs), which stores the main page, together with page additional files (java script file, used images, css style file). The functionality implemented in the main page / javascript file only uses HTML / AJAX. | The demo uses a Xilinx Memory File System (xilmfs), which stores the main page, together with page additional files (java script file, used images, css style file). The functionality implemented in the main page / javascript file only uses HTML / AJAX. | ||
| Line 66: | Line 66: | ||
| ===== Download and Launch the Arty Z7-20 DMM Shield Webserver Demo ===== | ===== Download and Launch the Arty Z7-20 DMM Shield Webserver Demo ===== | ||
| - | >1) Follow the [[:learn: | + | >1) Follow the [[learn: |
| >2) If you choose to use the project whithout building the hardware platform in Vivado (SDK Hardware Handoff metod in the above mentioned tutorial), you will notice that sdk folder lacks the hardware platform folder (design_1_wrapper_hw_platform_0).\\ In order to build this, before importing the projects in SDK (step 4), follow this procedure: In SDK, select File/ | >2) If you choose to use the project whithout building the hardware platform in Vivado (SDK Hardware Handoff metod in the above mentioned tutorial), you will notice that sdk folder lacks the hardware platform folder (design_1_wrapper_hw_platform_0).\\ In order to build this, before importing the projects in SDK (step 4), follow this procedure: In SDK, select File/ | ||
| >3) Follow the steps from [[# | >3) Follow the steps from [[# | ||
| Line 176: | Line 176: | ||
| >2) Run the mfsgen command, including all the files / folders to be included.\\ mfsgen -cvbf ../ | >2) Run the mfsgen command, including all the files / folders to be included.\\ mfsgen -cvbf ../ | ||
| - | Note that this step is also explained in the Xilinx documentation [[https://www.xilinx.com/ | + | Note that this step is also explained in the Xilinx documentation [[https://docs.xilinx.com/ |
| === Download the memory file system file in the board memory === | === Download the memory file system file in the board memory === | ||
| - | Although Xilinx proposes ([[https://www.xilinx.com/ | + | Although Xilinx proposes ([[https://docs.xilinx.com/ |
| In Vivado SDK, edit the desired debug (or running configuration) like this: | In Vivado SDK, edit the desired debug (or running configuration) like this: | ||
| * select Run / "Debug Configurations" | * select Run / "Debug Configurations" | ||

