uneron ESOM335X Tiny Windows CE Compute Module User Manual

uneron ESOM335X Tiny Windows CE Compute Module User Manual

Introduction

The eSOM335x is an ARM-based computer module with AM3358BZCZA100 ARM CortexA8 microprocessor family from Texas Instrument. RAM and storage memories was designed modular. There are 128MB/256MB/1GB DDR3L versions for RAM module. (default RAM is 512MB). The eMMC modules exist in 2G/4G/6G/8G/16GB/32GB versions. (Default eMMC is 8GB)

The eSOM335x can boot a real-time, small foot-print Windows CE very quickly. OS images are customized to enable users on rapid application development without any OS challenging. Users are free to choose the video output and can change their LCD without need to OS customization. In addition, users can configure their boot setting such as their logo and boot progress bar easily. Many device drivers like 4G module, Camera, CAN, Touch are integrated in OS image and users can add them to their projects safely. Users can develop applications in Visual Studio 2008 and LabVIEW for eSOM335x. Many sample codes are provided for software developer to access to eSOM335x peripherals and accelerates time-to-market procedures.

The eSOM335x targets a wide range of applications, including: Medical Devices, PLC, Industrial Automation, HMIs, Entertainment system, POS, Data Acquisition, Gaming and much more.

Features

• Texas Instrument AM3358BZCZA100 ARM Cortex-A8 Up to 1GHz Processor
• Replaceable and optional modular memories
• Support HDMI, TFT and LVDS as Video Output
• Rich interface through DDR3-SODIMM 204 pin connector
• On-board Gigabit Ethernet PHY, customizable Up to 2 Ethernet port
• Support 4G Module
• Support Camera
• Ready to Run WIN CE7 with quick launching
• Easy configuration OS parameters and driver settings
• Open-source WIN CE7 OS
• Rapid software development with many sample codes

Programming with Visual Studio

Visual Studio 2008 is the version of Microsoft’s popular IDE that also supports Windows Embedded Compact 7. WEC 7 (Compact 7) includes a suite of development tools that help you design, build, and deploy a Windows Embedded CE–based OS to a target hardware device. These tools are designed to make the development process straightforward as well as flexible. Users can interface with eSOM335x using an ethernet cable, and program application in Visual studio 2008, then deploy into their devices. Many sample codes are provided, and they can use them for rapid programming. These codes are simple and self- explaining. In the following, we describe how to program eSOM335x in step-by- step routine.

• Install visual studio 2008.
• Install _eSOM335x_WEC7_SDK.msi_ ( This file existed in SDK Folder on eSOM335x network drive accessible after buy this product.)
• Plug ethernet cable to development board and PC, then PC identify your new ethernet connection.
• Configure IP addresses in device and PC relatively. In PC side assign Default gateway to device IP, and in device side assign Default gateway to device IP.

Create new project

• Open Visual Studio 2008 and click create new project through File >New>Project. In Opened window set Project Type with Smart Device in Visual C# group as shown in following figure.
  
  Click OK, in the next window select Windows CE as Target platform and then click OK. Your project is created with empty form.
  

• In this form you can place your controls from toolbox section, in our case two label is in center of form.
  

Deploy project to Device

• Click on Target Device and select SDK1 ARMV7 Device

• Press Device Options , with this action, in opened window click on Devices and select SDK1.
  
  Click on Properties button, a new window appears, click on Configure button in this window. Select Use specific IP address check Box and type device IP as shown in following figure. Then click OK.

• Click on Connect to Device button , if everything is ok then Connection succeeded message appears in opened window.

• If click on Start Debugging button then click on Deploy button on opened window, your project run immediately on your device.

• If anything is OK, your application appears in device, below picture shows an example that run in eSOM335x
  

• A folder in your device is created for store your application data temporarily in Windows/Programs folder. After restarting this folder is deleted. You can copy application folder to eMMC or uSD drive to maintain in your device after restarting.

Sample Codes

Many source codes are provided for rapid application development. The table below details the libraries currently available for Visual C# programming:

these files are accessible through network drive URL after buy eSOM335x. In addition, sample codes for Codeplex are listed in below picture:

For example, if open GPIOtest project with VS2008, you can see project with a form designed for it as shown in the following figure:

If deploy this application on your device, immediately GPIOtest program run, and its form appeared in your device:

Create GPIO Project

