Backlight for efusA9X with Display Mode 9

    Hello,
    we use a
    display (EDT ET043080) which runs well with efusA9 and display mode 9. With
    efusA9X the backlight signal is always high and therefore the display is dark. The
    display dimming functionality of the F&S Control Panel has no effect. (With
    display mode 19 and the standard display delivered with the evaluation kit the dimming
    of the display works.)



    What can we
    do to get the backlight running for efusA9X with display mode 9?




    Best
    regards,


    Steffen

    Hello,
    quick hint - maybe there is a bug in the driver we have to check it ..., i saw no impact changes between A9 and A9x concering mode 9.
    Please try:


    Does it work now?

    F&S Elektronik Systeme GmbH
    As this is an international forum, please try to post in English.
    Da dies ein internationales Forum ist, bitten wir darum, Beiträge möglichst in Englisch zu verfassen.

    Hello,


    unfortunately it doesn't work. (I've used "reg open \Drivers\Display\lcd\mode9" instead of ...\builtin\..., see below).


    Checking these changes I've mentioned that there are some values in the "lcd" directory (like OutputDevice, see below) that can be deleted but will occur again after the next start. I'm not sure if this is expected.
    Could any bootloader option have impact?



    The changed registry:


    !>\: HKEY_LOCAL_MACHINE\drivers\display\lcd
    OK
    !>OK -> reg enum key \
    00 "Mode9" \
    01 "Mode19" \
    OK -> reg enum value \
    00 "UseBootInit"=dword:1 \
    01 "OutputDevice"=dword:32768 \
    02 "VidMemBase"=dword:-1086324736 \
    03 "VidMemLen"=dword:12 \
    04 "Mode"=dword:9 \
    OK
    !>\: HKEY_LOCAL_MACHINE\drivers\display\lcd\mode9
    OK
    !>OK -> reg enum key \
    00 "mode9" \
    OK -> reg enum value \
    00 "contrastvalue"=dword:1234 \
    01 "contrastenable"=dword:1 \
    02 "contrastfreq"=dword:4095 \
    OK
    !>


    Best regards,
    Steffen

    Hello,
    you are right "reg open \drivers\builtin\lcd\mode9" is correct!


    Quote

    Could any bootloader option have Impact?

    Don't think so because mode 19 is working.


    As a work around you may use mode19 by overwrite Rows, Columms, PLL, LPP and LCDClk with your values.


    We will check wath is wrong with mode9 on A9x and answer aps.

    F&S Elektronik Systeme GmbH
    As this is an international forum, please try to post in English.
    Da dies ein internationales Forum ist, bitten wir darum, Beiträge möglichst in Englisch zu verfassen.

    Hello,


    I've tried to but could not really test with Mode19 and modifies Parameters because there is a strange behavior:


    If I've set the display mode to 19 (and made "reg save" and "reg enum" to verify") the display mode is 9 again (like configured in my Image) after a reset.


    I guess there is a side effect resetting the display mode and setting other values like OutputDevice (see my previos post).


    I've appanded the debug output after changing the display mode to 19 and performing a reset.
    I don't know whether the line "Could not initlize LCD interface!" indicates a problem.


    Have you any idea about the unexpected registry actions?



    Best regards,
    Steffen


    ClearArmvSysScan()
    pInfo@0x80001100
    ArmrvSysScan()
    pInfo@0x80001100
    GetDeviceInfo()
    GetProcessorFeatures()
    ArchVersion 0x00000003
    PU Voltage 0x000004c9
    ARM Voltage 0x0000047e
    SOC Voltage 0x000004c9
    PeriphBase() 0x00a00000
    pInfo->NumCpus() 0x00000004
    pInfo->TimerClk() 0x00000042
    CLIDR=0x09200003
    L2CacheType=0x00000000
    L2Base=0x00a02000
    PL310_ID=0x410000c8
    L2 cache found
    pInfo->IsExtL2() 0x00000001
    pInfo->IsVFPSupported() 0x00000001
    CLIDR=0x09200003
    L2CacheType=0x00000000
    L2Base=0x00a02000
    PL310_ID=0x410000c8
    L2 cache found
    pInfo->GicIntfBase() 0x00a00100
    pInfo->GicDistBase() 0x00a01000
    pInfo->SecGicIntfBase() 0x00000000
    pInfo->SecGicDistBase() 0x00000000
    ConfigCpuAuxFeatures()
    ConfigCpuDiagCtrl()
    0x800011000x00000c09BeforeKernelSta<-6>INFO:OALLogSetZones: dpCurSettings.ulZoneMask: 0xb
    ======== .ldb div ========
    pcscmr2 0x13192c62
    pcscmr2_2 0x13192c62
    ======== .LDB_DI0 ========
    pcs2cdr 0xe30c1
    ======== .lcdfi1 ========
    pcscdr2 0x29150
    pcscdr2 _2 0x29750
    ======== .ldb control ========
    pLDBCtrl 0x0
    ======== .LVDS ========
    plvds 0x30000
    plvds 0x30000
    plvds 0x30007
    OUTPUT clk: LVDS <4>
    pccosr 0x1780100
    EBOOT: CCOK1 --
    BSPUpda<-4>INFO:OALLogSetZones: dpCurSettings.ulZoneMask: 0xb
    Microsoft Windows CE Bootloader Common Library Version 1.2 Built Oct 20 2015 15:37:25
    Microsoft Windows CE Bootloader for efusA9X Built Nov 5 2015
    Portions copyright (c) 2012 F&S Elektronik Systeme GmbH
    Boot Loader, Version 1.0
    NBoot, Version VN27
    HW rev. 1.10
    System ready!
    Preparing for download...
    Press >S< to step into monitor...
    Could not initliaze LCD interface!
    AUTO BOOT enabled
    +ReadKernelRegionFromNandFlash
    Image Signature in Flash Memory found (dwSig=0x43454345)
    TOC pointer=0x804831D8
    ROMHDR (cTOC = 0x002631d8) ---------------------
    DLL First : 0x4001efd9
    DLL Last : 0x4012f000
    Physical First : 0x80220000
    Physical Last : 0x804ef018
    Num Modules : 31
    RAM Start : 0x80620000
    RAM Free : 0x80663000
    RAM End : 0x90620000
    Num Copy Entries : 2
    Copy Entries Offset : 0x8044efc8
    Prof Symbol Length : 0x00000000
    Prof Symbol Offset : 0x00000000
    Num Files : 8
    Kernel Flags : 0x00000001
    FileSys RAM Percent : 0x20202020
    Driver Glob Start : 0x00000000
    Driver Glob Length : 0x00000000
    CPU : 0x01c4
    MiscFlags : 0x0002
    Extensions : 0x80222248
    Tracking Mem Start : 0x00000000
    Tracking Mem Length : 0x00000000
    Kernel (2876kB) read from flash disk started finished in 0 milliseconds
    Kernel read from NAND
    INFO: OEMLaunch: Jumping to Physical Address 0x80220000h (Virtual Address 0x80220000h)...


    Jumping to Kernel @ 0x80220000
    ArmrvSysScan()
    pInfo@0x80001100
    GetDeviceInfo()
    GetProcessorFeatures()
    ArchVersion 0x00000003
    PU Voltage 0x000004c9
    ARM Voltage 0x0000047e
    SOC Voltage 0x000004c9
    PeriphBase() 0x00a00000
    pInfo->NumCpus() 0x00000004
    pInfo->TimerClk() 0x00000042
    CLIDR=0x09200003
    L2CacheType=0x00000000
    L2Base=0x00a02000
    PL310_ID=0x410000c8
    L2 cache found
    pInfo->IsExtL2() 0x00000001
    pInfo->IsVFPSupported() 0x00000001
    CLIDR=0x09200003
    L2CacheType=0x00000000
    L2Base=0x00a02000
    PL310_ID=0x410000c8
    L2 cache found
    pInfo->GicIntfBase() 0x00a00100
    pInfo->GicDistBase() 0x00a01000
    pInfo->SecGicIntfBase() 0x00000000
    pInfo->SecGicDistBase() 0x00000000
    ConfigCpuAuxFeatures()
    ConfigCpuDiagCtrl()
    0x800011000x00000c09INFO:OALLogSetZones: dpCurSettings.ulZoneMask: 0xb
    Windows CE Kernel for ARM (Thumb Enabled)
    +OEMInit
    INFO:OALLogSetZones: dpCurSettings.ulZoneMask: 0x2b
    g_vaL2CtrlBase=0xa0a02000
    Enabling L2 cache
    OEMInit: silicon rev = 0x0
    OAL: Detected 1 CPUs (TODO)
    SMP support disabled
    efusA9X V1.10 BETA - Firmware Init
    Copyright (c) 2015 F&S Elektronik Systeme GmbH
    Build: Feb 9 2016/15:30:34
    OEMGetRamTable dwMemSize=1024 dwVidMemLen=12
    cBoardConfig.chFeatures1=0x0 0 chBoardType=0x8
    [OAL] RestartReason: IPP
    BINFS: RegisterVolume - Mounted volume '\BINFS'
    PM-NETDCU: STARTED
    BE2: Version 1.4, ActiveKey = Drivers\Active\01
    BE2: Version 1.4, ActiveKey = Drivers\Active\04
    ENET: Version 1.2, ActiveKey = Comm\ETHNETA
    BSPENETIomuxConfig: Enable RMII 0x2188000.
    ENETGetPHYId2: The name for the external PHY is AR8035
    BE2: Version 1.4, ActiveKey = Drivers\Active\29
    NI2C: Version 0.3, ActiveKey = Drivers\Active\30
    NI2C: Version 0.3, ActiveKey = Drivers\Active\31
    NI2C: Version 0.3, ActiveKey = Drivers\Active\32
    Serial: Port disabled. Serial debug is on !
    Serial: Version 1.5, ActiveKey =
    Serial: Version 1.5, ActiveKey =
    Serial: Version 1.5, ActiveKey =
    TCH: Version 1.1, ActiveKey = Drivers\Active\37
    SHC: Version 1.3, ActiveKey = Drivers\Active\38
    Using Polling Mode
    NSPI: Version 3.6, ActiveKey = Drivers\Active\39
    EXTRTC: Version 1.2, ActiveKey = Drivers\Active\40
    ETHMAN: Version 1.0, ActiveKey = Drivers\Active\42
    WAV: Version 1.0, ActiveKey = Drivers\BuiltIn\Audio
    BCS: Version 1.4, ActiveKey = Drivers\Active\44
    DIO: Version 1.4, ActiveKey = Drivers\Active\45
    SpiOverGpio: SPI_Init++ dwContex:aecf9ea0
    SpiOverGpio: SPI_Init-- hOpenDevice: a6c62b00
    SHC: [USDHC1] SD card inserted
    LCD: Version 1.0, ActiveKey = Drivers\Display\LCD
    LCD: Couldn't open key "Drivers\BuiltIn\PXP". Will use 0xfe02fc as default standard background colorkey.
    LCD: Read registry settings from Drivers\Display\LCD
    LCD: Read registry settings from Drivers\Display\LCD
    LCD: Display-Mode 9, Name ET043080
    LCD: OutputDevice = DRGB
    HW_LCDIF_CTRL1_RD = 0x010f2101
    AutoLaunch_BloodReader_Settings: Entry
    AutoLaunch_BloodReader_Settings: SignalStarted(45) called.
    AutoLaunch_BloodReader_Settings: Exit
    NDCUCFG V 62 started. Platform: efusA9X
    NDCUCFG Open COM1: at 115200 Baud
    CreateFile() failed -> ERROR COM1:
    SoftRTC disabled
    Detecting new link
    ENETParsePHYLink: Adapter->MIISeqDone = FALSE;
    ENET: LinkState: DISCONNECTED
    ENETCheckForHangEx- Start Update Link Status
    ENETParsePHYLink: Adapter->MIISeqDone = FALSE;
    ENETCheckForHangEx- Start Update Link Status
    ENETParsePHYLink: Adapter->MIISeqDone = FALSE;

    Hello,


    thought mode19 was working before? You are sure that HKLM\Drivers\Display\lcd\mode=19?

    Quote

    Could not initliaze LCD interface

    Did you enable LCD in bootloader? Please check: step into bootloader -> enter command "XDE" check if "N" i set, else set "N".
    After this adjustment it must be possibel to choose every display mode while OS launched.

    F&S Elektronik Systeme GmbH
    As this is an international forum, please try to post in English.
    Da dies ein internationales Forum ist, bitten wir darum, Beiträge möglichst in Englisch zu verfassen.

    Hello,


    does it work now? We check it there may be a bug in the display Driver but you can write your Settings into the mode19 this may serve as a workaround in the meanwhile:


    Mode9ToMode19

    F&S Elektronik Systeme GmbH
    As this is an international forum, please try to post in English.
    Da dies ein internationales Forum ist, bitten wir darum, Beiträge möglichst in Englisch zu verfassen.

    Hello,


    after setting XDE to 'N' the registry settings for the display can be changed without problems.


    After applying the registry changes of your last proposal the display still remains dark.


    The log contains the following LCD related messages (I've added Debug = 4):


    LCD: Version 1.0, ActiveKey = Drivers\Display\LCD
    LCD: Couldn't open key "Drivers\BuiltIn\PXP". Will use 0xfe02fc as default standard background colorkey.
    LCD: Read registry settings from Drivers\Display\LCD
    LCD: Read registry settings from Drivers\Display\LCD
    LCDEXT: Debug = 0x00000004 = 4
    I2CDevice = I2C3:
    LCDEXT: I2CDeviceAddress = 0x000000c0 = 192
    LCDEXT: PWMChannel = 0x00000001 = 1
    LCDEXT: PWRConChannel = 0x00000000 = 0
    LCDEXT: DisplayResetChannel = 0xffffffff = 4294967295 (Default)
    LCDEXT: I2CResetChannel = 0xffffffff = 4294967295 (Default)
    LCDEXT: Mode = 0x00000001 = 1 (Default)
    LCDEXT: Steps = 0x00000fff = 4095 (Default)
    LCDEXT: Freq = 0x00000200 = 512
    LCDEXT: DutyCycle = 0x00000050 = 80
    I2C_Write(): Message failed (flags=4)
    LCD: ASTADPEDT1.dll - Init failed
    LCD: Display-Mode 19, Name ET070080
    LCD: OutputDevice = DRGB
    HW_LCDIF_CTRL1_RD = 0x010f2101



    Best regards,
    Steffen

    Hello,


    I've just checked the display behavior with a efusA9 to be sure that the hardware is still operable.


    With efusA9 the display works like expected. But I've mentioned another difference to the efusA9X: Immediately after the start / reset the backlight is on. (The display has an undefined grey coloring because the bootscreen is still missing.) With efusA9X the display / backlight stays dark the whole time. Could it be that there is additionally to the XDE setting another option that must be adjusted in the bootloader?



    Best regards,
    Steffen

    Hello,


    if we enable the backlight permanently (by hardware means) the display works (with the desired mode 9). It seems that only the backlight control isn't working like expected.


    Do we have to do some additional configuration regarding the backlight or the related PWM?



    Best regards,
    Steffen

    Hello,
    as told above i think there is a bug in the driver, we have to check/rework. In the meanwhile you may use mode19 and overwrite your specail values. This should work my collegue test it.
    Any problems?

    F&S Elektronik Systeme GmbH
    As this is an international forum, please try to post in English.
    Da dies ein internationales Forum ist, bitten wir darum, Beiträge möglichst in Englisch zu verfassen.

    Hello,


    the display still remains dark. Like I've posted Friday morning. there are some error messages in the debug log (display Driver initialization failed after I2C communication failed). The Display that we use doesn't communicate via I2C. Maybe this is the reason for the error messages.


    Best regards,
    Steffen

    Hello,
    please set only the first eleven values under mode19:

    F&S Elektronik Systeme GmbH
    As this is an international forum, please try to post in English.
    Da dies ein internationales Forum ist, bitten wir darum, Beiträge möglichst in Englisch zu verfassen.

    Hello,


    I've tested both the recommended settings of the previous entry additionally to the entries for Mode19 of the BSP and the recommended settings after deleting the other entries beneath Mode19 without success. The difference is that the log entry regarding the I2C call is "missing" in the latter case.


    When I use the remote display I can change the Backlight Control with FSBoardConfig but without any effect.


    Last week we've made a test with Mode9 and have seen that the PWM signal was always high. After pulling it down the display was OK (except the rotation that isn't working yet according to the road map) but could not be dimmed afterwards therefore. I guess that the PWM Signal remains high also with Mode19 (not yet measured). What could be the reason?



    Best regards,
    Steffen



    Best regards,
    Steffen

    Hello,


    my collegue will test it again today.We should wait for the results.
    I will keep you informedas soon we have new.

    F&S Elektronik Systeme GmbH
    As this is an international forum, please try to post in English.
    Da dies ein internationales Forum ist, bitten wir darum, Beiträge möglichst in Englisch zu verfassen.

    Hello,


    we test it again and it works:


    You can adjust contrast using:
    "contrast set 0"/"contrast set 255" max /min.


    If you get still I2C errors, reset registry to default and/or set registry value debug to 255 for I2C with index 3.
    Thanks

    F&S Elektronik Systeme GmbH
    As this is an international forum, please try to post in English.
    Da dies ein internationales Forum ist, bitten wir darum, Beiträge möglichst in Englisch zu verfassen.

    Hello,


    we don't use the adapter of the evaluation kit. We have a direct connection between pin 87 (BL_CTRL, PWM) and the LEDCTL signal of the display and don't use any I2C for backlight control. Therefore we need the PWM signal of pin 87 working.


    Best regards,
    Steffen

    Quote

    Therefore we need the PWM signal of pin 87 working

    Yes, we will implement this aps.

    F&S Elektronik Systeme GmbH
    As this is an international forum, please try to post in English.
    Da dies ein internationales Forum ist, bitten wir darum, Beiträge möglichst in Englisch zu verfassen.

    Now PWM via pin 87 works (since beta V1.10 from 24.3.16).

    F&S Elektronik Systeme GmbH
    As this is an international forum, please try to post in English.
    Da dies ein internationales Forum ist, bitten wir darum, Beiträge möglichst in Englisch zu verfassen.