Hi Erich
There is nothing wrong.
Me too I'm reading the echo char while transmitting.
The timeout problem is while receiving form the mcu.
After transmitting a line you stay earing for a response.
How can I know when the response is complete?
Wait a lot of seconds is not so logic.
How can I know
Hi Paolo,
Thank you for your response.
On 08/02/2014 01:39 PM, Paolo Garro wrote:
> Hi Erich
> There is nothing wrong.
> Me too I'm reading the echo char while transmitting.
> The timeout problem is while receiving form the mcu.
> After transmitting a line you stay earing for a response.
> How
xon/xoff are characters send.
With USB this is does not work better than CR or any other character.
Target and PC do not communicate character by character any more.
Terminal emulaters do not stop in time, there are buffers inbetween,
overrunning oldfashion xon/off protokolls.
Michael
Am 02.0
Hi Erich,
You are pretty right...
Wait the " ok" and then the "\n> " prompt is not a valid solution.
In the middle of a ":" definition, the response is a sole " ok" without a
prompt so it is ambiguous in general.
I've also tried to wait for an error message r"\?\? -\d+ \d+ \n> $" to stop the
loop
Hi.
In 4e4th the PROMPT is a forth word, executed right after INTERPRET .
That way it is easy to modify.
I use character ACK ( $06 EMIT ) as signal for the 4e4th-IDE shell.
You may serve other information with the prompt string, like the
current number base, or what ever you need.
mk
; C PROMP
