Bug #402

Something wrong with bytestuffing

Added by Espen Solbu over 5 years ago. Updated over 5 years ago.

Status:ClosedStart date:04/20/2012
Priority:ImmediateDue date:
Assignee:Android Dashboard Developers% Done:

100%

Category:ParserSpent time:-
Target version:2.0 Multiple models

Description

"End byte" of frames (7E) also gets "decoded" to 7D 5E
This should not happen

Tested without hub
with ad1 connected to sensor

Associated revisions

Revision 340
Added by Espen Solbu over 5 years ago

closes #402 added truncating of decoded frame. Added option to print out hex representaton of frame without additional decoding

History

#1 Updated by Espen Solbu over 5 years ago

This does not consistenly reproduce.

When it happened, most frames would end up as corrupt. The frame looked like this:

7e fe 7d 5e a2 58 ac 00 00 00 00 7d 5e 00

I do not know if it got decoded. length seems strange

#2 Updated by Espen Solbu over 5 years ago

Happended again this is the frame pattern that it reacts too:

Before:        7e fe 7d 5d a1 62 c8 00 00 00 00 7e
After:        7e fe 7d a1 62 c8 00 00 00 00 7e 00

So, decoding does not change the size of the frame. This will trigger a corrupt frame..

#3 Updated by Espen Solbu over 5 years ago

  • Status changed from New to Closed
  • % Done changed from 0 to 100

Applied in changeset r340.

Also available in: Atom PDF