Hi, I'am using ponyprog several years (mostly for programming AVR's) and it's my favourite program.
Now, I've found out, the ATmega1284P is not supported by this program. ATmega1284 belong to series of mega84, mega164, mega324 and mega644, and now is cheaper than mega644 was two years ago (now, costs of both are similar). Most important, there is produced in DIP package (contrary to e.g. mega128, can be simply use in bread-board).
It's way, to add support this mcu to ponnyprog? (I've listed trough datasheet, and its similar than other (84, 164, 324...) supported by pp, and in first view not very different tnan mega128 (it have more RAM and less I/O, and probably different fusses)). For my suprise, there are different device signature for mega1284 and mega1284P, but I wasn't able to discover any difference between them.


Thanks

Hi mluno,

I have compared the datasheets from ATmega644 range with ATmega1284 and it was possible to add this device to PonyProg2000. In attachment you will find the pre-compilled windows executable of PonyProg2000 with support for ATmega1284P.

Please try it and let me know the result. I do not have this device.
Thanks

Yours sincerely
sonix

mluno Wrote:
-------------------------------------------------------
> Hi, I'am using ponyprog several years (mostly for
> programming AVR's) and it's my favourite program.
> Now, I've found out, the ATmega1284P is not
> supported by this program. ATmega1284 belong to
> series of mega84, mega164, mega324 and mega644,
> and now is cheaper than mega644 was two years ago
> (now, costs of both are similar). Most important,
> there is produced in DIP package (contrary to e.g.
> mega128, can be simply use in bread-board).
> It's way, to add support this mcu to ponnyprog?
> (I've listed trough datasheet, and its similar
> than other (84, 164, 324...) supported by pp, and
> in first view not very different tnan mega128 (it
> have more RAM and less I/O, and probably different
> fusses)). For my suprise, there are different
> device signature for mega1284 and mega1284P, but I
> wasn't able to discover any difference between
> them.
>
>
> Thanks

Thanks for your effort. Is seems to be O.K. I have tested to load a simple program (LED blinking etc.) and disabling fuses (CKDIV8 and JTAGEN, to speed-up device and release GPIO pins used by JTAG in default). Have you any idea what test, or it is sufficient.

Only problem was, my device has signature 1E 97 06 instead of 1E 97 05 expected by pony prog. Since there is no difference between mega1284 and mega1284P (I didn't found any in http://www.atmel.com/Images/Atmel-8272-8-bit-AVR-microcontroller-ATmega164A_PA-324A_PA-644A_PA-1284_P_datasheet.pdf ), I have this different signature ignored.

Hi Mluno,

I have added also signature bytes 1E 97 06 for ATmega1284. Precompiled windows executable is attached. Could you try it, please? And no, another tests as you did are not needed.

Yours sincerely
sonix

mluno Wrote:
-------------------------------------------------------
> Thanks for your effort. Is seems to be O.K. I have
> tested to load a simple program (LED blinking
> etc.) and disabling fuses (CKDIV8 and JTAGEN, to
> speed-up device and release GPIO pins used by JTAG
> in default). Have you any idea what test, or it is
> sufficient.
>
> Only problem was, my device has signature 1E 97 06
> instead of 1E 97 05 expected by pony prog. Since
> there is no difference between mega1284 and
> mega1284P (I didn't found any in
> http://www.atmel.com/Images/Atmel-8272-8-bit-AVR-m
> icrocontroller-ATmega164A_PA-324A_PA-644A_PA-1284_
> P_datasheet.pdf ), I have this different signature
> ignored.

I have tested it. Now it works without "unknown device" message, i.e. works good.