change device name through spi

[NRM]

hi

Working with Linux operating system I faced the problem not knowing how can the nrf52840 device name be changed via the SPI protocol and what frame format should be used?

I would appreciate if you help me with step by step guidance.

Many thanks

[Edvin]

Hello,

I am not sure what you are asking. What name do you want to change? Is the nRF52840 connected to your linux computer using SPI?

Best regards,

Edvin

[NRM]

Hello
Yes nrf52840 connected to a core board with linux operation system using SPI . How can I merge advertise and SPI(master and slave) communications examples into one code so that the string that nrf receives as a slave will sit instead of the device name ?
#define DEVICE_NAME      "Nordic"

On the other hand, the main issue is what should be the spi frame format for Linux?

[NRM]

I have no problem with the default pins on the DK boards and data is sent / received correctly. The problem is when the pins numbers change to:

cs:P0.24(AD20)
CLK:P0.15(AD10)
mosi:P0.17(AD12)
miso:P0.22(AD18)

in sdk_config.h

Sorry, I am a beginner. I tried to send a photo on this page, but I failed to send it.

I can get "<info> app: Transfer completed. Received: ÿÿÿÿÿÿÿ " from slave and " <info> app: Transfer completed "from master with spi usb to uart by terminal .

[Edvin]

Is this actually running on a custom board, or on the DK?

If it is on the DK, the reason it doesn't work is that the pins P0.17 and P0.22 are not routed out to the GPIO headers by default. If you look on the back of the DK, it shows you some of the pins and their use. e.g. pin P0.13-P0.16 are used for the LEDs (but they are routed out, so that is OK, as long as the application are not trying to control those GPIOs by toggling LEDs at the same time as you are trying to use them as SPI pins).

However, P0.17 and P0.22 are used as QSPI pins for the external flash chip on the DK, so these are not connected to the GPIO headers. You can see on the back of the DK what solder bridges you would have to cut and solder in order to do so. For these specifically, you would need to:

P0.17: cut SB17, solder SB23

P0.22: cut SB15, solder SB25

Alternatively, test with different GPIOs, if you want to do it on the DK.

Best regards,

Edvin

[NRM]

These examples were tested with changed pins on both the DK and the custom board and both have the same problem.

The photo below is taken of the SPI pins (cs:P0.24,CLK:P0.15,mosi:P0.17,miso:P0.22) on the DK :

[Edvin]

That is not a Nordic nRF52840 DK.

So when testing on the DK, did you modify the solder bridges like described in my previous reply?

And do you connect MOSI -> MOSI and MISO -> MISO in your SPI connection? And CS/SS -> CS/SS and CLK -> CLK?

[NRM]

Hello Edvin

I succeeded to get the data from the slave on the custom board.

thanks for your reply.

Best regards,

Nasim

[Edvin]

Hello Nasim,

I am glad to hear! If it is not too much of a problem, I am curious to know what the problem turned out to be. It would also help knowing these common pit falls, to be able to help other users quicker in the future. 

Best regards,

Edvin

[NRM]

Hello,
In short, I merged two examples of SPI and Template.
After making the necessary changes, I replaced the "m_rx_buf" instead of device name in the "gap_params_init" advertising configuration.
But the reason that the custom board did not send/receive data, I am not sure about this problem, maybe it is the simultaneous connection of the J-link programmer and the back up battery.