Bootloading Arduino Pro Mini 3.3V

Development Boards Arduino
1

Hi,

I think I screwed up :cry:

After reading through all kinds of blogs, wiki pages and datasheets I finally decided to try uploading a HEX file to the Arduino Pro Mini. After all, the setup was going to be for a prototype and the final product would be on a board with a standard ATmega 328P.

I was running the Arduino 1.5.6-r2 BETA and uploaded the ArduinoISP sketch to my Arduino Uno R2. All well, sketch uploaded.

Then I went on to connect the Pro Mini (3.3V) to the pins on the UNO.

As specified in the example, MISO to MISO, MOSI to MOSI and SCK to SCK, pin 10 went to the reset pin.

I hooked up the Pro Mini to the GND and 3.3V pins on the UNO.

After everything started up, I went on to burn the bootloader for ā€œArduino Pro or Pro Miniā€ with ā€œATmega 328 3.3V / 8 MHzā€ onto the COM port where the UNO was connected. The whole process didnā€™t take too long and failed with a verification error.

avrdude: verification error, first mismatch at byte 0x0000

0xff != 0x00

avrdude: verification error; content mismatch

I set out to investigate and it seems that there are some problems with 328 vs. 328p and according to the tutorial in at adafruit there are reported issues with the 1.5.2 beta.

Trying to upload the bootloader with avrdude from the command line fails as well (now with the stable 1.0.5-r2). After the first failed attemt, the signature is corrupted and requires the -F to burn.

avrdude -c arduino -p atmega328p -P COM5 -e -b 19200 -C ..\etc\avrdude.conf -F -U flash:w:ATmegaBOOT_168_a
tmega328_pro_8MHz.hex

avrdude: AVR device initialized and ready to accept instructions

Reading | ################################################## | 100% 0.02s

avrdude: Device signature = 0x000000
avrdude: Yikes!  Invalid device signature.
avrdude: Expected signature for ATMEGA328P is 1E 95 0F
avrdude: erasing chip
avrdude: reading input file "ATmegaBOOT_168_atmega328_pro_8MHz.hex"
avrdude: input file ATmegaBOOT_168_atmega328_pro_8MHz.hex auto detected as Intel
 Hex
avrdude: writing flash (32652 bytes):

Writing | ################################################## | 100% 2.80s

avrdude: 32652 bytes of flash written
avrdude: verifying flash memory against ATmegaBOOT_168_atmega328_pro_8MHz.hex:
avrdude: load data flash data from input file ATmegaBOOT_168_atmega328_pro_8MHz.
hex:
avrdude: input file ATmegaBOOT_168_atmega328_pro_8MHz.hex auto detected as Intel
 Hex
avrdude: input file ATmegaBOOT_168_atmega328_pro_8MHz.hex contains 32652 bytes
avrdude: reading on-chip flash data:

Reading | ################################################## | 100% 25.36s

avrdude: verifying ...
avrdude: verification error, first mismatch at byte 0x0000
         0xff != 0x00
avrdude: verification error; content mismatch

avrdude: safemode: Fuses OK

avrdude done.  Thank you.

The problem seems to be that the flash memory is not actually written? 2.8 seconds to write and 25.36 to read?

I added the -e flag to clear everything before burning but of course, no change there.

Could anyone help me out?

Thank you