Peter Bozzay wrote:
> "The differential input channels are not tested for devices in PDIP
> Package. This feature is only guaranteed to work for devices in TQFP
> and QFN/MLF Packages."
But that doesn't mean anything were different at the chip level. It's
still the same die that is built into t
Hi,
The next step will be adding separate menu positions for DIP and TQFP
packages :-)
Use commercial tools and it's already here. Atollic True Studio for
Cortex M3 is an example. Different entries for different packages.
Some difference in features/errata/workaround in different packages or
On 6/18/2011 2:08 AM, j...@lillahusetiskogen.se wrote:
On Sat, 18 Jun 2011 10:02:19 +0300
Oleksandr Redchuk wrote:
2011/6/18, Royce Pereira:
So the menu item for 32A is just for psychological purposes !
The next step will be adding separate menu positions for DIP and TQFP
packages :-)
Use
On Sat, 18 Jun 2011 10:02:19 +0300
Oleksandr Redchuk wrote:
> 2011/6/18, Royce Pereira :
>
> > So the menu item for 32A is just for psychological purposes !
>
> The next step will be adding separate menu positions for DIP and TQFP
> packages :-)
>
Use commercial tools and it's already here. A
2011/6/18, Royce Pereira :
> So the menu item for 32A is just for psychological purposes !
The next step will be adding separate menu positions for DIP and TQFP
packages :-)
--
wbr,
ReAl
___
AVR-GCC-list mailing list
AVR-GCC-list@nongnu.org
https://l
Hi, all,
Indeed there is no (code wise) difference between 32, 32L & 32A (also
applies to other MPUs like Mega8 etc).
I recently tried a commercial compiler, where selection for 32, 32L, &
32A was given separately, and posed the same query to them.
The answer was
" All three are the same for the
Well. Why AVR Studio 5.0 include ATmega32A for AVR Assembler and also other
compiler include ATmega32A for example CodeVisionAVR.
But AVR-GCC and AVR Burn-O-Mat softwares don't include ATmega32A.
I just wondered while in others include but AVR-GCC and AVR Burn-O-Mat don't.
Thanks for the rep
