avr-gcc-list
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [avr-gcc-list] ATmega128 problems


From: Hermann Kraus
Subject: Re: [avr-gcc-list] ATmega128 problems
Date: Fri, 08 Aug 2003 13:36:24 +0200
User-agent: Opera7.11/Linux M2 build 406


address@hidden CarryCoder2]$ simulavr --device=atmega128 -g
Simulating a atmega128 device.
MESSAGE: file ../../src/decoder.c: line 3352: generating opcode lookup_table
Waiting on port 1212 for gdb client to connect...
Connection opened by host 0.0.0.0, port 34172.
WARNING: file ../../src/memory.c: line 168: **** Attempt to write invalid
addr: 0x005b
WARNING: file ../../src/memory.c: line 148: **** Attempt to read invalid
addr: 0x1100
WARNING: file ../../src/memory.c: line 148: **** Attempt to read invalid
addr: 0x1101
[...]
I commented out all of the code in my main function except one. I need some help to understand what is going on because this is the first time I have used GDB or simulavr. I am guessing that I created a breakpoint when entering main and the errors occured during the boot-loader for the ATmega128. Is
this the proper assumption and if so, does anyone know a solution?
These warnings are not a problem of your program, these registers are not implemented in simulavr, yet. During boottime these registers are accessed from the To avoid confusion I've changed the line to: avr_warning( "**** FIXME: Attempt to read a register of an unimplement VDevice (addr: 0x%04x)\n", addr );

You shouldn't use version 0.1.1 anyways. It's quite old. Download the most recent version from cvs. If made a patch to support the changed of the positions bits in ATMega128 (compared to 90s8515). It also improves the timers, but the version in the mailinglist-archive has some bugs. I'll post a new patch to the simulavr-devel-list next week.

Hermann


reply via email to

[Prev in Thread] Current Thread [Next in Thread]