This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
RE: fconfig problem
- To: Christoph Csebits <christoph dot csebits at frequentis dot com>
- Subject: RE: [ECOS] fconfig problem
- From: Gary Thomas <gthomas at cambridge dot redhat dot com>
- Date: Tue, 03 Jul 2001 12:20:16 -0600 (MDT)
- Cc: ecos-discuss at sources dot redhat dot com
- Organization: Red Hat, Inc.
Check your default stacksize. The stack used by RedBoot was possibly
too small and 'fconfig' could cause this failure.
On 03-Jul-2001 Christoph Csebits wrote:
> hi
>
> im working on a MPC860T based custom board
> i have a RAM starting RedBoot with
> 29fxxx flash support.
> programming and erasing of the flash works fine.
> (cvs version Jun2001)
>
> but when i type fconfig my board crashes.
> (it seems that the BD ring of my SCC2 serial driver
> is destroyed -> illegal memory access to 0x0)
>
> i found out, hiding the line
>
> // memcpy((void*)&hold_config, (void*)&config, sizeof(config));
>
> in function do_flash_config in file flash.c
> prevents the board from crashing.
>
> but after that programming the flash results in:
>
> Update RedBoot non-volatile configuration - are you sure (y/n)? y
> .. Erase from 0xff3c0000-0xff3e0000: .
> .. Program from 0x00037758-0x00038758 at 0xff3c0000: $T0440:00036368;01:0003657c;#c9
>
> programming the same region (manually with fis write ...)
> without a previous fconfig command works fine.
>
> any idea?
>
> best regards, christoph
> --