We are migrating our application to use PicoCOM4 as a replacement of the PicoCOM2.
Our application works with the PicoCOM2 modul as expected.
Testing the same application on the PicoCOM4 the SPI-interface does not operate the chip select pin (PIN29 =PCS0) of the SPI-bus interface.
The SPI-driver version is V2.5, the Hardware version is V1.3
According to the documentation
QuoteNative SPI Support Version 1.3 (2011-11-14) page 11
pin 29 should be driven by the SPI-driver.
But looking into the documentation
QuotePicoCOM Device Driver Version V1.2 (2012-01-24) page 8
pin 29 is capable as a input terminal only. This contradicts with the information in SPI-driver documentation.
What can I do to make the pin 29 (PCS0) work?
Is there an error in the documentation?
here is my SPI configuration:
- reg open
- reg create key \Drivers\SPIController0
- reg set val "IrqTriggerLevel" dword 0x8
- reg open
- reg create key \Drivers\Builtin\SPI1
- reg set val "Dll" string "pc4_nspi"
- reg set val "FriendlyName" string "Native SPI driver"
- reg set val "Prefix" string "SPI"
- reg set val "Index" dword 1
- reg set val "Order" dword 0x65
- reg set val "ClockFreq" dword 0xf4240
- reg set val "SPIMode" dword 3
- reg set val "DriverMethod" dword 1
- reg set val "SPIController" dword 0
- reg open \Drivers\Builtin\CAN1
- reg set val "Flags" dword 4
- reg save
There was an entry
in the SPIController0 setting using the PicoCOM2, that activaded the chip select function.
Where is it controlled now? The above documentation does not reference to such an option.
Can I access /drive pin 29 (PCS0)?
Regards Jörg