2010-01-14 09:43:00     uClinux problems after SVN update

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

2010-01-14 09:43:00     uClinux problems after SVN update

Tom Hoover (UNITED STATES)

Message: 84580   

 

Greetings All,

 

 

 

I've been developing with svn trunk for a couple of months now with no problems. About a week ago I did an update and booting broke.

 

I'm in sync with the tools knowing that there can be issues there. The console output is below. It just hangs after the 'starting kernel' message.

 

I am working with both BF537 abd BF536 based boards. Both projects were just fine until last Thursday. Any reports of problems? I didn't see any in the forums.

 

We use SPI flash, but that's been fine for months and months.

 

My u-boot is older, could that be a problem?

 

Debuggin ideas also welcome.

 

Thanks,

 

Tom

 

------------------------------ console output below -------------------

 

 

 

U-Boot 1.1.6 (ADI-2008R1.5) (Dec 29 2009 - 15:25:49)                           

                                                                               

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

Board: vip808                                                                                    

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

RAM:   Serial Port initialized with Baud rate = 57600                          

SDRAM attributes:                                                              

tRCD 3 SCLK Cycles,tRP 3 SCLK Cycles,tRAS 6 SCLK CyclestWR 2 SCLK Cycles,CAS La

SDRAM Begin: 0x0                                                               

Bank size = 32 MB                                                              

32 MB                                                                          

*** Warning - bad CRC, using default environment                               

                                                                               

In:    serial                                                                  

Out:   serial                                                                  

Err:   serial                                                                  

Net:   Blackfin EMAC                                                           

MAC:   02:80:AD:20:31:42                                                       

Hit any key to stop autoboot:  0                                               

                                                                               

EEPROM @0x0 read: addr 00980000  off 30000  count 5050368 ... .................e

## Booting image at 00980000 ...                                               

   Image Name:   bf537-2.6.32.3-ADI-2010R1-pre-sv                              

   Created:      2010-01-14  14:22:05 UTC                                      

   Image Type:   Blackfin Linux Kernel Image (gzip compressed)                 

   Data Size:    3762334 Bytes =  3.6 MB                                       

   Load Address: 00001000                                                      

   Entry Point:  0019774c                                                      

   Verifying Checksum ... OK                                                   

   Uncompressing Kernel Image ... OK                                           

Starting Kernel at = 19774c                                                    

 

QuoteReplyEditDelete

 

 

2010-01-14 13:04:57     Re: uClinux problems after SVN update

Robin Getz (UNITED STATES)

Message: 84584   

 

Tom:

 

https://docs.blackfin.uclinux.org/doku.php?id=linux-kernel:debug:post_mortem

 

-Robin

QuoteReplyEditDelete

 

 

2010-01-14 13:42:40     Re: uClinux problems after SVN update

Mike Frysinger (UNITED STATES)

Message: 84585   

 

you probably need to change your default bootargs

QuoteReplyEditDelete

 

 

2010-02-15 10:22:29     Re: uClinux problems after SVN update

Tom Hoover (UNITED STATES)

Message: 86114   

 

Sorry for the late response.

 

Yes - a combination of changing bootargs and setting early printk fixed this . Thanks.

Attachments

    Outcomes