[#4191] Kernel does not boot if re-program clocks on trunk

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

[#4191] Kernel does not boot if re-program clocks on trunk

Submitted By: Jie Zhang

Open Date

2008-06-24 03:11:58     Close Date

2009-01-20 03:14:22

Priority:

Medium High     Assignee:

Mingquan Pan

Michael Hennerich

Status:

Closed     Fixed In Release:

N/A

Found In Release:

N/A     Release:

trunk

Category:

N/A     Board:

EZKIT Lite

Processor:

BF548     Silicon Revision:

Is this bug repeatable?:

Yes     Resolution:

Fixed

Uboot version or rev.:

    Toolchain version or rev.:

toolchain4.1_2008-11-13

App binary format:

N/A     

Summary: Kernel does not boot if re-program clocks on trunk

Details:

 

I selected "Re-program Clocks while Kernel boots?". Then the kernel didn't boot on bf548 ezkit. The last line on console was:

 

## Starting application at 0x00266000 ...

 

Follow-ups

 

--- Michael Hennerich                                        2008-06-27 08:01:34

assign to me

I guess "[#4204] Trunk kernel crashed on BF533-EZKIT after re-program

clocks of kernel booting" is a duplicate of this bug.

 

-Michael

 

--- Michael Hennerich                                        2008-06-30 04:00:58

Can you add more details (kernel config)

I can't reproduce it.

-Michael

 

--- Jie Zhang                                                2008-07-21 02:28:26

Sorry, I didn't notice your reply. The config file for bf548 ezkit is attached.

 

--- Mingquan Pan                                             2008-08-22 06:32:50

I can also reproduce it on trunk on bf548 ezkit board. Just select:Re-program

Clocks while Kernel boots? and the rest config is default,running it can see

kernel booting fails at above.

 

--- Michael Hennerich                                        2008-08-24 11:04:02

I'll take a look at it on Monday.

-Michael

 

--- Michael Hennerich                                        2008-08-25 09:35:37

Grace and Jie,

Was this on BF548/9 Silicon Rev. 0.1 ?

-Michael

 

--- Mingquan Pan                                             2008-08-28 04:59:43

It is on BF548 EZKIT 1.3 board with bf549 0.1 on it.

 

--- Michael Hennerich                                        2008-08-29 06:42:44

Yes this issue is Hardware Related and only on seen on the BF548 EZKIT Rev.

1.3.

There is not much I can do about it.

 

Latest BF548 EZKIT Rev. 1.4 doesn't show this issue.

I checked the source code and couldn't find Software related issues - or ways

to walk around it.

 

-Michael

 

--- Mingquan Pan                                             2008-09-02 23:43:20

But it is strange that on one bf548 ezkit 1.4 here with 0.2 silicon vision, this

bug can still be reproduced.

 

U-Boot 1.1.6-svn1327 (ADI-2008R2-pre) (Sep  3 2008 - 11:46:04)

 

CPU:   ADSP bf548-0.0 (Detected Rev: 0.2)

Board: ADI BF548 EZ-Kit board

       Support:   blackfin.uclinux.org/

Clock: VCO: 525 MHz, Core: 525 MHz, System: 131 MHz

RAM:   64 MB

Flash: 16 MB

NAND:  256 MiB

In:    serial

Out:   serial

Err:   serial

Net:   LAN9x18 (0x118a0000) detected at 0x24000000

MAC:   00:E0:22:FE:BD:0A

Hit any key to stop autoboot:  0

bfin> print

bootargs=root=/dev/mtdblock0 rw earlyprintk=serial,uart1,57600 console=tty0

console=ttyBF0,57600

bootcmd=run ramboot

bootdelay=5

baudrate=57600

loads_echo=1

rootpath=/romfs

hostname=bf548-ezkit

loadaddr=0x1000000

ubootfile=u-boot.ldr

update=tftp $(loadaddr) $(ubootfile);eeprom write $(loadaddr) 0x0 $(filesize)

addip=set bootargs $(bootargs)

ip=$(ipaddr):$(serverip):$(gatewayip):$(netmask):$(hostname):eth0:off

ramargs=set bootargs root=/dev/mtdblock0 rw earlyprintk=serial,uart1,57600

console=tty0 console=ttyBF0,57600

ramboot=tftp $(loadaddr) uImage;run ramargs;run addip;bootm

nfsargs=set bootargs root=/dev/nfs rw

nfsroot=$(serverip):$(rootpath),tcp,nfsvers=3

nfsboot=tftp $(loadaddr) vmImage;run nfsargs;run addip;bootm

flashboot=bootm 0x20100000

ethaddr=00:E0:22:FE:BD:0A

filesize=33860

fileaddr=1000000

gatewayip=192.168.0.1

netmask=255.255.255.0

ipaddr=10.100.4.50

serverip=10.100.4.174

stdin=serial

stdout=serial

stderr=serial

 

Environment size: 938/8188 bytes

bfin> tftp 0x2000000 linux

start Auto negotiation... (take ~2sec)

Auto negotiation complete, 100BaseTX, full duplex

TFTP from server 10.100.4.174; our IP address is 10.100.4.50

Filename 'linux'.

Load address: 0x2000000

Loading: #################################################################

         #################################################################

         #################################################################

         #################################################################

         #################################################################

         #################################################################

         #################################################################

         #################################################################

         #################################################################

         #################################################################

         #################################################################

         #################################################################

         #################################################################

         #################################################################

         #################################################################

         #################################################################

         #################################################################

         #################################################################

         #################################################################

         #################################################################

         #################################################################

         #################################

done

Bytes transferred = 7157458 (6d36d2 hex)

bfin> boote

Loading .text @ 0x00001000 (1739952 bytes)

Loading .rodata @ 0x001a9cc0 (496936 bytes)

Loading .init.rodata @ 0x002231e8 (156 bytes)

Loading __ksymtab @ 0x00223284 (18232 bytes)

Loading __ksymtab_gpl @ 0x002279bc (6896 bytes)

Loading __ksymtab_strings @ 0x002294ac (57300 bytes)

Loading __init_rodata @ 0x00237480 (172 bytes)

Loading __param @ 0x0023752c (1580 bytes)

Clearing .bss @ 0x00237b60 (87992 bytes)

Loading .data @ 0x0024d318 (101608 bytes)

Loading .init.text @ 0x00266000 (140324 bytes)

Loading .init.data @ 0x00288424 (28500 bytes)

Loading .init.setup @ 0x0028f378 (656 bytes)

Loading .initcall.init @ 0x0028f608 (616 bytes)

Loading .con_initcall.init @ 0x0028f870 (8 bytes)

Loading .init.ramfs @ 0x0028f878 (3744157 bytes)

Loading .text_l1 @ 0xffa00000 (5788 bytes)

sh_addr: FFA00000, p_paddr: 00621A15

Loading from: 0260D000 to 00621A15, size: 5788

Loading .data_l1 @ 0xff800000 (224 bytes)

sh_addr: FF800000, p_paddr: 006230B1

Loading from: 0260F000 to 006230B1, size: 224

## Starting application at 0x0027b4b0 ...

 

 

--- Michael Hennerich                                        2008-11-21 04:47:46

BF548 boots ok for me now.

Can you try again?

If you still seeing issues, then I assume this is an EZKIT HW issue similar to

 

BUG [#4615] kernel boot up fails with CONFIG_BFIN_KERNEL_CLOCK item on

 

-Michael

 

--- Mingquan Pan                                             2009-01-05 02:56:29

Yes, it is fixed on bf548 ezkit board.

 

--- Vivi Li                                                  2009-01-05 03:59:51

The fix for this bug will lead to another problem: BF561-EZKIT can't boot up

after re-program clocks.

 

For kernel version before 5728, it can boot up; after the patch, it fails as

bellow:

--

bfin> boote

Loading phdr 0 to 0x00001000 (1343192 bytes)

Loading phdr 1 to 0x00158790 (2342506 bytes)

Loading phdr 2 to 0x003945fa (6756 bytes)

Loading phdr 3 to 0x0039605e (192 bytes)

## Starting application at 0x001751f8 ...

--

 

--- Michael Hennerich                                        2009-01-09 07:47:43

Fixed on svn trunk.

 

On BF561 EBIU_SDGCTL bit 31 controls the SDRAM external data

path width, typically set 0 for a 32-bit bus width.

On other Blackfin derivatives this bit should be set by default.

 

-> Use WIDTH set by the initial bootloader

 

-Michael

 

--- Vivi Li                                                  2009-01-20 03:14:21

BF561-EZKIT can boot successfully after re-program clocks.

OK now. So close it.

 

 

 

    Files

    Changes

    Commits

    Dependencies

    Duplicates

    Associations

    Tags

 

File Name     File Type     File Size     Posted By

bf548.config    application/octet-stream    36104    Jie Zhang

Attachments

Outcomes