Trouble Shooting

Before you start make sure you have the latest version of the tools.

The latest tools are always available at the support page on the Coridium Website-

Check your cables, check the LED

See Connect USB    All Coridium boards have an Green LED that is driven when power is applied.  If that LED is not on, check you connection, or using the Schematics trace the power connections.

Determining which COM port should be used

The tools will query the Window registry and will list the available COM ports.  If you are using a Coridium USB dongle, a Coridium card with built in USB connection, a SparkFun USB dongle or a FTDI USB cable; then those COM ports will be listed in capital letters.  Those in lower case are NOT using a Coridium dongle or built in USB port, do not select those.  If you are using some other serial connection, refer to the section on ISP checks .


In the example above, COM9 is a Coridium board, com1 and com2 are serial ports built into the PC.

You can also identify an FTDI port using the Device Manager.

Open the Control Panel>System>Device Manager

USB(COMx not appearing)

      If the USB Serial Port does not appear, check the connection and if its still not there install the driver.

Open the /Program Files(x86)/Coridium/Windows Drivers folder.   Run the .exe file in that folder.   This will install the FTDI driver.   The FTDI FT232RL is the USB device we use on the Coridium USB dongle.  

We use the FTDI VCP driver, more information on its installation can be found at their website .

Offline indicator

      This will be shown if the port you were using last time the program was run is no longer available.  You must reselect a Port using the Option Menu to reestablish communication with the ARM.  Make sure any other copies of MakeItC or BASICtools are closed, as you can not open a port simultaneously with more than one program.

Reset ARM shows no message

If your BASIC program does not appear to start up, hit the STOP button.  This will stop any known existing program, even those that alter the UART baudrates.  If your program sends a large amount of data to the UART, it may take a while for the STOP to respond.  You may need to close BASICtools and re-open them.  When BASICtools starts up it halts any existing user program.  At that point you can load a new program -- something short like PRINT 1234    ' will erase a run away program.

After STOP or restarting BASICtools you should get a welcome message.

Check Baud Rate

Or you might not have the correct baud rate selected.  Make sure it is set to 19200 or 115200 baud.  Baud settings in the Device Manager do NOT affect the MakeItc or BASICtools.  Firmware versions after 8.34 use 115.2 Kb, this includes Teensy, mBed and many boards we built after 2014.

Reset ARMexpress

Check ARM connection

TclTerm has some tools to verify a connection to the ARM chip.

The connection test will use the Coridium USB dongle or built in USB connection to place the ARM into ISP mode (holds P0.14, P2.10 or P0.1 low during RESET, depending on the part -- details in the corresponding NXP User manual).  Then a ? will be sent followed by "Synchronized".  If an appropriate answer is received a command to ID the part will be sent and that will be reported --

Or if no part is found

If no part is found go back check the connection, power connections, or which port has been selected.

If your USB/serial connection is something homebrew, and if you followed the Coridium reference schematics, you can use the test menu under options to wiggle the required RESET, BOOT and RXD pins to verify they are connected to the CPU.