Changes

← Older edit

BELK/BXELK software components

9,327 bytes added, 09:27, 18 October 2022

no edit summary

~~From the software standpoint, BELK and BXELK are built on to of Zynq Linux BSP released by Xilinx. Customization are added to support the~~ {{InfoBoxTop}}{{Applies To Bora ~~and~~ }}{{Applies To BoraX ~~platforms, in particular at bootloader and linux kernel levels.~~}}{{Applies To BoraLite}}{{InfoBoxBottom}}

{{ObsoleteWikiPage|link=BORA_SOM/BELK-L/General/Release_Notes}} __FORCETOC__==Introduction==From the software standpoint, [[Bora Embedded Linux Kit (BELK)|Bora Embedded Linux Kit (BELK)]] and [[BoraX_Embedded_Linux_Kit_(BXELK)|BoraX Embedded Linux Kit (BXELK)]] are built on top of Zynq Linux BSP released by Xilinx. Customizations are added to support for the Bora and BoraX platforms, in particular at bootloader and Linux kernel levels. BELK and BXELK share the '''same''' software modules, even if they are based on different hardware platforms. Reading of [[Host_setup_and_development_flow_(BXELK)|this document]] is strongly recommended to understand the logical structure of the kits and how the software components are related. ==Kits' composition==The following table ~~reports~~ details the software modules of BELK/BXELK releases ~~information~~.

