Instructions

16Hardware

The message "C-Control Pro USB Device has not passed the Windows Logo Test ...." will normally

appear. This does not mean that the driver has failed during the Windows Logo Test. It merely

means that the driver has not taken part in the (quite costly) Redmond Test.

Here click "Continue Installation". The USB driver should then be installed after a few seconds.

In the PC software click on IDE in menu Options and select the area Interfaces. Here select the

communication port "USB0".

The FTDI driver supports 32 bit and 64 bit operating systems. The specific drivers are located in

the "FTDI USB Driver\i386" and "FTDI USB Driver\amd64".

Serial Connection

Due to the slow transmitting speed of the serial interface the USB connection should preferably be

used. If however due to hardware grounds the USB interface is not available then the Bootloader can

be switched into the Serial Mode.

To do this the key SW1 has to be kept pressed during power-up of the Application Board. After this

the Serial Bootloader Mode will be activated.

Select in the IDE the correct COM Interface.

2.1.2 Firmware

The operating system of C-Control Pro consists of the following components:

Bootloader

Interpreter

Bootloader

The Bootloader is available at any time. It serves the serial or USB communication with the IDE. By

use of command line commands the Interpreter and the user program can be transferred from the PC

to the Atmel Risc Chip. If a program is compiled and transferred to the Mega Chip the current Inter-

preter is also transferred at the same time.

If instead of the USB interface a serial connection should be set up from the IDE to the C-Con-

trol Pro module then the push button SW1 (Port M32:D.2 and M128:E.4 resp. at low level) must be

held pressed during power-up of the module. In this mode any communication will be directed

through the serial interface. This is useful when the module has already been incorporated into the

hardware application and the application board is thus not available. The serial communication how-

ever is considerably slower than the USB connection. In serial mode the USB pins are not used and

are thus available to the user for other tasks.

Since SW1 initiates the serial Bootloader during module start there should be no signal on Port

M32:D.2 and M128:E.4, resp. during power-up of the application since these ports are also usable

as outputs.