[#4323] reboot fails on bf527-ezkit 08r1 branch

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

[#4323] reboot fails on bf527-ezkit 08r1 branch

Submitted By: Vivi Li

Open Date

2008-08-07 23:04:56     Close Date

2008-11-14 06:28:05


Very Low     Assignee:

Mike Frysinger

Michael Hennerich


Closed     Fixed In Release:


Found In Release:

N/A     Release:



N/A     Board:



N/A     Silicon Revision:

Is this bug repeatable?:

N/A     Resolution:


Uboot version or rev.:

    Toolchain version or rev.:


App binary format:


Summary: reboot fails on bf527-ezkit 08r1 branch



reboot fails on bf527-ezkit 08r1 branch since kernel version 5113.


Bellow is the log:


Linux version (test@uclinux95-bf527-std) (gcc version 4.1.2 (ADI svn8

early printk enabled on early_BFuart0

Hardware Trace Active and Enabled

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

Compiled for ADSP-BF527 Rev 0.0

Warning: Unsupported Chip Revision ADSP-BF527 Rev 0.0 detected

Blackfin Linux support by   blackfin.uclinux.org/

Processor Speed: 525 MHz core clock and 131 MHz System Clock

Board Memory: 64MB

Kernel Managed Memory: 64MB

Memory map:

  text      = 0x00001000-0x0012afc0

  rodata    = 0x0012b000-0x00184d14

  data      = 0x00185000-0x0019c000

    stack   = 0x00186000-0x00188000

  init      = 0x0019c000-0x00443000

  bss       = 0x00443000-0x00452c10

  available = 0x00452c10-0x03eff000

  DMA Zone  = 0x03f00000-0x04000000

NOMPU: setting up cplb tables for global access

Instruction Cache Enabled

Data Cache Enabled (write-through)

Built 1 zonelists.  Total pages: 16002

Kernel command line: root=/dev/mtdblock0 rw earlyprintk=serial,uart1,57600 console=tty0 console=ttyf

Configuring Blackfin Priority Driven Interrupts

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

console handover: boot [early_BFuart0] -> real [ttyBF0]

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

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

Memory available: 59504k/65536k RAM, (2716k init code, 1191k kernel code, 516k data, 1024k dma, 584)

Blackfin Scratchpad data SRAM: 4 KB

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

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

Blackfin Instruction SRAM: 48 KB (42 KB free)

Security Framework v1.0.0 initialized

Mount-cache hash table entries: 512

NET: Registered protocol family 16

Blackfin GPIO Controller

Blackfin DMA Controller

stamp_init(): registering device resources

Generic PHY: Registered new driver

SCSI subsystem initialized

usbcore: registered new interface driver usbfs

usbcore: registered new interface driver hub

usbcore: registered new device driver usb

musb_hdrc: version 6.0, pio, host, debug=0

musb_hdrc: kernel must blacklist external hubs

musb_hdrc: USB Host mode controller at ffc03800 using PIO, IRQ 59

musb_hdrc musb_hdrc.0: MUSB HDRC host driver

musb_hdrc musb_hdrc.0: new USB bus registered, assigned bus number 1

usb usb1: configuration #1 chosen from 1 choice

hub 1-0:1.0: USB hub found

hub 1-0:1.0: 1 port detected

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

io scheduler noop registered

io scheduler anticipatory registered (default)

io scheduler cfq registered

bfin-t350mcqb: 320x240 24-bit RGB FrameBuffer initializing...

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

bfin-otp: initialized

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

Serial: Blackfin serial driver

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

RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize

bfin_mac_mdio: probed

bfin_mac: attached PHY driver [Generic PHY] (mii_bus:phy_addr=0:03, irq=-1, mdc_clk=2500000Hz(mdc_d)

bfin_mac: Version 1.1, Blackfin BF53[67] BF527 on-chip Ethernet MAC driver

bfin-spi bfin-spi.0: Blackfin BF5xx on-chip SPI Contoller Driver, Version 1.0, regs_base@ffc00500, 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

usbcore: registered new interface driver usbhid

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

Advanced Linux Sound Architecture Driver Version 1.0.12rc1 (Thu Jun 22 13:55:50 2006 UTC).

ALSA device list:

  No soundcards found.

TCP cubic registered

NET: Registered protocol family 1

NET: Registered protocol family 17

rtc-bfin rtc-bfin: setting the system clock to 2004-05-31 04:46:42 (1085978802)

usb 1-1: new high speed USB device using musb_hdrc and address 2

usb 1-1: configuration #1 chosen from 1 choice

scsi0 : SCSI emulation for USB Mass Storage devices

IP-Config: Complete:

      device=eth0, addr=, mask=, gw=,

     host=bf527-ezkit, domain=, nis-domain=(none),

     bootserver=, rootserver=, rootpath=

Freeing unused kernel memory: 2716k freed


        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|            -   blackfin.uclinux.org/

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

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

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


Have a lot of fun...



BusyBox v1.4.1 (2008-08-08 13:30:38 CST) Built-in shell (msh)

Enter 'help' for a list of built-in commands.


root:/> PHY: 0:03 - Link is Up - 100/Full

scsi 0:0:0:0: Direct-Access     SanDisk  U3 Cruzer Micro  2.21 PQ: 0 ANSI: 2

sd 0:0:0:0: [sda] 1994385 512-byte hardware sectors (1021 MB)

sd 0:0:0:0: [sda] Write Protect is off

sd 0:0:0:0: [sda] Assuming drive cache: write through

sd 0:0:0:0: [sda] 1994385 512-byte hardware sectors (1021 MB)

sd 0:0:0:0: [sda] Write Protect is off

sd 0:0:0:0: [sda] Assuming drive cache: write through

sda: sda1 sda2

sd 0:0:0:0: [sda] Attached SCSI removable disk


root:/> version

kernel:    Linux release, build #98 Fri Aug 8 19:44:47 CST 2008

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

user-dist: release svn-6979, build #1133 Fri Aug 8 19:44:26 CST 2008


root:/> reboot

bfin-wdt: Unexpected close, not stopping watchdog!

Restarting system.





--- Michael Hennerich                                        2008-08-08 04:19:27

I checked in a temporary workaround to fix BUG #4323.


The real issue is that the System Software Reset sequence doesn't really reset

the System. Without resetting the SIC_IWRx registers to its Reset = 0xFFFF FFFF

sate the bootrom kernel will sit in IDLE waiting for an event that will never



Add Mike.




--- Mike Frysinger                                           2008-08-08 19:02:24

seems only SIC_IWR1 on BF52x is affected.  SIC_IWR on BF537, SIC_IWR0 on BF52x,

and SIC_IWR[012] on BF54x all reset as expected.


hard to say what will happen in a watchdog or double fault case, so perhaps we

should be leaving the MDMA1 (and any other SIC_IWR1 bits the bootrom uses)

enabled all the time in the kernel until the hardware gets fixed ?


--- Michael Hennerich                                        2008-08-12 11:37:52

On BF52x we now keep MDMA0 and MDMA1 enabled in SIC_IWR1.

This workaround should be safe.


I leave this bug open with a low priority, until we get confirmation on this

issue. Surround the workarounds with ANOMALY_????, etc.





--- Michael Hennerich                                        2008-10-28 09:51:29

The518 Anomaly sheet now includes ANOMALY_05000431, however the 527 sheet

doesn't define ANOMALY_05000431 


+#define ANOMALY_05000431 (1)

+/* Certain SIC Registers are not Reset After Soft or Core Double Fault Reset





--- Mike Frysinger                                           2008-10-28 23:11:51

i dont see anomaly 431 in the BF51x anomaly sheet ... i do see it in the BF526

sheet only ...


but i dont think that's the issue ?  we actually want anomaly 435 ?

"Certain SIC Registers are not Reset After Soft or Core Double Fault



--- Michael Hennerich                                        2008-10-29 03:45:25

+#define ANOMALY_05000431 (1)

+/* Certain SIC Registers are not Reset After Soft or Core Double Fault Reset


+#define ANOMALY_05000435 (1)


Well - I meant ANOMALY_05000435, but erroneously copied the ANOMALY define from

the line above….




--- Mike Frysinger                                           2008-10-29 03:50:34

the latest public sheet doesnt have bf52x listed, but the internal tracker does.

ive updated the anomaly headers in our toolchain, so we can just copy those

over to the kernel and change the code to use this anomaly define ... then we

can close out this issue finally ...


--- Mike Frysinger                                           2008-11-14 06:28:05

ive switched the files over to ANOMALY_05000435












File Name     File Type     File Size     Posted By

No Files Were Found