[OpenWrt-Devel] different mtd erase size for a specific partion possible?
Today I checked out how to access the U-Boot variables of my WRT350N v2
(Orion) from Linux.
Installed uboot-envtools and created a fitting /etc/fw_env.config:
# WRT350N v2
# MTD device nameDevice offsetEnv. sizeFlash sector size
/dev/mtd50x0003c0000x20000x1000
I can read all U-Boot env vars, but not change any.
This seems to be a problem of the huge erase site 0x0001 of mtd.
Can I specify a separate erase size for the U-Boot partition?
static struct mtd_partition wrt350n_v2_nor_flash_partitions[] = {
{
...
}, {
.name = u-boot,
.offset = 0x007c,
.size = 0x0004,
}, {
...
},
};
linux: arch/arm/mach-orion5x/wrt350n-v2-setup.c
OpenWrt: target/linux/orion/patches/100-openwrt_partition_map.patch
Maddes
--
http://www.maddes.net/
Home: Earth / Germany / Ruhr-Area
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] different mtd erase size for a specific partion possible?
There is already a patch for this in openwrt, so it should work (in theory).
Do you use trunk or backfire or something older?
2010/5/25 Matthias Buecher / Germany m...@maddes.net:
Today I checked out how to access the U-Boot variables of my WRT350N v2
(Orion) from Linux.
Installed uboot-envtools and created a fitting /etc/fw_env.config:
# WRT350N v2
# MTD device name Device offset Env. size Flash sector size
/dev/mtd5 0x0003c000 0x2000 0x1000
I can read all U-Boot env vars, but not change any.
This seems to be a problem of the huge erase site 0x0001 of mtd.
Can I specify a separate erase size for the U-Boot partition?
static struct mtd_partition wrt350n_v2_nor_flash_partitions[] = {
{
...
}, {
.name = u-boot,
.offset = 0x007c,
.size = 0x0004,
}, {
...
},
};
linux: arch/arm/mach-orion5x/wrt350n-v2-setup.c
OpenWrt: target/linux/orion/patches/100-openwrt_partition_map.patch
Maddes
--
http://www.maddes.net/
Home: Earth / Germany / Ruhr-Area
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] different mtd erase size for a specific partion possible?
Both, backfire and latest trunk.
Can you hint me where this patch is?
Maddes
On 25.05.2010 21:59, Bernhard Loos wrote:
There is already a patch for this in openwrt, so it should work (in theory).
Do you use trunk or backfire or something older?
2010/5/25 Matthias Buecher / Germany m...@maddes.net:
Today I checked out how to access the U-Boot variables of my WRT350N v2
(Orion) from Linux.
Installed uboot-envtools and created a fitting /etc/fw_env.config:
# WRT350N v2
# MTD device nameDevice offsetEnv. sizeFlash sector size
/dev/mtd50x0003c0000x20000x1000
I can read all U-Boot env vars, but not change any.
This seems to be a problem of the huge erase site 0x0001 of mtd.
Can I specify a separate erase size for the U-Boot partition?
static struct mtd_partition wrt350n_v2_nor_flash_partitions[] = {
{
...
}, {
.name = u-boot,
.offset = 0x007c,
.size = 0x0004,
}, {
...
},
};
linux: arch/arm/mach-orion5x/wrt350n-v2-setup.c
OpenWrt: target/linux/orion/patches/100-openwrt_partition_map.patch
Maddes
--
http://www.maddes.net/
Home: Earth / Germany / Ruhr-Area
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] different mtd erase size for a specific partion possible?
https://dev.openwrt.org/browser/trunk/target/linux/generic-2.6/patches-2.6.32/222-partial_eraseblock_write.patch
2010/5/25 Matthias Buecher / Germany m...@maddes.net:
Both, backfire and latest trunk.
Can you hint me where this patch is?
Maddes
On 25.05.2010 21:59, Bernhard Loos wrote:
There is already a patch for this in openwrt, so it should work (in theory).
Do you use trunk or backfire or something older?
2010/5/25 Matthias Buecher / Germany m...@maddes.net:
Today I checked out how to access the U-Boot variables of my WRT350N v2
(Orion) from Linux.
Installed uboot-envtools and created a fitting /etc/fw_env.config:
# WRT350N v2
# MTD device name Device offset Env. size Flash sector size
/dev/mtd5 0x0003c000 0x2000 0x1000
I can read all U-Boot env vars, but not change any.
This seems to be a problem of the huge erase site 0x0001 of mtd.
Can I specify a separate erase size for the U-Boot partition?
static struct mtd_partition wrt350n_v2_nor_flash_partitions[] = {
{
...
}, {
.name = u-boot,
.offset = 0x007c,
.size = 0x0004,
}, {
...
},
};
linux: arch/arm/mach-orion5x/wrt350n-v2-setup.c
OpenWrt: target/linux/orion/patches/100-openwrt_partition_map.patch
Maddes
--
http://www.maddes.net/
Home: Earth / Germany / Ruhr-Area
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] different mtd erase size for a specific partion possible?
So I can mark the partition with MTD_ERASE_PARTIAL, but I can not see
how I can limit erase size to 0x1000 so that only mtd offsets 0x3c000 to
0x3dfff gets erased.
The last 128 bytes (0x3ff80 - 3) of the mtd partition on WRT350N v2
are very important and shouldn't be touched.
Or should this work out of the box with uboot-envtools?
Maddes
On 25.05.2010 23:14, Bernhard Loos wrote:
https://dev.openwrt.org/browser/trunk/target/linux/generic-2.6/patches-2.6.32/222-partial_eraseblock_write.patch
2010/5/25 Matthias Buecher / Germany m...@maddes.net:
Both, backfire and latest trunk.
Can you hint me where this patch is?
Maddes
On 25.05.2010 21:59, Bernhard Loos wrote:
There is already a patch for this in openwrt, so it should work (in theory).
Do you use trunk or backfire or something older?
2010/5/25 Matthias Buecher / Germany m...@maddes.net:
Today I checked out how to access the U-Boot variables of my WRT350N v2
(Orion) from Linux.
Installed uboot-envtools and created a fitting /etc/fw_env.config:
# WRT350N v2
# MTD device nameDevice offsetEnv. sizeFlash sector size
/dev/mtd50x0003c0000x20000x1000
I can read all U-Boot env vars, but not change any.
This seems to be a problem of the huge erase site 0x0001 of mtd.
Can I specify a separate erase size for the U-Boot partition?
static struct mtd_partition wrt350n_v2_nor_flash_partitions[] = {
{
...
}, {
.name = u-boot,
.offset = 0x007c,
.size = 0x0004,
}, {
...
},
};
linux: arch/arm/mach-orion5x/wrt350n-v2-setup.c
OpenWrt: target/linux/orion/patches/100-openwrt_partition_map.patch
Maddes
--
http://www.maddes.net/
Home: Earth / Germany / Ruhr-Area
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] different mtd erase size for a specific partion possible?
It should work out of the box with the patch.
It will (should) set the erase size to the right value.
2010/5/26 Matthias Buecher / Germany m...@maddes.net:
So I can mark the partition with MTD_ERASE_PARTIAL, but I can not see
how I can limit erase size to 0x1000 so that only mtd offsets 0x3c000 to
0x3dfff gets erased.
The last 128 bytes (0x3ff80 - 3) of the mtd partition on WRT350N v2
are very important and shouldn't be touched.
Or should this work out of the box with uboot-envtools?
Maddes
On 25.05.2010 23:14, Bernhard Loos wrote:
https://dev.openwrt.org/browser/trunk/target/linux/generic-2.6/patches-2.6.32/222-partial_eraseblock_write.patch
2010/5/25 Matthias Buecher / Germany m...@maddes.net:
Both, backfire and latest trunk.
Can you hint me where this patch is?
Maddes
On 25.05.2010 21:59, Bernhard Loos wrote:
There is already a patch for this in openwrt, so it should work (in
theory).
Do you use trunk or backfire or something older?
2010/5/25 Matthias Buecher / Germany m...@maddes.net:
Today I checked out how to access the U-Boot variables of my WRT350N v2
(Orion) from Linux.
Installed uboot-envtools and created a fitting /etc/fw_env.config:
# WRT350N v2
# MTD device name Device offset Env. size Flash sector size
/dev/mtd5 0x0003c000 0x2000 0x1000
I can read all U-Boot env vars, but not change any.
This seems to be a problem of the huge erase site 0x0001 of mtd.
Can I specify a separate erase size for the U-Boot partition?
static struct mtd_partition wrt350n_v2_nor_flash_partitions[] = {
{
...
}, {
.name = u-boot,
.offset = 0x007c,
.size = 0x0004,
}, {
...
},
};
linux: arch/arm/mach-orion5x/wrt350n-v2-setup.c
OpenWrt: target/linux/orion/patches/100-openwrt_partition_map.patch
Maddes
--
http://www.maddes.net/
Home: Earth / Germany / Ruhr-Area
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] different mtd erase size for a specific partion possible?
On 2010-05-26 12:02 AM, Matthias Buecher / Germany wrote: So I can mark the partition with MTD_ERASE_PARTIAL, but I can not see how I can limit erase size to 0x1000 so that only mtd offsets 0x3c000 to 0x3dfff gets erased. The last 128 bytes (0x3ff80 - 3) of the mtd partition on WRT350N v2 are very important and shouldn't be touched. Or should this work out of the box with uboot-envtools? You can't limit the erase size. It's not a partition setting, it's hardware defined. The chip can only erase in specifically sized blocks and not arbitrary ranges. - Felix ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] different mtd erase size for a specific partion possible?
Tried to set that flag, but can not find the right spot.
Any help?
Maddes
On 26.05.2010 00:08, Bernhard Loos wrote:
It should work out of the box with the patch.
It will (should) set the erase size to the right value.
2010/5/26 Matthias Buecher / Germany m...@maddes.net:
So I can mark the partition with MTD_ERASE_PARTIAL, but I can not see
how I can limit erase size to 0x1000 so that only mtd offsets 0x3c000 to
0x3dfff gets erased.
The last 128 bytes (0x3ff80 - 3) of the mtd partition on WRT350N v2
are very important and shouldn't be touched.
Or should this work out of the box with uboot-envtools?
Maddes
On 25.05.2010 23:14, Bernhard Loos wrote:
https://dev.openwrt.org/browser/trunk/target/linux/generic-2.6/patches-2.6.32/222-partial_eraseblock_write.patch
2010/5/25 Matthias Buecher / Germany m...@maddes.net:
Both, backfire and latest trunk.
Can you hint me where this patch is?
Maddes
On 25.05.2010 21:59, Bernhard Loos wrote:
There is already a patch for this in openwrt, so it should work (in
theory).
Do you use trunk or backfire or something older?
2010/5/25 Matthias Buecher / Germany m...@maddes.net:
Today I checked out how to access the U-Boot variables of my WRT350N v2
(Orion) from Linux.
Installed uboot-envtools and created a fitting /etc/fw_env.config:
# WRT350N v2
# MTD device nameDevice offsetEnv. sizeFlash sector size
/dev/mtd50x0003c0000x20000x1000
I can read all U-Boot env vars, but not change any.
This seems to be a problem of the huge erase site 0x0001 of mtd.
Can I specify a separate erase size for the U-Boot partition?
static struct mtd_partition wrt350n_v2_nor_flash_partitions[] = {
{
...
}, {
.name = u-boot,
.offset = 0x007c,
.size = 0x0004,
}, {
...
},
};
linux: arch/arm/mach-orion5x/wrt350n-v2-setup.c
OpenWrt: target/linux/orion/patches/100-openwrt_partition_map.patch
Maddes
--
http://www.maddes.net/
Home: Earth / Germany / Ruhr-Area
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
