Difference between revisions of "Bora Embedded Linux Kit (BELK)"

From DAVE Developer's Wiki
Jump to: navigation, search
(Related Documents)
m (BELK software components)
(35 intermediate revisions by 5 users not shown)
Line 2: Line 2:
 
{{Applies To Bora}}
 
{{Applies To Bora}}
 
{{InfoBoxBottom}}
 
{{InfoBoxBottom}}
 
{{ImportantMessage|text='''For BELK 3.0.2 or older, the boot process was based on the FSBL+second-stage bootloader (U-Boot) combination. From BELK 4.0.0 on, the boot process is based on the first-stage bootloader (U-Boot SPL)+second-stage bootloader (U-Boot) combination.'''
 
}}
 
 
  
 
==Introduction==
 
==Introduction==
Line 12: Line 8:
  
 
Bora Embedded Linux Kit (BELK for short) provides all the necessary components required to set up the developing environment for:
 
Bora Embedded Linux Kit (BELK for short) provides all the necessary components required to set up the developing environment for:
* building the first-stage bootloader:
+
* configuring the system (PS and PL) at hardware level
** FSBL for BELK 3.0.2 or older
+
* build the first-stage bootloader (FSBL)
** U-boot SPL for BELK 4.0.0 or newer
+
* building the second stage bootloader (U-Boot)
* building the second-stage bootloader (U-Boot)
 
 
* building and running Linux operating system on Bora-based systems
 
* building and running Linux operating system on Bora-based systems
* building Linux applications that will run on the target.
+
* building Linux applications that will run on the target
 +
 
 +
'''DAVE Embedded Systems''' provides all the customization required (in particular at bootloader and Linux kernel levels) to enable customers use the standard Zynq-7000 development tools for building all the firmware/software components that will run on the target system.
 +
 
 +
 
 +
==Logical structure of Bora Embedded Linux Kit (BELK)==
 +
To understand the structure of BELK, it is necessary to describe the basic organization of Xilinx Vivado Design Suite/Xilinx SDK and to recall briefly the recent history of development tools provided by Xilinx.
 +
 
 +
===A little bit of history===
 +
At the time of this writing (October 2013) Xilinx is migrating from mature ISE 14.x Design Suite - that should be the last series of this suite - to the new Vivado environment. Both are composed by several programs and some of these are in common. From the general standpoint, the main difference between ISE and Vivado - even if ISE does support Zynq - is that the latter has been expressively conceived to support newer SoC architectures such as Zynq, besides traditional FPGAs. Thus, adopting Vivado as the default environment for BELK would seem the natural choice. However, the migration process mentioned above has just begun and the majority of application notes and reference designs released by Xilinx still refers to ISE suite. Plus Vivado is still a little bit "green" and several bug fixes and improvements are introduced by every new release.
 +
 
 +
Since Bora was presented in 2013 and because this product addresses long longevity markets such as industrial and biomedical, '''DAVE Embedded Systems''' chose to build BELK upon Vivado that undoubtedly represents today the future of Xilinx development environments.
 +
 
 +
===Structure of BELK reference designs===
 +
 
 +
The typical linux-based Zynq design is composed by the following parts:
 +
* FSBL
 +
* U-Boot
 +
* device tree file
 +
* Linux kernel
 +
* Root file system
 +
* Executable image of core #1 (in case of AMP systems)
 +
* FPGA bitstream.
 +
 
 +
Generally speaking, these parts - in the binary/sinthesized form - are combined together in one monolithic file that is stored in a non-volatile memory such as SPI NOR flash. Generating this file is quite easy as described by Vivado documentation. However in real world products, this may be too rigid because developers may want to handle these parts separately and independently.
 +
 
 +
 
 +
===Basic structure of Vivado Design Suite and integration into BELK===
 +
Vivado/SDK (1) can be viewed as a collection of programs required to deal with all of the development aspects related to Xilinx components (software running on ARM cores, FPGA fabric verification and programming, power estimation etc.). These include strictly FPGA-related tools such as Floorplanner and pure-software development tools such as SDK.
 +
