AND9621/D

www.onsemi.com

2

APPLICATIONS INFORMATION

Q1: When running the AX::CodeBlocks IDE, I get the

following pop−up message when I try to debug. What

does it mean?

Figure 1.

A1: There are several reasons that this pop−up message

can occur.

The most likely cause for this pop−up is the ribbon cable

between the AXDBG−2−GEVK board and the development

board is not plugged in correctly. The debug link will not

work and you will get the message shown above.

The header for the ribbon cable is keyed on

AXDBG−2−GEVK, and the ribbon cable should plug into

the development board such that the ribbon cable faces away

from the development board (as shown below).

Figure 2.

If the ribbon cable is plugged in correctly and the pop−up

message is given, then the microcontroller is locked with a

key. The locking is normally done as a security measure to

avoid that the software can be read out or modified.

If “Yes” is selected on the pop−up, all the factory

calibration and any software stacks will be erased. Normally

“No” is the appropriate response.

NOTE: Devices that are sold pre−programmed with

software stacks (with AT interface, such as

AX−SFUS) are locked at the factory and the key

is a secret. If reprogramming is attempted the

calibration data and the software stack will be

erased and this is non−recoverable and will

render the chip inoperable.

If problems remain, please review Q2 for tips on solving

debug link and serial communication problems.

Q2: I’m having serial communication problems or

can’t get the AX debug link to connect to the

development board. What can I do?

A2: First check that the ribbon cable is plugged in

correctly as shown in Q1 of this document.

If the cable is plugged in correctly, then there may be a

problem with the virtual COM port.

Open the Windows device manager and verify a COM

port is shown that corresponds to the AXDBG−2−GEVK

board. See the picture below (USB Serial Port – COM8 in

this example).

If needed unplug and re−plug the AXDBG−2−GEVK

board to verify that a COM port is associated with it. The

first time an AXDBG−2−GEVK is plugged in, Windows

may need time to find the driver. This normally takes less

than 5 minutes.

Once a valid driver is installed and the COM port shows

up, there will be two serial converters, A and B, as shown in

the picture below.

Figure 3.