Microsoft Windows CE Toolkit for Visual Basic v5.0 serial key or number
Microsoft Windows CE Toolkit for Visual Basic v5.0 serial key or number
Windows Embedded Compact
Windows Embedded Compact
Source model
Support status
Windows Embedded Compact,[1] formerly Windows Embedded CE and Windows CE, is an operating system subfamily developed by Microsoft as part of its Windows Embedded family of products.*
Unlike Windows Embedded Standard, which is based on Windows NT, Windows Embedded Compact uses a different hybrid kernel.[2] Microsoft licenses Windows CE to original equipment manufacturers (OEMs), who can modify and create their own user interfaces and experiences, with Windows CE providing the technical foundation to do so.
The current version of Windows Embedded Compact supports x86 and ARM processors with board support package (BSP) directly.[3] The MIPS and SHx architectures had support prior to version 7.0.
On every version, changing the view options like showing hidden stuff in the Windows folder will lead you a bunch of stuff. Most of them are just images, while those files are a bunch of system files. The "homelogo" file is used in Internet Explorer Mobile, it can be seen on the home page (it probably appears on 6.0 and lower) and on these versions, it haves the old CE logo that can be customized on the desktop to make it look like a old version.
Features
Windows CE is optimized for devices that have minimal memory; a Windows CE kernel may run with one megabyte of memory.[4] Devices are often configured without disk storage, and may be configured as a "closed" system that does not allow for end-user extension (for instance, it can be burned into ROM). Windows CE conforms to the definition of a real-time operating system, with a deterministic interrupt latency. From Version 3 and onward, the system supports 256 priority levels[5] and uses priority inheritance for dealing with priority inversion. The fundamental unit of execution is the thread. This helps to simplify the interface and improve execution time.
The first version known during development under the code name "Pegasus"Template:Snd featured a Windows-like GUI and a number of Microsoft's popular apps, all trimmed down for smaller storage, memory, and speed of the palmtops of the day. Since then, Windows CE has evolved into a component-based, embedded, real-time operating system. It is no longer targeted solely at hand-held computers.[6] Many platforms have been based on the core Windows CE operating system, including Microsoft's AutoPC, Pocket PC 2000, Pocket PC 2002, Windows Mobile 2003, Windows Mobile 2003 SE, Windows Mobile 5, Windows Mobile 6, Smartphone 2002, Smartphone 2003, Portable Media Center, Zune, Windows Phone and many industrial devices and embedded systems. Windows CE even powered select games for the Dreamcast, was the operating system of the Gizmondo handheld, and can partially run on modified Xbox game consoles.
A distinctive feature of Windows CE compared to other Microsoft operating systems is that large parts of it are offered in source code form. First, source code was offered to several vendors, so they could adjust it to their hardware. Then products like Platform Builder (an integrated environment for Windows CE OS image creation and integration, or customized operating system designs based on CE) offered several components in source code form to the general public. However, a number of core components that do not need adaptation to specific hardware environments (other than the CPU family) are still distributed in binary only form.
Windows Embedded Compact Versions
Windows CE 1.0
Windows CE 2.0
Windows CE 3.0
Windows CE 4.0
Windows CE 5.0
Windows Embedded CE 6.0
Windows Embedded Compact 7
Windows Embedded Compact 2013
History
Windows Embedded Compact was formerly known as Windows CE. According to Microsoft, "CE" is not an explicit acronym for anything, although it implies a number of notions that Windows developers had in mind, such as "compact", "connectable", "compatible", "companion" and "efficient".[7][8] The name changed once in 2006, with the release of Windows Embedded CE 6.0, and again in 2011, with the release of Windows Embedded Compact 7.
Windows CE was originally announced by Microsoft at the COMDEX expo in 1996 and was demonstrated on stage by Bill Gates and John McGill. Microsoft had been testing Pegasus in early 1995 and released a strict reference platform to several hardware partners. The devices had to have the following minimum hardware specifications:
- SH3, MIPS 3000 or MIPS 4000 CPU
- Minimum of 4 MB of ROM
- Minimum of 2 MB of RAM with a back up power source, such as a CR2032 coin cell battery
- Powered by two AA batteries
- Weigh less than 1lbs
- A physical QWERTY keyboard including Ctrl, Alt and Shift keys
- An LCD display of 480×240 pixels with four shades of gray and two bits per pixel with touchscreen that could be operated by either stylus or finger nail
- An Infrared transceiver
- Serial port
- PC Card slot
- Built in speaker
Devices of the time mainly had 480×240 pixel displays with the exception of the Hewlett-Packard 'Palmtop PC' which had a 640×240 display. Each window took over the full display. Navigation was done by tapping or double tapping on an item. A contextual menu was also available by the user pressing the ALT key and tapping on the screen. Windows CE 1.0 did not include a cascading Start menu unlike Windows 95 and Windows NT 4.0 did. Microsoft released the Windows CE 1.0 Power Toys that included a cascading menu icon that appeared in the system tray. Also bundled were several other utilities, most notable were a sound applet for the system tray, enabling the user to quickly mute or unmute their device or adjust the volume and a 'pocket' version of Paint.
The release of Windows CE 2.0 was well received. Microsoft learned its lessons from consumer feedback of Windows CE 1.0 and made many improvements to the operating system. The Start menu was a cascading menu, identical to those found on Windows 95 and Windows NT 4.0. Color screens were also supported and manufacturers raced to release the first color H/PC. The first to market however, was Hewlett Packard with the HP 620LX. Windows CE 2.0 also supported a broader range of CPU architectures. Programs could be also installed directly in the OS by double clicking on CAB files. Due to the nature of the ROMs that contained the operating system, users were not able to flash their devices with the newer operating system. Instead manufacturers released upgrade ROMs that users had to physically install in their devices, after removing the previous version. This would usually wipe the data on the device and present the user with the setup wizard upon first boot.
Development tools
Visual Studio
Microsoft Visual Studio 2012, 2013, and 2015 support apps and Platform Builder development for Windows Embedded Compact 2013.[9]
Microsoft Visual Studio 2008 and earlier support projects for older releases of Windows CE/Windows Mobile, producing executable programs and platform images either as an emulator or attached by cable to an actual mobile device. A mobile device is not necessary to develop a CE program. The .NET Compact Framework supports a subset of the .NET Framework with projects in C#, and Visual Basic .NET, but not Managed C++. "Managed" apps employing the .NET Compact Framework also require devices with significantly larger memories (8 MB or more) while unmanaged apps can still run successfully on smaller devices. In Visual Studio 2010, the Windows Phone Developer Tools are used as an extension, allowing Windows Phone 7 apps to be designed and tested within Visual Studio.
Free Pascal and Lazarus
Free Pascal introduced the Windows CE port in Version 2.2.0, targeting ARM and x86 architectures. Later, the Windows CE header files were translated for use with Lazarus, a rapid application development (RAD) software package based on Free Pascal. Windows CE apps are designed and coded in the Lazarus integrated development environment (IDE) and compiled with an appropriate cross compiler.[10]
Platform Builder
This programming tool is used for building the platform (BSP + Kernel), device drivers (shared source or custom made) and also the apps. This is a one step environment to get the system up and running. One can also use Platform Builder to export an SDK (software development kit) for the target microprocessor (SuperH, x86, MIPS, ARM etc.) to be used with another associated tool set named below.
Others
The EmbeddedVisual C++ (eVC)Template:Snd a tool for development of embedded apps for Windows CE. It can be used standalone using the SDK exported from Platform Builder or using the Platform Builder's Platform Manager connectivity setup.
CodeGearDelphi PrismTemplate:Snd runs in Visual Studio, also supports the .NET Compact Framework and thus can be used to develop mobile apps. It employs the Oxygene compiler created by RemObjects Software, which targets .NET, the .NET Compact Framework, and Mono. Its command-line compiler is available free of charge.
Basic4ppcTemplate:Snd a programming language similar to Visual BasicTemplate:Snd targets the .NET Compact Framework and supports Windows CE and Windows Mobile devices.
GLBasicTemplate:Snd a very easy to learn and use BASIC dialect that compiles for many platforms, including Windows CE and Windows Mobile. It can be extended by writing inline C/C++ code.
LabVIEWTemplate:Snd a graphical programming language, supporting many platforms, including Windows CE.
AutoHotkeyTemplate:Snd a port of the open source macro-creation and automation software utility available for Windows CE. It allows the construction of macros and simple GUI apps developed by systems analyst Jonathan Maxian Timkang.[11]
Relationship to Windows Mobile, Pocket PC, and SmartPhone
Template:Wide image Often Windows CE, Windows Mobile, and Pocket PC are used interchangeably, in part due to their common origin. This practice is not entirely accurate. Windows CE is a modular/componentized operating system that serves as the foundation of several classes of devices. Some of these modules provide subsets of other components' features (e.g. varying levels of windowing support; DCOM vs COM), others which are separate (Bitmap or TrueType font support), and others which add additional features to another component. One can buy a kit (the Platform Builder) which contains all these components and the tools with which to develop a custom platform. Apps such as Excel Mobile (formerly Pocket Excel) are not part of this kit. The older Handheld PC version of Pocket Word and several other older apps are included as samples, however.
Windows Mobile is best described as a subset of platforms based on a Windows CE underpinning. Currently, Pocket PC (now called Windows Mobile Classic), SmartPhone (Windows Mobile Standard), and Pocket PC Phone Edition (Windows Mobile Professional) are the three main platforms under the Windows Mobile umbrella. Each platform uses different components of Windows CE, plus supplemental features and apps suited for their respective devices.
Pocket PC and Windows Mobile are Microsoft-defined custom platforms for general PDA use, consisting of a Microsoft-defined set of minimum profiles (Professional Edition, Premium Edition) of software and hardware that is supported. The rules for manufacturing a Pocket PC device are stricter than those for producing a custom Windows CE-based platform. The defining characteristics of the Pocket PC are the touchscreen as the primary human interface device and its extremely portable size.
CE v3.0 is the basis for Pocket PC 2002. A successor to CE v3.0 is CE.net.[12] "PocketPC [is] a separate layer of code on top of the core Windows CE OS... Pocket PC is based on Windows CE, but it's a different offering." And licensees of Pocket PC are forbidden to modify the WinCE part.[13]
The SmartPhone platform is a feature-rich OS and interface for cellular phone handsets. SmartPhone offers productivity features to business users, such as email, and multimedia abilities for consumers. The SmartPhone interface relies heavily on joystick navigation and PhonePad input. Devices running SmartPhone do not include a touchscreen interface. SmartPhone devices generally resemble other cellular handset form factors, whereas most Phone Edition devices use a PDA form factor with a larger display.
Releases
| Version | Changes |
|---|---|
| 1.0 | Released November 16, 1996.[14] Codename "Pegasus" and "Alder".[15]* Devices named "handheld PC" (H/PC)[12]* 4 MB ROM minimum
|
| 2.0 | Released September 29, 1997.[16] Codename "Birch".[15]* Devices named "Palm-sized PC"[12]* Real-time deterministic task scheduling
2.11 version (Palm-Size PC 1.1)Template:Snd changed screen resolution to QVGA, added handwriting recognition. 2.11 version (Palm-Size PC 1.2)Template:Snd based on Windows CE H/PC 2.11 kernel, removed Pocket Office. HandeldPC 2.11 version (HandheldPC Professional)Template:Snd added small versions of Microsoft Access, improved MS Office documents formats support. |
| 3.0 | Released June 15, 2000.[17] Codename "Cedar"[15] and "Galileo".
|
| 4.x | Released January 7, 2002.[18] Codename "Talisker/Jameson/McKendric".[15]* Integrated with .NET Compact Framework* Driver structure changed greatly, new features added
|
| 5.x | Released in August 2004.[15] Adds many new features. Codename "Macallan"[15]* Added automatic reporting for manufacturers[20]* Direct3D Mobile, a COM-based version of Windows XP's DirectX multimedia API[20]
|
| 6.0 | Released in September 2006. Codename "Yamazaki".[15]* Process address space is increased from 32 MB to 2 GB[22]* Number of processes has been increased from 32 to 32,768[23]
|
| 7.0 | Released in March 2011.
|
| 8.0 (2013) |
|
WinCE license PID
Question
- text/html12/3/2010 7:29:49 AMMr Prasad K0
Hi All:
What is PID while purchasing the licence for WinCE image? Is the PID inputted into the Image? How it will be inputted?
Thanks & best regards, Prasad K R S V
All replies
- text/html12/3/2010 1:19:17 PMBjoernF1
Hi,
The PID or ROMPID is a stamp that is located in the ROMHDR of the NK.bin file.
The "Product Key" that you receive when buying licenses for WinCE 6.0 plus some optional OEM numbers make up the PID.
You can use PB to obtain information on which type of license you will need for your project and to "stamp" the license key into the OS runtime image.
In PB see "Tools->"Platform Builder for CE 6.0"
To automate the process of "stamping" your image you could call "stampbin.exe" as part of custom Post-Make Image build action.
We use a small batch file that does the job for us.
More information on stampbin can be found here:
http://msdn.microsoft.com/en-us/library/ee504718.aspx
To use your Product Key create a ASCII text file and enter your 25 digit product key (Without any dashes "-") followed by a Whitespace followed by up to 5 Hex DWORDs containing your OEM data. If you do not want to use the OEM values set them to 0.
Using the Product Key inside the PID file requires the "-1" (Version 1 PID file) argument in the call to stampbin.
HTH,
Bjoern
- text/html12/26/2010 2:33:24 PMKIS_BOCS0
Hello Bjoern!
I have a licence key question:
I have a device (BEGA220A) which has preinstalled Win CE 5.0 but I don't have the licence key. (and as I read I can not get from the device unfortunately)
I downloaded this: http://www.microsoft.com/downloads/en/details.aspx?FamilyID=486e8250-d311-4f67-9fb3-23e8b8944f3e which is 120 days demo version only.
My question is, when I create a new image and download it into my device, do I lose my original licence?
What can I do to develop without any problem?
Thanks a lot!
KIS_BOCS
- text/html12/27/2010 4:03:06 PMPaul G. Tobey0
The license for Platform Builder IS NOT A LICENSE FOR WINDOWS CE SHIPMENT. Platform Builder is a piece of software that you need to buy to build Windows CE-based devices. When you buy it, it will have a license key as most MS products do: a string of letters and numbers that you enter to license that software. This is not the same as a license for each individual device on which you ship a copy of the operating system that you build USING PLATFORM BUILDER. That's a separate license.
I'm not sure what you mean by "lose my original license". The same key would obviously not be stamped on the new OS that you built using Platform Builder, no. That license belongs to the company that shipped Windows CE on the device and that's all it's good for; you can't redesign the operating system and reship the device to your customer without purchasing a license yourself to use for the device. You are not required to stamp the license data into the OS; it's a convenience.
So, there won't be any development problems that I can see, if you have a BSP for the this hardware. The problem is shipment of the commercial product when you are done, which will require you to purchase copies of the license from Microsoft or your Microsoft distributor for your device and the operating system you've built for it.
Paul T.
- text/html5/14/2013 8:23:08 AMSeeth0
Hey Paul,
I have stamped the license that we purchased and I used viewbin command to check if ROMPID and ROMHDR are changed.
I see some values other than 0x00000000 at this location.
But how do I see the PID on WEC7 device?
Any ideas?
Regards,
Seetharam
Seeth
- text/html5/14/2013 10:13:28 AMSeeth0
Run-time license applied to NK.bin will be visible anywhere on device?
I mean on Desktop or anywhere in control panel?
Seeth
- text/html6/11/2013 5:31:30 AMPravinMCP0
>>
Run-time license applied to NK.bin will be visible anywhere on device?
I mean on Desktop or anywhere in control panel?
>>
I have similar type of question. How to verify stamping image NK.bin with license key? or any program can find Run-time license key from NK.bin? I am asking this because in case of product shipment, production load the NK.bin with stamping and QC will verify the Run-time license key from NK.bin.
- text/html6/11/2013 8:34:39 AMVinoth[MCTS]0
There is no option in control panel or desktop. It resides in ROMHDR. ROMHDR is stored in the 1st page (Jump page) of the .nb0 image at the following address
#define ROM_SIGNATURE_OFFSET 0x40 // Offset from the image's physfirst address to the ROM signature.
#define ROM_SIGNATURE 0x43454345
#define ROM_TOC_POINTER_OFFSET 0x44 // Offset from the image's physfirst address to the TOC pointer.
#define ROM_TOC_OFFSET_OFFSET 0x48 // Offset from the image's physfirst address to the TOC offset (from physfirst).you can access it from OAL. if your RAMIMAGE start address is 0x80000000 then add the above offset to get the content of ROMHDR.
Then create an IOCTL in the OAL to retrieve the ROMHDR and call it using KernelIOControl()
Vinoth.R
www.e-consystems.com
http://vinoth-vinothblog.blogspot.com
- text/html6/11/2013 9:10:51 AMPravinMCP0
Thanks for reply. i'll try this.There is no option in control panel or desktop. It resides in ROMHDR. ROMHDR is stored in the 1st page (Jump page) of the .nb0 image at the following address
#define ROM_SIGNATURE_OFFSET 0x40 // Offset from the image's physfirst address to the ROM signature.
#define ROM_SIGNATURE 0x43454345
#define ROM_TOC_POINTER_OFFSET 0x44 // Offset from the image's physfirst address to the TOC pointer.
#define ROM_TOC_OFFSET_OFFSET 0x48 // Offset from the image's physfirst address to the TOC offset (from physfirst).you can access it from OAL. if your RAMIMAGE start address is 0x80000000 then add the above offset to get the content of ROMHDR.
Then create an IOCTL in the OAL to retrieve the ROMHDR and call it using KernelIOControl()
Vinoth.R
www.e-consystems.com
http://vinoth-vinothblog.blogspot.com
- Edited byPravinMCPTuesday, June 11, 2013 9:11 AM
- text/html6/11/2013 10:11:31 AMSeeth0
NK.nb0 will get changed if I stamp the license key to NK.bin using platform builder tool (stampbin)?
In my case the last modified time does change for NK.bin but not for NK.nb0.
I read NK.bin using viewbin and in that ROMPID has some values other than 0 as I mentioned in my previous reply. It means that the license key has been stamped successfully ?
Regards
Seeth
Seeth
- Proposed as answer bySeethTuesday, June 11, 2013 10:11 AM
- Unproposed as answer bySeethTuesday, June 11, 2013 10:12 AM
- Proposed as answer bySeethTuesday, June 11, 2013 10:13 AM
T20 / T30 WEC Software
Please find images, BSP, Platform Builder workspace, and other downloads and information about Toradex Windows Embedded Compact Software for Tegra T20/T30 in this article.
Warning: Always use the latest version of the Update Tool or NVFlash/Recovery Tools.
[*1] For T20 only. The WinCE 6 BSP / Workspace may work on Colibri and Apalis T30 but is not actively maintained for these modules.
[*2] For T30 only. Nvidia did not include the optional NEON unit in T20's implementation of the Cortex-A9 core, which is required to run WEC 2013.
[*3] Full featured WinCE7 image for Colibri T20
The WEC T20 / T30 BSP Release Details contain the roadmap for new features and bug-fixes and include also known issues and limitations of released BSP versions.
The Toradex Board Support Package for Windows CE is one of the most advanced BSPs available on the market. Aside from the standard Windows CE functionality, it includes a large number of additional drivers as well as optimized versions of standard drivers.
The Toradex bootloader and BSP were designed to be easily configurable. This relieves the application developer from the burden of creating a customized operating system image. Instead, the necessary adaptations can be made by registry settings and adding files to the on-board flash file system.
Toradex even provides the workspace for Microsoft's Platform Builder, which enables the customer to build exactly the same Windows CE image as the standard Colibri image.
The binary for our Colibri modules are available for download for free.
Before building your own Windows CE image, check if it is really required as our standard is very flexible and you can add a lot of drivers, components and programs without building your own image.
BSP Source Code
We do not provide the source code of our BSP. If you think you need source code, please contact us.
Microsoft Platform Builder Workspace
Toradex provides the Microsoft Platform Builder workspaces (solution files) which can be used to build an identical image as the pre-built binary images provided by Toradex. However, we recommend to use the binary images and configure them to your needs rather than building your own image. There are many advantages:
- The binary image is tested by Toradex and thousands of customers
- It is easier to upgrade to a newer BSP version since you only have to upload a new binary image instead of building your own image again
- You don't have to buy the Microsoft Platform Builder
- It's not necessary to build your own image if you want add or exclude features. As an example you can disable drivers, install drivers, add other WinCE features like the .NET Compact Framework, disable the explorer (desktop), etc.
- Toradex integrates the Microsoft Windows CE updates into their binary images.
In order to build a Windows CE image you need to download the workspace files and the BSP files which are located with the respective product BSP in our Software Section.
Overview on the Toradex Windows CE Features
We have invested a large amount of time and resource in developing our Windows CE operating system, and as a result, are able to provide you with an extremely robust, highly optimised and easily configurable operating system with a rich set of functional enhancements.
What do you mean by highly optimised?
To unlock the full potential of any hardware platform, it is important that the software is able to make use of the hardware resources in an efficient, effective way. We spend many thousands of man hours improving existing software implementations from device vendors and software providers to take advantage of features that may not have been fully utilised, or are simply not optimal. The result of such investment is that we really do squeeze every last drop of performance out of our systems, allowing you to fully leverage the capabilities of our computer modules.
Testament to this is our Windows Embedded Compact operating system for the Colibri T20 module which is able to cold boot (i.e. boot from power being applied) in 480 milliseconds. We have optimised many areas of operating system startup process, such as cache performance and concurrent driver loading, to achieve this very fast boot time, which today is unrivalled by any similar system.
What makes it easily configurable?
While our computer modules may be highly standardised, the applications they are deployed in are anything but. Every application has its own specific requirements and to be able to provide a standardised solution that is capable of meeting the requirements of a diverse range of applications requires a large amount of flexibility and configurabilty.
Through the use of the Windows registry, it is possible to configure the behaviour of our customised Windows CE operating system in almost every area you can think of. A short list of examples of things you can do with our registry configuration parameters are as follows:
- Configure display interfaces including all resolution and timing settings
- Rotate the display to support either portrait or landscape modes
- Change allocated video memory
- Configure audio and touch screen controller settings
- Disable any drivers that are not required
- Configure support for different serial interface standards
- Modify the behaviour of the USB stack including USB over current control
Our approach means you don't have to mess about creating your own operating system image - you can simply use ours and tailor it to your own needs.
Our Bootloader also provides provisions for system customisation. Examples include splash screen support on system startup and the ability to configure various system parameters such as MAC address and serial number.
What makes it extremely robust?
We have a very large customer base that have deployed our solutions into a hugely diverse range of applications with widely varying operating environments and conditions. From rally car instrumentation to tsunami warning systems, our operating system has been tried and tested and is one of the most mature available. Our systems run 24 hours a day, 7 days a week, without interruption.
The added advantage of so many customers using our standardised operating system is that when fixes or enhancements are made, everyone benefits from them. Our development engineers support our customers directly and so whenever there is an issue that needs addressing or an enhancement to make, we make sure that it is addressed and deployed promptly.
What functional enhancements do you provide?
We have extended the standard feature set provided by Windows CE to include additional functionality to help support your needs. For a list of such features, please see the section Special Features and Enhancements.
Drivers
Our standardised Windows CE operating system includes support for all of the standard features that are provided by the Colibri module. On top os this, we can also provide driver features for non-standard features which may be required, such as Bluetooth stacks and matrix keypads. The below table describes those driver which are included as standard and those which are available for purchase with support hours.
| Driver | Description | Cost (Support Hours) |
| FFUART | FFUART supports the full RS232 specification with all 9 signals. | - |
| BTUART | BTUART only supports RXD/TXD/CTS/RTS | - |
| IRDA | Handles the PXA270's IrDA port | - |
| Ethernet | 10/100Mbit driver for Davicom DM9000 | - |
| USB Host | 2 Ports supporting mass storage devices (USB-stick, hard disc, CD-ROM…) and other devices as keyboard, mouse, USB hub… | - |
| USB Client | Can be used as ActiveSync connection, mass storage or RNDIS | - |
| Audio | 16Bit stereo output (up to 48kHz), mic input, line-In | - |
| Touch Screen | All 4-wire resistive screens supported | - |
| Display | All types of displays supported. Easy configuration in registry | - |
| PS2 Mouse | Supports any standard PS/2 mouse | - |
| PS2 Keyboard | Supports any standard PS/2 keyboard | - |
| Compact Flash | Memory cards, Wireless LAN, modem, Bluetooth, serial card, GPS, GSM, … | - |
| SD/MMC | Memory cards, Wireless LAN, Bluetooth, GSM, GPS … | - |
| Wireless LAN | Support for different Wifi adapters | - |
| Flash File System | Standard FAT as well as TFAT (transaction safe FAT) are supported | - |
| SATA | Support for SATA interface (driver disabled in the registry by default) | - |
The following drivers are also available and can be purchased at Toradex. For more details on the Support Hours, please click here. | ||
| Bluetooth Support | Windows CE Bluetooth Stack and HCI Transport Driver for USB Devices | - |
| Colibri Plugin for TCPMP | Use the open source media player TCPMP (The Core Pocket Multimedia Player) on all Colibri modules | 8 |
| Matrix Keypad (PXAxxx only) | Fully customizable through registry (MK_IN, MK_OUT and scan code to virtual key) | - |
| External UART | Schematic and driver for external 16550-compatible UART controller attached to the system bus (up to 8 ports) | 8 |
| External Ethernet controller | Driver for the Asix AX88772B controller attached to USB. Reference schematics and further information about the controller are available on the Asix website | - |
| External Ethernet controller | Schematic and driver for Colibri PXA and Colibri T20 modules for an additional Ethernet controller attached to the system bus (Asix AX88796B). | 4 |
| Soft Key Touch Driver Extension | Support for "Soft Keys" on touch areas larger than the display size | - |
| SPI SD Card Driver | Add an additional SD memory card to one of the Colibri's SPI ports | 10 |
Services
Our Windows CE operating system supports a variety of services out of the box.
| Service | Description | Cost (Support Hours) |
| FTP Server | Access Colibri using the FTP File Transfer Protocol | - |
| HTTP Server | Allows the Colibri to act as a web server | - |
| Time Server / Client | Synchronize time with the network using the NTP protocol | - |
| File Server | File sharing over the network using the SMB protocol | - |
| OBEX Server | Protocol for IrDA File Transfer | - |
| Telnet Server | Access Colibri using the Telnet protocol | - |
The following services are also available and can be purchased at Toradex. For more details on the Support Hours, please click here. | ||
| Mail Server | SMTP, POP3 and mail sender services | 20 |
| Web Shop | Shopping cart, product selector, mail order form | on request |
Special Features and Enhancements
Our Windows CE operating system supports a range of additional features and enhancments to the standard Windows CE operating system.
| Feature | Description | Cost (Support hours) |
|---|---|---|
| Bootloader enhancements | Configuration through RS232, clear flash registry, download image to RAM, download image to Flash, set/save config structures, define initial GPIO configuration. Debug Functionality: erases flash range, write/read 32bit value at address. | - |
| Splash Screen | Display default start-up screen while Windows CE is booting. | - |
| GPIO Interrupts | Each GPIO can be configured to act as an interrupt source. | - |
| Power Management | Advanced Power Management, possible to set the wakeup sources and GPIO Sleep state in the Registry | - |
| SetFailSafe (PXAxxx only) | Add fail safe feature: This tool configures the bootloader to be fail-safe. This allows you to boot even after a failed bootloader update. | - |
| Bootloader Customizer Kit | The Bootloader Customizer Kit allows to place customer code directly in our standard bootloader. | 8 |
| .Net Framework 2.0 / 3.5 Flash Installer | Install the .Net Compact Framework 2.0 or 3.5 to the flash memory. | - |
| Silverlight Installer (CE 7 / CE 8 only) | Installs Silverlight support to the flash memory. | - |
| Multilanguage Support | Add additional languages to your system (can be switched at runtime) | 8 per western language |
| Large Input Panel | Add a larger software keyboard (SIP) (about 465x195 pixels) | - |
| WinCE Image Compression Tool | Compresses your own Windows CE image to about half of the original size. This saves Flash memory and improves the boot time. This feature is already used for Toradex binary images. | 4 |
| Splash-Screen Converter Tool | Converts your own bitmap to a Toradex Splash-Screen file | 4 |
Prior to starting Windows CE development for the Colibri module, we recommend you install the Colibri Software Development Kit (SDK). This will enable you to take advantage of some of the Toradex specific enhancements.
Software Development Kits for all supported versions of Windows CE/Embedded Compact can be downloaded using the following links:
Installation of Toradex SDKs for Visual Studio
Please follow the step by step documentation below to install the Toradex SDKs. The documentation has been tested on Windows 7 (32 and 64 bit) with Visual Studio 2008.
Install Windows CE 5.0 SDK
- Make sure VS2008 is up to date and close it before starting the installation.
- Download the Toradex Windows CE 5.0 SDK.
- Run the command prompt as administrator (Right-click -> Run as administrator).
- Browse to the folder you downloaded the SDK and run installation by typing:
- Select Custom Installation.
- We only need the ARM4I platform. So extend Embedded Visual C++ and set all platforms to Entire feature will be unavailable except the ARMV4I platform.
- Finish the installation process.
Install Windows CE 6.0 SDK
- Make sure VS2008 is up to date and close it before starting the installation.
- Download the Toradex Windows CE 6.0 SDK.
- Start the installation process.
- Finish Installation Process.
Install Windows Embedded Compact 7 SDK
- Install Windows Embedded Compact 7 specific updates for VS2008: [1], [2]
- Close VS2008 before start the installation.
- Download the Toradex Windows Embedded Compact 7 SDK.
- Run the installation process.
Install Windows Embedded Compact 2013 SDK
- Install Visual Studio 2012 or 2013 and make sure you have Application Builder for Windows Embedded Compact 2013 installed. You can get it here.
- Download the Toradex Windows Embedded Compact 2013 SDK.
- Run the installation process.
Updating from older SDKs
Older SDKs did not have unified names. With the following SDK version the new naming convention has been applied:
- CE 5 SDK 6.0
- CE 6 SDK 2.0
- CE 7 SDK 2.0
- CE 8 SDK 2.0
In case you want to migrate your project to one of the new SDKs, some renaming in the *.sln and *.vcproj files has to be done. Toradex provides a command line tool that does this job for you. Run the tool and provide the path to one of your projects as a parameter. You get the tool from here.
Installation issues
SDK not shown in Visual Studio
Some customers reported, that their SDK was not shown in Visual Studio after finalizing the installation process. Installing the SDK using user Administrator by command line as described for CE 5 SDK solved this issue. Try to uninstall the SDK and install it again by doing the following steps in such a case:
- Run the command prompt as administrator (Right-click -> Run as administrator).
- Browse to the folder you downloaded the SDK and run installation by typing:
Windows CE 5.0 SDK on Windows 10
When installing on Windows 10 we noticed that some users have issues with SDK not showing inside Visual Studio. To fix this issue please check that files are located in installation directory usually:
Then locate file and add this entry.
If the installation path of your SDK is different. Also, change your path inside the pasted code.
Webinar On-Demand: Windows Embedded Compact advantage with Toradex COMs powered by Freescale i.MX 6
All of this software is available for free if not stated differently. The table entries are encoded as follows:
f = full support
p = partial support
- = no support
N.A. = not available
Windows CE Tools
| Tool | Description | Apalis iMX6 | Apalis T30 | Colibri T30 | Colibri T20 | Colibri iMX6 | Colibri VFxx | PXA3xx | PXA 270 | Colibri iMX7 |
|---|---|---|---|---|---|---|---|---|---|---|
| AC97Tweak | Configures some special audio codec features which are not accessible through the common wave API. Audio input settings: source left/right, micboost, gain left/right, DC filter, High pass, mute. Audio output settings: gain left/right, bass, treble, de-emphasis, headphone driver, mute. Audio test features | - | p | p | p | - | - | f | f | - |
| ColibriCustomize | Customization possibility of the Colibri Win CE image. Automatically configures the registry for your own settings (Using .reg file). | - | - | - | - | - | - | f | f | - |
| ColibriDbgMsgLogger | Displays all debug messages from RAM buffer. | f | f | f | f | f | f | f | f | f |
| ColibriMonitor | Shows the usage of the CPU/RAM, processes/threads running, thread priority and has setting functionalities. | f | f | f | f | f | f | f | f | - |
| ColibriTweak | Adjusts system parameters like display settings, access registers, etc. of the Colibri module. | - | p | p | p | - | - | f | f | - |
| ConfigBlockEditor | Edit settings stored in the config block. | f | f | f | f | f | f | f | f | f |
| GPIOConfig | Provides an interactive interface to the versatile GPIOs of the Colibri modules. | - | f | f | f | - | p | f | f | - |
| RegAccessTool | Read from and Write to physical addresses (registers, etc.) in 8bit/16bit/32bit format (Formerly part of Colibri Tweak tool). | - | f | f | f | - | f | p | p | p |
| I2CTool | Tool to Read/Write on I2C. | f | f | f | f | f | f | - | - | - |
| SplashScreen | Changes the picture which you can see while WinCE is booting. Now integrated in to the Update Tool. | - | f | f | f | - | - | f | f | - |
| TouchTweak | Adjusts the touch screen driver to your touch screen if required. | - | - | - | - | - | - | f | f | - |
| ImageViewer (a) | Provides basic functionality to display a single image or a slideshow. | p | p | p | f | p | p | f | f | p |
| Launcher (a) | Automatically runs any .exe or .Ink file found in an AutoRun folder or copies files in a folder AutoCopy folder on each storage medium. | f | f | f | f | f | f | f | f | p |
| RTCSync (a) | Synchronizes the system time with the RTC chip on I2C. | f | f | f | f | f | f | f | f | - |
| UpdateTool (a) | Updates the WinCE Image and bootloader, warmboot or coldboot, etc, part of the standard image. | - | p | p | p | - | - | f | f | - |
| VideoPlayer (a) | included in standard WinCE image. | - | f | f | f | - | - | - | - | - |
NOTE:
- (a) Already included in the image.
See here for more information on our Windows CE features.
Download Here
PC Tools
| Tool | Description | Price (Support Hours) |
|---|---|---|
| Colibri Loader | Loads bootloader over JTAG (only for Colibri PXAxxx modules), load Images over Ethernet | Free |
| RemoteDisplay | Controls the Colibri module by a desktop PC (keyboard, mouse, display, file transfer) using a connection through ActiveSync (USB) or Ethernet. | Free |
| CreateTBin | This Windows program converts an OS binary file into a format that works with the Toradex Tool Chain. | Free |
| Splash Screen Customizer | Creates a customized splashscreen which can be shown while Windows CE is booting. | 4 |
| Win CE Image Compressor | Reduces the size of the Windows CE Image to about 50%. This leaves more flash space for user applications or the flash file system. | 5 |
What’s New in the Microsoft Windows CE Toolkit for Visual Basic v5.0 serial key or number?
Screen Shot
System Requirements for Microsoft Windows CE Toolkit for Visual Basic v5.0 serial key or number
- First, download the Microsoft Windows CE Toolkit for Visual Basic v5.0 serial key or number
-
You can download its setup from given links:
Microsoft Windows CE Toolkit for Visual Basic v5.0 serial key or number & Apps for Laptop & PC Free Download
Microsoft Windows CE Toolkit for Visual Basic v5.0 serial key or number& Free Download
Microsoft Windows CE Toolkit for Visual Basic v5.0 serial key or number
About Author