The ambitious objective is to provide a complete, user friendly, integrated environment that allows software developers to deal with FPGA development even if they are not familiar with this technology, by hiding a lot of its complexities (2). As usual this ease of use comes at the expence of control and flexibility. This could not be acceptable in many cases where engineers need to control and customize many aspects of the project to implement what is required by system specifications. For this reason BELK has been built around Vivado but some deviations from the default development approach suggested by Xilinx have been introduced, in order to '''push the modularization and the maintainability of the projects to the maximum possible extent'''.
 +
 
 +
The following pictures are retrieved from BELK Quick Start Guide and shows respectively the Vivado/SDK default development flow and how this has been integrated in the BELK infrastructure.
 +
 
 +
[[File:Belk-vivado-sdk-development-flow.png|thumbnail|center|300px|Vivado/SDK development flow]]
 +
[[File:Belk-vivado-sdk-integration.png|thumbnail|center|300px|Vivado/SDK integration into BELK]]
  
'''DAVE Embedded Systems''' provides all the customization required (in particular at bootloader and Linux kernel levels) to enable customers to use the standard Zynq-7000 development tools for building all the firmware/software components that will run on the target system.
 
  
==Kit content==
+
(1) The Software Development Kit (SDK) is the Xilinx Integrated Design Environment for creating embedded applications on Zynq™-7000 All Programmable SoCs. SDK is the first application IDE to deliver true homogenous and heterogenous multi-processor design and debug, it is optionally included with the Vivado Design Suite or ISE Design Suite, or available as a separate free download for application developers.
 +
 
 +
(2) Nevertheless FPGA developers will find all the traditional tools that allow complete control of FPGA fabric.
 +
 
 +
==Kit Contents==
  
 
{| class="wikitable"  
 
{| class="wikitable"  
Line 30: Line 62:
 
|-
 
|-
 
|style="text-align: center;" | [[File:Bora5-small.jpg|60px]]
 
|style="text-align: center;" | [[File:Bora5-small.jpg|60px]]
|[[:Category:Bora|BORA]] SOM<br>CPU: Xilinx Zynx 7000
+
|[[Bora_SOM | Bora SOM]]<br>CPU: Xilinx Zynx 7000
 
|Please refer to [[Hardware Manual (Bora) | Bora Hardware Manual]]
 
|Please refer to [[Hardware Manual (Bora) | Bora Hardware Manual]]
 
|-
 
|-
 
|style="text-align: center;" | [[File:Boraevb-02.png|80px]]
 
|style="text-align: center;" | [[File:Boraevb-02.png|80px]]
|BORA Carrier board
+
|BoraEVB Carrier board
 
|Please refer to [[BoraEVB | BoraEVB]] page
 
|Please refer to [[BoraEVB | BoraEVB]] page
 
|-
 
|-
Line 47: Line 79:
 
|}
 
|}
  
==Logical structure of Bora Embedded Linux Kit (BELK)==
 
Please refer to [[Logical_structure_of_Bora_and_BoraX_Embedded_Linux_Kits_(BELK/BXELK)|this page]].
 
  
 
== BELK software components ==
 
== BELK software components ==
Please refer to [[BELK/BXELK_software_components|this page]].
 
  
==Quick start guide==
+
'''DAVE Embedded Systems''' adds to the latest Linux BSP from Xilinx the customization required to support the Bora platform, in particular at bootloader and linux kernel levels.
Please refer to [[BELK/BXELK_Quick_Start_Guide|this page]].
+
 
