RE: Build Error After Update nRF Connect SDK from v2.3 to v2.5

Sigurd Hellesvik — Thu, 30 Nov 2023 13:09:53 GMT

Hi,

I agree with the addr -> address changes. See this commit for an example.

[quote user="skim"]1. NRFX_TIMER_DEFAULT_CONFIG -> NRFX_TIMER_DEFAULT_CONFIG(frequency) [/quote]

[quote user="skim"]2. NRFX_SPIM_PIN_NOT_USED -> ????. The compiler suggests NRF_GPIO_PIN_NOSENSE, but i am not sure if it is a match.[/quote]

I think it will be NRF_SPIM_PIN_NOT_CONNECTED

Regards,
Sigurd Hellesvik

skim — Thu, 30 Nov 2023 01:01:45 GMT

This is the change I made after looking through some documentations.

1. NRFX_TIMER_DEFAULT_CONFIG -> NRFX_TIMER_DEFAULT_CONFIG(frequency)

2. NRFX_SPIM_PIN_NOT_USED -> ????. The compiler suggests NRF_GPIO_PIN_NOSENSE, but i am not sure if it is a match.

3. nrfx_gpiote_out_task_addr_get -> nrfx_gpiote_out_task_address_get

4. nrfx_gpiote_clr_task_addr_get -> nrfx_gpiote_clr_task_address_get

5. nrfx_spim_start_task_get -> nrfx_spim_start_task_address_get

6. nrfx_spim_end_event_get -> nrfx_spim_end_event_address_get

Please let me know if the change I made was not correct.