Trouble flashing Arduino Pro Mini with a sketch

[CaptainZap]

Hi Guys,

I really need your help, this thing is driving me nuts. I was trying to build my first LED Dimmer, and made the physical board with sockets and all, and when I got to the part of flashing my Pro Mini, I keep getting this error :

     avrdude: Version 5.11, compiled on Sep  2 2011 at 19:38:36
     Copyright (c) 2000-2005 Brian Dean, http://www.bdmicro.com/
     Copyright (c) 2007-2009 Joerg Wunsch

     System wide configuration file is "C:\Program Files (x86)\Arduino\hardware/tools/avr/etc/avrdude.conf"

     Using Port                    : \\.\COM3
     Using Programmer              : arduino
     Overriding Baud Rate          : 57600
     avrdude: Send: 0 [30]   [20] 
     avrdude: Send: 0 [30]   [20] 
     avrdude: Send: 0 [30]   [20] 
     avrdude: Recv: 
     avrdude: stk500_getsync(): not in sync: resp=0x00

     avrdude done.  Thank you.

I've looked online, tried several debug methods I found but nothing works. I'm using an FTDI adapter, and I remember some time ago I was able to flash my pro mini with a temperature sketch, I think. This is what I've tried, with no results :
http://www.instructables.com/id/A-solution-to-avrdude-stk500getsync-not-in-syn/?&sort=ACTIVE&limit=40#DISCUSS
COM3 is the correct port, the board is selected correctly, the led on pin 13 blinks ever few seconds, I even tried removing drivers and downgrading the version. My FTDI adapter has VID 403 and PID 6001 and I am running windows 8.1.

I would appreciate any help you can offer. Thank you.

[hek]

Try detatching anything that draws power from the Arduino while flashing.

[CaptainZap]

@hek The Mini Pro board is connected only to the FTDI adapter, as I went with sockets for both arduino and RF chip, so they can be replaced if something goes bad.

After some digging around I found this on the seller's page :

"I couldn't get to work with factory flashed bootloader- neither in arduino, wiring and stk500 mode (in avrdude). After flashing new bootloader (optiboot_atmega328-Mini.hex from Arduino) with USBasp it's working fine on "-c arduino" mode in avrdude. Here is factory flash dump: http://www.mediafire.com/download/0dazcq8yxv2anv3/boot_mini.7z"

Anyone can tell me how to reflash the bootloader for this board ? I have an arduino uno if it helps.

[hek]

And you have the correct power-settinng on FTDI matching the mini board you're using?

Replace usb cable?

[CaptainZap]

The wiring is done correctly, I've even tried to change the cables a few times until now but nothing works. I have no usb cable - the adapter has an usb port on it :
http://www.aliexpress.com/item/FT232-FT232RL-high-quality-USB-to-TTL-module/1955253925.html
http://www.aliexpress.com/item/Pro-Mini-Module-Atmega328-5V-16M-For-Arduino-Compatible-With-Nano/1503533345.html

[CaptainZap]

As per the suggestion from this thread I've tried to flash my UNO with the FTDI adapter, but it failed with the same error. It works without issue with the USB connection from the UNO.
I remember for sure that the adapter used to work, and I'm thinking that I might have a fake FTDI adapter. Anyone know how I can try to reflash it so it will work ?

[niccodemi]

@CaptainZap FTDI recently released driver update with intent to disable fake ftdi chips.

There is a solution.

[CaptainZap]

Well I don't think I have the exact same problem, only if they made another change to the driver - to display a fake ID after the chip was bricked ?

Here's what I see in Device Manager :

[CaptainZap]

Well it must be the FTDI adapter, I went ahead and turned my UNO into a programmer, re-written the bootloader on the pro-mini, then flashed the sketch, and I'll test it after I make some re-touches to the dimmer board.

Actually I have a question if you can answer it, the sketch says the following :

• The MOSFET Gate pin is connected to Arduino pin 3 (LED_PIN),
• The MOSFET Drain pin is connected to the LED negative terminal
• The MOSFET Source pin is connected to ground. -- is this the same as the Negative from the power supply or just GND pin from the Arduino. The schematic kind of confuses me.

LE: I think it's the - of the power supply :

[meanpenugin]

Hard to tell in the breadboard. Make sure the V12 is going to the RAW pin and not the GND pin.

The breadboard also does not show a connection from the Arduino to GND. So add a connection from the Arduino GND pins to the minus terminal of the power supply. (This missing piece in the breadboard diagram is probably the source of the question)

GND and the minus terminal of the power supply should always be connected.

The FET is being used to control the current trough the LED to GND
As long as it's not running the current through the Arduino, it's fine.
Practically,

• if you connect it to the Arduino GND ipin
• and the Arduino GND pin is connected to the minus terminal of the power supply
• Then the current is NOT going to go into the Arduino, it will go to the power supply's minus terminal (path of east resistance)
• So, anywhere there is a direct path to the minus terminal of the power supply is good.

Edward

[CaptainZap]

@meanpenugin
Thanks so much for the explanation, and I'll try it once again as soon as I have some free time. For anyone looking for the original thread here is a link to it.

[CaptainZap]

Thanks to @meanpenugin help I was able to finish with the soldering, but now I'm encountering trouble controlling the device.
For example I wasn't able to include it properly the first time, but after a few tries it was added on the dashboard and for some reason it has parent node 255 instead of GW ?

And when I try to control it I'm getting all sorts of errors :