==Physical devices mapping==
+
The following table reports the XELK releases information.
Please refer to [[Physical_devices_mapping_(BELK/BXELK)|this page]].
+
{| class="wikitable"
==Advanced topics==
+
!
===Debugging with Eclipse===
+
!colspan="5" | BELK version
Please refer to [[Debugging with Eclipse (MVM)|this page]].
+
|-
===ConfigID feature===
+
|Release number
Please refer to [[ConfigID_management_(BELK/BXELK)|this page]].
+
|1.0.0
 +
|1.1.0
 +
|2.0.0
 +
|2.1.0
 +
|2.2.0
 +
|-
 +
|Status
 +
|Released
 +
|Released
 +
|Released
 +
|Released
 +
|Working
 +
|-
 +
|Release date
 +
|July 2013
 +
|November 2013
 +
|May 2014
 +
|August 2014
 +
|August 2015
 +
|-
 +
|'''Release notes'''
 +
|[[Bora_Embedded_Linux_Kit_(BELK)#BELK 1.0.0 | Ver 1.0.0]]
 +
|[[Bora_Embedded_Linux_Kit_(BELK)#BELK 1.1.0 | Ver 1.1.0]]
 +
|[[Bora_Embedded_Linux_Kit_(BELK)#BELK 2.0.0 | Ver 2.0.0]]
 +
|[[Bora_Embedded_Linux_Kit_(BELK)#BELK 2.1.0 | Ver 2.1.0]]
 +
| -
 +
|-
 +
|SOM PCB version
 +
|CS020313A
 +
|CS020313A
 +
|CS020313B
 +
|CS020313B
 +
|CS020313B
 +
|--
 +
|Supported carrier boards
 +
|[[BoraEVB-Lite]]
 +
|[[BoraEVB-Lite]]
 +
|[[BoraEVB]]
 +
|[[BoraEVB]]
 +
|[[BoraEVB]]
 +
|-
 +
|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
 +
|-
 +
|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
 +
|-
 +
|Drivers
 +
|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<br>[[ConfigID_and_UniqueID | ConfigID]]
 +
|-
 +
|Vivado version
 +
|valign="top" | 2013.2
 +
|valign="top" | 2013.3
 +
|valign="top" | 2013.3
 +
|valign="top" | 2013.3
 +
|valign="top" | 2014.4
 +
|-
 +
|Build System
 +
|valign="top" | -
 +
|valign="top" | -
 +
|valign="top" | -
 +
|valign="top" | Yocto Daisy (1.6)
 +
|valign="top" | Yocto Daisy (1.6)
 +
|-
 +
|}
 +
 
 +
 
 +
=== How to update BELK ===
 +
 
 +
{{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 ====
 +
 
 +
In BELK, the following source trees are clones of '''DAVE Embedded Systems''' public git repositories:
 +
 
 +
{| class="wikitable"
 +
|-
 +
!| Component
 +
!GIT Remote
 +
|-
 +
|Vivado project
 +
|git@git.dave.eu:dave/bora/bora.git
 +
|-
 +
|Linux
 +
|git@git.dave.eu:dave/bora/linux-xlnx.git
 +
|-
 +
|U-Boot
 +
|git@git.dave.eu:dave/bora/u-boot-xlnx.git
 +
|-
 +
|}
 +
 
 +
This means that these components can be kept in sync and up to date with '''DAVE Embedded Systems''' repositories.
 +
 
 +
==== RSA key generation ====
 +
 
 +
Please follow the procedure reported below to generate the RSA ssh key:
 +
 
 +
* 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>
 +
Host git.dave.eu
 +
    User git
 +
    Hostname git.dave.eu
 +
    PreferredAuthentications publickey
 +
    IdentityFile ~/.ssh/username@myhost.com
 +
</pre>
 +
 
 +
Please send the public key file to the following email support addresses:
 +
 
 +
* [mailto:support-bora@dave.eu support-bora@dave.eu]
 +
 
 +
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.
 +
 
 +
==== 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].
 +
 
 +
=== Release notes ===
 +
 
 +
==== BELK 2.1.0 ====
 +
 
 +
Updates:
 +
# Fix and performance improvement on u-boot network interface
 +
# Fix SD card hotplug issue in Linux
 +
# First [[Yocto BSP (BELK)|Yocto Daisy (1.6) BSP Release]]
 +
 
 +
===== Known Limitations =====
 +
 
 +
{| class="wikitable"
 +
|-
 +
!Issue
 +
!Description
 +
|-
 +
| ETH0 interface
 +
| 1. Primary Gigabit Ethernet Interface (ETH0) is not working correctly at 10Mbps<br>2. On BoraEVB, there is a mistake in the connection of the center tap pins. They should be separated from one another and connected through separate 0.1μF common-mode capacitors to ground (for further details (eg: connection and selection of the magnetics), please refer to the Micrel KSZ9031RNX datasheet).
 +
|-
 +
| 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
 +
|The DDR3 SDRAM bank on the BoraEVB is not supported in this BELK version.
 +
|-
 +
|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 ====
 +
 
 +
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 Limitations =====
 +
 
 +
The following table reports the known limitations of this BELK release:
 +
 
 +
{| class="wikitable"
 +
|-
 +
!Issue
 +
!Description
 +
|-
 +
|External DDR3 bank
 +
|The DDR3 SDRAM bank on the BoraEVB is not supported in this BELK version.
 +
|-
 +
|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 ====
 +
 
 +
Updates:
 +
# Switched to Vivado 2013.3
 +
# Added application note "AMP on Bora"
 +
 
 +
==== BELK 1.0.0 ====
 +
 
 +
First official release
  
 
== Related Documents ==
 
== Related Documents ==
Line 67: Line 302:
 
* [[Hardware Manual (Bora) | Bora Hardware Manual]]
 
* [[Hardware Manual (Bora) | Bora Hardware Manual]]
 
* [[BoraEVB-Lite | BoraEVB-Lite]]
 
* [[BoraEVB-Lite | BoraEVB-Lite]]
* [[BoraEVB | BORAEVB]]
+
* [[BoraEVB | BoraEVB]]
* [[BELK/BXELK Quick Start Guide]]
+
* Belk Quick Start Guide (available for BELK kit owners)
* [[FAQs_(Bora) | BORA FAQs]]
+
* [[Application_Notes_(Bora) | Application Notes]]
 +
* [[FAQs_(Bora) | Bora FAQs]]

Revision as of 13:34, 20 August 2015

Info Box
Bora5-small.jpg Applies to Bora

Introduction[edit | edit source]

Belk 01.png

Bora Embedded Linux Kit (BELK for short) provides all the necessary components required to set up the developing environment for:

  • configuring the system (PS and PL) at hardware level
  • build the first-stage bootloader (FSBL)
  • building the second stage bootloader (U-Boot)
  • building and running Linux operating system on Bora-based systems
  • building Linux applications that will run on the target

DAVE Embedded Systems provides all the customization required (in particular at bootloader and Linux kernel levels) to enable customers use the standard Zynq-7000 development tools for building all the firmware/software components that will run on the target system.


Logical structure of Bora Embedded Linux Kit (BELK)[edit | edit source]

To understand the structure of BELK, it is necessary to describe the basic organization of Xilinx Vivado Design Suite/Xilinx SDK and to recall briefly the recent history of development tools provided by Xilinx.

A little bit of history[edit | edit source]

At the time of this writing (October 2013) Xilinx is migrating from mature ISE 14.x Design Suite - that should be the last series of this suite - to the new Vivado environment. Both are composed by several programs and some of these are in common. From the general standpoint, the main difference between ISE and Vivado - even if ISE does support Zynq - is that the latter has been expressively conceived to support newer SoC architectures such as Zynq, besides traditional FPGAs. Thus, adopting Vivado as the default environment for BELK would seem the natural choice. However, the migration process mentioned above has just begun and the majority of application notes and reference designs released by Xilinx still refers to ISE suite. Plus Vivado is still a little bit "green" and several bug fixes and improvements are introduced by every new release.

Since Bora was presented in 2013 and because this product addresses long longevity markets such as industrial and biomedical, DAVE Embedded Systems chose to build BELK upon Vivado that undoubtedly represents today the future of Xilinx development environments.

Structure of BELK reference designs[edit | edit source]

The typical linux-based Zynq design is composed by the following parts:

  • FSBL
  • U-Boot
  • device tree file
  • Linux kernel
  • Root file system
  • Executable image of core #1 (in case of AMP systems)
  • FPGA bitstream.

Generally speaking, these parts - in the binary/sinthesized form - are combined together in one monolithic file that is stored in a non-volatile memory such as SPI NOR flash. Generating this file is quite easy as described by Vivado documentation. However in real world products, this may be too rigid because developers may want to handle these parts separately and independently.


Basic structure of Vivado Design Suite and integration into BELK[edit | edit source]

Vivado/SDK (1) can be viewed as a collection of programs required to deal with all of the development aspects related to Xilinx components (software running on ARM cores, FPGA fabric verification and programming, power estimation etc.). These include strictly FPGA-related tools such as Floorplanner and pure-software development tools such as SDK. The ambitious objective is to provide a complete, user friendly, integrated environment that allows software developers to deal with FPGA development even if they are not familiar with this technology, by hiding a lot of its complexities (2). As usual this ease of use comes at the expence of control and flexibility. This could not be acceptable in many cases where engineers need to control and customize many aspects of the project to implement what is required by system specifications. For this reason BELK has been built around Vivado but some deviations from the default development approach suggested by Xilinx have been introduced, in order to push the modularization and the maintainability of the projects to the maximum possible extent.

The following pictures are retrieved from BELK Quick Start Guide and shows respectively the Vivado/SDK default development flow and how this has been integrated in the BELK infrastructure.

Vivado/SDK development flow
Vivado/SDK integration into BELK


(1) The Software Development Kit (SDK) is the Xilinx Integrated Design Environment for creating embedded applications on Zynq™-7000 All Programmable SoCs. SDK is the first application IDE to deliver true homogenous and heterogenous multi-processor design and debug, it is optionally included with the Vivado Design Suite or ISE Design Suite, or available as a separate free download for application developers.

(2) Nevertheless FPGA developers will find all the traditional tools that allow complete control of FPGA fabric.

Kit Contents[edit | edit source]

Component Description Notes
Bora5-small.jpg Bora SOM
CPU: Xilinx Zynx 7000
Please refer to Bora Hardware Manual
Boraevb-02.png BoraEVB Carrier board Please refer to BoraEVB page
Alimentatore.jpg AC/DC Single Output Wall Mount adapter
Output: +12V – 2.0 A
Please refer to Belk Quick Start Guide
ProdSDC-MBLY-thumb.png MicroSDHC card with SD adapter and USB adapter Please refer to Belk Quick Start Guide


BELK software components[edit | edit source]

DAVE Embedded Systems adds to the latest Linux BSP from Xilinx the customization required to support the Bora platform, in particular at bootloader and linux kernel levels.

The following table reports the XELK releases information.

BELK version
Release number 1.0.0 1.1.0 2.0.0 2.1.0 2.2.0
Status Released Released Released Released Working
Release date July 2013 November 2013 May 2014 August 2014 August 2015
Release notes Ver 1.0.0 Ver 1.1.0 Ver 2.0.0 Ver 2.1.0 -
SOM PCB version CS020313A CS020313A CS020313B CS020313B CS020313B
Supported carrier boards BoraEVB-Lite BoraEVB-Lite BoraEVB BoraEVB BoraEVB
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
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
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
Vivado version 2013.2 2013.3 2013.3 2013.3 2014.4
Build System - - - Yocto Daisy (1.6) Yocto Daisy (1.6)


How to update BELK[edit | edit source]

200px-Emblem-important.svg.png It's recommended to use the latest available BELK version. Please refer to Release notes for further information. 200px-Emblem-important.svg.png

Updating git repositories[edit | edit source]

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

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

This means that these components can be kept in sync and up to date with DAVE Embedded Systems repositories.

RSA key generation[edit | edit source]

Please follow the procedure reported below to generate the RSA ssh key:

  • 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: cd ~/.ssh/
  • launch the following command:
    ssh-keygen -t rsa -C "username@myhost.com" -f username@myhost.com
  • this command creates the files ~/.ssh/username@myhost.com (private key) and ~/.ssh/username@myhost.com.pub (public key)
  • edit your ~/.ssh/config adding the following lines:
Host git.dave.eu
    User git
    Hostname git.dave.eu
    PreferredAuthentications publickey
    IdentityFile ~/.ssh/username@myhost.com

Please send the public key file to the following email support addresses:

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.

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 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 1. Primary Gigabit Ethernet Interface (ETH0) is not working correctly at 10Mbps
2. On BoraEVB, there is a mistake in the connection of the center tap pins. They should be separated from one another and connected through separate 0.1μF common-mode capacitors to ground (for further details (eg: connection and selection of the magnetics), please refer to the Micrel KSZ9031RNX datasheet).
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 The DDR3 SDRAM bank on the BoraEVB is not supported in this BELK version.
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 The DDR3 SDRAM bank on the BoraEVB is not supported in this BELK version.
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

Related Documents[edit | edit source]