Instructions

404FAQ

There are many developing systems for the Atmel Mega CPU. Some of these Compilers are com-

mercial, others a free. A good example of a free development system is the GNU C-Compiler. You

can transfer programs, that you wrote with the GNU C-Compiler, to the Atmel Mega CPU with a

AVR ISP programmer. But once you overwrote the installed bootloader, there is no way back, you

cannot longer use the C-Control Pro software.

6.2 Mega

1. How can I switch on the Pull-Up resistor of a port?

First switch the port to input with PortDataDir() (or PortDataDirBit() ), then use PortWrite() (or

PortWriteBit() ) to write a "1" into the port.

2. No USB connection existing to the Application Board.

Has the FTDI USB driver been loaded onto the PC? Or does “Unknown Device” appear in the Hard-

ware Manager, when the USB connector is plugged in?

Has the correct communication port been set in Options->IDE->Interfaces?

Are the ports M32:B.4-B.7,A.6-A.7 resp. M128:B.0-B.4,E.5 erroneously being used in the software

(see pin assignment of M32 and M128)? Are the jumpers on the Application Board set to these

ports?

A signal on M32:PortD.2 resp. M128:PortE.4 (SW1) during startup will activate the serial Boot-

loader.

(Mega128 only) Is Port.G4 (LED2) on Low during Reset? See SPI Switch Off in chapter "Firm-

ware".

When the SD card is used in conjunction with USB and the application board, there is a collision

on the SPI bus. If you want to use the SD Card interface, you have to remove the jumper on the

application board (Mega128 PB.0 to PB.4 and PE.5) and to use the serial mode.

3. The serial interface does not issue any characters or does not receive any characters.

Are the Ports D.0-D.1 erroneously used in the software (see pin assignment of M32 and M128)?

Are the jumpers on the Application Board set to these ports?

4. The Application Board does not react to any commands when serially connected.

In order to get the Bootloader into the serial mode the button SW1 must be pressed during startup

of the Application Board (observe jumper for SW1). For the serial mode M32:PortD.2 resp.

M128:PortE.4 (SW1) can also be fixed to GND level.

5. The Hardware Application does not start by itself (Autostart Behaviour).

A signal on the SPI interface during startup may activate USB communication.

A signal on M32:PortD.2 resp. M128:PortE.4 (SW1) during startup may activate the serial Boot-

loader.