>
> Typo, I did mean factory.bin ... . The type you use to initially flash
> OpenWrt ;-)
>
Ok, that will be factory.img. There is no factory.bin image for that
model to flash. If someone needs it badly, img file is 128-byte DNI
header prepended to bin file (kernel + fake rootfs).
Regards
On Tue, 19 Nov 2019 at 17:59, Michal Cieslakiewicz
wrote:
>
> >
> > That was my question, if the "new" OpenWrt sysupgrade.bin still works
> > in the initial flash.
> >
>
> sysupgrade.bin for this model is in format tar+metadata, it is not
> designed to be put into flash directly.
Typo, I did
>
> That was my question, if the "new" OpenWrt sysupgrade.bin still works
> in the initial flash.
>
sysupgrade.bin for this model is in format tar+metadata, it is not
designed to be put into flash directly.
Regards
Michal
___
openwrt-devel mailing
Hello,
Argh, I forgot to add this to my previous email...
ubi volume is successfully resized, but ubi filesystem on top of it is
not - so /overlay does not benefit from extra space. Are there any
methods for UBIFS online resize that complement ubirsvol?
Best regards
Michal
On Tue, 19 Nov 2019 at 17:33, Michal Cieslakiewicz
wrote:
>
> Hello,
>
> >
> > Have you checked that flashing a factory.bin image through tftp still
> > works?
> >
>
> Yes, it works. On this router the easiest way to flash memory via tftp
> is to enter uboot and execute 'fw_recovery' command,
Hello,
>
> Have you checked that flashing a factory.bin image through tftp still
> works?
>
Yes, it works. On this router the easiest way to flash memory via tftp
is to enter uboot and execute 'fw_recovery' command, then factory.img
file can be uploaded via tftp client. I hope this answers
On Tue, 19 Nov 2019 at 16:18, Michal Cieslakiewicz
wrote:
>
> Hello David,
>
> Two questions were raised just after publishing 'all-flash-space' patch.
> Now I am ready to provide more information on these issues:
>
> 0. Downgrade to vendor firmware.
>
> It is possible. Just don't forget to erase
Hello David,
Two questions were raised just after publishing 'all-flash-space' patch.
Now I am ready to provide more information on these issues:
0. Downgrade to vendor firmware.
It is possible. Just don't forget to erase both ubi concat partitions:
'mtd -r erase ubi' does the job fine.
1.
On Tue, 12 Nov 2019 17:15:17 +0100
David Bauer wrote:
> Hello Michal,
>
> Have you tried if this breaks sysupgrade from an older OpenWrt
> firmware? I'm not sure if an UBI resize works without additional
> steps.
>
> Best wishes
> David
>
Hello David,
Thanks! Good point, I was usually
Hello Michal,
On 11/12/19 2:02 PM, Michal Cieslakiewicz wrote:
> Netgear WNDR routers (AR9344 models) like WNDR4300 have 128 MiB of flash
> memory but only first 32 MiB are used now - both by vendor's firmware and
> OpenWrt. This patch concatenates two regions of flash memory: ubi part
> of
>
> Is revert to vendor firmware still possible with this change, e.g.
> using Netgear TFTP recovery mode?
>
Hello Piotr,
Yes, it is possible. I've performed such operation using fw_recovery
command from u-boot prompt.
However, looking at factory logs, reserved space is used somehow by
Hi Michal,
On 12.11.2019 14:02, Michal Cieslakiewicz wrote:
Netgear WNDR routers (AR9344 models) like WNDR4300 have 128 MiB of flash
memory but only first 32 MiB are used now - both by vendor's firmware and
OpenWrt. This patch concatenates two regions of flash memory: ubi part
of firmware
Wow!! This is applicable also to Netgear R6220!
On Tue, 12 Nov 2019, Michal Cieslakiewicz wrote:
Date: Tue, 12 Nov 2019 14:02:14
From: Michal Cieslakiewicz
To: "openwrt-devel@lists.openwrt.org"
Cc: Adrian Schmutzler
Subject: [OpenWrt-Devel] [PATCH] ath79: enable all space
Netgear WNDR routers (AR9344 models) like WNDR4300 have 128 MiB of flash
memory but only first 32 MiB are used now - both by vendor's firmware and
OpenWrt. This patch concatenates two regions of flash memory: ubi part
of firmware partition and reserved (unused) space beyond 'caldata_backup'
while
14 matches
Mail list logo
