Skip to content

Interpreting CC3000 test results #1

@lukeweston

Description

@lukeweston

Thanks for the code :)

I'm currently using your test to help debug a problematic custom-made CC3000 board.

I'm consistently getting first packet success and second packet failure.

The second (bad) packet is consistently all high up until the last byte, and this last byte tends to be variable when the test is repeated multiple times.

Do you have any ideas about interpreting this, or what it might mean for locating the fault?

Testing first packet:
Expected: 2 0 FF 0 0 0 0 0 0 0
Received: 2 0 FF 0 0 0 0 0 0 0

Testing second packet:
Expected: 2 0 0 0 5 4 0 40 1 0
Received: FF FF FF FF FF FF FF FF FF E0
PROBLEMS WITH THE SECOND PACKET!

Testing first packet:
Expected: 2 0 FF 0 0 0 0 0 0 0
Received: 2 0 FF 0 0 0 0 0 0 0

Testing second packet:
Expected: 2 0 0 0 5 4 0 40 1 0
Received: FF FF FF FF FF FF FF FF FF FC
PROBLEMS WITH THE SECOND PACKET!

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions