First of all I have to highlight an error in my previous mail:
I could *NOT* get the transmission from the PC to the feedback demo to work!
Sorry, but reading and pressing the send button seems to been done by different
persons inside me :-).
Joel Sherrill wrote:
>>What I could get to work
Knut Schwichtenberg wrote:
Joel Sherrill wrote:
Is the pin toggling high and low like the serial data going out?
Does the feedback "receiver" need to read 8 bits and reassemble them?
If so, is "changeValue" actually the value of a "pin state"
(e.g. high, low, etc)
So my other traces ar
Joel Sherrill wrote:
> Is the pin toggling high and low like the serial data going out?
> Does the feedback "receiver" need to read 8 bits and reassemble them?
>
> If so, is "changeValue" actually the value of a "pin state"
> (e.g. high, low, etc)
So my other traces are done and here is the full t
Joel Sherrill wrote:
Knut Schwichtenberg wrote:
Joel,
Joel Sherrill wrote:
All the set serial commands I see are like this:
FDBK RECV: --->set serialRx0 0x0<---
FDBK SET: serialRx0 ChangeValue 0x0
They all have 0 and that doesn't seem right. :(
Keep cool ;-). I copied
Knut Schwichtenberg wrote:
Joel,
Joel Sherrill wrote:
All the set serial commands I see are like this:
FDBK RECV: --->set serialRx0 0x0<---
FDBK SET: serialRx0 ChangeValue 0x0
They all have 0 and that doesn't seem right. :(
Keep cool ;-). I copied only the first part of that window i
Knut Schwichtenberg wrote:
Joel Sherrill wrote:
Knut Schwichtenberg wrote:
Also "-d" is not interpreted as expected :-((. The X-Windows catches
the
command-line and removes "-d" as displaynumber. "-D" works if changed.
-d to what program? I thought simulavr.tcl was
Joel Sherrill wrote:
> Knut Schwichtenberg wrote:
>>
Also "-d" is not interpreted as expected :-((. The X-Windows catches
the
command-line and removes "-d" as displaynumber. "-D" works if changed.
>>> -d to what program? I thought simulavr.tcl was handling it ok.
>
Joel,
Joel Sherrill wrote:
> All the set serial commands I see are like this:
>
> FDBK RECV: --->set serialRx0 0x0<---
> FDBK SET: serialRx0 ChangeValue 0x0
>
> They all have 0 and that doesn't seem right. :(
Keep cool ;-). I copied only the first part of that window into the mail. The PC
I'm wr
Knut Schwichtenberg wrote:
Also "-d" is not interpreted as expected :-((. The X-Windows catches the
command-line and removes "-d" as displaynumber. "-D" works if changed.
-d to what program? I thought simulavr.tcl was handling it ok.
Sorry, it was simulavr.tcl. "simulavr.tcl"
Knut Schwichtenberg wrote:
Joel Sherrill wrote:
That's what I get also. But shouldn't I see characters that
are written to the UART in the feedback window?
Well, with the GUI the characters are moved into the related object and if the
feedback window is the character equivalent for the
Joel Sherrill wrote:
> That's what I get also. But shouldn't I see characters that
> are written to the UART in the feedback window?
Well, with the GUI the characters are moved into the related object and if the
feedback window is the character equivalent for the GUI, I would expect one set
of cha
Knut Schwichtenberg wrote:
Joel Sherrill wrote:
Great. Now you are as far as I am. Did the "simfeedback.tcl" show
up in an xterm and print messages which look like it is getting the
events but no data from the UART?
Something like this? :-)
New Connection on Simulation Feedback Serve
Joel Sherrill wrote:
> Great. Now you are as far as I am. Did the "simfeedback.tcl" show
> up in an xterm and print messages which look like it is getting the
> events but no data from the UART?
Something like this? :-)
New Connection on Simulation Feedback Server established!
Socket: sock4 fro
Joel Sherrill wrote:
> Knut Schwichtenberg wrote:
> OK. Makes perfect sense. Eventually I will need to find something
> the real application is not using if I want debug IO. Luckily in this
> case, I think they are using one of the UARTs for debug IO but for
> testing the feedback, I wanted all
Knut Schwichtenberg wrote:
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
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
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
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-m
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 stdi
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.
Also "-d" is not interpreted as expected :-((. The X-Windows c
Michael N. Moran wrote:
Joel Sherrill wrote:
But at this point I don't seem to be able to
get the UART data I am transmitting to show up
in the "simfeedback.tcl" program. It is getting
events but the data is printed as 0.
Yesterday, I was struggling to debug simulavrxx
as realized b
Joel Sherrill wrote:
But at this point I don't seem to be able to
get the UART data I am transmitting to show up
in the "simfeedback.tcl" program. It is getting
events but the data is printed as 0.
Yesterday, I was struggling to debug simulavrxx
as realized by the "examples/spi/check.tcl."
Hi,
My ultimate goal is to be able to test
an application running on simulavr. I
want to pretend to be the devices it is
attached to and exercise the application
as on real hardware. In this light, I have
added "examples/feedback".
The goal will be to demonstrate that you
can programmaticall
23 matches
Mail list logo
