[#3839] u-boot crashes in bfin_EMAC_send during tftp without Network cable

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

[#3839] u-boot crashes in bfin_EMAC_send during tftp without Network cable

Submitted By: Michael Hennerich

Open Date

2008-01-17 06:57:22     Close Date

2008-01-17 08:33:19

Priority:

Medium High     Assignee:

Mike Frysinger

Category:

N/A     Fixed In Release:

N/A

Found In Release:

N/A     Status:

Closed

Board:

N/A     Processor:

N/A

Silicon Revision:

    Resolution:

Duplicated

Is the bug repeatable?:

N/A     

Summary: u-boot crashes in bfin_EMAC_send during tftp without Network cable

Details:

 

u-boot crashes in bfin_EMAC_send during tftp without Network cable present.

With Ethernet cable it never fails.

 

 

U-Boot 1.1.6-svn1099 (ADI-2008R1) (Jan 16 2008 - 11:05:05)

 

CPU:   ADSP bf537-0.2 (Detected Rev: 0.2)

Board: ADI BF537 stamp board

       Support: http://blackfin.uclinux.org/

Clock: VCO: 500 MHz, Core: 500 MHz, System: 100 MHz

RAM:   64 MB

Flash:  4 MB

In:    serial

Out:   serial

Err:   serial

Net:   Blackfin EMAC

MAC:   8A:B2:8D:D3:32:26

I2C:   ready

Hit any key to stop autoboot:  0

Link is down, please check your network connection

Using Blackfin EMAC device

TFTP from server 10.44.2.88; our IP address is 10.44.2.39

Filename 'uImage'.

Load address: 0x1000000

Loading: DCPLB exception outside of memory map at 0x5a400000

 

 

 

Ack! Something bad happened to the Blackfin!

 

SEQUENCER STATUS:

SEQSTAT: 00000026  IPEND: 3fc00c4  SYSCFG: 0032

  HWERRCAUSE: 0x0

  EXCAUSE   : 0x26

  physical IVG6 asserted : <0x03fc0788> { _evt_default + 0x0 }

  physical IVG7 asserted : <0x03fc0788> { _evt_default + 0x0 }

RETE: <0x02058580> /* unknown address */

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

RETX: <0x03fcaf04> { _bfin_EMAC_send + 0x70 }

RETS: <0x03fc82c0> { _NetSendUDPPacket + 0xd4 }

PC  : <0x03fc00c4> { _start + 0xc4 }

DCPLB_FAULT_ADDR: <0x5a5a5a5a> { ___smulsi3_highpart + 0x565cc86a }

ICPLB_FAULT_ADDR: <0x03fcaf04> { _bfin_EMAC_send + 0x70 }

 

PROCESSOR STATE:

R0 : 00000000    R1 : 03fe7260    R2 : 0000002a    R3 : 00000000

R4 : 00000019    R5 : 58022c0a    R6 : 03fe46b6    R7 : 00000043

P0 : 03fe728a    P1 : 03f601b0    P2 : 5a5a5a5a    P3 : 03fe4fec

P4 : 03fe9144    P5 : 03f5c000    FP : 00000035    SP : 03f5b628

LB0: 03fc7742    LT0: 03fc7740    LC0: 00000000

LB1: 00000001    LT1: 36478928    LC1: 00000000

B0 : ac2cdfde    L0 : 00000000    M0 : ff4def9f    I0 : 00000058

B1 : 7f2532d1    L1 : 00000000    M1 : 9cc9b7ed    I1 : 03fe728c

B2 : b458bbdf    L2 : 00000000    M2 : fedfae44    I2 : fe2be79e

B3 : 572774b4    L3 : 00000000    M3 : 2a8f3f51    I3 : f6aaf7be

A0.w: 20bc62f7   A0.x: 00000000   A1.w: 00009757   A1.x: 00000000

USP : e04ed705  ASTAT: 02001024

 

Hardware Trace:

   0 Target : <0x03fc04e4> { _bfin_panic + 0x0 }

     Source : <0x03fc05c6> { _trap_c + 0xa6 }

   1 Target : <0x03fc05c4> { _trap_c + 0xa4 }

     Source : <0x03fd2566> { _printf + 0x42 }

   2 Target : <0x03fd255c> { _printf + 0x38 }

     Source : <0x03fc08fc> { _serial_puts + 0x1c }

   3 Target : <0x03fc08f0> { _serial_puts + 0x10 }

     Source : <0x03fc08cc> { _serial_putc + 0x48 }

   4 Target : <0x03fc08b8> { _serial_putc + 0x34 }

     Source : <0x03fc08c4> { _serial_putc + 0x40 }

   5 Target : <0x03fc08b8> { _serial_putc + 0x34 }

     Source : <0x03fc08c4> { _serial_putc + 0x40 }

   6 Target : <0x03fc08b8> { _serial_putc + 0x34 }

     Source : <0x03fc08c4> { _serial_putc + 0x40 }

   7 Target : <0x03fc08b8> { _serial_putc + 0x34 }

     Source : <0x03fc08c4> { _serial_putc + 0x40 }

   8 Target : <0x03fc08b8> { _serial_putc + 0x34 }

     Source : <0x03fc08c4> { _serial_putc + 0x40 }

   9 Target : <0x03fc08b8> { _serial_putc + 0x34 }

     Source : <0x03fc08c4> { _serial_putc + 0x40 }

  10 Target : <0x03fc08b8> { _serial_putc + 0x34 }

     Source : <0x03fc08c4> { _serial_putc + 0x40 }

  11 Target : <0x03fc08b8> { _serial_putc + 0x34 }

     Source : <0x03fc08c4> { _serial_putc + 0x40 }

  12 Target : <0x03fc08b8> { _serial_putc + 0x34 }

     Source : <0x03fc08c4> { _serial_putc + 0x40 }

  13 Target : <0x03fc08b8> { _serial_putc + 0x34 }

     Source : <0x03fc08c4> { _serial_putc + 0x40 }

  14 Target : <0x03fc08b8> { _serial_putc + 0x34 }

     Source : <0x03fc08c4> { _serial_putc + 0x40 }

  15 Target : <0x03fc08b8> { _serial_putc + 0x34 }

     Source : <0x03fc08c4> { _serial_putc + 0x40 }

 

Please reset the board

 

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

 

Follow-ups

 

--- Mike Frysinger                                           2008-01-17 10:34:34

from my reading of the upstream u-boot list, u-boot itself has problems when eth

init fails (in the common code, not the driver code).  so i dont think this will

be fixed in u-boot-1.1.6; it'll require an upgrade to the latest (unreleased

yet) release.

 

dupe of [#3089]

 

 

 

    Files

    Changes

    Commits

    Dependencies

    Duplicates

    Associations

    Tags

 

File Name     File Type     File Size     Posted By

No Files Were Found

Attachments

    Outcomes