| Hi all. I need some info about device tree blob. I'm testing a powerpc board (very similar to mpc512xev) with the following feature: - 256MB flash (only 1 bank) Changes some lines of device tree source about flash localbus@80000020 { compatible = "fsl,mpc5121ads-localbus"; #address-cells = <2>; #size-cells = <1>; reg = <0000020 40>; ranges = <0 0 fc000000 04000000 2 0 82000000 00008000>; flash@0,0 { device_type = "rom"; compatible = "direct-mapped"; probe-type = "CFI"; reg = <0 0 4000000>; #address-cells = <1>; #size-cells = <1>; bank-width = <4>; device-width = <2>; partitions = <00000000 00040000 // first sector is protected 00040000 03c00000 // 60 Mb for filesystem 03c40000 00280000 // 2.5 Mb for kernel 03ec0000 00040000 // one sector for device tree 03f00000 00100000>; // one Mb for u-boot partition-names = "protected", "filesystem", "kernel", "device-tree", "u-boot"; }; .... with these changes: .... flash@0,0 { device_type = "rom"; compatible = "direct-mapped"; probe-type = "CFI"; reg = <0 0 1000000>; #address-cells = <1>; #size-cells = <1>; bank-width = <1>; device-width = <1>; partitions = <300000 200000 //uimage 400000 3200000>; // fs partition-names = "uimage", "fs"; }; .... The problem is that on bootstrap stage, kernel truncate the flash memory to 16MB, so i cannot access to the whole flash. kernel messages: mtd: partition "fs" extends beyond the end of device "60000000.flash" size truncated to 0xc00000. I'd like to know if i have to specify into the dtb file the size of flash mem. What about nand flash controller and its functionality? If you have more info about this, please write to me. Thanks in advance, @s |