AND9621/D

www.onsemi.com

3

The AXDBG−2−GEVK uses the USB Serial Converter B.

Right click on the B instance, and under the advanced

properties, make sure that enable VCP is selected. VCP

stands for Virtual COM Port. See the picture below.

Figure 4.

If the AXDBG−2−GEVK still doesn’t connect, than its

likely the EEPROM for the FTDI USB to serial chip has not

been programmed or has somehow been erased.

Issuing the following command from a CMD window will

program the FTDI EEPROM.

axftdieeprog.exe -p -f -s 3 -B

The “−s 3” part of the command specifies to make the

debugger number 3. For more details refer to application

note AND9330, production programming.

Now the debugger should work. Verify from the CMD

window by issuing:

axsdb --listserials

The command should return a 3 if the debugger is found.

For more debug interface information, refer to application

note AND9370, debug interface software manual.

Q3: I Installed AX::CodeBlocks but the SDCC compiler

is not in my path. What should I do?

A3: The easiest solution is to uninstall RadioLAB and the

AX::CodeBlocks IDE package from your machine.

Before reinstalling, make sure that the debugger is NOT

plugged in and also that the AX::CodeBlocks IDE installer

is ran BEFORE the RadioLab installer.

If the installation is done in the right order, the SDCC

compiler should be available from CodeBlocks when started

for the first time. See the Figure 5.

Figure 5.

If you know the SDCC compiler is installed and you get

errors related to the compiler path not found, it’s also

possible to set the compiler path in AX::CodeBlocks by

activating the following menu Settings−>Compiler.

Then change the default compiler to SDCC as shown

below.

Figure 6.

It may also be useful to verify that the SDCC compiler is

in the search path as shown in Figure 7.