Access to information is restricted depending on your login.
Request login-information through our contact form.
Access to information is restricted depending on your login.
Request login-information through our contact form.
There are many benefits in using a module, instead of making an own design.
If a Trizeps, in spite of it's small size, is still too big or if you plan to have a complete integration because of higher quantities, this can be done by Keith & Koep.
To run a product from the Trizeps-series your hardware only needs a power-supply of 3.3V. Supply-pins to the Trizeps-module should be buffered through capacitors. A voltage regulator with 1A nominal output should be sufficient.
Its recommended to additionally use following interfaces:
There are 3 ways of remote-debugging a Windows Embedded CE device:
The preffered and easiest way to debug an application is ActiveSync. This debug-transport is selected as default in the Keith & Koep SDK's and will be used by Visual-Studio and Embedded Visual C++ if you press F5
for debug.
To establisch an ActiveSync connection, you need to install ActiveSync ( see Microsoft's download website at http://www.microsoft.com/download) and connect the device to your PC using an USB-cable.
Another way to connect Visual-Studio to a target-device for debugging is an ethernet connection. This typically involves starting an application on the target-device and than connecting from Visual-Studio to this device.
The third possibility to debug an application is using the Platform-Builder Kitl-Interface. This is typically used, if the above debug-options don't give enough information or when debugging a driver. Kitl-debugging needs Microsoft Platform Builder and a special debug image to connect to. With a debug image you can step into most system calls. See the Getting Started Guides
found in the Board Support Packages (Microsoft)-section for details.
If you want to debug an application using the TCP/IP -connection instead of ActiveSync follow these steps:
.\Program Files\Common Files\Microsoft Shared\CoreCon\1.0\target\wce400\armv4i\
-directory to the device: i.e. to the flashdisk
-folder. If you are not using the english-version of Microsoft-Windows, .\Program Files\Common Files\
might have another name; i.e. in german: .\Programme\Gemeinsame Dateien\
.Show devices for platform:
should show the device associated to this SDK, if not select it.Use a specific IP address
to the IP-address of the device.F5
to debug the application.
If you can run the external Remote-Tools ( Program Files→Microsoft Visual Studio 2005→Remote Tools) but fail running Target→Remote Tools from inside Visual Studio and see this error message:
The Microsoft Active Sync reported the following error: Unable to load device side components. Please check server configuration settings.
Create a ARMV4
-folder and copy the contents of the folder:
C:\Program Files\Common Files\Microsoft Shared\Windows CE Tools\Platman\target\wce600\armV4i
to
C:\Program Files\Common Files\Microsoft Shared\Windows CE Tools\Platman\target\wce600\armV4
Hint: Target→Remote Tools uses the tools at: C:\Program Files\Common Files\Microsoft Shared\Windows CE Tools\Platman\bin\wce600\
, whereas the external tools use: C:\Programs\CE Remote Tools\5.01\bin\
.
Display flicker can have several reasons:
A small region at the end of flash is used to store the permanent registry (see Flash Division of Trizeps I to VI). If this is not availlable, the default-registry stored in the Windows CE image is used.
To store the registry:
To erase the registry:
All folders not stored under a drive or external store belong to the RAM-based filesystem (object-store).
To store files permanent copy them to the \flashdisk-folder or \TFFS-folder or to an externally mounted device i.e. \SDMMC Card, \Hard Disk ( USB-Drives), \Storage Card (Compact-Flash-Card). \flashdisk is a region of the NOR-flash where the OS-image resides. It is included in the system search path for programs and DLL's. \TFFS is the folder for a DiskOnChip-device ( if mounted on the Trizeps).
There are several ways to update a Trizeps-Device.
Using the bootloader, you may update the device with:
When using Windows CE, you may update the image while the OS is running, with the flashupdate or OS-Update-tool. On newer images, you can modify the image-file to have the extension .os. Double-Tap this file in the explorer and it will automatically start flashupdate with this files.
GPIO's are general-purpose pins, which may be configured as input, ouput or as special function pin. Most pins of the Trizeps-modules are GPIO's. Those pins can be used in application-programs, using Keith & Koep drvlib_app.dll ( see GPIO & SPin).
Most programs or drivers distributed for Windows Embedded CE use a CAB-file. For Trizeps you need a ARM-version of this cab-file. If the install fails to execute, it could be that the install-software only check for StrongARM (Trizeps1). To install this software to newer Trizeps-modules, which ie. use PXA270 as processor, set:
[HKEY_LOCAL_MACHINE\KUKINIT] "FakeStrongARM"=dword:1
Add the $device to the identifier:
HANDLE hfile=CreateFile(TEXT("\\$device\\COM10"), GENERIC_READ GENERIC_WRITE, 0,NULL, OPEN_EXISTING, 0, NULL);
Board Support Package. A Board-Support-Package contains drivers and software to build own OS-Images.
Software Development Kit. A Software-Development-Kit include header-files and libraries needed by an application to be build for a specified target-device.
_FLATRELEASEDIR is a variable used by the Platform-Builder to specify the output-directory for generated files. This directory contains the Windows Embedded CE Image nk_ram,nk_rom and nk_zip.nb0.