Kontron AM4204 - Manual (Page 72)

57 AM4204
www.kontron.com
In case ‘quilt’ is not installed, use ‘patch’ instead:
# for i in `cat patches/series`; do patch -p 1 < patches/$i; done
Please note, the last line in the “series”-file (# pcinic-pcie.patch) must be changed, depending on whether
pci host driver package is installed or not.
• Setup the SDK environment
# source ./env-setup --runtime-model OCTEON_CN56XX_PASS2
• Build the Linux kernel
#
make –C linux kernel
This will build the Linux kernel and root file system including all necessary libraries. Using ‘make –C linux
kernel-deb’ builds only the kernel without the root file system. After building has finished, a kernel and
rootfs image ‘linux/kernel_2.6/linux/vmlinux.64’ will be made. Before using it with the ‘bootoctlinux’
command, the file should be stripped.
Please refer to the online documentation provided with the Cavium Networks SDK for more detail.
5.3.3.2 Updating Cavium Linux BSP
A new Cavium Linux BSP, either rebuilt as described above or delivered as part of an AM4204 software
release, is installed from the bootloader CLI. The BSP is stored in Linux MTD partitions mtd3 (image 0) and
mtd8 (image 1). Generally, the active image (image0) is updated first. If the update worked and the board
started successfully, image1 can also be updated.
Prerequisites: a working TFTP server, DHCP server and network connectivity to the DHCP and TFTP server.
• Start system and connect to serial console
• Stop boot process at the bootloader command line
U-Boot 1.1.1 GA 2.04 (Build time: Dec 9 2009 - 13:59:54)
OCTEON CN5650-NSP pass 2.1, Core clock: 600 MHz, DDR clock: 400 MHz (800 Mhz data rate)
CUST_KONTRON_T5516 PLD version: 12 Board Type: 2 Option: 10 Revision: 0
Reset Type: 01 cold reset, Source: 08 Software Initiated
DRAM: 2048 MB
Flash: 128 MB
Calculating bootloader CRC checksum.....finished
Testing DRAM (fast), testpattern 5555555555555555
(fast), testpattern aaaaaaaaaaaaaaaa
2048MB - ok
Clearing DRAM........ done
Using default environment
Note:
The following description assumes that image 0 is activated either using the ‘activate_image0’
bootloader command or the appropriate ipmitool command as described above. If image1 would be
active, the upper and lower halves of the flash address space are swapped. In this case, the
‘data1a_backup_flash_update’ command would not update image1 kernel and root FS partition as
intended but image0 instead.