Closed ivpri closed 6 years ago
I never tried using e4thcom through a uCsim telnet connection - the idea is good but the uCsim telnet interface is far from easy to deal with, and the author of uCsim didn't fully support the interactive scripting use case. When I worked on simload.sh
I already had to work around a range of problems, and I guess that race conditions can be one of them. e4thcom might also contribute to problems since, as far as I know, recent versions have only been tested with serial interfaces.The only way i could make scripting work was with the Python Telnet client library. Maybe Python code can be used as a glue between uCsim and e4thcom?
On a second thought, did you try using the uCsim version in tg9541/sdcc-docker? I had difficulties using a newer version than uCsim 0.6-pre32,
as my scripting use case was again broken. Besides, the uCsim author was very helpful by adding crucial features for running STM8 eForth, and that's not a small feat.
Hi, stm8ef in sstm8 simulator works perfectly for me using telnet connection, However, I need also #include feature there so I've tried simload.sh but it fails:
So, next try was with simulated serial port using socat:
Redirect telnet to pty:
However, the same issue here with both using e4thcom or e.g. echo words > /dev/virtualcom0 In all these cases each second character is dropped, when I type wwoorrddss, the word is accepted:
Any Idea what's wrong?