Error on using ONLY SPI1 (Can not set SPI mode to Mode3)

Since I have a broken pin on SPI0, I have to use SPI1 on my Raspberry Pi 3B+ In config.txt i have set

# Uncomment some or all of these to enable the optional hardware interfaces
#dtparam=i2c_arm=on
#dtparam=i2s=on
#dtparam=spi=on
dtoverlay=spi1-1cs,cs0_pin=12

pi@raspberrypi:~ $ ls -l /dev/spidev* crw-rw---- 1 root spi 153, 0 Okt 1 11:36 /dev/spidev1.0 pi@raspberrypi:~ $

If i use this code:

            var settings = new SpiConnectionSettings(1, 0)
            {
                ChipSelectLineActiveState = PinValue.Low,
                ClockFrequency = 2000000,
                DataBitLength = 8,
                DataFlow = DataFlow.MsbFirst,
                Mode = SpiMode.Mode3
            };
            using var spiDevice = SpiDevice.Create(settings);
            spiDevice.WriteByte((byte)(address | 0x80));

i get: Unhandled exception. System.IO.IOException: Error 22. Can not set SPI mode to Mode3. at System.Device.Spi.UnixSpiDevice.Initialize() at System.Device.Spi.UnixSpiDevice.WriteByte(Byte value)

Add following information:

pi@raspberrypi:~ $ dotnet --info
.NET Core SDK (gemäß "global.json"):
 Version:   3.1.402
 Commit:    9b5de826fd

Laufzeitumgebung:
 OS Name:     raspbian
 OS Version:  10
 OS Platform: Linux
 RID:         linux-arm
 Base Path:   /opt/dotnet/sdk/3.1.402/

Host (useful for support):
  Version: 3.1.8
  Commit:  9c1330dedd

.NET Core SDKs installed:
  3.1.402 [/opt/dotnet/sdk]

.NET Core runtimes installed:
  Microsoft.AspNetCore.App 3.1.8 [/opt/dotnet/shared/Microsoft.AspNetCore.App]
  Microsoft.NETCore.App 3.1.8 [/opt/dotnet/shared/Microsoft.NETCore.App]

To install additional .NET Core runtimes or SDKs:
  https://aka.ms/dotnet-download

• Version of System.Device.Gpio package is 1.0.0
• Version of Iot.Device.Bindings package is 1.0.0

[krwq]

@wolfgangmauer, we only support Uln2003 for stepper motors for now. If you get that to work I’d recommend you to create a PR so someone can re-use your works 😄

[Ellerbach]

[Triage] As this seems to be Raspberry Pi related and based on the discussion, we will close this issue. Do not hesitate to reopen if needed.