Difference between revisions of "BoraX Embedded Linux Kit (BXELK)"
(→Target setup and first boot) |
|||
| Line 9: | Line 9: | ||
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 to: | ||
| − | * build the first-stage bootloader (FSBL) | + | * build the first-stage bootloader (FSBL) for BELK <= 3.0.2 and BXELK <= 1.0.1 |
| + | * build U-boot SPL for BELK-4.0.0 and BXELK-2.0.0 | ||
* build the 2nd-stage bootloader (U-Boot) | * build the 2nd-stage bootloader (U-Boot) | ||
* build and run Linux operating system on [[:Category:BoraX|BoraX system-on-module (SOM)]] | * build and run Linux operating system on [[:Category:BoraX|BoraX system-on-module (SOM)]] | ||
| Line 74: | Line 75: | ||
| − | Once power has been applied to the target, FSBL 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. | + | 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|NOR flash default partitioning]] | + | [[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]] | ||
Revision as of 09:45, 30 June 2017
| HOME | SOMs | SBCs | ToloMEO Embedded Assistant |  GET A QUOTE
|
 ONLINE HELPDESK
|
| Roadmap | IoT Services | ML/AI services | Embedded Design Services |
Info Box
|
Contents
Introduction[edit | edit source]
BoraX Embedded Linux Kit (BXELK for short) provides all the necessary components required to set up the developing environment to:
- build the first-stage bootloader (FSBL) for BELK <= 3.0.2 and BXELK <= 1.0.1
- build U-boot SPL for BELK-4.0.0 and BXELK-2.0.0
- build the 2nd-stage bootloader (U-Boot)
- build and run Linux operating system on BoraX system-on-module (SOM)
- build and debug 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 BoraX SOM and BoraXEVB
- source code of target software
- technical documentation (hardware manuals, mechanical drawings, reference schematics, application notes etc.)
Kit content[edit | edit source]
| Component | Description | Notes |
|---|---|---|
|
BoraX SOM (p/n DBXF4110D2R)
|
|
|
BoraXEVB carrier board | |
|
AC/DC Single Output Wall Mount adapter Output: +12V – 2.0 A |
|
|
microSDHC card with SD adapter and USB adapter |
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]
This chapter describes how to quickly start working with the BXELK kit. The following paragraphs will guide you through the setup and installation procedures.
Kit registration[edit | edit source]
 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 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 here.
Target setup and first boot[edit | edit source]
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.
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.
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 mmcblk0p2 partition of the 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.
TBD
[1] bootscript is used to do this task.
[2] This root file system has been generated by Yocto build system.
[3] The microSD card is bootable itself, as explained here.
Host setup and target software development[edit | edit source]
Please refer to this page.
Target configuration for the development stage (net_nfs)[edit | edit source]
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 here.
In DAVE Embedded Systems development kits, this configuration is generally denoted as net_nfs. 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).
Target configuration for standalone boot[edit | edit source]
Please refer to this page.
Recovery procedure[edit | edit source]
In case the target is not able to boot from NOR flash for any reason, this recovery procedure can be use to boot from microSD card.
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.