{| class="wikitable"

!colspan="812" | Kit composition!

|-

|'''Release number''' BELK BXELK

| 1.0.0 n/a

| 1.1.0 n/a

| 2.2.0 n/a

| 3.0.0 n/a

| 3.0.1 1.0.0| 3.0.2 1.0.1| 4.0.0 2.0.0| 4.91.0 4.1.0| 4.1.2 4.1.2| 4.1.4 4.1.4

|-

|'''Status''' BELK BXELK

| Released n/a

|-

|'''Release date''' BELK BXELK

| July 2013 n/a

| November 2013 n/a

| March 2016 n/a

| December 2016 December 2016

| January 2017 January 2017

| July 2017 July 2017

| Jan 2020 Jan 2020

| Sep 2020 Sep 2020

| Jul 2021 Jul 2021

|-

|'''Release notes''' BELK BXELK

| [[#BELK 1.0.0 | Ver 1.0.0]]

| [[#BELK 1.1.0 | Ver 1.1.0]]

| [[#BELK 2.0.0 | Ver 2.0.0]]

| [[#BELK 2.1.0 | Ver 2.1.0]]

| [[#BELK 2.2.0 | Ver 2.2.0]]

| [[#BELK 3.0.0 | Ver 3.0.0]]

| [[#BELK_3.0.1_.2F_BXELK_1.0.0 | Ver 3.0.1]]| [[#BELK_3.0.2_.2F_BXELK_1.0.1 | Ver 3.0.2]]| [[#BELK_4.0.0_.2F_BXELK_2.0.0 | Ver 4.0.0]]| [[#BELK_4.1.0 | Ver 4.1.0]]| [[BELK/BXELK software components#BELK 4.1.2|Ver 4.1.2]]| [[BELK/BXELK software components#BELK 4.1.4|Ver 4.1.4]]

|-

|--

|'''Supported carrier boards''' BELK BXELK

| [[BoraEVB-Lite]] n/a

| [[BoraEVB]] n/a

| [[BoraEVB]] [[BoraXEVB]]

|-

|'''U-Boot version'''

|2013.04-belk-1.0.0

|2013.04-belk-1.1.0

|2014.07-belk-2.2.0

|2014.07-belk-3.0.0

|2014.07-belk-3.0.2

|2017.01-belk-4.0.1

|2017.01-belk-4.1.1

|2017.01-belk-4.1.2

|2017.01-belk-4.1.4

|-

|'''Linux version'''

|3.9.0-bora-1.0.0

|3.9.0-bora-1.1.0

|3.17.0-bora-2.2.0

|3.17.0-bora-3.0.0

|4.9.0-bora-4.0.0

|4.9.0-bora-4.1.0

|4.9.0-bora-4.1.4

|-

|-

|'''Vivado version'''|valign="top" | 2013.2|valign="top" | 2013.3|valign="top" | 2013.3|valign="top" | 2013.3|valign="top" | 2014.4|valign="top" | 2014.4| valign="top" | 2014.4| valign="top" | 2014.4| valign="top" | 2017.1| valign="top" | 2017.1| valign="top" | 2017.1| valign="top" | 2017.1

|-

|-

|'''[[Managed Virtual Machine (MVM)]]'''

|N/A

|belk-4.0.0 (based on Ubuntu 14.04 64 bit)

|belk-4.1.0 (based on Ubuntu 14.04 64 bit)

|}

== Downloadable binary images==

~~=== How to update BELK ===~~

~~{{ImportantMessage|text=It's recommended to use the latest available~~ All binary images for BELK ~~version. Please refer to~~ /BXELK are hosted on [[~~Bora_Embedded_Linux_Kit_(BELK)#Release_notes~~ mirror:bora| ~~Release notes~~DAVE Embedded System mirror server]] . There you can find a sub directory for ~~further information~~each version of this development kit.}}

A summary of images with a brief description can be found in the tables below.{{ImportantMessage|text=In order to create a [[System_boot_and_recovery_via_microSD_card_(BELK/BXELK)#How_to_create_a_bootable_microSD_card|bootable microSD card]], '''the binary files must be renamed''' as follows:* For '''BELK <=3.0.2''' and '''BXELK <=~~= Updating git repositories ====~~1.0.1''' :**FSBL: <code>boot.bin</code>**Linux kernel: <code>uImage</code>**Device tree: <code>bora.dtb</code>* For '''BELK-4.1.0''' or newer and '''BXELK-2.0.0''' or newer:**U-Boot SPL: <code>boot.bin</code>**U-Boot: <code>u-boot.img</code>**[[BELK-AN-008:_Programming_the_FPGA_Bitstream_with_U-Boot|FPGA Bitstream]]: <code>fpga.bit</code>**Linux kernel: <code>uImage</code>**Device tree: <code>bora.dtb</code>}}

In {| class="wikitable"|-! rowspan="2" |Image !! colspan="1" |BELK~~, the following source trees are clones of '''DAVE Embedded Systems''' public git repositories~~version !! colspan="1" |BXELK version|-| 4.1.4 || 4.1.4|-| mksd.sh || [[mirror:bora/belk-4.1.4/mksd.sh|mksd.sh]] || [[mirror:bora/belk-4.1.4/mksd.sh|mksd.sh]]|-| [[Working_with_the_Yocto_build_system#bootscript|bootscript]] || [[mirror:bora/belk-4.1.4/boot.scr|boot.scr]] || [[mirror:bora/belk-4.1.4/boot.scr|boot.scr]]|-| U-Boot SPL (for uSD boot)|| [[mirror:bora/belk-4.1.4/belk-4.1.4_bora_mmc_boot.bin|boot.bin]] || [[mirror:bora/belk-4.1.4/belk-4.1.4_borax_mmc_boot.bin|boot.bin]]|-| U-Boot SPL (for NOR flash boot)|| [[mirror:bora/belk-4.1.4/belk-4.1.4_bora_qspi_boot.bin|boot.bin]] || [[mirror:bora/belk-4.1.4/belk-4.1.4_borax_qspi_boot.bin|boot.bin]]|-| U-Boot SPL (for NAND flash boot) (for BoraLite SOM)|| [[mirror:bora/belk-4.1.4/belk-4.1.4_bora_nand_boot.bin|boot.bin]] || -|-| U-Boot (for uSD boot) || [[mirror:bora/belk-4.1.4/belk-4.1.4_bora_mmc_u-boot.img|u-boot.img]] || [[mirror:bora/belk-4.1.4/belk-4.1.4_borax_mmc_u-boot.img|u-boot.img]]|-| U-Boot (for NOR flash boot)|| [[mirror:bora/belk-4.1.4/belk-4.1.4_bora_qspi_u-boot.img|u-boot.img]] || [[mirror:bora/belk-4.1.4/belk-4.1.4_borax_qspi_u-boot.img|u-boot.img]]|-| U-Boot (for NAND flash boot) (for BoraLite SOM)|| [[mirror:bora/belk-4.1.4/belk-4.1.4_bora_nand_u-boot.img|u-boot.img]] || -|-| [[BELK-AN-008:_Programming_the_FPGA_Bitstream_with_U-Boot|FPGA Bitstream]] || [[mirror:bora/belk-4.1.0/belk-4.1.0_bora_BASE_fpga.bit|fpga.bit]] || [[mirror:bora/belk-4.1.0/belk-4.1.0_borax_BASE__fpga.bit|fpga.bit]]|-| Linux kernel || [[mirror:bora/belk-4.1.4/belk-4.1.4_uImage|uImage]] || [[mirror:bora/belk-4.1.4/belk-4.1.4_uImage|uImage]]|-| Device tree || [[mirror:bora/belk-4.1.4/belk-4.1.4_bora.dtb|bora.dtb]] || [[mirror:bora/belk-4.1.4/belk-4.1.4_bora.dtb|bora.dtb]]|-|Root File System || [[mirror:bora/belk-4.1.4/belk-4.1.4_dave-image-devel-bora.tar.bz2|bora.tar.bz2]] || [[mirror:bora/belk-4.1.4/belk-4.1.4_dave-image-devel-bora.tar.bz2|bora.tar.bz2]]|}

{| class="wikitable" |-! rowspan="2" |Image !! colspan="1" |BELK version !! colspan="1" |BXELK version|-| 3.0.2 || 1.0.1 |-| mksd.sh || [[mirror:bora/belk-3.0.2/mksd.sh|mksd.sh]] || [[mirror:bora/bxelk-1.0.1/mksd.sh|mksd.sh]]|-| [[Working_with_the_Yocto_build_system#bootscript|bootscript]]|| [[mirror:bora/belk-3.0.2/boot.scr|boot.scr]] || [[mirror:bora/bxelk-1.0.1/boot.scr|boot.scr]]|-| FSBL (QSPI) || [[mirror:bora/belk-3.0.2/belk-3.0.0_bora_fsbl.bin|fsbl.bin]] || [[mirror:bora/bxelk-1.0.1/belk-3.0.0_borax_fsbl.bin|fsbl.bin]]|-| U-Boot (QSPI) || [[mirror:bora/belk-3.0.2/belk-3.0.2_bora_qspi_u-boot.bin|u-boot.bin]] || [[mirror:bora/bxelk-1.0.1/belk-3.0.2_bora_qspi_u-boot.bin|u-boot.bin]]|-| Boot.bin (SD) || [[mirror:bora/belk-3.0.2/belk-3.0.2_bora_mmc_boot.bin|boot.bin]] || [[mirror:bora/bxelk-1.0.1/belk-3.0.2_borax_mmc_boot.bin|boot.bin]]|-| Boot header || [[mirror:bora/belk-3.0.2/boot_header-1.0.1|boot-header]] || [[mirror:bora/bxelk-1.0.1/boot_header-1.0.1|boot-header]]|-| Linux kernel || [[mirror:bora/belk-3.0.2/belk-3.0.0_uImage|uImage]] || [[mirror:bora/bxelk-1.0.1/belk-3.0.0_uImage|uImage]]|-| Device tree || [[mirror:bora/belk-3.0.2/belk-3.0.0_bora.dtb|bora.dtb]] || [[mirror:bora/bxelk-1.0.1/belk-3.0.0_bora.dtb|bora.dtb]]|-|Root File System || [[mirror:bora/belk-3.0.2/belk-3.0.2_bora-image-devel-bora.tar.gz|bora.tar.gz]] || [[mirror:bora/belk-3.0.2/belk-3.0.2_bora-image-devel-bora.tar.gz|bora.tar.gz]]|} {| class="wikitable"|-! rowspan="2" |Image !! colspan="1" |BELK version !! colspan="1" |BXELK version|-| 3.0.1 || 1.0.0 |-| mksd.sh || [[mirror:bora/belk-3.0.1/mksd.sh|mksd.sh]] || [[mirror:bora/bxelk-1.0.0/mksd.sh|mksd.sh]]|-| uEnv || [[mirror:bora/belk-3.0.1/uEnv.txt|uEnv.txt]] || [[mirror:bora/bxelk-1.0.0/uEnv.txt|uEnv.txt]]|-| FSBL (QSPI) || [[mirror:bora/belk-3.0.1/belk-3.0.0_bora_fsbl.bin|fsbl.bin]] || [[mirror:bora/bxelk-1.0.0/belk-3.0.0_borax_fsbl.bin|fsbl.bin]]|-| U-Boot (QSPI) || [[mirror:bora/belk-3.0.1/belk-3.0.0_bora_qspi_u-boot.bin|u-boot.bin]] || [[mirror:bora/bxelk-1.0.0/belk-3.0.0_bora_qspi_u-boot.bin|u-boot.bin]]

|-

!| ~~Component!GIT Remote~~Boot.bin (SD) || [[mirror:bora/belk-3.0.1/belk-3.0.0_bora_mmc_boot.bin|boot.bin]] || [[mirror:bora/bxelk-1.0.0/belk-3.0.0_borax_mmc_boot.bin|boot.bin]]

|-

|~~Vivado project~~Boot header |~~git@git~~| [[mirror:bora/belk-3.~~dave~~0.eu1/boot_header-1.0.1|boot-header]] || [[mirror:~~dave~~bora/~~bora~~bxelk-1.0.0/~~bora~~boot_header-1.0.~~git~~1|boot-header]]

|-

|Linuxkernel |~~git@git~~| [[mirror:bora/belk-3.~~dave~~0.eu1/belk-3.0.0_uImage|uImage]] || [[mirror:~~dave~~bora/~~bora~~bxelk-1.0.0/~~linux~~belk-~~xlnx~~3.0.~~git~~0_uImage|uImage]]

|-

|UDevice tree || [[mirror:bora/belk-~~Boot~~3.0.1/belk-3.0.0_bora.dtb|~~git@git~~bora.~~dave.eu~~dtb]] || [[mirror:~~dave/~~bora/ubxelk-~~boot~~1.0.0/belk-~~xlnx~~3.0.0_bora.dtb|bora.~~git~~dtb]]

|-

|Root File System || [[mirror:bora/belk-3.0.1/belk-3.0.1_bora-image-devel-bora.tar.gz|bora.tar.gz]] || [[mirror:bora/belk-3.0.1/belk-3.0.1_bora-image-devel-bora.tar.gz|bora.tar.gz]]

|}

~~This means that these components can be kept~~ <section begin=microSDlayout/>===microSD layout===The microSD card provided with BELK/BXELK is partitioned as shown in ~~sync and up to date with '''DAVE Embedded Systems''' repositories.~~the following image:

~~==== RSA key generation ====~~

~~Please follow the procedure reported below to generate the RSA ssh key~~[[File:BXELK-uSD-partitioning.png|thumb|center|400px|microSD card partitioning]]

* select your username (ad es. username@myhost.com)

* start your Linux development server machine

* start a shell session

* make sure the '''ssh''' client components are installed

* enter the .ssh subdirectory into your home directory: <code>cd ~/.ssh/</code>

* launch the following command: <pre>ssh-keygen -t rsa -C "username@myhost.com" -f username@myhost.com</pre>

* this command creates the files <code>~/.ssh/username@myhost.com</code> ('''private key''') and <code>~/.ssh/username@myhost.com.pub</code> ('''public key''')

* edit your <code>~/.ssh/config</code> adding the following lines:

Most of storage space is occupied by two partitions:*a <code>FAT32</code> partition (<code>mmcblk0p1<~~pre~~/code>) containing:~~Host git~~** For '''BELK <= 3.0.2''' and '''BXELK <= 1.~~dave~~0.eu1''' : ~~User git~~***<code>boot.bin</code> boot image (containing FSBL, FPGA Bitstream an U-boot binaries) ~~Hostname git~~***U-Boot <code>boot.~~dave~~scr</code> bootscript***Linux kernel and DTB binary images** For '''BELK 4.0.eu0''' or newer and '''BXELK 2.0.0''' or newer: ~~PreferredAuthentications publickey~~***<code>boot.bin</code> u-boot SPL image ~~IdentityFile ~~~***<code>fpga.bit</code> optional [[BELK-AN-008:_Programming_the_FPGA_Bitstream_with_U-Boot|FPGA bitstream]]***<code>u-boot.~~ssh~~img</~~username@myhost~~code> u-boot image***U-Boot <code>boot.~~com~~scr</code> bootscript***Linux kernel and DTB binary images*** MVM image in OVA format*an <code>ext3</~~pre~~code> partition (<code>mmcblk0p2</code>) containing the root file system for the target.

~~Please send the public key~~ bootscript and root file system are used to boot the ~~following email support addresses:~~target as described in [[BELK/BXELK_Quick_Start_Guide#Target_setup_and_first_boot|this section]].

* It is worth remembering that the microSD card is [~~mailto:support~~[System boot and recovery via microSD card (BELK/BXELK)|bootable]] and U-Boot environment is retrieved from (and stored to with <code>saveenv</code>) into the FAT partition as <code>bora~~@dave~~.~~eu support-bora@dave.eu]~~env</code><section end=microSDlayout/>

~~with~~ ==Updates=={{ImportantMessage|text=It's recommended to use the ~~request~~ latest source release available. Please refer to [[#Release_notes | Release notes]] for ~~the creation of a new public git account associated to your username. The support team will enable the account and send you a confirmation as soon as possible~~further information.}}

<section begin="Synchronizing" the="" git="" repositories="" /><section begin=Synchronizingthegitrepositories/> === Updating git repositories ===In BELK/BXELK, the following source trees are clones of the correspondent '''DAVE Embedded Systems''' git repositories:{| class="wikitable"|-!| Component!GIT Remote|-|U-Boot|<code>git@git.dave.eu:dave/bora/u-boot-xlnx.git</code>|-|Linux kernel|<code>git@git.dave.eu:dave/bora/linux-xlnx.git</code>|-|Yocto BSP|<code>git@git.dave.eu:dave/bora/bora-bsp.git</code>|-|Vivado project|<code>git@git.dave.eu:dave/bora/bora.git</code>|-|}For more information about the access to these repositories, please refer to [[Accessing_DAVE_Embedded_Systems_restricted_git_repositories#Public_key_access|this link]]. === Updating the repositories from BELK 2.1.0 ====

{{ImportantMessage|text=To '''update the repositories from BELK 2.1.0''', the following commands should be used:}}

</pre>

==== Synchronizing the repositories ====

When the account is enabled, you can synchronize a source tree entering the repository directory and launching the <code>git fetch</code> command. Please note that <code>git fetch</code> doesn't merge the commits on the current branch. To do that, you should run the <code>git merge</code> command or replace the ''fetch-merge'' process with a single <code>git pull</code> command. Please note that the recommended method is the ''fetch-merge'' process. For further information on Git, please refer to [http://git-scm.com/documentation Git Documentation].

<section begin=Releasenotes/>== Release notes ===

==== BELK 34.01.~~0 =~~4 ===

Updates:

# ~~Added support~~ Fixes for ~~BORA Xpress SOM# Updated U~~MAC programming on [[BELK-~~Boot and Linux versions~~TN-010: MAC address programming on OTP|NOR SPI OTP]]

===== Known Limitations =====

{| class="wikitable"

|-

!~~Issue~~ID!Component!Subsystem

!Description

|-

| ~~Yocto ubi-utils command line~~0001| ~~Some Yocto ubi-utils command line are in non standard format. For ''ubimkvol'' and ''ubirmvol'' the UBI device must be the last argument (e.g. ubimkvol -m -N belk /dev/ubi0)~~|-BoraEVB|External DDR3 bank (BoraEVB only)|~~The~~ DDR3 ~~SDRAM~~ bank can be populated on ~~the BoraEVB is not supported in this BELK version~~request. For more details please refer to [mailto:sales@dave.eu Sales Department].

|-

|0002

|BoraEVB/BoraXEVB

|ETH1 interface

|~~The additional Gigabit~~ Please refer to [[AN-BELK-006:_Enabling_dual_Gigabit_Ethernet_support_on_BoraEVB/BoraXEVB|this application note]] for second Ethernet interface ~~(ETH1) is not supported in this BELK version~~support.

|-

|0003

|BoraEVB/BoraXEVB

|RTC

|Date/time retention is limited to about 4 hours.

|-

|0004

|BoraEVB/BoraXEVB

|System clock runs slower

|As per [https://xilinx-wiki.atlassian.net/wiki/spaces/A/pages/18841831/CPU+frequency+scaling#Missing%20Features,%20Known%20Issues%20and%20Limitations Xilinx issue], @333MHz (speedgrade -3) system clock is slower then expected

|}

==== BELK 24.1.2~~.0 =~~===

Updates:

~~# Switched to Vivado 2014.4~~# Added ~~“board part”~~ support for ~~the BORA SOM, which includes all the settings of the Zynq PS for BORA, allowing users to manage projects from the Vivado GUI (and not only using the CLI).# Added~~ MAC programming on [[~~ConfigID_and_UniqueID~~ BELK-TN-010: MAC address programming on OTP| ~~ConfigID~~NOR SPI OTP]]~~# Updated U-Boot and Linux versions~~

===== Known Limitations =====

{| class="wikitable"

|-

!~~Issue~~ID!Component!Subsystem

!Description

|-

| ~~Kernel command line~~0001| ~~User should remove '''mem=xxx''' from kernel command line to avoid system hang during boot. This is fixed in current u-boot default environment~~|-~~| Yocto ubi-utils command line| Some Yocto ubi-utils command line are in non standard format. For ''ubimkvol'' and ''ubirmvol'' the UBI device must be the last argument (e.g. ubimkvol -m -N belk /dev/ubi0)~~|-BoraEVB|External DDR3 bank (BoraEVB only)|~~The~~ DDR3 ~~SDRAM~~ bank can be populated on ~~the BoraEVB is not supported in this BELK version~~request. For more details please refer to [mailto:sales@dave.eu Sales Department].

|-

|0002

|BoraEVB/BoraXEVB

|ETH1 interface

|~~The additional Gigabit~~ Please refer to [[AN-BELK-006:_Enabling_dual_Gigabit_Ethernet_support_on_BoraEVB/BoraXEVB|this application note]] for second Ethernet interface ~~(ETH1) is not supported in this BELK version~~support.

|-

|0003

|BoraEVB/BoraXEVB

|RTC

|Date/time retention is limited to about 4 hours.

|-

|~~u-boot default environment~~0004|BoraEVB/BoraXEVB|System clock runs slower|~~Default u-boot environment has a syntax error on ''sdboot'' command. This is already fixed in <code>bora-next<~~As per [https://~~code> branch, release <code>belk~~xilinx-2wiki.2atlassian.~~1-rc1<~~net/wiki/spaces/A/pages/18841831/~~code>~~CPU+frequency+scaling#Missing%20Features, ~~available on u~~%20Known%20Issues%20and%20Limitations Xilinx issue], @333MHz (speedgrade -~~boot repository.~~3) system clock is slower then expected

|-

|0005

|Bora/BoraX/BoraLite SOM

|NOR QSPI flash

|Wrong QSPI flash size detection in belk-4.x.x: this issue has been fixed on u-boot repository:

* tag '''belk-4.1.3'''

* related commit 6074f0dc148d9e40e82fab9ad44ab24156323312

|}

==== BELK 24.1.0 ====

Updates:

# ~~Fix and performance improvement on u-boot network interface# Fix SD card hotplug issue in Linux# First~~ Added support for [~~[Building_the_software_components_via_Yocto_(BELK)|Yocto Daisy (1~~https://www.dave.~~6) BSP Release]~~eu/products/som/xilinx/zynq-XC7Z010-XC7Z020_boralite BoraLite SOM]

===== Known Limitations =====

{| class="wikitable"

|-

!~~Issue~~ID!Component!Subsystem

!Description

|-

| ~~ETH0 interface~~0001| ~~Primary Gigabit Ethernet Interface (ETH0) is not working correctly at 10Mbps ~~|-~~| Kernel command line| User should remove '''mem=xxx''' from kernel command line to avoid system hang during boot~~|-~~| Yocto ubi-utils command line| Some Yocto ubi-utils command line are in non standard format. For ''ubimkvol'' and ''ubirmvol'' the UBI device must be the last argument (e.g. ubimkvol -m -N belk /dev/ubi0)~~|-BoraEVB|External DDR3 bank (BoraEVB only)|~~The~~ DDR3 ~~SDRAM~~ bank can be populated on ~~the BoraEVB is not supported in this BELK version~~request. For more details please refer to [mailto:sales@dave.eu Sales Department].

|-

|0002

|BoraEVB/BoraXEVB

|ETH1 interface

|~~The additional Gigabit~~ Please refer to [[AN-BELK-006:_Enabling_dual_Gigabit_Ethernet_support_on_BoraEVB/BoraXEVB|this application note]] for second Ethernet interface ~~(ETH1) is not supported in this BELK version~~support.

|-

|0003

|BoraEVB/BoraXEVB

|RTC

|Date/time retention is limited to about 4 hours.

|-

|0004

|BoraEVB/BoraXEVB

|System clock runs slower

|As per [https://xilinx-wiki.atlassian.net/wiki/spaces/A/pages/18841831/CPU+frequency+scaling#Missing%20Features,%20Known%20Issues%20and%20Limitations Xilinx issue], @333MHz (speedgrade -3) system clock is slower then expected

|}

==== BELK 4.0.0 / BXELK 2.0.0 ====

Updates:

# ~~Added support for the BoraEVB carrier board~~Switched to Vivado 2017.1# Updated ~~supported drivers list (please refer to [[Bora_Embedded_Linux_Kit_(BELK)#BELK_software_components | BELK_software_components]])~~U-Boot and Linux versions

===== Known Limitations ===== ~~The following table reports the known limitations of this BELK release:~~

{| class="wikitable"

|-

!~~Issue~~ID!Component!Subsystem

!Description

|-

|0001|BoraEVB|External DDR3 bank (BoraEVB only)|~~The~~ DDR3 ~~SDRAM~~ bank can be populated on ~~the BoraEVB is not supported in this BELK version~~request. For more details please refer to [mailto:sales@dave.eu Sales Department].

|-

|0002

|BoraEVB/BoraXEVB

|ETH1 interface

|~~The additional Gigabit~~ Please refer to [[AN-BELK-006:_Enabling_dual_Gigabit_Ethernet_support_on_BoraEVB/BoraXEVB|this application note]] for second Ethernet interface ~~(ETH1) is not supported in this BELK version~~support.

|-

|0003

|BoraEVB/BoraXEVB

|RTC

|Date/time retention is limited to about 4 hours.

|-

|0004

|MVM

|MVM Eclipse cross-toolchain configuration

|Cross-toolchain configuration in Eclipse in the BELK MVM cannot be saved correctly. To fix the problem the following commands must be issued in the MVM terminal:

<pre>

cd /home/dvdk/bora/sdk/belk-4.0.0/sysroots/

sudo ln -s x86_64-petalinux-linux x86_64-petalinuxsdk-linux

</pre>

otherwise, the SDK can be updated for fixing this issue using [https://mirror.dave.eu/bora/belk-4.0.0/belk-4.0.1_sdk.sh this] file

|-

|0005

|MVM

|MVM Eclipse gdb remote debug

|Remote debug of an application using Eclipse and gdb is not working due to an issue with the Yocto SDK included in the BELK/BXELK MVM.

This issue will be fixed in next BELK/BXELK release. The SDK can be updated for fixing this issue using [https://mirror.dave.eu/bora/belk-4.0.0/belk-4.0.1_sdk.sh this] file

|-

|0006

|MVM

|Cross-building environment

|The script <code>~/env.sh</code> does not set the CC variable properly.

To fix this, please comment out the following line:

<code>export CC=gcc</code>

|-

|0007

|BoraEVB/BoraXEVB

|System clock runs slower

|As per [https://xilinx-wiki.atlassian.net/wiki/spaces/A/pages/18841831/CPU+frequency+scaling#Missing%20Features,%20Known%20Issues%20and%20Limitations Xilinx issue], @333MHz (speedgrade -3) system clock is slower then expected

|-

|}

==== BELK 13.0.2 / BXELK 1.0 =.1 ===

Updates:

# ~~Switched to Vivado 2013~~Fix BELK-3.30.1/BXELK-1.0.0 software issues# ~~Added application note "AMP on Bora"~~Use standard DAVE recovery scripts for u-boot

~~====~~ (BoraXEVB only) For LCD interfacing, please refer to [[AN-BELK 1-004:_Interfacing_BoraEVB/BoraXEVB_to_TFT_LCD_display|this application note]].~~0.0 ====~~

~~First official release~~==== Known Limitations ====

{| class="wikitable"

|-

!ID

!Component

!Issue

!Description

|-

|0001

|BoraEVB

|External DDR3 bank (BoraEVB only)

|DDR3 bank can be populated on request. For more details please refer to [mailto:sales@dave.eu Sales Department].

|-

|0002

|BoraEVB/BoraXEVB

|ETH1 interface

|Please refer to [[AN-BELK-006:_Enabling_dual_Gigabit_Ethernet_support_on_BoraEVB/BoraXEVB|this application note]] for second Ethernet interface support.

|-

|0003

|BoraEVB/BoraXEVB

|RTC

|Date/time retention is limited to about 4 hours.

|-

|}

=== BELK/BXELK older releases ===

For BELK/BXELK older releases information, please click on Expand here below (on the right)

==== BELK 3.0.1 / BXELK 1.0.0 ====

Updates: added support for BoraX/BoraXEVB evaluation system

~~roba presa da XUELK~~(BoraXEVB only) For LCD interfacing, please refer to [[AN-BELK-004:_Interfacing_BoraEVB/BoraXEVB_to_TFT_LCD_display|this application note]].

===== Known Limitations =====

~~== BXELK software components ==~~

~~{{ImportantMessage|text=From the software perspective, BXELK supports SBC Lynx and [[:Category:AXEL_ULite|AXEL ULite SOM]]. However, physical contents of the kit include SBC Lynx only.~~

}}

BoraX Embedded Linux Kit is largely derived from the Yocto distributions released by Xilinx for the Zynq product family. For this reason most of the documentation provided by Xilinx remains valid for the BXELK development kit.

~~The following table reports the BXELK releases information.~~

{| class="wikitable"

!

~~!colspan="3" | BXELK version~~

|-

~~|Release number~~!Issue~~|0.9.0|1.0.0|1.1.0~~!Description

|-

|~~Release type~~<code>canutils</code> package is missing is default root file system|~~Major|Major~~It can be downloaded directly from our package repository as described [[Physical devices mapping (BELK/BXELK)#CAN|~~Minor~~here]]

|-

|~~Status~~External DDR3 bank (BoraEVB only)|~~Beta|Released|Released~~DDR3 bank can be populated on request. For more details please refer to [mailto:sales@dave.eu Sales Department].

|-

|~~Release date~~ETH1 interface|~~March 2016|August 2016~~Please refer to [[AN-BELK-006:_Enabling_dual_Gigabit_Ethernet_support_on_BoraEVB/BoraXEVB|~~November 2016~~this application note]] for second Ethernet interface support.

|-

|-

|~~Build System~~Boot for NOR flash|~~Yocto Fido (1~~U-Boot is not configured properly to support NOR boot.8)~~|Yocto Fido (1.8)|Yocto Fido (1~~Please use boot from microSD card instead.8)

|-

|}

==== BELK 3.0.0 ====

Updates:

# Added preliminary support for BORA Xpress SOM

# Updated U-Boot and Linux versions

(BoraXEVB only) For LCD interfacing, please refer to [1[AN-BELK-004:_Interfacing_BoraEVB/BoraXEVB_to_TFT_LCD_display|this application note]] ~~Not included in the kit~~.====~~Downloadable binary images~~= Known Limitations =====

~~All binary images for BXELK are hosted on [[mirror:lynx|DAVE Embedded System mirror server]]. There you can find a sub directory for each version of this development kit.~~ ~~A summary of images with a brief description can be found into the table below:~~ {| class="wikitable"

|-

! ~~rowspan=2|Image~~ Issue!~~! colspan=2|BXELK version~~Description

|-

| ~~1.0~~Yocto ubi-utils command line| Some Yocto ubi-utils command line are in non standard format.~~0 || 1~~For ''ubimkvol'' and ''ubirmvol'' the UBI device must be the last argument (e.1g.0ubimkvol -m -N belk /dev/ubi0)

|-

| ~~bootscript~~ External DDR3 bank (BoraEVB only)|~~| [~~DDR3 bank can be populated on request. For more details please refer to [~~mirror~~mailto:~~lynx/xuelk-1.0.0/xuelk-1.0.0_boot.scr|boot~~sales@dave.~~scr]~~eu Sales Department] ~~|| [[mirror:lynx/xuelk-1.1~~.~~0/xuelk-1.1.0_boot.scr|boot.scr]]~~

|-

| ~~U-Boot |~~ETH1 interface| Please refer to [[~~mirror:lynx/xuelk-1.0.0/xuelk-1.0.0_mx6ul_lynx_u~~AN-~~boot.imx|u~~BELK-~~boot.imx]] || [[mirror~~006:~~lynx/xuelk-1.1.0~~_Enabling_dual_Gigabit_Ethernet_support_on_BoraEVB/~~xuelk-1.1.0_mx6ul_lynx_u-boot.imx~~BoraXEVB|~~u-boot.imx~~this application note]]for second Ethernet interface support.

|-

| ~~Linux kernel~~ RTC|~~| [[mirror:lynx/xuelk-1.0.0~~Date/~~xuelk-1.0~~time retention is limited to about 4 hours.~~0_uImage|uImage]] || [[mirror:lynx/xuelk-1.1.0/xuelk-1.1.0_uImage|uImage]]~~

|-

~~| Device tree || [[mirror:lynx/xuelk-1.0.0/xuelk-1.0.0_imx6ul-lynx-som000c.dtb|imx6ul-lynx-som000c.dtb]] || [[mirror:lynx/xuelk-1.1.0/xuelk-1.1.0_imx6ul-lynx-som000c.dtb|imx6ul-lynx-som000c.dtb]]~~

|}

=== ~~BXELK microSD Layout~~ = BELK 2.2.0 ====~~The microSD card provided with BXELK is partitioned as shown in the following image:~~

Updates:

# Switched to Vivado 2014.4

# Added “board part” for the BORA SOM, which includes all the settings of the Zynq PS for BORA, allowing users to manage projects from the Vivado GUI (and not only using the CLI).

# Added [[ConfigID_and_UniqueID | ConfigID]]

# Updated U-Boot and Linux versions

~~[[File:BXELK-uSD-partitioning.png|thumb|center|600px|microSD card partitioning]]~~ ~~Most of storage space is occupied by two partitions:~~*a <code>FAT32</code> partition (<code>mmcblk0p1</code>) containing:**U-Boot <code>bootscript</code>**Linux kernel and DTB binary images**BXELK virtual machine image in OFV format ([[Managed_Virtual_Machine_(MVM)|MVM]] basic version)**7-zip Windows executable file*an <code>ext3</code> partition (<code>mmcblk0p2</code>) containing the root file system for the target. ~~<code>bootscript</code> and root file system are used to boot the target as described in [[#AXEL_ULite_and_SBC_Lynx_Embedded_Linux_Kit_(BXELK)|this section]].~~ It is worth remembering that the microSD card is [[Booting_options_(SBC_Lynx)|bootable]], because U-Boot image is stored at address 0x400. However, even if U-Boot is run from the microSD card, '''the environment is retrieved from NOR flash'''. ~~=== BXELK updates ===~~ ~~{{ImportantMessage|text=It's recommended to use the latest available BXELK version. Please refer to [[#Release notes | Release notes]] for further information.}}~~ BXELK updating process consists of updating the [[Managed_Virtual_Machine_(MVM)|Managed Virtual Machine]] it is based on. The procedure is described [[Managed_Virtual_Machine_(MVM)#Updating_MVM|here]]. Please note that this process '''implicitly updates git source code repositories of U-Boot and/or Linux kernel'''. Thus '''it is strongly recommended to create new local branches if you need to modify source code'''. ~~=== Release notes ===~~ ~~==== BXELK 1.1.0 ====~~ ~~===== Notes =====~~ ~~Minor update on BXELK 1.0.0:~~* add some useful networking support (on both Linux and file system)* fix BXELK-1.0.0 shutdown issue* fix BXELK-1.0.0 MVM network-manager issues* minor fixes and enhancement ===== Known ~~issues and limitations~~ Limitations ===== ~~The following table reports the known limitations of this BXELK release:~~

{| class="wikitable"

!Description

|-

|~~Rebooting in Linux may hang~~Kernel command line|~~Software reboot on Linux may~~ User should remove '''mem=xxx''' from kernel command line to avoid system hang ~~(without rebooting the board) when root file system~~ during boot. This is fixed in ~~on SD/MMC~~current u-boot default environment

|-

|~~USB OTG Current Limit~~Yocto ubi-utils command line|~~USB OTG current limit is set at 75mA~~ Some Yocto ubi-utils command line are in ~~Host mode~~non standard format. For ''ubimkvol'' and ''ubirmvol'' the UBI device must be the last argument (e.g. ubimkvol -m -N belk /dev/ubi0)|-|External DDR3 bank (BoraEVB only)|DDR3 bank can be populated on request. For more details please refer to [mailto:sales@dave.eu Sales Department].|-|ETH1 interface|Please refer to [[AN-BELK-006:_Enabling_dual_Gigabit_Ethernet_support_on_BoraEVB/BoraXEVB|this application note]] for second Ethernet interface support.

|-

|~~Low Power Idle not supported~~RTC|~~Low Power Idle~~ Date/time retention is ~~not supported~~ limited to about 4 hours.|-|u-boot default environment|Default u-boot environment has a syntax error on ''sdboot'' command. This is already fixed in ~~this~~ <code>bora-next</code> branch, release<code>belk-2.2.1-rc1</code>, available on u-boot repository.

|-

~~|Failing mount of root file system on microSD card~~

~~|Some commercial microSD cards occasionally prevent the target from mounting the root file system stored on themselves. microSD cards delivered along with BXELK do not exhibit this problem.~~

|}

==== ~~BXELK~~ BELK 2.1.0.0 ====

~~===== Notes =====~~Updates:~~First stable release with support for SBC Lynx revision A~~ # Fix and ~~Axel ULite~~performance improvement on u-boot network interface# Fix SD card hotplug issue in Linux~~===== Known issues and limitations =====The following table reports the known limitations of this~~ # First [[Advanced_use_of_Yocto_build_system_(BELK/BXELK ~~release:~~)|Yocto Daisy (1.6) BSP Release]]

===== Known Limitations =====

{| class="wikitable"

!Description

|-

|~~Rebooting in Linux may hang~~ETH0 interface|~~Software reboot on Linux may hang~~ Primary Gigabit Ethernet Interface (~~without rebooting the board~~ETH0) ~~when root file system in on SD/MMC~~is not working correctly at 10Mbps

|-

|~~USB OTG Current Limit~~Kernel command line|~~USB OTG current limit is set at 75mA in Host mode~~User should remove '''mem=xxx''' from kernel command line to avoid system hang during boot

|-

|~~Low Power Idle not supported~~Yocto ubi-utils command line|~~Low Power Idle is not supported~~ Some Yocto ubi-utils command line are in ~~this release~~|-~~|BXELK environment fixup for SD boot on SBC Lynx|To boot with~~ non standard format. For ''ubimkvol'' and ''ubirmvol'' the ~~BXELK SD card, user may need to execute~~ UBI device must be the ~~following commands at u~~last argument (e.g. ubimkvol -~~boot prompt <pre>setenv mmcroot~~ m -N belk /dev/~~mmcblk0p2setenv mmc_loadfdt 'fatload mmc 0:1 ${fdtaddr} imx6ul-lynx-som000c.dtb'saveenv</pre>~~ubi0)

|-

|~~Failing mount of root file system on microSD card~~External DDR3 bank (BoraEVB only)|~~Some commercial microSD cards occasionally prevent the target from mounting the root file system stored~~ DDR3 bank can be populated on ~~themselves~~request. For more details please refer to [mailto:sales@dave. ~~microSD cards delivered along with BXELK do not exhibit this problem~~eu Sales Department].

|-

|~~System shutdown mode using the <code>shutdown -h now</code> command prevent the subsequent system's power-up~~ETH1 interface|~~Issuing a system shutdown by the command <code>shutdown -h now</code> as described in [[Supported power mode transitions~~ The additional Gigabit Ethernet interface (~~SBC Lynx~~ETH1)~~]] will prevent the subsequent system's boot~~is not supported in this BELK version.

|-

|~~Missing 7-zip Windows executable in microSD card~~RTC|~~Please download it from http:~~Date/~~/www.7-zip.org~~time retention is limited to about 4 hours.

|-

~~|In the MVM, <code>network-manager</code> applet is not installed by default.~~

~~| Please refer to [[VirtualBox_Network_Configuration#VBox_Bridged_configuration|this page]] to install it.~~

|}

==== ~~BXELK~~ BELK 2.0.9.0 ====~~===== Notes =====First beta release.~~Updates:# Added support for the BoraEVB carrier board# Updated supported drivers list (please refer to [[Bora_Embedded_Linux_Kit_(BELK)#BELK_software_components | BELK_software_components]]) ===== Known ~~issues and limitations~~ Limitations ===== The following table reports the known limitations of this ~~BXELK~~ BELK release:

{| class="wikitable"

!Description

|-

|~~Rebooting in Linux may hang~~External DDR3 bank (BoraEVB only)|~~Software reboot on Linux may hang (without rebooting the board) when root file system in~~ DDR3 bank can be populated on ~~SD/MMC~~request. For more details please refer to [mailto:sales@dave.eu Sales Department].

|-

|~~USB OTG Current Limit~~ETH1 interface|~~USB OTG current limit~~ The additional Gigabit Ethernet interface (ETH1) is ~~set at 75mA~~ not supported in ~~Host mode~~this BELK version.

|-

|-

|}

==== BELK 1.1.0 ====

Updates:

# Switched to Vivado 2013.3

# Added application note "AMP on Bora"

==== BELK 1.0.0 ====

First official release

</div>

U0007

Bureaucrats, dave_user, Administrators

8,221

edits

DAVE Developer's Wiki β

Changes

BELK/BXELK software components

DAVE Developer's Wiki ^β