Using Serialization on a nRF52832

RE: Using Serialization on a nRF52832

Declan Traill — Mon, 23 Apr 2018 05:43:09 GMT

Hi Jørgen,

Ok, thanks - I have SPI communications happening & am getting Advertising Report Events being sent from the Nordic to the NXP. The problem was that the REQ & RDY line state changes were not generating interrupts properly.

Regards,

Declan

RE: Using Serialization on a nRF52832

Jørgen Holmefjord — Fri, 20 Apr 2018 11:06:28 GMT

Which function call is returning NRF_ERROR_NO_MEM? Both SPI RDY and SPI REQ lines should be active low, and use pullups. In the serialization application examples in the SDK, the connectivity chip is reset after transport is initialized. I would recommend that you do something similar, to ensure the connectivity board is in the correct state when you send commands.

RE: Using Serialization on a nRF52832

Declan Traill — Mon, 16 Apr 2018 05:43:28 GMT

Hi Jørgen,

I have some serialization communications happening between my two CPUs (Nordic and NXP) via SPI,
but it seems to be different depending which CPU starts up first, and the comms seems to grind to a halt quite promptly and then
no message can be sent (get repeated NRF_ERROR_NO_MEM errors).

If I start up the Nordic CPU first, then a large amount of data (65535 bytes) gets streamed from the Nordic CPU coon after it starts up.
I get state sequence SER_PHY_STATE_TX_ZERO_HEADER, SER_PHY_STATE_RX_HEADER, SER_PHY_STATE_MEMORY_REQUEST, then lots of SER_PHY_STATE_RX_PAYLOAD packets.

If I start up the NXP CPU first, I get SER_PHY_EVT_GPIO_REQ (while in SER_PHY_STATE_MEMORY_REQUEST state), then nothing.
If I then try to send a command, such as sd_ble_gap_scan_start, I get HAL_TRANSP_TX_STATE_TX_ALLOCATED, HAL_TRANSP_TX_STATE_TRANSMITTING, SER_PHY_EVT_TX_API_CALL, then nothing (and nothing seems to happen at the Nordic end).

What is the startup sequence supposed to look like?
Which CPU should start up first, and what messages are exchanged at the start?
Is there any required sequence of commands that should be sent after startup?

Further to these questions, could you confirm that: the SPI RDY Line is Active High and should have an internall Pull-Down, and the SPI REQ Line is Active Low and should have an internal Pull-Up?

Are there any SPI requirements for pre_delay, post_delay, frame_delay or transfer_delay that should be set on the NXP side?

Regards,

Declan

RE: Using Serialization on a nRF52832

Jørgen Holmefjord — Fri, 13 Apr 2018 10:22:34 GMT

Good to hear that you found a solution!

RE: Using Serialization on a nRF52832

Declan Traill — Fri, 13 Apr 2018 04:19:03 GMT

Found the problem - I had disabled the call to event_handler() during board bring-up so that the code on the Nordic would continue running without the SPI link to the other CPU being present.

RE: Using Serialization on a nRF52832

Declan Traill — Thu, 12 Apr 2018 06:34:00 GMT

Hi,

I have a protoype board with a Nordic nRF52 chip connected to another CPU via SPI.

I am sending SPI data from the other CPU (configured as SPI Master), and can see the clock and data arriving at the GPIO pins of the Nordic chip, but even though the pins are configured as SPI MOSI and MISO pins, I am not getting any activity in the Nordic Serialization code indicating that data has been received - No IRQ generated and no Serialization events.

I checked that the initialization of the Serialization is done on the Nordic device & get a couple of IRQ/Events at startup, but nothing after that.

Can you suggest what might be wrong? I set up the Nordic Serialization code in the same way as one of the Serialization Example projects (for SPI).

Regards,

Declan

RE: Using Serialization on a nRF52832

Jørgen Holmefjord — Thu, 22 Mar 2018 15:28:18 GMT

This document might be of interest. It is for nRF51 series, and old serializers, but should have som useful information. You would most likely need all files found in components\serialization\application\ and components\serialization\common\. You will have to adapt the files to work with the application CPU and libraries.

SPI_REQ and SPI_RDY are simply GPIOs (like SPI_CS).

RE: Using Serialization on a nRF52832

Declan Traill — Wed, 21 Mar 2018 04:39:13 GMT

Hi Jørgen,

Thanks for the reply. I have already seen those pages, but there isn't a list anywhere of which files are required to be included in the build for the Application CPU project. I have tried adding the files I listed above, and had to add app_error_weak.c, app_error.c, ble_serialization.h and cond_field_serialization.h also. Now it builds ok & also the device driver for the Application CPU SPI peripheral will need to be defined in ser_phy.c

There is another question I have too: the SPI peripheral on the Application CPU I am using doesn't have SPI_REQ or SPI_RDY lines (it only has SPI_CSN, SPI_MOSI, SPI_MISO, SPI_CLK), can Serialization be made to work with this configuration over SPI? Is there anything I need to configure/change in software to allow the SPI to work with 4 wires, or can I configure normal GPIO lines on the Application CPU to function as SPI_REQ & SPI_RDY lines?

Regards,

Declan Traill

RE: Using Serialization on a nRF52832

Jørgen Holmefjord — Tue, 20 Mar 2018 15:15:54 GMT

Hi,

There are multiple application side examples for serialization. They are located within other example directories. Please have a look at this page for an overview of which examples include serialization examples.

Unfortunately, I'm not aware of any examples of non-Nordic serialization, but maybe you can get some inspiration from this thread? The serialization PHYs are described on this page. The Porting serialization libraries should describe the rest of what you need to implement this on another chip.

Best regards,
Jørgen