Knut Schwichtenberg wrote:
Joel Sherrill schrieb:
Knut Schwichtenberg wrote:
Joel,
back to the roots: If I got you right your problem is that under all
circumstances your receiver get always "0". And now you are looking
for reasons.
That's the root of the problem.
Okay, I'm not sure if I get you right:
I use the CVS loaded on 27-Mar:
make dogdb
../simulavr.tcl -d atmega128 -f feedback -s ./feedback.tcl -W
0x21,/dev/stderr
-R 0x22,- -F 4000000 -T exit -S ./simfeedback.tcl -g
No connect to socket possible now... retry Connection refused
No connect to socket possible now... retry Connection refused
User Interface Connection opened by host 127.0.0.1 port 7777
Waiting on port 1212 for gdb client to connect...
Connection opened by host 0.0.0.0, port -28871.
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--
...
What I do not understand is the duplicate of characters except if one
character
is routed to the special pin and one is the real received character.
No. That's just debug IO using the -R/-W port. Look at
main.c, it is mirroring a string to both ports and
uart_putchar is actually also doing a debug print to the
-R/-W magic port.
You are seeing debug IO and thinking it is really going
out the UART.
In the "simfeedback.tcl" window I see
....
FDBK RECV: --->set rxD0 L<---
FDBK SET: rxD0 ChangeValue L
FDBK RECV: --->set serialRx0 0x0<---
FDBK SET: serialRx0 ChangeValue 0x0
SerialRx: 0x0
FDBK RECV: --->set rxD0 H<---
FDBK SET: rxD0 ChangeValue H
FDBK RECV: --->set rxD0 L<---
FDBK SET: rxD0 ChangeValue L
FDBK RECV: --->set serialRx0 0x0<---
FDBK SET: serialRx0 ChangeValue 0x0
SerialRx: 0x0
.....
Do you talk about the "SerialRx: 0x0"?
Yes. That is the byte assembled by SerialRX and
handed off via a call to CharReceived() is always 0.
Clearly the RXD0 pin feeding into SerialRX.
Given the debug I posted earlier, I don't see how the pin
changes multiple times without Step ever seeing it.
The SerialRX PinChanged notification routine is showing transitions.
The state change bit sampling logic in Step is just always seeing 0.
Knut
Thanks. Maybe now we are on track.
--joel