| Author |
Message |
|
|
 Posted: Feb 14, 2012 - 04:14 PM |
|
Joined: Feb 14, 2012
Posts: 2
|
|
Hi,
I have an Atmega128 operating in Atmega103 compatibility mode. It is running Assembly code, i would like to step through it and and set some breakpoints. Is it possible to do this with a JTAG interface and how is this done?
Thx in advance!
Robbin |
|
|
| |
|
|
|
|
|
|
Posted: Feb 14, 2012 - 04:29 PM |
|
Joined: Jul 18, 2005
Posts: 62299
Location: (using avr-gcc in) Finchingfield, Essex, England
|
|
In the 128 datasheet look at the section "ATmega103 compatibility mode" (my copy has this on page 5). In that it says:
Quote:
Port F serves as digital input only in addition to analog input to the ADC.
I read that to mean that the JTAG (which is on PORTF) is not available in 103 mode. |
_________________
|
| |
|
|
|
|
|
|
Posted: Feb 15, 2012 - 09:08 AM |
|
Joined: Feb 14, 2012
Posts: 2
|
|
Is there an other way to debug an Atmega128 operation in 103 mode (running Assembly)?
I really would like to set some breakpoints. |
|
|
| |
|
|
|
|
|
|
Posted: Feb 15, 2012 - 09:10 AM |
|
Joined: Nov 02, 2009
Posts: 3239
Location: Zelenograd, Russia
|
|
| Why on Earth would one use the M103 compatibility mode in 21st century? |
_________________
Warning: Grumpy Old Chuff. Reading this post may severely damage your mental health.
|
| |
|
|
|
|
|
|
Posted: Feb 15, 2012 - 09:30 AM |
|
Joined: May 18, 2004
Posts: 49
|
|
|
|
|
|
|
|
Posted: Feb 15, 2012 - 09:37 AM |
|
Joined: May 18, 2004
Posts: 49
|
|
On that note:
in the case of a project completely written in assembler on an Atmega103, which was then run on an Atmega128 because the 103 was made obsolete, and one would want to not use the Atmega103C fuse, what would need to be changed to the assembler code?
Or is it software compatible and would one just need to rebuild with a different device? |
|
|
| |
|
|
|
|
|
FAQ
Search
Register
Log in to check your private messages
Log in
Maximize
RSS
