Knut Schwichtenberg wrote:
Okay, now I see your pain.
BUT, attached I have a checkdebug.tcl and that shows what it should! So forget
the AVR-sources so the problem is in the TCL world!
OMG! I have made an incredibly stupid mistake completely unrelated
to this and now it bites me!
The C++ c
Okay, now I see your pain.
BUT, attached I have a checkdebug.tcl and that shows what it should! So forget
the AVR-sources so the problem is in the TCL world!
Today it's to late to proceed, tomorrow there is another day!
Knut
Joel Sherrill schrieb:
> Knut Schwichtenberg wrote:
>> Joel Sherrill s
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.
Oka
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 r
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.
The SerialRX PinChanged notification routine is showing transitions.
The st
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.
Joel Sherrill schrieb:
> This is deep in the bowels and I don't know what else
> to check. The code in CVS demonstrates the problem
> but do
henne...@cableone.net wrote:
On Wed Apr 8 10:23 , Joel Sherrill sent:
henne...@cableone.net wrote:
On Tue Apr 7 18:35 , Joel Sherrill sent:
henne...@cableone.net wrote:
From the description, the pins are not connected.
Is the connection done with a Netlis
On Wed Apr 8 10:23 , Joel Sherrill sent:
>henne...@cableone.net wrote:
>> On Tue Apr 7 18:35 , Joel Sherrill sent:
>>
>>
>>> henne...@cableone.net wrote:
From the description, the pins are not connected.
Is the connection done with a Netlist?
If so, perhaps its methods des
henne...@cableone.net wrote:
On Tue Apr 7 18:35 , Joel Sherrill sent:
henne...@cableone.net wrote:
On Tue Apr 7 16:23 , Joel Sherrill sent:
By inserting debug prints, I have confirmed that
the hwuart is shifting the correct data out the
TXD pin. The TXD pin is connected
On Tue Apr 7 16:23 , Joel Sherrill sent:
>By inserting debug prints, I have confirmed that
>the hwuart is shifting the correct data out the
>TXD pin. The TXD pin is connected to the RX pin
>of a SerialRX instance. All data sampled at the
>RX pin is 0 (BAD). Thus all data in the feedback.tcl
>d
Hi,
I am at wits end. I am on the CVS head with the
feedback example.
By inserting debug prints, I have confirmed that
the hwuart is shifting the correct data out the
TXD pin. The TXD pin is connected to the RX pin
of a SerialRX instance. All data sampled at the
RX pin is 0 (BAD). Thus all da
11 matches
Mail list logo
