2010-09-04 21:45:33     Problem running images on BF518F-EZBRD

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

2010-09-04 21:45:33     Problem running images on BF518F-EZBRD

Andrew Bettino (UNITED STATES)

Message: 93143   

 

Hello,

 

I am having great difficulty getting any images loaded over TFTP to run on my BF518F board. I am able to load u-boot onto the device over UART. This u-boot seems to operate correctly and I am able to use tftp to load files onto the device.  I cannot boot a linux image or get a u-boot.bin image to load.

 

Here is what happens with the uImage

 

DHCP client bound to address 192.168.1.103                

bfin> tftp 0x1000000 uImage                               

Using Blackfin EMAC device                                

TFTP from server 192.168.1.100; our IP address is 192.168.1.103

Filename 'uImage'.                                        

Load address: 0x1000000                                   

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

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

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

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

         #

done

Bytes transferred = 3818692 (3a44c4 hex)

bfin> bootm 0x1000000

## Booting kernel from Legacy Image at 01000000 ...

   Image Name:   Linux-2.6.28.10-ADI-2009R1.1

   Created:      2010-08-31  13:19:09 UTC

   Image Type:   Blackfin Linux Kernel Image (gzip compressed)

   Data Size:    3818628 Bytes =  3.6 MB

   Load Address: 00001000

   Entry Point:  00190b80

   Verifying Checksum ... Bad Data CRC

ERROR: can't get kernel image!

bfin>

 

 

Here is what happens with u-boot.bin

 

Filename 'u-boot.bin'.

Load address: 0x1000000

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

done

Bytes transferred = 153428 (25754 hex)

bfin> go 0x1000000

## Starting application at 0x01000000 ...

 

 

Ack! Something bad happened to the Blackfin!

 

SEQUENCER STATUS:

SEQSTAT: 00000021  IPEND: 8008  SYSCFG: 0032

  HWERRCAUSE: 0x0: undef

  EXCAUSE   : 0x21: undef inst

  physical IVG15 asserted : <0x03fa0558> { _evt_default + 0x0 }

RETE: <0x3aae3e57> { ___smulsi3_highpart + 0x36b2b8a7 }

RETN: <0xffb00fec> { __etext_l1 + 0x100fe4 }

RETX: <0x01001404> /* unknown address */

RETS: <0x01000072> /* unknown address */

RETI: <0x03fa00da> { _start + 0xda }

DCPLB_FAULT_ADDR: <0xffe01004> { __etext_l1 + 0x400ffc }

ICPLB_FAULT_ADDR: <0x01001404> /* unknown address */

 

PROCESSOR STATE:

R0 : ffa00000    R1 : 010000e0    R2 : 00000104    R3 : 20000000

R4 : 03fa0000    R5 : 01000000    R6 : 00000000    R7 : 01001404

P0 : 03f3ee41    P1 : 00000428    P2 : ffe01004    P3 : ffa00000

P4 : 01000000    P5 : 03f3ff80    FP : 03f3f684    SP : ffb00f18

LB0: 03fb8560    LT0: 03fb8554    LC0: 00000000

LB1: 03fb2f30    LT1: 03fb2f2e    LC1: 00000000

B0 : ffb00400    L0 : 00000000    M0 : 43b0b4cb    I0 : 01000040

B1 : 00000000    L1 : 00000000    M1 : e5584b9b    I1 : 03fc8baa

B2 : 00000000    L2 : 00000000    M2 : 9085c21f    I2 : 00b50ef2

B3 : 00000000    L3 : 00000000    M3 : d4c5104e    I3 : a28b2aba

A0.w: 00023069   A0.x: 00000000   A1.w: 000001a4   A1.x: 00000000

USP : ffb00ffc  ASTAT: 00000020

 

