DHCOM Settings: Difference between revisions

From Wiki-DB
Jump to navigationJump to search
← Older edit
Lzenz (talk | contribs)
635 edits
Lzenz (talk | contribs)
635 edits
 
(25 intermediate revisions by 2 users not shown)
Line 2: Line 2:


The hardware settings are configured with the DHCOM settings binary-file stored in the flash memory. This allows you to customize the hardware-settings without recompiling the bootloader. The settings-binary contains the following configuration options:
The hardware settings are configured with the DHCOM settings binary-file stored in the flash memory. This allows you to customize the hardware-settings without recompiling the bootloader. The settings-binary contains the following configuration options:
:[[Image:DHCOM Settings Block.png|1000px]]
 
'''Version 1: VALIDATION_ID = "DH"'''
Supported from all DHCOM modules.
:[[Image:DHCOM Settings Block.png|1500px]]
 
'''Please note:''' Each row of the diagram is treated like a 32-bit unsigned integer value. Please consider that the memory layout is little endian.


Supported by  
Supported by  
* U-Boot DH VERSION v1.11.0.1 or higher for iMX25
* U-Boot DH VERSION v1.11.0.1 or higher for iMX25
* U-Boot DH VERSION v0.7.0.0 or higher for AM35x
* U-Boot DH VERSION v0.7.0.0 or higher for AM35x
'''Version 2: VALIDATION_ID = "V2"'''
Supported from i.MX6 or newer DHCOM modules.
:[[Image:DHCOM_Settings_Block_V2.png|1500px]]
Supported by
* U-Boot DH VERSION v0.4.2.4 or higher for iMX6


== Create a customized settings-block ==
== Create a customized settings-block ==
Line 14: Line 26:
The easy way is to use the '''DHCOM Settings.bin Generator.''' If you use this tool you don´t have to bother about the layout of the binary. You can edit your settings in a easy to understand GUI. This tool provides you additional help through tooltips which appear if you move the mouse-pointer over a input element. You don't have to start from scratch. So called configuration-files are available to load predefined configurations from a xml structure. It is possible to store your own settings in a configuration-file to reuse them later for another board.   
The easy way is to use the '''DHCOM Settings.bin Generator.''' If you use this tool you don´t have to bother about the layout of the binary. You can edit your settings in a easy to understand GUI. This tool provides you additional help through tooltips which appear if you move the mouse-pointer over a input element. You don't have to start from scratch. So called configuration-files are available to load predefined configurations from a xml structure. It is possible to store your own settings in a configuration-file to reuse them later for another board.   


==== System requirements to run the DHCOM Settings.bin Generator ====
==== System requirements to run the DHCOM Settings.bin Generator on your PC ====
* Microsoft Windows
* Microsoft Windows
* .NET Framework 2.0
* .NET Framework 2.0
Line 21: Line 33:
Here you can download the current version of the '''DHCOM Settings.bin Generator''':
Here you can download the current version of the '''DHCOM Settings.bin Generator''':


* [[media:DHCOMSettingsBinGenerator1v5.zip|Download DHCOM Settings.bin Generator v1.5.0.0]]
* [[media:DHCOMSettingsGeneratorV2_V2.0.0.2.zip|Download DHCOM Settings.bin Generator v2.0.0.2]]


Available '''configuration-files''':
Available '''configuration-files''':
Line 32: Line 44:
! Settings Name: !! Description: !! Unit:  
! Settings Name: !! Description: !! Unit:  
|-
|-
| VALIDATION_ID ||„DH“ ||
| VALIDATION_ID ||„DH“ or <span style="color:red"> "V2" </span>||
|-
|-
| DISPLAY_ID|| unique ID of Display ||
| DISPLAY_ID|| unique ID of Display ||
Line 42: Line 54:
| Y_RESOLUTION || Display y resolution || pixel
| Y_RESOLUTION || Display y resolution || pixel
|-
|-
| PIXEL_CLOCK || Pixel clock || kHz
| PIXEL_CLOCK || Pixel clock <span style="color:red"> supports more than 16bit with "V2" </span>|| kHz
|-
|-
| LCD_CONFIG_FLAGS || LCD Configuration Register || see description
| LCD_CONFIG_FLAGS || LCD Configuration Register / <span style="color:red"> Added new parameters with "V2" </span> || see description
|-
|-
| HSW || Horizontal synchronization pulse width || pixel clocks
| HSW || Horizontal synchronization pulse width || pixel clocks
Line 91: Line 103:


