This is the mail archive of the ecos-discuss@sourceware.org mailing list for the eCos project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: aboutãredboot 3


On Fri, Feb 12, 2010 at 04:12:56PM +0900, Shu Higashiyama wrote:
> Hello ALL

Hello Shu,

> I question on redboot again. 
> 
> LPC2468 OEM Board /embeddedartists is used. 
> 
> I added the command that had been taught yesterday. 
> 
> $ ecosconfig --srcdir=${ECOS_REPOSITORY} add flash
> 
> make
> 
> Compile ends safely. 
> 
> When starting
> "
> Future start message "+ FLASH: driver init failed: Invalid FLASH address

Well, that occures here:

    redboot/<version>/src/flash.c:do_flash_init()

So, called cyg_flash_init() from that routing stats an error:

    CYG_FLASH_ERR_INVALID

There are many reasons why FLASH driver in a mess. Look on RE

    CYG_FLASH_ERR_INVALID

in eCos FLASH driver code:

    io/flash/<version>/src/flash.c

> **Warning** FLASH configuration checksum error or invalid key
> Use 'fconfig -i' to [re]initialize database
> 
> RedBoot(tm) bootstrap and debug environment [ROM]
> Non-certified release, version v3_0 - built 15:37:08, Feb 12 2010

[snip]

> Platform: Embedded Artists LPC2468 OEM Board (ARM7TDMI-S)
> RAM: 0xa0000000-0xa2000000 [0xa00055f0-0xa1ffd000 available]
> 
> 
> It stops without the command prompt coming out. 

Do you see the prompt in the RedBoot build is built without flash
support? If you can get alive RedBoot without FLASH support, then
build, burn it and also build ecos FLASH tests for your platform.

Then run `flash1' test in GDB and walk throught out flash init code
(I hope that will be possible). And I hope you'll get a clue what
happens on flash init more detaily. But, before GDBugging...

> Flash_sst_39vfxxx.inl 
> flash_ea2468.c 
  ^^^^^^^^^^^^^^
As I could see there are definitions for your flash parts, check the
base address, the bus with, etc. for your FLASH IC, be sure that all
is correct (may be the board's vendor fitted the IC in another way?)
Also, check that your HAL plf init code setups those things properly
too (e.g. bus with for fitted IC).

> flash_ea2468.cdl 
> is uncertain though confirmed. 
> 
> Please teach some coping processes. 

If the things which I mentioned the above are correct, then (IMO) the
most interesting things for GDBugging (digging) are calls: sst_init()
and sst_query() from flash_sst_39vfxxx.inl.

> I am sorry my best regards in a rudimentary question because it is a
> beginner. 

Good points to know how to eCos FLASH geers spin is here
http://ecos.sourceware.org/docs-latest/ref/io-flash.html

HTH

Sergei

> --------------------------------------------
>  Shu Higashiyama
> jyu-shaãCorp.
> 
>  2-20-19-609,Teraya,Tsurumi-ku,Yokohama-city,Japan
> 
>  Tel 81-45-576-0976
>  Fax 81-45-576-0976
> 
> E-Mail aeb05134@nifty.com
> ããã higashi@jiyu-sha.co.jp
> URL http://homepage1.nifty.com/jiyu-sha/
>     http://www.jiyu-sha.co.jp
> ---------------------------------------------
> 
> 
> 
> -- 
> Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
> and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]