Excellent, This worked for me.
File sizes are:
Initrd.img/ramdisk.gz – 2425607
Vmlinuz/zImage – 1524976
Which fit nicely in the flash. I redid the flash layout to get rid of some of
the not needed sections and make more useable space.
EM-438/EM-7220 ver.AG0 2006-05-23
== Executing boot script in 1.000 seconds - enter ^C to abort
^C
RedBoot> ^C
RedBoot> fis list
Name FLASH addr Mem addr Length Entry point
RedBoot 0xF0000000 0xF0000000 0x00040000 0x00000000
RedBoot config 0xF07C0000 0xF07C0000 0x00001000 0x00000000
FIS directory 0xF07E0000 0xF07E0000 0x00020000 0x00000000
zImage 0xF0040000 0x01008000 0x00400000 0x01008000
ramdisk.gz 0xF0440000 0x01800000 0x00340000 0x01800000
Chris
From: Maciej Soltysiak [mailto:mac...@soltysiak.com]
Sent: Monday, March 18, 2013 4:25 PM
To: Arnaud Patard; Luke Kenneth Casson Leighton
Cc: Chris Wilkinson; debian-arm@lists.debian.org
Subject: Re: Can't get a Linux 3.6-rc zImage smaller than 2MB
On Mon, Mar 18, 2013 at 6:10 PM, Arnaud Patard <arnaud.pat...@rtp-net.org>
wrote:
"Chris Wilkinson" <kins...@verizon.net> writes:
> Is it necessary to flash-kernel? Once /boot on HD is populated with
> the new kernel, doesn’t it finally boot from that and it doesn’t matter what
> version is flashed?
redboot is configured to read the kernel from the flash, so yes, you
need flash-kernel. I've not tested to load a kernel from disk so I've
no idea if you can configure and use redboot to do it (but it's unlikely).
I was wondering if it would be possible to use a different portion of the flash
memory for the kernel.
I mean that redboot MTD has like 7 regions.
Anyway, as some people requested, I wanted to share what worked for me, so I
redid the same thing but with 3.8.3.
Here are the steps:
https://soltysiak.com/compiling-linux-kernel-for-ss4000-e-aka-lanner-em-7210-running-debian/
Best regards,
Maciej
