https://devzone.nordicsemi.com/f/nordic-q-a/11959/nrf52832-spi-no-transfer-done-oledHei guys, this is my environment: nrf52832 on custom board. SDK 9.2 SD 132 1.0..0-3 preloaded in SD memory region OLED with no MISO line PINS configuration: CLK P04 CS P03 MOSI P05 The OLED needsen-USTelligent Community 13Sat, 05 Mar 2016 10:41:39 GMThttps://devzone.nordicsemi.com/thread/45293?ContentTypeID=1Sat, 05 Mar 2016 10:41:39 GMT137ad170-7792-4731-bb38-c0d22fbe4515:396c2dce-419f-48dc-bc0b-88441ac7c15asilvergaucho<p>solved, modyfing spi configuration to mode3.</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/45292?ContentTypeID=1Tue, 23 Feb 2016 12:29:21 GMT137ad170-7792-4731-bb38-c0d22fbe4515:7c1fffab-a551-4239-a658-3a93ac274e18run_ar<p>Have you considered the newer SDK: nRF5_SDK_11.0.0-2.alpha and SD132 v 2? These has quite a lot of changes so I think it would make sense testing these before spending to much time debugging this problem.</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/45291?ContentTypeID=1Sat, 20 Feb 2016 14:46:01 GMT137ad170-7792-4731-bb38-c0d22fbe4515:712770cd-cdc0-4dac-91fe-b6ffc5fe84f1silvergaucho<p>mmhhh as far as I understood, uC is resetting thx to APP_ERROR_CHECK due to temptative to assign GPIOTE in function nrf_drv_gpiote_in_init() after the second write temptative. It enters in the first if and result is NRF_ERROR_INVALID_STATE (8). I think this is because the GPIOTE channel is not released by the spi_master_event_handler(). But i still missing something....</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/45290?ContentTypeID=1Sat, 20 Feb 2016 14:06:22 GMT137ad170-7792-4731-bb38-c0d22fbe4515:12257878-5c86-4b34-a7f7-f51f855be334silvergaucho<p>anyone can help me? Would be very appreciated. Thanks</p><div style="clear:both;"></div>