On Sat, Jun 16, 2018 at 2:40 PM Linus Torvalds
<torva...@linux-foundation.org> wrote:
>
> In the meantime, "just retry" is the way to get it to work.
> Eventually it will - at least as long as you're not trying to download
> too much, and at least as long as the environment isn't too noisy for
> BLE.
I can also make the EON Core crash when there are enough BLE packet
errors. It's probably because we do not re-try - we just fail that
command and then go to the next one. Which will also usually fail,
because we've now confused the EON Core.
So I've gotten "SYSTEM FAILURE" "ERR - c1500000" three times today
while trying to debug this. That resets the time and date on the dive
computer, btw, but Suunto tells me that it doesn't affect the actual
deco calculations even if it happens between dives. I got similar
things when I did things wrong over USB, so I'm not entirely
surprised, but it does make for more exciting debugging.
I'll try to figure out what the proper re-try sequence is. I've
already fixed some of my wrong assumptions of the protocol, but they
don't really matter (the "connection ID" magic value isn't actually 4
bytes, it's a 2-byte magic value and there are two bytes of flags. I
think that's where I need to fill in retransmit information is, but
I'm flying mostly blind.
Linus
_______________________________________________
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
