Windows Embedded Compact 7.0

Home 9 Windows Embedded Compact 7.0
Awaiting product image

Product inquiry

Documents

Functions

novaluefound

Drivers

Name
Status
Comments
Limitations
Links

PWM

on request

PCI support

on request

on DIMM-MX6-PCIe only

CPU types

available

Support for DIMM-MX6S and DIMM-MX6DL is available with Developer Kit revision v0401 and later

Wireless LAN

on request

USB Host interface driver

available

The driver support handles "Mass-Storage Devices" and "Human interface devices (HID), keyboard and mouse)". Support for other devices such as serial port adapters are available on request.

USB Function driver

available

The function "Serial Client (MS Mobile Device Service)" and "Mass Storage Client" are included. If another function is needed send a request to emtrion.

Touch driver (capacitive touch)

available

The capactive touch feature supports the touch controller which is mounted on emtrion's ET0700M06 display adapter.

Touch driver (resistive touch)

available

Storage: SATA

on request

Storage: SD card

available

The microSD socket on the Lothron base is currently not supported. If needed send a request to emtrion.

Storage: onboard NAND

available

Starting with Release 2 of the Developer Kit

Serial interfaces (RS232)

available

Currently only 3 interfaces are registered in the kernel image of the current Developer Kit release.

PMIC driver support (Powermgmt)

available

PMIC driver support is required to reduce or disable voltage to peripherials, which are currently not used by the application or the operating system.

Audio driver for analog audio

on request

SPI

on request

I2C (onchip)

available

IrDA

on request

GPIO driver

on request

Camera interfaces

on request

CAN interfaces

on request

On-board Ethernet (10/100MBit/s)

available

HW watchdog

available

HW accelerated audio/video codecs

on request

DirectDraw hardware acceleration support

available

DirectDraw hardware acceleration support on DIMM-MX6 under WEC7

Display Driver (onchip)

available

Supported display resolution and connectivity on DIMM-MX6 under WEC7

True

Dienste

Name
Status
Comments
Limitations
Links

Persistente/Hive-based Registry

available

True

Release Notes

10.09.2015 – V0401

  • Important when you are upgrading from Developer Kit Revision 2.01 and earlier resp. Kernel V0201 and earlier or from another operating system:
    • You must reset the device to the delivery state. For details how to do this see chapter 5.6 in the Developer Kit manual which is also in the Documents folder of the DVD.
    • The U-Boot commands which have to use are changed if you update from Revision 1.00. Please use only the commands described in the manual for this release.
  • Changes:
    • Support for DIMM-MX6Solo and DIMM-MX6DualLite added
    • Improve USDHC driver performance
    • Fix external SD Card Card Detect and Write Protect problems
    • Fix problems with HDMI
    • Improve USBH driver performance
    • All Microsoft Updates till update 49, July 2015 are included

     

29.01.2015 – V0301

  • Important when you are upgrading from Developer Kit Revision 2.01 and earlier resp. Kernel V0201 and earlier or from another operating system:
    • You must reset the device to the delivery state. For details how to do this see chapter 5.6 in the Developer Kit manual which is also in the Documents folder of the DVD.
    • The U-Boot commands which have to use are changed if you update from Revision 1.00. Please use only the commands described in the manual for this release.
  • Changes:
    • Bugfixes in cache and multicore handling
    • Added support for HDMI monitors
    • Fixed stability issue when the system runs a long time with a heavy network load
    • Improvements in the drivers
    • All Microsoft Updates till update 41, November 2014 are included

 

15.07.2014 – V0201

  • BugFix: the handling of the static IP configuration provided by uboot is handled correctly now
  • Support for DIMM-MX6Q with 2GB RAM was added

 

11.12.2013 – V0200

  • This revision requires U-Boot release on October 30th, 2013 or later. If you have an older revision on your DIMM-MX6 you need to update this according the instructions in the U-Boot update guide which can found in the Documents folder on the DVD
  • Important when you are upgrading from Developer Kit Revision 1.00 resp. Kernel V0100 or from another operating system:
    • You must reset the device to the delivery state. For details how to do this see chapter 5.6 in the Developer Kit manual which is also in the Documents folder of the DVD.
    • The U-Boot commands which have to use are changed. Please use only the commands described in the manual for this release.
  • Changes:
    • Added: support for onboard NAND flash
    • Added: support for persistent (hive-based) registry
    • Added: support for capacitive touch controller
    • Added: using configuration through boot parameters configured in U-Boot
    • Added: support for RTC and HW watchdog
    • Added: monitoring of core temperature
    • Improvement of cache and multiprocessor support
    • BugFix: Network driver is using the Ethernet hardware (MAC) address which was assigned to the board in U-Boot
    • BugFix: KITL network driver is also using the Ethernet hardware (MAC) address which was assigned to the board in U-Boot if KITL is enabled
    • BugFix in serial driver
    • All Microsoft Updates till update 28, October 2013 are included.
  • Known issues:
    • There is a stability issue when the system runs a long time with a heavy network load.
       

