2008-05-29 04:49:10     Booting Fails if ROMFS Size is increased?

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

2008-05-29 04:49:10     Booting Fails if ROMFS Size is increased?

Appalayagari Sreedhar (INDIA)

Message: 56401   

 

Hi,

 

Custom board which i am working has BF533 64MB sdram.

 

When i increase the Blocks = 16384 (16MB romfs) I am getting BAD CRC DATA. when the kernel starts booting from Flash.

 

When i decreased the BLOCKS = 12288 (12 MB) the entire application booted properly from flash.

 

Is anything i am missing to check or anything i am doing wrong?

 

Thank you.

 

Sreedhar.

QuoteReplyEditDelete

 

 

2008-05-29 11:43:05     Re: Booting Fails if ROMFS Size is increased?

Mike Frysinger (UNITED STATES)

Message: 56413   

 

post the actual commands you are using to load/erase/program things in u-boot, and the error messages you're seeing

 

what version of u-boot/toolchain are you using ?  what flash ?  what are your u-boot settings ?

QuoteReplyEditDelete

 

 

2008-05-31 09:09:09     Re: Booting Fails if ROMFS Size is increased?

Appalayagari Sreedhar (INDIA)

Message: 56522   

 

Hi Mike,

 

The flash chip is M28w640hsbxxx and I used VDSP flash driver to flash the data into the Flash Chip.

 

Blackfin is configured for BMODE pins 00.

 

U-Boot 1.1.6-svn (ADI-2007R1) (May 14 2008 - 14:35:52)

 

uclinux distribution is 2007R1 RC3.

 

I have flashed final image file from location 0x20040000 when the Rootfs Blocks = 12288 it booted succesfully.

 

When the Rootfs blocks are increased to 16384, it says BAD CRC Error.

 

I am pasting the teraterm log report here.

 

U-Boot 1.1.6-svn (ADI-2007R1) (May 28 2008 - 14:44:46)

 

CPU:   ADSP BF533 Rev.: 0.5

Board: ADI BF533 EZ-Kit Lite board

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

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-05-31  13:18:15 UTC

   Image Type:   Blackfin Linux Kernel Image (gzip compressed)

   Data Size:    4732127 Bytes =  4.5 MB

   Load Address: 00300000

   Entry Point:  00300000

addr = 1000000

len = 4834df

data = 1000040

   Verifying Checksum ... crc32 = 10b9ec9f

Bad Data CRC

 

 

QuoteReplyEditDelete

 

 

2008-05-31 13:26:01     Re: Booting Fails if ROMFS Size is increased?

Mike Frysinger (UNITED STATES)

Message: 56526   

 

do not use VDSP to flash things.  we cannot assist in any way with such things.  you already have a perfectly good flash tool at your disposal: u-boot.

 

if you dont know how to use u-boot to program the flash, read the documentation:

http://docs.blackfin.uclinux.org/doku.php?id=bootloaders:u-boot:parallel-flash

 

you're also using an old release (2007R1) ... you really should upgrade to 2008R1

QuoteReplyEditDelete

 

 

2008-06-02 07:10:52     Re: Booting Fails if ROMFS Size is increased?

Appalayagari Sreedhar (INDIA)

Message: 56559   

 

Hi Mike,

 

Thanks for the reply.

 

I am not using the VDSP Flash Programmer for Flashing the final image.

 

I have written the VDSP driver for the Flash Chip and by using it, I am able to write the flash data succesfully, I read back the entire data and it seems ok.

 

Will there be any difference if we use the developed VDSP based driver and flash driver in the u-boot in this type of scenario. I could see that the data is properly flashed and working fine when the Blocks = 12288

 

once if the Blocks  = 16384 the booting fails.

 

I have done the diagnostics of my Flash chip for its entire size and seems to be ok.

 

Can you explain me why this is happening.

 

Best Regards,Sreedhar.

QuoteReplyEditDelete

 

 

2008-06-02 12:19:02     Re: Booting Fails if ROMFS Size is increased?

Mike Frysinger (UNITED STATES)

Message: 56575   

 

the answer is still the same.  we dont use/know/care about VDSP and cannot assist you in such endeavors.

 

the flash chip you're using is CFI compliant afaik which means you dont have to write any custom drivers in u-boot.

QuoteReplyEditDelete

 

 

2008-06-05 10:33:28     Re: Booting Fails if ROMFS Size is increased?

Appalayagari Sreedhar (INDIA)

Message: 56734   

 

Hi Mike,

 

Thankyou, I would like to know, if there will be any difference in Flashing using VDSP developed driver and uclinux driver.

 

The flash binary data will be the same.

 

My question is if i increase the blocks size to 16384, booting fails. it says CRC error.

 

If there is really a problem with VDSP flashing it should not work even with the blocksize = 12288.

 

Can you please tell me what could be the problem Mike.

 

If u need any more info please let me know, but please help me in solving this problem.

 

Best Regards,Sreedhar.

 

 

QuoteReplyEditDelete

 

 

2008-06-05 10:45:52     Re: Booting Fails if ROMFS Size is increased?

Mike Frysinger (UNITED STATES)

Message: 56739   

 

if you want to use VDSP, you're on your own

QuoteReplyEditDelete

 

 

2008-06-05 11:14:44     Re: Booting Fails if ROMFS Size is increased?

Appalayagari Sreedhar (INDIA)

Message: 56746   

 

Hi Mike,

 

Thankyou. I will check with linux driver itself. can you tell one thing will there be any problem if rootfs block sizes are increased to 16384? i am working with 2007R1 distribution.

 

Best Regards,Sreedhar.

QuoteReplyEditDelete

 

 

2008-06-05 11:31:04     Re: Booting Fails if ROMFS Size is increased?

Mike Frysinger (UNITED STATES)

Message: 56748   

 

there should be no problem related to BLOCKSIZE

Attachments

    Outcomes