nRF52 series Continuous Carrier Issue

We have product under final development which uses an nRF51822 as a peripheral to a RP2040.  Product has worked well for many months using Nordic proprietary radio TX/RX.  On the nRF51 series there is TEST a radio register 0x540 which allows the nRF&51 to be placed into a constant carrier more to allow compliance testing.  This seems to have been left out of the radio registers on the nRF52811 and presumably it is not activated.

There are reference drivers for the nRF52 series that purport to be able to activate a constant carrier on the nRF52 series. In viewing the driver in some detail I cannot get any understanding of how the nRF52811 is put into a constant carrier mode

We have our own nRF52 series driver running well under MicroPython. We wish to add a function that allows for a continuous carrier.  Is there a document or an application note that specifically defines how the registers of the nRF52811 should be managed to place the chip into a constant carrier mode

Our existing pcb modules have the nRF52811 as a peripheral  to. RP2040.  The nRF52811 is programmed via the SWDIO/SWCLK and data is exchanged between the nRF52811 and the RP2040 via an SPI interface.  The radio on the nRF52811 works well and testing show that at least 8 adjacent 1 MHz channels operate continuously with a very low error rate.  The modules have an on- board antenna etched into the pcb

We now need to perform pre compliance and compliance tests but cannot do so until we can set up a continuous carrier.  We can control the channel number and transmit power with the existing driver

Any assistance with identifying what registers are involved in setting up a constant carrier would be appreciated

  • Hi Hieu

    We may disagree with the interpretation of clauses in the ETSI 300 328 specifications as we are relying on clause 4.2.1 which states

    “Software fitted to production models shall be substantially the same as that used during type testing.”

    From our prospective the Zephyr app which we now have compiled for the nRF52811 works well but needs to be separately loaded onto our modules and run separately. Ie it is distinctly different code.

    The good news for us is that the software gurus have now been able to interpret what registers in the nRF52811 need set to emulate most of the test functions in the Nordic Zephyr app.  We now have an integrated MicroPython driver that allows us to write normal MicroPython apps/ scripts plus write scripts that can modulate the nRF52811 for compliance test purposes.  There is a little more testing to go but we will probably release this with the next firmware update

    Many thanks again for your support

    Kind Regards

    Julian Dinsdale

  • Hi Julian,

    Could it be that we are looking at different documents? Here is the one I was referring to:

    If possible, please give me a link to the docs you are using.

    Best regards,

    Hieu

Related