Hardware Trace:

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

     Source : <0x03fa0cb4> { _trap_c + 0x138 }

   1 Target : <0x03fa0ca8> { _trap_c + 0x12c }

     Source : <0x03fa0b98> { _trap_c + 0x1c }

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

     Source : <0x03fa04fc> { _trap + 0x60 }

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

     Source : <0x0100006e> /* unknown address */

   4 Target : <0x0100004e> /* unknown address */

     Source : <0x01000044> /* unknown address */

   5 Target : <0x01000020> /* unknown address */

     Source : <0x010000de> /* unknown address */

   6 Target : <0x010000dc> /* unknown address */

     Source : <0x0100001c> /* unknown address */

   7 Target : <0x01000000> /* unknown address */

     Source : <0x03fb305a> { _do_go_exec + 0x26 }

   8 Target : <0x03fb3056> { _do_go_exec + 0x22 }

     Source : <0x03fa1266> { _icache_disable + 0xe }

   9 Target : <0x03fa1258> { _icache_disable + 0x0 }

     Source : <0x03fb3052> { _do_go_exec + 0x1e }

  10 Target : <0x03fb3052> { _do_go_exec + 0x1e }

     Source : <0x03fa12a6> { _dcache_disable + 0xe }

  11 Target : <0x03fa1298> { _dcache_disable + 0x0 }

     Source : <0x03fb304e> { _do_go_exec + 0x1a }

  12 Target : <0x03fb304c> { _do_go_exec + 0x18 }

     Source : <0x03fa1276> { _icache_status + 0xe }

  13 Target : <0x03fa1268> { _icache_status + 0x0 }

     Source : <0x03fb3048> { _do_go_exec + 0x14 }

  14 Target : <0x03fb3046> { _do_go_exec + 0x12 }

     Source : <0x03fa1286> { _dcache_status + 0xe }

  15 Target : <0x03fa1278> { _dcache_status + 0x0 }

     Source : <0x03fb3042> { _do_go_exec + 0xe }

 

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

 

 

 

 

Any idea what could be causing these errors?

QuoteReplyEditDelete

 

 

2010-09-04 23:46:19     Re: Problem running images on BF518F-EZBRD

Mike Frysinger (UNITED STATES)

Message: 93144   

 

run mtest.  are you using a release image or your own ?

QuoteReplyEditDelete

 

 

2010-09-05 00:43:10     Re: Problem running images on BF518F-EZBRD

Andrew Bettino (UNITED STATES)

Message: 93145   

 

I have attempted to use images that I have built and also tried pre-built images that came with the dev board. I have not had success with any of these. I have run memtest for many minutes and it has not printed out any errors. I'm assuming it prints out errors as they occur.

QuoteReplyEditDelete

 

 

2010-09-06 00:30:29     Re: Problem running images on BF518F-EZBRD

Mike Frysinger (UNITED STATES)

Message: 93161   

 

yes, it should print errors as soon as it finds one

 

when you tftp the u-boot.bin over, do a crc on it and see if it matches the crc as the file on your tftp server

 

cant say ive seen any errors like this on the bf518f-ezbrd before ...

QuoteReplyEditDelete

 

 

2010-09-06 11:07:30     Re: Problem running images on BF518F-EZBRD

Andrew Bettino (UNITED STATES)

Message: 93184   

 

It looks like they don't match. I ran crc32 on the blackfin with the sytanx below. I also just ran crc32 on my machine. I believe this is the correct way to do it?

 

On blackfin:

 

Bytes transferred = 153428 (25754 hex)

bfin> crc32 0x1000000 $(filesize)                                             

CRC32 for 01000000 ... 01025753 ==> e911082c                                  

 

On my machine:

 

andy@andy-laptop:/tftpboot$ crc32 u-boot.bin

92e8d318

 

Do you think there is still some issue with the memory? Here is memory dump from 0x1000000 from the blackfin followed by u-boot.bin in a hex editor. It looks to be the same data.

 

01000000: 0fece10e ffb0e14e 3e106190 36216001    ....N....a.>.`!6             

01000010: 36313629 3c013639 31fc3c19 0060e300    )61696.<.<.1..`.             

