Bureaucrats, dave_user, Administrators
8,147
edits
Changes
no edit summary
{{Applies To Bora}}
{{Applies To BoraLite}}
{{AppliesToBORA Lite AN}}
{{Applies To BoraX}}
{{InfoBoxBottom}}
{{WarningMessage|text=This application note was validated against specific versions of the kit only. It may not work with other versions. Supported versions are listed in the ''History'' section.}}
{{ImportantMessage|text=It is assumed to use ZYNQ SOC with <b><i>speed grade -1</i></b> (even using command line script or GUI). In any case, there are no issues using <b><i>speed grade -3</i></b> SOC provided with BELK kit}}
==History==
|-
|1.0.0
|15:03, 4 September 2015 (CEST)
|[[Bora_Embedded_Linux_Kit_(BELK)#BELK_software_components|2.2.0]]
|First release
|-
|2.0.0
|10:21, 9 November 2015 (CET)
|[[Bora_Embedded_Linux_Kit_(BELK)#BELK_software_components|2.2.0, 3.0.0]]
|Added support for BoraX/BoraXEVB platform
|-
|{{oldid|8292|2.0.1}}
|11:53, 13 March 2017 (CET)
|[[Bora_Embedded_Linux_Kit_(BELK)#BELK_software_components|2.2.0, 3.0.0]]
|Added info for installing Qt on rfs using <code>smart</code>
|-
|3.0.0
|TBDJanuary 2020
|[[Bora_Embedded_Linux_Kit_(BELK)#BELK_software_components|4.1.0 / 2.1.0]]
|Migrated AN migration to BELK 4.1.0 / BXELK 2.1.0
|-
|}
To implement frame buffer, a portion of main SDRAM is used. This area is allocated at runtime by linux frame buffer driver. Even if LCD is 18 bpp, each pixel is represented by 32-bit word in memory. In fact each pixel is in RGB666 format, so for each colour only the six most significant bits of the frame buffer RGB888 are used to drive the display.
The Vivado project can also be build with the procedure explained [[Creating_and_building_example_Vivado_project_(BELK/BXELK)#Command_line_based_procedure|here]].
===Bora + BoraEVB===
|}
The Vivado project can also be build with the procedure explained [[Creating_and_building_example_Vivado_project_(*BELK/BXELK) This signal is used to control backlight. It is usually driven by a PWM signal whose duty cycle is proportional to backlight intensity. For #Command_line_based_procedure|here]] with the sake of simplicity, in this project this signal is driven by a GPIO, thus only two intensity levels are supported (0% and 100%).following modifications:*<code>export BASE_NAME bora_LVDS</code>*<code>export U-BOOT_PS7_DIR bora</code>
===BoraLite + Adapter + BoraXEVB===
|-
|}
(*) This signal is used to control backlight. It is usually driven by a PWM signal whose duty cycle is proportional to backlight intensity. For the sake of simplicity, in this project this signal is driven by a GPIO, thus only two intensity levels are supported (0% and 100%). This is a CMOS 2.5V level signal. Make sure that voltage levels of this signal are compatible with LCD backlight input.<br>
(**) On the adapter this signal is routed (via configurable 0R) to multiple pins of the EVB connector to meet all the features of the EVB. Please make sure to configure the Adapter for the use of the LVDS connector.
The Vivado project can also be build with the procedure explained [[Creating_and_building_example_Vivado_project_(BELK/BXELK)#Command_line_based_procedure|here]] with the following modifications:
*<code>export BASE_NAME boralite_LVDS</code>
*<code>export U-BOOT_PS7_DIR bora</code>
==== BoraLiteAdapter BLADP0000R0R ====
|}
==Enabling frame buffer driver in linux kernel==
U-boot:
Kernel and device tree can also be built with the following procedure:
* update Bora kernel repository (as described [[Bora_Embedded_Linux_Kit_(BELK)/BXELK_software_components#Updating_the_repositories_from_BELK_2.1.0_to_BELK_2.2.0Updating_git_repositories|here]]) '''TODO''': update repo???
* the default KIT binary files of kernel (uImage) can be used.
* build the <code>bora-an004.dtb</code> devicetree
Install root file system on second (ext4) partition of your BELK SD card (firstly deleting all previous rfs files):
* get rfs image [httpshttp://mirror.dave.eu/bora/belk-34.1.0.1/belk-34.01.1_bora0_dave-image-devel-bora.tar.gz bz2 here]
Insert the SD card into Bora/BoraX EVB and turn on the board.
Once the kernel has completed boot, frame buffer can be accessed from user space applications via <code>/dev/fb0</code> device file (for more details please refer to https://www.kernel.org/doc/Documentation/fb/framebuffer.txt).
=== Pre-built binaries ===
* For Bora SoM use:
** [http://mirror.dave.eu/bora/belk-4.1.0/belk-4.1.0_uImage uImage]
** [http://mirror.dave.eu/bora/belk-4.1.0/belk-4.1.0_bora-an004.dtb dtb]
** [http://mirror.dave.eu/bora/belk-4.1.0/belk-4.1.0_bora_LVDS_fpga.bin fpga]
* For BoraLite SoM use:
** [http://mirror.dave.eu/bora/belk-4.1.0/belk-4.1.0_uImage uImage]
** [http://mirror.dave.eu/bora/belk-4.1.0/belk-4.1.0_bora-an004.dtb dtb]
** [http://mirror.dave.eu/bora/belk-4.1.0/belk-4.1.0_boralite_LVDS_fpga.bin fpga]
* For BoraX SoM use:
** [http://mirror.dave.eu/bora/belk-4.1.0/belk-4.1.0_uImage uImage]
** [http://mirror.dave.eu/bora/belk-4.1.0/belk-4.1.0_bora-an004.dtb dtb]
** [http://mirror.dave.eu/bora/belk-4.1.0/belk-4.1.0_borax_LVDS_fpga.bin fpga]
=== How to install test tools for LCD device ===
root@bora:~# smart update
* install Qt the <code>tslib</code> required packages using <code>smart</code>
root@bora:~# smart install tslib-calibrate-1.1-r0
