Changes

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. == History =={| class="wikitable" border="1"!Version!Date!BELK/BXELK version!Notes|-|{{oldid|8547|1.0.0}}|Apr 2019|[[BELK/BXELK_software_components#BELK_3.0.2_.2F_BXELK_1.0.1|3.0.0]]|BELK 3.0.0|-|2.0.0|Jan 2020|[[BELK/BXELK_software_components#BELK_4.1.0|4.1.0]]|Updated for BELK/BXELK 4.1.0|-|} 

! 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> ||

TBD ({{ImportantMessage|text=NOR and NAND flash memories cannot be used accessed at the same time because they shares some Zynq pins. In U-boot the switching between accesses to NOR and NAND is automatically done by U-boot itself. By default in kernel only NAND flash can be accessed. For NOR support in Linux)kernel please contact [mailto:support-bora@dave.eu technical support].}}

Generally speaking, NAND flash memory is partitons partitions are defined in using the devitetreekernel command line:

partition@nand-partition-table { label = "nand-SPL"; reg = <0x0 0x80000Bora>; };pri mtdparts partition@nand-uboot { label mtdparts= "nand-uboot"; reg mtdparts= <0x80000 0x80000>; }; partition@nandpl35x-uboot-env1 { label = "nand-:256K(spl),768K(uboot-),256K(env1"; reg = <0x100000 0x40000>; }; partition@nand-uboot-env2 { label = "nand-uboot-),256K(env2"; reg = <0x140000 0x40000>; }; partition@nand),6M(fpga),512K(fdt),8M(kernel),-bitstream { label = "(nand-bitstream";ubi) reg = <0x180000 0x440000Bora>; }; partition@nand-device-tree { label = "nand-device-tree"; reg = <0x5C0000 0x40000>; }; partition@nand-linux { label = "nand-linux"; reg = <0x600000 0x400000>; }; partition@nand-rootfs { label = "nand-rootfs"; reg = <0xA00000 0x1F600000>; };

defines these adding <code>addmisc</code> to the <code>bootargs</code> parameters list. The kernel ''dmesg'' will configure the NAND partitionsin the following way: <pre>[ 1.148350] Creating 8 MTD partitions on "pl35x-nand":[ 1.153486] 0x000000000000-0x000000040000 : "spl"[ 1.170502] 0x000000040000-0x000000100000 : "uboot"[ 1.186404] 0x000000100000-0x000000140000 : "env1"[ 1.202301] 0x000000140000-0x000000180000 : "env2"[ 1.218170] 0x000000180000-0x000000780000 : "fpga"[ 1.229456] 0x000000780000-0x000000800000 : "fdt"[ 1.237981] 0x000000800000-0x000001000000 : "kernel"[ 1.244063] 0x000001000000-0x000040000000 : "nand-ubi"</pre> 

mtd0: 00080000 00040000 00020000 "nand-SPLspl"mtd1: 00080000 000c0000 00020000 "nand-uboot"mtd2: 00040000 00020000 "nand-uboot-env1"mtd3: 00040000 00020000 "nand-uboot-env2"mtd4: 00440000 00600000 00020000 "nand-bitstreamfpga"mtd5: 00040000 00080000 00020000 "nand-device-treefdt"mtd6: 00400000 00800000 00020000 "nand-linuxkernel"mtd7: 1f600000 3f000000 00020000 "nand-rootfsubi"

The following examples shows how to configure Bora/BoraEVB or BoraX and /BoraXEVB to act as a mass storage device.

Last, BoraEVB (or BoraXEVB ) is connected to a Linux PC with a USB cable like this one:

On PC side, BoraEVB (or BoraXEVB ) is detected as a common USB mass storage device. ==CAN== See [[BoraXEVB#CAN_-_J24 | CAN Pinout]] page and [[Creating_and_building_example_Vivado_project_(BELK/BXELK) | BXELK Vivado project]] for more details. {| class="wikitable"|-! Physical device !! Processor's resource !! Connector !! Type !! Notes|-| CAN BUS || can0 || J24 || differential CAN bus |||-|} The following commands can be issued from command line in order to send and receive CAN frames:<pre>root@bora:~# dmesg | grep -i can[ 0.643798] CAN device driver interface[ 0.997787] can: controller area network core (rev 20120528 abi 9)[ 1.008392] can: raw protocol (rev 20120528)[ 1.012661] can: broadcast manager protocol (rev 20120528 t)[ 1.018294] can: netlink gateway (rev 20130117) max_hops=1root@bora:~# canconfig can0 stopcan0 state: STOPPEDroot@bora:~# canconfig can0 bitrate 500000can0 bitrate: 500000, sample-point: 0.875root@bora:~# canconfig can0 startcan0 state: ERROR-ACTIVEroot@bora:~# cansend can0 -i 0x77 0x33 0x88 0x33 0x88 0x33 0x88 0x33interface = can0, family = 29, type = 3, proto = 1root@bora:~# cansend can0 -i 0x77 0x33 0x88 0x33 0x88 0x33 0x88 0x33interface = can0, family = 29, type = 3, proto = 1root@bora:~# cansend can0 -i 0x77 0x33 0x88 0x33 0x88 0x33 0x88 0x33interface = can0, family = 29, type = 3, proto = 1root@bora:~# candump can0interface = can0, family = 29, type = 3, proto = 1<0x100> [8] 12 34 56 78 9a bc de ff<0x100> [8] 12 34 56 78 9a bc de ff<0x100> [8] 12 34 56 78 9a bc de ff<0x100> [8] 12 34 56 78 9a bc de ff<0x100> [8] 12 34 56 78 9a bc de ff^Croot@bora:~#</pre> ---- In case <code>canutils</code> package is missing, user can install it directly from DAVE's [http://yocto.dave.eu/belk-latest/ BORA package server] using <code>smart update && smart install canutils</code> commands:  <pre>root@bora:~# smart updateUpdating cache... ######################################## [100%] Fetching information for 'all'...-> https://yocto.dave.eu/belk-3.0.1/all/repodata/repomd.xmlrepomd.xml ######################################## [ 50%][snip]Channels have 393 new packages.Saving cache... root@bora:~# smart install canutilsLoading cache...Updating cache... ######################################## [100%] Computing transaction... Installing packages (2): canutils-4.0.6-r0@armv7a_vfp_neon libsocketcan2-0.0.9-r0@armv7a_vfp_neon 27.8kB of package files are needed. 46.8kB will be used. Confirm changes? (Y/n): y [..snip..]</pre> See [[Advanced_use_of_Yocto_build_system_(BELK/BXELK)]] for more information about using Yocto packages and <code>smart</code> ==UART0==UART0 is a spare UART device available on the JP17 PMOD connector. This device is routed through the PL.See [[Creating_and_building_example_Vivado_project_(BELK/BXELK) | BXELK Vivado project]] for more details. {| class="wikitable"|-! Physical device !! Processor's resource !! Connector !! Type !! Linux device file !! Notes|-| UART0 || UART0 || JP17 || 2-wire LVTTL UART || <code>/dev/ttyPS1</code> |||-|} == Temperature sensors ==Bora SOM has a [http://www.ti.com/lit/ds/symlink/tmp422.pdf TMP421AIDCN] temperature sensor onboard. The following commands can be issued from command line in order to get the SOM temperatue:* read the PCB temperature<pre>root@bora:~# cat /sys/devices/soc0/amba/e0004000.i2c/i2c-0/0-004f/hwmon/hwmon1/temp1_input</pre>the returned value has to be divided by 1000 for a °C temperature* read the CPU temperature<pre>root@bora:~# cat /sys/devices/soc0/amba/e0004000.i2c/i2c-0/0-004f/hwmon/hwmon1/temp2_input</pre>the returned value has to be divided by 1000 for a °C temperature Moreover, the SOC has an internal temperature sensor device which can be read using the following shell script:<pre>root@bora:~# cat temp.sh#!/bin/sh # TcpuTEMP_RAW=`cat /sys/devices/soc0/amba/f8007100.adc/iio:device0/in_temp0_raw`TEMP_OFFSET=`cat /sys/devices/soc0/amba/f8007100.adc/iio:device0/in_temp0_offset`TEMP_SCALE=`cat /sys/devices/soc0/amba/f8007100.adc/iio:device0/in_temp0_scale`TEMP=`awk "BEGIN {print (($TEMP_RAW+$TEMP_OFFSET)*$TEMP_SCALE)/1000}"` echo "Cpu Temp: ${TEMP}"</pre>