2010-03-18 04:33:29     Custom board : uboot panics after giving any command on console.

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

2010-03-18 04:33:29     Custom board : uboot panics after giving any command on console.

Kanwar Saad (PAKISTAN)

Message: 87399   

 

Hi. i have made my own custom blackfin bf537 board. i have ported latest u-boot on my board according to the instructions given on koop. when i run it from jtag it comes to the console with bfin> prompt. but when enter any thing on console it gives me an error dump as shown below.

 

One thing is that i have not configured EBIU of blackfin for flash yet. thanks in advance for ur help.

 

 

 

�������������>>0>��0>��H[뫅�5

 

                             X

 

FabcdeGabeHabc

 

X

 

I

 

X>

 

Early:start.S: Init Registers

 

Early:start.S: Find ourselves

 

Early:start.S: Lower to 15

 

Early: Board init flash

 

Early: Init CPLB tables

 

Early: Exceptions setup

 

Early: Turn on ICACHE

 

Early: Turn on DCACHE

 

Early: Init global data

 

Early: IRQ init

 

Early: Environment init

 

Early: Baudrate init

 

Early: Serial init

 

Early: Console init flash

 

Early: End of early debugging

 

 

 

 

 

U-Boot 2009.11.1-svn2236 (ADI-2010R1-pre) (Mar 18 2010 - 01:06:25)

 

 

 

CPU:   ADSP bf537-0.3 (Detected Rev: 0.3) (bypass boot)

 

Board: ADI BF537 Cow board

 

       Support: nothing

 

Clock: VCO: 600 MHz, Core: 600 MHz, System: 120 MHz

 

RAM:   128 MB

 

Flash: ## Unknown FLASH on Bank 1 - Size = 0x31dc596f = -1762656256 MB

 

797.8 MB

 

ICPLB exception outside of memory map at 0xaf400000

 

Ack! Something bad happened to the Blackfin!

 

 

 

SEQUENCER STATUS:

 

SEQSTAT: 0006202c  IPEND: 0032  SYSCFG: 0032

 

  HWERRCAUSE: 0x18: raise 5 instruction

 

  EXCAUSE   : 0x2c: icplb miss

 

RETE: <0x07f80000> { _start + 0x0 }

 

RETN: <0x07f1fd30> /* unknown address */

 

RETX: <0xaf6d01a2> { ___smulsi3_highpart + 0xa772f23e }

 

RETS: <0x07f808c8> { _trap_c + 0x1a0 }

 

RETI: <0x07f809ec> { _exception_to_level5 + 0x0 }

 

DCPLB_FAULT_ADDR: <0x07fb4c30> { ___smulsi3_highpart + 0x13ccc }

 

ICPLB_FAULT_ADDR: <0xaf6d01a2> { ___smulsi3_highpart + 0xa772f23e }

 

 

 

PROCESSOR STATE:

 

R0 : 07f1fd60    R1 : 00000010    R2 : 00000005    R3 : 00000000

 

R4 : ffffffff    R5 : 00000040    R6 : 00000000    R7 : 000009b0

 

P0 : ffe02108    P1 : 07faf1b8    P2 : af6d01a2    P3 : 07f1ff80

 

P4 : 07fb24e8    P5 : 07f1fd60    FP : 07fada44    SP : ffb00f18

 

LB0: 07f878e4    LT0: 07f878e4    LC0: 00000000

 

LB1: 07f86eae    LT1: 07f86eac    LC1: 00000000

 

B0 : 65d14bdd    L0 : 00000000    M0 : a97f1a59    I0 : 00000008

 

B1 : e3807f7c    L1 : 00000000    M1 : 231e7afd    I1 : 07fa23c6

 

B2 : 6b5fb7ee    L2 : 00000000    M2 : 0b121354    I2 : a03f5dfe

 

B3 : 559e6eeb    L3 : 00000000    M3 : b10447fc    I3 : 389f7bdd

 

A0.w: 0000005f   A0.x: 00000000   A1.w: 0000005f   A1.x: 00000000

 

USP : a19773f9  ASTAT: 00001004

 

 

 

Hardware Trace:

 

   0 Target : <0x07f8075e> { _trap_c + 0x36 }

 

     Source : <0x07f80756> { _trap_c + 0x2e }

 

   1 Target : <0x07f80750> { _trap_c + 0x28 }

 

     Source : <0x07f80742> { _trap_c + 0x1a }

 

   2 Target : <0x07f80728> { _trap_c + 0x0 }

 

     Source : <0x07f80948> { _trap + 0x6c }

 

   3 Target : <0x07f808dc> { _trap + 0x0 }

 

     Source : <0x07f808c6> { _trap_c + 0x19e }

 

   4 Target : <0x07f808b6> { _trap_c + 0x18e }

 

     Source : <0x07f808b0> { _trap_c + 0x188 }

 

   5 Target : <0x07f808ae> { _trap_c + 0x186 }

 

     Source : <0x07f80748> { _trap_c + 0x20 }

 

   6 Target : <0x07f80728> { _trap_c + 0x0 }

 

     Source : <0x07f80a74> { _exception_to_level5 + 0x88 }

 

   7 Target : <0x07f809ec> { _exception_to_level5 + 0x0 }

 

     Source : <0x07f809ea> { _trap + 0x10e }

 

   8 Target : <0x07f8094c> { _trap + 0x70 }

 

     Source : <0x07f808da> { _trap_c + 0x1b2 }

 

   9 Target : <0x07f808d4> { _trap_c + 0x1ac }

 

     Source : <0x07f808b4> { _trap_c + 0x18c }

 

  10 Target : <0x07f808ae> { _trap_c + 0x186 }

 

     Source : <0x07f80748> { _trap_c + 0x20 }

 

  11 Target : <0x07f80728> { _trap_c + 0x0 }

 

     Source : <0x07f80948> { _trap + 0x6c }

 

  12 Target : <0x07f808dc> { _trap + 0x0 }

 

     Source : <0x07f812f8> { _malloc + 0x3a4 }

 

  13 Target : <0x07f812d2> { _malloc + 0x37e }

 

     Source : <0x07f80d0c> { _sbrk + 0x30 }

 

  14 Target : <0x07f80d0c> { _sbrk + 0x30 }

 

     Source : <0x07f80d08> { _sbrk + 0x2c }

 

  15 Target : <0x07f80cdc> { _sbrk + 0x0 }

 

     Source : <0x07f812ce> { _malloc + 0x37a }

 

 

 

### ERROR ### Please RESET the board ###

 

QuoteReplyEditDelete

 

 

2010-03-18 04:35:52     Re: Custom board : uboot panics after giving any command on console.

Kanwar Saad (PAKISTAN)

Message: 87400   

 

U-boot version is  u-boot.2009.11.1

QuoteReplyEditDelete

 

 

2010-03-18 04:37:59     Re: Custom board : uboot panics after giving any command on console.

Kanwar Saad (PAKISTAN)

Message: 87401   

 

do not worry about garbage in the start. my SCLK was not stable there.

QuoteReplyEditDelete

 

 

2010-03-18 11:24:49     Re: Custom board : uboot panics after giving any command on console.

Mike Frysinger (UNITED STATES)

Message: 87407   

 

are you sure you correctly followed the directions ?  usually this error only occurs when people didnt load things properly -- i.e. they didnt clear the bss.

QuoteReplyEditDelete

 

 

2010-03-19 03:19:48     Re: Custom board : uboot panics after giving any command on console.

Kanwar Saad (PAKISTAN)

Message: 87472   

 

yes you may be right. the command used to clear the bss section given there on koop is not running on my gdb.

 

(gdb) call memset(&_bss_start, 0, &_bss_end - &_bss_start)

 

it gives me the the following error

 

'No symbol table is loaded. use the "FILE" command'.

 

I cant find any any way to load the symbol table. also i've tried to find absolute addresses of _bss_start and _bss_end from memory map file generated when u-boot compiles but there were no such labels. the only one's i find were __bss_vma and __bss_len.

 

I saw a section in start.S file of u-boot which clears the bss section, then why should we have to explicitly clear it since we know that start.S file executes first.

QuoteReplyEditDelete

 

 

2010-03-19 06:23:48     Re: Custom board : uboot panics after giving any command on console.

Kanwar Saad (PAKISTAN)

Message: 87475   

 

thanks, it worked. Initializing bss solved it. I think i have to learn gdb again

QuoteReplyEditDelete

 

 

2010-03-19 06:28:10     Re: Custom board : uboot panics after giving any command on console.

Kanwar Saad (PAKISTAN)

Message: 87476   

 

but as mentioned on koop the _bss_start and _bss_end are not in the new u-boot. edit it to the following command instead.

 

(gdb) call memset(&_bss_vma, 0, &_bss_end).

QuoteReplyEditDelete

 

 

2010-03-19 12:20:40     Re: Custom board : uboot panics after giving any command on console.

Mike Frysinger (UNITED STATES)

Message: 87483   

 

if by "new" you mean "current trunk", then that is probably correct.  the documentation reflects the latest release (2009R1.1).

QuoteReplyEditDelete

 

 

2010-03-20 09:55:01     Re: Custom board : uboot panics after giving any command on console.

Kanwar Saad (PAKISTAN)

Message: 87520   

 

now we are stuck on ethernet. after reaching the console, when anything related to ethernet is executed we get the error.

 

Ethernet: tx error

 

Ethernet: tx time out

 

Ethernet: tx time out

 

Ethernet: tx time out

 

Ethernet: tx time out

 

Ethernet: tx time out

 

...

 

...

 

....

 

and then we get a PANIC and get a random error dump.

 

 

 

any idea what can be the problem??

QuoteReplyEditDelete

 

 

2010-03-20 13:17:12     Re: Custom board : uboot panics after giving any command on console.

Mike Frysinger (UNITED STATES)

Message: 87521   

 

you really should start new threads for new issues ...

 

at any rate, verify you configured your Blackfin MAC settings correctly (RMII vs MII) and then make sure the actual pins to the PHY are correct.  i'm assuming the board is actually plugged in with the right cable to a network device.

 

the bfin_mac.c driver itself has verbose debug options in it you can enable via the normal #define DEBUG method.

Attachments

    Outcomes