Update of bug #22699 (project avrdude):
Status: None => Need Info
Assigned to: None => joerg_wunsch
_______________________________________________________
Follow-up Comment #1:
> 1. The following devices do not have AVR910 device code
> in the conf file: mega48, mega88, mega168. These should
> be added so a AVR910 can be used for these devices.
Klaus Leidinger uses 0x31, 0x33, 0x35, myAVR uses 0x6, 0x7,
0x8, respectively. Which one to chose, and why that one?
> 2. The following devices use device code 0x75 although that
> is already allocated to the mega16 bootloader. I suggest
> that device code 0x73 might be better: mega329, mega329p,
> mega3290, mega3290p, mega649, mega6490.
I agree that 0x75 is a poor choice, and should be avoided.
But in which respect would 0x73 (ATmega32 BOOT) be better
here?
> 3. The device code for mega162 is listed as 0x63 but this
> should be 0x62 because device code 0x63 is for the mega162
> bootloader.
There's no official assignment for the ATmega162 bootloader,
or the ATmega162 at all.
The closest match would be the ATmega161 which is kind of a
predecessor of the ATmega162 (code 0x60), but I don't know
for sure whether both use the exact same programming
parameters. Further, both Klaus Leidinger's and myAVR's
AVR910 implementation agree on using device code 0x63 for
the ATmega162 so changing that right now will cause further
incompatibilities.
_______________________________________________________
Reply to this item at:
<http://savannah.nongnu.org/bugs/?22699>
_______________________________________________
Message sent via/by Savannah
http://savannah.nongnu.org/
_______________________________________________
avrdude-dev mailing list
[email protected]
http://lists.nongnu.org/mailman/listinfo/avrdude-dev
