Thank you for your tip Florian,
I'm looking at DIR-645 DTS file, which seems to have the same flash layout
my router has.
On DIR-645 DTS file, it creates 6 partitions instead of 8: uboot,
uboot-env, factory, nvram, devdata and firmware.
I'm assuming I should need to do the same, so: upgrade and rootfs becomes
firmware, factory would be devconf, and langpack together with rootfs would
be gone.
I don't know how to map properly, but if you have a suggestion, please
tell me. It's hard for me to see the mapping.
Thanks once again!
----- Original Message -----
From: "Florian Fainelli" <[email protected]>
To: "OpenWrt Development List" <[email protected]>
Sent: Monday, June 24, 2013 5:53 AM
Subject: Re: [OpenWrt-Devel] Help with DTS file
2013/6/24 [email protected] <[email protected]>:
On Sun, Jun 23, 2013 at 5:50 PM, Flávio Silveira <[email protected]>
wrote:
Good evening,
I'm trying to create a dts file for my router which is not supported
yet
and I'm stuck on the definition of partitions.
Do I have to follow the same as stock firmware?
Router's serial log with stock firmware shows this:
Creating 8 MTD partitions on "raspi":
0x000000150060-0x0000003cc060 : "rootfs"
0x000000050000-0x0000003e0000 : "upgrade"
0x000000040000-0x000000050000 : "devconf"
0x000000030000-0x000000040000 : "devdata"
0x0000003e0000-0x000000400000 : "langpack"
0x000000000000-0x000000400000 : "flash"
0x000000000000-0x000000030000 : "u-boot"
0x000000030000-0x000000038000 : "boot env"
Partitions should not overlap. This partition table doesn't seem to be
valid.
Parititions can overlap, even with DT, but you just need to make sure
that node addresses are unique, such that if you want to make
overlapping partitions of this kind:
firmware@30000 {
reg = <0x30000 0x10000>;
name = "firmware";
};
rootfs@30001 {
reg = <0x30000 0x2000>;
};
Since both firmware and rootfs start at the same offset, you still
need them to have an unique node name if you want the MTD OF parser to
be able to parse *both* of them.
--
Florian
_______________________________________________
openwrt-devel mailing list
[email protected]
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
_______________________________________________
openwrt-devel mailing list
[email protected]
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