===='' DHCOM AM35 ''====
===='' DHCOM AM35 ''====
The clock-source of the pixel-clock runs with 432.0 MHz. The divider has to be greater or equal 1.
The clock-source of the pixel-clock runs with 86.4 MHz. The divider has to be greater or equal 1.


'''Be aware of the fact if you choose a pixel-clock between two possible values the smaller value will be used.'''
'''UBoot Version <= 1.2.0.3: If you choose a pixel-clock between two possible values the next higher value is used.'''
 
'''UBoot Version >= 1.2.0.4: If you choose a pixel-clock between two possible values the next lower value is used.'''


== LCD_CONFIG_FLAGS description: ==
== LCD_CONFIG_FLAGS description: ==
Line 117: Line 131:
|-
|-
|IBL || Inverted Backlight Enable || 0 active high / 1 active low
|IBL || Inverted Backlight Enable || 0 active high / 1 active low
|-
|<span style="color:red"> BL_ON </span> ||<span style="color:red"> Backlight default state </span> ||<span style="color:red"> 0 backlight off / 1 backlight on </span>
|-
|<span style="color:red"> DI_TYPE </span> ||<span style="color:red"> Display output Type </span> ||<span style="color:red"> 0 Ignore DHCOM Display settings (Don’t commit parameters to OS) / 1 Headless (Disp. Interf. deact.) / 2 RGB / 3 LVDS0 / 4 LVDS1 / 5 Dual Chan LVDS / 6 HDMI / 7 rffu …  </span>
|-
|<span style="color:red"> NEXT_DI </span> ||<span style="color:red"> Additional display available </span> ||<span style="color:red"> 0 No / 1 Additional display settings block attached </span>
|}
|}


Line 131: Line 151:
|-
|-
|GPIO_I_DIR || DHCOM GPIO_I direction || 1 input / 0 output
|GPIO_I_DIR || DHCOM GPIO_I direction || 1 input / 0 output
|-
|GPIO_J_DIR || DHCOM GPIO_J direction (camera interface) || 1 input / 0 output
|-
|… || ||
|-
|GPIO_W_DIR || DHCOM GPIO_W direction (camera interface) || 1 input / 0 output
|-
|-
|}
|}
'''Please note:''' If you own a DHeva01 428-100 or a DHeva01 428-200 you have to enable the USB-OTG power with configuring the DHCOM GPIO_B as an output with initial state high to use the USB-OTG port. Newer versons of DHeva01 are not affected.


== GPIO_STATE description: ==
== GPIO_STATE description: ==
Line 146: Line 174:
|-
|-
|GPIO_I_STATE || DHCOM GPIO_I default state if dir = output || 1 high / 0 low
|GPIO_I_STATE || DHCOM GPIO_I default state if dir = output || 1 high / 0 low
|-
|GPIO_J_STATE || DHCOM GPIO_J default state if dir = output (camera interface) || 1 high / 0 low
|-
|… || ||
|-
|GPIO_W_STATE || DHCOM GPIO_W default state if dir = output (camera interface) || 1 high / 0 low
|-
|-
|}
|}
'''Please note:''' If you own a DHeva01 428-100 or a DHeva01 428-200 you have to enable the USB-OTG power with configuring the DHCOM GPIO_B as an output with initial state high to use the USB-OTG port. Newer versons of DHeva01 are not affected.


