[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Simulavr-devel] Help with New Example
From: |
Knut Schwichtenberg |
Subject: |
Re: [Simulavr-devel] Help with New Example |
Date: |
Sun, 29 Mar 2009 14:33:32 +0200 |
User-agent: |
Thunderbird 2.0.0.19 (X11/20081227) |
Joel Sherrill wrote:
> Knut Schwichtenberg wrote:
>> Joel Sherrill wrote:
>>
>>> Knut Schwichtenberg wrote:
>>>
>>>> Joel,
>>>>
>>>> I tried your example and currently I don't understand your example. And
>>>> therefore please explain the details.
>>>> Using 0x20 / 0x21 means PINF and PINE as IO - you can't use these
>>>> addresses on a
>>>> M128 without a look to the HW-manual.
>>>>
>>>>
>>> I was trying to copy the stdiodemo to get the UART connected
>>> to the UI port. But still use a "magic" port to write debug output.
>>> I guess I need to switch the magic port to a reserved address.
>>> The real app (see below) uses two serial ports.
>>>
>>> My AVR ignorance is showing. Sorry.
>>>
>> :-)
>>
Okay, here I can only say: You loose a little. :-( The M128 uses all register in
the IO-space from 0x20 to 0x5f. As far as I understand for these magic ports you
need spare addresses (unused to be more precise) or you are "removing an IO
component from the silicon". Currently I decided to remove PORT "E" which are
the addresses 0x21, 0x22 and 0x23 using 0x21 instead of 0x20 prints the
following out on the shell:
make dogdb
avr-gcc -g -O2 -mmcu=atmega128 -DF_CPU=4000000 -c -o debugio.o debugio.c
avr-gcc -g -O2 -mmcu=atmega128 -DF_CPU=4000000 -o feedback main.o debugio.o
uart.o
../simulavr.tcl -d atmega128 -f feedback -s ./feedback.tcl -W 0x21,/dev/stderr
-R 0x22,- -F 4000000 -T exit -S ./simfeedback.tcl -g
User Interface Connection opened by host 127.0.0.1 port 7777
Waiting on port 1212 for gdb client to connect...
Initialize debug io
-uart init--h-h-e-e-l-l-l-l-o-o- - -w-w-o-o-r-r-l-l-d-d-J--O--E--L--
-Connection opened by host 0.0.0.0, port -20541.
As a hint I would suggest to use a common define for the -R and the related C
statement, otherwise ... - I think you know too well.
But I'm confused about the debugger behavior. I'll check in the oldish
checkdebug - style especially find a gdb-GUI :-)
- [Simulavr-devel] Help with New Example, Joel Sherrill, 2009/03/27
- Re: [Simulavr-devel] Help with New Example, Michael N. Moran, 2009/03/27
- Re: [Simulavr-devel] Help with New Example, Knut Schwichtenberg, 2009/03/28
- Re: [Simulavr-devel] Help with New Example, Joel Sherrill, 2009/03/28
- Re: [Simulavr-devel] Help with New Example, Knut Schwichtenberg, 2009/03/28
- Re: [Simulavr-devel] Help with New Example, Joel Sherrill, 2009/03/28
- Re: [Simulavr-devel] Help with New Example,
Knut Schwichtenberg <=
- Re: [Simulavr-devel] Help with New Example, Joel Sherrill, 2009/03/29
- Re: [Simulavr-devel] Help with New Example, Knut Schwichtenberg, 2009/03/29
- Re: [Simulavr-devel] Help with New Example, Knut Schwichtenberg, 2009/03/29
- Re: [Simulavr-devel] Help with New Example, Joel Sherrill, 2009/03/29
- Re: [Simulavr-devel] Help with New Example, Knut Schwichtenberg, 2009/03/29
- Re: [Simulavr-devel] Help with New Example, Joel Sherrill, 2009/03/30
- Re: [Simulavr-devel] Help with New Example, Knut Schwichtenberg, 2009/03/30
- Re: [Simulavr-devel] Help with New Example, Joel Sherrill, 2009/03/30
- Re: [Simulavr-devel] Help with New Example, Joel Sherrill, 2009/03/30
- Re: [Simulavr-devel] Help with New Example, Knut Schwichtenberg, 2009/03/30