This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

McSPI1 CS3 is stuck to HIGH on AM3517 EVM

Hi,

Tried to use two different EVM boards that I possess, same result. Observing on my logic analyser. This SPI mode has 4 CS (0-3) and only the fourth CS is always stuck.

Its other SPI signals (like CLK or Data) are working fine, tried to change SPI clock polarity, speed and it actually affects the signals, but the CS is still always HIGH.

Tried to set mode of SPI_CS_HIGH which should make it active low but it is still const HIGH!

Tried to have a single board definition by removing all other SPI CS definitions (I am trying to use all four) but the result was the same.

Tried to validate my SPI protocol driver by swapping CS's between different SPI devices, but it is always CS3 that is stuck.

Checked the CS level before booting Kernel and it is LOW! So, the kernel might be responsible for this pin behavior.

Using Kernel 2.6.37 base rootfs came with SDK5.

My SPI board definitions are:

{
.modalias = "rf_io_dev", // io dev
.bus_num = 1,
.chip_select = 3,
.max_speed_hz = 1000000,
.mode = SPI_MODE_0,
.controller_data = &rf_mcspi_config,
},

/* mcSPI 1 */
OMAP3_MUX(MCSPI1_CLK, OMAP_MUX_MODE0 | OMAP_PIN_OUTPUT),
OMAP3_MUX(MCSPI1_SIMO, OMAP_MUX_MODE0 | OMAP_PIN_OUTPUT),
OMAP3_MUX(MCSPI1_SOMI, OMAP_MUX_MODE0 | OMAP_PIN_INPUT),
OMAP3_MUX(MCSPI1_CS0, OMAP_MUX_MODE0 | OMAP_PIN_OUTPUT),
OMAP3_MUX(MCSPI1_CS1, OMAP_MUX_MODE0 | OMAP_PIN_OUTPUT),
OMAP3_MUX(MCSPI1_CS2, OMAP_MUX_MODE0 | OMAP_PIN_OUTPUT),
OMAP3_MUX(MCSPI1_CS3, OMAP_MUX_MODE0 | OMAP_PIN_OUTPUT),

Please advise,

Great thanks,

Yakir