[help me]SPI Commnunication btw nRF52 series and intanRHD2132, SPIM + TIMER

RE: [help me]SPI Commnunication btw nRF52 series and intanRHD2132, SPIM + TIMER

Håkon Alseth — Fri, 31 May 2024 13:25:31 GMT

Happy to help out.

Let me know if you have any issues or questions. Hope you have a great weekend!

Kind regards,

Håkon

RE: [help me]SPI Commnunication btw nRF52 series and intanRHD2132, SPIM + TIMER

seongmincho — Fri, 31 May 2024 12:57:10 GMT

Thank you for your kind response. I've decided on the next course of action

RE: [help me]SPI Commnunication btw nRF52 series and intanRHD2132, SPIM + TIMER

Håkon Alseth — Fri, 31 May 2024 12:40:48 GMT

Hi,

When using easydma list, it will auto-increment your pointers for each transaction. You should setup a buffer that is as large as your overall transfer on both RX and TX.

Instead of using m_tx_buffer/m_rx_buffer as the EasyDMA buffers, you should use Command (declare it as a 1-d array instead of 2-d array) / result.

Kind regards,

Håkon

RE: [help me]SPI Commnunication btw nRF52 series and intanRHD2132, SPIM + TIMER

seongmincho — Fri, 31 May 2024 11:09:03 GMT

Hello! I have programmed new code based on your advice. Thank you for your help.
As a result, the minimum value of 'TIME_TO_WAIT_US' has been reduced from 43us to 13us. However, there is still room for improvement. I need the value to be smaller than 13us('TIME_TO_WAIT_US'). It seems that I am not utilizing the buffer effectively. Could you please review the code and suggest any necessary modifications?

Here are the requirements I need to implement:

- Send a 16-bit command to the ADC via SPI. (receive the 16-bit data to the nRF52840 via SPI)
- The 16-bit command must be sent at regular intervals defined by TIME_TO_WAIT_US.

Could you advise on how to manage the variables uint8_t Command[30][2] and uint8_t result[70] more efficiently in the code?

RE: [help me]SPI Commnunication btw nRF52 series and intanRHD2132, SPIM + TIMER

Håkon Alseth — Wed, 29 May 2024 08:11:10 GMT

Hi,

For new projects, we recommend that you use nRF connect SDK (ncs):

https://academy.nordicsemi.com/courses/nrf-connect-sdk-fundamentals/

[quote user="seongmincho"]

1. The person in the link you provided uses 'nRF5_SDK,' right? It seems to me that 'nRF5_SDK' is often used with 'SEGGER Embedded Studio'.

[/quote]

Yes, but the low level nrfx APIs are quite similar (almost identical).

[quote user="seongmincho"]2. Is the difference between 'nRF Connect SDK' and 'nRF5_SDK' just that one is the newer version and the other is the older version? Sometimes it's really confusing and difficult when looking at different versions of the code. There's no clear place that explains these concepts, so I'm asking you."[/quote]

Both nRF5 SDK and NCS runs on the same hardware, so there will be similarities in the low level APIs.

As mentioned, we do recommend that you use NCS for new projects.

Kind regards,

Håkon

RE: [help me]SPI Commnunication btw nRF52 series and intanRHD2132, SPIM + TIMER

seongmincho — Wed, 29 May 2024 07:55:14 GMT

"Thank you so much for your response. I am applying PPI and making some adjustments.

I have a few questions that are different from the original post's topic.

1. The person in the link you provided uses 'nRF5_SDK,' right? It seems to me that 'nRF5_SDK' is often used with 'SEGGER Embedded Studio'.

2. Is the difference between 'nRF Connect SDK' and 'nRF5_SDK' just that one is the newer version and the other is the older version? Sometimes it's really confusing and difficult when looking at different versions of the code. There's no clear place that explains these concepts, so I'm asking you."

RE: [help me]SPI Commnunication btw nRF52 series and intanRHD2132, SPIM + TIMER

Håkon Alseth — Tue, 28 May 2024 07:20:14 GMT

Hi,

The error that you're receiving is 0xBAD0000 + 11 -> NRFX_ERROR_BUSY.

You should consider to use SPIM + PPI, as shown in this thread: RE: Reading samples from external ADC using SPIM with EasyDMA arrayList

Kind regards,

Håkon