@delu Well the documentation clearly states this:

Hi

Using the new simplicity studio 5 (amazing by the way), I noticed that the SPIDRV configuration doesn't create the sl_spidrv_instances.h file as documented. I haven't tried all the peripherals, but the simple LED configuration creates its corresponding sl_simple_led_instances.h (and c).

This isn't a big issue, but I guess it is a bug.

Using the MGM210P022JIA and Gecko SDK Suite: Bluetooth 3.0.0.2, Micrium OS Kernel.

I have a similar issue when using SPIDRV with application CS control. It manifests as CLK not outputting anything on the pin. It adheres to the clock polarity rules, so CLK pin gets pulled high/low depending on config, but CLK doesn't actually clock. Data gets clocked correctly and at the correct rate, but not the CLK assigned pin. With Auto CS control this doesn't happen and everything works.

My CH_PRIORITY was already lifted too...

Couldn't figure it out, so got my use case working by setting the CSHOLD value.

I have a similar issue when using SPIDRV with application CS control. It manifests as CLK not outputting anything on the pin. It adheres to the clock polarity rules, so CLK pin gets pulled high/low depending on config, but CLK doesn't actually clock. Data gets clocked correctly and at the correct rate, but not the CLK assigned pin. With Auto CS control this doesn't happen and everything works.

Couldn't figure it out, so got my use case working by setting the CSHOLD value.