It is possible to customize existing meta layers by creating an own meta layer with bitbake append files. In this description the meta layer meta-altera for Intel FPGA devices is used as reference.
For more informations about the OS used and the sources and versions of yocto project or meta-altera layer, see Yocto KICKstart#Used source files.
Initialize the environment
Scroll Ignore |
---|
scroll-pdf | true |
---|
scroll-office | true |
---|
scroll-chm | true |
---|
scroll-docbook | true |
---|
scroll-eclipsehelp | true |
---|
scroll-epub | true |
---|
scroll-html | true |
---|
|
|
Before starting to create a custom meta layer, navigate to the yocto poky directory and initialize the environment with the following commands:
Code Block |
---|
language | bash |
---|
theme | Midnight |
---|
linenumbers | true |
---|
|
cd path/to/yocto/poky
source oe-init-build-env
|
Download required sources
Scroll Ignore |
---|
scroll-pdf | true |
---|
scroll-office | true |
---|
scroll-chm | true |
---|
scroll-docbook | true |
---|
scroll-eclipsehelp | true |
---|
scroll-epub | true |
---|
scroll-html | true |
---|
|
|
Since the created meta-custom layer should depend on meta-altera, these sources files must be downloaded and added to the yocto project.
Navigate to yocto poky directory and download meta-altera layer:
Code Block |
---|
language | bash |
---|
theme | Midnight |
---|
linenumbers | true |
---|
|
cd path/to/yocto/poky
git clone -b dunfell https://github.com/kraj/meta-altera.git |
Add meta-altera to yocto project with:
Code Block |
---|
language | bash |
---|
theme | Midnight |
---|
linenumbers | true |
---|
|
cd path/to/yocto/poky/build
bitbake-layers add-layer ./meta-altera |
Create
custom meta BSP layer
Scroll Ignore |
---|
scroll-pdf | true |
---|
scroll-office | true |
---|
scroll-chm | true |
---|
scroll-docbook | true |
---|
scroll-eclipsehelp | true |
---|
scroll-epub | true |
---|
scroll-html | true |
---|
|
|
In this example, the created layer is named meta-custom. If you want to use a different name, just replace "custom".
Create own layer "meta-custom" with:
Code Block |
---|
language | bash |
---|
theme | Midnight |
---|
linenumbers | true |
---|
|
bitbake-layers create-layer path/to/yocto/poky/meta-custom |
The created layer contains a sample recipes folder, that can be removed:
Code Block |
---|
language | bash |
---|
theme | Midnight |
---|
linenumbers | true |
---|
|
rm -rf path/to/yocto/poky/meta-custom/recipes-example |
Make meta-custom dependent on meta-altera:
Code Block |
---|
language | bash |
---|
theme | Midnight |
---|
linenumbers | true |
---|
|
sed -i '/LAYERDEPENDS_meta-custom/s/core/meta-altera/g' path/to/yocto/poky/meta-custom/conf/layer.conf |
Add the meta-custom layer to the yocto project with:
Code Block |
---|
language | bash |
---|
theme | Midnight |
---|
linenumbers | true |
---|
|
bitbake-layers add-layer path/to/yocto/poky/meta-custom |
Add required parameters to local.conf
Scroll Ignore |
---|
scroll-pdf | true |
---|
scroll-office | true |
---|
scroll-chm | true |
---|
scroll-docbook | true |
---|
scroll-eclipsehelp | true |
---|
scroll-epub | true |
---|
scroll-html | true |
---|
|
First the variable "MACHINE" must be redefined in the local.conf file. Several machines are defined In the machine configuration file, you can store general settings for the custom BSP layer, such as the version of u-boot or the linux kernel. Here, we will use the cyclone5 machine configuration file from the meta-altera layer as a template. For other machine configurations in the meta-altera layer
(, see meta-altera/conf/machine.
Download the cyclone5 machine configuration file to the meta-custom layer and rename it
for more information). In this example, the machine 'cyclone5' is used.
Remove the default value and add 'cyclone5':
Code Block |
---|
language | bash |
---|
theme | Midnight |
---|
linenumbers | true |
---|
|
sedi '/^MACHINE/s/MACHINE/#MACHINE/g'buildlocal.conf
echo -e '\nMACHINE = "cyclone5"' >> machine
cd path/to/yocto/poky/ |
build/conf/localmeta-custom/conf/machine
wget https://github.com/kraj/meta-altera/raw/dunfell/conf/machine/cyclone5.conf
mv cyclone5.conf custom.conf |
For the linux kernel in the meta-altera layer it's required to define a the preferred provider and version in local.conf (see meta-altera/recipes-kernel/linux for other linux kernel versions)
- Make the following changes to the content of custom.conf:
Change the name in line 2 from 'cyclone5' to 'custom' and customize the variables UBOOT_EXTLINUX_DEFAULT_LABEL and UBOOT_EXTLINUX_MENU_DESCRIPTION_default:
Code Block |
---|
language | bash |
---|
theme | Midnight |
---|
linenumbers | true |
---|
|
echo
e
\nPREFERRED_PROVIDER_virtual/kernel = "linux-altera-lts"' >> /^#@NAME:/s/.*/#@NAME: custom/g' path/to/yocto/poky/ |
buildmeta-custom/conf/machine/ |
local
echo
e
PREFERRED_VERSION_linux-altera-lts = "5.4%"' >>/^UBOOT_EXTLINUX_DEFAULT_LABEL/s/".*"/"Cyclone5 custom SDMMC"/g' path/to/yocto/poky/ |
build
local
Set the preferred u-boot version for meta-altera in local.conf (see meta-altera/recipes-bsp/u-boot for other u-boot versions):
Code Block |
---|
language | bash |
---|
theme | Midnight |
---|
linenumbers | true |
---|
|
echo -e '\nPREFERRED_VERSION_u-boot-socfpga = "v2021.04%"' >>sed -i '/^UBOOT_EXTLINUX_MENU_DESCRIPTION_default/s/".*"/"Cyclone5 custom SDMMC"/g' path/to/yocto/poky/meta-custom/conf/machine/custom.conf |
The KMACHINE variable defines the MACHINE name, which is referenced in the build/conf/local.conf
Scroll Ignore |
---|
scroll-pdf | true |
---|
scroll-office | true |
---|
scroll-chm | true |
---|
scroll-docbook | true |
---|
scroll-eclipsehelp | true |
---|
scroll-epub | true |
---|
scroll-html | true |
---|
|
file. Redefine KMACHINE with your own MACHINE name:
The following command creates the workspace directory and adds it to bblayers.conf:
code |
---|
language | bash |
---|
theme | Midnight |
---|
linenumbers | true |
---|
|
devtool
create-workspace-i '/^KMACHINE/s/".*"/"custom"/g' path/to/yocto/poky/meta-custom/conf/machine/custom.conf |
For the linux kernel in the meta-altera layer it's required to define a the preferred provider and version in custom.conf (see Yocto KICKstart#Used source files for more information about the version used). Add the provider and version for linux kernel:
Code Block |
---|
language | bash |
---|
theme | Midnight |
---|
linenumbers | true |
---|
|
echo -e '\nPREFERRED_PROVIDER_virtual/kernel = "linux-altera-lts"' >> path/to/yocto/poky/meta-custom/conf/machine/custom.conf
echo -e 'PREFERRED_VERSION_linux-altera-lts = "5.4%"' >> path/to/yocto/poky/meta-custom/conf/machine/custom.conf |
Set the preferred u-boot version for meta-altera in custom.conf (see Yocto KICKstart#Used source files for more information about the version used)
Scroll Ignore |
---|
scroll-pdf | true |
---|
scroll-office | true |
---|
scroll-chm | true |
---|
scroll-docbook | true |
---|
scroll-eclipsehelp | true |
---|
scroll-epub | true |
---|
scroll-html | true |
---|
|
To prepare the u-boot sources for modify the default configuration and create patches, do the following steps:
- It is not possible to call menuconfig if UBOOT_CONFIG is defined. But UBOOT_CONFIG is needed to assign a defconfig file to UBOOT_MACHINE. UBOOT_MACHINE must therefore be defined manually. The variable UBOOT_CONFIG is predefined in the machine configuration file for cyclone5 with the value 'cyclone5-socdk' (see meta-altera/conf/machine/cyclone5.conf). The associated defconfig file is therefore socfpga_cylcone5_defconfig (see meta-altera/recipes-bsp/u-boot/u-boot-socfpga-common.inc). Accordingly these variables must be defined in local.conf
:
Code Block |
---|
language | bash |
---|
theme | Midnight |
---|
linenumbers | true |
---|
|
echo -e '\ |
nUBOOT_MACHINEnPREFERRED_VERSION_u-boot-socfpga = " |
socfpga_cyclone5_defconfigv2021.04%"' >> path/to/yocto/poky/ |
buildmeta-custom/conf/machine/ |
local.conf
echo -e 'UBOOT_CONFIG = ""' >>
Other variables in the custom.conf file are changed or added at other points in this guide.
Add required parameters to local.conf
Before you start configuring the meta-custom layer, the MACHINE variable in the path/to/yocto/poky/build/conf/local.conf
Run following command to prepare the workspace and fetch and unpack the sourcesfile must be set to the correct machine. The correct machine name is defined in the meta-custom/conf/machine/custom.conf file with the variable KMACHINE.
Remove the default value of the MACHINE variable in local.conf and add the new MACHINE 'custom':
Code Block |
---|
language | bash |
---|
theme | Midnight |
---|
linenumbers | true |
---|
|
devtoolmodify u-boot-socfpga -OTo make changes to u-boot configuration, follow these steps:
Launch menuconfig with following command and make your changes-i '/^MACHINE/s/MACHINE/#MACHINE/g' path/to/yocto/poky/build/conf/local.conf
echo -e '\nMACHINE = "custom"' >> path/to/yocto/poky/build/conf/local.conf |
Create workspace
The following command creates the workspace directory and adds it to bblayers.conf:
Code Block |
---|
language | bash |
---|
theme | Midnight |
---|
linenumbers | true |
---|
|
devtool |
menuconfig
-socfpgaExit and save your configuration. devtool-fragment.cfg will be created automatically.Prepare u-boot configuration in workspace
To prepare the u-boot sources for modify the default configuration and create patches, do the following steps:
To set the correct default defconfig file for the u-boot, it is required to set the UBOOT_MACHINE variable in the meta-custom/conf/machine/custom.conf file. The defconfig file 'socfpga_cylcone5_defconfig' will be used as default u-boot configuration (see meta-altera/recipes-bsp/u-boot/u-boot-socfpga-common.inc for other Intel fpga defconfig files). If UBOOT_MACHINE has been defined, UBOOT_CONFIG is no longer needded.
Remove the variable UBOOT_CONFIG and add UBOOT_MACHINE to meta-custom/conf/machine/custom.conf
Do following steps to create patches for u-boot source files:
Navigate to u-boot-socfpga in the workspace and add, modify or remove files:
Code Block |
---|
language | bash |
---|
theme | Midnight |
---|
linenumbers | true |
---|
|
cd path/to/yocto/poky/build/workspace/sources/u-boot-socfpga |
Run a build to test your changes:
Code Block |
---|
language | bash |
---|
theme | Midnight |
---|
linenumbers | true |
---|
|
devtoolsed build u-boot-socfpga-i '/^UBOOT_CONFIG/d' path/to/yocto/poky/meta-custom/conf/machine/custom.conf
echo -e '\nUBOOT_MACHINE = "socfpga_cyclone5_defconfig"' >> path/to/yocto/poky/meta-custom/conf/machine/custom.conf
|
Run following command to prepare the workspace and fetch and unpack the sources
Add the changes made with:
Code Block |
---|
language | bash |
---|
theme | Midnight |
---|
linenumbers | true |
---|
|
git add . |
Commit your changes and add a short message. The message is used to name the patch file:
Code Block |
---|
language | bash |
---|
theme | Midnight |
---|
linenumbers | true |
---|
|
gitdevtool commitmodify u-boot-m "<message>"socfpga -O |
To make changes to u-boot configuration, follow these steps:
Launch menuconfig with following command and make your changesIf you want to generate more patches, repeat steps 1 - 4, otherwise navigate back to the poky directory:
Code Block |
---|
language | bash |
---|
theme | Midnight |
---|
linenumbers | true |
---|
|
cd path/to/yocto/poky |
Create and update devtool menuconfig u-boot |
recipe bbappendAdd the
- Exit and save your configuration. devtool-fragment.cfg
and the patches to the meta-custom layer with- will be created automatically.
Create patches for u-boot source files
Do following steps to create patches for u-boot source files:
Navigate to u-boot-socfpga in the workspace and add, modify or remove files:
Code Block |
---|
language | bash |
---|
theme | Midnight |
---|
linenumbers | true |
---|
|
devtool update-recipe u-boot-socfpga -a path/to/yocto/poky/meta-custom -O |
Remove the UBOOT_CONFIG and UBOOT_MACHINE variables from local.conf if you use the default defconfig file for the MACHINE 'cyclone5'cd path/to/yocto/poky/build/workspace/sources/u-boot-socfpga |
Run a build to test your changes:
Code Block |
---|
language | bash |
---|
theme | Midnight |
---|
linenumbers | true |
---|
|
sed
-i '/UBOOT_MACHINE = "socfpga_cyclone5_defconfig"/d' path/to/yocto/poky/build/conf/local.conf
sed -i '/UBOOT_CONFIG = ""/d' path/to/yocto/poky/build/conf/local.conf
Add the changes made with:
Code Block |
---|
language | bash |
---|
theme | Midnight |
---|
linenumbers | true |
---|
|
git add . |
Commit your changes and add a short message. The message is used to name the patch file:
Code Block |
---|
language | bash |
---|
theme | Midnight |
---|
linenumbers | true |
---|
|
git commit -m "<message>" |
If you get the following error message: "*** Please tell me who you are. Run ...", run this commands to define a name and email:
Code Block |
---|
language | bash |
---|
theme | Midnight |
---|
linenumbers | true |
---|
|
git config --local user.email "oe.patch@oe"
git config --local user.name "OpenEmbedded" |
If you want to generate more patches, repeat steps 1 - 4, otherwise navigate back to the poky directory:
Code Block |
---|
language | bash |
---|
theme | Midnight |
---|
linenumbers | true |
---|
|
cd path/to/yocto/poky |
Create and update u-boot recipe bbappend
Add the devtool-fragment.cfg and the patches to the meta-custom layer with
Scroll Ignore |
---|
scroll-pdf | true |
---|
scroll-office | true |
---|
scroll-chm | true |
---|
scroll-docbook | true |
---|
scroll-eclipsehelp | true |
---|
scroll-epub | true |
---|
scroll-html | true |
---|
|
To prepare the linux kernel sources for modify the default configuration and create patches, do the following steps:
Run following command to prepare the workspace and fetch and unpack the sources:
Code Block |
---|
language | bash |
---|
theme | Midnight |
---|
linenumbers | true |
---|
|
devtool |
modifylinuxaltera-ltsboot-socfpga -a path/to/yocto/poky/meta-custom -O |
with menuconfigTo make changes to linux kernel configuration, follow these steps:
Launch menuconfig with following command and make your changes:
Code Block |
---|
language | bash |
---|
theme | Midnight |
---|
linenumbers | true |
---|
|
devtool menuconfig linux-altera-lts |
Exit and save your configuration. devtool-fragment.cfg will be created automatically. Scroll Ignore |
---|
scroll-pdf | true |
---|
scroll-office | true |
---|
scroll-chm | true |
---|
scroll-docbook | true |
---|
scroll-eclipsehelp | true |
---|
scroll-epub | true |
---|
scroll-html | true |
---|
|
|
Prepare linux kernel configuration in workspace
To prepare the linux kernel sources for modify the default configuration and create patches, do the following steps:
Run following command to prepare the workspace and fetch and unpack the sources
Do following steps to create patches for u-boot source files:
Navigate to linux-altera-lts in the workspace and add, modify or remove files:
Code Block |
---|
language | bash |
---|
theme | Midnight |
---|
linenumbers | true |
---|
|
cd path/to/yocto/poky/build/workspace/sources/devtool modify linux-altera-lts -O |
To make changes to linux kernel configuration, follow these steps:
Launch menuconfig with following command and make your changes:
Run a build to test your changes:
Code Block |
---|
language | bash |
---|
theme | Midnight |
---|
linenumbers | true |
---|
|
devtool buildmenuconfig linux-altera-lts |
Add the changes made with:
- Exit and save your configuration. devtool-fragment.cfg will be created automatically.
Create patches for linux kernel source files
Do following steps to create patches for u-boot source files:
Navigate to linux-altera-lts in the workspace and add, modify or remove files:
Code Block |
---|
|
Code Block |
---|
language | bash |
---|
theme | Midnight |
---|
linenumbers | true |
---|
|
git add . |
cd path/to/yocto/poky/build/workspace/sources/linux-altera-lts |
Run a build to test your changesCommit your changes and add a short message. The message is used to name the patch file:
Code Block |
---|
language | bash |
---|
theme | Midnight |
---|
linenumbers | true |
---|
|
gitdevtool commitbuild -m "<message>"linux-altera-lts |
Add the changes made withIf you want to generate more patches, repeat step 1 - 4, otherwise navigate back to the poky directory:
Code Block |
---|
language | bash |
---|
theme | Midnight |
---|
linenumbers | true |
---|
|
cd path/to/yocto/poky |
Add the devtool-fragment.cfg and the patches to the meta-custom layer with
Commit your changes and add a short message. The message is used to name the patch file:
Code Block |
---|
language | bash |
---|
theme | Midnight |
---|
linenumbers | true |
---|
|
devtool
update-recipe
linux
altera-lts -a path/to/yocto/poky/meta-custom -O
If you want to generate more patches, repeat step 1 - 4, otherwise navigate back to the poky directory:
Scroll Ignore |
---|
scroll-pdf | true |
---|
scroll-office | true |
---|
scroll-chm | true |
---|
scroll-docbook | true |
---|
scroll-eclipsehelp | true |
---|
scroll-epub | true |
---|
scroll-html | true |
---|
|
Remove the workspace from bblayers.conf and delete the workspace folder:
code |
---|
language | bash |
---|
theme | Midnight |
---|
linenumbers | true |
---|
|
cd path/to/yocto/poky |
Create and update linux kernel recipe bbappend
Add the devtool-fragment.cfg and the patches to the meta-custom layer with:
Code Block |
---|
language | bash |
---|
theme | Midnight |
---|
linenumbers | true |
---|
|
devtool update-recipe linux-altera-lts -a/build
bitbake-layers remove-layer workspace
rm -rf path/to/yocto/poky/build/workspace |
Remove workspace
scrollscroll-ignore |
---|
scroll-pdf | true |
---|
scroll-office | true |
---|
scroll-chm | true |
---|
scroll-docbook | true |
---|
scroll-eclipsehelp | true |
---|
scroll-epub | true |
---|
scroll-html | true |
---|
|
If you create a u-boot file for an Intel Cyclone V / Arria V with quartus version 20.1 you have to convert the handoff data into source code.
compile your quartus projectrun the embedded command shell (Intel SoC EDS):
Code Block |
---|
language | bash |
---|
theme | Midnight |
---|
linenumbers | true |
---|
|
~/intelFPGA_lite/20.1/embedded/embedded_command_shell.sh |
navigate to your quartus project directory and convert the handoff data into source code:
Code Block |
---|
Remove the workspace from bblayers.conf and delete the workspace folder:
language | bash |
---|
theme | Midnight |
---|
linenumbers | true |
---|
|
cd path/to/ |
quartus/project
mkdir -p bspcreate-settings-type spl-bsp-dir build \
--preloader-settings-dir hps_isw_handoff/soc_system_hps_0/ \
--settings build/settings.bsprf path/to/yocto/poky/build/workspace |
Scroll Ignore |
---|
scroll-pdf | true |
---|
scroll-office | true |
---|
scroll-chm | true |
---|
scroll-docbook | true |
---|
scroll-eclipsehelp | true |
---|
scroll-epub | true |
---|
scroll-html | true |
---|
|
|
Add handoff files to u-boot
If you create a u-boot file for an Intel Cyclone V / Arria V with quartus version 20.1 you have to convert the handoff data into source code.
- compile your quartus project
run the embedded command shell (Intel SoC EDS)
Next you have to run the qts_filter to take the sources from the handoff folder, format them and copy them to u-boot source code.
Fetch qts_filter.sh from github:
Code Block |
---|
language | bash |
---|
theme | Midnight |
---|
linenumbers | true |
---|
|
wget https://github.com/altera-opensource/u-boot-socfpga/blob/socfpga_v2021.04/arch/arm/mach-socfpga/qts-filter.sh |
Run qts_filter for cyclone5 to format and copy the handoff files to custom meta layer:
Code Block |
---|
language | bash |
---|
theme | Midnight |
---|
linenumbers | true |
---|
|
mkdir -p path/to/yocto/poky/meta-custom/recipes-bsp/u-boot/u-boot-socfpga/qts
./qts_filter.sh cyclone5 \
path/to/quartus/project \
path/to/quartus/project/build \
path/to/yocto/poky/meta-custom/recipes-bsp/u-boot/u-boot-socfpga/qts |
Add the generated files to the u-boot bbappend file:
~/intelFPGA_lite/20.1/embedded/embedded_command_shell.sh |
navigate to your quartus project directory and convert the handoff data into source code:
Code Block |
---|
Code Block |
---|
language | bash |
---|
theme | Midnight |
---|
linenumbers | true |
---|
|
cd path/to/yoctoquartus/pokyproject
recipetoolmkdir edit u-boot-socfpga-p build
bsp-create-settings --type spl --bsp-dir build \
--preloader-settings-dir hps_isw_handoff/soc_system_hps_0/ \
--settings build/settings.bsp |
Next you have to run the qts_filter to take the sources from the handoff folder, format them and copy them to u-boot source code.
Fetch qts_filter.sh from githubAdd qts_filter files and the following task to copy the qts_filter files to the correct place in u-boot sources during build image (if your are using another board, you have to adjust the file path):
Code Block |
---|
|
SRC_URI += "file://qts/iocsr_config.h \
file://qts/pinmux_config.h \
file://qts/pll_config.h \
file://qts/sdram_config.h \
"
do_configure_prepend () {
install -m 0644 ${WORKDIR}/qts/iocsr_config.h ${S}/board/altera/cyclone5-socdk/qts/
install -m 0644 ${WORKDIR}/qts/pinmux_config.h ${S}/board/altera/cyclone5-socdk/qts/
install -m 0644 ${WORKDIR}/qts/pll_config.h ${S}/board/altera/cyclone5-socdk/qts/
install -m 0644 ${WORKDIR}/qts/sdram_config.h ${S}/board/altera/cyclone5-socdk/qts/
} |
For more information see u-boot-socfpga/doc/README.socfpga.
bash | theme | Midnight |
---|
linenumbers | true |
---|
|
wget https://raw.githubusercontent.com/altera-opensource/u-boot-socfpga/socfpga_v2021.04/arch/arm/mach-socfpga/qts-filter.sh |
Run qts_filter for cyclone5 to format and copy the handoff files to custom meta layer:
Code Block |
---|
language | bash |
---|
theme | Midnight |
---|
linenumbers | true |
---|
|
mkdir -p path/to/yocto/poky/meta-custom/recipes-bsp/u-boot/u-boot-socfpga/qts
./qts_filter.sh cyclone5 \
path/to/quartus/project \
path/to/quartus/project/build \
path/to/yocto/poky/meta-custom/recipes-bsp/u-boot/u-boot-socfpga/qts |
Add the generated files to the u-boot bbappend file:
Code Block |
---|
language | bash |
---|
theme | Midnight |
---|
linenumbers | true |
---|
|
cd path/to/yocto/poky/meta-custom/recipes-bsp/u-boot
gedit u-boot-socfpga*.bbappend |
Add qts_filter files and the following task to copy the qts_filter files to the correct place in u-boot sources during build image (if your are using another board, you have to adjust the file path):
Code Block |
---|
|
SRC_URI += "file://qts/iocsr_config.h \
file://qts/pinmux_config.h \
file://qts/pll_config.h \
file://qts/sdram_config.h \
"
do_configure_prepend () {
install -m 0644 ${WORKDIR}/qts/iocsr_config.h ${S}/board/altera/cyclone5-socdk/qts
install -m 0644 ${WORKDIR}/qts/pinmux_config.h ${S}/board/altera/cyclone5-socdk/qts
install -m 0644 ${WORKDIR}/qts/pll_config.h ${S}/board/altera/cyclone5-socdk/qts
install -m 0644 ${WORKDIR}/qts/sdram_config.h ${S}/board/altera/cyclone5-socdk/qts
} |
For more information see u-boot-socfpga/doc/README.socfpga.
Add custom device tree
u-boot
To add an own device tree to u-boot do following steps:
Copy the .dts/.dtsi files to meta-custom/recipes-bsp/u-boot/u-boot-socfpga/dts:
Code Block |
---|
language | bash |
---|
theme | Midnight |
---|
linenumbers | true |
---|
|
mkdir -p path/to/yocto/poky/meta-custom/recipes-bsp/u-boot/u-boot-socfpga/dts
cp custom.dts path/to/yocto/poky/meta-custom/recipes-bsp/u-boot/u-boot-socfpga/dts/custom.dts
cp custom-u-boot.dtsi path/to/yocto/poky/meta-custom/recipes-bsp/u-boot/u-boot-socfpga/dts/custom-u-boot.dtsi |
Add the .dts/.dtsi files to the u-boot bbappend file:
Code Block |
---|
language | bash |
---|
theme | Midnight |
---|
linenumbers | true |
---|
|
cd path/to/yocto/poky/meta-custom/recipes-bsp/u-boot
gedit u-boot-socfpga*.bbappend |
Copy the following code to the u-boot bbappend file to copy the files to the correct directory and add them to the correct Makefile:
Code Block |
---|
|
SRC_URI += "[...]
file://dts/custom.dts \
file://dts/custom-u-boot.dtsi \
"
do_configure_prepend () {
[...]
install -m 0644 ${WORKDIR}/dts/custom.dts ${S}/arch/arm/dts
install -m 0644 ${WORKDIR}/dts/custom-u-boot.dtsi ${S}/arch/arm/dts
} |
Redefine the variable UBOOT_EXTLINUX_FDT_default with the file name of your device tree in the machine configration file of meta-custom:
Code Block |
---|
theme | Midnight |
---|
linenumbers | true |
---|
|
sed -i '/^UBOOT_EXTLINUX_FDT_default/s/".*"/"..\/custom.dtb"/g' path/to/yocto/poky/meta-custom/conf/machine/custom.conf |
- Change in menuconfig the device tree to custom.dts:
- Run menuconfig as described here: Create a custom BSP layer for Intel fpga (Note: If a devtool-fragment.cfg file for u-boot already exists in the meta-custom layer, you should update it manually, otherwise the existing changes there will be deleted)
- Go to Boot options → Default fdt file and change the value to 'custom.dtb'
- Go to Device Tree Control → Default Device Tree for DT control and change the value to 'custom'
linux kernel
Adding your own device tree to the linux kernel is similar to the steps above:
Copy the .dts file to meta-custom/recipes-kernel/linux/linux-altera-lts/dts:
Code Block |
---|
language | bash |
---|
theme | Midnight |
---|
linenumbers | true |
---|
|
mkdir -p path/to/yocto/poky/meta-custom/recipes-kernel/linux/linux-altera-lts/dts
cp custom.dts path/to/yocto/poky/meta-custom/recipes-kernel/linux/linux-altera-lts/dts/custom.dts |
Add the .dts file to the linux kernel bbappend file:
Code Block |
---|
language | bash |
---|
theme | Midnight |
---|
linenumbers | true |
---|
|
cd path/to/yocto/poky/meta-custom/recipes-kernel/linux
gedit liunx-altera-lts*.bbappend |
Copy the following code to the linux kernel bbappend file to copy the files to the correct directory during image generation:
Code Block |
---|
|
SRC_URI += "[...]
file://dts/custom.dts \
"
do_configure_prepend () {
[...]
install -m 0644 ${WORKDIR}/dts/custom.dts ${S}/arch/${ARCH}/boot/dts
} |
Redefine the variable KERNEL_DEVICETREE with the file name of your device tree in the machine configration file of meta-custom.
Open the custom.conf file:
Code Block |
---|
theme | Midnight |
---|
linenumbers | true |
---|
|
gedit path/to/yocto/poky/meta-custom/conf/machine/custom.conf |
Delete the content of the variable KERNEL_DEVICETREE and add your customized device tree:
Code Block |
---|
|
KERNEL_DEVICETREE = "custom.dtb"
|
It is possible to add an fpga configuration file to the meta layer, which is used to configure the fpga from u-boot.
- First generate an rbf file from the sof file generated by the quartus project:
run the nios ii command shell (Intel Quartus):
Code Block |
---|
language | bash |
---|
theme | Midnight |
---|
linenumbers | true |
---|
|
~/intelFPGA_lite/20.1/nios2eds/nios2_command_shell.sh |
run following command to convert the sof file to rbf:
Code Block |
---|
language | bash |
---|
theme | Midnight |
---|
linenumbers | true |
---|
|
cd path/to/quartus/project/output_files
quartus_cpf -c -o bitstream_compression=on custom.sof soc_system.rbf |
Run following commands to create a recipe in the specified directory:
Code Block |
---|
language | bash |
---|
theme | Midnight |
---|
linenumbers | true |
---|
|
mkdir -p path/to/yocto/poky/meta-custom/recipes-bsp/rbf
cat > path/to/yocto/poky/meta-custom/recipes-bsp/rbf/custom-rbf.bb << EOF
DESCRIPTION = "Add fpga configuration file to image"
LICENSE = "MIT"
LIC_FILES_CHKSUM = "file://\${COMMON_LICENSE_DIR}/MIT;md5=0835ade698e0bcf8506ecda2f7b4f302"
FILESEXTRAPATHS_prepend := "\${THISDIR}/files:"
SRC_URI = " file://soc_system.rbf"
inherit deploy
do_deploy () {
install -m 0644 \${WORKDIR}/soc_system.rbf \${DEPLOYDIR}
}
addtask deploy after do_compile
EOF |
Create the files folder in meta-custom/recipes-bsp/rbf and copy the rbf file there:
Code Block |
---|
language | bash |
---|
theme | Midnight |
---|
linenumbers | true |
---|
|
mkdir -p path/to/yocto/poky/meta-custom/recipes-bsp/rbf/files
cp path/to/soc_system.rbf path/to/yocto/poky/meta-custom/recipes-bsp/rbf/files/ |
Add with the variable IMAGE_BOOT_FILES the rbf file to the FAT partition of the image in the machine configuration file of meta-custom layer:
Code Block |
---|
language | bash |
---|
theme | Midnight |
---|
linenumbers | true |
---|
|
echo -e '\nIMAGE_BOOT_FILES += "soc_system.rbf"' >> path/to/yocto/poky/meta-custom/conf/machine/custom.conf |
Add the following commands to CONFIG_BOOTCOMMAND via u-boot menuconfig, so that u-boot will configure the fpga with the rbf file:
- Run menuconfig as described here: Create a custom BSP layer for Intel fpga (Note: If a devtool-fragment.cfg file for u-boot already exists in the meta-custom layer, you should update it manually, otherwise the existing changes there will be deleted)
- Go to Boot options and enable 'Enable a default value for bootcmd'
- Change the value of 'bootcmd value' to 'load mmc 0:1 $loadaddr soc_system.rbf; fpga load 0 $loadaddr $filesize; bridge enable; run distro_bootcmd'
References
Scroll Ignore |
---|
Scroll Ignore |
---|
scroll-pdf | true |
---|
scroll-office | true |
---|
scroll-chm | true |
---|
scroll-docbook | true |
---|
scroll-eclipsehelp | true |
---|
scroll-epub | true |
---|
scroll-html | true |
---|
|
- Linux Kernel Development Manual
- Reference Manual#devtool Quick Reference
- Board Support Package (BSP) Developers's Guide
- u-boot-socfpga/doc/README.socfpga
- Patching the source for a recipe
- Intel SoC EDS User Guide