== HW_CONFIG_FLAGS description: ==
== HW_CONFIG_FLAGS description: ==
Line 172: Line 208:
|-
|-
|DIS_CON || Disable Bootloader console on FFUART || 0 console enabled / 1 console disabled
|DIS_CON || Disable Bootloader console on FFUART || 0 console enabled / 1 console disabled
|-
|DISP_ADPT_EE_CHK || Enable display-adapter EEPROM check for display-settings || 0 don’t check EEPROM for DH settings / 1 check EEPROM for DH settings
|-
|-
|}
|}

Latest revision as of 13:59, 4 March 2016

The hardware settings are configured with the DHCOM settings binary-file stored in the flash memory. This allows you to customize the hardware-settings without recompiling the bootloader. The settings-binary contains the following configuration options:

Version 1: VALIDATION_ID = "DH" Supported from all DHCOM modules.

Please note: Each row of the diagram is treated like a 32-bit unsigned integer value. Please consider that the memory layout is little endian.

Supported by

  • U-Boot DH VERSION v1.11.0.1 or higher for iMX25
  • U-Boot DH VERSION v0.7.0.0 or higher for AM35x

Version 2: VALIDATION_ID = "V2" Supported from i.MX6 or newer DHCOM modules.

Supported by

  • U-Boot DH VERSION v0.4.2.4 or higher for iMX6

Create a customized settings-block

The hard way to create a settings binary is to use a hex-editor and create a file with the memory-layout as shown above.

The easy way is to use the DHCOM Settings.bin Generator. If you use this tool you don´t have to bother about the layout of the binary. You can edit your settings in a easy to understand GUI. This tool provides you additional help through tooltips which appear if you move the mouse-pointer over a input element. You don't have to start from scratch. So called configuration-files are available to load predefined configurations from a xml structure. It is possible to store your own settings in a configuration-file to reuse them later for another board.

System requirements to run the DHCOM Settings.bin Generator on your PC

  • Microsoft Windows
  • .NET Framework 2.0

Download

Here you can download the current version of the DHCOM Settings.bin Generator:

Available configuration-files:

Settings Block description:

Settings Name: Description: Unit:
VALIDATION_ID „DH“ or "V2"
DISPLAY_ID unique ID of Display
LENGTH Length of the settings block
X_RESOLUTION Display x resolution pixel
Y_RESOLUTION Display y resolution pixel
PIXEL_CLOCK Pixel clock supports more than 16bit with "V2" kHz
LCD_CONFIG_FLAGS LCD Configuration Register / Added new parameters with "V2" see description
HSW Horizontal synchronization pulse width pixel clocks
VSW Vertical synchronisation pulse width line clocks
HFP Horizontal front porch pixel clocks
HBP Horizontal back porch pixel clocks
VFP Vertical front porch line clocks
VBP Vertical back porch line clocks
DATALINES count of datalines number of datalines
ACB AC Bias frequency
ACBI AC Bias transitions per interrupt
GPIO_DIR DHCOM GPIO default direction register see description
GPIO_STATE DHCOM GPIO default state register see description
HW_CONFIG_FLAGS Hardware Configuration Register see description

Remark: How to choose a PIXEL_CLOCK:

DHCOM iMX25

The frequency of the clock-source for the pixel clock is 66.5 MHz. The divider has to be greater or equal 2. Only the following pixel clock frequencies are possible:

  • 33.250MHz
  • 22.167MHz
  • 16.625MHz
  • 13.300MHz
  • 11.083MHz
  • 9.500MHz
  • 8.312MHz
  • 7.389MHz
  • 6.650MHz
  • ...

Be aware of the fact if you choose a pixel-clock between two possible values the smaller value will be used.

DHCOM AM35

The clock-source of the pixel-clock runs with 86.4 MHz. The divider has to be greater or equal 1.

UBoot Version <= 1.2.0.3: If you choose a pixel-clock between two possible values the next higher value is used.

UBoot Version >= 1.2.0.4: If you choose a pixel-clock between two possible values the next lower value is used.

LCD_CONFIG_FLAGS description:

