This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
Re: JFFS2, redboot and fis command
On Thu, Jul 08, 2004 at 12:47:02PM +0300, Edgar Grimberg wrote:
> Hello,
> I have some sort of a problem with fis parameters. First a short
> description.
> I've built RedBoot with JFFS2 support succesfully:
>
> [root@wks-edgar redboot]# ecosconfig check
> Target: eb40a
> Template: redboot
> Added:
> CYGPKG_IO
> CYGPKG_IO_SERIAL
> CYGPKG_KERNEL
> CYGPKG_MEMALLOC
> CYGPKG_LIBC
> CYGPKG_LIBC_I18N
> CYGPKG_LIBC_SETJMP
> CYGPKG_LIBC_SIGNALS
> CYGPKG_LIBC_STARTUP
> CYGPKG_LIBC_STDIO
> CYGPKG_LIBC_STDLIB
> CYGPKG_LIBC_TIME
> CYGPKG_LIBM
> CYGPKG_IO_WALLCLOCK
> CYGPKG_ERROR
> CYGPKG_IO_FLASH
> CYGPKG_IO_FILEIO
> CYGPKG_IO_DISK
> CYGPKG_FS_JFFS2
> CYGPKG_LINUX_COMPAT
> No conflicts
Thats an unusual configuration. Redboot is designed to run without the
kernel. Also, as far as i know, jffs2 support is not available from
Redboot. David Woodhouse said he had a hack to make it work, but i
don't think he ever contributed it.
> I flashed the bin file and have RedBoot running. Here's some output from
> it.
>
> RAM: 0x00100000-0x00120000, [0x0010b3c0-0x00120000] available
> FLASH: 0x01000000 - 0x01400000, 64 blocks of 0x00010000 bytes each.
>
> RedBoot> help fis
> Manage FLASH images
> fis {cmds}
> Erase FLASH contents
> fis erase -f <flash_addr> -l <length>
> Write raw data directly to FLASH
> fis write -f <flash_addr> -b <mem_base> -l <image_length>
>
> Well, I wonder what did I do wrong not to have the other fis options in
> place?
It looks like you have not enabled CYGOPT_REDBOOT_FIS.
However, i suggest you read the documentation about building redboot.
You will then have a more normal configuration.
Andrew
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss