There is a problem with the SPI signal waveform.

[odenwar]

I checked the SPI communication using the NRF52832 development board.

Based on the firmware of the previously developed NRF52810 product, the SPI operation code is applied.
Compilation and download were executed, and the operation waveform is as follows.

Experiment 1

SS	P0.14
SCK	P0.10
MOSI	P0.06

  

SCK is showing normal signal.

Experiment 2

I tested by changing the port based on SCK.

LE	P0.14
SCK	P0.06
MOSI	P0.10

                                                                                                   
   

LE	P0.10
SCK	P0.14
MOSI	P0.06

Experiment 3

The data was transferred from FF values to AA values.

SS	P0.10
SCK	P0.14
MOSI	P0.06

  

Questions .
1. Why is my data not being transmitted?
2. Why are the signal levels of SS in Experiment 1 and SCK in Experiment 3 change?
3. Why does the MOSI in Experiment 1 have random pulses?

[Eugene Yu]

You need to refer to the back side of nRF52-DK.

Because some GPIO pins are using for specific functions such as LED, Button, and UART.

As for port no.6, it is using for UART which means, it already configured UART tx if you use NRF_LOG with the UART backend.

I recommend you to use RTT instead of UART backend and disable the BSP function that using buttons and LEDs.

[Karl Ylvisaker]

Hello, 

To supplement Eugene's excellent answer, I'd just like to point you in the direction of the nRF52 DK's Connector Interface summary. As Eugene already mentions, many of the pins are already in use for different functionality on the DK, and you must either solder or cut their associated solder bridges to disconnect them from this functionality.
In your case, you are attempting to use both pins used by the UART (p0.06), the NFC antenna (p0.10) and a button (p0.14). You can read about how to Solder bridge configurations here, and the NFC antenna disabling here

For future reference, please also make sure to check the SoC's Pin Assignment documentation in advance of any pin assignment, to make sure that the pin in question is not designated as a low-frequency pin (<10 kHz), if you intend to use it for high-frequency signals.

Please do as suggested by Eugene, and let us know if it does not resolve / explain your issue.

Best regards,
Karl