2008-07-09 10:04:43     Booting Unsuccesful

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

2008-07-09 10:04:43     Booting Unsuccesful

Appalayagari Sreedhar (INDIA)

Message: 58550   

 

Hi,

 

I am facing problem while booting from Flash. BF533 BMODE pins are connected to :00

 

I have integrated the crytographic routines for secure booting of my uImage in u-boot.

 

I am reading the entire uImage from Flash into the Sdram memory and do the decryption then i am doing the CRC check and uncompressing from sdram similar like

 

tftp <sdram memory location> uImage;bootm

 

I have compared the decrypted uImage with the original uImage bin file matches.

 

i am getting the following error.

 

U-Boot 1.1.6-svn (ADI-2007R1) (Jul  7 2008 - 23:20:04)

 

CPU:   ADSP BF533 Rev.: 0.5

Board: ADI BF533 NP2x00 board

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

       Support: http://analog.com/ (&&) http://jasmin-infotech.com/

Clock: VCO: 594 MHz, Core: 594 MHz, System: 118 MHz

SDRAM: 64 MB

FLASH:   8 MB

*** Warning - bad CRC, using default environment

 

In:    serial

Out:   serial

Err:   serial

I2C:   ready

Hit any key to stop autoboot:  0

## Booting image at 20040000 ...

   Image Name:   uClinux Kernel and ext2

   Created:      2008-07-09  10:53:03 UTC

   Image Type:   Blackfin Linux Kernel Image (gzip compressed)

   Data Size:    5276777 Bytes =  5 MB

   Load Address: 00300000

   Entry Point:  00300000

   Verifying Checksum ... crc32 = 0x615b2738

OK

   Uncompressing Kernel Image ... OK

Starting Kernel at = 300000

Linux version 2.6.19.3-ADI-2007R1-svn (sreedhar@linux-hms-jasmin) (gcc version 4

.1.1 (ADI 07R1)) #252 Wed Jul 9 14:04:01 IST 2008

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

Compiled for ADSP-BF533 Rev. 0.5

Blackfin uClinux support by http://blackfin.uclinux.org/

Processor Speed: 594 MHz core clock and 118 Mhz System Clock

Board Memory: 64MB

Kernel Managed Memory: 64MB

Memory map:

  text      = 0x00300000-0x00413ea8

  init      = 0x00414000-0x00422cd4

  data      = 0x00428954-0x00460430

  stack     = 0x0042a000-0x0042c000

  bss       = 0x00460430-0x0058e244

  available = 0x0058e244-0x02f00000

  rootfs    = 0x02f00000-0x03f00000

  DMA Zone  = 0x03f00000-0x04000000

Instruction Cache Enabled

Data Cache Enabled (write-back)

Hardware Trace Enabled

Built 1 zonelists.  Total pages: 11938

Kernel command line: root=/dev/mtdblock0 rw,console=ttyBF0,57600

Configuring Blackfin Priority Driven Interrupts

PID hash table entries: 256 (order: 8, 1024 bytes)

Dentry cache hash table entries: 8192 (order: 3, 32768 bytes)

Inode-cache hash table entries: 4096 (order: 2, 16384 bytes)

Physical pages: 2f00

Memory available: 41856k/61277k RAM, (59k init code, 1103k kernel code, 1207k da

ta, 1024k dma)

Blackfin Scratchpad data SRAM: 4 KB

Blackfin DATA_A SRAM: 16 KB

Blackfin DATA_B SRAM: 16 KB

Blackfin Instruction SRAM: 64 KB

Security Framework v1.0.0 initialized

Capability LSM initialized

Mount-cache hash table entries: 512

NET: Registered protocol family 16

Blackfin GPIO Controller

Blackfin DMA Controller

ezkit_init(): registering device resources

Data access CPLB miss

- Used by the MMU to signal a CPLB miss on a data access.

 

 

 

 

Can anyone suggest me where i am doing wrong and help me to solve this problem.

 

Best Regards,Sreedhar

QuoteReplyEditDelete

 

 

2008-07-09 11:48:19     Re: Booting Unsuccesful

Robin Getz (UNITED STATES)

Message: 58565   

 

Sreedhar:

 

Are you asking us to fix a bug in code that you modified (that was working before), without sharing it? I can't help with that.

 

If you revert your changes, does it work?

 

-Robin

QuoteReplyEditDelete

 

 

2008-07-09 15:04:47     Re: Booting Unsuccesful

Appalayagari Sreedhar (INDIA)

Message: 58571   

 

Hi Robin,

 

I did not corrected anything.

 

I am facing the booting problem. which i have mentioned, I will be encryting the uImage separetely.

 

I have integrated the decrytion routine in the bootm code of u-boot,  I will read the data from the flash into the CFG_LOAD_ADDR and decrypts and then starts booting from the loaction CFG_LOAD_ADDR.

 

I am facing the problem which i have mentioned in my previous mail.

 

when i placed some delay before and after the Flash read the booting is succesful.

 

does this required? is i am doing something wrong? please guide me.

 

Best Regards,Sreedhar.

QuoteReplyEditDelete

 

 

2008-07-14 22:08:19     Re: Booting Unsuccesful

Mike Frysinger (UNITED STATES)

Message: 58777   

 

have you verified that booting the kernel without any of your encryption pieces works (or fails) ?

 

you're also booting an old kernel (2007R1) ... the kernel debug output has been greatly improved, so you should be able to get a hardware traceback which would assist in debugging

 

otherwise, you could try using kgdb or jtag to figure out where the crash is coming from

QuoteReplyEditDelete

Attachments

    Outcomes