[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: MCM2+8 with external Flash
No RAM is used by the boot loader so you can upload an 8MB image to RAM and then
load it to flash. You should even be able to upload a 10MB large image if you split the image
in to parts, lets say 2x5MB. Something like this should work (I haven't tested it though):
--file <first_half> 0xc0000000
--flash c0000000 0 0x500000
--file <second_half> 0xc0000000
--flash c0000000 0x500000 0x500000
I think your problem has to do with the ./flashitall script. Run ./flashitall -p.
Check that you really program the correct size into flash. For a 6MB image it should be
something like this:
--flash 0xc0004000 0 0x600000
You can program 8MB at one time but then you have to send the image to the DRAM base, e.g. 0xc0000000
otherwise the image will not fit.
> On Wed, Oct 22, 2003 at 07:52:58PM +0200, Bernhard Roessmann wrote:
> > Hi again,
> > I am using a MCM2+8 with 8MByte external flash chip (AMD
> > My ptablespec looks like this.
> > [ptable]
> > # name size rw-options type image-file
> > rescue 0x010000 ro rescue rescue.img
> > flash1 0x1F0000 ro kernel flash1.img
> > flash2 0x200000 rw jffs flash2.img
> > As you can see, the whole internal flash (2MB) is used for
> rescue and
> > flash1, the external flash as flash2 (only 2MB first).
> > Everything works fine now.
> > If I increase flash2 now up to 0x600000 (6MB), the MCM boots after
> > flashitall and works normally. But it doesn't boot anymore
> with "normal
> > boot" option (serial kernel output shows nothing!).
> > If I increase flash2 beyond 6MB, e.g. 0x800000 (8MB, which ist the
> > external flash size), MCM NEVER boots, neither after the
> reboot after
> > flashitall nor with normal boot mode.
> > Whats wrong?
> I'm not sure exactly how RAM is used by the boot loader, but
> I know that
> it loads the entire flashimage to RAM before writing it to
> flash. So you
> may need more than 8MB RAM to be able to flash a 6MB image. Maybe
> someone else can explain the bootloader internals?
> I suggest that you exclude the jffs-partition from your fimage and
> initialize the jffs partition on first-time boot using
> eraseflash and dd
> to write an unpadded factorydefault-image
> to the character device.
> Best regards