Settings Name: Description: Unit:
IVS Inverted Vertical Sync Pulse 0 active high / 1 active low
IHS Inverted Horizontal Sync 0 active high / 1 active low
IPC Inverted Pixel Clock 0 Data is sampled on rising edge / 1 Data is sampled on falling edge
IOE Inverted Output Enable 0 active high / 1 active low
IDATA Inverted Data 0 active high / 1 active low
ACT_PAS Active or passiv matrix display 0 passiv / 1active
PWM_POL PWM polarity 0 low state backlight off and high state backlight on / 1 low state backlight on and high state backlight off
BL_EN_GPIO Backlight enable GPIO number 0 no backlight enable GPIO / 1 DHCOM GPIO_A / 2 DHCOM GPIO_B / … / 9 = DHCOM GPIO_I
IBL Inverted Backlight Enable 0 active high / 1 active low
BL_ON Backlight default state 0 backlight off / 1 backlight on
DI_TYPE Display output Type 0 Ignore DHCOM Display settings (Don’t commit parameters to OS) / 1 Headless (Disp. Interf. deact.) / 2 RGB / 3 LVDS0 / 4 LVDS1 / 5 Dual Chan LVDS / 6 HDMI / 7 rffu …
NEXT_DI Additional display available 0 No / 1 Additional display settings block attached

GPIO_DIR description:

Settings Name: Description: Unit:
GPIO_A_DIR DHCOM GPIO_A direction 1 input / 0 output
GPIO_B_DIR DHCOM GPIO_B direction 1 input / 0 output
…
GPIO_I_DIR DHCOM GPIO_I direction 1 input / 0 output
GPIO_J_DIR DHCOM GPIO_J direction (camera interface) 1 input / 0 output
…
GPIO_W_DIR DHCOM GPIO_W direction (camera interface) 1 input / 0 output

Please note: If you own a DHeva01 428-100 or a DHeva01 428-200 you have to enable the USB-OTG power with configuring the DHCOM GPIO_B as an output with initial state high to use the USB-OTG port. Newer versons of DHeva01 are not affected.

GPIO_STATE description:

Settings Name: Description: Unit:
GPIO_A_STATE DHCOM GPIO_A default state if dir = output 1 high / 0 low
GPIO_B_STATE DHCOM GPIO_B default state if dir = output 1 high / 0 low
…
GPIO_I_STATE DHCOM GPIO_I default state if dir = output 1 high / 0 low
GPIO_J_STATE DHCOM GPIO_J default state if dir = output (camera interface) 1 high / 0 low
…
GPIO_W_STATE DHCOM GPIO_W default state if dir = output (camera interface) 1 high / 0 low

Please note: If you own a DHeva01 428-100 or a DHeva01 428-200 you have to enable the USB-OTG power with configuring the DHCOM GPIO_B as an output with initial state high to use the USB-OTG port. Newer versons of DHeva01 are not affected.

HW_CONFIG_FLAGS description:

Settings Name: Description: Unit:
SILENT_MODE Disable Bootloader messages on FFUART 0 enabled FFUART outputs / 1 disabled FFUART outputs
UPDATE_DEV Configures auto update storage devices 0b000000 All Update Medias disabled

0bxxxxx1 Update via MicroSD Slot

0bxxxx1x Update via SD/MMC Slot

0bxxx1xx Update via USB Host 1

0bxx1xxx Update via USB OTG

0bx1xxxx Update via USB Host 2

0b1xxxxx Update via Ethernet

LCD_MODE Enable Bootloader messages on LCD Display 1 enabled / 1 disabled
DIS_CON Disable Bootloader console on FFUART 0 console enabled / 1 console disabled
DISP_ADPT_EE_CHK Enable display-adapter EEPROM check for display-settings 0 don’t check EEPROM for DH settings / 1 check EEPROM for DH settings
Retrieved from "https://wiki.dh-electronics.com/index.php?title=DHCOM_Settings&oldid=1507"