• State
  • Locked Locked
  • Replies 2 replies
  • Subscribers 98 subscribers
  • Views 465 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

SDIO driver issue in TI AM 3517

kobi Beifus
Prodigy 20 points
Other Parts Discussed in Thread: AM3505, AM3517, AM1808
I am using  TI EVB AM3505, which includes kernel version 2.6.32 and AM35x-OMAP35x-PSP-SDK-03.00.01.06.
I am using driver which run over SDIO driver.

My driver fails when the the SDIO is detected. 
Logs with SDIO driver and my driver debug enabled are in the attachment.

 0825.lte_logs.txt

There are 2 kernel logs for this issue:

  1. Warning report from dma driver: Spurious DMA IRQ - /arch/arm/plat-omap/dma.c.
  2. When my driver calls to sdio_memcpy_fromio in gdm_sdio_irq, it return -84 error code , which means "Illegal byte sequence" error.

When I use my driver with TI EVB 1808 I had no issue.

Are you familiar with this issue? how can I fix this issue?

 

  • 0
    TI__Mastermind 30150 points

    kobi Beifus said:
    I am using  TI EVB AM3505, which includes kernel version 2.6.32 and AM35x-OMAP35x-PSP-SDK-03.00.01.06.
    I am using driver which run over SDIO driver.

    You seem to be using the AM3517 EVM but it is not clear to me if you use the according DVSDK 3.00.00.03 SW:
    http://focus.ti.com/docs/toolsw/folders/print/linuxsdk-am35x.html
    Can you confirm?

     

    kobi Beifus said:

    There are 2 kernel logs for this issue:

    1. Warning report from dma driver: Spurious DMA IRQ - /arch/arm/plat-omap/dma.c.
    2. When my driver calls to sdio_memcpy_fromio in gdm_sdio_irq, it return -84 error code , which means "Illegal byte sequence" error.

    When I use my driver with TI EVB 1808 I had no issue.

    It is difficult to comment on this error message as it is coming from a custom dirver (written by you) and that interface with the SDIO driver.

    The AM1808 Linux kernel tree (coming from the Davinci Linux tree for ARM926) and the AM3517 Linux kernel tree (coming from the OMAP Linux tree for Cortex A8) are different tree so the underlaying SDIO driver might be different too.
    Not even speaking about the different Linux kernel version that was provided as part of the DVSDK SW for AM18xx and AM3517.
    so the fact it was wrking on AM1808 might not be very relevant for AM3517.

    Each Linux PSP version does include a Linux driver datasheet that gives details about the different Linux drivers. Please have a look at what is or not supported for SDIO.

     

  • 0 in reply to AnBer
    Prodigy 20 points

    I am using AM3517 EVM.

    I am aware of the different between AM1808 and AM3517. 

    we read AM3517 datasheet and we don't find what is the issue.

    The problem is that our custom driver come from 3 party. This driver works fine on Ubuntu and AM1808.
    What can be the root cause of this issue? Do you know how shall we debug this issue?