Dario Presti wrote:
Hello,
I'm working on MPC8323_rdb board whit 1 new flash device S29GL512P instead
of original flash devices.
the bootloader is u-boot 1.1.6 (I know is too old and I'm going to upgrade
it) and the kernel is 2.6.20.
2.6.20 is also too old. :-)
I did this modification to the bootloader to support new flash:
1)I modified the board/mpc8323rdb/config.mk file to set TEXT_BASE from
0xFE000000 TO 0xFC000000
2)I modified the file /include/configs/MPC8323RDB.h:
#define CFG_FLASH_BASE 0xFC000000 /* FLASH base address */
#define CFG_FLASH_SIZE 64 /* FLASH size is 64M */
#define CFG_LBLAWBAR0_PRELIM CFG_FLASH_BASE /* Window base at flash base */
#define CFG_LBLAWAR0_PRELIM 0x80000019 /* 64MB window size */
#define CFG_OR0_PRELIM 0xfc006ff7 /* 64MB Flash size */
#define CFG_MAX_FLASH_BANKS 1 /* number of banks */
#define CFG_MAX_FLASH_SECT 512 /* sectors per device */
3)I modify and recompiled .dts file
fl...@fc000000 {
device_type = "jedec-flash";
compatible = "direct-mapped";
probe-type = "CFI";
reg = <0xfc000000 0x1000000>;
bank-width = <0x2>;
partitions = <0x0 0x80001 0x80000 0x20000 0xa0000 0x180000
0x220000
0xde0000>;
partition-names = "U-Boot", "dtb", "Kernel", "rootfs";
};
but the kernel find the flash at 0xFE000000 and the boot stop because kernel
panic. The log is:
Is the kernel even using that node, or some other means to determine the
flash location? The "MPC8323RDB Flash Bank 1" messages make me think
you've got a custom flash map driver.
-Scott
_______________________________________________
Linuxppc-dev mailing list
Linuxppc-dev@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/linuxppc-dev