2009-02-09 03:07:24     How to solve sd/mmc and serial flash with same spi conflictive problems in Bf527

Document created by Aaronwu Employee on Aug 13, 2013
Version 1Show Document
  • View in full screen mode

2009-02-09 03:07:24     How to solve sd/mmc and serial flash with same spi conflictive problems in Bf527

Bill Xie (CHINA)

Message: 69061   

 

Hi,

 

   In my sesytem with spi/sd and serial flash.I want to mount one serial flash partion as to save some code variable.

 

So enble mtd configure . But sd and serial flash use same spi bus line led to some exceptional message.

 

The output message is :

 

  m25p80 spi0.1: m25p40 (512 Kbytes)

Creating 3 MTD partitions on "m25p80":

0x00000000-0x00040000 : "bootloader"

mtd: Giving out device 0 to bootloader

0x00020000-0x00060000 : "file system"

mtd: Giving out device 1 to file system

0x00060000-0x00080000 : "code file system"

mtd: Giving out device 2 to code file system

bfin-spi bfin-spi.0: Blackfin BF5xx on-chip SPI Contoller Driver, Version 1.0, regs_base@ffc00500, dma channel@7

Initializing USB Mass Storage driver...

usbcore: registered new interface driver usb-storage

USB Mass Storage support registered.

rtc-bfin rtc-bfin: rtc core: registered rtc-bfin as rtc0

i2c /dev entries driver

usbcore: registered new interface driver usbhid

drivers/hid/usbhid/hid-core.c: v2.6:USB HID core driver

drivers/mmc/spi_mmc/spi_mmc_core.c spi_mmc_init 1304

mmc_pio_spi:cs_#: 0x29, baud=0x0, flag=0xff00, ctrl=0x400

mmc_pio_spi:cs_#: 0x29, baud=0x0, flag=0xff20, ctrl=0x5009

peripheral_request: Peripheral 18 function 2 is already reserved by bfin-spi !

Hardware Trace:

   0 Target : <0x000047f0> { _dump_stack + 0x0 }

     Source : <0x00005cd2> { _peripheral_request + 0x14a }

   1 Target : <0x00005cd2> { _peripheral_request + 0x14a }

     Source : <0x0000d82e> { _printk + 0x16 }

   2 Target : <0x0000d82a> { _printk + 0x12 }

     Source : <0x0000d6e0> { _vprintk + 0x1b8 }

   3 Target : <0x0000d6d4> { _vprintk + 0x1ac }

     Source : <0x0000d6c6> { _vprintk + 0x19e }

   4 Target : <0x0000d6c2> { _vprintk + 0x19a }

     Source : <0x0000d510> { _wake_up_klogd + 0x24 }

   5 Target : <0x0000d4ec> { _wake_up_klogd + 0x0 }

     Source : <0x0000dc18> { _release_console_sem + 0x1f4 }

   6 Target : <0x0000dc0a> { _release_console_sem + 0x1e6 }

     Source : <0x0000dbfc> { _release_console_sem + 0x1d8 }

   7 Target : <0x0000dbf2> { _release_console_sem + 0x1ce }

     Source : <0x0000dbe4> { _release_console_sem + 0x1c0 }

   8 Target : <0x0000dbc4> { _release_console_sem + 0x1a0 }

     Source : <0x0000daaa> { _release_console_sem + 0x86 }

   9 Target : <0x0000da7a> { _release_console_sem + 0x56 }

     Source : <0x0000dba6> { _release_console_sem + 0x182 }

  10 Target : <0x0000dba0> { _release_console_sem + 0x17c }

     Source : <0x0000d3e6> { __call_console_drivers + 0x7e }

  11 Target : <0x0000d3e0> { __call_console_drivers + 0x78 }

     Source : <0x0000d3a2> { __call_console_drivers + 0x3a }

  12 Target : <0x0000d392> { __call_console_drivers + 0x2a }

     Source : <0x0000d382> { __call_console_drivers + 0x1a }

  13 Target : <0x0000d368> { __call_console_drivers + 0x0 }

     Source : <0x0000db9c> { _release_console_sem + 0x178 }

  14 Target : <0x0000db92> { _release_console_sem + 0x16e }

     Source : <0x0000db30> { _release_console_sem + 0x10c }

  15 Target : <0x0000db2a> { _release_console_sem + 0x106 }

     Source : <0x0000d366> { ___call_console_drivers + 0x52 }

Stack from 01ee7ef8:

        001bf1f4 00005cd6 00000002 00008412 001bc3e0 0014b7c4 00000012 00000002

        00701a64 00005d24 01ee7f6c 01ee6000 001db4e4 00000000 00000000 001977bc

        00000000 01ee7f48 000f9196 001dced8 000f929c 0070e31c 00000000 00000000

        00000000 00000000 00000000 00000000 01ee6000 84138412 00008414 000f7710

        001dce88 001c4654 00196f70 0015a614 00000518 001c4654 00000000 00000000

        00000000 00000000 00000000 00000000 00000001 00000000 00000000 00000000

 

Call Trace:

[<001c45cc>] _kernel_init+0x0/0x234

[<00001666>] _kernel_thread_helper+0x6/0xc

 

mmc_pio_spi:Requesting Peripherals failed

drivers/mmc/spi_mmc/bfin_pio_spi.c bfin_pio_spi_init 127

drivers/mmc/spi_mmc/bfin_pio_spi.c bfin_pio_spi_unselect 58

spi_mmc: configure for card detection

No IRQF_TRIGGER set_type function for IRQ 55 (<NULL>)

 

-- Bill

QuoteReplyEditDelete

 

 

2009-02-09 04:28:46     Re: How to solve sd/mmc and serial flash with same spi conflictive problems in Bf527

Yi Li (CHINA)

Message: 69075   

 

Bill,

 

Do you select CONFIG_SPI_MMC_BFIN_PIO_SPI? Please try to use the spi framework driver.

 

-Yi

QuoteReplyEditDelete

 

 

2009-02-09 20:35:47     Re: How to solve sd/mmc and serial flash with same spi conflictive problems in Bf527

Bill Xie (CHINA)

Message: 69157   

 

Yi,

 

    Thank you. Yes,i choose CONFIG_SPI_MMC_BFIN_PIO_SPI. If I select CONFIG_MMC_FRAMEWORK_DRIVER,the sd cannot  work.

 

--Bill

QuoteReplyEditDelete

 

 

2009-02-09 20:42:37     Re: How to solve sd/mmc and serial flash with same spi conflictive problems in Bf527

Yi Li (CHINA)

Message: 69158   

 

Bill,

 

> If I select CONFIG_MMC_FRAMEWORK_DRIVER,the sd cannot  work.

 

What is the problem now? it still cannot work?

 

-Yi

QuoteReplyEditDelete

 

 

2009-02-09 21:18:42     Re: How to solve sd/mmc and serial flash with same spi conflictive problems in Bf527

Bill Xie (CHINA)

Message: 69164   

 

Yi,

 

    Thank you very much. /proc/spi_mmc and /dev/spi_mmc both are not exist.

 

-Bill

Attachments

    Outcomes