AtMega128-16AU vs ATMEGA128A-AU

Is there a discrepancy in the compiler using this microcontroller?

JAG
Benutzer
Avatar
Gender:
Location: Mexico
Age: 59
Posts: 18
Registered: 07 / 2008
Subject:

AtMega128-16AU vs ATMEGA128A-AU

 ·  Posted: 05.05.2023 - 07:18  ·  #1
For years, our system has run on a custom PCB based on the ATmega128-16AU. The distributor was out of this component, so we purchased the AtMega128A-AU that was said to be a drop-in replacement. The newly assembled microcontrollers on our PCB runs the display routines but doesn't read the keyboard and has problems with the watchdog routine doing repetitive resets on the first board we tested today. Has anyone experienced the same discrepancy as us with these two microcontrollers?
pvs-deck
PowerUser
Avatar
Gender:
Age: 53
Homepage: pvs-deck.de
Posts: 1340
Registered: 02 / 2009
Subject:

Re: AtMega128-16AU vs ATMEGA128A-AU

 ·  Posted: 05.05.2023 - 09:13  ·  #2
Hallo Jag,

leider benutze ich diese CPU nicht.

Aber kurz einige Fragen, was ist das für eine Tastatur?
Wie ist diese angeschlossen?
Welche Schnittstelle I2C, SPI oder wie auch immer.

Evtl. Kommt Dein Watchdog Problem von einen Hänger mit dem Keyboard.
Aber Du gibst hier etwas wenig infos zum helfen.

Gruß
Thorsten

------------------------
Hello Jag,

sorry i don't use this CPU.

But briefly some questions, what is this keyboard?
How is it connected?
Which interface I2C, SPI or whatever.

Maybe your watchdog problem comes from a hange with the keyboard.
But you give here a little bit less infos to help.

Greetings
Thorsten
Merlin
Administrator
Avatar
Gender:
Age: 24
Posts: 1373
Registered: 03 / 2005
Subject:

Re: AtMega128-16AU vs ATMEGA128A-AU

 ·  Posted: 06.05.2023 - 16:18  ·  #3
Also are you recompiling for the new part or simply programming with the old hex file and ignoring the signature error?
JAG
Benutzer
Avatar
Gender:
Location: Mexico
Age: 59
Posts: 18
Registered: 07 / 2008
Subject:

Re: AtMega128-16AU vs ATMEGA128A-AU

 ·  Posted: 12.05.2023 - 19:20  ·  #4
I'm using the same hex files for AtMega128-16AU and AtMega128A.

The keyboard that we are currently using is a 4x4 membrane type, and we are reading it through the AVR-co libraries. However, during our testing phase, we observed that all the ports used ( PB0 to PB3 configured as output, and PB4 to PB7 set as input) are unresponsive when the 128A is installed. We have verified this by using a digital probe to check the port and we have found that there are no signals being detected.

I'll try Merlin following your suggestion and see what happens with the new hex file and keep you posted about the findings.

Your feedback is greatly appreciated.
JAG
Benutzer
Avatar
Gender:
Location: Mexico
Age: 59
Posts: 18
Registered: 07 / 2008
Subject:

Re: AtMega128-16AU vs ATMEGA128A-AU

 ·  Posted: 13.05.2023 - 00:45  ·  #5
Today, we switched to AtMega128-16AU and reinstalled the original hex file. As a result, the issue with the keyboard malfunctioning and the occurrence of watchdog resets has been resolved. Based on the results, it is possible that the two Atmega devices may not be fully compatible. We have recorded this observation here to assist others who may encounter similar difficulties. Thank you for your attention to this matter.
Selected quotes for multi-quoting:   0

Registered users in this topic

Currently no registered users in this section

The statistic shows who was online during the last 5 minutes. Updated every 90 seconds.
MySQL Queries: 15 · Cache Hits: 14   95   109 · Page-Gen-Time: 0.020987s · Memory Usage: 2 MB · GZIP: on · Viewport: SMXL-HiDPI