Bitcounter raising BCMATCH event for short packets

[Yuval0]

Hi,

I'm trying to use the bitcounter to drop packets that don't comply to a specific UUID. I'm working with nrf52840.

My question is - if the received packet is shorter than the configured BCC value, will the bcmatch event not be asserted?

For example, if i configure NRF_RADIO->BCC = 96, and a packet arrives with 9 bytes after the access adress (72 bits), will the bcmatch event not be triggered at all?

Thanks!

Yuval

[Håkon Alseth]

Hi,

 

My question is - if the received packet is shorter than the configured BCC value, will the bcmatch event not be asserted?

For example, if i configure NRF_RADIO->BCC = 96, and a packet arrives with 9 bytes after the access adress (72 bits), will the bcmatch event not be triggered at all?

This highly depend on when you start the bitcounter, but it must be started after the EVENTS_ADDRESS has occurred.

If you start it on EVENTS_ADDRESS, it will start from the address match and going forward for the amount of configured bits.

For more detailed information related to the bit counter, see here:

https://docs.nordicsemi.com/bundle/ps_nrf52840/page/radio.html#ariaid-title12

 

For example, if i configure NRF_RADIO->BCC = 96, and a packet arrives with 9 bytes after the access adress (72 bits), will the bcmatch event not be triggered at all?

At this time, the demodulator will continue to demodulate data, but you can get a corrupt/invalid payload at the end.

If you get a address match, and a device address match, you will receive more data; as the validity of the payload is depending on the CRC.

 

Kind regards,

Håkon