BORA SOM/BELK-L/General/Release Notes
Release Notes[edit | edit source]
DAVE Embedded Systems adds to the latest Linux BSP from Xilinx the customization required to support the SOC platform. For this reason most of the documentation provided by Xilinx remains valid for the BELK development kit.
However, some customization is required, in particular at bootloader and linux kernel levels.
The following table reports the BELK releases information.
|Release type||Minor (base on BELK 4.0.0 major release)|
|Release date||Sep 2021|
|Release notes||Ver 4.1.5|
|MVM (distro version)||Ubuntu 16.04|
SPI NOR Flash (boot)
|Build System||Yocto Morty (2.2)|
BELK 4.1.5[edit | edit source]
New MVM must be installed for using BELK-4.1.0. The VM is available for download on DAVE's BORA Reserved Area for registered users.
- Updated u-boot version for BORA Lite support (updated defconfig for NOR and SD boot)
Known Limitations[edit | edit source]
The following table reports the known limitations of this BELK release:
|0001||BoraEVB||External DDR3 bank (BoraEVB only)||DDR3 bank can be populated on request. For more details please refer to Sales Department.|
|0002||BoraEVB||ETH1 interface||Please refer to this application note for second Ethernet interface support.|
|0003||BoraEVB||RTC||Date/time retention is limited to about 4 hours.|
|0004||BoraEVB||System clock runs slower||As per Xilinx issue, @333MHz (speedgrade -3) system clock is slower then expected|
Downloadable binary images[edit | edit source]
All binary images for BELK are hosted on DAVE Embedded System mirror server. There you can find a sub directory for each version of this development kit.
U-boot performs 2-stage bootloader providing two files:
u-boot.img. Both two files must be stored into SD card using
A summary of images with a brief description can be found into the table below:
|Image||BELK version 4.1.5|
Release types[edit | edit source]
BELK release type can be:
- Major, when substantial changes are applied to the BSP (eg: major kernel version upgrades) or to the development kit (eg: new features, build system updates, ..). This usually means that a new DVDK is created for the BELK release
- Maintenance, when minor updates and bug fixes are introduced. This usually means that the DVDK remains the same provided with the previous major version, and only an update of the source tree repositories (and the tftp binaries) is required
As an example, BELK 4.1.0 is a maintenance release, so it provides the DVDK released with the 4.0.0 major release; customers can easily upgrade to the 1.1.0 release by updating the software components as described in Synchronizing git repositories.