nRF52832 Radio

[xiaobai]

 

This one was written by a former colleague of mine, using radio to simulate a BLE broadcast driver.I use in my own project, it is completely possible to realize the radio simulation BLE broadcast data sending and receiving BLE broadcast data through this function.However, I ported these functions to SDK15.2 in the radio case, but found that they did not work, and the radio ported to 17.0 also did not work.At this time, there is a question. The configuration, sending and receiving of radio here are all directly operated registers, so there should be no problem of not being able to use the transplant.Therefore, I would like to ask whether there is something wrong with the related functions of radio in my side, which leads to the failure of using it during transplantation. In other words, the use of radio requires not only these functions, but also other aspects. Please kindly give me your advice.

[Jørgen Holmefjord]

Hi,

You are right that most of the code you have posted writes directly to the registers and should not be affected by the SDK version. However, the clock_init function seems to use the SDK driver, and may be affected.

What exactly is not working after migrating to the later SDK versions? Does it not send/receive packets? Do the application crash? Is there any error codes from the clock drivers?

What was the original SDK version of the project?

Was this written for the same chip variant as you are running it on?

Best regards,
Jørgen

[Jørgen Holmefjord]

If you can upload the full project and source codes, I can try to run and debug it. 

Writing down the code from your screenshots will take too much time.

[xiaobai]

The above is based on the Radio of the official 15.2 SDK. Could you please help me to have a look at the reason why Radio related functions cannot be used in this SDK

[Jørgen Holmefjord]

Still not sure I understand what is failing. I ran your code on two DKs, one nRF52 DK (with nRF52832) and one nRF52840 DK. Both seems to be sending and receiving packets, and printing something to the UART terminal.

If I run both kits at the same time, the logging is much faster, which I assume is because the kits are receiving packets from each other.

[hmolesworth]

The code in main.c assumes a low-frequency 32kHz crystal is fitted to the module/board; is that the case? If not then this will stop any BLE operation, in which case just change to non-crystal mode.

    /* Start low frequency crystal oscillator for app_timer(used by bsp)*/
    NRF_CLOCK->LFCLKSRC = (CLOCK_LFCLKSRC_SRC_Xtal << CLOCK_LFCLKSRC_SRC_Pos);

[xiaobai]

I used this routine mainly because I wanted my label to use RADIO to simulate and receive BLE broadcast packets. However, when I downloaded the HEX file generated by this project into the nRF52832 development board, I found through the tool that the development board did not seem to send out my simulated broadcast packets, and the broadcast packets received were wrong.

[xiaobai]

This is the log of the radio project that can receive and receive normally in my project. I can search the device with the bluetooth address of ff:ff:ff:ff:ff:ff via the NRF Connect tool on my mobile phone.

The above figure is the log of the project I downloaded from git to nRF52832 development board (with printing added). The original intention of this routine is the same as that of my above routine, both of which want to send and receive BLE broadcast through radio simulation.However, I found that this routine not only sent the phone is not scanned, but also received the error.