Bureaucrats, dave_user, Administrators
8,157
edits
Changes
→Target setup and first boot
{{Applies To Bora}}
{{Applies To BoraX}}
{{Applies To BoraLite}}
{{InfoBoxBottom}}
[[File:BoraEVB-first-boot.jpg|thumb|center|600px|BELK target setup for first boot]]
[[File:BoraX-BoraXEVB-1st-boot.jpg|thumb|center|600px|BXELK target setup for first boot]]
[[File:BoraX-BoraXEVB-Lite-1st-boot.jpg|thumb|center|600px|BXELK BORA Lite 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 DIVELK 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)}}
