I know this is an old post, but there are a few conversations about voodoo in the answers around these ideas, let's try to be a little more real about what is happening and summarize the good materials to check:
In principle, when this happens, it is recommended that you enable avrdude mode for avrdude in order to better understand what is happening. To do this, you only need to go to the settings and check the detailed mode window. It is also a good idea to step away from the arduino IDE and launch the console to be more comfortable reading the avrdude output that you click on the upload button.
What is important for entering 3 or 4 -v into a team call. This is what the avrdude command looks like with the parameters compiled, since they completely depend on how Arduino was installed:
avrdude -v -v -v -v -C /path/to/avrdude.conf -patmega328 -P/dev/usbport -U flash:w:/path/to/firmware.hex
A good way to get the right command line to use is to copy it from the verbose output of the Arduino IDE output log when verbosity is enabled.
When you get avrdude: stk500_recv(): programmer is not responding , it basically means that something is wrong before the blink starts. Basically you need to check (from hardware to software, low to high):
- if the cable and / or connectors do not have microcommands;
- if no soldering points are closed (i.e. touching something metallic), this means:
- if there is no short circuit on the circuit board between
Rx and Tx (usually pins 1 and 0 ); - if there is no contact with a metal element under the board or small bits between the legs of the components (for example, FTDI, atmega chip or any other);
- if the atmega chip has not failed (GND / VCC shortcut or cut or VCC input is dead ...);
- if Arduino pins
1 and 0 are not used by any screen or custom design ( /!\ does not apply to leonardo, since it has independent USB processing); - if the USB to UART converter does not have a problem (
FTDI for the older duemilanove or Atmega16U2 for the new Unos); - if the Atmega328 chip is fried or improperly installed;
- if the bootloader has been overwritten or does not work;
- if the right bit rate is used to enter the bootloader;
- if the target MCU and Board are set to the correct settings;
usually avrdude -v -v -v -v can help find a lot at what stage it fails. Could he even connect to the USB port (cable failure, USB / UART, PCB ...) or a problem with the bootloader.
Update: I tried turning on the Atmega and installing it in the other direction. Now I have no problems downloading, but then nothing happens. The LED indicator also does not blink.
I am afraid that if you change the position of the atmega, and then it does not work, then the fact that you put the power source on the digital contacts may have burned your chip.
zmo Jan 31 '14 at 23:04 2014-01-31 23:04
source share