Bureaucrats, dave_user, Administrators
4,650
edits
Changes
no edit summary
{{InfoBoxTop}}
{{Applies To Bora}}
{{Applies To BoraX}}
{{InfoBoxBottom}}
This article details how physical devices are handled by the Linux kernel in the context of the [[Bora_Embedded_Linux_Kit_(BELK)|BELK]] and [[BoraX_Embedded_Linux_Kit_(BXELK)|BXELK kit]]kits.
==Console UART==
{| class="wikitable"
|-
! Kit !! Physical device !! Processor's resource !! Connector !! Type !! Linux device file !! Notes
|-
| BELK || Boot Console || UART1 || J17 || 2-wire RS232 UART || <code>/dev/ttyPS0</code> |||-| BXELK || Boot Console || UART1 || J17 || 2-wire RS232 UART || <code>/dev/ttyPS0</code> ||
|-
|}
[1] This type of cables forces the ID signal of the USB port to be connected to ground, selecting the host mode on SBC Lynx side.
===Device mode===
The following examples shows how to configure Bora/BoraEVB or BoraX and /BoraXEVB to act as a mass storage device.
First, a local file named <code>mass</code> is created to emulate a mass storage disk that is populated with a file named <code>file.txt</code>:
[ 209.099572] zynq-udc: bind to driver g_mass_storage
</pre>
Last, BoraEVB (or BoraXEVB ) is connected to a Linux PC with a USB cable like this one:
[[File:USB-cable-micro-host-a.png|thumb|center|400px|USB cable used to connect BoraXEVB to PC]]
On PC side, BoraEVB (or BoraXEVB ) is detected as a common USB mass storage device.
==CAN==
----
In case <code>canutils </code> package is missing, user can install it directly from [[TODO|BORA package server]] using <code>smart update && smart install canutils</code> commands:
