Wiki-DB - User contributions [en]

DHCOR STM32MP1 Linux

2022-02-22T10:43:48Z

Mschmoeller: /* Activating Device Tree Overlays */

== U-Boot Bootloader Commands ==

=== Activating Device Tree Overlays ===
:Some of the hardware features can be activated with the help of a device tree overlay. To activate a device tree overlay, you have to go into the U-Boot console first. This can be done during the first seconds after startup, by simply hitting any button on a keyboard once the system tells you to do so.

:When you are in the bootloder, you can view a list of all available device tree overlays with the following command.
:{| class="wikitable" align="center" | style="color: #000000; background: #FFFFFF;" valign="top" |
|<tt>''> ls mmc 0:4 /boot </tt>
|}

:After that, you can select a device tree overlay with the following commands:

:To activate CAN support:
:{| class="wikitable" align="center" | style="color: #000000; background: #FFFFFF;" valign="top" |
|<tt>''> setenv loaddtos '#conf-stm32mp157a-avenger96.dtb#conf-stm32mp15xx-avenger96-overlay-fdcan1-x6.dtbo#conf-stm32mp157a-avenger96-overlay-fdcan2-x6.dtbo' </tt>
|}

:To activate the 96Boards D3Camera Mezzanine Board enter:
:{| class="wikitable" align="center" | style="color: #000000; background: #FFFFFF;" valign="top" |
|<tt>''> setenv loaddtos '#conf-stm32mp157a-avenger96.dtb#conf-stm32mp15xx-avenger96-overlay-ov5640-x7.dtbo' </tt>
|}

:If you want to make use of the MIPI DSI interface, you can start with an MIPI DSI interface board developed by DH electronics. If you want to use it, simply contact us to find out more about it.
:To activate the MIPI DSI Interface enter the following device tree overlay.
:{| class="wikitable" align="center" | style="color: #000000; background: #FFFFFF;" valign="top" |
|<tt>''> setenv loaddtos '#conf-stm32mp157a-avenger96.dtb#conf-stm32mp15xx-avenger96-overlay-644-100-x6-otm8009a.dtbo' </tt>
|}

:If you want to save your settings, so that you don't have to enter the device tree overlay after every reboot, enter this command:
:{| class="wikitable" align="center" | style="color: #000000; background: #FFFFFF;" valign="top" |
|<tt>''> saveenv </tt>
|}

:To reset your device tree overlay, simply override the last settings:
:{| class="wikitable" align="center" | style="color: #000000; background: #FFFFFF;" valign="top" |
|<tt>''> setenv loaddtos '#conf-stm32mp157a-avenger96.dtb' </tt>
|}

:Once the device tree overlay is set, you can boot up your board by entering boot:
:{| class="wikitable" align="center" | style="color: #000000; background: #FFFFFF;" valign="top" |
|<tt>''> boot </tt>
|}

== Linux Userspace Commands ==

=== Logging in after Startup ===
:After booting, you con login as the user "root" without any password. Note, that the standard console is connected to the UART 1 port (96Boards name).
:{| class="wikitable" align="center" | style="color: #000000; background: #FFFFFF;" valign="top" |
|<tt>dh-stm32mp1-dhcor-avenger96 login: '''root'''</tt>
|}

=== Interacting with GPIOs ===
:An GPIO can be activated with the gpioset command. To find out which GPIO is connected to what gpiochip-device, take a look at the Hardware Section below.
:The GPIO "A" can be turned on by
:{| class="wikitable" align="center" | style="color: #000000; background: #FFFFFF;" valign="top" |
|<tt>''# gpioset gpiochip0 14=1</tt>
|}

:and off by
:{| class="wikitable" align="center" | style="color: #000000; background: #FFFFFF;" valign="top" |
|<tt>''# gpioset gpiochip0 14=0</tt>
|}

=== Interacting with the User LEDs ===
:In between the two USB-Host connectors of the Avenger96, you can find four so called User LEDs. These LEDs can be used for simple programming examples and be accessed and manipulated by the user form the userspace.
:The LEDs are located under /sys/class/leds.
:To disable the blinking of the LED0 hit following command:
:{| class="wikitable" align="center" | style="color: #000000; background: #FFFFFF;" valign="top" |
|<tt>''# echo none > /sys/class/leds/green:user0/trigger</tt>
|}

:The LEDs can also be turned on or off permanently by writing either "1" or "0" to the following file:
:{| class="wikitable" align="center" | style="color: #000000; background: #FFFFFF;" valign="top" |
|<tt>''# echo 1 > /sys/class/leds/green:user0/brightness</tt>
|}

:{| class="wikitable" align="center" | style="color: #000000; background: #FFFFFF;" valign="top" |
|<tt>''# echo 0 > /sys/class/leds/green:user0/brightness</tt>
|}

=== Accessing Devices over I2C ===
:Once you have connected some I2C devices to the Avenger96, you can scan the I2C bus and see if your device is available.
:To scan for devices on the I2C-Bus 1 enter the following command:
:{| class="wikitable" align="center" | style="color: #000000; background: #FFFFFF;" valign="top" |
|<tt>''# i2cdetect -y 1 </tt>
|}

:To write on the device on the address 0x50 to its register number 0x10 the value 0x20 enter the following command:
:{| class="wikitable" align="center" | style="color: #000000; background: #FFFFFF;" valign="top" |
|<tt>''# i2cset -y 1 0x50 0x10 0x20 </tt>
|}

:To read the data of the device on the address 0x50 at its register 0x10 enter this:
:{| class="wikitable" align="center" | style="color: #000000; background: #FFFFFF;" valign="top" |
|<tt>''# i2cget -y 1 0x50 0x10 </tt>
|}

:For a dump of the entire registers of the device at address 0x50 enter the following command:
:{| class="wikitable" align="center" | style="color: #000000; background: #FFFFFF;" valign="top" |
|<tt>''# i2cdump -f 1 0x50 </tt>
|}

=== Unsing the internal RTC ===
:Read out the current date and time of the system (not the RTC itself)
:{| class="wikitable" align="center" | style="color: #000000; background: #FFFFFF;" valign="top" |
|<tt>''# date</tt>
|}

:Set a specific system time
:{| class="wikitable" align="center" | style="color: #000000; background: #FFFFFF;" valign="top" |
|<tt>''# date -s "2020-01-30 10:00:00"</tt>
|}

:Save the current system time to the RTC of the STM32MP1
:{| class="wikitable" align="center" | style="color: #000000; background: #FFFFFF;" valign="top" |
|<tt>''# hwclock -w</tt>
|}

:When you allready have stored a date on the RTC and you want to read it out, use the next command. This command only gives back the time, but does not synchronize it with the system time. This is done in the next step.
:{| class="wikitable" align="center" | style="color: #000000; background: #FFFFFF;" valign="top" |
|<tt>''# hwclock -r</tt>
|}

:The system time can be synchronised to the RTC by this command:
:{| class="wikitable" align="center" | style="color: #000000; background: #FFFFFF;" valign="top" |
|<tt>''# hwclock -s</tt>
|}

=== Using the second UART port ===
:If you want to use the second UART Port available on the Low Speed Expansion Connector of the Avenger96, you can access it easily with the tool called minicom
:To open up its configuration enter the following command
:{| class="wikitable" align="center" | style="color: #000000; background: #FFFFFF;" valign="top" |
|<tt>''# minicom -s</tt>
|}

:Once you've opend minicom, navigate to ''<tt>Serial port setup</tt>'' and change the Serial Device to ''<tt>/dev/ttySTM1</tt>''.
:Now you can hit ''<tt>exit</tt>'' and you are in a terminal which is connected to the second UART port.

:To reopen the settings of minicom press ''<tt>CTRL + A</tt>'' and then ''<tt>O</tt>'' on your keyboard.
:To close minicom press ''<tt>CTRL + A</tt>'' and then ''<tt>X</tt>'' on your keyboard.

=== Connecting to a WiFi network ===
:After bootup, you have to enter the following commands:

:activating the wlan0 interface
:{| class="wikitable" align="center" | style="color: #000000; background: #FFFFFF;" valign="top" |
|<tt>''# ifconfig wlan0 up</tt>
|}

:Enter the SSID and the WPA Key
:{| class="wikitable" align="center" | style="color: #000000; background: #FFFFFF;" valign="top" |
|<tt>''# wpa_passphrase "YOUR SSID" your-wpa-key > wpa_supplicant.conf </tt>
|}

:Defining the settings
:{| class="wikitable" align="center" | style="color: #000000; background: #FFFFFF;" valign="top" |
|<tt>''# wpa_supplicant -B -Dnl8011 -iwlan0 -cwpa_supplicant.conf </tt>
|}

:After that you should get the message "successfully initialized wpa_supplicant"

:Requesting an IP-Address from the DHCP-Server
:{| class="wikitable" align="center" | style="color: #000000; background: #FFFFFF;" valign="top" |
|<tt>''# udhcpc -i wlan0 </tt>
|}

:Checking your IP Address
:{| class="wikitable" align="center" | style="color: #000000; background: #FFFFFF;" valign="top" |
|<tt>''# ifconfig </tt>
|}

=== Connecting to a Bluetooth Device ===
:In this example you can see how to connect a bluetooth headset to the Avenger96 and play a song over it.
:For this you have to first store a *.wav audiofile in the home directory (/home/root).

:First start pulsaudio
:{| class="wikitable" align="center" | style="color: #000000; background: #FFFFFF;" valign="top" |
|<tt>''# pulseaudio --start</tt>
|}

:Bring up the Bluetooth Device
:{| class="wikitable" align="center" | style="color: #000000; background: #FFFFFF;" valign="top" |
|<tt>''# hciconfig hci0 up</tt>
|}

:Start the Bluetooth configuration tool
:{| class="wikitable" align="center" | style="color: #000000; background: #FFFFFF;" valign="top" |
|<tt>''# bluetoothctl</tt>
|}

:Now you are controlling the configuration tool. Here you can start the scanning for bluetooth devices
:{| class="wikitable" align="center" | style="color: #000000; background: #FFFFFF;" valign="top" |
|<tt>''[bluetooth]# scan on</tt>
|}

:Once you see the device you like to connect to stop the scanning.
:{| class="wikitable" align="center" | style="color: #000000; background: #FFFFFF;" valign="top" |
|<tt>''[bluetooth]# scan off</tt>
|}

:Now Copy the MAC-address of your bluetooth device and pair to it
:{| class="wikitable" align="center" | style="color: #000000; background: #FFFFFF;" valign="top" |
|<tt>''[bluetooth]# pair xx:xx:xx:xx:xx:xx</tt>
|}

:Next add it to the list of trusted devices
:{| class="wikitable" align="center" | style="color: #000000; background: #FFFFFF;" valign="top" |
|<tt>''[bluetooth]# trust xx:xx:xx:xx:xx:xx</tt>
|}

:Finally connect to it
:{| class="wikitable" align="center" | style="color: #000000; background: #FFFFFF;" valign="top" |
|<tt>''[bluetooth]# connect xx:xx:xx:xx:xx:xx</tt>
|}

:Your Headphone should now be connected to the Avenger96, so you can leave the bluetooth configuration tool
:{| class="wikitable" align="center" | style="color: #000000; background: #FFFFFF;" valign="top" |
|<tt>''[bluetooth]# exit</tt>
|}

:Now you can start playing your audiofile
:{| class="wikitable" align="center" | style="color: #000000; background: #FFFFFF;" valign="top" |
|<tt>''# aplay audiofile.wav</tt>
|}

:When you want to remove your device from the Avenger96, open ''<tt>bluetoothctl</tt>'' again and remove its MAC-address
:{| class="wikitable" align="center" | style="color: #000000; background: #FFFFFF;" valign="top" |
|<tt>''[bluetooth]# remove xx:xx:xx:xx:xx:xx</tt>
|}

=== Activating the CAN interface ===
:The Avenger96 has two CAN FD ports which can be accessed from the GPIOs on the Low Speed Expansion Connector:
::FDCAN 1:
:::PA12 - TX
:::PA11 - RX

::FDCAN 2:
:::PB13 - TX
:::PB5 - RX

:To activate them, you have to add a Device Tree Overlay in the bootloader, like mentioned in the beginning of this page.
:Once this is done, you have to connect a CAN-Transceiver to the GPIOs and from here you can access the CAN-Bus.

:Setup CAN interface with baudrate 500kbit/sec.
:{| class="wikitable" align="center" | style="color: #000000; background: #FFFFFF;" valign="top" |
|<tt>''# ip link set can0 up type can bitrate 500000</tt>
|}

:Start to listen on CAN port
:{| class="wikitable" align="center" | style="color: #000000; background: #FFFFFF;" valign="top" |
|<tt>''# candump can0</tt>
|}

:Send test message
:{| class="wikitable" align="center" | style="color: #000000; background: #FFFFFF;" valign="top" |
|<tt>''# cansend can0 100#11.2233.44556677.88</tt>
|}

:Deinitialize CAN port
:{| class="wikitable" align="center" | style="color: #000000; background: #FFFFFF;" valign="top" |
|<tt>''# ip link set can0 down</tt>
|}

