none
How to force Windows CE to use the display connected to the HDMI, without testing the HDMI connection RRS feed

  • Question

  • Our company develops hardvare devices, which run Windows CE and Windows 7 Embedded.

    The hardware engineers made a small mistake in the HDMI hardware (they forgot to invert one line), and because of this, the HDMI socket wrongfuly detects the presence of the display. So, the Windows CE senses that no display attached to the HDMI socket, but in fact, there is a display, just the Windows CE beleives it wrongfuly.

    And, after we can make the Windows beleive that it has a display, it handles the display correctly, so the only problem is the detection of the presence of the HDMI display.

    We can suppose, that there is always a display on the HDMI, so we no need any kind of HDMI detection.

    Our company sold 200 devices when they realize the hardware problem. (The display works fine after switching on the system, it becomes wrong after the first unplug and plug.) So, the company sold 200 devices, and we cannot call them back, it would be too high cost, and loosing the trust.

    We would like to change (update) the software, and we would like the new software to avoid any kind of HDMI line checking, any HDMI presence checking.

    Can we somehow overrule the HDMI detection, and explain to the Windows CE that it does have HDMI display even if it cannot sense the presence? Can we force the Windows CE to use an HDMI display which it cannot sense?

    Tuesday, April 1, 2014 3:53 PM

All replies

  • Peter:

    You describe the problem as if Windows CE cares if you have an HDMI display connected or not.   Windows CE doesn't really care.  For that matter, Windows CE doesn't even know what an HDMI display is.

    What does care, is your HDMI display driver.   You can modify it, or ask your vendor to modify it.  Since we don't know anything, in fact absolutely nothing, about your HDMI display driver we cannot make recommendations about how you would modify it.


    Bruce Eitman (eMVP) Senior Engineer Bruce.Eitman AT Eurotech DOT com My BLOG http://geekswithblogs.net/bruceeitman Eurotech Inc. www.Eurotech.com

    Tuesday, April 1, 2014 4:27 PM
    Moderator
  • If you could provide a little more info about, for instance, what chipset you use for HDMI, what processor, etc., then maybe we can be of a bit more assistance as to what to look for...

    Just remember that *anything* is possible on CE, so what you want is definitely possible (as long as you have the required source of course).


    Good luck,

    Michel Verhagen, eMVP
    Check out my blog: http://guruce.com/blog

    GuruCE
    Microsoft Embedded Partner
    http://guruce.com
    Consultancy, training and development services.

    Tuesday, April 1, 2014 9:23 PM
    Moderator
  • Thank you very much for your answers.

    The display chipset (and this handles the HDMI socket too) is Intel Graphics Media Accelerator 3600 Series

    Driver provider: Intel Corporation

    Driver Date: 15.03.2013

    Driver Version: 8.14.8.1091

    ((((((A stupid question... There are many layers in the device system. Some driver is more close to the hardware, some drivers are above them. So, probably the Intel driver is the lowest driver, which access directly the hardware, but there are probably higher level Microsoft drivers. Can't we change, or hook into the chain, or attach to some of them, and after that we would "lie" to all the above layers, that the specific HDMI line, the display detection line is sensing the presence of the display?))))))

    Wednesday, April 2, 2014 6:44 AM
  • That's not a stupid question...

    Yes, there are many layers but none of the higher layers will have any knowledge of the HDMI detect line. The only place you can "fake" that is in the lower layer driver. The higher layers merely present a display frame that the lower layer driver routes to the correct output.

    Do you have full source of the Intel driver?

    If you do; no problem. If you don't... :(


    Good luck,

    Michel Verhagen, eMVP
    Check out my blog: http://guruce.com/blog

    GuruCE
    Microsoft Embedded Partner
    http://guruce.com
    Consultancy, training and development services.

    Wednesday, April 2, 2014 7:32 AM
    Moderator
  • Thank you for the answer. I told everything to my boss, I even showed your comment to him. His idea is that:

    The machine works correctly until we unplug-plug the display, or until the device goes to sleep mode. The unplug-plug problem is not a problem actualy, because it cannot happen on customer side, nobody will unplug any cable. But, the second problem is a real problem, the sleep mode. The sleep function is essential part of our solution, the machine goes to sleep mode in many cases. So, the question of my boss is the next:

    Why the machine works after a normal boot up process, and does not work after a wake up from sleep? What goes on different way? Why can the machine beleive that it has display after the boot up? Can we start any program after every wake up case to make the situation same as it would be after a boot up? Can we write or start any program which would simulate a boot up situation after a wake up?

    Wednesday, April 2, 2014 12:00 PM
  • That depends; do you need to wake up quickly? Do you need to retain any data?

    If not; IOCTL_HAL_REBOOT could be a solution.

    I'm assuming you don't have access to the source code of the display driver (you did not answer that question)?

    Without source it is just very difficult to know what the driver does after a wake, and whether you can do anything about it.

    I'd say; ask Intel for access to source, or ask them for insight into the HDMI detection process.

    I don't think any of us can do anything more for you without at least insight into the source code...


    Good luck,

    Michel Verhagen, eMVP
    Check out my blog: http://guruce.com/blog

    GuruCE
    Microsoft Embedded Partner
    http://guruce.com
    Consultancy, training and development services.

    Wednesday, April 2, 2014 12:06 PM
    Moderator
  • Peter:

    I think that Michel's answer is clear, but just in case:

    You didn't answer about having source for the driver, but unless you work for Intel, you do not have the source code.

    There are only two solutions to your problem:

    1. Change the driver - but since you do not have source code, this is not an option for you.

    2. Change your hardware.   Your boss won't like it, but it isn't the software engineer's fault so break it to him gently and start to solve the problem.


    Bruce Eitman (eMVP) Senior Engineer Bruce.Eitman AT Eurotech DOT com My BLOG http://geekswithblogs.net/bruceeitman Eurotech Inc. www.Eurotech.com

    Wednesday, April 2, 2014 12:25 PM
    Moderator