Most probably you have a genuine Keith&Koep bootloader.
To boot your freshly compiled kernel with this bootloader you need to add a boot-header
in front of the kernel-image telling him how to handle the following bits and bytes.
If this is done you can configure the DHCP- and TFTP- (NFS-)servers and advance to the next
section booting
- your kernel zImage
- the "gen_boot" tool from K&K
# a FAT formated SD/MMC/CF-Card or
* a configured DHCP-server up and running and
* a configured TFTP-server up and running
- a configured NFS-server (if you intend to boot from NFS)
for creating the Keith&Koep bootimage use the following commands :
> gen_boot -d0 0xa2000000 1 0xa2000000 0x200000 > /tmp/header
> cat /trizeps4_path/linux/arch/arm/boot/zImage >> /tmp/header
For setting up an DHCP-server just make an entry like the following one
for your platform with the correct MAC-addres, the attributed IP-address
and the name of the file to load up on request. It can contain the NFS-server path too
which you need when you want to boot from NFS
host trizeps4_eval {
hardware ethernet 00:50:c2:3b:82:c1;
fixed-address 10.0.0.2;
next-server 10.0.0.1;
filename "/kt4";
option root-path "/project/trizeps4/rootfs";
}
For setting up a TFTP-server just configure the directory which to serve
(server_args = -s /srv/tftp/) and place the image file (in this example ./kt4)
with sufficient permissions in this directory
For setting up a NFS-server edit the file "/etc/exports" and add a line like the following one
to grant NFS-access to the mentioned directory for host in the given IP-address range :
/project/trizeps4/rootfs 10.0.0.0/24(rw,no_root_squash,no_all_squash,...)