AT90S2313 | AT90S8515 | ATMega | ATmega128 | ECL | FETS | IAR | Keyboard | LCD | STK50 | TMOS | UART

I have code to read a keypad on Port D and output it to LEDS on Port B.
This works fine on ATmega8515, but I get wrong results with ATmega162 -
it cannot distinguish keypad rows correctly. Are there any differences
between an ATmega8515 and ATmega162 that could cause this?



(You need to be a member of avrclub -- send a blank email to avrclub-subscribe@yahoogroups.com )

--- In a...@yahoogroups.com, "wallisadrian" wrote:
> I have code to read a keypad on Port D and output it to LEDS on
Port
> B. This works fine on ATmega8515, but I get wrong results with
> ATmega162 - it cannot distinguish keypad rows correctly. Are there
> any differences
> between an ATmega8515 and ATmega162 that could cause this?

Be sure to check setting for things like JTAG port. For example, I
believe the '162 by default uses some of the pins on one of the
ports for JTAG. To get those pins back you have to set/reset some
fuse bits to disable JTAG and regain those pins back.

Likewise check to make sure you are properly set up to use the
internal oscillator of a chip vs. using an external crystal/clock to
the chip.

Basically, different ports often have alternative functions you can
use and it might be the port you are using is currently set up for
specific functionality like serial communication, JTAG, clock, SPI,
etc.

Patrick



(You need to be a member of avrclub -- send a blank email to avrclub-subscribe@yahoogroups.com )