Difference between revisions of "BoraX Embedded Linux Kit (BXELK)"

From DAVE Developer's Wiki
Jump to: navigation, search
 
(12 intermediate revisions by 4 users not shown)
Line 2: Line 2:
 
{{Applies To BoraX}}
 
{{Applies To BoraX}}
 
{{InfoBoxBottom}}
 
{{InfoBoxBottom}}
==Introduction==
 
  
 +
{{ObsoleteWikiPage|link=DESK-XZ7-L}}
 +
 +
{{ImportantMessage|text='''For BXELK 1.0.1 or older, the boot process was based on the FSBL+second-stage bootloader (U-Boot) combination. From BXELK 2.0.0 on, the boot process is based on the first-stage bootloader (U-Boot SPL)+second-stage bootloader (U-Boot) combination.'''
 +
}}
 +
 +
<section begin="Unboxing" />
 +
==Unboxing==
  
 
[[File:BORA_Xpress.png|thumb|center|400px|BoraX SOM]]
 
[[File:BORA_Xpress.png|thumb|center|400px|BoraX SOM]]
  
  
BoraX Embedded Linux Kit (BXELK for short) provides all the necessary components required to set up the developing environment to:
+
BoraX Embedded Linux Kit (BXELK for short) provides all the necessary components required to set up the developing environment for:
* build the first-stage bootloader (FSBL) for BELK <= 3.0.2 and BXELK <= 1.0.1
+
* building the first-stage bootloader:
* build U-boot SPL for BELK-4.0.0 and BXELK-2.0.0
+
**FSBL for BXELK 1.0.1 or older
* build the 2nd-stage bootloader (U-Boot)
+
**U-boot SPL for BXELK 2.0.0 or newer
* build and run Linux operating system on [[:Category:BoraX|BoraX system-on-module (SOM)]]
+
* building the second-stage bootloader (U-Boot)
* build and debug applications that will be executed on top of Yocto-based Linux distribution running on the target.
+
* building and running Linux operating system on [[BORA_Xpress_SOM|BORA Xpress SOM]]
 +
* building and debugging applications that will be executed on top of Yocto-based Linux distribution running on the target.
 +
 
 
The main kit components are:
 
The main kit components are:
* hardware platform, composed by [[:Category:BoraX|BoraX SOM]] and [[BoraXEVB]]
+
* hardware platform, composed by [[BORA_Xpress_SOM|BORA Xpress SOM]] and [[BORA_Xpress_SOM/BORA_Xpress_Evaluation_Kit | BORA Xpress Evalutation kit]]
 
* source code of target software
 
* source code of target software
 
* technical documentation (hardware manuals, mechanical drawings, reference schematics, application notes etc.)
 
* technical documentation (hardware manuals, mechanical drawings, reference schematics, application notes etc.)
 +
<section end="Unboxing" />
 +
<section begin="Kit Content" />
  
==Kit content==
+
==Kit contents==
 
