71 lines
1.6 KiB
Text
71 lines
1.6 KiB
Text
Freescale MPC8323ERDB Board
|
|
-----------------------------------------
|
|
|
|
1. Memory Map
|
|
The memory map looks like this:
|
|
|
|
0x0000_0000 0x03ff_ffff DDR 64M
|
|
0x8000_0000 0x8fff_ffff PCI MEM 256M
|
|
0x9000_0000 0x9fff_ffff PCI_MMIO 256M
|
|
0xe000_0000 0xe00f_ffff IMMR 1M
|
|
0xd000_0000 0xd3ff_ffff PCI IO 64M
|
|
0xfe00_0000 0xfeff_ffff NOR FLASH (CS0) 16M
|
|
|
|
2. Compilation
|
|
|
|
Assuming you're using BASH (or similar) as your shell:
|
|
|
|
export CROSS_COMPILE=your-cross-compiler-prefix-
|
|
make distclean
|
|
make MPC8323ERDB_config
|
|
make
|
|
|
|
3. Downloading and Flashing Images
|
|
|
|
3.1 Reflash U-boot Image using U-boot
|
|
|
|
N.b, have an alternate means of programming
|
|
the flash available if the new u-boot doesn't boot.
|
|
|
|
First try a:
|
|
|
|
tftpboot $loadaddr $uboot
|
|
|
|
to make sure that the TFTP load will succeed before
|
|
an erase goes ahead and wipes out your current firmware.
|
|
Then do a:
|
|
|
|
run tftpflash
|
|
|
|
which is a shorter version of the manual sequence:
|
|
|
|
tftp $loadaddr u-boot.bin
|
|
protect off fe000000 +$filesize
|
|
erase fe000000 +$filesize
|
|
cp.b $loadaddr fe000000 $filesize
|
|
|
|
To keep your old u-boot's environment variables, do a:
|
|
|
|
saveenv
|
|
|
|
prior to resetting the board.
|
|
|
|
3.2 Downloading and Booting Linux Kernel
|
|
|
|
Ensure that all networking-related environment variables are set
|
|
properly (including ipaddr, serverip, gatewayip (if needed),
|
|
netmask, ethaddr, eth1addr, rootpath (if using NFS root),
|
|
fdtfile, and bootfile).
|
|
|
|
Then, do one of the following, depending on whether you
|
|
want an NFS root or a ramdisk root:
|
|
|
|
run nfsboot
|
|
|
|
or
|
|
|
|
run ramboot
|
|
|
|
4 Notes
|
|
|
|
The console baudrate for MPC8323ERDB is 115200bps.
|