https://devzone.nordicsemi.com/f/nordic-q-a/116507/custom-board-and-application-based-on-nrf-connect-sdkHi, recently I started migrating my company&#39;s firmware from nRF5 SDK to nRF Connect SDK. I have been following the devAcademy courses and so far 1. I have created my custom board files 2. Defined the .dts for the custom board and populated it with theen-USTelligent Community 13Wed, 20 Nov 2024 10:15:59 GMThttps://devzone.nordicsemi.com/thread/511257?ContentTypeID=1Wed, 20 Nov 2024 10:15:59 GMT137ad170-7792-4731-bb38-c0d22fbe4515:0f429665-8e8a-45aa-b055-2927ff3a328emasterLee<p>Good! I want to make some progress the classic way and then perhaps I can test the device driver model when I have set up the main structure.</p> <p><br />Thank you for your time and help!</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/511128?ContentTypeID=1Tue, 19 Nov 2024 14:27:40 GMT137ad170-7792-4731-bb38-c0d22fbe4515:f6a37c03-1732-4936-87d2-2179f7f3ec63Einar Thorsrud<p>Hi,</p> <p>I do not see any fundamental problems with ignoring the Zephyr driver model. The advantage of that is that the interface is standardized and portable, but it is fine to implement drivers in your application in other ways, and in many cases that makes more sense. (You can refer to this <a href="https://github.com/einarthorsrud/random_ncs_samples/tree/main/spi_master_slave_separate">unofficial sample</a> to se a simple way to implement for instance SPI communication.)</p><div style="clear:both;"></div>