+
{| class="wikitable" style="margin: auto;"
{| class="wikitable"  
 
 
|-
 
|-
 
!Component
 
!Component
Line 27: Line 36:
 
!Notes
 
!Notes
 
|-
 
|-
|style="text-align: center;" | [[File:BORA_Xpress.png|60px]]
+
| style="text-align: center;" | [[File:BORA_Xpress.png|60px]]
|BoraX SOM (p/n DBXF4110D2R)<br>
+
|[[BORA Xpress SOM|BORA Xpress]] SOM (p/n DBXF4110S2R)<br>
 
*SoC: Xilinx XC7Z030 (866Mhz, Speed "-3", Tj 0-100°C)
 
*SoC: Xilinx XC7Z030 (866Mhz, Speed "-3", Tj 0-100°C)
 
*SDRAM: 1 GB DDR3
 
*SDRAM: 1 GB DDR3
Line 34: Line 43:
 
*NAND: 1GB (SLC)
 
*NAND: 1GB (SLC)
 
|
 
|
 +
* For more details, please refer to the[[BORA_Xpress_SOM/BORA_Xpress_Hardware | BORA Xpress Hardware Manual]]
 +
* By default, ARM cores frequency is set to 667 MHz and the [[Creating and building example Vivado project (BELK/BXELK)|example Vivado project]] is implemented for a "-1" device. This choice makes the software released with the kit compatible with possible variants based on different SoM models. In this regard, see also the [[#Order codes|order codes section]].
 
|-
 
|-
|style="text-align: center;" | [[File:BoraXEVB-01.png|60px]]
+
| style="text-align: center;" | [[File:BoraXEVB-01.png|60px]]
|[[BoraXEVB]] carrier board
+
|[[BORA_Xpress_SOM/BORA_Xpress_Evaluation_Kit | BORA Xpress]] Carrier board
 
|
 
|
 
|-
 
|-
|style="text-align: center;" | [[File:Alimentatore.jpg|40px]]
+
| style="text-align: center;" | [[File:Alimentatore.jpg|40px]]
 
|AC/DC Single Output Wall Mount adapter<br>
 
|AC/DC Single Output Wall Mount adapter<br>
 
Output: +12V – 2.0 A
 
Output: +12V – 2.0 A
 
|
 
|
 
|-
 
|-
|style="text-align: center;" | [[File:ProdSDC-MBLY-thumb.png|50px]]
+
| style="text-align: center;" | [[File:ProdSDC-MBLY-thumb.png|50px]]
 
|microSDHC card with SD adapter and USB adapter
 
|microSDHC card with SD adapter and USB adapter
 
|
 
|
 
|-
 
|-
 
|}
 
|}
 +
 +
===Order codes===
 +
{| class="wikitable" style="margin: auto;"
 +
|+
 +
!Order code
 +
!Description
 +
|-
 +
|BXELK-H-S
 +
|This code refers to the default configuration detailed above
 +
|-
 +
|BXELK-H-S-D
 +
|This variant is like BELK-L-S, except the SOM, which is DBXD4110S2R.
 +
|}
 +
<section end="Kit Content" />
  
 
==Logical structure of BXELK==
 
==Logical structure of BXELK==
Line 57: Line 82:
  
 
==Quick start guide==
 
==Quick start guide==
This chapter describes how to quickly start working with the BXELK kit. The following paragraphs will guide you through the setup and installation procedures.
+
Please refer to [[BELK/BXELK_Quick_Start_Guide|this page]].
===Kit registration===
 
{{ImportantMessage|text='''Customers are strongly recommended to register their kits'''. Registration grants access to reserved material such as source code and additional documentation.}}
 
 
 
Please register your development kit by sending an email to [mailto:support-bora@dave.eu support-bora@dave.eu], providing the kit P/N and CODE. If you also wish to access git repositories containing source code, please follow the procedure described [[Accessing_DAVE_Embedded_Systems_restricted_git_repositories|here]].
 
 
 
===Target setup and first boot===
 
This section describes how to quickly start BoraX/BoraXEVB system included in the BXELK:
 
*on target side, connect a null-modem cable on J17 DB9 connector, denoted also as UART1
 
*on host side, connect the other end of the null-modem cable to a COM port and start your favorite terminal software that will be used to interact with the target's serial console; communication parameters are 115200-8-N-1
 
*optionally connect the BoraXEVB board to an Ethernet LAN by plugging cable into connector J8, also denoted as BORAX ETHERNET
 
*connect 12V power supply to JP2 connector, also denoted as PSU 12V JACK
 
*insert the microSD card in the slot J21, also denoted as MICROSD.
 
 
 
 
 
[[File:BoraX-BoraXEVB-1st-boot.jpg|thumb|center|600px|Target setup for first boot]]
 
 
 
 
 
Once power has been applied to the target, FSBL or U-boot SPL and U-Boot bootloaders will be fetched from the SPI NOR flash that equips BoraX SOM and executed. Boot messages will be printed out to the serial console. Redundant U-Boot environment is stored in the NOR flash as well, as depicted in the following image.
 
 
 
 
 
[[File:BXELK-NOR-partitioning.png|thumb|center|350px|BXELK <= 1.0.1 NOR flash default partitioning]]
 
[[File:BXELK-2.0.0-NOR-partitioning.png|thumb|center|350px|BXELK-2.0.0 NOR flash default partitioning]]
 
 
 
 
 
By default, U-Boot is configured to retrieve Linux kernel image stored in the microSD card [1]. In turn, Linux kernel shall mount root file system from the <code>mmcblk0p2</code> partition of the [[#BXELK microSD Layout|microSD card itself]] [2], [3]. At the end of boot process, Linux shell shall be available on the serial console. Default boot process '''does not download any bitstream''' to the Programmable Logic.
 
 
 
The following dump shows the typical messages printed out to the console during bootstrap process.
 
<pre class="mw-collapsible mw-collapsed">
 
TBD
 
</pre>
 
 
 
 
 
 
 
[1] <code>bootscript</code> is used to do this task.
 
 
 
[2] This root file system has been generated by [[Advanced_use_of_Yocto_build_system_(BELK/BXELK)|Yocto build system]].
 
 
 
[3] The microSD card is bootable itself, as explained [[System_boot_and_recovery_via_microSD_card_(BELK/BXELK)|here]].
 
 
 
===Host setup and target software development===
 
Please refer to [[Host setup and development flow (BXELK)|this page]].
 
 
 
===Target configuration for the development stage (<code>net_nfs</code>)===
 
During the development stage, the target is usually connected via Ethernet LAN to the host machine and is configured to:
 
*retrieve binary images (i.e. Linux kernel) via TFTP protocol
 
*mount the development root file system via NFS protocol. This root file system is physically in the file system of the host machine as depicted [[Deploying_Embedded_Linux_Systems#The_development_environment|here]].
 
In DAVE Embedded Systems development kits, this configuration is generally denoted as <code>net_nfs</code>. U-Boot bootloader supports this configuration. Some U-Boot environment variables are needed to set it up.
 
 
 
For more information about how to set up and use TFTP and NFS servers, please refer to the following link [[Booting_the_system_via_NFS_(BELK/BXELK)|Booting the system via NFS (BELK/BXELK)]].
 
 
 
===Target configuration for standalone boot===
 
Please refer to [[Standalone_boot_(BXELK)|this page]].
 
===Recovery procedure===
 
In case the target is not able to boot from NOR flash for any reason, this [[System_boot_and_recovery_via_microSD_card_(BELK/BXELK)|recovery procedure]] can be use to boot from microSD card.
 
  
 
==Physical devices mapping==
 
==Physical devices mapping==
Please refer to [[Physical_devices_mapping_(BXELK)|this page]].
+
Please refer to [[Physical_devices_mapping_(BELK/BXELK)|this page]].
 
==Advanced topics==
 
==Advanced topics==
 
===Debugging with Eclipse===
 
===Debugging with Eclipse===

Latest revision as of 16:05, 31 January 2024

Info Box
BORA Xpress.png Applies to BORA Xpress



Attention.png THIS PAGE IS OBSOLETE, DON'T USE IT AS REFERENCE
The new documentation is available here: DESK-XZ7-L


200px-Emblem-important.svg.png

For BXELK 1.0.1 or older, the boot process was based on the FSBL+second-stage bootloader (U-Boot) combination. From BXELK 2.0.0 on, the boot process is based on the first-stage bootloader (U-Boot SPL)+second-stage bootloader (U-Boot) combination.


Unboxing[edit | edit source]

BoraX SOM


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

  • building the first-stage bootloader:
    • FSBL for BXELK 1.0.1 or older
    • U-boot SPL for BXELK 2.0.0 or newer
  • building the second-stage bootloader (U-Boot)
  • building and running Linux operating system on BORA Xpress SOM
  • building and debugging applications that will be executed on top of Yocto-based Linux distribution running on the target.

The main kit components are:

  • hardware platform, composed by BORA Xpress SOM and BORA Xpress Evalutation kit
  • source code of target software
  • technical documentation (hardware manuals, mechanical drawings, reference schematics, application notes etc.)


Kit contents[edit | edit source]

Component Description Notes
BORA Xpress.png BORA Xpress SOM (p/n DBXF4110S2R)
  • SoC: Xilinx XC7Z030 (866Mhz, Speed "-3", Tj 0-100°C)
  • SDRAM: 1 GB DDR3
  • NOR: bootable SPI flash 16 MB
  • NAND: 1GB (SLC)
  • For more details, please refer to the BORA Xpress Hardware Manual
  • By default, ARM cores frequency is set to 667 MHz and the example Vivado project is implemented for a "-1" device. This choice makes the software released with the kit compatible with possible variants based on different SoM models. In this regard, see also the order codes section.
BoraXEVB-01.png BORA Xpress Carrier board
Alimentatore.jpg AC/DC Single Output Wall Mount adapter

Output: +12V – 2.0 A

ProdSDC-MBLY-thumb.png microSDHC card with SD adapter and USB adapter

Order codes[edit | edit source]

Order code Description
BXELK-H-S This code refers to the default configuration detailed above
BXELK-H-S-D This variant is like BELK-L-S, except the SOM, which is DBXD4110S2R.


Logical structure of BXELK[edit | edit source]

Please refer to this page.

BXELK software components[edit | edit source]

Please refer to this page.

Quick start guide[edit | edit source]

Please refer to this page.

Physical devices mapping[edit | edit source]

Please refer to this page.

Advanced topics[edit | edit source]

Debugging with Eclipse[edit | edit source]

Please refer to this page.

ConfigID feature[edit | edit source]

Please refer to this page.