Bureaucrats, dave_user, Administrators
8,154
edits
Changes
→Kit registration
{{Applies To Bora}}
{{Applies To BoraX}}
{{Applies To BoraLite}}
{{InfoBoxBottom}}
{{ImportantMessage|text='''Customers are strongly recommended to register their kits'''. Registration grants access to reserved material such as source code and additional documentation.
To register the kit, please send an email to [mailto:support-borahelpdesk@dave.eu support-borahelpdesk@dave.eu], [[Development_Kits_Identification_Codes|providing the kit P/N and S/N]].
If you also wish to access git repositories containing source code, please follow the procedure described [[Accessing_DAVE_Embedded_Systems_restricted_git_repositories|here]].}}
[[File:BoraEVB-first-boot.jpg|thumb|center|600px|BELK target setup for first boot]][[File:BoraX-BoraXEVB-1st-boot.jpg|thumb|center|600px|BXELK Bora+BoraEVB target setup for first boot]]
[[File:BoraX-BoraXEVB-1st-boot.jpg|thumb|center|600px|BoraX+BoraXEVB target setup for first boot]] <span id="BoraX-BoraXEVB-Lite"></span>[[File:BoraXEVB-BoraLite.jpg|thumb|center|600px|Bora Lite+Adapter+BoraXEVB 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 Bora/BoraX /BORA Lite 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.
===Target configuration for the development stage (<code>net_nfs</code>)===
{{ImportantMessage|text=The default BELK/BXELK Virtual Machine network configuration is using NAT: this allows to accessing external network (i.e. Internet) using the host computer's networking connection.
For software development using <code>net_nfs</code> with tftp/nfs protocols, please configure your VM network interface in ''Bridge mode'' (see below)}}
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]].An example of ''Bridge mode'' configuration can be found [[Booting_the_system_via_NFS_(DIVELK) | 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.
===Target configuration for standalone boot===
Please refer to [[Standalone_boot_(BELK/BXELK)|this page]].
===Recovery procedure===
In case the target is not able to boot from NOR or NAND flash for any reason, this [[System_boot_and_recovery_via_microSD_card_(BELK/BXELK)|recovery procedure]] can be use to boot from microSD card.
