Re: [Ltib] Having trouble to run 'spidev_test' on Phytec 3250 board.

On Fri, Aug 20, 2010 at 8:58 AM, Jorge A. Castro <address@hidden> wrote:

Hi Quentin

Thanks for the information. I'm now trying to test some drivers in my board (like I2C, SPI and CAN), and this application may help me to find out if SPI is properly working.

Thanks again.

Regards

Jorge Castro
On 08/19/2010 04:52 PM, Quentin YANG wrote:
Hi Jorge,

You can find the 'spidev_test.c' under ' X:\lpc3250\ltib-qs\rpm\BUILD\linux-2.6.34\Documentation\spi\'
Just copy and compile it in user space. (i.e., X:\lpc3250\ltib-qs\rootfs\home\user\ )

I attached my 'spidev_test' project.
(It's an Eclipse Makefile project.)

Regards,
Quentin
On Fri, Aug 20, 2010 at 1:33 AM, Jorge A. Castro <address@hidden> wrote:
Hi Quentin,

I'm using a LPC3250 from Future Design Inc, which is pretty similar than Phytec 3250. I'm wondering if I can find that spidev_test in order to test this drive in my board. Do you know where to find it? I was looking in the LTIB configuration but I didn't found it.

Thanks,

Jorge

On 08/18/2010 07:30 PM, Quentin YANG wrote:
Hi Kevin,

I can successfully run 'spidev_test' from user space as shown below.

address@hidden debug]# ./spidev_test
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

But when I passed on command line option '-O' , I received error message.

address@hidden debug]# ./spidev_test -O
can't set spi mode: Invalid argument
Aborted

'dmesg' shows:
......
spidev spi1.0: setup: unsupported mode bits 2
......

According to source code: driver/spi/spi.c
............................
    bad_bits = spi->mode & ~spi->master->mode_bits;
    if (bad_bits) {
        dev_dbg(&spi->dev, "setup: unsupported mode bits %x\n",
            bad_bits);
        return -EINVAL;
    }
..............................

It seems has something to do with '~spi->master->mode_bits'.

Any comments on this error?
What could be the reason?

Question Two:
Have you ever tried to run 'spidev_test' on dev:ssp1 on Phytec board?
I could not see any 'SPI CLK signal' on PCM-988/GPIO Expansion Board Patch Field 43E although I was able to run 'spidev_test'.
I am wondering whether it's hardware related or just firmware's problem?
If you can run 'spidev_test' on your phytec board on dev:ssp1, then I can rule out the possibility of hardware fault.

I am waiting for the arrival of our Hardware debugger TRACE32, which is the last resort.

Thanks

Regards,
Quentin
_______________________________________________
LTIB home page: http://ltib.org

Ltib mailing list
address@hidden
http://lists.nongnu.org/mailman/listinfo/ltib
  
-- Jorge A. Castro Canam-Technology, Inc.
_______________________________________________
LTIB home page: http://ltib.org

Ltib mailing list
address@hidden
http://lists.nongnu.org/mailman/listinfo/ltib
-- 
Jorge A. Castro
Canam-Technology, Inc.
_______________________________________________
LTIB home page: http://ltib.org

Ltib mailing list
address@hidden
http://lists.nongnu.org/mailman/listinfo/ltib

From:	Quentin YANG
Subject:	Re: [Ltib] Having trouble to run 'spidev_test' on Phytec 3250 board.
Date:	Fri, 20 Aug 2010 09:47:19 +1000