Problems driving the chip select pin PCS0 on SPI interface

  • 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

    Quote

    Native SPI Support Version 1.3 (2011-11-14) page 11

    pin 29 should be driven by the SPI-driver.
    But looking into the documentation

    Quote

    PicoCOM 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:


    There was an entry

    Code
    1. reg set value "CSDecode" dword 1


    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

    Mit freundlichen Grüßen
    Jörg Bartel


    Entwicklungsinenieur
    Saxon Junkalor GmbH
    Alte Landebahn 29
    06846 Dessau


    Tel: 0340 5510344

  • I think there is missing a registry value in the applied ndcucfg script:

    Code
    1. reg set val CsPin dword 0xB


    This should enable usage of Pin 29 (IO-Pin 11/0xB). We will correct this line in the supplied scripts.

    Software developer, F&S Elektronik Systeme GmbH
    As this is an international forum, please try to post in English.
    Da dies ein internationales Forum ist, bitten wir darum, Beiträge möglichst in Englisch zu verfassen.

  • Hai there,


    I have tried the setting

    Code
    1. reg set val CsPin dword 0xB

    with no success. The PCS0 line stays at zero. I would expect it to be high and getting active low.


    Can you reconstruct the behavior I am observing?


    What is about the documentation content in the PicoCOM device driver V1.2 page 8?
    It says pin 29 is an input.
    Can this be the reason that it not works?

    Mit freundlichen Grüßen
    Jörg Bartel


    Entwicklungsinenieur
    Saxon Junkalor GmbH
    Alte Landebahn 29
    06846 Dessau


    Tel: 0340 5510344

  • I have currently tested it again and I think the drivers version 2.5 is incompatible to the latest kernel release (some CEDDK functionality I suppose). Anyway I have sent you the latest drivers version (3.2) and all required scripts via E-Mail. This will work for sure.


    Regarding the Input-marking in the documentation: This is faulty in the documentation. Only the other SPI pins have some restrictions on Input/Output capabilities. We have also updated the device driver documentation.


    Sorry for this inconveniences!

    Software developer, F&S Elektronik Systeme GmbH
    As this is an international forum, please try to post in English.
    Da dies ein internationales Forum ist, bitten wir darum, Beiträge möglichst in Englisch zu verfassen.