setenv custom_autoboot \"echo Scalp board autoboot from QSPI && run boot_from_qspi\";
fi
run custom_autoboot" > uenv.scr.txt
```
```
$ ../../../tools/u-boot-tools/mkimage -T script -C none -n 'Scalp U-Boot Script File' -A arm -d uenv.scr.txt uenv.scr
```
...
...
@@ -732,6 +771,12 @@ Then checkout the **SCALP-USER-v0.5.1** tag.
$ git checkout SCALP-USER-v0.5.1
```
**For the design with the NoC Scalp :**
```
$ git checkout SCALP-ROUTER-v0.1
```
**If you have not gone through the scalp\_safe\_petalinux firmware creation section, please go to section [Copy Scalp board files](#copy-scalp-board-files).**
#### Build the user bitstream file.
...
...
@@ -751,6 +796,10 @@ and File -> Export -> Export Hardware -> include bitstream
In my case **\<SCALP_USER_FIRMWARE\>** corresponds to "scalp\_user\_firmware".
**For the design with the NoC Scalp :**
**\<SCALP_USER_FIRMWARE\>** corresponds to "scalp\_router\_firmware".
**If you have not gone through the scalp\_safe\_petalinux firmware creation process, please follow the instructions below to clone the scalp\_petalinux GIT repository.**
**Use version 0.5.1 for the GIT scalp_petalinux repository and version 0.5.1 for the GIT scalp_firmware repository. Be careful, sometimes the versions are identical, but depending on the evolution of the FPGA firmware and the PetaLinux firmware, the versions may be different.**
**For the design with the NoC Scalp :**
```
$ git checkout SCALP-ROUTER-v0.1
```
### Create a new Scalp User Petalinux project from a BSP
**If you want to name your "scalp_user_firmware" project, please delete the one already present. This folder has been left deliberately.**
...
...
@@ -781,6 +836,10 @@ $ cd <PROJECT NAME>
In my case **\<path-to-bsp\>** corresponds to /home/jo/Documents/Projets/Hepia/scalp_project/scalp_petalinux/bsp/SCALP-USER-FIRMWARE-BSP-V0.5.1.bsp
**For the design with the NoC Scalp :**
**\<path-to-bsp\>** corresponds to /home/jo/Documents/Projets/Hepia/scalp_project/scalp_petalinux/bsp/SCALP-ROUTER-FIRMWARE-BSP-V0.1.bsp
### Importing hardware configuration
**The hardware description of the project must have been exported from Vivado beforehand.**
In my case **\<PATH_TO_SCALP_FIRMWARE_PROJECT\>** corresponds to /home/jo/Documents/Projets/Hepia/scalp_project/scalp_firmware/ and **\<SCALP_USER_FIRMWARE\>** corresponds to **scalp_user_firmware**.
**For the design with the NoC Scalp :**
**\<PATH_TO_SCALP_FIRMWARE_PROJECT\>** corresponds to /home/jo/Documents/Projets/Hepia/scalp_project/scalp_firmware/ and **\<SCALP_USER_FIRMWARE\>** corresponds to **scalp_router_firmware**.
**In the case of user firmware, it is not necessary to configure U-Boot. It is not used.**
The name of the bitstream file before the .bit.bin extension must be the same as the firmware name defined in the export environment variable SCALP\_USER\_FIRMWARE="\<SCALP\_USER\_FIRMWARE>" described in the section [Importing hardware configuration](#importing-hardware-configuration).
In my case, the environment variable **BITSTREAM\_FILE\_NAME** corresponds to **scalp\_user\_firmware.bit.bin**.
Otherwise, the bitstream configuration file will not be automatically taken into account.
**For the design with the NoC Scalp :**
The environment variable **BITSTREAM\_FILE\_NAME** corresponds to **scalp\_router\_firmware.bit.bin**.
### Build the PetaLinux project
```
...
...
@@ -863,6 +937,14 @@ $ lsblk <----- Without the SD card inserted.
$ sudo dd if=./images/linux/virtualfs-ext4.img of=/dev/\<MMC_DEV_NODE\> status=progress <----- Beware of danger, be sure.
```
or
```
$ cp ../tools/virtfs.sh images/linux/ && cd images/linux/ && chmod +x virtfs.sh && sudo ./virtfs.sh && cd ../.. && lsblk