• 2Building the Platform Project
  • 2.1CPU Type
• 3Windows CE Image Customization
• 6Image Debugging

1. Compulab Driver Download Windows 7
2. Compulab Driver Download Torrent
3. Compulab Driver Download

Installing the Driver Package

• Close the Platform Builder Application if it is open.
• Copy the CM_X300_BSP directory to WINCE600Platform
• Copy the CM_X300 directory to WINCE600OSDesigns
• Launch VS2005 and open WINCE600OSDesignsCM_X300CM_X300.sln

View and Download CompuLab Fit-PC2 owner's manual online. Fit-PC2 desktop pdf manual download. URL of this page. Related Manuals for CompuLab fit-PC2. Desktop CompuLab FIT-PC4 Owner's Manual (9 pages) Desktop CompuLab fit-PC2i Owner's Manual. Release spacers using a 5.5mm nut-driver and remove with. Since no aging takes place during fitlet2 operation, Compulab provides 5 year warranty for the product. Operation in wide temperature range filtet2 is the first miniature PC by Compulab able to operate at the full industrial temperature range of -40°C to 85°C. Compaq Driver free download - Driver Booster, Bluetooth Driver Ver.5.0.1.1500.zip, WLan Driver 802.11n Rel. 4.80.28.7.zip, and many more programs.

Compulab Driver Download Windows 7

Software Download. Find the software repository for all of Compulab's product line below; Airtop Product line. Airtop2 Software Repository; Airtop Software Repository.

Building the Platform Project

The CM_X300 Platform Project is used to build CompuLab Windows Embedded CE demo image. It includes many components and is highly recommended as a starting point for a new project. The demo image is relatively large, ~35 MB. Typical Windows CE images for a specific application are much smaller, 8-15 MB.

To build the CM_X300 platform:

• select the Open->Project/Solution command from the File menu of the VS2005 and select the WINCE600OSDesignsCM_X300CM_X300.sln file.
• Check that the project is configured for Release.
• Perform Rebuild Solution from the Build menu (alternatively, perform Build->Advanced Build Commands->Clean Sysgen).

The build process takes about 15-20 minutes.

CPU Type

The CM-X300 may be assembled with two CPU types:

• PXA300 - the C624 option
• PXA310 - the C624M option

The default BSP configuration targets the PXA310 CPU.

Choosing CPU Type

The CPU type is defined in CM_X300_BSP.BAT file in the platform directory. Ensure that the BSP_CPU_TYPE setting corresponds with the correct CPU type. Leave the appropriate line without the REM directive:

Build Options

• Use Build->Advanced Build Commands->Sysgen when adding Platform Builder components (Catalog items) to the project.
• Use Build->Advanced Build Commands->Clean Sysgen when removing Platform Builder components (Catalog items) from the project.
• Use Build->Advanced Build Commands->Build Current BSP and Subprojects when modifying Compulab BSP components that are included in the project or performing changes in the BSP files.
• Use Build->Advanced Build Commands-> Rebuild Build Current BSP and Subprojects when adding/removing Compulab BSP components to/from the project.

Windows CE Image Customization

There are two ways to customize the Windows CE image:

1. Recommended method: Add or remove BSP components from the demo CM_X300 project.
2. Create a new platform project and then manually add all the necessary BSP components as described in the Platform Builder documentation. Refer to Windows CE OSDesign Development page.

BSP customization using batch files

The BSP is fully customizable and allows inclusion/exclusion of each component via BSP_NO environment variables.

To exclude a certain driver, set the BSP_NO environment variables in CM_X300_BSPCM_X300_BSP_COMMON.bat and rebuild the BSP with Build->Advanced Build Commands->Rebuild Current BSP and Subprojects.

The following table lists the BSP_NO environment variables that can be defined:

RAM-Based Registry support

The CM-X300 BSP is configured for HIVE-based registry with lazy flushing. The registry hive is located in the system NAND flash.To support a RAM-Based registry, perform the following actions:

• Add the RAM-based Registry component to the project
• Disable the following variables in the CM_X300_BSPCM_X300_PRODUCTION.bat:

• Perform 'Clean Sysgen' using Build->Advanced Build Commands->Clean Sysgen

Persistent File System

The CM-X300 BSP is configured to store the root directory in RAM, therefore the root filesystem is not persistent. To make the root and its subsequent folders persistent, change the Catalog item 'ROM and RAM File System' to 'ROM-Only file System'.

CM-X300 BSP Subprojects

