Objective Development Forums

Porting BootloadHID to mega64 BOOTLOADER_ADDRESS ??

2008-04-18T23:26:17+02:00

Thanks!

I was unnecessarily confusing myself

Statistics: Posted by Guest — Fri Apr 18, 2008 11:26 pm

Porting BootloadHID to mega64 BOOTLOADER_ADDRESS ??

2008-04-17T09:22:50+02:00

8k flash size minus 2k boot loader = 6k, or in hex 1800.

Statistics: Posted by christian — Thu Apr 17, 2008 9:22 am

Hey!

2008-04-17T07:11:38+02:00

I did not get it!

I am trying to figure out BOOTLOADER_ADDRESS for atmega8.

Can you explain me how to find it?

Thanks!

Statistics: Posted by Guest — Thu Apr 17, 2008 7:11 am

Porting BootloadHID to mega64 BOOTLOADER_ADDRESS ??

2008-03-28T15:06:55+02:00

Crystals never have deviations of more than several 100 ppm. That's certainly within the tolerance (of much less than 1% for crystal clocks, BTW).

If it works on one computer but not on another, you probably have voltage level problems on D+ and D-. Please have a look at the zener diodes and voltage levels.

Statistics: Posted by christian — Fri Mar 28, 2008 3:06 pm

It works :D

2008-03-26T02:37:40+02:00

With the settings provided by Dirk it correctly shows up on my mac. On my linux box i still get an error about not correctly assigning an address; but as the device is intended to run with the mac it's no problem. - Tomorrow i will take an oscilloscope and look at the crystal if it's within the 1% tolerance mentioned in "bootloaderconfig.h".

Many thanks,

Johannes

Statistics: Posted by muenchner — Wed Mar 26, 2008 2:37 am

Porting BootloadHID to mega64 BOOTLOADER_ADDRESS ??

2008-03-25T20:51:44+02:00

Use

BOOTSZ1 = 0
BOOTSZ0 = 0

for a 1024 word bootloader on the mega16.

BOOTLOADER_ADDRESS = 3800

Regards,

Dirk

Statistics: Posted by STB — Tue Mar 25, 2008 8:51 pm

Likewise problem

2008-03-24T22:27:39+02:00

Hello,

i have an analog problem: I want to use BootloadHID on a mega16 with a 16Mhz crystal. I already changed the frequency in bootloaderconfig.h to "#define USB_CFG_CLOCK_KHZ 16000".
Looking at the documentation of the mega64 i got out, why to use MCUCR instead of GICR on a mega64 (just searched for IVCE and voila), but concerning the BOOTLOADER_ADDRESS i'm lost.

Regards
Johannes

Statistics: Posted by muenchner — Mon Mar 24, 2008 10:27 pm

Porting BootloadHID to mega64 BOOTLOADER_ADDRESS ??

2008-03-24T18:03:20+02:00

I managed it myself.

For all other who want to use it with the mega64, only a few changes are to apply.

Makefile:

Code:

DEVICE = atmega64
BOOTLOADER_ADDRESS = F800

main.c

Code:

GICR = (1 << IVCE);  /* enable change of interrupt vectors */
GICR = (1 << IVSEL); /* move interrupts to boot flash section */
(...)
GICR = (1 << IVCE);  /* enable change of interrupt vectors */
GICR = (1 << IVSEL); /* move interrupts to boot flash section */

change to:

Code:

MCUCR = (1 << IVCE);  /* enable change of interrupt vectors */
MCUCR = (0 << IVSEL); /* move interrupts to application flash section */
(...)
MCUCR = (1 << IVCE);  /* enable change of interrupt vectors */
MCUCR = (1 << IVSEL); /* move interrupts to boot flash section */

Regards,

Dirk

Statistics: Posted by STB — Mon Mar 24, 2008 6:03 pm

Porting BootloadHID to mega64 BOOTLOADER_ADDRESS ??

2008-03-24T18:11:09+02:00

Hi !

I'm trying to port the BootloadHID to the mega64.

The entry BOOTLOADER_ADDRESS is unclear to me, i do not understand, why it is pointing to 0x1800 on the mega8 in my opinion this must be 0x0C00. I never worked with code in the bootblock area.

Who can explain me what BOOTLOADER_ADDRESS is used for.

Regards,

Dirk

P.S.: The USB stack is a piece of great work, im currently using ist to emulate a Keyboard, Mouse and some data Transfer which works perfect on the mega64

Statistics: Posted by STB — Mon Mar 24, 2008 4:06 pm