[#5640] It frequently fails to initialize BCSP with bluetooth EZ-Extender

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

[#5640] It frequently fails to initialize BCSP with bluetooth EZ-Extender

Submitted By: Vivi Li

Open Date

2009-10-26 00:59:16     Close Date

2009-11-10 03:44:28

Priority:

Medium     Assignee:

Michael Hennerich

Status:

Closed     Fixed In Release:

N/A

Found In Release:

2010R1     Release:

Category:

Tests     Board:

STAMP

Processor:

BF537     Silicon Revision:

Is this bug repeatable?:

Yes     Resolution:

Rejected

Uboot version or rev.:

    Toolchain version or rev.:

gcc4.1-09r1-rc9

App binary format:

N/A     

Summary: It frequently fails to initialize BCSP with bluetooth EZ-Extender

Details:

 

Test with bluetooth EZ-Extender on bf537-stamp, it frequently fails to initialize BCSP.

 

--

Linux version 2.6.31.4-ADI-2010R1-pre-svn7692 (test@uboot34-bf537stamp) (gcc version 4.1.2 (ADI svn)) #92 Fri Oct 23 17:57:52 CST 2009

register early platform devices

bootconsole [early_shadow0] enabled

bootconsole [early_BFuart0] enabled

early printk enabled on early_BFuart0

Limiting kernel memory to 56MB due to anomaly 05000263

Board Memory: 64MB

Kernel Managed Memory: 64MB

Memory map:

  fixedcode = 0x00000400-0x00000490

  text      = 0x00001000-0x001200f0

  rodata    = 0x001200f0-0x0017d6cc

  bss       = 0x0017e000-0x0018ec08

  data      = 0x0018ec08-0x001a0000

    stack   = 0x0019e000-0x001a0000

  init      = 0x001a0000-0x007c6000

  available = 0x007c6000-0x037ff000

  DMA Zone  = 0x03f00000-0x04000000

Hardware Trace Active and Enabled

Boot Mode: 0

Reset caused by Software reset

Blackfin support (C) 2004-2009 Analog Devices, Inc.

Compiled for ADSP-BF537 Rev 0.2

Blackfin Linux support by http://blackfin.uclinux.org/

Processor Speed: 500 MHz core clock and 125 MHz System Clock

NOMPU: setting up cplb tables

Instruction Cache Enabled for CPU0

  External memory: cacheable in instruction cache

Data Cache Enabled for CPU0

  External memory: cacheable (write-back) in data cache

Built 1 zonelists in Zone order, mobility grouping off.  Total pages: 14223

Kernel command line: root=/dev/mtdblock0 rw ip=10.100.4.50 earlyprintk=serial,uart0,57600 console=ttyBF0,57600 ip=10.100.4.50:10.100.4.174:10.100.4.174:255.255.255.0:bf537-stamp:eth0:off

PID hash table entries: 256 (order: 8, 1024 bytes)

Dentry cache hash table entries: 8192 (order: 3, 32768 bytes)

Inode-cache hash table entries: 4096 (order: 2, 16384 bytes)

Memory available: 48812k/65536k RAM, (6296k init code, 1148k kernel code, 512k data, 1024k dma, 7744k reserved)

NR_IRQS:98

Configuring Blackfin Priority Driven Interrupts

console [ttyBF0] enabled, bootconsole disabled

console [ttyBF0] enabled, bootconsole disabled

Calibrating delay loop... 995.32 BogoMIPS (lpj=1990656)

Security Framework initialized

Mount-cache hash table entries: 512

Blackfin Scratchpad data SRAM: 4 KB

Blackfin L1 Data A SRAM: 16 KB (16 KB free)

Blackfin L1 Data B SRAM: 16 KB (16 KB free)

Blackfin L1 Instruction SRAM: 48 KB (36 KB free)

NET: Registered protocol family 16

Blackfin DMA Controller

stamp_init(): registering device resources

bio: create slab <bio-0> at 0

Bluetooth: Core ver 2.15

NET: Registered protocol family 31

Bluetooth: HCI device and connection manager initialized

Bluetooth: HCI socket layer initialized

NET: Registered protocol family 2

IP route cache hash table entries: 1024 (order: 0, 4096 bytes)

TCP established hash table entries: 2048 (order: 2, 16384 bytes)

TCP bind hash table entries: 2048 (order: 1, 8192 bytes)

TCP: Hash tables configured (established 2048 bind 2048)

TCP reno registered

NET: Registered protocol family 1

msgmni has been set to 95

io scheduler noop registered

io scheduler anticipatory registered (default)

io scheduler cfq registered

bfin-uart: Blackfin serial driver

bfin-uart.0: ttyBF0 at MMIO 0xffc00400 (irq = 18) is a BFIN-UART

bfin-uart.1: ttyBF1 at MMIO 0xffc02000 (irq = 20) is a BFIN-UART

brd: module loaded

bfin_mii_bus: probed

bfin_mac: attached PHY driver [SMSC LAN83C185] (mii_bus:phy_addr=0:01, irq=-1, mdc_clk=2500000Hz(mdc_div=24)@sclk=125MHz)

bfin_mac bfin_mac.0: Blackfin on-chip Ethernet MAC driver, Version 1.1

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

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

bfin-wdt: initialized: timeout=20 sec (nowayout=0)

Bluetooth: HCI UART driver ver 2.2

Bluetooth: HCI H4 protocol initialized

Bluetooth: HCI BCSP protocol initialized

TCP cubic registered

NET: Registered protocol family 17

Bluetooth: L2CAP ver 2.13

Bluetooth: L2CAP socket layer initialized

Bluetooth: SCO (Voice Link) ver 0.6

Bluetooth: SCO socket layer initialized

Bluetooth: RFCOMM TTY layer initialized

Bluetooth: RFCOMM socket layer initialized

Bluetooth: RFCOMM ver 1.11

Bluetooth: BNEP (Ethernet Emulation) ver 1.3

Bluetooth: BNEP filters: protocol multicast

Bluetooth: HIDP (Human Interface Emulation) ver 1.2

rtc-bfin rtc-bfin: setting system clock to 2015-01-19 19:25:28 UTC (1421695528)

IP-Config: Complete:

     device=eth0, addr=10.100.4.50, mask=255.255.255.0, gw=10.100.4.174,

     host=bf537-stamp, domain=, nis-domain=(none),

     bootserver=10.100.4.174, rootserver=10.100.4.174, rootpath=

Freeing unused kernel memory: 6296k freed

dma_alloc_init: dma_page @ 0x02053000 - 256 pages at 0x03f00000

                           _____________________________________

        a8888b.           / Welcome to the uClinux distribution \

       d888888b.         /       _     _                         \

       8P"YP"Y88        /       | |   |_|            __  __ (TM)  |

       8|o||o|88  _____/        | |    _ ____  _   _ \ \/ /       |

       8'    .88       \        | |   | |  _ \| | | | \  /        |

       8`._.' Y8.       \       | |__ | | | | | |_| | /  \        |

      d/      `8b.       \      \____||_|_| |_|\____|/_/\_\       |

     dP   .    Y8b.       \   For embedded processors including   |

    d8:'  "  `::88b        \    the Analog Devices Blackfin      /

   d8"         'Y88b        \___________________________________/

  :8P    '      :888

   8a.   :     _a88P         For further information, check out:

._/"Yaa_:   .| 88P|            - http://blackfin.uclinux.org/

\    YP"    `| 8P  `.          - http://docs.blackfin.uclinux.org/

/     \.___.d|    .'           - http://www.uclinux.org/

`--..__)8888P`._.'  jgs/a:f    - http://www.analog.com/blackfin

 

Have a lot of fun...

 

 

BusyBox v1.15.2 (2009-10-22 12:57:54 CST) hush - the humble shell

 

root:/> version

kernel:    Linux release 2.6.31.4-ADI-2010R1-pre-svn7692, build #92 Fri Oct 23 17:57:52 CST 2009

toolchain: bfin-uclinux-gcc release gcc version 4.1.2 (ADI svn)

user-dist: release svn-9016, build #43 Fri Oct 23 17:57:11 CST 2009

root:/>

root:/> iwrap_boot -b /dev/ttyBF1

root:/>

root:/> hcid -n &

hcid[171]: Bluetooth HCI daemon

[1] 171 hcid -n

root:/>

root:/> hciattach -n /dev/ttyBF1 bcsp &

[2] 172 hciattach -n /dev/ttyBF1 bcsp

BCSP initialization timed out

root:/>

--

 

Follow-ups

 

--- Michael Hennerich                                        2009-10-26 10:28:48

Did you disable SW5 1,2 ?

 

Connect the BFBLUET-EZEXT onto UART1 P12 Header

On the ADSP-BF537 STAMP-BOARD:

Disconnect SW-5: 1,2

SW5: OFF, OFF, X, X

 

-Michael

 

--- Vivi Li                                                  2009-10-27 02:26:51

The setting is correct.

It seems to me that the first time to run this case, it will pass. Software

reboot the kernel and run the test again, it almost always fail.

 

--- Michael Hennerich                                        2009-10-27 05:02:14

That is expected -

Reboot does not reset the CHIP on the Bluetooth card.

Once the Card is in BCSP mode - and the HCI is attached - it won't let you

reattach.

Since there is not /RESET signal on the STAMP UART header - pressing the reset

button won't help here either. (you need to power cycle the board + card)

 

I would suggest that you test the card on a BF526-EZBRD - where we use the big

connector to attach the card to the EZBRD. Here we have additional GPIOs - we

could use to reset the CHIP on the card.

Unfortunately on the BF526-EZBRD we loose the serial console when used with the

Bluetooth card.

 

Alternatively we could do a wire from the BF537-STAMP to one of the RESET

Selects on the Bluetooth Card.

 

 

-Michael 

 

--- Vivi Li                                                  2009-10-27 06:39:58

As I want to test it in regression machine, so no one can plug off the power

manually each time.

 

I don't have schematic for Bluetooth Card, and I don't know the normal reset

signal is enough for the card to reset.

So could you give some detail about how to do a wire for BF537-STAMP?

 

--- Michael Hennerich                                        2009-10-28 05:24:57

Two options -

1) I could add some RESET GPIO toggling as an option into the iwarp_boot

utility.

2) you do some sysfs GPIO toggling from your test script.

 

I mail you the latest schematics I have.

 

-Michael

 

--- Vivi Li                                                  2009-11-10 03:44:28

While software reboot doesn't work with bluetooth card, board reset works and no

need to plug off the power, only need to reset board before the test.

So reject this bug and close it.

 

 

 

    Files

    Changes

    Commits

    Dependencies

    Duplicates

    Associations

    Tags

 

File Name     File Type     File Size     Posted By

config.bluetooth    application/octet-stream    35886    Vivi Li

Attachments

Outcomes