RE: Unexpected Address matching

mark — Tue, 19 Jan 2016 09:32:12 GMT

I seem to be getting correlation on addresses

The radio transmit example code has been modified to transmit 10,000 times with a 5 ms delay inbetween each transmission. The PCA100036 board with the receive program address set up to a different base0 address, it still picks up unexpected packets.

This happens with prefix0 set 0xc3438303

receive NRF_RADIO->BASE0 = 0x3109429E transmit NRF_RADIO->BASE0 = 0x31084258

from what I see, these addresses should be conforming to the recommend rules on address requirements.

again with

receive NRF_RADIO->BASE0 = 0x23094254 transmit NRF_RADIO->BASE0 = 0x23084292

I have checked the radio PCNF1 register, the BALEN is set to 4 and the ENDIAN set to 1(big)

main.c transmitter main.c

main.c receiver main.c

RE: Unexpected Address matching

David Edwin — Mon, 18 Jan 2016 10:14:41 GMT

I typically use these set of rules are from the Bluetooth specification (see Bluetooth Core Specifications 4.2 Vol 6, Part B, section 2.1.2 - Access Address ) the as these are general radio rules as well:

The Access Address should meet the following requirements:

It shall have no more than six consecutive zeros or ones.
It shall not be a sequence that differs from the advertising channel packets Access Address (0x8E89BED6) by only one bit. : In addition do not choose the access addresses (if you are using many) so that they differ only by 1 bit.
It shall not have all four octets equal.
It shall have no more than 24 transitions.
Should not start with 0xAA or 0x55 (so it does not match the preamble)
It shall have a minimum of two transitions in the most significant six bits

Transition is a 1 to 0 or 0 to 1 in the bit pattern.