Instructions

66Hardware

The library function ForceBootloader(), as well as a change in the "C-Control Configuration"

AVR32Bit Unit options lead to an internal reset, where the Autostart behavior is ignored. This is done

on purpose in order to make remote maintenance possible. In this case the user program can also

be launched from the IDE, or a pressure on the reset button triggers Autostart again.

On delivery, the Autostart jumper is set. Please remove, otherwise no program transfer is pos-

sible.

Remote Maintenance

To service an application with the AVR32Bit from afar, the application can use ForceBootloader() to

jump into the bootloader. If the Autostart-Jumper is set, an update of the application would again

start the program. You can prevent this, if you activate the Disable Autostart option in the C-Control

configuration after a ForceBootloader. When the application update and the desired option changes

are done, set Disable Autostart to off and restart the application from the IDE.

2.2.2.2 USB Troubleshooting

The USB Support C-Pro AVR32Bit Control is executed by the microcontroller itself, and not by an

external chip, like e.g. on the C-Control Pro Mega Applicationboard. This is problematic as far as the

Windows operating system does not always process interruptions of the USB system correctly. You

will notice this in everyday life, when sometimes a USB device (stick, hard disk or USB-to-serial

converter) only works when you plug it in a second time. To counteract this, several measures have

been taken to minimize the number of USB restarts:

The C-Control Pro AVR32Bit unit stays as long as possible in the firmware and seldom jumps to

the bootloader like the C-Control Pro Mega Units.

You can use the Start/Stop button to stop the Unit without having to perform a reset.

Pressing the reset button skips the USB initialization in the boot loader, and starts the firmware

directly. Only a power-on reset leaves the AVR32Bit module in the bootloader (if the Autostart-

Jumper is not set).

In rare cases, it may happen that the unit is not detected at power-on. This can be seen in the

Windows device manager, if there C-Control AVR32Bit COM port does not appear when you turn on

the unit. Please detach from the USB Hub (if any) and replug in, or if that does not help, perform a

restart of Windows. Then the C-Control Pro Unit is recognized again.

If the user program is started directly by a Autostart, no message "Interpreter started" is issued.

The reason is that the USB subsystem needs up to 2 seconds to activate the virtual COM port.

Since the user program starts running immediately, all the outputs of the first 2 seconds are lost.

Also debug messages are not visible in this time with an active Autostart. A start of the program

through the start button when the unit is in bootloader (e.g. after a power-on reset), behaves like a

Autostart. Therefore, there are also no outputs in the first 2 seconds.

IDE does not respond

During the execution of programs on the AVR32Bit, overwriting foreign memory can have an impact

to the IDE. In this case, the USB CDC protocol is no longer performed error-free by the AVR32, and

the virtual COM port on the PC can get into a blocking state, that will the IDE only allow to accept

data with delays (timeouts) . The IDE then no longer works properly. In normal case the IDE can be

get out of this situation by pressing the reset button on the AVR32Bit module, but sometimes it just

helps to quit the IDE with the Windows Task Manager.