NRFX build error NRFX_SPIM_DEFAULT_CONFIG; about nrf-doom

[auwi-nordic]

Thanks for testing!

Yeah, the nRF5 SDK / nrfx setup is a bit hacky. nRF5 SDK does not really support nRF53, and I don't think there are plans to add support unfortunately. I should probably add that disclaimer to the readme. The only reason it was used here was that the project started on nRF52, and we don't need a Bluetooth stack yet.

[dovoto]

Thanks for the response. Its a shame they are not supporting the SDK, it feels much cleaner than the new nrf connect stuff.

[auwi-nordic]

Yeah, with multi-core I think the nRF5 SDK and SoftDevice code architecture was getting a bit outdated. Need that RTOS to handle all those concurrency challenges, and it's more up to the challenges faced by the larger customers I suppose.

I can kind of agree, I'm experimenting with nRF Connect SDK and Zephyr myself now to open up the option of using Bluetooth keyboard and mouse, and maybe Thread for multiplayer. It's daunting, and a lot of different concepts/scripts/tools, but when it works it works and you can take on bigger tasks, like simultaneous Bluetooth and Thread.

I hope to write some Blog posts on porting Doom to Zephyr/nRF Connect SDK to get a more practical guide to getting started with a real project. We'll see what comes of that.

[dovoto]

Definitely will keep an eye out for that. My product sort of relies on an approachable development environment on the application side (the network side can be mostly static and so is not as critical). Not quite arduino level of dumbed down but that level of getting started would be nice.