01000020: 0020e101 03fae141 0000e104 03fae144    .. .A.......D...             

01000030: 535852e1 082c600e 60061833 e1436003    .RXS.`,.3..`.`C.             

01000040: 099d2000 60001805 004ce300 e1002015    . .....`..L.. ..             

       

 

00000000: 0ee1 ec0f 4ee1 b0ff 9061 103e 0160 2136  ....N....a.>.`!6

00000010: 2936 3136 3936 013c 193c fc31 00e3 6000  )61696.<.<.1..`.

00000020: 01e1 2000 41e1 fa03 04e1 0000 44e1 fa03  .. .A.......D...

00000030: e152 5853 0e60 2c08 3318 0660 0360 43e1  .RXS.`,.3..`.`C.

00000040: 0020 9d09 0518 0060 00e3 4c00 1520 00e1  . .....`..L.. ..

QuoteReplyEditDelete

 

 

2010-09-06 11:17:10     Re: Problem running images on BF518F-EZBRD

Mike Frysinger (UNITED STATES)

Message: 93186   

 

looking at the first 0x50 bytes isnt the same as all 0x25754 bytes

 

you could try loading some 16KB files into L1 data and see if it transfers fine

 

assuming you have a big chunk of programmed flash, you could do:

cp.b 0x20000000 0 <some big size>

cmp.b 0x20000000 0 <some big size>

 

what rev of the bf518f-ezbrd do you have ?  look at the silkscreen info and the BOM sticker.

QuoteReplyEditDelete

 

 

2010-09-06 13:03:43     Re: Problem running images on BF518F-EZBRD

Andrew Bettino (UNITED STATES)

Message: 93188   

 

According to the silkscreen I have the Rev 0.2 board. I'll run some more tests and post the results.

QuoteReplyEditDelete

 

 

2010-09-06 16:59:42     Re: Problem running images on BF518F-EZBRD

Andrew Bettino (UNITED STATES)

Message: 93190   

 

When I try to do the following command I get a failure. Would you expect this to work? It looks like it should be in the memory range for the flash.

 

bfin> cp.b 0x20000000 0 1000000

 

 

Ack! Something bad happened to the Blackfin!

 

SEQUENCER STATUS:

SEQSTAT: 0000c026  IPEND: 8030  SYSCFG: 0032

  HWERRCAUSE: 0x3: external memory addressing error

  EXCAUSE   : 0x26: dcplb miss

  physical IVG15 asserted : <0x03fa0558> { _evt_default + 0x0 }

RETE: <0x3aac3e77> { ___smulsi3_highpart + 0x36b0b8c7 }

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

RETX: <0x03fa9fe2> { _do_mem_cp + 0x192 }

RETS: <0x03fa9f4c> { _do_mem_cp + 0xfc }

RETI: <0x03fa9fe2> { _do_mem_cp + 0x192 }

DCPLB_FAULT_ADDR: <0x20400000> { ___smulsi3_highpart + 0x1c447a50 }

ICPLB_FAULT_ADDR: <0x03fa9fe2> { _do_mem_cp + 0x192 }

 

 

 

PROCESSOR STATE:

R0 : 00000004    R1 : ffa00000    R2 : 00000000    R3 : 00000000

R4 : 00000000    R5 : 00000000    R6 : 00000001    R7 : 00bfffff

P0 : 03fc1a5c    P1 : 03f3f691    P2 : 00000001    P3 : 20400000

P4 : 00400000    P5 : 03f3ff80    FP : 20000000    SP : 03f3f158

LB0: 03fb302c    LT0: 03fb302a    LC0: 00000000

LB1: 03fafc5a    LT1: 03fafc4c    LC1: 00000000

B0 : ffb00400    L0 : 00000000    M0 : 4390b4cb    I0 : ffb00540

B1 : 00000000    L1 : 00000000    M1 : e5584b9b    I1 : 03fcac10