In addition to the drivers supplied with the BSP, there are a few useful utilities distributed as Subprojects. Subprojects allow adding software modules to the build without modifying the BSP source code located in the Platform source tree.There are two Subproject types available with CM_X300_BSP:

• Subprojects that add optional functionality to the BSP are located in the WINCE600PLATFORMCM_X300_BSPSubprojects directory.

These Subprojects are provided with the source code.

• The Subprojects that add custom applications, control panel applets and registry settings to the demo image are located at WINCE600OSDesignsCM_X300Subprojects directory.

KITL Connection

Platform Builder communicates with a device using KITL protocol. For details about KITL refer to Microsoft's KITL Broadcast article.

The following actions should be performed in order to setup a KITL connection between the CM-X300 and Platform Builder 6.0:

1. Ensure that a serial terminal is connected to the CM-X300 as described in Setting up a console
2. Ensure that an Ethernet cable is connected to the CM-X300 platform
3. In Platform Builder, go to Target->Connectivity Options.
   
4. Click on Add Device and provide a device name (such as CM-X300).
   
5. In Kernel Service Map, select Ethernet for Download and Transport options and KdStub for the Debugger.
6. Press Download settings and at the same time, נoot the target device and press SPACE in the device console to get Eboot main menu.
7. Type 'D' to download the image from Platform Builder (results in a broadcast of BOOT ME messages).
8. Platform Builder will show the target device unique name (e.g. CM_X30064242) in the Active Devices area.
   
9. Press Transport settings and select Use device name from bootloader.
   

Once the connection is configured, download and launch the newly created WinCE image:

1. In Platform Builder Target toolbar, select the configured device and then select Target->Attach Device.
2. Ensure that Eboot is ready for download (i.e. Sends Boot Me messages).

Image Debugging

Platform Debugging with RETAILMSG

Debug messages output to the serial port may be enabled for both Retail and Debug build types.
To enable RETAILMSG output to COM-A serial port, set the 'STUART Usage' option to 'Debug Serial' in the BSP Configuration menu in Eboot

Platform Debugging over Ethernet

KITL allows platform debugging over Ethernet and enables use of VS2005 Remote Tools. During debug session, KITL redirects all the serial output into VS2005 output window.

• Choose the following platform options to enable platform debugging:
  • Enable kernel debugger.
  • Enable KITL.
• Perform Build->Advanced Build Commands ->Rebuild Current BSP and Subprojects.
• Start the debug session as described in Setup Target for CM_X300 Image Evaluation section.

See Also

• 5Installing Debian images onto the internal storage

Introduction

This article provides instructions needed to install the Debian Linux live image on the IOT-GATE-iMX8 / SBC-IOT-iMX8 device, using a Linux Host workstation and a USB flash drive.The image includes Linux kernel, device driver modules, and Debian root filesystem.

Preparation steps

• Obtain a Linux PC workstation.
• Obtain a USB flash drive. Any commercially available USB flash drive of 1GB (or larger) may be used for the installation.
• Download the IOT-GATE-iMX8 and SBC-IOT-iMX8 Debian Linux package from CompuLab website.
• Unzip the package to a directory on the host workstation.
• The Debian Linux live image file, mentioned below, can be found in the images subdirectory.
• Plug the USB flash drive into the host PC. From now we assume the device name of the flash drive on your Linux PC is /dev/sdX.

Compulab Driver Download Torrent

Installation

• Flash the image file to the USB flash drive:

Run Debian Linux image

• Insert the USB flash drive into one of the USB ports.
• Connect a standard USB cable (included in the kit) between your host PC and the IOT-GATE-iMX8/SBC-IOT-iMX8 Debug console connector. (see drawing)

Use a terminal emulator as described here

• Power-on the system.
• The system will automatically boot the live disk image from the USB flash drive.

Installing Debian images onto the internal storage

Please use the `CompuLab Deployment Tool` to install the IOT-GATE-iMX8 / SBC-IOT-iMX8 Debian Linux onto on-board eMMC storage.
The `CompuLab Deployment Tool` is a shell script that allows to deploy a working OS image from USB flash drive to the IOT-GATE-iMX8 / SBC-IOT-iMX8 on-board storage (eMMC).

Follow the step-by-step procedure for a selected image:

• In the terminal window issue, root privilege is needed (sudu):

• Follow the steps below:

Compulab Driver Download

Post installation

• Power-off the system.
• Remove the USB flash drive from the unit.
• Power-on the system.