=== Activating the MIPI CSI Interface ===
:The Avenger96 is compatible with the [https://www.96boards.org/product/d3camera/ D3Camera Mezzanine Board] available on the 96Boards website.

:To activate this Mezzanine Board you have to connect it to the Avenger96 before you power it up. Note, that you also have to access the UART0 which is then available on the Solderpins of the D3Camera Mezzanine board.
:Like for CAN you also have to activate the proper device tree overlay as describte in the beginning of this page.

:Once the system is booted, you have to connect a display to the Avenger96 via HDMI and then enter the following command.
:{| class="wikitable" align="center" | style="color: #000000; background: #FFFFFF;" valign="top" |
|<tt>''# XDG_RUNTIME_DIR=/var/run/user/0/ gst-launch-1.0 v4l2src device=/dev/video0 ! video/x-raw,width=1280,height=720,pixelformat=RGB565 ! waylandsink</tt>
|}

=== Mounting a USB Drive ===
:To mount a USB drive connect it to the Avenger96 and mount it with the following command
:{| class="wikitable" align="center" | style="color: #000000; background: #FFFFFF;" valign="top" |
|<tt>''# mount /dev/sda1 /mnt</tt>
|}

:Now your USB drive is available under the following directory
:{| class="wikitable" align="center" | style="color: #000000; background: #FFFFFF;" valign="top" |
|<tt>''# cd /mnt</tt>
|}

:To unmount the drive enter the following command
:{| class="wikitable" align="center" | style="color: #000000; background: #FFFFFF;" valign="top" |
|<tt>''# umount /dev/sda1 </tt>
|}

=== Formatting and mounting the eMMC ===
:At first you can check all block devices by this command
:{| class="wikitable" align="center" | style="color: #000000; background: #FFFFFF;" valign="top" |
|<tt>''# lsblk</tt>
|}

:First partitionate the eMMC device
:{| class="wikitable" align="center" | style="color: #000000; background: #FFFFFF;" valign="top" |
|<tt>''# cfdisk /dev/mmcblk2</tt>
|}

:Now select the partitiontable ''<tt>gpt</tt>''. Then in the menu you can add a new partiton by entering ''<tt>new</tt>'' and then the size of your partition e.g. ''<tt>7G</tt>''.
:After that enter ''<tt>write</tt>'' and confirm it with ''<tt>yes</tt>''. Then you can ''<tt>quit</tt>'' this tool.

:Now you can format the new partition
:{| class="wikitable" align="center" | style="color: #000000; background: #FFFFFF;" valign="top" |
|<tt>''# mkfs.ext4 /dev/mmcblk2p1</tt>
|}

:To access this partition you have to mount it just like an USB-Stick
:{| class="wikitable" align="center" | style="color: #000000; background: #FFFFFF;" valign="top" |
|<tt>''# mount /dev/mmcblk2p1 /mnt</tt>
|}

=== Read out the ADC Pins ===
:The GPIOs G and H are mapped as ADC pins. These pins can meassure a value from 0 V to 2,9 V. This reference voltage of 2,9 V is driven by the LDO1 of the PMIC.
:The value measured is calculated as followed:
::''<tt>Umeassured = ( RAW + OFFSET ) * SCALE</tt>''

:You can read out the values as followed:

:'''GPIO G:'''
:Navigate to its directory
:{| class="wikitable" align="center" | style="color: #000000; background: #FFFFFF;" valign="top" |
|<tt>''# cd /sys/bus/iio/devices/iio:device0</tt>
|}

:Read out ''<tt>SCALE</tt>''
:{| class="wikitable" align="center" | style="color: #000000; background: #FFFFFF;" valign="top" |
|<tt>''# cat in_voltage_scale</tt>
|}

:Read out ''<tt>OFFSET</tt>''
:{| class="wikitable" align="center" | style="color: #000000; background: #FFFFFF;" valign="top" |
|<tt>''# cat in_voltage_offset</tt>
|}

:Once you know these two values, you can read the actual ADC value
:{| class="wikitable" align="center" | style="color: #000000; background: #FFFFFF;" valign="top" |
|<tt>''# cat in_voltage6_raw</tt>
|}

:'''GPIO H:'''
:Navigate to its directory
:{| class="wikitable" align="center" | style="color: #000000; background: #FFFFFF;" valign="top" |
|<tt>''# cd /sys/bus/iio/devices/iio:device1</tt>
|}

:Read out ''<tt>SCALE</tt>''
:{| class="wikitable" align="center" | style="color: #000000; background: #FFFFFF;" valign="top" |
|<tt>''# cat in_voltage_scale</tt>
|}

:Read out ''<tt>OFFSET</tt>''
:{| class="wikitable" align="center" | style="color: #000000; background: #FFFFFF;" valign="top" |
|<tt>''# cat in_voltage_offset</tt>
|}

:Once you know these two values, you can read the actual ADC value
:{| class="wikitable" align="center" | style="color: #000000; background: #FFFFFF;" valign="top" |
|<tt>''# cat in_voltage2_raw</tt>
|}

== Kernel Userspace Interfaces to Access Hardware ==
The pinmuxing of the DHCOR STM32MP1 can be configured just as needed by you as a customer and therefore the interfaces used in each configuration might be different. However, to give you an easy way to start developing with the DHCOR STM32MP1 you can use the Avenger96 Board, which is the reference design for our DHCOR module. Thus, the interfaces described here, are the configuration for the Avenger96.

=== Serial (UART) Interfaces ===
:{| class="wikitable"
! style="background-color:#efefef; width: 200px; text-align:left" | 96Boards Name
! style="background-color:#efefef; width: 200px; text-align:left" | Linux Name
! style="background-color:#efefef; width: 200px; text-align:left" | Hardware Name
|-
| UART 0
| <tt>/dev/ttySTM1</tt>
| UART 7
|-
| UART 1 (Standard UART)
| <tt>/dev/ttySTM0</tt>
| UART 4
|}

=== I²C Interfaces ===
:{| class="wikitable"
! style="background-color:#efefef; width: 200px; text-align:left" | 96Boards Name
! style="background-color:#efefef; width: 200px; text-align:left" | Linux Name
! style="background-color:#efefef; width: 200px; text-align:left" | Hardware Name
|-
| I2C0
| <tt>/dev/i2c-1</tt>
| I2C2
|-
| I2C1
| <tt>/dev/i2c-0</tt>
| I2C1
|-
| OnBoard
| <tt>/dev/i2c-2</tt>
| I2C4
|}

=== microSD and eMMC ===
:{| class="wikitable"
! style="background-color:#efefef; width: 200px; text-align:left" | 96Boards Name
! style="background-color:#efefef; width: 200px; text-align:left" | Linux Name
! style="background-color:#efefef; width: 200px; text-align:left" | Hardware Name
|-
| microSD
| <tt>mmcblk1</tt>
| SDMMC1
|-
| eMMC
| <tt>mmcblk2</tt>
| SDMMC2
|}

=== GPIOs ===
:{| class="wikitable"
! style="background-color:#efefef; width: 200px; text-align:left" | 96Boards Name
! style="background-color:#efefef; width: 200px; text-align:left" | Linux Name
! style="background-color:#efefef; width: 200px; text-align:left" | Hardware Name
|-
| A
| <tt>gpiochip0 14</tt>
| PA14
|-
| B
| <tt>gpiochip1 11</tt>
| PB11
|-
| C
| <tt>gpiochip2 3</tt>
| PC3
|-
| D
| <tt>gpiochip3 8</tt>
| PD8
|-
| E
| <tt>gpiochip3 14</tt>
| PD14
|-
| F
| <tt>gpiochip3 15</tt>
| PD15
|-
| G (mapped as ADC)
| <tt>gpiochip5 12</tt>
| PF12
|-
| H (mapped as ADC)
| <tt>gpiochip5 13</tt>
| PF13
|-
| I
| <tt>gpiochip0 12</tt>
| PA12
|-
| J
| <tt>gpiochip1 5</tt>
| PB5
|-
| K
| <tt>gpiochip0 11</tt>
| PA11
|-
| L
| <tt>gpiochip1 13</tt>
| PB13
|}

:Beside the GPIOs, the Avenger96 has also four user LEDs, which are controlled the same way as the GPIOs.
:{| class="wikitable"
! style="background-color:#efefef; width: 200px; text-align:left" | 96Boards Name
! style="background-color:#efefef; width: 200px; text-align:left" | Linux Name
! style="background-color:#efefef; width: 200px; text-align:left" | Hardware Name
|-
| LED 0
| <tt>/sys/class/leds/green:user0</tt>
| PZ7
|-
| LED 1
| <tt>/sys/class/leds/green:user1</tt>
| PF3
|-
| LED 2
| <tt>/sys/class/leds/green:user2</tt>
| PG0
|-
| LED 3
| <tt>/sys/class/leds/green:user3</tt>
| PG1
|}

== Linux Kernel ==



=== How to build a Kernel ===
{| class="wikitable" align="center" | style="width: 98%; background: #f3f3f3;" valign="top" |
|
Get sources from Github
{| class="wikitable" style="width: 100%; color: #000000; background: #ffffff;" |
|
1. Start the Console on Linux 
2. <tt>''git clone https://github.com/dh-electronics/linux-stm32mp1.git --branch dev/5.4.69_dhsom''</tt> 
3. <tt>''cd linux-stm32mp1''</tt>
|}
Configure and build the Device Tree + Kernel
{| class="wikitable" style="width: 100%; color: #000000; background: #ffffff;" |
|
4. <tt>''ARCH=arm CROSS_COMPILE=/opt/gcc-arm-8.3-2019.03-x86_64-arm-linux-gnueabihf/bin/arm-linux-gnueabihf- make stm32mp1_dhsom_defconfig''</tt> 
5. <tt>''ARCH=arm CROSS_COMPILE=/opt/gcc-arm-8.3-2019.03-x86_64-arm-linux-gnueabihf/bin/arm-linux-gnueabihf- make menuconfig''</tt> (optional: If you want to add/remove Kernel features) 
6. <tt>''ARCH=arm CROSS_COMPILE=/opt/gcc-arm-8.3-2019.03-x86_64-arm-linux-gnueabihf/bin/arm-linux-gnueabihf- make dtbs''</tt> 
7. <tt>''ARCH=arm CROSS_COMPILE=/opt/gcc-arm-8.3-2019.03-x86_64-arm-linux-gnueabihf/bin/arm-linux-gnueabihf- make zImage</tt>
|}
Create the FIT-image with our script ([[media:Dh-create-fitimage_1.0_all.deb|Download link]])
{| class="wikitable" style="width: 100%; color: #000000; background: #ffffff;" |
|-
| '''Interactive mode for selecting device trees'''
| '''Device trees are set as parameter'''
|-
|
8. <tt>''create_fitimage''</tt> 
Enter the numbers (space seperated) of the device trees to include (e.g. if you want to include the device tree for the Avenger96 include the number of <tt>''./arch/arm/boot/dts/stm32mp157a-avenger96.dtb''</tt> (usually 1). 
Enter the numbers (space seperated) of the device trees overlays to include (e.g. for the Avenger96 enter the files which contain <tt>''Avenger96''</tt> (usually 0 1 2 3 4 5 6 7).
|
(Example is for the Avenger96) 
8. <tt>''create_fitimage --dtb ./arch/arm/boot/dts/stm32mp157a-avenger96.dtb --dtbo ./arch/arm/boot/dts/stm32mp157a-avenger96-overlay-644-100-x6-otm8009a.dtbo,./arch/arm/boot/dts/stm32mp157a-avenger96-overlay-644-100-x6-rpi7inch.dtbo,./arch/arm/boot/dts/stm32mp157a-avenger96-overlay-fdcan1-x6.dtbo,./arch/arm/boot/dts/stm32mp157a-avenger96-overlay-fdcan2-x6.dtbo,./arch/arm/boot/dts/stm32mp157a-avenger96-overlay-i2c1-eeprom-x6.dtbo,./arch/arm/boot/dts/stm32mp157a-avenger96-overlay-i2c2-eeprom-x6.dtbo,./arch/arm/boot/dts/stm32mp157a-avenger96-overlay-ov5640-x7.dtbo,./arch/arm/boot/dts/stm32mp157a-avenger96-overlay-spi2-eeprom-x6.dtbo''</tt>
|}
|}

Add Yocto SDK with QT5 to QT Creator

2021-10-26T11:59:49Z

Mschmoeller: /* Download and install the SDK package */

The following instructions are based on '''DHCOM STM32MP1''' computer on module and Yocto version "dunfell"
__TOC__

== Prepairing your virtual machine ==

Get the [[Virtual Machine for Application Development]].

Install the following package:

$ sudo apt-get install qtcreator qt5default

== Download and install the SDK package ==

Get the [[media:20211026-dhlinux-glibc-x86_64-dh-image-demo-cortexa7t2hf-neon-vfpv4-toolchain-nodistro.0.zip|QT5 SDK for STM32mp1]]

Unpack the archive and install the toolchain.

$ sh ./dhlinux-glibc-x86_64-meta-toolchain-qt5-cortexa7t2hf-neon-vfpv4-toolchain-nodistro.0.sh

Choose the installation directory (default: /opt/dhlinux/nodistro.0/).

The toolchain is now installed to your system.

== Configure Qt Creator ==

Run QT Creator

In Qt Creator go to Tools > Options > Devices and add your Wandboard as a generic linux device.

[[Image:Qtcreator-add-device.jpg|550px]]

go to Tools > Options > Build & Run and:

Add a new c++ compiler. Select your compiler: /opt/dhlinux/nodistro.0/sysroots/x86_64-oesdk-linux/usr/bin/arm-dhlinux-linux-gnueabi/arm-dhlinux-linux-gnueabi-g++

[[Image:Qtcreator-add-compiler.jpg|850px]]

Add a new debugger. Select your debugger: /opt/dhlinux/nodistro.0/sysroots/x86_64-oesdk-linux/usr/bin/arm-dhlinux-linux-gnueabi/arm-dhlinux-linux-gnueabi-gdb

[[Image:Qtcreator-add-debugger.jpg|850px]]

Add your Qt version by selecting the qmake located in /opt/dhlinux/nodistro.0/sysroots/x86_64-oesdk-linux/usr/bin/qmake

[[Image:Qtcreator-add-qt-version.jpg|850px]]

Add a new kit selecting your new Qt5 version and compiler and setting the sysroot to /opt/dhlinux/nodistro.0/sysroots/cortexa7t2hf-neon-vfpv4-dhlinux-linux-gnueabi and leave the Qt mkspec empty.
Then select your device

[[Image:Qtcreator-add-kit.jpg|850px]]

If there is a warning/error shown, please click apply between each step.

There is one last point. The SDK comes with an environment-setup which sets some variables that are needed if you want to use the toolchain. There are two ways to get this environment into Qt Creator:
* The first way is rather simple: Open a shell and source the environment-setup script (in the example <tt>/opt/dhlinux/nodistro.0/environment-setup-cortexa7t2hf-neon-vfpv4-dhlinux-linux-gnueabi</tt>). After that start Qt Creator in the same shell session. If you want to use another toolchain, you have start a new shell session, source the corresponding environment-setup and start QtCreator from there.
* The other possible way is bit more complicated, but in return it is possible to change the toolchain without restarting Qt Creator: In the settings of the kit there is a button for setting the environment of this kit ("Change"-button right of "Environment"). When this button is pressed, a window for editing text opens. There you can set environment variables by the schema <variable>=<value>, one variable can be set per line. You cannot simply copy the setup script, because at the script the shell is called and other variables are referenced which isn't supported by Qt Creator. It is also possible that the setup script imports additional scripts from the "environment-setup.d" directory of each sysroot. So you have to source the setup script and look what variables have been set and write them and their respective values into the window. If you want to use another toolchain, than you can change the used kit. An example for configuring the environment of a kit is inside the collapsible box.

<div class="toccolours mw-collapsible mw-collapsed" style="overflow:auto;">
<div style="font-weight:bold;">Example for setting the environment variables at the kit</div>
<div class="mw-collapsible-content">

/opt/dhlinux/nodistro.0/environment-setup-cortexa7t2hf-neon-vfpv4-dhlinux-linux-gnueabi:

<tt># Check for LD_LIBRARY_PATH being set, which can break SDK and generally is a bad practice
# http://tldp.org/HOWTO/Program-Library-HOWTO/shared-libraries.html#AEN80
# http://xahlee.info/UnixResource_dir/_/ldpath.html
# Only disable this check if you are absolutely know what you are doing!
if [ ! -z "$LD_LIBRARY_PATH" ]; then
echo "Your environment is misconfigured, you probably need to 'unset LD_LIBRARY_PATH'"
echo "but please check why this was set in the first place and that it's safe to unset."
echo "The SDK will not operate correctly in most cases when LD_LIBRARY_PATH is set."
echo "For more references see:"
echo " http://tldp.org/HOWTO/Program-Library-HOWTO/shared-libraries.html#AEN80"
echo " http://xahlee.info/UnixResource_dir/_/ldpath.html"
return 1
fi
export SDKTARGETSYSROOT=/opt/dhlinux/nodistro.0/sysroots/cortexa7t2hf-neon-vfpv4-dhlinux-linux-gnueabi
export PATH=/opt/dhlinux/nodistro.0/sysroots/x86_64-oesdk-linux/usr/bin:/opt/dhlinux/nodistro.0/sysroots/x86_64-oesdk-linux/usr/sbin:/opt/dhlinux/nodistro.0/sysroots/x86_64-oesdk-linux/bin:/opt/dhlinux/nodistro.0/sysroots/x86_64-oesdk-linux/sbin:/opt/dhlinux/nodistro.0/sysroots/x86_64-oesdk-linux/usr/bin/../x86_64-oesdk-linux/bin:/opt/dhlinux/nodistro.0/sysroots/x86_64-oesdk-linux/usr/bin/arm-dhlinux-linux-gnueabi:/opt/dhlinux/nodistro.0/sysroots/x86_64-oesdk-linux/usr/bin/arm-dhlinux-linux-musl:$PATH
export PKG_CONFIG_SYSROOT_DIR=$SDKTARGETSYSROOT
export PKG_CONFIG_PATH=$SDKTARGETSYSROOT/usr/lib/pkgconfig:$SDKTARGETSYSROOT/usr/share/pkgconfig
export CONFIG_SITE=/opt/dhlinux/nodistro.0/site-config-cortexa7t2hf-neon-vfpv4-dhlinux-linux-gnueabi
export OECORE_NATIVE_SYSROOT="/opt/dhlinux/nodistro.0/sysroots/x86_64-oesdk-linux"
export OECORE_TARGET_SYSROOT="$SDKTARGETSYSROOT"
export OECORE_ACLOCAL_OPTS="-I /opt/dhlinux/nodistro.0/sysroots/x86_64-oesdk-linux/usr/share/aclocal"
export OECORE_BASELIB="lib"
export OECORE_TARGET_ARCH="arm"
export OECORE_TARGET_OS="linux-gnueabi"
unset command_not_found_handle
export CC="arm-dhlinux-linux-gnueabi-gcc -mthumb -mfpu=neon-vfpv4 -mfloat-abi=hard -mcpu=cortex-a7 --sysroot=$SDKTARGETSYSROOT"
export CXX="arm-dhlinux-linux-gnueabi-g++ -mthumb -mfpu=neon-vfpv4 -mfloat-abi=hard -mcpu=cortex-a7 --sysroot=$SDKTARGETSYSROOT"
export CPP="arm-dhlinux-linux-gnueabi-gcc -E -mthumb -mfpu=neon-vfpv4 -mfloat-abi=hard -mcpu=cortex-a7 --sysroot=$SDKTARGETSYSROOT"
export AS="arm-dhlinux-linux-gnueabi-as "
export LD="arm-dhlinux-linux-gnueabi-ld --sysroot=$SDKTARGETSYSROOT"
export GDB=arm-dhlinux-linux-gnueabi-gdb
export STRIP=arm-dhlinux-linux-gnueabi-strip
export RANLIB=arm-dhlinux-linux-gnueabi-ranlib
export OBJCOPY=arm-dhlinux-linux-gnueabi-objcopy
export OBJDUMP=arm-dhlinux-linux-gnueabi-objdump
export READELF=arm-dhlinux-linux-gnueabi-readelf
export AR=arm-dhlinux-linux-gnueabi-ar
export NM=arm-dhlinux-linux-gnueabi-nm
export M4=m4
export TARGET_PREFIX=arm-dhlinux-linux-gnueabi-
export CONFIGURE_FLAGS="--target=arm-dhlinux-linux-gnueabi --host=arm-dhlinux-linux-gnueabi --build=x86_64-linux --with-libtool-sysroot=$SDKTARGETSYSROOT"
export CFLAGS=" -O2 -pipe -g -feliminate-unused-debug-types "
export CXXFLAGS=" -O2 -pipe -g -feliminate-unused-debug-types "
export LDFLAGS="-Wl,-O1 -Wl,--hash-style=gnu -Wl,--as-needed"
export CPPFLAGS=""
export KCFLAGS="--sysroot=$SDKTARGETSYSROOT"
export OECORE_DISTRO_VERSION="0.0.1"
export OECORE_SDK_VERSION="nodistro.0"
export ARCH=arm
export CROSS_COMPILE=arm-dhlinux-linux-gnueabi-
# Append environment subscripts
if [ -d "$OECORE_TARGET_SYSROOT/environment-setup.d" ]; then
for envfile in $OECORE_TARGET_SYSROOT/environment-setup.d/*.sh; do
. $envfile
done
fi
if [ -d "$OECORE_NATIVE_SYSROOT/environment-setup.d" ]; then
for envfile in $OECORE_NATIVE_SYSROOT/environment-setup.d/*.sh; do
. $envfile
done
fi</tt>

There are additional scripts in the "environment-setup.d"-directories of the sysroots which are included at the main setup-script. These scripts have the following content:

/opt/dhlinux/nodistro.0/sysroots/x86_64-oesdk-linux/environment-setup.d/cmake.sh:

<tt>export OE_CMAKE_TOOLCHAIN_FILE="$OECORE_NATIVE_SYSROOT/usr/share/cmake/OEToolchainConfig.cmake"
export OE_CMAKE_FIND_LIBRARY_CUSTOM_LIB_SUFFIX="`echo $OECORE_BASELIB | sed -e s/lib//`"</tt>

/opt/dhlinux/nodistro.0/sysroots/x86_64-oesdk-linux/environment-setup.d/openssl.sh:

<tt>export PATH=$OECORE_NATIVE_SYSROOT/usr/bin:$PATH
export OE_QMAKE_CFLAGS="$CFLAGS"
export OE_QMAKE_CXXFLAGS="$CXXFLAGS"
export OE_QMAKE_LDFLAGS="$LDFLAGS"
export OE_QMAKE_CC="$CC"
export OE_QMAKE_CXX="$CXX"
export OE_QMAKE_LINK="$CXX"
export OE_QMAKE_AR=$AR
export OE_QMAKE_STRIP=$STRIP
export QT_CONF_PATH=$OECORE_NATIVE_SYSROOT/usr/bin/qt.conf
export OE_QMAKE_LIBDIR_QT=`qmake -query QT_INSTALL_LIBS`
export OE_QMAKE_INCDIR_QT=`qmake -query QT_INSTALL_HEADERS`
export OE_QMAKE_MOC=$OECORE_NATIVE_SYSROOT/usr/bin/moc
export OE_QMAKE_UIC=$OECORE_NATIVE_SYSROOT/usr/bin/uic
export OE_QMAKE_RCC=$OECORE_NATIVE_SYSROOT/usr/bin/rcc
export OE_QMAKE_QDBUSCPP2XML=$OECORE_NATIVE_SYSROOT/usr/bin/qdbuscpp2xml
export OE_QMAKE_QDBUSXML2CPP=$OECORE_NATIVE_SYSROOT/usr/bin/qdbusxml2cpp
export OE_QMAKE_QT_CONFIG=`qmake -query QT_INSTALL_LIBS`/mkspecs/qconfig.pri
export OE_QMAKE_PATH_HOST_BINS=$OECORE_NATIVE_SYSROOT/usr/bin
export QMAKESPEC=`qmake -query QT_INSTALL_LIBS`/mkspecs/linux-oe-g++</tt>

/opt/dhlinux/nodistro.0/sysroots/x86_64-oesdk-linux/environment-setup.d/qt5.sh:

<tt>export OPENSSL_CONF="$OECORE_NATIVE_SYSROOT/usr/lib/ssl-1.1/openssl.cnf"</tt>

This results in the following environment configuration:

[[File:Qtcreator-set-environment.png|1000px]]

</div></div>

Add Yocto SDK with QT5 to QT Creator

2021-08-02T13:37:01Z

Mschmoeller: /* Download and install the SDK package */

The following instructions are based on '''DHCOM STM32MP1''' computer on module and Yocto version "dunfell"
__TOC__

== Prepairing your virtual machine ==

Get the [[Virtual Machine for Application Development]].

Install the following package:

$ sudo apt-get install qtcreator qt5default

== Download and install the SDK package ==

Get the [[media:2021-08-02-dhlinux-glibc-x86_64-dh-image-demo-cortexa7t2hf-neon-vfpv4-toolchain-nodistro.0.zip|QT5 SDK for STM32mp1]]

Unpack the archive and install the toolchain.

$ sh ./dhlinux-glibc-x86_64-meta-toolchain-qt5-cortexa7t2hf-neon-vfpv4-toolchain-nodistro.0.sh

Choose the installation directory (default: /opt/dhlinux/nodistro.0/).

The toolchain is now installed to your system.

== Configure Qt Creator ==

Run QT Creator

In Qt Creator go to Tools > Options > Devices and add your Wandboard as a generic linux device.

[[Image:Qtcreator-add-device.jpg|550px]]

go to Tools > Options > Build & Run and:

Add a new c++ compiler. Select your compiler: /opt/dhlinux/nodistro.0/sysroots/x86_64-oesdk-linux/usr/bin/arm-dhlinux-linux-gnueabi/arm-dhlinux-linux-gnueabi-g++

[[Image:Qtcreator-add-compiler.jpg|850px]]

Add a new debugger. Select your debugger: /opt/dhlinux/nodistro.0/sysroots/x86_64-oesdk-linux/usr/bin/arm-dhlinux-linux-gnueabi/arm-dhlinux-linux-gnueabi-gdb

[[Image:Qtcreator-add-debugger.jpg|850px]]

Add your Qt version by selecting the qmake located in /opt/dhlinux/nodistro.0/sysroots/x86_64-oesdk-linux/usr/bin/qmake

[[Image:Qtcreator-add-qt-version.jpg|850px]]

Add a new kit selecting your new Qt5 version and compiler and setting the sysroot to /opt/dhlinux/nodistro.0/sysroots/cortexa7t2hf-neon-vfpv4-dhlinux-linux-gnueabi and leave the Qt mkspec empty.
Then select your device

[[Image:Qtcreator-add-kit.jpg|850px]]

If there is a warning/error shown, please click apply between each step.

There is one last point. The SDK comes with an environment-setup which sets some variables that are needed if you want to use the toolchain. There are two ways to get this environment into Qt Creator:
* The first way is rather simple: Open a shell and source the environment-setup script (in the example <tt>/opt/dhlinux/nodistro.0/environment-setup-cortexa7t2hf-neon-vfpv4-dhlinux-linux-gnueabi</tt>). After that start Qt Creator in the same shell session. If you want to use another toolchain, you have start a new shell session, source the corresponding environment-setup and start QtCreator from there.
* The other possible way is bit more complicated, but in return it is possible to change the toolchain without restarting Qt Creator: In the settings of the kit there is a button for setting the environment of this kit ("Change"-button right of "Environment"). When this button is pressed, a window for editing text opens. There you can set environment variables by the schema <variable>=<value>, one variable can be set per line. You cannot simply copy the setup script, because at the script the shell is called and other variables are referenced which isn't supported by Qt Creator. It is also possible that the setup script imports additional scripts from the "environment-setup.d" directory of each sysroot. So you have to source the setup script and look what variables have been set and write them and their respective values into the window. If you want to use another toolchain, than you can change the used kit. An example for configuring the environment of a kit is inside the collapsible box.

<div class="toccolours mw-collapsible mw-collapsed" style="overflow:auto;">
<div style="font-weight:bold;">Example for setting the environment variables at the kit</div>
<div class="mw-collapsible-content">

/opt/dhlinux/nodistro.0/environment-setup-cortexa7t2hf-neon-vfpv4-dhlinux-linux-gnueabi:

<tt># Check for LD_LIBRARY_PATH being set, which can break SDK and generally is a bad practice
# http://tldp.org/HOWTO/Program-Library-HOWTO/shared-libraries.html#AEN80
# http://xahlee.info/UnixResource_dir/_/ldpath.html
# Only disable this check if you are absolutely know what you are doing!
if [ ! -z "$LD_LIBRARY_PATH" ]; then
echo "Your environment is misconfigured, you probably need to 'unset LD_LIBRARY_PATH'"
echo "but please check why this was set in the first place and that it's safe to unset."
echo "The SDK will not operate correctly in most cases when LD_LIBRARY_PATH is set."
echo "For more references see:"
echo " http://tldp.org/HOWTO/Program-Library-HOWTO/shared-libraries.html#AEN80"
echo " http://xahlee.info/UnixResource_dir/_/ldpath.html"
return 1
fi
export SDKTARGETSYSROOT=/opt/dhlinux/nodistro.0/sysroots/cortexa7t2hf-neon-vfpv4-dhlinux-linux-gnueabi
export PATH=/opt/dhlinux/nodistro.0/sysroots/x86_64-oesdk-linux/usr/bin:/opt/dhlinux/nodistro.0/sysroots/x86_64-oesdk-linux/usr/sbin:/opt/dhlinux/nodistro.0/sysroots/x86_64-oesdk-linux/bin:/opt/dhlinux/nodistro.0/sysroots/x86_64-oesdk-linux/sbin:/opt/dhlinux/nodistro.0/sysroots/x86_64-oesdk-linux/usr/bin/../x86_64-oesdk-linux/bin:/opt/dhlinux/nodistro.0/sysroots/x86_64-oesdk-linux/usr/bin/arm-dhlinux-linux-gnueabi:/opt/dhlinux/nodistro.0/sysroots/x86_64-oesdk-linux/usr/bin/arm-dhlinux-linux-musl:$PATH
export PKG_CONFIG_SYSROOT_DIR=$SDKTARGETSYSROOT
export PKG_CONFIG_PATH=$SDKTARGETSYSROOT/usr/lib/pkgconfig:$SDKTARGETSYSROOT/usr/share/pkgconfig
export CONFIG_SITE=/opt/dhlinux/nodistro.0/site-config-cortexa7t2hf-neon-vfpv4-dhlinux-linux-gnueabi
export OECORE_NATIVE_SYSROOT="/opt/dhlinux/nodistro.0/sysroots/x86_64-oesdk-linux"
export OECORE_TARGET_SYSROOT="$SDKTARGETSYSROOT"
export OECORE_ACLOCAL_OPTS="-I /opt/dhlinux/nodistro.0/sysroots/x86_64-oesdk-linux/usr/share/aclocal"
export OECORE_BASELIB="lib"
export OECORE_TARGET_ARCH="arm"
export OECORE_TARGET_OS="linux-gnueabi"
unset command_not_found_handle
export CC="arm-dhlinux-linux-gnueabi-gcc -mthumb -mfpu=neon-vfpv4 -mfloat-abi=hard -mcpu=cortex-a7 --sysroot=$SDKTARGETSYSROOT"
export CXX="arm-dhlinux-linux-gnueabi-g++ -mthumb -mfpu=neon-vfpv4 -mfloat-abi=hard -mcpu=cortex-a7 --sysroot=$SDKTARGETSYSROOT"
export CPP="arm-dhlinux-linux-gnueabi-gcc -E -mthumb -mfpu=neon-vfpv4 -mfloat-abi=hard -mcpu=cortex-a7 --sysroot=$SDKTARGETSYSROOT"
export AS="arm-dhlinux-linux-gnueabi-as "
export LD="arm-dhlinux-linux-gnueabi-ld --sysroot=$SDKTARGETSYSROOT"
export GDB=arm-dhlinux-linux-gnueabi-gdb
export STRIP=arm-dhlinux-linux-gnueabi-strip
export RANLIB=arm-dhlinux-linux-gnueabi-ranlib
export OBJCOPY=arm-dhlinux-linux-gnueabi-objcopy
export OBJDUMP=arm-dhlinux-linux-gnueabi-objdump
export READELF=arm-dhlinux-linux-gnueabi-readelf
export AR=arm-dhlinux-linux-gnueabi-ar
export NM=arm-dhlinux-linux-gnueabi-nm
export M4=m4
export TARGET_PREFIX=arm-dhlinux-linux-gnueabi-
export CONFIGURE_FLAGS="--target=arm-dhlinux-linux-gnueabi --host=arm-dhlinux-linux-gnueabi --build=x86_64-linux --with-libtool-sysroot=$SDKTARGETSYSROOT"
export CFLAGS=" -O2 -pipe -g -feliminate-unused-debug-types "
export CXXFLAGS=" -O2 -pipe -g -feliminate-unused-debug-types "
export LDFLAGS="-Wl,-O1 -Wl,--hash-style=gnu -Wl,--as-needed"
export CPPFLAGS=""
export KCFLAGS="--sysroot=$SDKTARGETSYSROOT"
export OECORE_DISTRO_VERSION="0.0.1"
export OECORE_SDK_VERSION="nodistro.0"
export ARCH=arm
export CROSS_COMPILE=arm-dhlinux-linux-gnueabi-
# Append environment subscripts
if [ -d "$OECORE_TARGET_SYSROOT/environment-setup.d" ]; then
for envfile in $OECORE_TARGET_SYSROOT/environment-setup.d/*.sh; do
. $envfile
done
fi
if [ -d "$OECORE_NATIVE_SYSROOT/environment-setup.d" ]; then
for envfile in $OECORE_NATIVE_SYSROOT/environment-setup.d/*.sh; do
. $envfile
done
fi</tt>

There are additional scripts in the "environment-setup.d"-directories of the sysroots which are included at the main setup-script. These scripts have the following content:

/opt/dhlinux/nodistro.0/sysroots/x86_64-oesdk-linux/environment-setup.d/cmake.sh:

<tt>export OE_CMAKE_TOOLCHAIN_FILE="$OECORE_NATIVE_SYSROOT/usr/share/cmake/OEToolchainConfig.cmake"
export OE_CMAKE_FIND_LIBRARY_CUSTOM_LIB_SUFFIX="`echo $OECORE_BASELIB | sed -e s/lib//`"</tt>

/opt/dhlinux/nodistro.0/sysroots/x86_64-oesdk-linux/environment-setup.d/openssl.sh:

<tt>export PATH=$OECORE_NATIVE_SYSROOT/usr/bin:$PATH
export OE_QMAKE_CFLAGS="$CFLAGS"
export OE_QMAKE_CXXFLAGS="$CXXFLAGS"
export OE_QMAKE_LDFLAGS="$LDFLAGS"
export OE_QMAKE_CC="$CC"
export OE_QMAKE_CXX="$CXX"
export OE_QMAKE_LINK="$CXX"
export OE_QMAKE_AR=$AR
export OE_QMAKE_STRIP=$STRIP
export QT_CONF_PATH=$OECORE_NATIVE_SYSROOT/usr/bin/qt.conf
export OE_QMAKE_LIBDIR_QT=`qmake -query QT_INSTALL_LIBS`
export OE_QMAKE_INCDIR_QT=`qmake -query QT_INSTALL_HEADERS`
export OE_QMAKE_MOC=$OECORE_NATIVE_SYSROOT/usr/bin/moc
export OE_QMAKE_UIC=$OECORE_NATIVE_SYSROOT/usr/bin/uic
export OE_QMAKE_RCC=$OECORE_NATIVE_SYSROOT/usr/bin/rcc
export OE_QMAKE_QDBUSCPP2XML=$OECORE_NATIVE_SYSROOT/usr/bin/qdbuscpp2xml
export OE_QMAKE_QDBUSXML2CPP=$OECORE_NATIVE_SYSROOT/usr/bin/qdbusxml2cpp
export OE_QMAKE_QT_CONFIG=`qmake -query QT_INSTALL_LIBS`/mkspecs/qconfig.pri
export OE_QMAKE_PATH_HOST_BINS=$OECORE_NATIVE_SYSROOT/usr/bin
export QMAKESPEC=`qmake -query QT_INSTALL_LIBS`/mkspecs/linux-oe-g++</tt>

/opt/dhlinux/nodistro.0/sysroots/x86_64-oesdk-linux/environment-setup.d/qt5.sh:

<tt>export OPENSSL_CONF="$OECORE_NATIVE_SYSROOT/usr/lib/ssl-1.1/openssl.cnf"</tt>

This results in the following environment configuration:

[[File:Qtcreator-set-environment.png|1000px]]

</div></div>

DHCOM STM32MP1-D2

2021-04-09T13:32:27Z

Mschmoeller: /* Download binaries/images */

[[Image:Page Under Construction.png|600px|DHCOM STM32MP1-D2]]

{|
|
|
|-
|__TOC__
|[[Image:DHCOM STM32MP1 Pers medres.jpg|600px|DHCOM STM32MP1-D2]]
|}

== Hardware ==

{| class="wikitable" align="center" | style="width: 100%; color: #000000; background: #f3f3f3;" valign="top" |
|-
| style="width: 50%; background: #076b8d; border: 0pt;" |
| style="width: 50%; background: #076b8d; border: 0pt;" |
|-
|valign="top" style="border: 0pt;" |
* '''Dual ARM Cortex®-A7 up to 650 MHz and Single ARM Cortex®-M4 up to 209 MHz'''
* 3D GPU OpenGL® ES2.0 up to 533 MHz, Power Management: STPMIC1A
* TrustZone, cryptography, hash, secure boot
* DDR3L: 256 / 512 / 1024 Mbyte (32 bit)
* eMMC flash: 4 / 8 / 16 GB
* 2 MByte SPI boot flash
* 256 byte EEPROM
* WiFi / Bluetooth: WiFi IEEE 802.11 a/b/g/n, 802.11j (hosted mode) with dual band, Bluetooth® v5.0 (BR/EDR/BLE), PCB antenna and U.FL antenna connector
* On-board microSD card socket
* RTC with temperature compensation ± 3.0 ppm between -40 to +85°C
* Supply voltage range: 3.3 or 5.0 VDC / typ. 1 W-1.5 W (without WiFi/BT)
* Industrial temperature range (-40°C to +85°C)
* SODIMM-200 socket with DHCOM pin assignment
* JTAG debug connection via FFC plug connector or Tag-Connect
* Bus interface: 16 bit asynchron address/data bus, 1 CS
* Ethernet 1: 10 / 100 Mbit with PHY, IEEE 1588v2
* Ethernet 2: 10 / 100 Mbit with PHY
* MMC/SD interface: 4 bit mode
|valign="top" style="border: 0pt;" |
* CAN 1: V2.0B and CAN FD V1.0, TTCAN (time triggered)
* CAN 2: V2.0B and CAN FD V1.0
* UART 1: Rx / Tx / Rts / Cts, up to 12.5 Mbit/s
* UART 2: Rx / Tx / Rts / Cts, up to 12.5 Mbit/s
* UART 3: Rx / Tx, up to 12.5 Mbit/s
* SPI 1: max. 50 Mbit/s
* I2C 1: max. 1 Mbit/s
* I2C 2: max. 1 Mbit/s
* USB host 1: High-Speed
* USB OTG: High-Speed
* Parallel camera: 10 bit interface up to 140 Mbytes/s
* Display RGB: Max. 1366 x 768 pixels, 24 bit
* MIPI®-DSI 2 data lanes up to 1 GHz each
* Touch: 4-wire
* I²S Audio interface
* GPIOs: 24 IOs
* PWM: 1x 16 bit
* Analog: 4x 16 bit ADC and 2x 12 bit DAC
|}

*[[DHCOM STM32MP1 Hardware|Hardware and PCNs]]

== Software Support ==
*[[DHCOM STM32MP1 Bootloader U-Boot|STM32MP1: Bootloader U-Boot]]
*[[DHCOM STM32MP1 Linux|STM32MP1: Linux]]
*[[DHCOM STM32MP1 Yocto|STM32MP1: Yocto]]
*[[OpenOCD JTAG on STM32MP1|How to use JTAG on STM32MP1]]
*[[IPC|Inter‐Processor Communication (Cortex-A7 to Cortex-M4)]]

== BSP Sources ==
==== [https://www.denx.de/wiki/U-Boot U-Boot] ====
* [https://github.com/dh-electronics/u-boot-stm32mp1/tree/dev/2020.07_dhsom DH U-Boot (based on v2020.07)]

==== [https://www.kernel.org Linux Kernel and Yocto] ====
* Mainline
* [https://github.com/dh-electronics/linux-stm32mp1/tree/dev/5.10.17_dhsom DH 5.10.17 Development]
* [https://github.com/dh-electronics/dhcom_stm32mp1-bsp-platform '''NEW''' Yocto meta layer --> Github]

== Download binaries/images ==
Note: Based on kernel 5.10.x and Yocto version dunfell
* [[media:Dh-image-demo-dh-stm32mp1-dhcom-pdk2-20210409.wic.xz|'''NEW''' DH Mainline based Starter Image]]

DHCOM STM32MP1-D2

2021-02-25T10:26:56Z

Mschmoeller: /* Linux Kernel and Yocto */

[[Image:Page Under Construction.png|600px|DHCOM STM32MP1-D2]]

{|
|
|
|-
|__TOC__
|[[Image:DHCOM STM32MP1 Pers medres.jpg|600px|DHCOM STM32MP1-D2]]
|}

== Hardware ==

{| class="wikitable" align="center" | style="width: 100%; color: #000000; background: #f3f3f3;" valign="top" |
|-
| style="width: 50%; background: #076b8d; border: 0pt;" |
| style="width: 50%; background: #076b8d; border: 0pt;" |
|-
|valign="top" style="border: 0pt;" |
* '''Dual ARM Cortex®-A7 up to 650 MHz and Single ARM Cortex®-M4 up to 209 MHz'''
* 3D GPU OpenGL® ES2.0 up to 533 MHz, Power Management: STPMIC1A
* TrustZone, cryptography, hash, secure boot
* DDR3L: 256 / 512 / 1024 Mbyte (32 bit)
* eMMC flash: 4 / 8 / 16 GB
* 2 MByte SPI boot flash
* 256 byte EEPROM
* WiFi / Bluetooth: WiFi IEEE 802.11 a/b/g/n, 802.11j (hosted mode) with dual band, Bluetooth® v5.0 (BR/EDR/BLE), PCB antenna and U.FL antenna connector
* On-board microSD card socket
* RTC with temperature compensation ± 3.0 ppm between -40 to +85°C
* Supply voltage range: 3.3 or 5.0 VDC / typ. 1 W-1.5 W (without WiFi/BT)
* Industrial temperature range (-40°C to +85°C)
* SODIMM-200 socket with DHCOM pin assignment
* JTAG debug connection via FFC plug connector or Tag-Connect
* Bus interface: 16 bit asynchron address/data bus, 1 CS
* Ethernet 1: 10 / 100 Mbit with PHY, IEEE 1588v2
* Ethernet 2: 10 / 100 Mbit with PHY
* MMC/SD interface: 4 bit mode
|valign="top" style="border: 0pt;" |
* CAN 1: V2.0B and CAN FD V1.0, TTCAN (time triggered)
* CAN 2: V2.0B and CAN FD V1.0
* UART 1: Rx / Tx / Rts / Cts, up to 12.5 Mbit/s
* UART 2: Rx / Tx / Rts / Cts, up to 12.5 Mbit/s
* UART 3: Rx / Tx, up to 12.5 Mbit/s
* SPI 1: max. 50 Mbit/s
* I2C 1: max. 1 Mbit/s
* I2C 2: max. 1 Mbit/s
* USB host 1: High-Speed
* USB OTG: High-Speed
* Parallel camera: 10 bit interface up to 140 Mbytes/s
* Display RGB: Max. 1366 x 768 pixels, 24 bit
* MIPI®-DSI 2 data lanes up to 1 GHz each
* Touch: 4-wire
* I²S Audio interface
* GPIOs: 24 IOs
* PWM: 1x 16 bit
* Analog: 4x 16 bit ADC and 2x 12 bit DAC
|}

*[[DHCOM STM32MP1 Hardware|Hardware and PCNs]]

== Software Support ==
*[[DHCOM STM32MP1 Bootloader U-Boot|STM32MP1: Bootloader U-Boot]]
*[[DHCOM STM32MP1 Linux|STM32MP1: Linux]]
*[[DHCOM STM32MP1 Yocto|STM32MP1: Yocto]]
*[[OpenOCD JTAG on STM32MP1|How to use JTAG on STM32MP1]]
*[[IPC|Inter‐Processor Communication (Cortex-A7 to Cortex-M4)]]

== BSP Sources ==
==== [https://www.denx.de/wiki/U-Boot U-Boot] ====
* [https://github.com/dh-electronics/u-boot-stm32mp1/tree/dev/2020.07_dhsom DH U-Boot (based on v2020.07)]

==== [https://www.kernel.org Linux Kernel and Yocto] ====
* Mainline
* [https://github.com/dh-electronics/linux-stm32mp1/tree/dev/5.10.17_dhsom DH 5.10.17 Development]
* [https://github.com/dh-electronics/dhcom_stm32mp1-bsp-platform '''NEW''' Yocto meta layer --> Github]

== Download binaries/images ==
Note: Based on kernel 5.10.x and Yocto version dunfell
* [https://xxx '''NEW''' DH Mainline based Starter Image]

Template:DebianVM Development

2021-02-12T12:21:30Z

Mschmoeller: /* Yocto Builds */

== Introduction ==
For cross developing of applications we provide virtual machines with preinstalled toolchains. Choose the virtual machine which fits to your DHCOM target (Debian 8 on target -> Debian 8 virtual machine). Debian 8 does include support for architecture armhf and armel (Debian 6 only armel). '''By default Debian 8 is configured for armhf.'''
The sections '''Code Examples for Userspace-Applications to Access SPI, I2C, GPIOs, and more''' and '''Booting via NFS''' apply for Debian 6 and Debian 8.
== Debian 9 "Stretch" VM image (for VMware and VirtualBox) ==
=== Get the virtual machine ===
* Get [https://my.vmware.com/web/vmware/free#desktop_end_user_computing/vmware_workstation_player/12_0 VMware player] or [https://www.virtualbox.org/wiki/Downloads VirtualBox]

* [[media:RND Debian Stretch v2.0.Vx.zip|Debian 9 "Stretch" VMware Image]] Default password for devel user: '''devel''' Default password for root user: '''root'''
: Remark: For security reasons, you must set your own password when starting the virtual machine for the first time:
::# Enter default user devel password (devel)
::# Enter default user devel password again (devel)
::# Enter your own user devel password
::# Enter your own user devel password again

{|class="wikitable" style="padding:5px;"
|-
! Version: !! File: !! Changes:
|- style="text-align: left" valign="top"
| v2.0.Vx || style="text-align: left;width: 13em" | Debian Stretch v2.0.Vx.zip || style="text-align: left;width: 40em" | - First release version of Debian 9 VM
|}

=== Installed Toolchains ===
:* '''Used for building the Linux Kernel for our ARMv7 DHCOM devices.'''
::* '''ARM GCC 8.3'''
:::: armhf: <tt>CROSS_COMPILE=/opt/gcc-arm-8.3-2019.03-x86_64-arm-linux-gnueabihf/bin/arm-linux-gnueabihf-</tt>

::* '''Linaro GCC 7.4'''
:::: armhf: <tt>CROSS_COMPILE=/opt/gcc-linaro-7.4.1-2019.02-x86_64_arm-linux-gnueabihf/bin/arm-linux-gnueabihf-</tt>

::* '''Linaro GCC 6.3'''
:::: armhf: <tt>CROSS_COMPILE=/opt/gcc-linaro-6.3.1-2017.05-x86_64_arm-linux-gnueabihf/bin/arm-linux-gnueabihf-</tt>

::* '''Linaro GCC 4.9'''
:::: armhf: <tt>CROSS_COMPILE=/opt/gcc-linaro-4.9-2014.11-x86_64_arm-linux-gnueabihf/bin/arm-linux-gnueabihf-</tt>

:* '''Used for building the Linux Kernel for our ARMv5 DHCOM devices.'''
::* '''CodeSourcery GCC 4.5'''
:::: armel: <tt>CROSS_COMPILE=/opt/CodeSourcery-2011.03-41/bin/arm-none-linux-gnueabi-</tt>
=== Yocto Builds ===
'''Note:''' If you are going to set up any DH electronics Yocto project by using the repo tool, you need to install Python version 3.6 or later.

This versions are not provided by official Debian Stretch package repositories.
To manually install Python 3.6.9 , please follow the instructions:
$: sudo apt install libsqlite3-dev
$: wget https://www.python.org/ftp/python/3.6.9/Python-3.6.9.tgz
$: tar xvf Python-3.6.9.tgz
$: cd Python-3.6.9
$: ./configure --enable-optimizations --enable-shared
$: make -j8
$: sudo make install
$: sudo /sbin/ldconfig -v

== Debian 8 "Jessie" VM image (for VMware) ==
=== Get the virtual machine ===
* [https://my.vmware.com/web/vmware/free#desktop_end_user_computing/vmware_workstation_player/12_0 Get the VMware player]

* [[media:Debian Jessie v1.3.zip|Debian 8 "Jessie" VMware Image]] '''Important info (Feb/2018):''' Don't update the system, because it will brake the cross compiler. If you are asked to upgrade, say NO! Password for devel user: '''devel''' Password for root user: '''root'''

{|class="wikitable" style="padding:5px;"
|-
! Version: !! File: !! Changes:
|- style="text-align: left" valign="top"
| v1.3 || style="text-align: left;width: 13em" | Debian Jessie v1.3.zip || style="text-align: left;width: 40em" | - Debian Security updates - Compatibility VMware player 5.0 - Ready for yocto build - Build environment for DHCOM i.MX6 Qt5.7.1 / Qt5.9.1 - Add some useful tools
|-
| v1.2 || style="text-align: left;width: 13em" | Debian Jessie v1.2.zip || style="text-align: left;width: 40em" | - Debian Security updates - Qt Creator + Support for imx6 modules + Demos - Update elbe to v1.0 - Add some tools / editors
|-
| v1.1 || style="text-align: left;width: 13em" | Debian Jessie v1.1.zip || style="text-align: left;width: 40em" | - Compatibility VMware player 6.0
|-
| v1.0 || style="text-align: left;width: 13em" | Debian Jessie v1.0.zip || style="text-align: left;width: 40em" | - New Debian 8 VM
|}

=== Installed Toolchains ===
:* '''Used for building the Linux Kernel for our ARMv7 DHCOM devices.'''
::* '''Debian Multiarch Cross Toolchain GCC 4.9'''
:::: armhf: <tt>CROSS_COMPILE=arm-linux-gnueabihf-</tt>
:::: The Cross Toolchains is preinstalled. They should be used for cross development of native Linux applications. They are downloaded and installed with the Debian Package Manager.
:::: Install directory is <tt>/usr/bin/</tt>. Please have a look at the preconfigured Examples for cross development using the Eclipse IDE.

::* '''Linaro GCC 4.9'''
:::: armhf: <tt>CROSS_COMPILE=/opt/gcc-linaro-4.9-2014.11-x86_64_arm-linux-gnueabihf/bin/arm-linux-gnueabihf-</tt>

:* '''Used for building the Linux Kernel for our ARMv5 DHCOM devices.'''
::* '''Debian Multiarch Cross Toolchain'''
:::: armel: <tt>CROSS_COMPILE=arm-linux-gnueabi-</tt>
:::: The Cross Toolchains is preinstalled. They should be used for cross development of native Linux applications. They are downloaded and installed with the Debian Package Manager.
:::: Install directory is <tt>/usr/bin/</tt>. Please have a look at the preconfigured Examples for cross development using the Eclipse IDE.

::* '''CodeSourcery GCC 4.5'''
:::: armel: <tt>CROSS_COMPILE=/opt/CodeSourcery-2011.03-41/bin/arm-none-linux-gnueabi-</tt>

=== Qt5 Development ===

==== Qt5.5.1 prebuilt and preinstalled ====
We provide the prebuilt Qt5.5.1 libraries including WebEngine (only QtQuick) and WebKit in <tt>/work/qt5/sysroot/</tt>. This directory contains a Debian 8 based rootfilesystem which is prepared for DHCOM i.MX6, the matching sysroot (*-dev packages), and the Qt5.5.1 libraries installed.

==== Qt5.7.1 ====
We support the latest Qt5.7.1 on our DHCOM i.MX6 and DHCOM am335x. Please download and install the [[media:Qmake-sysroot-mx6-crossarmhf_5.7.1-1.0_amd64.deb|'''qmake-sysroot-am33-crossarmhf_5.7.1-1.0''']] package to the DebianVM:
# open a terminal
# # for i.MX6: <tt>wget https://dl.dropboxusercontent.com/u/19433555/DHCOM/imx6/qmake-sysroot-mx6-crossarmhf_5.7.1-1.0_amd64.deb</tt>
# # for AM335x: <tt>wget https://dl.dropboxusercontent.com/u/19433555/DHCOM/am335x/qmake-sysroot-am33-crossarmhf_5.7.1-1.0_amd64.deb</tt>
# install the package
# # <tt>sudo dpkg -i qmake-sysroot-mx6-crossarmhf_5.7.1-1.0_amd64.deb</tt>
# now the sysroot and qmake is ready to use
# path to qmake is <tt>/work/qt5_mx6_armhf/sysroot/usr/local/qt5.7.1/bin/qmake</tt>

==== Build a Qt5 Application via console ====
# open a terminal
# navigate to your Qt5 sources
# # <tt>/work/qt5/sysroot/usr/local/qt5.5.1/bin/qmake your_own_app.pro</tt>
# # <tt>make</tt>
==== Qt Creator ====
# Start Qt Creator IDE
# Open demo project TwoLED: <tt>/work/qt5_Demos/TwoLED</tt>
# There you can find the configurations for your own project.

== Debian 6 "Squeeze" VM image (for VMware) ==
=== Get the virtual machine ===
* [https://my.vmware.com/web/vmware/free#desktop_end_user_computing/vmware_player/6_0 Get the VMware player]

* [[media:Debian Squeeze v1.5pw.zip|Debian Squeeze VMware Image (PW: dhelectronics)]] Password for devel user: '''devel''' Password for root user: '''root'''

{|class="wikitable" style="padding:5px;"
|-
! Version: !! File: !! Changes:
|- style="text-align: left" valign="top"
| v1.5 || style="text-align: left;width: 13em" | Debian Squeeze v1.5pw.zip || style="text-align: left;width: 40em" | - Update VMware Tools - DH UBI-Tools - Language: English - System updates
|- style="text-align: left" valign="top"
| v1.4 || Debian Squeeze v1.4pw.zip || style="text-align: left" | - ELBE v0.3.1 - ELDK 4.2 - Qt Creator 2.6.1 + Qt target libs 4.7.2 - System updates
|- style="text-align: left" valign="top"
| v1.3 || Debian Squeeze v1.3.zipx || style="text-align: left" | - Mono 2.10 - mtd-utils - System updates
|- style="text-align: left" valign="top"
| v1.2 || Debian Squeeze v1.2.zipx || style="text-align: left" | - Emdebian Toolchain gcc 4.3 / g++ 4.3 (<code>arm-linux-gnueabi-...</code>) - TortoiseHg + TortoiseHg for Nautilus - Add Plugin "REST Client" in Iceweasel
|- style="text-align: left" valign="top"
| v1.1 || Debian Squeeze v1.1.zipx || style="text-align: left" | - Update Eclipse Indigo with CDT 8.0 - Add demo project "crosshelloworld"
|- style="text-align: left" valign="top"
| v1.0 || Debian Squeeze.zipx || style="text-align: left" | - First Release - CodeSourcery Toolchain (<code>arm-none-linux-gnueabi-...</code>) - Eclipse Helios & Indigo
|}

=== Installed Toolchains ===
:* '''Used for building the Linux Kernel for our ARMv5 DHCOM devices.'''
::* '''Debian Multiarch Cross Toolchain GCC 4.3'''
:::: armel: <tt>CROSS_COMPILE=arm-linux-gnueabi-</tt>
:::: The Cross Toolchains is preinstalled. They should be used for cross development of native Linux applications. They are downloaded and installed with the Debian Package Manager.
:::: Install directory is <tt>/usr/bin/</tt>. Please have a look at the preconfigured Examples for cross development using the Eclipse IDE.

::* '''CodeSourcery GCC 4.5'''
:::: armel: <tt>CROSS_COMPILE=/opt/CodeSourcery/Sourcery_G++_Lite/bin/arm-none-linux-gnueabi-</tt>

=== Setting up a Eclipse Cross Executable Project: ===
* Use Eclipse Indigo (version 3.7.1) for your project.
* Create a new C++ Project and choose as Executable Project type '''Cross-Compile Project''' and as Toolchains '''Cross GCC'''
* Click the Button "Next" and specify under '''Tool command path''' the Toolchain path.
:*CodeSourcery:
::Folder "'''<code>/opt/CodeSourcery/Sourcery_G++_Lite/bin'''</code>"
::Prefix type "<code>'''arm-none-linux-gnueabi-'''</code>"
:*Emdebian Toolchain:
::Folder "<code>'''/usr/bin'''</code>"
::Prefix type "<code>'''arm-linux-gnueabi-'''</code>"

== Use Virtualbox instead of VMware Player/Workstation ==

[[media:DOC_VMware_Machine_mit_VirtualBox_starten_V1.0_2015-10-21.pdf| VMware Maschine mit VirtualBox starten (German)]]

== Booting via TFTP/NFS ==
=== Prepare the virtual machine ===
# '''Setup nfs-kernel-server'''
#* Install thf nfs server: <code>$ sudo apt-get install nfs-kernel-server </code>
#* Create a nfsservice directory: <code>$ mkdir /work/nfsroot </code>
#* Place the root file system in the folder <code>$ cd /work/nfsroot; sudo tar xf jessie....tar.gz </code>
#* Remove network config from rootfs <code>$ rm /work/nfsroot/etc/systemd/network/wired-dhcp.network</code>
#* Check whether the line below is part of the <tt>'''/etc/exports'''</tt> file
#* <code>/work/nfsroot X.X.X.0/255.255.255.0(rw,no_root_squash,no_subtree_check,insecure)</code>
#** The <tt>'''X'''</tt> must be substituted by our network settings
#* Restart the nfs-server with <code>4 /etc/init.d/nfs-kernel-server restart</code>
# '''Setup tftp-hpa server'''
#* Install a tftp server : <code>$ sudo apt-get install tftpd-hpa </code>
#* Create a tftp service directory: <code>$ mkdir /work/tftp </code>
#* Edit config: <code>$ sudo vi /etc/default/tftpd-hpa </code>
#** Take care that TFTP_DIRECTORY points to your tftp service directory, for example '/work/tftp'
#* Copy Kernel and DeviceTree into the tftp service directory
#* Restart the tftp-server with <code>$ /etc/init.d/tftp-hpa restart</code>

=== Setup the DHCOM Module for TFTP/NFS Boot ===
This example works with static IP addresses and is tested with DHCOM i.MX6 U-Boot 2015.10 and Kernle 4.4.38. It is possible to work with DHCP, too. For further information see [https://www.kernel.org/doc/Documentation/filesystems/nfs/nfsroot.txt https://www.kernel.org/doc/Documentation/filesystems/nfs/nfsroot.txt]
* Enter U-Boot console by pressing '''DEL/BACKSPACE''' on a RS232 terminal while switching on the power supply of the target
* Set IP addresses
{| class="wikitable"
|<tt># env set serverip 192.168.178.90</tt> <tt># env set ipaddr 192.168.178.91</tt>
|}
* bootargs for nfs root (up to Debian Jessie)
{| class="wikitable"
|<tt># env set rootfs 'root=/dev/nfs nfsroot=192.168.178.90:/work/nfsroot/ ip=192.168.178.91:192.168.178.90::255.255.255.0:dhcom:eth0:none'</tt>
|}
* bootargs for nfs root (since Debian Stretch)
{| class="wikitable"
|<tt># env set rootfs 'root=/dev/nfs nfsroot=192.168.178.90:/work/nfsroot/,nfsvers=3 ip=192.168.178.91:192.168.178.90::255.255.255.0:dhcom:eth0:none'</tt>
|}
* load Linux kernel and devicetree with tftp (change filename and path to match you setup)
{| class="wikitable"
|<tt># tftp ${loadaddr} zImage</tt> <tt># tftp ${fdt_addr} dtbs/imx6dl-dhcom3B-pdk2.dtb</tt>
|}
* set bootargs and boot
{| class="wikitable"
|<tt># run linuxargs</tt> <tt># bootz ${loadaddr} - ${fdt_addr}</tt>
|}
* optional: '''save it to be permanent'''
{| class="wikitable"
|<tt># env set bootcmd 'tftp ${loadaddr} zImage; tftp ${fdt_addr} dtbs/imx6dl-dhcom3B-pdk2.dtb; run linuxargs; bootz ${loadaddr} - ${fdt_addr}</tt> <tt># env save</tt>
|}

== Code Examples for Userspace-Applications to Access SPI, I2C, GPIOs, and more ==
* The following code samples are designed to get you started quickly with the device interfaces to SPI, I2C, GPIOs and more in Linux userspace applications.
* Within Eclipse you can Import the provided projects:
:# Execute '''">File>Import ..."'''
:# Navigate to '''">General>Existing Projects into Workspace"''' within the import dialog
:# Follow the dialog until you have finished.

[[media:Demos_SPI_I2C_GPIO.zip|Download Code Examples SPI, I2C, GPIOs and more ]]

Included Demos:
* SPI
* I2C
* GPIO
* RTC
* UART
* Watchdog
* ADC (only for i.MX25)

[[media:DHCOM_HAL.zip|Download C++ HAL class library for SPI, I2C, GPIO, UART and physical address space access]]

* For further documentation have a look at [http://www.kernel.org/doc/Documentation/ http://www.kernel.org/doc/Documentation/].

Template:DebianVM Development

2021-02-03T15:06:42Z

Mschmoeller: /* Debian 9 "Stretch" VM image (for VMware and VirtualBox) */

== Introduction ==
For cross developing of applications we provide virtual machines with preinstalled toolchains. Choose the virtual machine which fits to your DHCOM target (Debian 8 on target -> Debian 8 virtual machine). Debian 8 does include support for architecture armhf and armel (Debian 6 only armel). '''By default Debian 8 is configured for armhf.'''
The sections '''Code Examples for Userspace-Applications to Access SPI, I2C, GPIOs, and more''' and '''Booting via NFS''' apply for Debian 6 and Debian 8.
== Debian 9 "Stretch" VM image (for VMware and VirtualBox) ==
=== Get the virtual machine ===
* Get [https://my.vmware.com/web/vmware/free#desktop_end_user_computing/vmware_workstation_player/12_0 VMware player] or [https://www.virtualbox.org/wiki/Downloads VirtualBox]

* [[media:RND Debian Stretch v2.0.Vx.zip|Debian 9 "Stretch" VMware Image]] Default password for devel user: '''devel''' Default password for root user: '''root'''
: Remark: For security reasons, you must set your own password when starting the virtual machine for the first time:
::# Enter default user devel password (devel)
::# Enter default user devel password again (devel)
::# Enter your own user devel password
::# Enter your own user devel password again

{|class="wikitable" style="padding:5px;"
|-
! Version: !! File: !! Changes:
|- style="text-align: left" valign="top"
| v2.0.Vx || style="text-align: left;width: 13em" | Debian Stretch v2.0.Vx.zip || style="text-align: left;width: 40em" | - First release version of Debian 9 VM
|}

=== Installed Toolchains ===
:* '''Used for building the Linux Kernel for our ARMv7 DHCOM devices.'''
::* '''ARM GCC 8.3'''
:::: armhf: <tt>CROSS_COMPILE=/opt/gcc-arm-8.3-2019.03-x86_64-arm-linux-gnueabihf/bin/arm-linux-gnueabihf-</tt>

::* '''Linaro GCC 7.4'''
:::: armhf: <tt>CROSS_COMPILE=/opt/gcc-linaro-7.4.1-2019.02-x86_64_arm-linux-gnueabihf/bin/arm-linux-gnueabihf-</tt>

::* '''Linaro GCC 6.3'''
:::: armhf: <tt>CROSS_COMPILE=/opt/gcc-linaro-6.3.1-2017.05-x86_64_arm-linux-gnueabihf/bin/arm-linux-gnueabihf-</tt>

::* '''Linaro GCC 4.9'''
:::: armhf: <tt>CROSS_COMPILE=/opt/gcc-linaro-4.9-2014.11-x86_64_arm-linux-gnueabihf/bin/arm-linux-gnueabihf-</tt>

:* '''Used for building the Linux Kernel for our ARMv5 DHCOM devices.'''
::* '''CodeSourcery GCC 4.5'''
:::: armel: <tt>CROSS_COMPILE=/opt/CodeSourcery-2011.03-41/bin/arm-none-linux-gnueabi-</tt>
=== Yocto Builds ===
'''Note:''' If you are going to set up any DH electronics Yocto project by using the repo tool, you need to install Python version 3.6 or later.

This versions are not provided by official Debian Stretch package repositories.
To manually install Python 3.6.9 , please follow the instructions:
$: wget https://www.python.org/ftp/python/3.6.9/Python-3.6.9.tgz
$: tar xvf Python-3.6.9.tgz
$: cd Python-3.6.9
$: ./configure --enable-optimizations --enable-shared
$: make -j8
$: sudo make install
$: sudo /sbin/ldconfig -v

== Debian 8 "Jessie" VM image (for VMware) ==
=== Get the virtual machine ===
* [https://my.vmware.com/web/vmware/free#desktop_end_user_computing/vmware_workstation_player/12_0 Get the VMware player]

* [[media:Debian Jessie v1.3.zip|Debian 8 "Jessie" VMware Image]] '''Important info (Feb/2018):''' Don't update the system, because it will brake the cross compiler. If you are asked to upgrade, say NO! Password for devel user: '''devel''' Password for root user: '''root'''

{|class="wikitable" style="padding:5px;"
|-
! Version: !! File: !! Changes:
|- style="text-align: left" valign="top"
| v1.3 || style="text-align: left;width: 13em" | Debian Jessie v1.3.zip || style="text-align: left;width: 40em" | - Debian Security updates - Compatibility VMware player 5.0 - Ready for yocto build - Build environment for DHCOM i.MX6 Qt5.7.1 / Qt5.9.1 - Add some useful tools
|-
| v1.2 || style="text-align: left;width: 13em" | Debian Jessie v1.2.zip || style="text-align: left;width: 40em" | - Debian Security updates - Qt Creator + Support for imx6 modules + Demos - Update elbe to v1.0 - Add some tools / editors
|-
| v1.1 || style="text-align: left;width: 13em" | Debian Jessie v1.1.zip || style="text-align: left;width: 40em" | - Compatibility VMware player 6.0
|-
| v1.0 || style="text-align: left;width: 13em" | Debian Jessie v1.0.zip || style="text-align: left;width: 40em" | - New Debian 8 VM
|}

=== Installed Toolchains ===
:* '''Used for building the Linux Kernel for our ARMv7 DHCOM devices.'''
::* '''Debian Multiarch Cross Toolchain GCC 4.9'''
:::: armhf: <tt>CROSS_COMPILE=arm-linux-gnueabihf-</tt>
:::: The Cross Toolchains is preinstalled. They should be used for cross development of native Linux applications. They are downloaded and installed with the Debian Package Manager.
:::: Install directory is <tt>/usr/bin/</tt>. Please have a look at the preconfigured Examples for cross development using the Eclipse IDE.

::* '''Linaro GCC 4.9'''
:::: armhf: <tt>CROSS_COMPILE=/opt/gcc-linaro-4.9-2014.11-x86_64_arm-linux-gnueabihf/bin/arm-linux-gnueabihf-</tt>

:* '''Used for building the Linux Kernel for our ARMv5 DHCOM devices.'''
::* '''Debian Multiarch Cross Toolchain'''
:::: armel: <tt>CROSS_COMPILE=arm-linux-gnueabi-</tt>
:::: The Cross Toolchains is preinstalled. They should be used for cross development of native Linux applications. They are downloaded and installed with the Debian Package Manager.
:::: Install directory is <tt>/usr/bin/</tt>. Please have a look at the preconfigured Examples for cross development using the Eclipse IDE.

::* '''CodeSourcery GCC 4.5'''
:::: armel: <tt>CROSS_COMPILE=/opt/CodeSourcery-2011.03-41/bin/arm-none-linux-gnueabi-</tt>

=== Qt5 Development ===

==== Qt5.5.1 prebuilt and preinstalled ====
We provide the prebuilt Qt5.5.1 libraries including WebEngine (only QtQuick) and WebKit in <tt>/work/qt5/sysroot/</tt>. This directory contains a Debian 8 based rootfilesystem which is prepared for DHCOM i.MX6, the matching sysroot (*-dev packages), and the Qt5.5.1 libraries installed.

==== Qt5.7.1 ====
We support the latest Qt5.7.1 on our DHCOM i.MX6 and DHCOM am335x. Please download and install the [[media:Qmake-sysroot-mx6-crossarmhf_5.7.1-1.0_amd64.deb|'''qmake-sysroot-am33-crossarmhf_5.7.1-1.0''']] package to the DebianVM:
# open a terminal
# # for i.MX6: <tt>wget https://dl.dropboxusercontent.com/u/19433555/DHCOM/imx6/qmake-sysroot-mx6-crossarmhf_5.7.1-1.0_amd64.deb</tt>
# # for AM335x: <tt>wget https://dl.dropboxusercontent.com/u/19433555/DHCOM/am335x/qmake-sysroot-am33-crossarmhf_5.7.1-1.0_amd64.deb</tt>
# install the package
# # <tt>sudo dpkg -i qmake-sysroot-mx6-crossarmhf_5.7.1-1.0_amd64.deb</tt>
# now the sysroot and qmake is ready to use
# path to qmake is <tt>/work/qt5_mx6_armhf/sysroot/usr/local/qt5.7.1/bin/qmake</tt>

==== Build a Qt5 Application via console ====
# open a terminal
# navigate to your Qt5 sources
# # <tt>/work/qt5/sysroot/usr/local/qt5.5.1/bin/qmake your_own_app.pro</tt>
# # <tt>make</tt>
==== Qt Creator ====
# Start Qt Creator IDE
# Open demo project TwoLED: <tt>/work/qt5_Demos/TwoLED</tt>
# There you can find the configurations for your own project.

== Debian 6 "Squeeze" VM image (for VMware) ==
=== Get the virtual machine ===
* [https://my.vmware.com/web/vmware/free#desktop_end_user_computing/vmware_player/6_0 Get the VMware player]

* [[media:Debian Squeeze v1.5pw.zip|Debian Squeeze VMware Image (PW: dhelectronics)]] Password for devel user: '''devel''' Password for root user: '''root'''

{|class="wikitable" style="padding:5px;"
|-
! Version: !! File: !! Changes:
|- style="text-align: left" valign="top"
| v1.5 || style="text-align: left;width: 13em" | Debian Squeeze v1.5pw.zip || style="text-align: left;width: 40em" | - Update VMware Tools - DH UBI-Tools - Language: English - System updates
|- style="text-align: left" valign="top"
| v1.4 || Debian Squeeze v1.4pw.zip || style="text-align: left" | - ELBE v0.3.1 - ELDK 4.2 - Qt Creator 2.6.1 + Qt target libs 4.7.2 - System updates
|- style="text-align: left" valign="top"
| v1.3 || Debian Squeeze v1.3.zipx || style="text-align: left" | - Mono 2.10 - mtd-utils - System updates
|- style="text-align: left" valign="top"
| v1.2 || Debian Squeeze v1.2.zipx || style="text-align: left" | - Emdebian Toolchain gcc 4.3 / g++ 4.3 (<code>arm-linux-gnueabi-...</code>) - TortoiseHg + TortoiseHg for Nautilus - Add Plugin "REST Client" in Iceweasel
|- style="text-align: left" valign="top"
| v1.1 || Debian Squeeze v1.1.zipx || style="text-align: left" | - Update Eclipse Indigo with CDT 8.0 - Add demo project "crosshelloworld"
|- style="text-align: left" valign="top"
| v1.0 || Debian Squeeze.zipx || style="text-align: left" | - First Release - CodeSourcery Toolchain (<code>arm-none-linux-gnueabi-...</code>) - Eclipse Helios & Indigo
|}

=== Installed Toolchains ===
:* '''Used for building the Linux Kernel for our ARMv5 DHCOM devices.'''
::* '''Debian Multiarch Cross Toolchain GCC 4.3'''
:::: armel: <tt>CROSS_COMPILE=arm-linux-gnueabi-</tt>
:::: The Cross Toolchains is preinstalled. They should be used for cross development of native Linux applications. They are downloaded and installed with the Debian Package Manager.
:::: Install directory is <tt>/usr/bin/</tt>. Please have a look at the preconfigured Examples for cross development using the Eclipse IDE.

::* '''CodeSourcery GCC 4.5'''
:::: armel: <tt>CROSS_COMPILE=/opt/CodeSourcery/Sourcery_G++_Lite/bin/arm-none-linux-gnueabi-</tt>

=== Setting up a Eclipse Cross Executable Project: ===
* Use Eclipse Indigo (version 3.7.1) for your project.
* Create a new C++ Project and choose as Executable Project type '''Cross-Compile Project''' and as Toolchains '''Cross GCC'''
* Click the Button "Next" and specify under '''Tool command path''' the Toolchain path.
:*CodeSourcery:
::Folder "'''<code>/opt/CodeSourcery/Sourcery_G++_Lite/bin'''</code>"
::Prefix type "<code>'''arm-none-linux-gnueabi-'''</code>"
:*Emdebian Toolchain:
::Folder "<code>'''/usr/bin'''</code>"
::Prefix type "<code>'''arm-linux-gnueabi-'''</code>"

== Use Virtualbox instead of VMware Player/Workstation ==

[[media:DOC_VMware_Machine_mit_VirtualBox_starten_V1.0_2015-10-21.pdf| VMware Maschine mit VirtualBox starten (German)]]

== Booting via TFTP/NFS ==
=== Prepare the virtual machine ===
# '''Setup nfs-kernel-server'''
#* Install thf nfs server: <code>$ sudo apt-get install nfs-kernel-server </code>
#* Create a nfsservice directory: <code>$ mkdir /work/nfsroot </code>
#* Place the root file system in the folder <code>$ cd /work/nfsroot; sudo tar xf jessie....tar.gz </code>
#* Remove network config from rootfs <code>$ rm /work/nfsroot/etc/systemd/network/wired-dhcp.network</code>
#* Check whether the line below is part of the <tt>'''/etc/exports'''</tt> file
#* <code>/work/nfsroot X.X.X.0/255.255.255.0(rw,no_root_squash,no_subtree_check,insecure)</code>
#** The <tt>'''X'''</tt> must be substituted by our network settings
#* Restart the nfs-server with <code>4 /etc/init.d/nfs-kernel-server restart</code>
# '''Setup tftp-hpa server'''
#* Install a tftp server : <code>$ sudo apt-get install tftpd-hpa </code>
#* Create a tftp service directory: <code>$ mkdir /work/tftp </code>
#* Edit config: <code>$ sudo vi /etc/default/tftpd-hpa </code>
#** Take care that TFTP_DIRECTORY points to your tftp service directory, for example '/work/tftp'
#* Copy Kernel and DeviceTree into the tftp service directory
#* Restart the tftp-server with <code>$ /etc/init.d/tftp-hpa restart</code>

=== Setup the DHCOM Module for TFTP/NFS Boot ===
This example works with static IP addresses and is tested with DHCOM i.MX6 U-Boot 2015.10 and Kernle 4.4.38. It is possible to work with DHCP, too. For further information see [https://www.kernel.org/doc/Documentation/filesystems/nfs/nfsroot.txt https://www.kernel.org/doc/Documentation/filesystems/nfs/nfsroot.txt]
* Enter U-Boot console by pressing '''DEL/BACKSPACE''' on a RS232 terminal while switching on the power supply of the target
* Set IP addresses
{| class="wikitable"
|<tt># env set serverip 192.168.178.90</tt> <tt># env set ipaddr 192.168.178.91</tt>
|}
* bootargs for nfs root (up to Debian Jessie)
{| class="wikitable"
|<tt># env set rootfs 'root=/dev/nfs nfsroot=192.168.178.90:/work/nfsroot/ ip=192.168.178.91:192.168.178.90::255.255.255.0:dhcom:eth0:none'</tt>
|}
* bootargs for nfs root (since Debian Stretch)
{| class="wikitable"
|<tt># env set rootfs 'root=/dev/nfs nfsroot=192.168.178.90:/work/nfsroot/,nfsvers=3 ip=192.168.178.91:192.168.178.90::255.255.255.0:dhcom:eth0:none'</tt>
|}
* load Linux kernel and devicetree with tftp (change filename and path to match you setup)
{| class="wikitable"
|<tt># tftp ${loadaddr} zImage</tt> <tt># tftp ${fdt_addr} dtbs/imx6dl-dhcom3B-pdk2.dtb</tt>
|}
* set bootargs and boot
{| class="wikitable"
|<tt># run linuxargs</tt> <tt># bootz ${loadaddr} - ${fdt_addr}</tt>
|}
* optional: '''save it to be permanent'''
{| class="wikitable"
|<tt># env set bootcmd 'tftp ${loadaddr} zImage; tftp ${fdt_addr} dtbs/imx6dl-dhcom3B-pdk2.dtb; run linuxargs; bootz ${loadaddr} - ${fdt_addr}</tt> <tt># env save</tt>
|}

== Code Examples for Userspace-Applications to Access SPI, I2C, GPIOs, and more ==
* The following code samples are designed to get you started quickly with the device interfaces to SPI, I2C, GPIOs and more in Linux userspace applications.
* Within Eclipse you can Import the provided projects:
:# Execute '''">File>Import ..."'''
:# Navigate to '''">General>Existing Projects into Workspace"''' within the import dialog
:# Follow the dialog until you have finished.

[[media:Demos_SPI_I2C_GPIO.zip|Download Code Examples SPI, I2C, GPIOs and more ]]

Included Demos:
* SPI
* I2C
* GPIO
* RTC
* UART
* Watchdog
* ADC (only for i.MX25)

[[media:DHCOM_HAL.zip|Download C++ HAL class library for SPI, I2C, GPIO, UART and physical address space access]]

* For further documentation have a look at [http://www.kernel.org/doc/Documentation/ http://www.kernel.org/doc/Documentation/].

Template:DebianVM Development

2021-01-25T15:46:17Z

Mschmoeller: /* Debian 9 "Stretch" VM image (for VMware and VirtualBox) */

== Introduction ==
For cross developing of applications we provide virtual machines with preinstalled toolchains. Choose the virtual machine which fits to your DHCOM target (Debian 8 on target -> Debian 8 virtual machine). Debian 8 does include support for architecture armhf and armel (Debian 6 only armel). '''By default Debian 8 is configured for armhf.'''
The sections '''Code Examples for Userspace-Applications to Access SPI, I2C, GPIOs, and more''' and '''Booting via NFS''' apply for Debian 6 and Debian 8.
== Debian 9 "Stretch" VM image (for VMware and VirtualBox) ==
=== Get the virtual machine ===
* Get [https://my.vmware.com/web/vmware/free#desktop_end_user_computing/vmware_workstation_player/12_0 VMware player] or [https://www.virtualbox.org/wiki/Downloads VirtualBox]

* [[media:RND Debian Stretch v2.0.Vx.zip|Debian 9 "Stretch" VMware Image]] Default password for devel user: '''devel''' Default password for root user: '''root'''
: Remark: For security reasons, you must set your own password when starting the virtual machine for the first time:
::# Enter default user devel password (devel)
::# Enter default user devel password again (devel)
::# Enter your own user devel password
::# Enter your own user devel password again

{|class="wikitable" style="padding:5px;"
|-
! Version: !! File: !! Changes:
|- style="text-align: left" valign="top"
| v2.0.Vx || style="text-align: left;width: 13em" | Debian Stretch v2.0.Vx.zip || style="text-align: left;width: 40em" | - First release version of Debian 9 VM
|}

=== Installed Toolchains ===
:* '''Used for building the Linux Kernel for our ARMv7 DHCOM devices.'''
::* '''ARM GCC 8.3'''
:::: armhf: <tt>CROSS_COMPILE=/opt/gcc-arm-8.3-2019.03-x86_64-arm-linux-gnueabihf/bin/arm-linux-gnueabihf-</tt>

::* '''Linaro GCC 7.4'''
:::: armhf: <tt>CROSS_COMPILE=/opt/gcc-linaro-7.4.1-2019.02-x86_64_arm-linux-gnueabihf/bin/arm-linux-gnueabihf-</tt>

::* '''Linaro GCC 6.3'''
:::: armhf: <tt>CROSS_COMPILE=/opt/gcc-linaro-6.3.1-2017.05-x86_64_arm-linux-gnueabihf/bin/arm-linux-gnueabihf-</tt>

::* '''Linaro GCC 4.9'''
:::: armhf: <tt>CROSS_COMPILE=/opt/gcc-linaro-4.9-2014.11-x86_64_arm-linux-gnueabihf/bin/arm-linux-gnueabihf-</tt>

:* '''Used for building the Linux Kernel for our ARMv5 DHCOM devices.'''
::* '''CodeSourcery GCC 4.5'''
:::: armel: <tt>CROSS_COMPILE=/opt/CodeSourcery-2011.03-41/bin/arm-none-linux-gnueabi-</tt>
=== Yocto Builds ===
'''Note:''' If you are going to set up any DH electronics Yocto project by using the repo tool, you need to install Python version 3.6 or later.

This versions are not provided by official Debian Stretch package repositories.
To manually install Python 3.6.9 , please follow the instructions:
$: wget https://www.python.org/ftp/python/3.6.9/Python-3.6.9.tgz
$: tar xvf Python-3.6.9.tgz
$: cd Python-3.6.9
$: ./configure --enable-optimizations --enable-shared
$: make -j8
$: sudo make altinstall

== Debian 8 "Jessie" VM image (for VMware) ==
=== Get the virtual machine ===
* [https://my.vmware.com/web/vmware/free#desktop_end_user_computing/vmware_workstation_player/12_0 Get the VMware player]

* [[media:Debian Jessie v1.3.zip|Debian 8 "Jessie" VMware Image]] '''Important info (Feb/2018):''' Don't update the system, because it will brake the cross compiler. If you are asked to upgrade, say NO! Password for devel user: '''devel''' Password for root user: '''root'''

{|class="wikitable" style="padding:5px;"
|-
! Version: !! File: !! Changes:
|- style="text-align: left" valign="top"
| v1.3 || style="text-align: left;width: 13em" | Debian Jessie v1.3.zip || style="text-align: left;width: 40em" | - Debian Security updates - Compatibility VMware player 5.0 - Ready for yocto build - Build environment for DHCOM i.MX6 Qt5.7.1 / Qt5.9.1 - Add some useful tools
|-
| v1.2 || style="text-align: left;width: 13em" | Debian Jessie v1.2.zip || style="text-align: left;width: 40em" | - Debian Security updates - Qt Creator + Support for imx6 modules + Demos - Update elbe to v1.0 - Add some tools / editors
|-
| v1.1 || style="text-align: left;width: 13em" | Debian Jessie v1.1.zip || style="text-align: left;width: 40em" | - Compatibility VMware player 6.0
|-
| v1.0 || style="text-align: left;width: 13em" | Debian Jessie v1.0.zip || style="text-align: left;width: 40em" | - New Debian 8 VM
|}

=== Installed Toolchains ===
:* '''Used for building the Linux Kernel for our ARMv7 DHCOM devices.'''
::* '''Debian Multiarch Cross Toolchain GCC 4.9'''
:::: armhf: <tt>CROSS_COMPILE=arm-linux-gnueabihf-</tt>
:::: The Cross Toolchains is preinstalled. They should be used for cross development of native Linux applications. They are downloaded and installed with the Debian Package Manager.
:::: Install directory is <tt>/usr/bin/</tt>. Please have a look at the preconfigured Examples for cross development using the Eclipse IDE.

::* '''Linaro GCC 4.9'''
:::: armhf: <tt>CROSS_COMPILE=/opt/gcc-linaro-4.9-2014.11-x86_64_arm-linux-gnueabihf/bin/arm-linux-gnueabihf-</tt>

:* '''Used for building the Linux Kernel for our ARMv5 DHCOM devices.'''
::* '''Debian Multiarch Cross Toolchain'''
:::: armel: <tt>CROSS_COMPILE=arm-linux-gnueabi-</tt>
:::: The Cross Toolchains is preinstalled. They should be used for cross development of native Linux applications. They are downloaded and installed with the Debian Package Manager.
:::: Install directory is <tt>/usr/bin/</tt>. Please have a look at the preconfigured Examples for cross development using the Eclipse IDE.

::* '''CodeSourcery GCC 4.5'''
:::: armel: <tt>CROSS_COMPILE=/opt/CodeSourcery-2011.03-41/bin/arm-none-linux-gnueabi-</tt>

=== Qt5 Development ===

==== Qt5.5.1 prebuilt and preinstalled ====
We provide the prebuilt Qt5.5.1 libraries including WebEngine (only QtQuick) and WebKit in <tt>/work/qt5/sysroot/</tt>. This directory contains a Debian 8 based rootfilesystem which is prepared for DHCOM i.MX6, the matching sysroot (*-dev packages), and the Qt5.5.1 libraries installed.

==== Qt5.7.1 ====
We support the latest Qt5.7.1 on our DHCOM i.MX6 and DHCOM am335x. Please download and install the [[media:Qmake-sysroot-mx6-crossarmhf_5.7.1-1.0_amd64.deb|'''qmake-sysroot-am33-crossarmhf_5.7.1-1.0''']] package to the DebianVM:
# open a terminal
# # for i.MX6: <tt>wget https://dl.dropboxusercontent.com/u/19433555/DHCOM/imx6/qmake-sysroot-mx6-crossarmhf_5.7.1-1.0_amd64.deb</tt>
# # for AM335x: <tt>wget https://dl.dropboxusercontent.com/u/19433555/DHCOM/am335x/qmake-sysroot-am33-crossarmhf_5.7.1-1.0_amd64.deb</tt>
# install the package
# # <tt>sudo dpkg -i qmake-sysroot-mx6-crossarmhf_5.7.1-1.0_amd64.deb</tt>
# now the sysroot and qmake is ready to use
# path to qmake is <tt>/work/qt5_mx6_armhf/sysroot/usr/local/qt5.7.1/bin/qmake</tt>

==== Build a Qt5 Application via console ====
# open a terminal
# navigate to your Qt5 sources
# # <tt>/work/qt5/sysroot/usr/local/qt5.5.1/bin/qmake your_own_app.pro</tt>
# # <tt>make</tt>
==== Qt Creator ====
# Start Qt Creator IDE
# Open demo project TwoLED: <tt>/work/qt5_Demos/TwoLED</tt>
# There you can find the configurations for your own project.

== Debian 6 "Squeeze" VM image (for VMware) ==
=== Get the virtual machine ===
* [https://my.vmware.com/web/vmware/free#desktop_end_user_computing/vmware_player/6_0 Get the VMware player]

* [[media:Debian Squeeze v1.5pw.zip|Debian Squeeze VMware Image (PW: dhelectronics)]] Password for devel user: '''devel''' Password for root user: '''root'''

{|class="wikitable" style="padding:5px;"
|-
! Version: !! File: !! Changes:
|- style="text-align: left" valign="top"
| v1.5 || style="text-align: left;width: 13em" | Debian Squeeze v1.5pw.zip || style="text-align: left;width: 40em" | - Update VMware Tools - DH UBI-Tools - Language: English - System updates
|- style="text-align: left" valign="top"
| v1.4 || Debian Squeeze v1.4pw.zip || style="text-align: left" | - ELBE v0.3.1 - ELDK 4.2 - Qt Creator 2.6.1 + Qt target libs 4.7.2 - System updates
|- style="text-align: left" valign="top"
| v1.3 || Debian Squeeze v1.3.zipx || style="text-align: left" | - Mono 2.10 - mtd-utils - System updates
|- style="text-align: left" valign="top"
| v1.2 || Debian Squeeze v1.2.zipx || style="text-align: left" | - Emdebian Toolchain gcc 4.3 / g++ 4.3 (<code>arm-linux-gnueabi-...</code>) - TortoiseHg + TortoiseHg for Nautilus - Add Plugin "REST Client" in Iceweasel
|- style="text-align: left" valign="top"
| v1.1 || Debian Squeeze v1.1.zipx || style="text-align: left" | - Update Eclipse Indigo with CDT 8.0 - Add demo project "crosshelloworld"
|- style="text-align: left" valign="top"
| v1.0 || Debian Squeeze.zipx || style="text-align: left" | - First Release - CodeSourcery Toolchain (<code>arm-none-linux-gnueabi-...</code>) - Eclipse Helios & Indigo
|}

=== Installed Toolchains ===
:* '''Used for building the Linux Kernel for our ARMv5 DHCOM devices.'''
::* '''Debian Multiarch Cross Toolchain GCC 4.3'''
:::: armel: <tt>CROSS_COMPILE=arm-linux-gnueabi-</tt>
:::: The Cross Toolchains is preinstalled. They should be used for cross development of native Linux applications. They are downloaded and installed with the Debian Package Manager.
:::: Install directory is <tt>/usr/bin/</tt>. Please have a look at the preconfigured Examples for cross development using the Eclipse IDE.

::* '''CodeSourcery GCC 4.5'''
:::: armel: <tt>CROSS_COMPILE=/opt/CodeSourcery/Sourcery_G++_Lite/bin/arm-none-linux-gnueabi-</tt>

=== Setting up a Eclipse Cross Executable Project: ===
* Use Eclipse Indigo (version 3.7.1) for your project.
* Create a new C++ Project and choose as Executable Project type '''Cross-Compile Project''' and as Toolchains '''Cross GCC'''
* Click the Button "Next" and specify under '''Tool command path''' the Toolchain path.
:*CodeSourcery:
::Folder "'''<code>/opt/CodeSourcery/Sourcery_G++_Lite/bin'''</code>"
::Prefix type "<code>'''arm-none-linux-gnueabi-'''</code>"
:*Emdebian Toolchain:
::Folder "<code>'''/usr/bin'''</code>"
::Prefix type "<code>'''arm-linux-gnueabi-'''</code>"

== Use Virtualbox instead of VMware Player/Workstation ==

[[media:DOC_VMware_Machine_mit_VirtualBox_starten_V1.0_2015-10-21.pdf| VMware Maschine mit VirtualBox starten (German)]]

== Booting via TFTP/NFS ==
=== Prepare the virtual machine ===
# '''Setup nfs-kernel-server'''
#* Install thf nfs server: <code>$ sudo apt-get install nfs-kernel-server </code>
#* Create a nfsservice directory: <code>$ mkdir /work/nfsroot </code>
#* Place the root file system in the folder <code>$ cd /work/nfsroot; sudo tar xf jessie....tar.gz </code>
#* Remove network config from rootfs <code>$ rm /work/nfsroot/etc/systemd/network/wired-dhcp.network</code>
#* Check whether the line below is part of the <tt>'''/etc/exports'''</tt> file
#* <code>/work/nfsroot X.X.X.0/255.255.255.0(rw,no_root_squash,no_subtree_check,insecure)</code>
#** The <tt>'''X'''</tt> must be substituted by our network settings
#* Restart the nfs-server with <code>4 /etc/init.d/nfs-kernel-server restart</code>
# '''Setup tftp-hpa server'''
#* Install a tftp server : <code>$ sudo apt-get install tftpd-hpa </code>
#* Create a tftp service directory: <code>$ mkdir /work/tftp </code>
#* Edit config: <code>$ sudo vi /etc/default/tftpd-hpa </code>
#** Take care that TFTP_DIRECTORY points to your tftp service directory, for example '/work/tftp'
#* Copy Kernel and DeviceTree into the tftp service directory
#* Restart the tftp-server with <code>$ /etc/init.d/tftp-hpa restart</code>

=== Setup the DHCOM Module for TFTP/NFS Boot ===
This example works with static IP addresses and is tested with DHCOM i.MX6 U-Boot 2015.10 and Kernle 4.4.38. It is possible to work with DHCP, too. For further information see [https://www.kernel.org/doc/Documentation/filesystems/nfs/nfsroot.txt https://www.kernel.org/doc/Documentation/filesystems/nfs/nfsroot.txt]
* Enter U-Boot console by pressing '''DEL/BACKSPACE''' on a RS232 terminal while switching on the power supply of the target
* Set IP addresses
{| class="wikitable"
|<tt># env set serverip 192.168.178.90</tt> <tt># env set ipaddr 192.168.178.91</tt>
|}
* bootargs for nfs root (up to Debian Jessie)
{| class="wikitable"
|<tt># env set rootfs 'root=/dev/nfs nfsroot=192.168.178.90:/work/nfsroot/ ip=192.168.178.91:192.168.178.90::255.255.255.0:dhcom:eth0:none'</tt>
|}
* bootargs for nfs root (since Debian Stretch)
{| class="wikitable"
|<tt># env set rootfs 'root=/dev/nfs nfsroot=192.168.178.90:/work/nfsroot/,nfsvers=3 ip=192.168.178.91:192.168.178.90::255.255.255.0:dhcom:eth0:none'</tt>
|}
* load Linux kernel and devicetree with tftp (change filename and path to match you setup)
{| class="wikitable"
|<tt># tftp ${loadaddr} zImage</tt> <tt># tftp ${fdt_addr} dtbs/imx6dl-dhcom3B-pdk2.dtb</tt>
|}
* set bootargs and boot
{| class="wikitable"
|<tt># run linuxargs</tt> <tt># bootz ${loadaddr} - ${fdt_addr}</tt>
|}
* optional: '''save it to be permanent'''
{| class="wikitable"
|<tt># env set bootcmd 'tftp ${loadaddr} zImage; tftp ${fdt_addr} dtbs/imx6dl-dhcom3B-pdk2.dtb; run linuxargs; bootz ${loadaddr} - ${fdt_addr}</tt> <tt># env save</tt>
|}

== Code Examples for Userspace-Applications to Access SPI, I2C, GPIOs, and more ==
* The following code samples are designed to get you started quickly with the device interfaces to SPI, I2C, GPIOs and more in Linux userspace applications.
* Within Eclipse you can Import the provided projects:
:# Execute '''">File>Import ..."'''
:# Navigate to '''">General>Existing Projects into Workspace"''' within the import dialog
:# Follow the dialog until you have finished.

[[media:Demos_SPI_I2C_GPIO.zip|Download Code Examples SPI, I2C, GPIOs and more ]]

Included Demos:
* SPI
* I2C
* GPIO
* RTC
* UART
* Watchdog
* ADC (only for i.MX25)

[[media:DHCOM_HAL.zip|Download C++ HAL class library for SPI, I2C, GPIO, UART and physical address space access]]

* For further documentation have a look at [http://www.kernel.org/doc/Documentation/ http://www.kernel.org/doc/Documentation/].

DHCOM STM32MP1 Yocto

2020-11-17T13:05:26Z

Mschmoeller: Created page with "For general information about the Yocto Project please refer to the official [https://www.yoctoproject.org/ Website]. "Yocto is not an embedded Linux distribution – it creat..."

DHCOM STM32MP1-D2

2020-11-17T12:46:39Z

Mschmoeller:

[[Image:Page Under Construction.png|600px|DHCOM STM32MP1-D2]]

{|
|
|
|-
|__TOC__
|[[Image:DHCOM STM32MP1 Pers medres.jpg|600px|DHCOM STM32MP1-D2]]
|}

== Hardware ==

{| class="wikitable" align="center" | style="width: 100%; color: #000000; background: #f3f3f3;" valign="top" |
|-
| style="width: 50%; background: #076b8d; border: 0pt;" |
| style="width: 50%; background: #076b8d; border: 0pt;" |
|-
|valign="top" style="border: 0pt;" |
* '''Dual ARM Cortex®-A7 up to 650 MHz and Single ARM Cortex®-M4 up to 209 MHz'''
* 3D GPU OpenGL® ES2.0 up to 533 MHz, Power Management: STPMIC1A
* TrustZone, cryptography, hash, secure boot
* DDR3L: 256 / 512 / 1024 Mbyte (32 bit)
* eMMC flash: 4 / 8 / 16 GB
* 2 MByte SPI boot flash
* 256 byte EEPROM
* WiFi / Bluetooth: WiFi IEEE 802.11 a/b/g/n, 802.11j (hosted mode) with dual band, Bluetooth® v5.0 (BR/EDR/BLE), PCB antenna and U.FL antenna connector
* On-board microSD card socket
* RTC with temperature compensation ± 3.0 ppm between -40 to +85°C
* Supply voltage range: 3.3 or 5.0 VDC / typ. 1 W-1.5 W (without WiFi/BT)
* Industrial temperature range (-40°C to +85°C)
* SODIMM-200 socket with DHCOM pin assignment
* JTAG debug connection via FFC plug connector or Tag-Connect
* Bus interface: 16 bit asynchron address/data bus, 1 CS
* Ethernet 1: 10 / 100 Mbit with PHY, IEEE 1588v2
* Ethernet 2: 10 / 100 Mbit with PHY
* MMC/SD interface: 4 bit mode
|valign="top" style="border: 0pt;" |
* CAN 1: V2.0B and CAN FD V1.0, TTCAN (time triggered)
* CAN 2: V2.0B and CAN FD V1.0
* UART 1: Rx / Tx / Rts / Cts, up to 12.5 Mbit/s
* UART 2: Rx / Tx / Rts / Cts, up to 12.5 Mbit/s
* UART 3: Rx / Tx, up to 12.5 Mbit/s
* SPI 1: max. 50 Mbit/s
* I2C 1: max. 1 Mbit/s
* I2C 2: max. 1 Mbit/s
* USB host 1: High-Speed
* USB OTG: High-Speed
* Parallel camera: 10 bit interface up to 140 Mbytes/s
* Display RGB: Max. 1366 x 768 pixels, 24 bit
* MIPI®-DSI 2 data lanes up to 1 GHz each
* Touch: 4-wire
* I²S Audio interface
* GPIOs: 24 IOs
* PWM: 1x 16 bit
* Analog: 4x 16 bit ADC and 2x 12 bit DAC
|}

*[[DHCOM STM32MP1 Hardware|Hardware and PCNs]]

== Software Support ==
*[[DHCOM STM32MP1 Bootloader U-Boot|STM32MP1: Bootloader U-Boot]]
*[[DHCOM STM32MP1 Linux|STM32MP1: Linux]]
*[[DHCOM STM32MP1 Yocto|STM32MP1: Yocto]]
*[[OpenOCD JTAG on STM32MP1|How to use JTAG on STM32MP1]]
*[[IPC|Inter‐Processor Communication (Cortex-A7 to Cortex-M4)]]

== BSP Sources ==
==== [https://www.denx.de/wiki/U-Boot U-Boot] ====
* [https://github.com/dh-electronics/u-boot-stm32mp1/tree/dev/2020.07_dhsom DH U-Boot (based on v2020.07)]

==== [https://www.kernel.org Linux Kernel] ====
* Mainline
:* [https://github.com/dh-electronics/linux-stm32mp1/tree/dev/5.4.69_dhsom DH 5.4.69 Development]

Add Yocto SDK with QT5 to QT Creator

2020-05-25T07:31:25Z

Mschmoeller: /* Download and install the SDK package */

The following instructions are based on '''DHCOM STM32MP1''' computer on module and Yocto version "zeus"
__TOC__

== Prepairing your virtual machine ==

Get the [[Virtual Machine for Application Development]].

Install the following package:

$ sudo apt-get install qtcreator qt5default

== Download and install the SDK package ==

Get the [[media:Dhlinux-glibc-x86_64-meta-toolchain-qt5-cortexa7t2hf-neon-vfpv4-toolchain-nodistro.0.zip|QT5 SDK for STM32mp1]]

Unpack the archive and install the toolchain.

$ sh ./dhlinux-glibc-x86_64-meta-toolchain-qt5-cortexa7t2hf-neon-vfpv4-toolchain-nodistro.0.sh

Choose the installation directory (default: /opt/dhlinux/nodistro.0/).

The toolchain is now installed to your system.

== Configure Qt Creator ==

Run QT Creator

In Qt Creator go to Tools > Options > Devices and add your Wandboard as a generic linux device.

[[Image:Qtcreator-add-device.jpg|550px]]

go to Tools > Options > Build & Run and:

Add a new c++ compiler. Select your compiler: /opt/dhlinux/nodistro.0/sysroots/x86_64-oesdk-linux/usr/bin/arm-dhlinux-linux-gnueabi/arm-dhlinux-linux-gnueabi-g++

[[Image:Qtcreator-add-compiler.jpg|850px]]

Add a new debugger. Select your debugger: /opt/dhlinux/nodistro.0/sysroots/x86_64-oesdk-linux/usr/bin/arm-dhlinux-linux-gnueabi/arm-dhlinux-linux-gnueabi-gdb

[[Image:Qtcreator-add-debugger.jpg|850px]]

Add your Qt version by selecting the qmake located in /opt/dhlinux/nodistro.0/sysroots/x86_64-oesdk-linux/usr/bin/qmake

[[Image:Qtcreator-add-qt-version.jpg|850px]]

Add a new kit selecting your new Qt5 version and compiler and setting the sysroot to /opt/dhlinux/nodistro.0/sysroots/cortexa7t2hf-neon-vfpv4-dhlinux-linux-gnueabi and leave the Qt mkspec empty.
Finally select your device

[[Image:Qtcreator-add-kit.jpg|850px]]

If there is a warning/error shown, please click apply between each step

Add Yocto SDK with QT5 to QT Creator

2020-05-19T05:04:52Z

Mschmoeller: /* Download and install the SDK package */

Add Yocto SDK with QT5 to QT Creator

2020-05-15T05:30:28Z

Mschmoeller: /* Download and install the SDK package */

Add Yocto SDK with QT5 to QT Creator

2020-05-15T05:29:59Z

Mschmoeller: /* Prepairing your virtual machine */

The following instructions are based on '''DHCOM STM32MP1''' computer on module and Yocto version "zeus"
__TOC__

== Prepairing your virtual machine ==

Get the [[Virtual Machine for Application Development]].

Install the following package:

$ sudo apt-get install qtcreator qt5default

== Download and install the SDK package ==

Get the [[media:Dhlinux-glibc-x86_64-meta-toolchain-qt5-cortexa7t2hf-neon-vfpv4-toolchain-nodistro.0.zip|QT5 SDK for STM32mp1]]

Unpack the archive and install the toolchain.

$ sh ./dhlinux-glibc-x86_64-meta-toolchain-qt5-cortexa7t2hf-neon-vfpv4-toolchain-nodistro.0.sh

Choose the installation directory (default: /opt/dhlinux/nodistro.0/)

The toolchain is now installed to your system.

== Configure Qt Creator ==

Run QT Creator

In Qt Creator go to Tools > Options > Devices and add your Wandboard as a generic linux device.

[[Image:Qtcreator-add-device.jpg|550px]]

go to Tools > Options > Build & Run and:

Add a new c++ compiler. Select your compiler: /opt/dhlinux/nodistro.0/sysroots/x86_64-oesdk-linux/usr/bin/arm-dhlinux-linux-gnueabi/arm-dhlinux-linux-gnueabi-g++

[[Image:Qtcreator-add-compiler.jpg|850px]]

Add a new debugger. Select your debugger: /opt/dhlinux/nodistro.0/sysroots/x86_64-oesdk-linux/usr/bin/arm-dhlinux-linux-gnueabi/arm-dhlinux-linux-gnueabi-gdb

[[Image:Qtcreator-add-debugger.jpg|850px]]

Add your Qt version by selecting the qmake located in /opt/dhlinux/nodistro.0/sysroots/x86_64-oesdk-linux/usr/bin/qmake

[[Image:Qtcreator-add-qt-version.jpg|850px]]

Add a new kit selecting your new Qt5 version and compiler and setting the sysroot to /opt/dhlinux/nodistro.0/sysroots/cortexa7t2hf-neon-vfpv4-dhlinux-linux-gnueabi and leave the Qt mkspec empty.
Finally select your device

[[Image:Qtcreator-add-kit.jpg|850px]]

If there is a warning/error shown, please click apply between each step

Add Yocto SDK with QT5 to QT Creator

2020-05-15T05:29:45Z

Mschmoeller: /* Download and install the SDK package */

The following instructions are based on '''DHCOM STM32MP1''' computer on module and Yocto version "zeus"
__TOC__

== Prepairing your virtual machine ==

Get the [[Virtual Machine for Application Development]].

Install the following package:

$ sudo apt-get install qtcreator qt5default

== Download and install the SDK package ==

Get the [[media:Dhlinux-glibc-x86_64-meta-toolchain-qt5-cortexa7t2hf-neon-vfpv4-toolchain-nodistro.0.zip|QT5 SDK for STM32mp1]]

Unpack the archive and install the toolchain.

$ sh ./dhlinux-glibc-x86_64-meta-toolchain-qt5-cortexa7t2hf-neon-vfpv4-toolchain-nodistro.0.sh

Choose the installation directory (default: /opt/dhlinux/nodistro.0/)

The toolchain is now installed to your system.

== Configure Qt Creator ==

Run QT Creator

In Qt Creator go to Tools > Options > Devices and add your Wandboard as a generic linux device.

[[Image:Qtcreator-add-device.jpg|550px]]

go to Tools > Options > Build & Run and:

Add a new c++ compiler. Select your compiler: /opt/dhlinux/nodistro.0/sysroots/x86_64-oesdk-linux/usr/bin/arm-dhlinux-linux-gnueabi/arm-dhlinux-linux-gnueabi-g++

[[Image:Qtcreator-add-compiler.jpg|850px]]

Add a new debugger. Select your debugger: /opt/dhlinux/nodistro.0/sysroots/x86_64-oesdk-linux/usr/bin/arm-dhlinux-linux-gnueabi/arm-dhlinux-linux-gnueabi-gdb

[[Image:Qtcreator-add-debugger.jpg|850px]]

Add your Qt version by selecting the qmake located in /opt/dhlinux/nodistro.0/sysroots/x86_64-oesdk-linux/usr/bin/qmake

[[Image:Qtcreator-add-qt-version.jpg|850px]]

Add a new kit selecting your new Qt5 version and compiler and setting the sysroot to /opt/dhlinux/nodistro.0/sysroots/cortexa7t2hf-neon-vfpv4-dhlinux-linux-gnueabi and leave the Qt mkspec empty.
Finally select your device

[[Image:Qtcreator-add-kit.jpg|850px]]

If there is a warning/error shown, please click apply between each step

Add Yocto SDK with QT5 to QT Creator

2020-05-15T05:29:27Z

Mschmoeller: /* Download and install the SDK package */

The following instructions are based on '''DHCOM STM32MP1''' computer on module and Yocto version "zeus"
__TOC__

== Prepairing your virtual machine ==

Get the [[Virtual Machine for Application Development]].

Install the following package:

$ sudo apt-get install qtcreator qt5default

== Download and install the SDK package ==

Get the [[media:Dhlinux-glibc-x86_64-meta-toolchain-qt5-cortexa7t2hf-neon-vfpv4-toolchain-nodistro.0.zip|QT5 SDK for STM32mp1]]

Unpack the archive and install the toolchain.

$ sh ./dhlinux-glibc-x86_64-meta-toolchain-qt5-cortexa7t2hf-neon-vfpv4-toolchain-nodistro.0.sh

Choose the installation directory (default: /opt/dhlinux/nodistro.0/)

The toolchain is now installed to your system.

== Configure Qt Creator ==

Run QT Creator

In Qt Creator go to Tools > Options > Devices and add your Wandboard as a generic linux device.

[[Image:Qtcreator-add-device.jpg|550px]]

go to Tools > Options > Build & Run and:

Add a new c++ compiler. Select your compiler: /opt/dhlinux/nodistro.0/sysroots/x86_64-oesdk-linux/usr/bin/arm-dhlinux-linux-gnueabi/arm-dhlinux-linux-gnueabi-g++

[[Image:Qtcreator-add-compiler.jpg|850px]]

Add a new debugger. Select your debugger: /opt/dhlinux/nodistro.0/sysroots/x86_64-oesdk-linux/usr/bin/arm-dhlinux-linux-gnueabi/arm-dhlinux-linux-gnueabi-gdb

[[Image:Qtcreator-add-debugger.jpg|850px]]

Add your Qt version by selecting the qmake located in /opt/dhlinux/nodistro.0/sysroots/x86_64-oesdk-linux/usr/bin/qmake

[[Image:Qtcreator-add-qt-version.jpg|850px]]

Add a new kit selecting your new Qt5 version and compiler and setting the sysroot to /opt/dhlinux/nodistro.0/sysroots/cortexa7t2hf-neon-vfpv4-dhlinux-linux-gnueabi and leave the Qt mkspec empty.
Finally select your device

[[Image:Qtcreator-add-kit.jpg|850px]]

If there is a warning/error shown, please click apply between each step

Add Yocto SDK with QT5 to QT Creator

2020-05-14T08:04:33Z

Mschmoeller:

The following instructions are based on '''DHCOM STM32MP1''' computer on module and Yocto version "zeus"
__TOC__

== Prepairing your virtual machine ==

Get the [[Virtual Machine for Application Development]].

Install the following package:

$ sudo apt-get install qtcreator qt5default

== Download and install the SDK package ==

Get the [[Link]]

Unpack the archive and install the toolchain

$ sh ./dhlinux-glibc-x86_64-meta-toolchain-qt5-cortexa7t2hf-neon-vfpv4-toolchain-nodistro.0.sh

Choose the installation directory (default: /opt/dhlinux/nodistro.0/)

The toolchain is now installed to your system.

== Configure Qt Creator ==

Run QT Creator

In Qt Creator go to Tools > Options > Devices and add your Wandboard as a generic linux device.

[[Image:Qtcreator-add-device.jpg|550px]]

go to Tools > Options > Build & Run and:

Add a new c++ compiler. Select your compiler: /opt/dhlinux/nodistro.0/sysroots/x86_64-oesdk-linux/usr/bin/arm-dhlinux-linux-gnueabi/arm-dhlinux-linux-gnueabi-g++

[[Image:Qtcreator-add-compiler.jpg|850px]]

Add a new debugger. Select your debugger: /opt/dhlinux/nodistro.0/sysroots/x86_64-oesdk-linux/usr/bin/arm-dhlinux-linux-gnueabi/arm-dhlinux-linux-gnueabi-gdb

[[Image:Qtcreator-add-debugger.jpg|850px]]

Add your Qt version by selecting the qmake located in /opt/dhlinux/nodistro.0/sysroots/x86_64-oesdk-linux/usr/bin/qmake

[[Image:Qtcreator-add-qt-version.jpg|850px]]

Add a new kit selecting your new Qt5 version and compiler and setting the sysroot to /opt/dhlinux/nodistro.0/sysroots/cortexa7t2hf-neon-vfpv4-dhlinux-linux-gnueabi and leave the Qt mkspec empty.
Finally select your device

[[Image:Qtcreator-add-kit.jpg|850px]]

If there is a warning/error shown, please click apply between each step

Add Yocto SDK with QT5 to QT Creator

2020-05-14T08:04:10Z

Mschmoeller: Created page with "The following instructions are based on '''DHCOM STM32MP1''' computer on module and Yocto version "zeus" __TOC__ == Prepairing your virtual machine == Get the Virtual Mac..."

The following instructions are based on '''DHCOM STM32MP1''' computer on module and Yocto version "zeus"
__TOC__

== Prepairing your virtual machine ==

Get the [[Virtual Machine for Application Development]].

Install the following package:

$ sudo apt-get install qtcreator qt5default

== Download and install the SDK package ==

Get the [[Link]]

Unpack the archive and install the toolchain

$ sh ./dhlinux-glibc-x86_64-meta-toolchain-qt5-cortexa7t2hf-neon-vfpv4-toolchain-nodistro.0.sh

Choose the installation directory (default: /opt/dhlinux/nodistro.0/)

The toolchain is now installed to your system.

== Configure Qt Creator ==

Run QT Creator

In Qt Creator go to Tools > Options > Devices and add your Wandboard as a generic linux device.

[[Image:Qtcreator-add-device.jpg|850px]]

go to Tools > Options > Build & Run and:

Add a new c++ compiler. Select your compiler: /opt/dhlinux/nodistro.0/sysroots/x86_64-oesdk-linux/usr/bin/arm-dhlinux-linux-gnueabi/arm-dhlinux-linux-gnueabi-g++

[[Image:Qtcreator-add-compiler.jpg|850px]]

Add a new debugger. Select your debugger: /opt/dhlinux/nodistro.0/sysroots/x86_64-oesdk-linux/usr/bin/arm-dhlinux-linux-gnueabi/arm-dhlinux-linux-gnueabi-gdb

[[Image:Qtcreator-add-debugger.jpg|850px]]

Add your Qt version by selecting the qmake located in /opt/dhlinux/nodistro.0/sysroots/x86_64-oesdk-linux/usr/bin/qmake

[[Image:Qtcreator-add-qt-version.jpg|850px]]

Add a new kit selecting your new Qt5 version and compiler and setting the sysroot to /opt/dhlinux/nodistro.0/sysroots/cortexa7t2hf-neon-vfpv4-dhlinux-linux-gnueabi and leave the Qt mkspec empty.
Finally select your device

[[Image:Qtcreator-add-kit.jpg|850px]]

If there is a warning/error shown, please click apply between each step

File:Qtcreator-add-kit.jpg

2020-05-14T07:59:39Z

Mschmoeller:

File:Qtcreator-add-qt-version.jpg

2020-05-14T07:57:11Z

Mschmoeller:

File:Qtcreator-add-debugger.jpg

2020-05-14T07:55:29Z

Mschmoeller:

File:Qtcreator-add-compiler.jpg

2020-05-14T07:54:30Z

Mschmoeller:

File:Qtcreator-add-device.jpg

2020-05-14T07:52:08Z

Mschmoeller:

Yocto

2020-05-13T12:13:04Z

Mschmoeller: /* Example Configurations */

Building Qt5 using Yocto

2020-05-13T12:11:05Z

Mschmoeller: Mschmoeller moved page Building Qt5 using Yocto to Building Qt5 for i.MX6 using Yocto Dizzy

#REDIRECT [[Building Qt5 for i.MX6 using Yocto Dizzy]]

Building Qt5 for i.MX6 using Yocto Dizzy

2020-05-13T12:11:05Z

Mschmoeller: Mschmoeller moved page Building Qt5 using Yocto to Building Qt5 for i.MX6 using Yocto Dizzy

Please read the [[Yocto | Yocto tutorial]] before you proceed with building Qt5. The following instruction were tested on our '''DHCOM i.MX6''' computer on module with Yocto stable branch '''Dizzy'''

__TOC__

== Configure Sources ==

=== Clone meta-qt5 ===

Clone the stable branch dizzy of meta-qt5 inside the yocto/sources directory:

$ git clone -b dizzy https://github.com/meta-qt5/meta-qt5.git

Be sure to clone the same branch for meta-qt5 as you are using for the other layers!

=== Edit your yocto configuration files ===

1. Edit yocto/build/conf/bblayers.conf to add the meta-qt5 layer at the end:

${BSPDIR}/sources/meta-qt5 \
${BSPDIR}/sources/meta-openembedded/meta-ruby \
${BSPDIR}/sources/meta-openembedded/meta-multimedia \

2. Edit yocto/build/conf/local.conf and add:

<pre>
EXTRA_IMAGE_FEATURES = "debug-tweaks ssh-server-openssh "

IMAGE_INSTALL_append = " gcc g++ binutils libgcc libgcc-dev libstdc++ libstdc++-dev libstdc++-staticdev \
autoconf automake ccache chkconfig glib-networking glibmm \
packagegroup-core-buildessential pkgconfig \
boost cmake zlib glib-2.0 packagegroup-fsl-tools-testapps \
ruby \
cpufrequtils \
nano \
gdb \
gstreamer \
gst-meta-video \
gst-fsl-plugin \
gst-plugins-base-app \
gst-plugins-base \
gst-plugins-good \
gst-plugins-good-rtsp \
gst-plugins-good-udp \
gst-plugins-good-rtpmanager \
gst-plugins-good-rtp \
gst-plugins-good-video4linux2 \
openssh-sftp-server \
packagegroup-fsl-gstreamer \
packagegroup-fsl-tools-testapps \
packagegroup-fsl-tools-benchmark \
imx-vpu \
imx-test \
qtbase-fonts \
qtbase-plugins \
qtbase-tools \
qtbase-examples \
qtdeclarative \
qtdeclarative-plugins \
qtdeclarative-tools \
qtdeclarative-examples \
qtdeclarative-qmlplugins \
qtmultimedia \
qtmultimedia-plugins \
qtmultimedia-examples \
qtmultimedia-qmlplugins \
qtsvg \
qtsvg-plugins \
qtsensors \
qtimageformats-plugins \
qtsystems \
qtsystems-tools \
qtsystems-examples \
qtsystems-qmlplugins \
qtscript \
qt3d \
qt3d-examples \
qt3d-qmlplugins \
qt3d-tools \
qtwebkit \
qtwebkit-examples-examples \
qtwebkit-qmlplugins \
qtgraphicaleffects-qmlplugins \
qtconnectivity-qmlplugins \
qtlocation-plugins \
qtlocation-qmlplugins \
cinematicexperience \
cairo pango fontconfig freetype pulseaudio dbus \
alsa-lib alsa-tools alsa-state alsa-utils-alsaconf fsl-alsa-plugins \
i2c-tools \
"

</pre>

We include ssh-server-openssh in EXTRA_IMAGE_FEATURES and the openssh-sftp-server in IMAGE_INSTALL_append for rapid deploying using QtCreator

If you plan on using the 'core-image-minimal' image, then you must add 'dbus' to the IMAGE_INSTALL_append list.

If you plan to use Qt5 eglfs plugin for accelerated graphics using the framebuffer, you need to discard X11 and wayland so the proper graphics drivers get included and remove '''cairo''' because of X11 dependencies:

<pre>
DISTRO_FEATURES_remove = "x11 wayland"
</pre>

==== '''Bug''' in meta-fsl-demos: packagegroup-fsl-tools-testapps ====
Solution is already available:
* [https://github.com/Freescale/meta-fsl-demos/commit/eae8a8dd506855f9e12628d7071baade540aa2e4 packagegroup-fsl-tools-testapps: Only install GTK+3 demos when enabling X11]
* If packagegroup-fsl-tools-testapps is not required please remove it from <tt>IMAGE_INSTALL_append</tt> in <tt>local.conf</tt>

== Bitbake! ==

Bitbake an image like core-image-minimal (you need to be in your yocto/build directory):

<pre>
$ bitbake core-image-minimal
</pre>

Note: If bitbake fails with an error regarding cmake or drm recipes, locate their directories, delete them and try again. We discoverd this several times. There is no clean solution available at the moment.

== Test your image ==

Boot your image and run some Qt5 examples:

$ . /demo/path -platform eglfs

== Cross compile Qt5 for QtCreator ==

It is now very easy to build an environment for cross compilation using QtCreator. Version 1.7 in paths refers to Yocto Dizzy branch, if you are using different branch please use corresponding paths.

=== bitbake a meta-toolchain-qt5 ===

Bitbake a poky toolchain (you need to be in your yocto/build directory):

<pre>
$ bitbake meta-toolchain-qt5
</pre>

=== Install your new toolchain ===

Run the new installer that has been generated in yocto/build/tmp/deploy/sdk

$ sh poky-eglibc-x86_64-meta-toolchain-qt5-cortexa9hf-vfp-neon-toolchain-1.7.sh

This will install a cross compiler and its needed environment including the Qt5 arm libraries.

=== Configure Qt creator ===

Run qtcreator from the terminal after running the setup environment script located in /opt/poky/1.7

In QtCreator go to Tools > Options > Devices and add your Wandboard as a generic linux device.

go to Tools > Options > Build & Run and:
# Add a new compiler. Select your poky compiler: /opt/poky/1.7/sysroots/x86_64-pokysdk-linux/usr/bin/arm-poky-linux-gnueabi/arm-poky-linux-gnueabi-cpp
# Add your new cross compiled Qt version by selecting the qmake located in /opt/poky/1.7/sysroots/x86_64-pokysdk-linux/usr/bin/qt5
# Add a new kit selecting your new Qt5 version and compiler and setting the sysroot to /opt/poky/1.7/sysroots/cortexa9hf-vfp-neon-poky-linux-gnueabi and leave the Qt mkspec empty. Finally select your board for the device.

== External References ==
* The content of this tutorial heavily borrowed from [http://wiki.wandboard.org/Building_Qt5_using_yocto_on_Wandboard 'Building Qt5 using yocto on Wandboard']

Avenger96 Camera Support

2019-10-01T05:47:10Z

Mschmoeller:

== Introduction ==

The support for the CSI interface is not implemented in the Yocto sources yet. If you want to use the D3 camera mezzanine board, you need to do the following steps at first.

== Get the patches and implent them into your own Yocto source ==

Download the patch package: [[media:AV96_D3-camera-support.tar.xz|here]]
Copy the package content into the meta-av96 layer: meta-av96/recipes-bsp/linux-stm32mp/files

Edit the linux-stm32mp recipe (meta-av96/recipes-bsp/linux-stm32mp/linux-stm32mp_%.bbappend) and add the patch files.

For example :
SRC_URI += "file://0003-dts-pinctrl-enable-pull-up-on-dcmi-pins.patch"

Then rebuild your image.

== Test your image ==

If you want to easily check if your implementation works, apply the D3 camera mezzanine board to your AV96 board and boot your image.

After ST's demo launcher has started, click on the "camera preview" option.

Your patches have been applied correctly, if a camera window pops up.

Avenger96 Camera Support

2019-10-01T05:43:35Z

Mschmoeller: Created page with " == Introduction == The support for the CSI interface is not implemented in the Yocto sources yet. If you want to use the D3 camera mezzanine board, you need to do the follow..."

== Introduction ==

The support for the CSI interface is not implemented in the Yocto sources yet. If you want to use the D3 camera mezzanine board, you need to do the following steps at first.

== Get the patches and implent them into your own Yocto source ==

Download the patch package: [[media:AV96_D3-camera-support.tar.xz|here]]
Copy the package content into the meta-av96 layer: meta-av96/recipes-bsp/linux-stm32mp/files

Edit the linux-stm32mp recipe (meta-av96/recipes-bsp/linux-stm32mp/linux-stm32mp_%.bbappend) and add the patch files.

For example :
SRC_URI += "file://0003-dts-pinctrl-enable-pull-up-on-dcmi-pins.patch"

Then rebuild your image.

== Test your image ==

If you want to easily check if your implementation works, apply the D3 camera mezzanine board to your AV96 board and boot your image.
After ST's demo launcher has started, click on the "camera preview" option. Your patches have been applied correctly, if a camera window pops up.

Avenger96 Image Programming

2019-08-20T12:47:37Z

Mschmoeller:

== Introduction ==

This guide is about how to flash the AV96 board with STM32 Cube Programmer.

== Install STM32 Cube Programmer ==

Download the installer from the [https://www.st.com/en/development-tools/stm32cubeprog.html official STM32 Cube Programmer site].

Follow ST's installation instructions.

== Get the image ==

Build your own Yocto image by using the following source and on GitHub: [https://github.com/dh-electronics/meta-av96 AV96 Yocto Layer]

Instructions how to build the image can be found in the repository readme.

Once you have built your own AV96 Yocto image, your build provides all the files you need to use the Cube Programmer.

== Prepairing the target device ==

To get access to your target with the STM32 Cube Programmer you need to switch the AV96 boot mode to USB boot:

[[File:AV96USBBootswitch.png|700px]]

Then connect the USB-C interface of the AV96 board to your computer and power on your device.

== Programm the image with STM32 Cube Programmer ==

Start the STM32 Cube Programmer Tool.

If your device is connected correctly, you should be able to see the available USB Port:

[[File:AV96USBConnect.png|800px]]

If not, check your connection and boot mode configuration, then press the refresh button on the right.

Continue by clicking the green "Connect" button on the right.

[[File:AV96USBConnected.png|800px]]

Check the device informations on the right bottom side after a successful connection, then click on the "Open file" Header.

Choose the wanted flash layout from your Yocto build.

For example:
:''FlashLayout_nor-emmc_stm32mp157a-av96-basic.tsv'' (U-Boot -> NOR-SPI, Linux -> eMMC)

These layouts you can find in the following directory of your build:

:''$YOCTO_HOME/build-openstlinuxweston-stn32mp1-av96/tmp-glibc/deploy/images/stm32mp1-av96/flashlayout_av96-weston/''

[[File:AV96Flashlayout.png|800px]]

You should be able to see the files, destinations and address offsets which have to be programmed.

If you dont want them all to be flashed, unselect the checkboxes on the left of the wanted partition.

You need to choose the "Binaries path" of the images to be flashed by clicking on the browse button or fill it in manually.

For Yocto this is the following directory:

:''$YOCTO_HOME/build-openstlinuxweston-stn32mp1-av96/tmp-glibc/deploy/images/stm32mp1-av96''

At last click on "Download" to flash your device.

You will get a status message whether your flash process was successful or not.

If you want to boot your device please don't forget to switch the boot mode.

Avenger96 Image Programming

2019-08-20T12:37:20Z

Mschmoeller:

== Introduction ==

This guide is about how to flash the AV96 board with STM32 Cube Programmer.

== Install STM32 Cube Programmer ==

Download the installer from the [https://www.st.com/en/development-tools/stm32cubeprog.html official STM32 Cube Programmer site].

Follow ST's installation instructions.

== Get the images ==

Build your own Yocto image by using the following source and on GitHub: [https://github.com/dh-electronics/meta-av96 AV96 Yocto Layer]

Instructions how to build the image can be found in the repository readme.

Once you have built your own AV96 Yocto image, your build provides all the files you need to use the Cube Programmer.

== Prepairing the target device ==

To get access to your target with the STM32 Cube Programmer you need to switch the AV96 boot mode to USB boot:

[[File:AV96USBBootswitch.png|700px]]

Then connect the USB-C interface of the AV96 board to your computer and power on your device.

== Programm the image with STM32 Cube Programmer ==

Start the STM32 Cube Programmer Tool.

If your device is connected correctly, you should be able to see the available USB Port:

[[File:AV96USBConnect.png|800px]]

If not, check your connection and boot mode configuration, then press the refresh button on the right.

Continue by clicking the green "Connect" button on the right.

[[File:AV96USBConnected.png|800px]]

Check the device informations on the right bottom side after a successful connection, then click on the "Open file" Header.

Choose the wanted flash layout from your Yocto build
.
For example: FlashLayout_nor-emmc_stm32mp157a-av96-basic.tsv (U-Boot -> NOR-SPI, Linux -> eMMC)

These layouts you can find in the following directory of your build:

$YOCTO_HOME/build-openstlinuxweston-stn32mp1-av96/tmp-glibc/deploy/images/stm32mp1-av96/flashlayout_av96-weston/

[[File:AV96Flashlayout.png|800px]]

You should be able to see the files, destinations and address offsets which have to be programmed.

If you dont want them all to be flashed, unselect the checkboxes on the left of the wanted partition.

You need to choose the "Binaries path" of the images to be flashed by clicking on the browse button or fill it in manually.

For Yocto this is the following directory:

$YOCTO_HOME/build-openstlinuxweston-stn32mp1-av96/tmp-glibc/deploy/images/stm32mp1-av96

At last click on "Download" to flash your device.

You will get a status message whether your flash process was successful or not.

If you want to boot your device please don't forget to switch the boot mode.

File:AV96Flashlayout.png

2019-08-20T12:23:48Z

Mschmoeller:

File:AV96USBConnected.png

2019-08-20T12:17:43Z

Mschmoeller: Mschmoeller uploaded a new version of File:AV96USBConnected.png

File:AV96USBConnected.png

2019-08-20T12:12:08Z

Mschmoeller:

File:AV96USBConnect.png

2019-08-20T12:05:59Z

Mschmoeller:

Avenger96 Image Programming

2019-08-20T11:53:02Z

Mschmoeller: Created page with " == Introduction == This guide is about how to flash the AV96 board with STM32 Cube Programmer. == Install STM32 Cube Programmer == Download the installer from the [https:..."

File:AV96USBBootswitch.png

2019-08-20T11:45:48Z

Mschmoeller:

Yocto

2019-03-18T11:21:37Z

Mschmoeller:

Setup Yocto for Dizzy/Krogoth

2019-03-18T11:21:15Z

Mschmoeller: Created page with "== Setup Yocto Build System == ==== Install Required Host Packages ==== Install the required packages for your host development system. The Yocto Project documentation has..."

== Setup Yocto Build System ==

==== Install Required Host Packages ====

Install the required packages for your host development system. The Yocto Project documentation has a listing of install commands for many different linux host systems (Debian, Ubuntu, etc.).

[http://www.yoctoproject.org/docs/latest/ref-manual/ref-manual.html#required-packages-for-the-host-development-system Required Packages for the Host Development System]

==== Download and Install Google's repo utility ====

The BSP is based on the Yocto Project, which consists of a number of applicable metadata 'layers'. These are managed by the repo utility. 
$: mkdir ~/bin
$: curl http://commondatastorage.googleapis.com/git-repo-downloads/repo > ~/bin/repo
$: chmod a+x ~/bin/repo

==== Create the BSP directory to download all of the metadata for the BSP layers ====
Note: You can use your own BSP directory. In the following we use <code>~/fsl-community-bsp</code>
$: PATH=${PATH}:~/bin
$: cd
$: mkdir fsl-community-bsp
$: cd fsl-community-bsp

==== Initialize the repositories ====

The next step is to initialize the repositories. This establishes which branch of the repository will be used for your development. The ''master'' branch is the current development branch.

Note: The master branch is a development branch, not a stable branch. It is constantly changing with code updates, the adding of new features, and so forth.

For Dizzy use:
$: repo init -u https://github.com/Freescale/fsl-community-bsp-platform -b dizzy

For Krogoth use:
$: repo init -u https://github.com/Freescale/fsl-community-bsp-platform -b krogoth

==== Download all of the metadata for the BSP layers ====

$: repo sync

Once this has completed, you should have all of the metadata source of the Freescale Community BSP in fsl-community-bsp.

==== Add DHCOM i.MX6 BSP layer ====

To clone the OpenEmbedded / Yocto BSP layer for DHCOM i.MX6 execute the following steps:

$: cd fsl-community-bsp/sources

For Dizzy use:
$: git clone -b dizzy https://github.com/dh-electronics/meta-dhcom_imx6.git

For Krogoth use:
$: git clone -b krogoth https://github.com/dh-electronics/meta-dhcom_imx6.git

Edit <code>~/fsl-community-bsp/build/conf/bblayers.conf</code> (run bitbake once to create build directory, see 'Setup environment and build an image') to add the meta-dhcom_imx6 layer at the end:

${BSPDIR}/sources/meta-dhcom_imx6 \

== Setup environment and build an image ==

To start a build, first set the MACHINE shell environment variable to set the machine. These are: 
{| border="1" style="border-collapse:collapse; height:150px; width:500px; margin: 1em auto 1em auto;"
|+DHCOM i.MX6 Machines in Yocto
! Board Type !! HW !! MACHINE
|- align="left"
| DHCOM i.MX6 Solo || 200 || <code> dhcom2bimx6s </code> (former dhcomimx6s)
|- align="left"
| DHCOM i.MX6 DualLite || 200 || <code> dhcom2bimx6dl </code> (former dhcomimx6dl)
|- align="left"
| DHCOM i.MX6 Dual || 200 || <code> dhcom2bimx6d </code>
|- align="left"
| DHCOM i.MX6 Quad || 200 || <code> dhcom2bimx6q </code> (former dhcomimx6q)
|-
|
|- align="left"
| DHCOM i.MX6 Solo || 300 || <code> dhcom3bimx6s </code>
|- align="left"
| DHCOM i.MX6 DualLite || 300 || <code> dhcom3bimx6dl </code>
|- align="left"
| DHCOM i.MX6 Dual || 300 || <code> dhcom3bimx6d </code>
|- align="left"
| DHCOM i.MX6 Quad || 300 || <code> dhcom3bimx6q </code>
|-
|
|- align="left"
| DHCOM i.MX6 Solo || 400 || <code> dhcom4bimx6s </code> (new)
|- align="left"
| DHCOM i.MX6 DualLite || 400 || <code> dhcom4bimx6dl </code> (new)
|- align="left"
| DHCOM i.MX6 Dual || 400 || <code> dhcom4bimx6d </code> (new)
|- align="left"
| DHCOM i.MX6 Quad || 400 || <code> dhcom4bimx6q </code> (new)
|}

For example, if you have a DHCOM i.MX6 Duallite HW300, then use MACHINE "dhcom3bimx6dl".

Run the <code>setup-environment</code> script. This is a helper script which sets up the environment and creates a build directory for you. The first time you run this, you will be asked to accept the Freescale end user license agreement (EULA).

$: MACHINE=dhcom3bimx6dl source ./setup-environment build

Run bitbake with <code>core-image-minimal</code> as its argument. This will create a small image and should have the shortest possible build time. Note: all of the sources are downloaded from the internet and built from scratch. This includes the toolchain (gcc) and all of the native utilities, so building an image for the first time could take a few hours, depending on the performance of your host machine.

$: bitbake core-image-minimal

==== Locating the images and installing to a microSD card ====
Once the image is built successfully, there are several target images that are built by default. One of these is an image suitable for loading directly into an SD card. It contains all of the required binaries (bootloader, kernel, filesystem) in a preformatted binary image.

You can find the image at:

build/tmp/deploy/images/<MACHINE>/core-image-minimal-<MACHINE>.sdcard

The <code>.sdcard</code> image can be directly copied to an SD card with the <code>dd</code> command:

$ sudo dd if=tmp/deploy/images/<MACHINE>/core-image-minimal-<MACHINE>.sdcard of=/dev/sd<N> bs=1M

Note: '''<MACHINE>''' in the above corresponds to the MACHINE name provided to bitbake. '''"N"''' in the above command is the letter assigned to the SD card. This will vary depending on your host machine configuration.

==== Running the image on DHCOM i.MX6 ====
As this is just a console image, you will need a serial terminal program such as minicom in order to interact with the board and run commands. Simply plug the microSD card into the slot on the DHCOM i.MX6 module and apply power. You should immediately see log messages in the serial terminal. When complete, you should get a login prompt:

Poky (Yocto Project Reference Distro) 2.1.2 dhcom3bimx6dl /dev/ttymxc0 
dhcom3bimx6dl login:

The default login username is 'root' and there is no password.

=== Other interesting images ===

The image <code> core-image-minimal</code> builds relatively quickly due to its small size. It is a good image to test to see if your board works. There are other images that you can also try, but can take a good deal longer to build.

{| border="1" cellpadding="5" style="border-collapse:collapse; height:150px; margin: 1em auto 1em auto;"
! Image
! Description
|-
! core-image-base
| Basic image with kernel modules and other features
|-
! core-image-x11
| Basic image with X11 support
|-
! core-image-sato
| Image with Sato, a mobile environment and visual style for mobile devices. The image supports X11 with a Sato theme, Pimlico applications, and contains terminal, editor, and file manager.
|}

Yocto

2019-03-18T10:41:24Z

Mschmoeller: /* Setup Yocto Build System & Build Image */

Yocto

2019-03-18T10:39:40Z

Mschmoeller:

Yocto

2019-03-14T13:53:59Z

Mschmoeller:

For general information about the Yocto Project please refer to the official [https://www.yoctoproject.org/ Website]. "Yocto is not an embedded Linux distribution – it creates a custom one for you." This says that if you are using Yocto to build your system image '''you are the distributor'''. If you're not aware of what this means for you please contact us.

__TOC__

== Requirements hardware and software ==
* Linux-based (Debian/Ubuntu is recommended) host system to use for building Linux/Yocto
* min 4GB RAM / > 8GB RAM are recommended
* disk space (depending on image to build about 80 GB)
* a microSD card-reader to write the generated image to the microSD card

== Supported Stable Branch ==
With our OpenEmbedded / Yocto BSP Layer for DHCOM i.MX6 we support the following branches:

{| border="1" style="border-collapse:collapse; height:75px; width:300px;"
! Name !! Version
|- align="center"
| Dizzy || 1.7
|- align="center"
| Krogoth || 2.1
|- align="center"
| Thud (i.MX6ull only)|| 2.6
|}

Our BSP layer is based on the Freescale Community BSP.

More information about Yocto stable branch maintenance at [https://wiki.yoctoproject.org/wiki/Stable_branch_maintenance https://wiki.yoctoproject.org/]

== Setup Yocto Build System (Thud - i.MX6ull only) ==

==== Install Required Host Packages ====

Install the required packages for your host development system. The Yocto Project documentation has a listing of install commands for many different linux host systems (Debian, Ubuntu, etc.).

[http://www.yoctoproject.org/docs/latest/ref-manual/ref-manual.html#required-packages-for-the-host-development-system Required Packages for the Host Development System]

==== Download and Install Google's repo utility ====

The BSP is based on the Yocto Project, which consists of a number of applicable metadata 'layers'. These are managed by the repo utility. 
$: mkdir ~/bin
$: curl http://commondatastorage.googleapis.com/git-repo-downloads/repo > ~/bin/repo
$: chmod a+x ~/bin/repo

==== Create the BSP directory to download all of the metadata for the BSP layers ====
Note: You can use your own BSP directory. In the following we use <code>~/dhcom-yocto-bsp</code>
$: PATH=${PATH}:~/bin
$: cd
$: mkdir dhcom-yocto-bsp
$: cd dhcom-yocto-bsp

==== Initialize the repositories ====

For Thud:
$: repo init -u https://github.com/dh-electronics/dhcom_imx6-bsp-platform -b thud

==== Download all of the metadata for the BSP layers ====

$: repo sync

Once this has completed, you should have all of the metadata source of DHCOM and Freescale Community BSP in dhcom-yocto-bsp.

== Setup environment and build an image (Thud- i.MX6ull only) ==

start a build, first set the MACHINE shell environment variable to set the machine. These are: 
{| border="1" style="border-collapse:collapse; height:150px; width:500px; margin: 1em auto 1em auto;"
|+DHCOM i.MX6 Machines in Yocto
! Board Type !! HW !! MACHINE
|- align="left"
| DHCOM i.MX6 ULL|| 100 || <code> dhcom1bimx6ull </code>
|}

For example, if you have a DHCOM i.MX6 Duallite HW300, then use MACHINE "dhcom3bimx6dl".

Run the <code>setup-environment</code> script. This is a helper script which sets up the environment and creates a build directory for you. The first time you run this, you will be asked to accept the Freescale end user license agreement (EULA).

$: MACHINE=dhcom1bimx6ull source ./setup-environment build

Run bitbake with <code>core-image-minimal</code> as its argument. This will create a small image and should have the shortest possible build time. Note: all of the sources are downloaded from the internet and built from scratch. This includes the toolchain (gcc) and all of the native utilities, so building an image for the first time could take a few hours, depending on the performance of your host machine.

$: bitbake core-image-minimal

==== Locating the images and installing to a microSD card ====
Once the image is built successfully, there are several target images that are built by default. One of these is an image suitable for loading directly into an SD card. It contains all of the required binaries (bootloader, kernel, filesystem) in a preformatted binary image.

You can find the image at:

build/tmp/deploy/images/<MACHINE>/core-image-minimal-<MACHINE>.wic.gz
The <code>.wic.gz</code> image can be unziped with <code>gunzip</code> and copied to an SD card with the <code>dd</code> command:

$ gunzip -c tmp/deploy/images/<MACHINE>/core-image-minimal-<MACHINE>.wic.gz | sudo dd of=/dev/sd<N> bs=1M iflag=fullblock oflag=direct conv=fsync status=progress

Note: '''<MACHINE>''' in the above corresponds to the MACHINE name provided to bitbake. '''"N"''' in the above command is the letter assigned to the SD card. This will vary depending on your host machine configuration.

== Setup Yocto Build System (Krogoth & Dizzy) ==

==== Install Required Host Packages ====

Install the required packages for your host development system. The Yocto Project documentation has a listing of install commands for many different linux host systems (Debian, Ubuntu, etc.).

[http://www.yoctoproject.org/docs/latest/ref-manual/ref-manual.html#required-packages-for-the-host-development-system Required Packages for the Host Development System]

==== Download and Install Google's repo utility ====

The BSP is based on the Yocto Project, which consists of a number of applicable metadata 'layers'. These are managed by the repo utility. 
$: mkdir ~/bin
$: curl http://commondatastorage.googleapis.com/git-repo-downloads/repo > ~/bin/repo
$: chmod a+x ~/bin/repo

==== Create the BSP directory to download all of the metadata for the BSP layers ====
Note: You can use your own BSP directory. In the following we use <code>~/fsl-community-bsp</code>
$: PATH=${PATH}:~/bin
$: cd
$: mkdir fsl-community-bsp
$: cd fsl-community-bsp

==== Initialize the repositories ====

The next step is to initialize the repositories. This establishes which branch of the repository will be used for your development. The ''master'' branch is the current development branch.

Note: The master branch is a development branch, not a stable branch. It is constantly changing with code updates, the adding of new features, and so forth.

For Dizzy use:
$: repo init -u https://github.com/Freescale/fsl-community-bsp-platform -b dizzy

For Krogoth use:
$: repo init -u https://github.com/Freescale/fsl-community-bsp-platform -b krogoth

==== Download all of the metadata for the BSP layers ====

$: repo sync

Once this has completed, you should have all of the metadata source of the Freescale Community BSP in fsl-community-bsp.

==== Add DHCOM i.MX6 BSP layer ====

To clone the OpenEmbedded / Yocto BSP layer for DHCOM i.MX6 execute the following steps:

$: cd fsl-community-bsp/sources

For Dizzy use:
$: git clone -b dizzy https://github.com/dh-electronics/meta-dhcom_imx6.git

For Krogoth use:
$: git clone -b krogoth https://github.com/dh-electronics/meta-dhcom_imx6.git

Edit <code>~/fsl-community-bsp/build/conf/bblayers.conf</code> (run bitbake once to create build directory, see 'Setup environment and build an image') to add the meta-dhcom_imx6 layer at the end:

${BSPDIR}/sources/meta-dhcom_imx6 \

== Setup environment and build an image (Krogoth & Dizzy) ==

To start a build, first set the MACHINE shell environment variable to set the machine. These are: 
{| border="1" style="border-collapse:collapse; height:150px; width:500px; margin: 1em auto 1em auto;"
|+DHCOM i.MX6 Machines in Yocto
! Board Type !! HW !! MACHINE
|- align="left"
| DHCOM i.MX6 Solo || 200 || <code> dhcom2bimx6s </code> (former dhcomimx6s)
|- align="left"
| DHCOM i.MX6 DualLite || 200 || <code> dhcom2bimx6dl </code> (former dhcomimx6dl)
|- align="left"
| DHCOM i.MX6 Dual || 200 || <code> dhcom2bimx6d </code>
|- align="left"
| DHCOM i.MX6 Quad || 200 || <code> dhcom2bimx6q </code> (former dhcomimx6q)
|-
|
|- align="left"
| DHCOM i.MX6 Solo || 300 || <code> dhcom3bimx6s </code>
|- align="left"
| DHCOM i.MX6 DualLite || 300 || <code> dhcom3bimx6dl </code>
|- align="left"
| DHCOM i.MX6 Dual || 300 || <code> dhcom3bimx6d </code>
|- align="left"
| DHCOM i.MX6 Quad || 300 || <code> dhcom3bimx6q </code>
|-
|
|- align="left"
| DHCOM i.MX6 Solo || 400 || <code> dhcom4bimx6s </code> (new)
|- align="left"
| DHCOM i.MX6 DualLite || 400 || <code> dhcom4bimx6dl </code> (new)
|- align="left"
| DHCOM i.MX6 Dual || 400 || <code> dhcom4bimx6d </code> (new)
|- align="left"
| DHCOM i.MX6 Quad || 400 || <code> dhcom4bimx6q </code> (new)
|}

For example, if you have a DHCOM i.MX6 Duallite HW300, then use MACHINE "dhcom3bimx6dl".

Run the <code>setup-environment</code> script. This is a helper script which sets up the environment and creates a build directory for you. The first time you run this, you will be asked to accept the Freescale end user license agreement (EULA).

$: MACHINE=dhcom3bimx6dl source ./setup-environment build

Run bitbake with <code>core-image-minimal</code> as its argument. This will create a small image and should have the shortest possible build time. Note: all of the sources are downloaded from the internet and built from scratch. This includes the toolchain (gcc) and all of the native utilities, so building an image for the first time could take a few hours, depending on the performance of your host machine.

$: bitbake core-image-minimal

==== Locating the images and installing to a microSD card ====
Once the image is built successfully, there are several target images that are built by default. One of these is an image suitable for loading directly into an SD card. It contains all of the required binaries (bootloader, kernel, filesystem) in a preformatted binary image.

You can find the image at:

build/tmp/deploy/images/<MACHINE>/core-image-minimal-<MACHINE>.sdcard

The <code>.sdcard</code> image can be directly copied to an SD card with the <code>dd</code> command:

$ sudo dd if=tmp/deploy/images/<MACHINE>/core-image-minimal-<MACHINE>.sdcard of=/dev/sd<N> bs=1M

Note: '''<MACHINE>''' in the above corresponds to the MACHINE name provided to bitbake. '''"N"''' in the above command is the letter assigned to the SD card. This will vary depending on your host machine configuration.

==== Running the image on DHCOM i.MX6 ====
As this is just a console image, you will need a serial terminal program such as minicom in order to interact with the board and run commands. Simply plug the microSD card into the slot on the DHCOM i.MX6 module and apply power. You should immediately see log messages in the serial terminal. When complete, you should get a login prompt:

Poky (Yocto Project Reference Distro) 2.1.2 dhcom3bimx6dl /dev/ttymxc0 
dhcom3bimx6dl login:

The default login username is 'root' and there is no password.

=== Other interesting images ===

The image <code> core-image-minimal</code> builds relatively quickly due to its small size. It is a good image to test to see if your board works. There are other images that you can also try, but can take a good deal longer to build.

{| border="1" cellpadding="5" style="border-collapse:collapse; height:150px; margin: 1em auto 1em auto;"
! Image
! Description
|-
! core-image-base
| Basic image with kernel modules and other features
|-
! core-image-x11
| Basic image with X11 support
|-
! core-image-sato
| Image with Sato, a mobile environment and visual style for mobile devices. The image supports X11 with a Sato theme, Pimlico applications, and contains terminal, editor, and file manager.
|}

== Example Configurations ==

*'''[[Building Qt5 using Yocto | Building Qt5 using Yocto]]'''
*'''[[Building Chromium, VLC and X11VNC using Yocto | Building Chromium, VLC and X11VNC using Yocto]]'''

== External References ==
* The content of this tutorial heavily borrowed from [http://wiki.wandboard.org/Getting_started_with_Yocto_on_Wandboard i.MX6 Wandboard Wiki 'Getting started with Yocto on Wandboard']
* Have a look at [http://wiki.wandboard.org/Building_Qt5_using_yocto_on_Wandboard 'Building Qt5 using yocto on Wandboard'] to get information for adding Qt5
* Documentation of the latest [https://www.yoctoproject.org/documentation Yocto Project Releases]
* More additional information on [https://community.freescale.com/docs/DOC-1616 Freescale Yocto Project Main-Page]