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

Radio Transmitter Example

1. How should I connect with UART to my board?

2. How to put the device into RX mode as required by RED EN300328?

Test the Radio Test Example application by performing the following steps:

  1. Compile and program the application.
  2. Start a terminal emulator like PuTTY and connect to the used COM port with the following UART settings:
    • Baud rate: 115.200
    • 8 data bits
    • 1 stop bit
    • No parity
    • HW flow control: None
  3. The text "RF Test" should appear at the top of the terminal.
  4. Type any of the letters described above. An output text should be displayed in the PUTTY window, or a sweep or signal should be started.
  5. Use a spectrum analyzer to confirm the behavior of the radio module.
Parents
  • Hi,

     

    1. You need a to use something for the Virtual COM port. A nRF52-DK can be used for this, see this link. You have to cut SB6 on the DK (to not power the nRF52 on the DK itself), then hook up your board to the UART pins described in the link. You can edit the code and configure other pins if that works better with your board.

    2. For simply configuring the radio to operate in receive mode, the radio test example For testing received blocking, see our nAN-34, which describes how to set up a produciton test using our DTM application. This comes with a script for doing a PER test, needed for the blocking tests.

     

    Best regards,

    Andreas

  • that means I am using my PCB connected to the DK board?

    Is there a block diagram of the system?

    My current PCB is already connected to the pins P05-P08.

    How should i connect to my PCB????

    where should i burn the project on the SDK or on my PCB or both?

    DTM cannot work with my PCB as far as i know..

    I think you need to add the comment for this on the radio example.

  • Hi Nir,

     

    Do you have available GPIOs in your design at all? If not you might have to refurbish one of your samples for the purpose, cut some traces and solder on some wires, that should be acceptable for this specific test but if so you should confirm with your cert house. You can then redefine the assigned UART pins in pca10040.h and reflash your board.

     

    The current test implementation is designed against the DTM specification and does not support control over the SWD line. You could implement this yourself though, initiating the transmission e.g. by writing TASKS_ENABLE. If then sending a predetermined payload, the receiver could still do the PER calculation, but in this case the test house probably would not be able to use a BLE tester, you would have to make the receiver using a nRF52 DK yourself. If you decide to go with this you should also confirm with the test house if they accept it.

     

    Best regards,

    Andreas

  • Do you have an example for it?

    how can I change the pins setup?

  • Hi,

     

    No, we do not have an example for how to change UART pins.

    1. Download SDK v.15.0
    2. Open project of DTM example for whatever IDE you have available. SES can be downloaded for free through Segger.
    3. Browse and open 'PCA10056.h', (through 'boards.h' if needed) and change code lines 87-90 to whatever GPIO number you want to use

    #define RX_PIN_NUMBER  8
    #define TX_PIN_NUMBER  6
    #define CTS_PIN_NUMBER 7
    #define RTS_PIN_NUMBER 5

    Build, flash and you are good to go.

     

    Best regards,

    Andreas

  • On this system, I should have

    1. EVB- NRF52- should act like mater to send data

    2. My PCB- which should receive the commands 

    Should I burn the same FW on both?

    Is there a simple document which describes the block diagram and the FW for each part??

    The information is not clear nor setup...

    this test should be done by any customer .. 

  • Hi,

     

    In order to use the python PER script linked below, both boards should be loaded with the DTM application. If you load the DK with the exact same hex file as yo udo with your DUT, remember that the UART pins will also change. The nRF52 on the DK will then not have its UART connected to the pins(lines) that go to the interface MCU, which it needs to get commands to/from the PC.

     

    We do not have any documents or similar on basic UART, but this is freely available at a number of sources, e.g. this by Sparkfun. There has not been a demand for anything this elaborate from us directly, and there is a lot of assistance to be found through previously answered DevZone queries.

     

    An attempt to break it down

    Tester (nRF52 on DK), no change needed. just flash it with the pre-compiled DTM application:

    DK-side nRF52 side
    TXD (P0.08) RXD (P0.08)
    RXD (P0.06) TXD(P0.06)
    CTS (not needed)  
    RTS (not needed)  

     

    DUT (Custom device):

    DK-Side nRF52 side
    TXD (P0.08) RXD (whatever you set it to)
    RXD (P0.06) TXD (whatever you set it to)
    CTS (not needed) Not needed
    RTS (not needed) Not needed

     

    Best regards,

    Andreas

Reply
  • Hi,

     

    In order to use the python PER script linked below, both boards should be loaded with the DTM application. If you load the DK with the exact same hex file as yo udo with your DUT, remember that the UART pins will also change. The nRF52 on the DK will then not have its UART connected to the pins(lines) that go to the interface MCU, which it needs to get commands to/from the PC.

     

    We do not have any documents or similar on basic UART, but this is freely available at a number of sources, e.g. this by Sparkfun. There has not been a demand for anything this elaborate from us directly, and there is a lot of assistance to be found through previously answered DevZone queries.

     

    An attempt to break it down

    Tester (nRF52 on DK), no change needed. just flash it with the pre-compiled DTM application:

    DK-side nRF52 side
    TXD (P0.08) RXD (P0.08)
    RXD (P0.06) TXD(P0.06)
    CTS (not needed)  
    RTS (not needed)  

     

    DUT (Custom device):

    DK-Side nRF52 side
    TXD (P0.08) RXD (whatever you set it to)
    RXD (P0.06) TXD (whatever you set it to)
    CTS (not needed) Not needed
    RTS (not needed) Not needed

     

    Best regards,

    Andreas

Children
No Data
Related