Arduino Compatible Pro Mini (HCARDU0059 & HCARDU0081)

Paul Ridd
Posts: 6
Joined: Thu Jan 15, 2015 1:41 pm

Re: Arduino Compatible Pro Mini (HCARDU0059 & HCARDU0081)

Post by Paul Ridd » Tue Dec 01, 2015 12:28 pm

Thanks Andrew. The calibration is stored in the EEPROM so thanks for confirming this is not erased.

As for the main problem - I, er, um, er, hadn't connected the DTR pin at all :oops:

Now it's plugged in it works so much better. Sorry.

SATTCAT
Posts: 2
Joined: Thu Dec 03, 2015 10:49 am

Re: Arduino Compatible Pro Mini (HCARDU0059 & HCARDU0081)

Post by SATTCAT » Mon Dec 07, 2015 11:28 am

Hi
I am trying to connect to an Arduino Compatible Pro Mini 5v board (HCARDU0059) from my Windows XP PC via a USB Serial Port Download Adapter (HCARDU0011).

I've made the following connections, all tested OK with a multimeter:
ADAPTER -- PRO MINI
3.3v -- (Not connected)
GND -- GND
VBUS -- VCC
TXD -- RXI
RXD -- TXO
DTR -- DTR

On the PC, I downloaded and installed "CDM v2.10.00 WHQL Certified.zip" from the FTDI website and I now see "USB Serial Port (COM6)" in Device Manager. This shows as "This device is working properly" under Device Status and, as expected, disappears when I unplug the adapter.
The STA light on the adapter glows brightly as soon as it is plugged into the PC.
On the Pro Mini, there's an LED near the end connector that glows brightly and another LED at the opposite end of the board that flashes continuously.

When I try to upload my sketch (fully tested on a standard Arduino Uno) the following happens:
(1) Sketch compiles OK in IDE with the expected "Binary sketch size: 9,822 bytes (of a 32,256 byte maximum)" message;
(2) IDE says "Uploading..." and progress bar rapidly advances from approx 50% to about 90% complete;
(3) After several seconds the flashing LED on the Pro Mini turns off;
(4) The TX LED on the adapter flashes a few times (not very brightly);
(5) The LED on the Pro Mini starts flashing again - this is probably no more than a second from when it turned off;
(6) After several more seconds the progress bar in the IDE goes to 100% complete and the following error is displayed:
avrdude: stk500_getsync(): not in sync: resp=0x00
or with the shift key pressed:
avrdude: usbdev_open(): did not find any USB device "usb"

Can anyone offer any advice as to what may be wrong?
Many thanks
Rob

andrew
Site Admin
Posts: 907
Joined: Sun Aug 05, 2012 4:15 pm

Re: Arduino Compatible Pro Mini (HCARDU0059 & HCARDU0081)

Post by andrew » Mon Dec 07, 2015 1:03 pm

3.3v -- (Not connected)
GND -- GND
VBUS -- VCC
TXD -- RXI
RXD -- TXO
DTR -- DTR
That looks correct to me.
"CDM v2.10.00 WHQL Certified.zip" from the FTDI website and I now see "USB Serial Port (COM6)" in Device Manager.
Again this seems like the driver is installed correctly.
On the Pro Mini, there's an LED near the end connector that glows brightly and another LED at the opposite end of the board that flashes continuously.
That's a good sign as it mean that the pro mini is alive and running code.
(4) The TX LED on the adapter flashes a few times (not very brightly);
This means the Arduino IDE has correctly managed to reset the Pro Mini, which then reboots into the bootloader, which in turn should accept your new sketch.
(6) After several more seconds the progress bar in the IDE goes to 100% complete and the following error is displayed:
avrdude: stk500_getsync(): not in sync: resp=0x00
This is a generic error message and basically means the the IDE is not getting any kind of response back from the pro mini. The main causes of this is either a bad connection or the Tx and Rx pins being connected in the wrong order. However it looks like you have that bit set up right.

What are you selecting for the board type?
Comments made by this poster do not necessarily reflect the views of Hobby Components Ltd.

SATTCAT
Posts: 2
Joined: Thu Dec 03, 2015 10:49 am

Re: Arduino Compatible Pro Mini (HCARDU0059 & HCARDU0081)

Post by SATTCAT » Mon Dec 07, 2015 1:45 pm

Hi Andrew
Many thanks for the quick reply.
I had left the board type as Arduino Uno, which is what I developed the code on (Doh!).
Switching it to the relevant Pro Mini fixed the problem.
Thanks again for your help
Rob

Post Reply