Passing Parameters to Software interrupt (EGU)

RE: Passing Parameters to Software interrupt (EGU)

Javiehm — Fri, 19 Nov 2021 13:27:13 GMT

SO that worked, actually what i was planning to do makes almost no sense/ if someone wants to know then send me a mail...

it is possible to manage Slave switsching with the software provided, doing what i wanted to do.... goes into interrupting the spi workflow

RE: Passing Parameters to Software interrupt (EGU)

Javiehm — Wed, 29 Sep 2021 10:53:39 GMT

Thank you! i will try this and let you know

RE: Passing Parameters to Software interrupt (EGU)

Kenneth — Wed, 29 Sep 2021 10:48:31 GMT

You need some global variables to handle this for you, e.g. that will work as kind of a state machine so when you receive the SPI interrupt you know what have been sent and received.

Tip: If you are using nrf_drv_spi_init(), then you can find that the last parameter is called 'p_context', this can be a pointer to the global varible that you will also receive in the callback spi_evt_handler().

Kenneth