29.05.2013 – V0100

  • First Release

Known Issues

The Freescale i.MX6 SoC can demand a lot of power from the power supply. Therefore emtrion designed a new base board Cadun which can handle the demands of our DIMM-MX6. If you already purchased a Verno with DIMM-MX6 and your application needs more power than Verno can deliver, you can contact us to exchange it with a Cadun. Because of mentioned power supply issues the Lothron base board should only be used, if you want to test a device, which can not be connected to Cadun. If you use Lothron please follow this guide.

Article

Supported display resolution and connectivity on DIMM-MX6 under WEC7

Details

DirectDraw hardware acceleration support on DIMM-MX6 under WEC7

Details

Using Lothron with DIMM-MX6

Details

How to get an update of your Developer Kit

Details

Assignment of the debug serial console

Details

Article available: True

Block diagram

Downloads / Documents

Release Notes (DIMM-MX6DevKitCE7)

Release Notes of the second release of the DIMM-MX6 Developer...
29. August 2023 - en
Download

Developer Kits

Sorry, No posts.

Accessories

Sorry, No posts.

Supported operating systems

Sorry, No posts.

FAQ

Updating Developer Kit for Windows embedded compact


How can get the latest updates for Windows embedded compact?

This depends on the company which has written the corresponding components. For public components which comes from Microsoft and haven't any need for special adaptation to the BSP, you can download the updates from Microsoft's download center.

For components which was written or ported by emtrion to the BSP, emtrion provides the updates through a SVN repository on emtrion's internet server. You will find more details how to update the BSP via SVN in the documentation which can be found on the Developer Kit DVD. If you did not receive or lost the DVD, please contact us and we will help you to establish the access to the SVN repository.

Troubleshooting USB Mobile Device Connection under Windows embedded Compact 7 on DIMM-MX6


The connection to the Mobile Device Center will not established when the USB cable is connected. What are possible reasons?

There are two reasons possible:

  1. the connection is not correctly set up on the DIMM-MX6 Windows embedded compact device
  2. the Windows Mobile Center has not launched all required processes

 

Solution:

  1. Check/Setup the connection on the DIMM-MX6 device:
    1. Open the control panel applet "Freescale USB driver". On the tab "USB Device Class Select" the item "ActiveSync" should be selected. If not correct it.
      Note: if you change the device class you must have no USB cable plugged in the USB device connector.
    2. Open from the "Start menu" -[gt] "Settings" then "Network and Dial-Up Connections". We need at least one direct connection using the USB cable. The USB interface is available in the system as a COM port as soon as the USB cable is plugged in and the "ActiveSync" USB device class is selected (see 1.1). If there is no direct connection you can create such a connection with these steps (make sure that there is a physical USB connection between the device and your PC):
      1. Make a double-click on "Make New Connection"
      2. Enter a connection name that you want. In these instructions, the name "USB cable" is used.
      3. Select the connection type "Direct connection"
      4. Press the button "Next"
      5. In the drop-down box "Select a device:" you have to select the item which has not the part "UNIMODEM" in the name (e.g. COM2:)
      6. Press the button "Configure". The dialog "Device Properties" is shown.
      7. On the tab "Call Options" select all checkboxes.
      8. Close the dialog "Device Properties" using the OK button in the upper right corner of the dialog.
      9. Press the button "Finish" to close the dialog "Device"
    3. Open the control panel applet "PC connection". Verify that the checkbox "Enable direct connections to the desktop computer" is selected. Verify also that the direct connection from 1.2 is used (in our example "USB cable"). If not press the button "Change connection" and select the direct connection.
  2. Check the Windows Mobile Center installation on the PC
    1. When the USB cable is plugged in a USB port on your PC a device named "Microsoft USB Sync" should be available. You can verify this if you take a look in the device manager on your PC. The device manager can be found in the control panel. In the device manager, you should find a device with the name "Microsoft USB Sync" in the category "Mobile devices".
    2. If you have started the "Windows Mobile Device Center" you should see the following processes on the process tab of the Windows Task Manager on your PC. The Windows Task Manager can be opened by a click with the right mouse button and selecting the item "Start Task-Manager". The important processes are:
      1. wmdc.exe: this is the process of the Windows Mobile Device Center. If this process is missing you can start it from the control panel by choosing the item "Windows Mobile Device Center"
      2. WmdHost.exe: this is the Windows Mobile Device Center Sync Host and is very important for the detection of a device in the Mobile Device Center. If this process is missing you can start it by executing the executable (there is no link in the start menu or control panel). This executable is located in the directory %SystemRoot%WindowsMobile (typically C:WindowsWindowsMobile).
        Note: On PCs, with 64bit operating systems this process is marked with *32 because it's always a 32bit process.

Media

89
Back
Telefon
Mail