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.

SPI3 problem on OMAP3530 Custom board

hi all

we have a custom board based on OMAP 3530, which has been tested with

booting linux,android operating systems, the design is based on beagleboard rev c development board. 

we have brought out SPI3 pins on the board and the muxing of that has been done in the u-boot as below

MUX_VAL(CP(ETK_D3_ES2), (IEN | PTU | EN | M1)) /*MCSPI3_CLK*/\
MUX_VAL(CP(ETK_D0_ES2), (IEN | PTD | EN | M1)) /*MCSPI3_SIMO*/\
MUX_VAL(CP(ETK_D1_ES2), (IEN | PTD | DIS | M1)) /*MCSPI3_SOMI*/\
MUX_VAL(CP(ETK_D2_ES2), (IEN | PTD | EN | M1)) /*MCSPI3_CS0*/\
MUX_VAL(CP(ETK_D7_ES2), (IEN | PTD | EN | M1)) /*MCSPI3_CS1*/\

by running a linux after integrationg spi related codes we got three devices

spidev3.0 spidev3.1 and spidev4.0in the /dev directory.. and tested this with spidev_test.c by shorting SIMO and SOMI 

but could not get the desired output . all pins are showing voltage 0.

 the output is as below

root@beagleboard:~/spi_codes# ./spidev3.1
spi mode: 0
bits per word: 8
max speed: 500000 Hz (500 KHz)

00 00 00 00 00 00
00 00 00 00 00 00
00 00 00 00 00 00
00 00 00 00 00 00
00 00 00 00 00 00
00 00 00 00 00 00
00 00

kindly help us to tackle this issue 

thank u 

  • Hi Kiran,

    I revise your software configuration and it seems correct. You should pay attention on the parameter when starting spidev_test because if the spi is not configured properly it will be used the default spi device - *device = "/dev/spidev1.1".

    I advise you to check the connections and lines on the board. May be the problem due to some hardware issue.

    BR

    Tsvetolin Shulev

  • hi Tsvetolin Shulev

    thanks for the reply

    i checked the hardware connections and they are fine..

    we have also brought out mcspi3 and mcspi4 on the expansion header of our custom board as in BB-rev-c and they are working fine (we checked the data transmission and reception using loop back method)

    so we have brought out mcspi3 on two sides ,one on expansion header and another for our dedicated peripheral interfacing.

    so my doubt is  bringing out mcspi3 on two sides causing any problem?