Some of eSOM335x pin can be used as GPIO, these pins are specified in pinmux and Hardware Manual document. If you are using eDVK335x, some of GPIOs are accessible through a 2×24 pin header as shown in the following figure:

Note: GPIO3[21] is reserved for sound chip. GPIO3[17] and GPIO3[18] is used as touch panel interrupt and reset. GPIO0[18] and GPIO0[19] are also reserved.

For example, a new helloBlinky project is created for using GPIO116 as output and GPIO1 18 as input. You can access to GPIO pins with GPIO class. You can add GPIO.cs class file to your project with right click on your project and click on Add >Existing Item as shown in below figure:

This file exists in SampleCodes \ GPIOTest in eSOM335x network drive, then it is better to copy this file to your project folder and in opened window select this file.

In addition, you must click Add References and in Browse tab in opened window, select OpenNETCF.IO and add it to your project. Methods of GPIO class list in below table:

Designed form of this application shown as the following figure:

After deploy this application following UI appeared in device desktop:

Source code for this application is written here

Create ADC Project

eSOM335x has 8 channels for analog to digital conversion as shown in following table, for more information refer to pinMux document.

For handle with ADC channel, a class library is provided as ADC.cs. following table lists methods of this library. An example for using this class is explained in the following.

Adding folder paths to the OS

By default, Windows folder is system path, therefore most of application is in this folder that means, after calling, Windows can find them. For example, if you copy your application to Windows folder, you can call it from command prompt and OS can find it in Windows folder and run it. This folder was created in RAM while booting operating system. If restart your development board, OS cannot find your application because this application was deleted from this folder. For solve this problem, you can copy your application into a permanent memory like eMMC drives and add this folder to Windows path variables through Registry editor. For this work, go to Windows folder and run regedit , then click on _HKEY_LOCAL_MACHINE then LOADER_. Click on system path, there are 2 paths, and you can type your folder path instead of any of them. A reboot required to apply changes.

In another way, you can edit platform.org file in WINCE700\platform\eSOM335x\FILES folder as shown in following figure, after add path, you need to build your NK with Platform Builder and replace NK.bin instead of old version.

Autorun

There are multiple ways to autorun an application after device power on:

• AutoLaunchProgram : If you want to launch your application after OS booting, you must go to Windows folder on your device OS and run AutoLaunchProgram.exe

In this window click on Browse button and select application file, therefore after restarting your device, selected application automatically launches Immediately after OS boot and Win CE desktop appears.

• Registry Editor : another way to autorun an application is from Registry Editor. Run regedit in Windows folder and click on _HKEY_LOCAL_MACHINE then init_ as shown in following figure:

In this window exist Launch and Depend registry followed by a number like Launch99 and Depend99. In Launch registry, users can write application name, for example if click on Launch99 , in opened dialog, AutoLaunch.exe is written on Value data field, that means AutoLaunch application run after boot, but OS firstly check its dependency in Depend99.

Open Depend99 , as shown in following figure, some text is written in Value data field imply that before AutoLaunch run, Launch20 , Launch30 and launch50 must be running. Launch20 refers to drivers library, Launch30 refers to gwes.dll (graphic diver) and Launch50 refers to explorer.exe.

Windows check init registry while booting and run launch numbers respectively due to their numbers from low to high. Users can add or edit Launch and Depends due to their needs. In this case (Launch99) OS run AutoLaunch.exe after windows explorer and desktop appears. Config of this application is in ethDebugAutoRUN.reg file as shown in below figure.

Users can add any other Process in Registry Editor in Startup directory, follow these instructions to add a process:

• right click on this page and click on New - >String Value
• Rename it to Process1
• Click on Process1 and write your application name in Value data field. (Note that your application must be in Windows Path to OS can recognize it.)
• Again, Right click and click on New- >DWORD Value
• Rename it to Process1Delay then double click on it and set time delay for running application in Value data.
• After restart, your application appears after a delay time.

In addition to the edit AutoLaunch.exe and startup configuration, users can edit Launch99 directly. Double click on it and write your application name in Value data field.

• For remove Windows explorer environment, users can edit dependency in Depend99 with delete number 32 that run process32 (explorer.exe). In another way, users can replace their application name instead of explorer.exe in Launch50 , in this manner, application run immediately after windows launch and Windows shell do not appear. If you want to appear Windows shell, you should burn windows again with old NK.

Read User Manual Online (PDF format)

Download This Manual (PDF format)

Download this manual  >>