Hi, I'm using a micro minimosd which is a board based on an arduino pro mini, I believe. It's this one.
To program it, you need to first load the EEPROM clear, and then load the provided firmware.
The thing is that I did something wrong (don't know what) but the firmware didn't properly upload, and now I can't load anything on it, not even the EEPROM clear.
The board seems to be still somehow working, as the leds light up and twinkle when I try to upload something, but it does actually nothing, so I was told I had to re-load the bootloader. For that, I bought a USBasp, and connected as shown in the picture (MISO with MISO, MOSI with MOSI, RST, etc.), and tried to burn the bootloader. But I get the following error message (sorry for the spanish part):
Arduino:1.6.12 (Windows 10), Tarjeta:"Arduino Pro or Pro Mini, ATmega328 (5V, 16 MHz)"
avrdude: warning: cannot set sck period. please check for usbasp firmware update.
avrdude: warning: cannot set sck period. please check for usbasp firmware update.
***failed;
avrdude: WARNING: invalid value for unused bits in fuse "efuse", should be set to 1 according to datasheet
This behaviour is deprecated and will result in an error in future version
You probably want to use 0xfd instead of 0x05 (double check with your datasheet first).
avrdude: warning: cannot set sck period. please check for usbasp firmware update.
avrdude: Expected signature for ATmega328P is 1E 95 0F
Double check chip, or use -F to override this check.
Error quemando bootloader
Este reporte podría tener más información con
"Mostrar salida detallada durante la compilación"
opción habilitada en Archivo -> Preferencias.
One thing that bothers me is that the port menu is greyed out when I use the USBasp, as if I couldn't select a port. Could that be the problem? I do have a port selection when I use the FTDI adapter.
I encountered the same issue with my Micro Minim OSD boards. The two that I bought came without a bootloader installed. Like you I burnt the bootloader and encountered the same error message. However, despite the error message the boards function correctly and I can now upload sketches as normal.
I suggest uploading the blink sketch (LED is on pin 13) to your board using your FTDI and see if it works. This should activate the green LED.
Your computer (and the Arduino IDE) should detect the FTDI adapter as a COM port, irrespective of whether it has a target board attached to it or not.
Sorry I didn't tell you anything earlier, but for some reason I didn't receive any notification of reply.
Thank you for your reply. I tried uploading the blink sketch as you suggested, but it didn't work either. I get the following message:
Arduino:1.6.12 (Windows 10), Tarjeta:"Arduino Pro or Pro Mini, ATmega328 (5V, 16 MHz)"
El Sketch usa 928 bytes (3%) del espacio de almacenamiento de programa. El máximo es 30.720 bytes.
Las variables Globales usan 9 bytes (0%) de la memoria dinámica, dejando 2.039 bytes para las variables locales. El máximo es 2.048 bytes.
avrdude: stk500_recv(): programmer is not responding
avrdude: stk500_getsync() attempt 1 of 10: not in sync: resp=0x6d
avrdude: stk500_recv(): programmer is not responding
avrdude: stk500_getsync() attempt 2 of 10: not in sync: resp=0x6d
avrdude: stk500_recv(): programmer is not responding
avrdude: stk500_getsync() attempt 3 of 10: not in sync: resp=0x6d
avrdude: stk500_recv(): programmer is not responding
avrdude: stk500_getsync() attempt 4 of 10: not in sync: resp=0x6d
avrdude: stk500_recv(): programmer is not responding
avrdude: stk500_getsync() attempt 5 of 10: not in sync: resp=0x6d
avrdude: stk500_recv(): programmer is not responding
avrdude: stk500_getsync() attempt 6 of 10: not in sync: resp=0x6d
avrdude: stk500_recv(): programmer is not responding
avrdude: stk500_getsync() attempt 7 of 10: not in sync: resp=0x6d
avrdude: stk500_recv(): programmer is not responding
avrdude: stk500_getsync() attempt 8 of 10: not in sync: resp=0x6d
avrdude: stk500_recv(): programmer is not responding
avrdude: stk500_getsync() attempt 9 of 10: not in sync: resp=0x6d
avrdude: stk500_recv(): programmer is not responding
avrdude: stk500_getsync() attempt 10 of 10: not in sync: resp=0x6d
Problema subiendo a la placa. Visita http://www.arduino.cc/en/Guide/Troubleshooting#upload para sugerencias.
Este reporte podría tener más información con
"Mostrar salida detallada durante la compilación"
opción habilitada en Archivo -> Preferencias.
When I plug the FTDI adapter, I do have the Port menu active. It's when I plug the USBasp that it's greyed out and I can't select anything. Maybe it's a drivers problem or something, but I don't know if it's actually required. Does it happen to you too? is your Port menu greyed out when plugging in the USBasp?
The USBAsp does not project a serial port. The IDE can find the USBAsp from the VID and PID - the port menu is ignored when doing burn bootloader/upload with programmer with a programmer that does not operate through a serial port.
Thank you DrAzzy. Then it has to be something else.
The first code I posted, at the end of it, it says: "Error quemando bootloader", which means "Error burning bootloader". So I assume the bootloader wasn't properly installed.
But yesterday I tried again and only got the "avrdude: warning: cannot set sck period. please check for usbasp firmware update." messages, so I assumed that this time, the bootloader was properly burnt.
However, I got the 2nd message above while trying to load EEPROM clear. Also the blink sketch failed. Is there any way to know if the bootloader is properly installed after I burn it? I don't think the FTDI adapter is failing, as I've used it for other boards like this.