08      12/02/14 12:44:38.784   JobHandler_LuaUPnP::HandleActionRequest device: 40 service: urn:upnp-org:serviceId:Dimming1 action: SetLoadLevelTarget <0x2eca0680>
08      12/02/14 12:44:38.784   JobHandler_LuaUPnP::HandleActionRequest argument DeviceNum=40 <0x2eca0680>
08      12/02/14 12:44:38.785   JobHandler_LuaUPnP::HandleActionRequest argument serviceId=urn:upnp-org:serviceId:Dimming1 <0x2eca0680>
08      12/02/14 12:44:38.785   JobHandler_LuaUPnP::HandleActionRequest argument action=SetLoadLevelTarget <0x2eca0680>
08      12/02/14 12:44:38.785   JobHandler_LuaUPnP::HandleActionRequest argument newLoadlevelTarget=100 <0x2eca0680>
08      12/02/14 12:44:38.785   JobHandler_LuaUPnP::HandleActionRequest argument rand=0.12523629035042994 <0x2eca0680>
51      12/02/14 12:44:38.789   0x31 0x35 0x3b 0x30 0x3b 0x31 0x3b 0x31 0x3b 0x33 0x3b 0x31 0x30 0x30 0xd 0xa (15;0;1;1;3;100\r\n) <0x2af2a000>
52      12/02/14 12:44:38.856   0x30 0x3b 0x30 0x3b 0x33 0x3b 0x30 0x3b 0x39 0x3b 0x73 0x65 0x6e 0x64 0x3a 0x20 0x30 0x2d 0x30 0x2d 0x31 0x35 0x2d 0x31 0x35 0x20 0x73 0x3d 0x30 0x2c 0x63 0x3d 0x31 0x2c 0x74 0x3d 0x33 0x2c 0x70 0x74 0x3d 0x30 0x2c 0x6c 0x3d 0x33 0x2c 0x73 0x74 0x3d 0x66 0x61 0x69 0x6c 0x3a 0x31 0x30 0x30 (0;0;3;0;9;send: 0-0-15-15 s=0,c=1,t=3,pt=0,l=3,st=fail:100) <0x2e85d680>
08      12/02/14 12:44:46.039   JobHandler_LuaUPnP::HandleActionRequest device: 40 service: urn:upnp-org:serviceId:Dimming1 action: SetLoadLevelTarget <0x2eca0680>
08      12/02/14 12:44:46.039   JobHandler_LuaUPnP::HandleActionRequest argument DeviceNum=40 <0x2eca0680>
08      12/02/14 12:44:46.039   JobHandler_LuaUPnP::HandleActionRequest argument serviceId=urn:upnp-org:serviceId:Dimming1 <0x2eca0680>
08      12/02/14 12:44:46.039   JobHandler_LuaUPnP::HandleActionRequest argument action=SetLoadLevelTarget <0x2eca0680>
08      12/02/14 12:44:46.040   JobHandler_LuaUPnP::HandleActionRequest argument newLoadlevelTarget=0 <0x2eca0680>
08      12/02/14 12:44:46.040   JobHandler_LuaUPnP::HandleActionRequest argument rand=0.9738186305664368 <0x2eca0680>
51      12/02/14 12:44:46.048   0x31 0x35 0x3b 0x30 0x3b 0x31 0x3b 0x31 0x3b 0x33 0x3b 0x30 0xd 0xa (15;0;1;1;3;0\r\n) <0x2af2a000>
52      12/02/14 12:44:46.096   0x30 0x3b 0x30 0x3b 0x33 0x3b 0x30 0x3b 0x39 0x3b 0x73 0x65 0x6e 0x64 0x3a 0x20 0x30 0x2d 0x30 0x2d 0x31 0x35 0x2d 0x31 0x35 0x20 0x73 0x3d 0x30 0x2c 0x63 0x3d 0x31 0x2c 0x74 0x3d 0x33 0x2c 0x70 0x74 0x3d 0x30 0x2c 0x6c 0x3d 0x31 0x2c 0x73 0x74 0x3d 0x66 0x61 0x69 0x6c 0x3a 0x30 (0;0;3;0;9;send: 0-0-15-15 s=0,c=1,t=3,pt=0,l=1,st=fail:0) <0x2e85d680>

Any way you can help me resolve this ?
Note that the voltage for the output is not adjusted when I try to control the level of the device.
One thing I've noticed is that after first powering the node the voltage drops consistently from ~9.5 V to about 0.01V in like 1 minute or so. And my arduino pro mini, powered by 12 V (~12.3V actually) is burning up really bad. I believe I might have a loop of some sort in my design ?

Thanks.

[meanpenugin]

Hi,

Did you check the voltage of the output of the power supply?
I bet it's over 12V

LE33 seems to allow up to 20V
Arduino Mini Input Voltage range is 7-9 V
http://arduino.cc/en/Main/ArduinoBoardMini

I would check voltages at all the points to make sure it is in range.
Double check at the plugs (if you are using them) to make sure it's not shorted

Edward

[CaptainZap]

Yes, I did check the output it's 12.3 Volts and my chinese knockoff of the pro mini is rated to work with 12V. I'll try to get a regulator to power it at 5V instead and see how it goes. I don't use LE33, and went instead for the cheaper version the SOT23.
To power it to 5V I intend to use one of those USB adapters for the car's cigarette lighter, because I have a few lying around in my car.

[korttoma]

I'm running a similar setup for my RGBW led strip. Feeding my 5v Arduino Pro mini with 12V on the raw pin and powering the radio from VCC through a ams1117 3.3v regulator. Newer had any problems with it but I do recommend a high quality 12v source since the radio is sensitive to disturbance from the power source.

http://forum.micasaverde.com/index.php/topic,18103.msg157785.html#msg157785

I think you should check your wiring again, and again

[pete1450]

I apologize if you are aware of this, but are you pressing the reset button once the sketch is ready to transmit? Using a sparkfun FTDI board with knockoff pro minis, I press the reset button as soon as the first TX light blinks on serial board. If I don't: similar errors.