B2 : 00000000    L2 : 00000000    M2 : 9085c31d    I2 : 48b50ef2

B3 : 00000000    L3 : 00000000    M3 : d485544e    I3 : a28b2aba

A0.w: 00004571   A0.x: 00000000   A1.w: 00000165   A1.x: 00000000

USP : ffb00ffc  ASTAT: 00000002

 

Hardware Trace:

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

     Source : <0x03fa05ae> { _evt_default + 0x56 }

   1 Target : <0x03fa0558> { _evt_default + 0x0 }

     Source : <0x03fa0556> { _trap + 0xba }

   2 Target : <0x03fa0500> { _trap + 0x64 }

     Source : <0x03fa0ca6> { _trap_c + 0x12a }

   3 Target : <0x03fa0c52> { _trap_c + 0xd6 }

     Source : <0x03fa0c3a> { _trap_c + 0xbe }

   4 Target : <0x03fa0c16> { _trap_c + 0x9a }

     Source : <0x03fa0bda> { _trap_c + 0x5e }

   5 Target : <0x03fa0bc4> { _trap_c + 0x48 }

     Source : <0x03fa0bbe> { _trap_c + 0x42 }

   6 Target : <0x03fa0bac> { _trap_c + 0x30 }

     Source : <0x03fa0cca> { _trap_c + 0x14e }

   7 Target : <0x03fa0cb8> { _trap_c + 0x13c }

     Source : <0x03fa0b92> { _trap_c + 0x16 }

   8 Target : <0x03fa0b7c> { _trap_c + 0x0 }

     Source : <0x03fa04fc> { _trap + 0x60 }

   9 Target : <0x03fa049c> { _trap + 0x0 }

     Source : <0x03fa9fe0> { _do_mem_cp + 0x190 }

  10 Target : <0x03fa9fe0> { _do_mem_cp + 0x190 }

     Source : <0x03fa9fd8> { _do_mem_cp + 0x188 }

  11 Target : <0x03fa9fd6> { _do_mem_cp + 0x186 }

     Source : <0x03fa9fce> { _do_mem_cp + 0x17e }

  12 Target : <0x03fa9fca> { _do_mem_cp + 0x17a }

     Source : <0x03fa9ff0> { _do_mem_cp + 0x1a0 }

  13 Target : <0x03fa9fe0> { _do_mem_cp + 0x190 }

     Source : <0x03fa9fd8> { _do_mem_cp + 0x188 }

  14 Target : <0x03fa9fd6> { _do_mem_cp + 0x186 }

     Source : <0x03fa9fce> { _do_mem_cp + 0x17e }

  15 Target : <0x03fa9fca> { _do_mem_cp + 0x17a }

     Source : <0x03fa9ff0> { _do_mem_cp + 0x1a0 }

 

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

QuoteReplyEditDelete

 

 

2010-09-06 17:01:27     Re: Problem running images on BF518F-EZBRD

Mike Frysinger (UNITED STATES)

Message: 93192   

 

async memory is 4 banks of 1 meg.  it isnt 16 meg.

 

QuoteReplyEditDelete

 

 

2010-09-06 17:23:01     Re: Problem running images on BF518F-EZBRD

Andrew Bettino (UNITED STATES)

Message: 93193   

 

When I do the copy and compare on just 1 Meg is succeeds

 

bfin> cp.b 0x20000000 0 0xfffff

bfin> cmp.b 0x20000000 0 0xfffff

Total of 1048575 bytes were the same

QuoteReplyEditDelete

 

 

2010-09-06 21:43:03     Re: Problem running images on BF518F-EZBRD

Andrew Bettino (UNITED STATES)

Message: 93197   

 

Well the problem seems to be with the prebuilt UART bootloader 2009R1.1. I downloaded the latest SVN snapshot and this one worked fine. I'm not sure what the differences are or why no one else seems to have this issue. Thanks for your help.

Attachments

    Outcomes