2009-03-17 14:05:57     trunk for BF548-EZKIT, no workaround for anomly 05000448?

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

2009-03-17 14:05:57     trunk for BF548-EZKIT, no workaround for anomly 05000448?

Dong Ye (UNITED STATES)

Message: 71127   

 

Hi,

 

Try to build trunk for BF548-EZKIT, choose silicon revision 0.1. Got the following compile error:

 

arch/blackfin/mach-common/arch_checks.c:72:3: error: #error You are using a part with anomaly 05000448, this issue causes random memory read/write failures - that means random crashes.

 

 

Comment out the aforementioned conditional compilation block. Compile OK. Yet get kernel panic when booting the uImage.

 

## Booting image at 01000000 ...

   Image Name:   Linux-2.6.28.7-ADI-2009R1-pre-sv

   Created:      2009-03-17  17:59:25 UTC

   Image Type:   Blackfin Linux Kernel Image (gzip compressed)

   Data Size:    5358365 Bytes =  5.1 MB

   Load Address: 00001000

   Entry Point:  002da6b4

   Verifying Checksum ... OK

   Uncompressing Kernel Image ... OK

Starting Kernel at = 2da6b4

Linux version 2.6.28.7-ADI-2009R1-pre-svn6198 (dongu@owl) (gcc version 4.1.2 (ADI svn)) #18 Tue Mar 17 13:59:14 EDT 2009

console [early_BFuart0] enabled

early printk enabled on early_BFuart0

Board Memory: 64MB

Kernel Managed Memory: 64MB

Memory map:

  fixedcode = 0x00000400-0x00000490

  text      = 0x00001000-0x001ec3c0

  rodata    = 0x001ec3c0-0x0028dfd0

  bss       = 0x0028dfd0-0x002a779c

  data      = 0x002a779c-0x002c4000

    stack   = 0x002c2000-0x002c4000

  init      = 0x002c5000-0x009eb000

  available = 0x009eb000-0x03dff000

  DMA Zone  = 0x03e00000-0x04000000

Hardware Trace Active and Enabled

Boot Mode: 3

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

Compiled for ADSP-BF548 Rev 0.1

Kernel panic - not syncing: You can't run on this processor due to 05000448

 

Comments?

 

Thanks,

Dong

QuoteReplyEditDelete

 

 

2009-03-17 14:10:32     Re: trunk for BF548-EZKIT, no workaround for anomly 05000448?

Mike Frysinger (UNITED STATES)

Message: 71129   

 

read the anomaly sheet please

QuoteReplyEditDelete

 

 

2009-03-17 14:31:59     Re: trunk for BF548-EZKIT, no workaround for anomly 05000448?

Dong Ye (UNITED STATES)

Message: 71133   

 

Mike,

 

Thanks a lot for your time.

 

Maybe I asked a wrong question. Yes the anomly sheet indicates that there is no workaround available.

Then how should I configure the kernel in order to run the resulting image on a BF548-EZKIT?

 

I tried all the silicion revision options presented. None of them succeds (choosing "none" leads to compile error; choosing all others leads to "Kernel panic - not syncing: You can't run on this processor due to 05000448").

 

The 2008R1.5 release worked.

 

Dong

QuoteReplyEditDelete

 

 

2009-03-17 14:35:04     Re: trunk for BF548-EZKIT, no workaround for anomly 05000448?

Mike Frysinger (UNITED STATES)

Message: 71134   

 

there is no configure option.  you need to delete the panic() line from the source code manually.  doing this indicates you understand that things may randomly crash at any time and there's nothing in software that can be done to "fix" it.

 

anomaly 448 wasnt known at the time of the 2008R1.5 release ... otherwise the panic() message would have been there too.

Attachments

    Outcomes