Hello Daniel,
thanks for your answer!
On 24/06/17 21:05, Daniel Drotos wrote:
On Sat, 24 Jun 2017, tg9...@gmx-topmail.de wrote:
This means that a program outside of uCsim needs to monitor the reply
from the µC code before the next line of input can be sent
(handshake, half-duplex operation)
On Sat, 24 Jun 2017, tg9...@gmx-topmail.de wrote:
This means that a program outside of uCsim needs to monitor the reply
from the µC code before the next line of input can be sent (handshake,
half-duplex operation).
Well, I don't have solution for this scenario. What about expect? I've
never
OK, I found the reason for the "strange" behaviour described below,
which is maybe the key to a solution on my side:
`netcat` depends on TTY line processing, which means that newline gets
consumed instead of being passed on to the UART simulation through the
socket. A work around is inserting
Hi Daniel,
thanks for the answer!
However, the STM8 code I intend to test implements an interactive
console. An important detail is that , and I've got the following
problems with the proposed solution:
* The processing of serial input data by the simulator code takes time.
This means that
On Fri, 23 Jun 2017, tg9...@gmx-topmail.de wrote:
I'd like to use the uC simulation uCsim for test automation, and my use-case
requires the uCsim serial port simulation to exchange information through a
script.
You can find some examples for this usage in ucsim source code, see
example, s51.
Hi all,
I'd like to use the uC simulation uCsim for test automation, and my
use-case requires the uCsim serial port simulation to exchange
information through a script.
Entering commands through `netcat` works fine for the emulator console,
it fails for the simulated serial interface (which
