This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Odd behavior in tx radio and rx radio pairs

I am doing some custom work, and have discovered an odd bug, that I can not seem to figure out.

On the tx radio, I am transmitting a BLE ADV packet with the first 3 bytes 0x4225BB. On the receiving radio, I am receiving 0x422503. The receive radio's checksum is correct (per the crc register). The rest of the packet is correct.

I also tried to transmit a BLE ADV packet with first 3 bytes 0xAAAA0E. The receiving radio picked up 0xAA2A02 and again, the checksum is correct (per the crc register). The rest of the packet is correct, it only seems to effect the 2 bytes.

I have verified the memory of each the tx-er and rx-er at receive and transmit time, and it reinforces the above statements.

I am using a NRF52832 to transmit, and and NRF51822 to receive. I am using custom code, not the Nordic stack. I have tried this on multiple devices and the behavior is the same.

Is there something that I am missing?

Parents
  • Hi

    Have you tried to use a phone to receive the adv packet, to see if the issue is the same (or if the packet can even be received) ?

    If you have an Android phone the nRF Connect app from Nordic allows you to see the raw data from an advertiser.

    Are you able to share the code you used to transmit the adv packet?
    Then I can take a look and see if there is something there that could explain the issue.

    Best regards

Reply
  • Hi

    Have you tried to use a phone to receive the adv packet, to see if the issue is the same (or if the packet can even be received) ?

    If you have an Android phone the nRF Connect app from Nordic allows you to see the raw data from an advertiser.

    Are you able to share the code you used to transmit the adv packet?
    Then I can take a look and see if there is something there that could explain the issue.

    Best regards

Children
No Data
Related