Re: [OpenWrt-Devel] Looking for a Broadcom Asus tester(s)
Hi, thanks for your feedback and sorry for my mistake. Now I tried openwrt-brcm47xx-legacy-asus-wl-500gp-v2-squashfs.trx from r45811 and it works. Great! I'm wondering whether we should improve the make menuconfig help text about subtarget selection a little bit. Just for users like me, not reading the wiki page _before_ running the compiler :-) Regards, mhei Am Donnerstag, 28. Mai 2015, 21:57:04 schrieb Rafał Miłecki: On 28 May 2015 at 21:44, Rafał Miłecki zaj...@gmail.com wrote: On 28 May 2015 at 21:31, Michael Heimpold m...@heimpold.de wrote: I have a Asus WL-500gP V2 router and restored original Asus Firmware version 3.0.4.4. Then I tried openwrt-brcm47xx-generic-squashfs.trx, openwrt-brcm47xx-generic-squashfs-gz.trx openwrt-brcm47xx-generic-squashfs-noloader-nodictionary.trx, but without look. The original firmware always rejected the image :-( You were supposed to test device-specific firmware, in your case it means openwrt-brcm47xx-legacy-asus-wl-520gp-v2-squashfs.trx (yes, there isn't any reason for you to use generic instead of legacy) So above file (asus-wl-520gp-v2) is indeed for Asus WL-500gP v2. It should be named 500, not 520, I fixed this mistake in r45811: https://dev.openwrt.org/changeset/45811/ So whatever file you have: openwrt-brcm47xx-legacy-asus-wl-500gp-v2-squashfs.trx openwrt-brcm47xx-legacy-asus-wl-520gp-v2-squashfs.trx , please try it and let me know if it worked with original firmware. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Looking for a Broadcom Asus tester(s)
On 28 May 2015 at 21:44, Rafał Miłecki zaj...@gmail.com wrote: On 28 May 2015 at 21:31, Michael Heimpold m...@heimpold.de wrote: I have a Asus WL-500gP V2 router and restored original Asus Firmware version 3.0.4.4. Then I tried openwrt-brcm47xx-generic-squashfs.trx, openwrt-brcm47xx-generic-squashfs-gz.trx openwrt-brcm47xx-generic-squashfs-noloader-nodictionary.trx, but without look. The original firmware always rejected the image :-( You were supposed to test device-specific firmware, in your case it means openwrt-brcm47xx-legacy-asus-wl-520gp-v2-squashfs.trx (yes, there isn't any reason for you to use generic instead of legacy) So above file (asus-wl-520gp-v2) is indeed for Asus WL-500gP v2. It should be named 500, not 520, I fixed this mistake in r45811: https://dev.openwrt.org/changeset/45811/ So whatever file you have: openwrt-brcm47xx-legacy-asus-wl-500gp-v2-squashfs.trx openwrt-brcm47xx-legacy-asus-wl-520gp-v2-squashfs.trx , please try it and let me know if it worked with original firmware. -- Rafał ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Looking for a Broadcom Asus tester(s)
Hi Rafał, I have a Asus WL-500gP V2 router and restored original Asus Firmware version 3.0.4.4. Then I tried openwrt-brcm47xx-generic-squashfs.trx, openwrt-brcm47xx-generic-squashfs-gz.trx openwrt-brcm47xx-generic-squashfs-noloader-nodictionary.trx, but without look. The original firmware always rejected the image :-( The OpenWrt version I tested was: git-svn-id: svn://svn.openwrt.org/openwrt/trunk@45810 3c298f89-4303-0410-b956-a3cf2f4a3e73 HTH + thanks for your hard work, regards, Michael Am Mittwoch, 27. Mai 2015, 22:32:57 schrieb Rafał Miłecki: Hi, With few recent commits OpenWrt can now generate Asus-specific TRX files for brcm47xx and bcm53xx. The magic is about some extra data at the end of TRX (so the format differs a bit, even it using the same file extension and layout). My request for someone having Broadcom-based Asus devices is: 1) Install original firmware 2) Try to install OpenWrt .trx firmware for that device 3) Let us know if it worked I don't have any Asus device around, so I'm not sure if OpenWrt generates really compatible images now. Above way is the only one to verify it for sure :) ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Looking for a Broadcom Asus tester(s)
On 28 May 2015 at 21:44, Rafał Miłecki zaj...@gmail.com wrote: On 28 May 2015 at 21:31, Michael Heimpold m...@heimpold.de wrote: I have a Asus WL-500gP V2 router and restored original Asus Firmware version 3.0.4.4. Then I tried openwrt-brcm47xx-generic-squashfs.trx, openwrt-brcm47xx-generic-squashfs-gz.trx openwrt-brcm47xx-generic-squashfs-noloader-nodictionary.trx, but without look. The original firmware always rejected the image :-( You were supposed to test device-specific firmware, in your case it means openwrt-brcm47xx-legacy-asus-wl-520gp-v2-squashfs.trx (yes, there isn't any reason for you to use generic instead of legacy) Ahh, wait, I just noticed you use 500gP V2, not 520... let me take a look again. -- Rafał ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Looking for a Broadcom Asus tester(s)
On 28 May 2015 at 21:31, Michael Heimpold m...@heimpold.de wrote: I have a Asus WL-500gP V2 router and restored original Asus Firmware version 3.0.4.4. Then I tried openwrt-brcm47xx-generic-squashfs.trx, openwrt-brcm47xx-generic-squashfs-gz.trx openwrt-brcm47xx-generic-squashfs-noloader-nodictionary.trx, but without look. The original firmware always rejected the image :-( You were supposed to test device-specific firmware, in your case it means openwrt-brcm47xx-legacy-asus-wl-520gp-v2-squashfs.trx (yes, there isn't any reason for you to use generic instead of legacy) ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] Looking for a Broadcom Asus tester(s)
Hi, With few recent commits OpenWrt can now generate Asus-specific TRX files for brcm47xx and bcm53xx. The magic is about some extra data at the end of TRX (so the format differs a bit, even it using the same file extension and layout). My request for someone having Broadcom-based Asus devices is: 1) Install original firmware 2) Try to install OpenWrt .trx firmware for that device 3) Let us know if it worked I don't have any Asus device around, so I'm not sure if OpenWrt generates really compatible images now. Above way is the only one to verify it for sure :) -- Rafał ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Looking for a Broadcom Asus tester(s)
Hi, I tested it on my ASUS RT-AC87U and it works like a charm. Cheers! El 27/05/2015 a las 22:32, Rafał Miłecki escribió: Hi, With few recent commits OpenWrt can now generate Asus-specific TRX files for brcm47xx and bcm53xx. The magic is about some extra data at the end of TRX (so the format differs a bit, even it using the same file extension and layout). My request for someone having Broadcom-based Asus devices is: 1) Install original firmware 2) Try to install OpenWrt .trx firmware for that device 3) Let us know if it worked I don't have any Asus device around, so I'm not sure if OpenWrt generates really compatible images now. Above way is the only one to verify it for sure :) ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Looking for a Broadcom Asus tester(s)
On Wed, 2015-05-27 at 22:32 +0200, Rafał Miłecki wrote: Hi, With few recent commits OpenWrt can now generate Asus-specific TRX files for brcm47xx and bcm53xx. The magic is about some extra data at the end of TRX (so the format differs a bit, even it using the same file extension and layout). My request for someone having Broadcom-based Asus devices is: 1) Install original firmware 2) Try to install OpenWrt .trx firmware for that device 3) Let us know if it worked I don't have any Asus device around, so I'm not sure if OpenWrt generates really compatible images now. Above way is the only one to verify it for sure :) Has the partition corruption I saw with the RT-AC87U a while ago (when I tested if it would boot, which it didn't) been sorted out? I really don't want to risk breaking my device again. I was lucky I was able to get a build of asuswrt-merlin to go far enough to build mtd-erase2, actually it's a symlink to the rc utility, (with an appropriate change) to allow me to fix the problem. btw, off-topic, I've been able to load the R8000 OpenWrt chk firmware via Luci a few times now so I don't know what changed but it seems ok now. Ian ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Looking for a Broadcom Asus tester(s)
On 28 May 2015 at 07:42, Rafał Miłecki zaj...@gmail.com wrote: On 28 May 2015 at 07:33, Ian Kent ra...@themaw.net wrote: On Wed, 2015-05-27 at 22:32 +0200, Rafał Miłecki wrote: Hi, With few recent commits OpenWrt can now generate Asus-specific TRX files for brcm47xx and bcm53xx. The magic is about some extra data at the end of TRX (so the format differs a bit, even it using the same file extension and layout). My request for someone having Broadcom-based Asus devices is: 1) Install original firmware 2) Try to install OpenWrt .trx firmware for that device 3) Let us know if it worked I don't have any Asus device around, so I'm not sure if OpenWrt generates really compatible images now. Above way is the only one to verify it for sure :) Has the partition corruption I saw with the RT-AC87U a while ago (when I tested if it would boot, which it didn't) been sorted out? It's not perfect yet, but it works: http://git.openwrt.org/?p=openwrt.git;a=commitdiff;h=beff7e61f2935a447522bc3057c51a0ef828be60 target/linux/bcm53xx/patches-3.18/901-mtd-bcm47xxpart-workaround-for-Asus-RT-AC87U-asus-pa.patch For DD we'll get a better solution (I started working on it by patch to linux-mtd for parsers support). For more details, see https://patchwork.ozlabs.org/patch/473018/ (discussion). -- Rafał ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Looking for a Broadcom Asus tester(s)
On 28 May 2015 at 07:33, Ian Kent ra...@themaw.net wrote: On Wed, 2015-05-27 at 22:32 +0200, Rafał Miłecki wrote: Hi, With few recent commits OpenWrt can now generate Asus-specific TRX files for brcm47xx and bcm53xx. The magic is about some extra data at the end of TRX (so the format differs a bit, even it using the same file extension and layout). My request for someone having Broadcom-based Asus devices is: 1) Install original firmware 2) Try to install OpenWrt .trx firmware for that device 3) Let us know if it worked I don't have any Asus device around, so I'm not sure if OpenWrt generates really compatible images now. Above way is the only one to verify it for sure :) Has the partition corruption I saw with the RT-AC87U a while ago (when I tested if it would boot, which it didn't) been sorted out? It's not perfect yet, but it works: http://git.openwrt.org/?p=openwrt.git;a=commitdiff;h=beff7e61f2935a447522bc3057c51a0ef828be60 target/linux/bcm53xx/patches-3.18/901-mtd-bcm47xxpart-workaround-for-Asus-RT-AC87U-asus-pa.patch For DD we'll get a better solution (I started working on it by patch to linux-mtd for parsers support). btw, off-topic, I've been able to load the R8000 OpenWrt chk firmware via Luci a few times now so I don't know what changed but it seems ok now. Support for extracting TRX files from bin (Linksys) and chk (Netgear) was added few months ago. -- Rafał ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
