Difference between revisions of "BELK/BXELK software components"

From DAVE Developer's Wiki
Jump to: navigation, search
 
(102 intermediate revisions by 4 users not shown)
Line 2: Line 2:
 
{{Applies To Bora}}
 
{{Applies To Bora}}
 
{{Applies To BoraX}}
 
{{Applies To BoraX}}
 +
{{Applies To BoraLite}}
 
{{InfoBoxBottom}}
 
{{InfoBoxBottom}}
 +
 +
{{ObsoleteWikiPage|link=BORA_SOM/BELK-L/General/Release_Notes}}
 +
 
__FORCETOC__
 
__FORCETOC__
 
==Introduction==
 
==Introduction==
−
From the software standpoint, BELK and BXELK are built on to of Zynq Linux BSP released by Xilinx. Customization are added to support 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.
+
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==
 
==Kits' composition==
 
The following table details the software modules of BELK/BXELK releases.
 
The following table details the software modules of BELK/BXELK releases.
 
{| class="wikitable"  
 
{| class="wikitable"  
−
!colspan="8" | Kit composition
+
! colspan="12" | Kit composition
 +
!
 
|-
 
|-
 
|'''Release number'''<br>BELK<br>BXELK
 
|'''Release number'''<br>BELK<br>BXELK
Line 19: Line 26:
 
|<br>2.2.0<br>n/a
 
|<br>2.2.0<br>n/a
 
|<br>3.0.0<br>n/a
 
|<br>3.0.0<br>n/a
−
|<br>3.0.1<br>0.9.0
+
|<br>3.0.1<br>1.0.0
 +
|<br>3.0.2<br>1.0.1
 +
|<br>4.0.0<br>2.0.0
 +
|<br>4.1.0<br>4.1.0
 +
|<br>4.1.2<br>4.1.2
 +
|<br>4.1.4<br>4.1.4
 
|-
 
|-
 
|'''Status'''<br>BELK<br>BXELK
 
|'''Status'''<br>BELK<br>BXELK
Line 28: Line 40:
 
|<br>Released<br>n/a
 
|<br>Released<br>n/a
 
|<br>Released<br>n/a
 
|<br>Released<br>n/a
−
|<br>Released<br>Beta
+
|<br>Released<br>Released
 +
|<br>Released<br>Released
 +
|<br>Released<br>Released
 +
|<br>Released<br>Released
 +
|<br>Released<br>Released
 +
|<br>Released<br>Released
 
|-
 
|-
 
|'''Release date'''<br>BELK<br>BXELK
 
|'''Release date'''<br>BELK<br>BXELK
Line 38: Line 55:
 
|<br>March 2016<br>n/a
 
|<br>March 2016<br>n/a
 
|<br>December 2016<br>December 2016
 
|<br>December 2016<br>December 2016
 +
|<br>January 2017<br>January 2017
 +
|<br>July 2017<br>July 2017
 +
|<br>Jan 2020<br>Jan 2020
 +
|<br>Sep 2020<br>Sep 2020
 +
|<br>Jul 2021<br>Jul 2021
 
|-
 
|-
 
|'''Release notes'''<br>BELK<br>BXELK
 
|'''Release notes'''<br>BELK<br>BXELK
 
|<br>[[#BELK 1.0.0 | Ver 1.0.0]]
 
|<br>[[#BELK 1.0.0 | Ver 1.0.0]]
−
|<br>[[BELK 1.1.0 | Ver 1.1.0]]
+
|<br>[[#BELK 1.1.0 | Ver 1.1.0]]
 
|<br>[[#BELK 2.0.0 | Ver 2.0.0]]
 
|<br>[[#BELK 2.0.0 | Ver 2.0.0]]
 
|<br>[[#BELK 2.1.0 | Ver 2.1.0]]
 
|<br>[[#BELK 2.1.0 | Ver 2.1.0]]
 
|<br>[[#BELK 2.2.0 | Ver 2.2.0]]
 
|<br>[[#BELK 2.2.0 | Ver 2.2.0]]
 
|<br>[[#BELK 3.0.0 | Ver 3.0.0]]
 
|<br>[[#BELK 3.0.0 | Ver 3.0.0]]
−
|<br>
+
|<br>[[#BELK_3.0.1_.2F_BXELK_1.0.0 | Ver 3.0.1]]
 +
|<br>[[#BELK_3.0.2_.2F_BXELK_1.0.1 | Ver 3.0.2]]
 +
|<br>[[#BELK_4.0.0_.2F_BXELK_2.0.0 | Ver 4.0.0]]
 +
|<br>[[#BELK_4.1.0 | Ver 4.1.0]]
 +
|<br> [[BELK/BXELK software components#BELK 4.1.2|Ver 4.1.2]]
 +
|<br> [[BELK/BXELK software components#BELK 4.1.4|Ver 4.1.4]]
 
|-
 
|-
−
|'''SOM PCB version'''<br>BELK<br>BXELK
+
|'''SOM PCB version'''<br>BELK<br><br>BXELK
−
|<br>CS020313A<br>n/a
+
|<br>CS020313A<br><br>n/a
−
|<br>CS020313A<br>n/a
+
|<br>CS020313A<br><br>n/a
−
|<br>CS020313B<br>n/a
+
|<br>CS020313B<br><br>n/a
−
|<br>CS020313B<br>n/a
+
|<br>CS020313B<br><br>n/a
−
|<br>CS020313B<br>n/a
+
|<br>CS020313B<br><br>n/a
−
|<br>CS020313C<br>n/a
+
|<br>CS020313B/CS020313C<br><br>n/a
−
|<br>CS020313C<br>CS112714B
+
|<br>CS020313B/CS020313C<br><br>CS112714B
 +
|<br>CS020313B/CS020313C<br><br>CS112714B
 +
|<br>CS020313B/CS020313C<br><br>CS112714B
 +
|<br>CS020313B/CS020313C/CS061919<br><br>CS112714B
 +
|<br>CS020313B/CS020313C/CS061919<br><br>CS112714B
 +
|<br>CS020313B/CS020313C/CS061919<br><br>CS112714B
 
|--
 
|--
 
|'''Supported carrier boards'''<br>BELK<br>BXELK
 
|'''Supported carrier boards'''<br>BELK<br>BXELK
Line 64: Line 96:
 
|<br>[[BoraEVB]]<br>n/a
 
|<br>[[BoraEVB]]<br>n/a
 
|<br>[[BoraEVB]]<br>n/a
 
|<br>[[BoraEVB]]<br>n/a
 +
|<br>[[BoraEVB]]<br>[[BoraXEVB]]
 +
|<br>[[BoraEVB]]<br>[[BoraXEVB]]
 +
|<br>[[BoraEVB]]<br>[[BoraXEVB]]
 +
|<br>[[BoraEVB]]<br>[[BoraXEVB]]
 +
|<br>[[BoraEVB]]<br>[[BoraXEVB]]
 
|<br>[[BoraEVB]]<br>[[BoraXEVB]]
 
|<br>[[BoraEVB]]<br>[[BoraXEVB]]
 
|-
 
|-
Line 73: Line 110:
 
|2014.07-belk-2.2.0  
 
|2014.07-belk-2.2.0  
 
|2014.07-belk-3.0.0
 
|2014.07-belk-3.0.0
−
|TBD
+
|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'''
 
|'''Linux version'''
Line 82: Line 124:
 
|3.17.0-bora-2.2.0
 
|3.17.0-bora-2.2.0
 
|3.17.0-bora-3.0.0
 
|3.17.0-bora-3.0.0
−
|TBD
+
|3.17.0-bora-3.0.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
 +
|4.9.0-bora-4.1.4
 
|-  
 
|-  
 
|'''Drivers'''
 
|'''Drivers'''
−
|valign="top" | -
+
| valign="top" | -
−
|valign="top" | -
+
| valign="top" | -
−
|valign="top" | Gigabit Eth #0<br>UART<br>NOR<br>NAND<br>SD/MMC<br>USB Host/Device<br>RTC<br>CAN<br>I2C
+
| valign="top" | Gigabit Eth #0<br>UART<br>NOR<br>NAND<br>SD/MMC<br>USB Host/Device<br>RTC<br>CAN<br>I2C
−
|valign="top" | Gigabit Eth #0<br>UART<br>NOR<br>NAND<br>SD/MMC<br>USB Host/Device<br>RTC<br>CAN<br>I2C
+
| valign="top" | Gigabit Eth #0<br>UART<br>NOR<br>NAND<br>SD/MMC<br>USB Host/Device<br>RTC<br>CAN<br>I2C
−
|valign="top" | Gigabit Eth #0<br>UART<br>NOR<br>NAND<br>SD/MMC<br>USB Host/Device<br>RTC<br>CAN<br>I2C<br>[[ConfigID_and_UniqueID | ConfigID]]
+
| valign="top" | Gigabit Eth #0<br>UART<br>NOR<br>NAND<br>SD/MMC<br>USB Host/Device<br>RTC<br>CAN<br>I2C<br>[[ConfigID_and_UniqueID | ConfigID]]
−
|valign="top" | Gigabit Eth #0<br>UART<br>NOR<br>NAND<br>SD/MMC<br>USB Host/Device<br>RTC<br>CAN<br>I2C<br>[[ConfigID_and_UniqueID | ConfigID]]
+
| valign="top" | Gigabit Eth #0<br>UART<br>NOR<br>NAND<br>SD/MMC<br>USB Host/Device<br>RTC<br>CAN<br>I2C<br>[[ConfigID_and_UniqueID | ConfigID]]
−
|TBD
+
| valign="top" | Gigabit Eth #0<br>UART<br>NOR<br>NAND<br>SD/MMC<br>USB Host/Device<br>RTC<br>CAN<br>I2C<br>[[ConfigID_and_UniqueID | ConfigID]]
 +
| valign="top" | Gigabit Eth #0<br>UART<br>NOR<br>NAND<br>SD/MMC<br>USB Host/Device<br>RTC<br>CAN<br>I2C<br>[[ConfigID_and_UniqueID | ConfigID]]
 +
| valign="top" | Gigabit Eth #0<br>UART<br>NOR<br>NAND<br>SD/MMC<br>USB Host/Device<br>RTC<br>CAN<br>I2C<br>[[ConfigID_and_UniqueID | ConfigID]]
 +
| valign="top" | Gigabit Eth #0<br>UART<br>NOR<br>NAND<br>SD/MMC<br>USB Host/Device<br>RTC<br>CAN<br>I2C<br>[[ConfigID_and_UniqueID | ConfigID]]
 +
| valign="top" | Gigabit Eth #0<br>UART<br>NOR<br>NAND<br>SD/MMC<br>USB Host/Device<br>RTC<br>CAN<br>I2C<br>[[ConfigID_and_UniqueID | ConfigID]]
 +
| valign="top" | Gigabit Eth #0<br>UART<br>NOR<br>NAND<br>SD/MMC<br>USB Host/Device<br>RTC<br>CAN<br>I2C<br>[[ConfigID_and_UniqueID | ConfigID]]
 
|-
 
|-
 
|'''Vivado version'''
 
|'''Vivado version'''
−
|valign="top" | 2013.2
+
| valign="top" | 2013.2
−
|valign="top" | 2013.3
+
| valign="top" | 2013.3
−
|valign="top" | 2013.3
+
| 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" | 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
 
|-
 
|-
 
|'''Build System'''
 
|'''Build System'''
−
|valign="top" | -
+
| valign="top" | -
−
|valign="top" | -
+
| valign="top" | -
−
|valign="top" | -
+
| valign="top" | -
−
|valign="top" | Yocto Daisy (1.6)
+
| valign="top" | Yocto Daisy (1.6)
−
|valign="top" | Yocto Daisy (1.6)  
+
| valign="top" | Yocto Daisy (1.6)
−
|valign="top" | Yocto Daisy (1.6)  
+
| valign="top" | Yocto Daisy (1.6)
−
|valign="top" | Yocto Daisy (1.6)  
+
| valign="top" | Yocto Daisy (1.6)
 +
| valign="top" | Yocto Daisy (1.6)
 +
| valign="top" | Yocto Morty (2.2)
 +
| valign="top" | Yocto Morty (2.2)
 +
| valign="top" | Yocto Morty (2.2)
 +
| valign="top" | Yocto Morty (2.2)
 
|-
 
|-
 +
|'''[[Managed Virtual Machine (MVM)]]'''
 +
|N/A
 +
|N/A
 +
|N/A
 +
|N/A
 +
|N/A
 +
|N/A
 +
|N/A
 +
|N/A
 +
|belk-4.0.0 (based on Ubuntu 14.04 64 bit)
 +
|belk-4.1.0 (based on Ubuntu 14.04 64 bit)
 +
|belk-4.1.0 (based on Ubuntu 14.04 64 bit)
 +
|belk-4.1.0 (based on Ubuntu 14.04 64 bit)
 
|}
 
|}
  
 
== Downloadable binary images==
 
== Downloadable binary images==
−
TBD
 
  
−
==microSD layout==
 
−
TBD
 
  
−
==Updates==
 
−
TBD
 
−
{{ImportantMessage|text=It's recommended to use the latest available BELK version. Please refer to [[Bora_Embedded_Linux_Kit_(BELK)#Release_notes | Release notes]] for further information.}}
 
  
−
=== Updating git repositories ===
+
All binary images for BELK/BXELK are hosted on [[mirror:bora|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 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 <= 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 BELK, the following source trees are clones of '''DAVE Embedded Systems''' public git repositories:
+
{| class="wikitable"
 +
|-
 +
! rowspan="2" |Image !! colspan="1" |BELK 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)<br>(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)<br>(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"  
+
{| 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
+
| 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]]
−
!GIT Remote
 
 
|-
 
|-
−
|Vivado project
+
| Boot header || [[mirror:bora/belk-3.0.1/boot_header-1.0.1|boot-header]] || [[mirror:bora/bxelk-1.0.0/boot_header-1.0.1|boot-header]]
−
|git@git.dave.eu:dave/bora/bora.git
 
 
|-
 
|-
−
|Linux
+
| Linux kernel || [[mirror:bora/belk-3.0.1/belk-3.0.0_uImage|uImage]] || [[mirror:bora/bxelk-1.0.0/belk-3.0.0_uImage|uImage]]
−
|git@git.dave.eu:dave/bora/linux-xlnx.git
 
 
|-
 
|-
−
|U-Boot
+
| Device tree || [[mirror:bora/belk-3.0.1/belk-3.0.0_bora.dtb|bora.dtb]] || [[mirror:bora/bxelk-1.0.0/belk-3.0.0_bora.dtb|bora.dtb]]
−
|git@git.dave.eu:dave/bora/u-boot-xlnx.git
 
 
|-
 
|-
 +
|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 in sync and up to date with '''DAVE Embedded Systems''' repositories.
+
<section begin=microSDlayout/>
 +
===microSD layout===
 +
The microSD card provided with BELK/BXELK is partitioned as shown in 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: <br><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:
 
  
−
<pre>
+
Most of storage space is occupied by two partitions:
−
Host git.dave.eu
+
*a <code>FAT32</code> partition (<code>mmcblk0p1</code>) containing:
−
    User git
+
** For '''BELK <= 3.0.2''' and '''BXELK <= 1.0.1''' :
−
    Hostname git.dave.eu
+
***<code>boot.bin</code> boot image (containing FSBL, FPGA Bitstream an U-boot binaries)
−
    PreferredAuthentications publickey
+
***U-Boot <code>boot.scr</code> bootscript
−
    IdentityFile ~/.ssh/username@myhost.com
+
***Linux kernel and DTB binary images
−
</pre>
+
** For '''BELK 4.0.0''' or newer and '''BXELK 2.0.0''' or newer:
 +
***<code>boot.bin</code> u-boot SPL image
 +
***<code>fpga.bit</code> optional [[BELK-AN-008:_Programming_the_FPGA_Bitstream_with_U-Boot|FPGA bitstream]]
 +
***<code>u-boot.img</code> u-boot image
 +
***U-Boot <code>boot.scr</code> bootscript
 +
***Linux kernel and DTB binary images
 +
*** MVM image in OVA format
 +
*an <code>ext3</code> partition (<code>mmcblk0p2</code>) containing the root file system for the target.
 +
 
 +
bootscript and root file system are used to boot the 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 [[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.env</code>
 +
<section end=microSDlayout/>
  
−
Please send the public key file to the following email support addresses:
+
==Updates==
 +
{{ImportantMessage|text=It's recommended to use the latest source release available. Please refer to [[#Release_notes | Release notes]] for further information.}}
  
−
* [mailto:support-bora@dave.eu support-bora@dave.eu]
+
<section begin="Synchronizing" the="" git="" repositories="" />
 +
<section begin=Synchronizingthegitrepositories/>
  
−
with the request 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.
+
=== 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 ===
 
=== Updating the repositories from BELK 2.1.0 ===
Line 184: Line 356:
  
 
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].
 
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 end=Synchronizingthegitrepositories/>
  
 +
<section begin=Releasenotes/>
 
== Release notes ==
 
== Release notes ==
  
−
=== BELK 3.0.0 ===
+
=== BELK 4.1.4 ===
  
 
Updates:
 
Updates:
−
# Added support for BORA Xpress SOM
+
# Fixes for MAC programming on [[BELK-TN-010: MAC address programming on OTP|NOR SPI OTP]]
−
# Updated U-Boot and Linux versions
 
  
 
==== Known Limitations ====
 
==== Known Limitations ====
Line 197: Line 370:
 
{| class="wikitable"  
 
{| class="wikitable"  
 
|-
 
|-
−
!Issue
+
!ID
 +
!Component
 +
!Subsystem
 
!Description
 
!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)
−
|External DDR3 bank  
+
|DDR3 bank can be populated on request. For more details please refer to [mailto:sales@dave.eu Sales Department].
−
|The DDR3 SDRAM bank on the BoraEVB is not supported in this BELK version.
 
 
|-
 
|-
 +
|0002
 +
|BoraEVB/BoraXEVB
 
|ETH1 interface
 
|ETH1 interface
−
|The additional Gigabit Ethernet interface (ETH1) is not supported in this BELK version.
+
|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
 
|RTC
 
|Date/time retention is limited to about 4 hours.
 
|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 2.2.0 ===
+
=== BELK 4.1.2 ===
  
 
Updates:
 
Updates:
−
# Switched to Vivado 2014.4
+
# Added support for MAC programming on [[BELK-TN-010: MAC address programming on OTP|NOR SPI OTP]]
−
# 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
 
  
 
==== Known Limitations ====
 
==== Known Limitations ====
Line 226: Line 405:
 
{| class="wikitable"  
 
{| class="wikitable"  
 
|-
 
|-
−
!Issue
+
!ID
 +
!Component
 +
!Subsystem
 
!Description
 
!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
+
|BoraEVB
−
|-
+
|External DDR3 bank (BoraEVB only)
−
| Yocto ubi-utils command line
+
|DDR3 bank can be populated on request. For more details please refer to [mailto:sales@dave.eu Sales Department].
−
| 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)
 
−
|-
 
−
|External DDR3 bank  
 
−
|The DDR3 SDRAM bank on the BoraEVB is not supported in this BELK version.
 
 
|-
 
|-
 +
|0002
 +
|BoraEVB/BoraXEVB
 
|ETH1 interface
 
|ETH1 interface
−
|The additional Gigabit Ethernet interface (ETH1) is not supported in this BELK version.
+
|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
 
|RTC
 
|Date/time retention is limited to about 4 hours.
 
|Date/time retention is limited to about 4 hours.
 
|-
 
|-
−
|u-boot default environment
+
|0004
−
|Default u-boot environment has a syntax error on ''sdboot'' command. This is already fixed in <code>bora-next</code> branch, release <code>belk-2.2.1-rc1</code>, available on u-boot repository.
+
|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
 
|-
 
|-
 +
|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 2.1.0 ===
+
=== BELK 4.1.0 ===
  
 
Updates:
 
Updates:
−
# Fix and performance improvement on u-boot network interface
+
# Added support for [https://www.dave.eu/products/som/xilinx/zynq-XC7Z010-XC7Z020_boralite BoraLite SOM]
−
# Fix SD card hotplug issue in Linux
 
−
# First [[Building_the_software_components_via_Yocto_(BELK)|Yocto Daisy (1.6) BSP Release]]
 
  
 
==== Known Limitations ====
 
==== Known Limitations ====
Line 260: Line 447:
 
{| class="wikitable"  
 
{| class="wikitable"  
 
|-
 
|-
−
!Issue
+
!ID
 +
!Component
 +
!Subsystem
 
!Description
 
!Description
 
|-
 
|-
−
| ETH0 interface
+
|0001
−
| Primary Gigabit Ethernet Interface (ETH0) is not working correctly at 10Mbps<br>
+
|BoraEVB
−
|-
+
|External DDR3 bank (BoraEVB only)
−
| Kernel command line
+
|DDR3 bank can be populated on request. For more details please refer to [mailto:sales@dave.eu Sales Department].
−
| 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)
 
−
|-
 
−
|External DDR3 bank  
 
−
|The DDR3 SDRAM bank on the BoraEVB is not supported in this BELK version.
 
 
|-
 
|-
 +
|0002
 +
|BoraEVB/BoraXEVB
 
|ETH1 interface
 
|ETH1 interface
−
|The additional Gigabit Ethernet interface (ETH1) is not supported in this BELK version.
+
|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
 
|RTC
 
|Date/time retention is limited to about 4 hours.
 
|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 2.0.0 ===
+
=== BELK 4.0.0 / BXELK 2.0.0 ===
  
 
Updates:
 
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]])
+
# Updated U-Boot and Linux versions
  
 
==== Known Limitations ====
 
==== Known Limitations ====
−
 
−
The following table reports the known limitations of this BELK release:
 
  
 
{| class="wikitable"  
 
{| class="wikitable"  
 
|-
 
|-
−
!Issue
+
!ID
 +
!Component
 +
!Subsystem
 
!Description
 
!Description
 
|-
 
|-
−
|External DDR3 bank  
+
|0001
−
|The DDR3 SDRAM bank on the BoraEVB is not supported in this BELK version.
+
|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
 
|ETH1 interface
−
|The additional Gigabit Ethernet interface (ETH1) is not supported in this BELK version.
+
|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
 
|RTC
 
|Date/time retention is limited to about 4 hours.
 
|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.<br />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 1.1.0 ===
+
=== BELK 3.0.2 / BXELK 1.0.1 ===
  
 
Updates:
 
Updates:
−
# Switched to Vivado 2013.3
+
# Fix BELK-3.0.1/BXELK-1.0.0 software issues
−
# Added application note "AMP on Bora"
+
# Use standard DAVE recovery scripts for u-boot
−
 
 
−
=== BELK 1.0.0 ===
 
−
 
 
−
First official release
 
−
 
 
  
 +
(BoraXEVB only) For LCD interfacing, please refer to [[AN-BELK-004:_Interfacing_BoraEVB/BoraXEVB_to_TFT_LCD_display|this application note]].
  
 +
==== 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)
  
−
roba presa da XUELK
+
<div class="mw-collapsible mw-collapsed">
  
 +
==== BELK 3.0.1 / BXELK 1.0.0 ====
  
 +
Updates: added support for BoraX/BoraXEVB evaluation system
  
−
== BXELK software components ==
+
(BoraXEVB only) For LCD interfacing, please refer to [[AN-BELK-004:_Interfacing_BoraEVB/BoraXEVB_to_TFT_LCD_display|this application note]].
−
{{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.
+
===== Known Limitations =====
  
−
The following table reports the BXELK releases information.
 
 
{| class="wikitable"  
 
{| class="wikitable"  
−
!
 
−
!colspan="3" | BXELK version
 
 
|-
 
|-
−
|Release number
+
!Issue
−
|0.9.0
+
!Description
−
|1.0.0
 
−
|1.1.0
 
 
|-
 
|-
−
|Release type
+
| <code>canutils</code> package is missing is default root file system
−
|Major
+
| It can be downloaded directly from our package repository as described [[Physical devices mapping (BELK/BXELK)#CAN|here]]
−
|Major
 
−
|Minor
 
 
|-
 
|-
−
|Status
+
|External DDR3 bank (BoraEVB only)
−
|Beta
+
|DDR3 bank can be populated on request. For more details please refer to [mailto:sales@dave.eu Sales Department].
−
|Released
 
−
|Released
 
 
|-
 
|-
−
|Release date
+
|ETH1 interface
−
|March 2016
+
|Please refer to [[AN-BELK-006:_Enabling_dual_Gigabit_Ethernet_support_on_BoraEVB/BoraXEVB|this application note]] for second Ethernet interface support.
−
|August 2016
 
−
|November 2016
 
 
|-
 
|-
−
|Release notes
+
|RTC
−
|[[#BXELK 0.9.0|0.9.0]]
+
|Date/time retention is limited to about 4 hours.
−
|[[#BXELK 1.0.0|1.0.0]]
 
−
|[[#BXELK 1.1.0|1.1.0]]
 
−
|-
 
−
|PCB version
 
−
|SBC Lynx CS214515
 
−
|SBC Lynx CS214515A<br>
 
−
(AXELULite CS184015) [1]
 
−
|SBC Lynx CS214515A<br>
 
−
(AXELULite CS184015) [1]
 
−
|-
 
−
|[[ConfigID_and_UniqueID|ConfigIDs]] (core/interfaces)
 
−
|0x00000008/0x0000000E
 
−
|0x00000008/0x0000000E<br>
 
−
0x0000000C/NA<br>
 
−
(0x0000000B/NA) [1]
 
−
|0x00000008/0x0000000E<br>
 
−
0x0000000C/NA<br>
 
−
(0x0000000B/NA) [1]
 
−
|-
 
−
|[[Managed_Virtual_Machine_(MVM)|MVM]] version
 
−
|xuelk-0.9.0, tested with:<br/>
 
−
Virtual Box 5.0.14<br/>
 
−
Vagrant 1.8.1
 
−
|xuelk-1.0.0, tested with:<br/>
 
−
Virtual Box 5.0.26<br/>
 
−
Vagrant 1.8.1
 
−
|xuelk-1.1.0, tested with:<br/>
 
−
Virtual Box 5.1.10<br/>
 
−
Vagrant 1.8.7
 
−
|-
 
−
|U-Boot version/release
 
−
|U-Boot 2015.04/xuelk-0.9.0
 
−
|U-Boot 2015.04/xuelk-1.0.0
 
−
|U-Boot 2015.04/xuelk-1.1.0
 
−
|-
 
−
|Linux version/release
 
−
|Linux 3.14.52/xuelk-0.9.0
 
−
|Linux 3.14.52/xuelk-1.0.0
 
−
|Linux 3.14.52/xuelk-1.1.0
 
−
|-
 
−
|Drivers
 
−
|valign="top"|UART<br/>
 
−
Ethernet<br/>
 
−
SD/MMC<br/>
 
−
USB Host<br/>
 
−
USB Device<br/>
 
−
NOR Flash<br/>
 
−
NAND Flash<br/>
 
−
ADC<br/>
 
−
RTC<br/>
 
−
|valign="top"|UART<br/>
 
−
Ethernet<br/>
 
−
SD/MMC<br/>
 
−
USB Host<br/>
 
−
USB Device<br/>
 
−
NOR Flash<br/>
 
−
NAND Flash<br/>
 
−
ADC<br/>
 
−
RTC<br/>
 
−
CAN<br/>
 
−
DWM<br/>
 
−
LCD<br/>
 
−
|valign="top"|UART<br/>
 
−
Ethernet<br/>
 
−
SD/MMC<br/>
 
−
USB Host<br/>
 
−
USB Device<br/>
 
−
NOR Flash<br/>
 
−
NAND Flash<br/>
 
−
ADC<br/>
 
−
RTC<br/>
 
−
CAN<br/>
 
−
DWM<br/>
 
−
LCD<br/>
 
−
|-
 
−
|NXP BSP version
 
−
|3.14.52_1.1.0_ga
 
−
|3.14.52_1.1.0_ga
 
−
|3.14.52_1.1.0_ga
 
 
|-
 
|-
−
|Build System
+
|Boot for NOR flash
−
|Yocto Fido (1.8)
+
|U-Boot is not configured properly to support NOR boot. Please use boot from microSD card instead.
−
|Yocto Fido (1.8)
 
−
|Yocto Fido (1.8)
 
 
|-
 
|-
 
|}
 
|}
  
 +
==== BELK 3.0.0 ====
  
 +
Updates:
 +
# Added preliminary support for BORA Xpress SOM
 +
# Updated U-Boot and Linux versions
  
−
[1] Not included in the kit.
+
(BoraXEVB only) For LCD interfacing, please refer to [[AN-BELK-004:_Interfacing_BoraEVB/BoraXEVB_to_TFT_LCD_display|this application note]].
−
====Downloadable binary images====
+
===== Known Limitations =====
  
−
 
+
{| class="wikitable"  
−
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 !! colspan=2|BXELK version
+
!Issue
 +
!Description
 
|-
 
|-
−
| 1.0.0 || 1.1.0
+
| 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)
 
|-
 
|-
−
| bootscript || [[mirror:lynx/xuelk-1.0.0/xuelk-1.0.0_boot.scr|boot.scr]] || [[mirror:lynx/xuelk-1.1.0/xuelk-1.1.0_boot.scr|boot.scr]]
+
|External DDR3 bank (BoraEVB only)
 +
|DDR3 bank can be populated on request. For more details please refer to [mailto:sales@dave.eu Sales Department].
 
|-
 
|-
−
| U-Boot || [[mirror:lynx/xuelk-1.0.0/xuelk-1.0.0_mx6ul_lynx_u-boot.imx|u-boot.imx]] || [[mirror:lynx/xuelk-1.1.0/xuelk-1.1.0_mx6ul_lynx_u-boot.imx|u-boot.imx]]
+
|ETH1 interface
 +
|Please refer to [[AN-BELK-006:_Enabling_dual_Gigabit_Ethernet_support_on_BoraEVB/BoraXEVB|this application note]] for second Ethernet interface support.
 
|-
 
|-
−
| Linux kernel || [[mirror:lynx/xuelk-1.0.0/xuelk-1.0.0_uImage|uImage]] || [[mirror:lynx/xuelk-1.1.0/xuelk-1.1.0_uImage|uImage]]
+
|RTC
 +
|Date/time retention is limited to about 4 hours.
 
|-
 
|-
−
| 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]]
+
===== Known Limitations =====
−
 
 
−
 
 
−
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 =====
 
−
 
 
−
The following table reports the known limitations of this BXELK release:
 
−
 
 
  
 
{| class="wikitable"  
 
{| class="wikitable"  
Line 523: Line 649:
 
!Description
 
!Description
 
|-
 
|-
−
|Rebooting in Linux may hang
+
| Kernel command line
−
|Software reboot on Linux may hang (without rebooting the board) when root file system in on SD/MMC
+
| 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)
 
|-
 
|-
−
|USB OTG Current Limit
+
|External DDR3 bank (BoraEVB only)
−
|USB OTG current limit is set at 75mA in Host mode
+
|DDR3 bank can be populated on request. For more details please refer to [mailto:sales@dave.eu Sales Department].
 
|-
 
|-
−
|Low Power Idle not supported
+
|ETH1 interface
−
|Low Power Idle is not supported in this release
+
|Please refer to [[AN-BELK-006:_Enabling_dual_Gigabit_Ethernet_support_on_BoraEVB/BoraXEVB|this application note]] for second Ethernet interface support.
 +
|-
 +
|RTC
 +
|Date/time retention is 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 <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 1.0.0 ====
+
==== BELK 2.1.0 ====
  
−
===== Notes =====
+
Updates:
−
 
+
# Fix and performance improvement on u-boot network interface
−
First stable release with support for SBC Lynx revision A and Axel ULite
+
# Fix SD card hotplug issue in Linux
−
 
+
# First [[Advanced_use_of_Yocto_build_system_(BELK/BXELK)|Yocto Daisy (1.6) BSP Release]]
−
===== Known issues and limitations =====
 
−
The following table reports the known limitations of this BXELK release:
 
  
 +
===== Known Limitations =====
  
 
{| class="wikitable"  
 
{| class="wikitable"  
Line 551: Line 683:
 
!Description
 
!Description
 
|-
 
|-
−
|Rebooting in Linux may hang
+
| ETH0 interface
−
|Software reboot on Linux may hang (without rebooting the board) when root file system in on SD/MMC
+
| Primary Gigabit Ethernet Interface (ETH0) is not working correctly at 10Mbps<br>
 
|-
 
|-
−
|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 in this release
+
| 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)
 
|-
 
|-
−
|BXELK environment fixup for SD boot<br/>on SBC Lynx
+
|External DDR3 bank (BoraEVB only)
−
|To boot with the BXELK SD card, user may need to execute the following commands at u-boot prompt<br/>
+
|DDR3 bank can be populated on request. For more details please refer to [mailto:sales@dave.eu Sales Department].
−
<pre>
 
−
setenv mmcroot /dev/mmcblk0p2
 
−
setenv mmc_loadfdt 'fatload mmc 0:1 ${fdtaddr} imx6ul-lynx-som000c.dtb'
 
−
saveenv
 
−
</pre>
 
 
|-
 
|-
−
|Failing mount of root file system on microSD card
+
|ETH1 interface
−
|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.
+
|The additional Gigabit Ethernet interface (ETH1) is not supported in this BELK version.
 
|-
 
|-
−
|System shutdown mode using the <code>shutdown -h now</code> command prevent the subsequent system's power-up
+
|RTC
−
|Issuing a system shutdown by the command <code>shutdown -h now</code> as described in [[Supported power mode transitions (SBC Lynx)]] will prevent the subsequent system's boot.
+
|Date/time retention is limited to about 4 hours.
−
|-
 
−
|Missing 7-zip Windows executable in microSD card
 
−
|Please download it from http://www.7-zip.org.  
 
 
|-
 
|-
−
|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 0.9.0 ====
+
==== BELK 2.0.0 ====
−
===== Notes =====
+
 
−
First beta release.
+
Updates:
−
===== Known issues and limitations =====
+
# Added support for the BoraEVB carrier board
−
The following table reports the known limitations of this BXELK release:
+
# Updated supported drivers list (please refer to [[Bora_Embedded_Linux_Kit_(BELK)#BELK_software_components | BELK_software_components]])
 +
 
 +
===== Known Limitations =====
 +
 
 +
The following table reports the known limitations of this BELK release:
  
 
{| class="wikitable"  
 
{| class="wikitable"  
Line 592: Line 718:
 
!Description
 
!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 on SD/MMC
+
|DDR3 bank can be populated on request. For more details please refer to [mailto:sales@dave.eu Sales Department].
 
|-
 
|-
−
|USB OTG Current Limit
+
|ETH1 interface
−
|USB OTG current limit is set at 75mA in Host mode
+
|The additional Gigabit Ethernet interface (ETH1) is not supported in this BELK version.
 
|-
 
|-
−
|LDO Mode not supported
+
|RTC
−
|LDO Mode is not supported in this SW release
+
|Date/time retention is limited to about 4 hours.
−
|-
 
−
|Low Power Idle not supported
 
−
|Low Power Idle is not supported in this release
 
−
|-
 
−
|DDR3 Frequency limited at 306 MHz
 
−
|The DDR3 RAM frequency is limited at 306 MHz in this release
 
 
|-
 
|-
 
|}
 
|}
 +
 +
==== BELK 1.1.0 ====
 +
 +
Updates:
 +
# Switched to Vivado 2013.3
 +
# Added application note "AMP on Bora"
 +
 +
==== BELK 1.0.0 ====
 +
 +
First official release
 +
 +
</div>
 +
 +
<section end=Releasenotes/>

Latest revision as of 09:27, 18 October 2022

HOME SOMs SBCs ToloMEO Embedded Assistant Sale-tag.pngGET A QUOTE Customer-service.pngONLINE HELPDESK
Roadmap IoT Services ML/AI services Embedded Design Services
Info Box
Bora5-small.jpg Applies to Bora
BORA Xpress.png Applies to BORA Xpress
BORALite-TOP.png Applies to BORA Lite


Attention.png THIS PAGE IS OBSOLETE, DON'T USE IT AS REFERENCE
The new documentation is available here: BORA_SOM/BELK-L/General/Release_Notes


Introduction[edit | edit source]

From the software standpoint, Bora Embedded Linux Kit (BELK) and 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 this document is strongly recommended to understand the logical structure of the kits and how the software components are related.

Kits' composition[edit | edit source]

The following table details the software modules of BELK/BXELK releases.

Kit composition
Release number
BELK
BXELK
1.0.0
n/a
1.1.0
n/a
2.0.0
n/a
2.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.1.0
4.1.0
4.1.2
4.1.2
4.1.4
4.1.4
Status
BELK
BXELK
Released
n/a
Released
n/a
Released
n/a
Released
n/a
Released
n/a
Released
n/a
Released
Released
Released
Released
Released
Released
Released
Released
Released
Released
Released
Released
Release date
BELK
BXELK
July 2013
n/a
November 2013
n/a
May 2014
n/a
August 2014
n/a
September 2015
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
Ver 1.0.0
Ver 1.1.0
Ver 2.0.0
Ver 2.1.0
Ver 2.2.0
Ver 3.0.0
Ver 3.0.1
Ver 3.0.2
Ver 4.0.0
Ver 4.1.0
Ver 4.1.2
Ver 4.1.4
SOM PCB version
BELK

BXELK
CS020313A

n/a
CS020313A

n/a
CS020313B

n/a
CS020313B

n/a
CS020313B

n/a
CS020313B/CS020313C

n/a
CS020313B/CS020313C

CS112714B
CS020313B/CS020313C

CS112714B
CS020313B/CS020313C

CS112714B
CS020313B/CS020313C/CS061919

CS112714B
CS020313B/CS020313C/CS061919

CS112714B
CS020313B/CS020313C/CS061919

CS112714B
Supported carrier boards
BELK
BXELK
BoraEVB-Lite
n/a
BoraEVB-Lite
n/a
BoraEVB
n/a
BoraEVB
n/a
BoraEVB
n/a
BoraEVB
n/a
BoraEVB
BoraXEVB
BoraEVB
BoraXEVB
BoraEVB
BoraXEVB
BoraEVB
BoraXEVB
BoraEVB
BoraXEVB
BoraEVB
BoraXEVB
U-Boot version 2013.04-belk-1.0.0 2013.04-belk-1.1.0 2013.04-belk-2.0.0 2013.04-belk-2.1.0 2014.07-belk-2.2.0 2014.07-belk-3.0.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.9.0-bora-2.0.0 3.9.0-bora-2.1.0 3.17.0-bora-2.2.0 3.17.0-bora-3.0.0 3.17.0-bora-3.0.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 4.9.0-bora-4.1.4
Drivers - - Gigabit Eth #0
UART
NOR
NAND
SD/MMC
USB Host/Device
RTC
CAN
I2C 		Gigabit Eth #0
UART
NOR
NAND
SD/MMC
USB Host/Device
RTC
CAN
I2C 		Gigabit Eth #0
UART
NOR
NAND
SD/MMC
USB Host/Device
RTC
CAN
I2C
ConfigID 		Gigabit Eth #0
UART
NOR
NAND
SD/MMC
USB Host/Device
RTC
CAN
I2C
ConfigID 		Gigabit Eth #0
UART
NOR
NAND
SD/MMC
USB Host/Device
RTC
CAN
I2C
ConfigID 		Gigabit Eth #0
UART
NOR
NAND
SD/MMC
USB Host/Device
RTC
CAN
I2C
ConfigID 		Gigabit Eth #0
UART
NOR
NAND
SD/MMC
USB Host/Device
RTC
CAN
I2C
ConfigID 		Gigabit Eth #0
UART
NOR
NAND
SD/MMC
USB Host/Device
RTC
CAN
I2C
ConfigID 		Gigabit Eth #0
UART
NOR
NAND
SD/MMC
USB Host/Device
RTC
CAN
I2C
ConfigID 		Gigabit Eth #0
UART
NOR
NAND
SD/MMC
USB Host/Device
RTC
CAN
I2C
ConfigID
Vivado version 2013.2 2013.3 2013.3 2013.3 2014.4 2014.4 2014.4 2014.4 2017.1 2017.1 2017.1 2017.1
Build System - - - Yocto Daisy (1.6) Yocto Daisy (1.6) Yocto Daisy (1.6) Yocto Daisy (1.6) Yocto Daisy (1.6) Yocto Morty (2.2) Yocto Morty (2.2) Yocto Morty (2.2) Yocto Morty (2.2)
Managed Virtual Machine (MVM) N/A N/A N/A N/A N/A N/A N/A N/A belk-4.0.0 (based on Ubuntu 14.04 64 bit) belk-4.1.0 (based on Ubuntu 14.04 64 bit) belk-4.1.0 (based on Ubuntu 14.04 64 bit) belk-4.1.0 (based on Ubuntu 14.04 64 bit)

Downloadable binary images[edit | edit source]

All binary images for BELK/BXELK are hosted on 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 in the tables below.

200px-Emblem-important.svg.png

In order to create a bootable microSD card, the binary files must be renamed as follows:

  • For BELK <= 3.0.2 and BXELK <= 1.0.1 :
    • FSBL: boot.bin
    • Linux kernel: uImage
    • Device tree: bora.dtb
  • For BELK-4.1.0 or newer and BXELK-2.0.0 or newer:
    • U-Boot SPL: boot.bin
    • U-Boot: u-boot.img
    • FPGA Bitstream: fpga.bit
    • Linux kernel: uImage
    • Device tree: bora.dtb
Image BELK version BXELK version
4.1.4 4.1.4
mksd.sh mksd.sh mksd.sh
bootscript boot.scr boot.scr
U-Boot SPL (for uSD boot) boot.bin boot.bin
U-Boot SPL (for NOR flash boot) boot.bin boot.bin
U-Boot SPL (for NAND flash boot)
(for BoraLite SOM)		 boot.bin -
U-Boot (for uSD boot) u-boot.img u-boot.img
U-Boot (for NOR flash boot) u-boot.img u-boot.img
U-Boot (for NAND flash boot)
(for BoraLite SOM)		 u-boot.img -
FPGA Bitstream fpga.bit fpga.bit
Linux kernel uImage uImage
Device tree bora.dtb bora.dtb
Root File System bora.tar.bz2 bora.tar.bz2
Image BELK version BXELK version
3.0.2 1.0.1
mksd.sh mksd.sh mksd.sh
bootscript boot.scr boot.scr
FSBL (QSPI) fsbl.bin fsbl.bin
U-Boot (QSPI) u-boot.bin u-boot.bin
Boot.bin (SD) boot.bin boot.bin
Boot header boot-header boot-header
Linux kernel uImage uImage
Device tree bora.dtb bora.dtb
Root File System bora.tar.gz bora.tar.gz
Image BELK version BXELK version
3.0.1 1.0.0
mksd.sh mksd.sh mksd.sh
uEnv uEnv.txt uEnv.txt
FSBL (QSPI) fsbl.bin fsbl.bin
U-Boot (QSPI) u-boot.bin u-boot.bin
Boot.bin (SD) boot.bin boot.bin
Boot header boot-header boot-header
Linux kernel uImage uImage
Device tree bora.dtb bora.dtb
Root File System bora.tar.gz bora.tar.gz


microSD layout[edit | edit source]

The microSD card provided with BELK/BXELK is partitioned as shown in the following image:


microSD card partitioning


Most of storage space is occupied by two partitions:

  • a FAT32 partition (mmcblk0p1) containing:
    • For BELK <= 3.0.2 and BXELK <= 1.0.1 :
      • boot.bin boot image (containing FSBL, FPGA Bitstream an U-boot binaries)
      • U-Boot boot.scr bootscript
      • Linux kernel and DTB binary images
    • For BELK 4.0.0 or newer and BXELK 2.0.0 or newer:
      • boot.bin u-boot SPL image
      • fpga.bit optional FPGA bitstream
      • u-boot.img u-boot image
      • U-Boot boot.scr bootscript
      • Linux kernel and DTB binary images
      • MVM image in OVA format
  • an ext3 partition (mmcblk0p2) containing the root file system for the target.

bootscript and root file system are used to boot the target as described in this section.

It is worth remembering that the microSD card is bootable and U-Boot environment is retrieved from (and stored to with saveenv) into the FAT partition as bora.env


Updates[edit | edit source]

200px-Emblem-important.svg.png

It's recommended to use the latest source release available. Please refer to Release notes for further information.



Updating git repositories[edit | edit source]

In BELK/BXELK, the following source trees are clones of the correspondent DAVE Embedded Systems git repositories:

Component GIT Remote
U-Boot git@git.dave.eu:dave/bora/u-boot-xlnx.git
Linux kernel git@git.dave.eu:dave/bora/linux-xlnx.git
Yocto BSP git@git.dave.eu:dave/bora/bora-bsp.git
Vivado project git@git.dave.eu:dave/bora/bora.git

For more information about the access to these repositories, please refer to this link.

Updating the repositories from BELK 2.1.0[edit | edit source]

200px-Emblem-important.svg.png

To update the repositories from BELK 2.1.0, the following commands should be used: 

git fetch origin
git checkout -b <new_branch_name> origin/bora

Synchronizing the repositories[edit | edit source]

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


Release notes[edit | edit source]

BELK 4.1.4[edit | edit source]

Updates:

  1. Fixes for MAC programming on NOR SPI OTP

Known Limitations[edit | edit source]

ID Component Subsystem Description
0001 BoraEVB External DDR3 bank (BoraEVB only) DDR3 bank can be populated on request. For more details please refer to Sales Department.
0002 BoraEVB/BoraXEVB ETH1 interface Please refer to this application note for second Ethernet interface support.
0003 BoraEVB/BoraXEVB RTC Date/time retention is limited to about 4 hours.
0004 BoraEVB/BoraXEVB System clock runs slower As per Xilinx issue, @333MHz (speedgrade -3) system clock is slower then expected

BELK 4.1.2[edit | edit source]

Updates:

  1. Added support for MAC programming on NOR SPI OTP

Known Limitations[edit | edit source]

ID Component Subsystem Description
0001 BoraEVB External DDR3 bank (BoraEVB only) DDR3 bank can be populated on request. For more details please refer to Sales Department.
0002 BoraEVB/BoraXEVB ETH1 interface Please refer to this application note for second Ethernet interface support.
0003 BoraEVB/BoraXEVB RTC Date/time retention is limited to about 4 hours.
0004 BoraEVB/BoraXEVB System clock runs slower As per Xilinx issue, @333MHz (speedgrade -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 4.1.0[edit | edit source]

Updates:

  1. Added support for BoraLite SOM

Known Limitations[edit | edit source]

ID Component Subsystem Description
0001 BoraEVB External DDR3 bank (BoraEVB only) DDR3 bank can be populated on request. For more details please refer to Sales Department.
0002 BoraEVB/BoraXEVB ETH1 interface Please refer to this application note for second Ethernet interface support.
0003 BoraEVB/BoraXEVB RTC Date/time retention is limited to about 4 hours.
0004 BoraEVB/BoraXEVB System clock runs slower As per Xilinx issue, @333MHz (speedgrade -3) system clock is slower then expected

BELK 4.0.0 / BXELK 2.0.0[edit | edit source]

Updates:

  1. Switched to Vivado 2017.1
  2. Updated U-Boot and Linux versions

Known Limitations[edit | edit source]

ID Component Subsystem Description
0001 BoraEVB External DDR3 bank (BoraEVB only) DDR3 bank can be populated on request. For more details please refer to Sales Department.
0002 BoraEVB/BoraXEVB ETH1 interface Please refer to this application note for second Ethernet interface 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: 
cd /home/dvdk/bora/sdk/belk-4.0.0/sysroots/
sudo ln -s x86_64-petalinux-linux x86_64-petalinuxsdk-linux

otherwise, the SDK can be updated for fixing this issue using 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 this file

0006 MVM Cross-building environment The script ~/env.sh does not set the CC variable properly.

To fix this, please comment out the following line:

export CC=gcc

0007 BoraEVB/BoraXEVB System clock runs slower As per Xilinx issue, @333MHz (speedgrade -3) system clock is slower then expected

BELK 3.0.2 / BXELK 1.0.1[edit | edit source]

Updates:

  1. Fix BELK-3.0.1/BXELK-1.0.0 software issues
  2. Use standard DAVE recovery scripts for u-boot

(BoraXEVB only) For LCD interfacing, please refer to this application note.

Known Limitations[edit | edit source]

ID Component Issue Description
0001 BoraEVB External DDR3 bank (BoraEVB only) DDR3 bank can be populated on request. For more details please refer to Sales Department.
0002 BoraEVB/BoraXEVB ETH1 interface Please refer to 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[edit | edit source]

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

BELK 3.0.1 / BXELK 1.0.0[edit | edit source]

Updates: added support for BoraX/BoraXEVB evaluation system

(BoraXEVB only) For LCD interfacing, please refer to this application note.

Known Limitations[edit | edit source]
Issue Description
canutils package is missing is default root file system It can be downloaded directly from our package repository as described here
External DDR3 bank (BoraEVB only) DDR3 bank can be populated on request. For more details please refer to Sales Department.
ETH1 interface Please refer to this application note for second Ethernet interface support.
RTC Date/time retention is limited to about 4 hours.
Boot for NOR flash U-Boot is not configured properly to support NOR boot. Please use boot from microSD card instead.

BELK 3.0.0[edit | edit source]

Updates:

  1. Added preliminary support for BORA Xpress SOM
  2. Updated U-Boot and Linux versions

(BoraXEVB only) For LCD interfacing, please refer to this application note.

Known Limitations[edit | edit source]
Issue Description
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)
External DDR3 bank (BoraEVB only) DDR3 bank can be populated on request. For more details please refer to Sales Department.
ETH1 interface Please refer to this application note for second Ethernet interface support.
RTC Date/time retention is limited to about 4 hours.

BELK 2.2.0[edit | edit source]

Updates:

  1. Switched to Vivado 2014.4
  2. 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).
  3. Added ConfigID
  4. Updated U-Boot and Linux versions
Known Limitations[edit | edit source]
Issue Description
Kernel command line 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)
External DDR3 bank (BoraEVB only) DDR3 bank can be populated on request. For more details please refer to Sales Department.
ETH1 interface Please refer to this application note for second Ethernet interface support.
RTC Date/time retention is 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 bora-next branch, release belk-2.2.1-rc1, available on u-boot repository.

BELK 2.1.0[edit | edit source]

Updates:

  1. Fix and performance improvement on u-boot network interface
  2. Fix SD card hotplug issue in Linux
  3. First Yocto Daisy (1.6) BSP Release
Known Limitations[edit | edit source]
Issue Description
ETH0 interface 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)
External DDR3 bank (BoraEVB only) DDR3 bank can be populated on request. For more details please refer to Sales Department.
ETH1 interface The additional Gigabit Ethernet interface (ETH1) is not supported in this BELK version.
RTC Date/time retention is limited to about 4 hours.

BELK 2.0.0[edit | edit source]

Updates:

  1. Added support for the BoraEVB carrier board
  2. Updated supported drivers list (please refer to BELK_software_components)
Known Limitations[edit | edit source]

The following table reports the known limitations of this BELK release:

Issue Description
External DDR3 bank (BoraEVB only) DDR3 bank can be populated on request. For more details please refer to Sales Department.
ETH1 interface The additional Gigabit Ethernet interface (ETH1) is not supported in this BELK version.
RTC Date/time retention is limited to about 4 hours.

BELK 1.1.0[edit | edit source]

Updates:

  1. Switched to Vivado 2013.3
  2. Added application note "AMP on Bora"

BELK 1.0.0[edit | edit source]

First official release


HOME SOMs SBCs ToloMEO Embedded Assistant Sale-tag.pngGET A QUOTE Customer-service.pngONLINE HELPDESK
Roadmap IoT Services ML/AI services Embedded Design Services
Retrieved from "https://wiki.dave.eu/index.php?title=BELK/BXELK_software_components&oldid=17103"