Skip to content

Packets with Failed CRCs are being Acked #11

@bradjc

Description

@bradjc

Correct me if I'm wrong, but after a quick perusal of the driver I can't find anywhere where it checks if the CRC was correct. This means that packets are being acked that fail the CRC. This causes problems in higher layers.

In cc2420x, a failed crc packet never makes it out of DriverLayerP and therefore can't be acked in SoftwareAckLayer.

I ran into this when the first packet in a series of blip fragments wasn't received successfully, but the second one was causing BLIP to try to write to an unallocated buffer.

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