RGB Display after switch from PM7A to PMA9

Scheuch · Jun 19th 2019

Good day,

Currently I am testing a PicoMODA9_V2_WEC7.

Since it should be pin compatible with the PicoMOD7A, I plugged it into the hardware currently used with said PM7A (WCE6).

We are using an "Ampire AM800480E2TMQW" as display and it is working fine with the PM7A, but with the PMA9 I only get a white display at startup, which than switches over to black.

Are there any registry settings that may differ between PM7A and PMA9?

The registry used for the display settings is as follows:

Code

reg open \drivers\display\LCD
reg create key Mode100
reg set value name string "Ampire AM800480E2TMQW"
reg set value BLW dword 40
reg set value HSW dword 48
reg set value ELW dword 40
reg set value config dword 0x00700000
reg set value BFW dword 29
reg set value VSW dword 3
reg set value EFW dword 17
reg set value msignal dword 2
reg set value rows dword 480
reg set value LPP dword 480
reg set value width dword 152
reg set value height dword 91
reg set value contrastenable dword 0
reg set value contrastvalue dword 0
reg set value type dword 6
reg set value columns dword 800
reg set value PPL dword 800
reg set value bpp dword 16
reg set value lcdclk dword 25
reg set value EnableCursor dword 0
reg set value OutputDevice dword 0x08000
display mode set 100
reg open \drivers\display\LCD
reg set value AccelLevel dword 1
reg save

Display More

I already added a line for the OutputDevice setting, since I figured the PMA9 might try to use the LVDS instead of the RGB.

I would like to ask you about any hints, what might be the problem.

Best regards

fs-support_ZU · Jun 21st 2019

Hello,

"OutputDevice" have to be adjusted under "HKLM\Drivers\Display\LCD" *not* under "HKLM\Drivers\Display\LCD\Mode<X>". But it is not required to specify this value here. It can be also done by the value "type" refer chapter "Registry value type".

So (assume) following should work:

- delete "OutputDevice"

- register "reg set value type dword 0x8006"

Scheuch · Jun 24th 2019

Good day,

thank you for the quick help, but I am still not able to drive the RGB display.

After comparing the registry values under Drivers\Display\LCD between PM7A and PMA9 I saw that the PMA9 has some values less than the PM7A.

For example there is no mentioning of the Display drivers like it used to be on the PM7A.

Is that as it should be? Or do I need to add the display driver manually?

PM7A:

Code

\: HKEY_LOCAL_MACHINE\Drivers\Display\LCD
OK
!>reg enum<LF>
OK -> reg enum key \
00 "mode100" \
01 "Mode6" \
OK -> reg enum value \
00 "AccelLevel"=dword:1 \
01 "Mode"=dword:100 \
02 "VidMemBase"=dword:1325400064 \
03 "UseBootInit"=dword:0 \
04 "XMemBase"=dword:0 \
05 "XMemLen"=dword:0 \
06 "DisplayDll"=string:display.dll \
07 "MemBase"=dword:-134217728 \
08 "MemLen"=dword:688 \
09 "PrimaryWin"=dword:2 \
10 "DDOverlayWin"=dword:1 \
11 "OESWin"=dword:0 \
12 "OESFlip"=dword:0 \
13 "UseAsPost"=string:CAM1: \
14 "UseForWB"=string:CAM3: \
15 "BlendPolicy"=dword:1 \
16 "PresetColorkeyPrimaryWin"=dword:8 \
17 "PresetColorkeyDDOverlayWin"=dword:8 \

Display More

PMA9:

Code

\: HKEY_LOCAL_MACHINE\Drivers\Display\LCD
OK
!>reg enum<LF>
OK -> reg enum key \
00 "Mode100" \
01 "Mode6" \
02 "Mode19" \
OK -> reg enum value \
00 "OutputDevice"=dword:32774 \
01 "AccelLevel"=dword:1 \
02 "Mode"=dword:100 \
03 "UseBootInit"=dword:0 \

Display More

Best regards

fs-support_ZU · Jun 24th 2019

Hello,

please delete HKLM\drivers\display\lcd\OutputDevice"=dword:8006" this is an invalid value.

Set "HKLM\drivers\display\lcd\mode100\type=dword:8006". Don't touch other values under "HKLM\Drivers\Display\lcd" without "mode" in a basic step!

Scheuch · Jun 24th 2019

Good day,

I have now set the type parameter as value in my Mode key, but still have the same problem. --> A White screen at startup followed by a black screen.

So the PicoMODA9 does not need any references to any drivers like the PicoMOD7A?

Or is this entry just missing?

Where there any changes to the registry keys in the switch from PM7A to PMA9? For example the already exsisting CAN- and I2C-drivers seem to have slightly different keys than before. PMA9 has a I2C key already exsisting, which should in theory be I2C1(shouldn't it?) Same with the CAN-driver key.

Is there a possibility that a changed key might interfere with my hardware and therefore the display?

best regards

fs-support_ZU · Jun 25th 2019

Hello,

>> Is there a possibility that a changed key might interfere with my hardware and therefore the Display?

<< I don't think so. But it would be a good idea to start with the default image settinges.

So please set registry to default by bootloader command "R"... .

Afterwards adjust your display and provide me complete bootlog and LCD registry.

Thanks.

Scheuch · Jun 26th 2019

Good day,

I just reset the registry and set my display parameters.

Display Reg :

Code

reg open \drivers\display\LCD
reg create key Mode100
reg set value name string "Ampire AM800480E2TMQW"
reg set value BLW dword 40
reg set value HSW dword 48
reg set value ELW dword 40
reg set value config dword 0x00700000
reg set value BFW dword 29
reg set value VSW dword 3
reg set value EFW dword 17
reg set value msignal dword 2
reg set value rows dword 480
reg set value LPP dword 480
reg set value width dword 152
reg set value height dword 91
reg set value contrastenable dword 0
reg set value contrastvalue dword 0
reg set value type dword 0x8006
reg set value columns dword 800
reg set value PPL dword 800
reg set value bpp dword 16
reg set value lcdclk dword 25
reg set value EnableCursor dword 0
display mode set 100
reg open \drivers\display\LCD
reg set value AccelLevel dword 1
reg save

Display More

Log Output:

Code

:> <0>of Symbol Offset : 0x00000000
Num Files : 8
Kernel Flags : 0x00000001
FileSys RAM Percent : 0x20202020
Driver Glob Start : 0x00000000
Driver Glob Length : 0x00000000
CPU : 0x01c2
MiscFlags : 0x0002
Extensions : 0x802221f0
Tracking Mem Start : 0x00000000
Tracking Mem Length : 0x00000000
Kernel (3627kB) read from flash disk started finished in 573 milliseconds
Kernel read from NAND
INFO: OEMLaunch: Jumping to Physical Address 0x10220000h (Virtual Address 0x10220000h)...
Jumping to Kernel @ 0x10220000
INFO:OALLogSetZones: dpCurSettings.ulZoneMask: 0xb
Windows CE Kernel for ARM (Thumb Enabled)
OAL: Enabling L2 cache
OEMInit: silicon rev = 0x14
SMP support enabled
PicoMODA9 V2.50 - Firmware Init
Build: Aug 13 2018/07:31:10
OAL: Detected 2 CPUs
OAL: Another CPU core started
OAL: OEMGetRamTable TotalMemSize=512 VidMemSize=0
OAL: HW watchdog enabled
WARNING: SNVS was reset.
[OAL] MACB: Disabled
[OAL] RestartReason: IPP
FSPART: FS partition driver loaded
BINFS: RegisterVolume - Mounted volume '\BINFS'
FS-PM: STARTED
BE2: Version 1.4, ActiveKey = Drivers\Active\01
BE2: Version 1.4, ActiveKey = Drivers\Active\04
IPU: Version 1.4, ActiveKey = Drivers\Active\11
NI2C: Version 1.3, ActiveKey = Drivers\Active\18
PP: Version 1.1, ActiveKey = Drivers\Active\21
VDI: Version 1.1, ActiveKey = Drivers\Active\22
ENET: Version 1.5, ActiveKey = Comm\ETHNETA
ETHMAN: Version 1.2, ActiveKey = Drivers\Active\32
BE2: Version 1.4, ActiveKey = Drivers\Active\35
I2C: Version 4.2, ActiveKey = Drivers\Active\36
NI2C: Version 1.3, ActiveKey = Drivers\Active\37
COMMDD2: Version 1.0, ActiveKey = Drivers\Active\38
Serial: Version 1.11, ActiveKey = Drivers\Active\38
COMMDD2: Version 1.0, ActiveKey = Drivers\Active\39
Serial: Version 1.11, ActiveKey = Drivers\Active\39
Serial: Port disabled. Serial debug is on !
COMMDD2: Version 1.0, ActiveKey = Drivers\Active\40
Serial: Version 1.11, ActiveKey = Drivers\Active\40
TCH: Version 1.4, ActiveKey = Drivers\Active\41
SHC: Version 1.6, ActiveKey = Drivers\Active\42
SHC: Version 1.6, ActiveKey = Drivers\Active\43
I2C: Version 4.2, ActiveKey = Drivers\Active\44
WAV: Version 1.3, ActiveKey = Drivers\Active\45
SHC: [USDHC1] SD card inserted
NSPI: Version 3.8, ActiveKey = Drivers\Active\46
EXTRTC: Version 1.2, ActiveKey = Drivers\Active\47
PPU: Version 1.1, ActiveKey = Drivers\Active\48
FCR: Version 0.2, ActiveKey = Drivers\Active\49
DIO: Version 1.4, ActiveKey = Drivers\Active\50
FRW: Version 1.3, ActiveKey = Drivers\Active\56
GALCORE 4.6.9(9754) (Sep 19 2014 12:09:40)
Major GPU: SysIntr=28 MemBases=0x130000 MMU Version=0
2D GPU: SysIntr=29 MemBases=0x134000 MMU Version=0
Video memory: BaseAddress=0x0 PhysBase=0x106d6000 size=0x7000000 physSize=0x0
LCD: Version 1.5, ActiveKey = Drivers\Display\LCD
LCD: Read registry settings from Drivers\Display\LCD
LCD: Read registry settings from Drivers\Display\LCD
LCD: Display-Mode 100, Name Ampire AM800480E2TMQW
TchProxy: TouchDriverTimeout=100ms
SHC: [USDHC1] SD card inserted
NDCUCFG V 69 started. Platform: PicoMODA9
CheckAutoStart: Version 1.7, LaunchNum = 100
NDCUCFG Open COM1: at 115200 Baud
CreateFile() failed -> ERROR COM1:
ENET: LinkState: DISCONNECTED
Explorer(V2.0) taskbar thread started.
BCS: Version 1.4, ActiveKey = Drivers\Active\76

Display More

fs-support_ZU · Jun 26th 2019

Hello,

and sorry i can't see any clear mistake. Assume the display should work. One point is not clear to me how do you control the brightness of backlight (Pin12). Is it possibel that this pin is low all the time after OS is load? Try to enable the contrast and try some values between 0...4095.

I nothing helps best would be to send us a complete kit so that we can check it in our office.

Share