Hello to everyone.
Im a doctorate of the department of Electronics Engineering of the University of Modena and Reggio Emilia (Italy) and Im working in collaboration with a company in Bologna (Italy). This company gave me an Altera Cyclone V SOC Development Kit (already used by others inside the company, but I made sure it was brought back in the factory settings depicted by the user manual).
I have to admit that Im pretty new to Linux, and I have little knowledge about the way operating systems work (much more about how a transistor works or is made). I have followed no one course in my academic career about how to bother with operating systems compilations. I instead have a good knowledge about C language and a sufficient knowledge about assembly and matlab. And, as you will have noticed, not being a native speaker, even my English is not perfect: sorry for that.
I work on Ubuntu 14.04 LTS operating in a virtual machine (VirtualBox version 5.2.12) running on Windows 8.1 operating in my laptop; Ubuntu is updated to the latest version and also all the packages installed.
Using the included SDcard image (with Angstrom Linux) and all the factory settings the kit works just fine, with no particular trouble.
Now, in the last weeks I was slavishly following the getting started guides available at rocketboards.org for the 17.1 toolkit (at the time when I have started 18.0 was not yet delivered).
- I have started with Compiling the Hardware Design using the 2017.10 GSRD and using the 17.1 version of Quartus, generating the system in Platform Developer. The procedure terminates correctly and all the files supposed to be generated, they are.
- Then following the guide Generating and Compiling the Preloader I generate and compile the preloader and again this time it seems that all the required files have been generated correctly in the appropriate folder.
- Next, I generate the device tree using the device tree generator (sopc2dts) adopting the following settings:
sopc2dts --input soc_system.sopcinfo\
--output socfpga.dtb\
--type dtb\
--board soc_system_board_info.xml\
--board hps_common_board_info.xml\
--bridge-removal all\
--clocks\
--verbose
And the file is generated, I suppose correctly, again, but I have read that sometimes sopc2dts can give some problems.
- The next step is the Linux compilation, made following again the apposite guide on rocketboards.org, again in the version for the 17.1 gsrd release. I have set the host with all the packages shown in the guide; the only trouble is with ia32-libs needed since my machine is 64 bits: that package cannot be found and so cannot be installed. Then I proceed by building kernel and rootfs using angstrom 2017.10 distribution, i.e. using the following commands:
cd ~
mkdir angstrom-build
cd angstrom-build
wget http://releases.rocketboards.org/rel...src/altera.xml
wget http://commondatastorage.googleapis....downloads/repo
chmod 777 repo
export PATH=$PATH:~/angstrom-build
repo init -u git://github.com/Angstrom-distribution/angstrom-manifest -b angstrom-v2017.06-yocto2.3
mkdir -p .repo/local_manifests
mv altera.xml .repo/local_manifests/
repo sync
MACHINE=cyclone5 . ./setup-environment # Replace machine name (eg. MACHINE=cyclone5) with the target family, options are: cyclone5, arria5, arria10 and stratix10
sed -i '/meta-altera/a \ \ ${TOPDIR}\/layers\/meta-altera-refdes \\' conf/bblayers.conf # This is to add the meta-altera-refdes layer to conf/bblayers.conf
sed -i '/meta-atmel/d' conf/bblayers.conf # We do not need this layer
sed -i "s%/usr/bin/env python$%/usr/bin/env python2%" ~/bin/repo
export KERNEL_PROVIDER=linux-altera-ltsi
export KERNEL_TAG=refs/tags/ACDS17.1_REL_GSRD_UPDATE1_PR # Check above for newer release tags and replace it with the version you are building with
export UBOOT_TAG=refs/tags/ACDS17.1_REL_GSRD_UPDATE1_PR # Check above for newer release tags and replace it with the version you are building with
export KBRANCH=socfpga-4.9.78-ltsi # Check above for release branch to use
BB_ENV_EXTRAWHITE="$BB_ENV_EXTRAWHITE KBRANCH KERNEL_TAG UBOOT_TAG KERNEL_PROVIDER"
sudo bitbake gsrd-console-image The only differences from the scripts found in the guide is the substitution of the machine name target with cyclone5, and in the line sed -i '/meta-altera/a \ \ ${TOPDIR}\/layers\/meta-altera-refdes \\' conf/bblayers.conf # This is to add the meta-altera-refdes layer to conf/bblayers.conf layers has replaced sources in the folder path since in the downloaded and extracted packet the sources folder doesnt exist.
Now, the final report is:
NOTE: Tasks Summary: Attempted 3359 tasks of which 6 didn't need to be rerun and all succeeded.
NOTE: Writing buildhistory
Summary: There were 131 WARNING messages shown.
Of the images that should be generated, I cant find the evidenced ones, I dont know why.
u-boot-* U-Boot ELF file
u-boot-*.bin U-Boot binary file
u-boot-*.img U-Boot image
vmlinux Kernel ELF file
zImage Compressed kernel image
gsrd-console-image-*.cpio GSRD Root Filesystem in cpio archive format
gsrd-console-image-*.ext3 GSRD Root Filesystem as ext3 image
gsrd-console-image-*.tar.gz GSRD Root Filesystem in tar gzip archive format
gsrd-console-image-*.tar.xz GSRD Root Filesystem in tar archive format
gsrd-console-image-*.jffs2 GSRD Root Filesystem in jffs2 format
console-image-*.cpio Standard Angstrom Root Filesystem in cpio archive format
console-image-*.ext3 Standard Angstrom Root Filesystem as ext3 image
console-image-*.tar.gz Standard Angstrom Root Filesystem in tar gzip archive format
console-image-*.tar.xz Standard Angstrom Root Filesystem in tar archive format
console-image-*.jffs2 GSRD Root Filesystem in jffs2 format
- I have created once the u-boot.scr script using the instructions in the guide Progremming FPGA.
Continue...