Burning bootloader on Mega48v

Development Tools IDE 1.x
1

Hi

I have a custom board with an Atmega48V on.
I have connected an avrisp mkii through the isp pins.
When i open avr studio up, i can read the micro signature and confirm connection.

I know the mega48 is not officially supported, but i saw this thread and tried to test it.
http://forums.hackaday.com/viewtopic.php?f=2&t=2161

atmega48.name=Rotceh-hack QM7298 w/ ATmega48V xD

attiny48.upload.using=arduino
atmega48.upload.maximum_size=4094
atmega48.upload.speed=19200

atmega48.bootloader.low_fuses=0xE2
atmega48.bootloader.high_fuses=0xDF
atmega48.bootloader.extended_fuses=0xFF
atmega48.bootloader.path=atmega
atmega48.bootloader.file=atmega48.hex
atmega48.bootloader.unlock_bits=0x3F
atmega48.bootloader.lock_bits=0x0F

atmega48.build.mcu=atmega48
atmega48.build.f_cpu=8000000L
atmega48.build.core=arduino
atmega48.build.variant=standard

Put that inside the Boards.txt

I also changed the drivers on my avrisp mkii from jungo to libusb-win32.

But when i try to burn the bootloader onto the chip, i get this error message

 ***failed;  
avrdude: verification error, first mismatch at byte 0x0000
         0xff != 0x01
avrdude: verification error; content mismatch
2

woj

Were you able to this file?
atmega48.hex
Since the part is in the 168 family, can likely use the optiboot 168 bootloaded.

On the other hand, the '48 does not have a separate bootloader space:

For software security, the Flash Program memory space is divided into
two sections, Boot Loader Section and Application Program Section in ATmega88 and
ATmega168. ATmega48 does not have separate Boot Loader and Application Program sections, and the SPM instruction can be executed from the entire Flash.

Odd that a different chip is called here:
attiny48.upload.using=arduino

Signature Bytes:
ATmega48 0x1E 0x92 0x05 << matches listing for Atmega48 in avrdude.conf, good sign!
ATmega88 0x1E 0x93 0x0A
ATmega168 0x1E 0x94 0x06

atmega48.bootloader.low_fuses=0xE2
atmega48.bootloader.high_fuses=0xDF
atmega48.bootloader.extended_fuses=0xFF

Check these settings against pages 285-288, see what is being setup.