[<<][staapl][>>][..]
Sat Nov 5 13:52:51 EDT 2011

Reliable ping

When target is sending stuff, i.e. in a print loop, it will look as if
it is responding to pings.  This means the pings are too simple.

It still gets stuck sometimes:


foo
01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F 10 11 12 13 14 15 16 17   C-c C-c
Command "foo" interrupted.
Trying cold restart...
target-off
target-on
recv-header: malformed header: (0)

but I this seems to be due to a stack underflow on the device, using:

  : foo 1 + dup dump foo ;

with a correct def it doesn't behave like that:

  : foo 0 begin 1 + dup dump again ;

I do get this error still:

bad-reply-id: 0 ()

That latter one seems to be recoverable by another retry.

This one however seems to indicate that pk2 is stuck:

icsp-recv: pk2 read: expected 3 bytes, got 1:
icsp-recv: b:2 h:#t a:#f -> (0)

even the stat command doesn't give good results:

stat
(status
 (0 "Vdd GND")
 (1 "Vdd")
 (0 "Vpp GND")
 (0 "Vpp")
 (0 "VddError (Vdd < Vfault)")
 (0 "VppError (Vpp < Vfault)")
 (0 "Button Pressed")
 (0 "Reset since READ_STATUS")
 (0 "UART Mode")
 (0 "ICD transfer timeout/Bus Error")
 (0 "Script abort - upload full")
 (0 "Script abort - download empty")
 (0 "RUN_SCRIPT on empty script")
 (0 "Script buffer overflow")
 (0 "Download buffer overflow"))
(voltages (0.000152587890625 "Vdd") (3.425 "Vpp"))
subbytes: ending index 65 out of range [1, 64] for byte-string: #"@\254\0@\4\0 \376\200\3\1\0\304\37\200 \0\0\361\a$\b\0@\374\1\n\2\0\210?`A\0\0\361\a0\b\0@\374\1\r\2\0\20\177\200\203\0\0\3...

Maybe it would be good to find out how to reliably reset the pk2?




[Reply][About]
[<<][staapl][>>][..]