This is the mail archive of the ecos-discuss@sources.redhat.com 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: Creating images with fis create


On Fri, 7 Jan 2005 20:57:15 +0200, Wayne Gemmell <waynetg@telkomsa.net> wrote:

Hi all,

I am running the following setup:

RedBoot> version

RedBoot(tm) bootstrap and debug environment [ROM]
Release version - built 13:27:08, Mar 12 2002

Platform: FAL (V850/SA1)
Copyright (C) 2000, 2001, 2002, Red Hat, Inc.

RAM: 0x00200000-0x00300000, 0x00202dc0-0x002ed000 available
FLASH: 0x00400000 - 0x00500000, 16 blocks of 0x00010000 bytes each.

after uploading the image to the unit I create the flash image by using the
following command

fis create fx35 -b 0x205000 -l 20000
and get the following output

An image named 'fx35' exists - are you sure (y/n)? y
* CAUTION * about to program 'fx35'
            at 0x00420000..0x00424e1f from 0x00205000 - are you sure (y/n)? y
... Erase from 0x00420000-0x00430000: .
... Program from 0x00205000-0x00209e20 at 0x00420000: .
... Erase from 0x004f0000-0x00500000: .
... Program from 0x002ef000-0x002ff000 at 0x004f0000: .

I can either write fis load fx35;g or just go to run the program. When I reset
and attempt to run the program using "fis load fx35" I get no response,
including flashing lights although the output of fis list is as follows

Name              FLASH addr  Mem addr    Length      Entry point
(reserved)        0x00400000  0x00400000  0x00010000  0x00000000
RedBoot           0x00410000  0x00410000  0x00020000  0x00000000
RedBoot[backup]   0x00430000  0x00430000  0x00020000  0x00000000
RedBoot config    0x00400000  0x00400000  0x00001000  0x00000000
FIS directory     0x004F0000  0x004F0000  0x00010000  0x00000000
fx35              0x00420000  0x00205000  0x00010000  0x00205000
RedBoot>

I have not altered Redboot, when I received it it had a demo program already
loaded. Any ideas? Here are some other inputs that might be useful...

RedBoot> load -m y
Entry point: 0x00205000, address range: 0x00205000-0x002184bc
xyzModem - CRC mode, 1855(SOH)/0(STX)/0(CAN) packets, 38 retries

[wayne@Wuler] v850-elf-size fx35.S3
   text    data     bss     dec     hex filename
      0   79036       0   79036   134bc fx35.S3

Thanks
Wayne Gemmell


Your old fx35 image in FIS has a length 0f 0x00010000 but your new image has a size of 0x002184bc - 0x00205000 (which is more than 0x10000). That means that only the first 0x10000 bytes of your new image will be programmed to flash (and loaded to RAM afterwards). Either try to create a new image (with a new name) or remove your old fx35 image before creating a new one.

Wolfram
--
Wolfram 'L.A.' Kattanek     Institut fuer Mikroelektronik- und
Email:       LA@imms.de     Mechatronik-Systeme (IMMS) gGmbH
Tel: +49 3677 / 6955-44     Ehrenbergstr. 27
Fax: +49 3677 / 6955-15     98693 Ilmenau / Germany

--
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]