Oh, there is that? I did a quick look at the list and didn't find the name... Sorry for being dumb:-(
So is there a way to integrate the /lib/firmware/brcfmac/4366c.bin into the built image? I guess I could just replace somewhere in the repo, and then build a fully working firmware.
Edit: I found the instruction of ImageBuilder. I assume what I need to do is to use the FILE variable, cp the files to their desired location and build it. Does that sound reasonable?
Edit2: I used the ImageBuilder to generate a firmware. I am hoping that it has included the corrent bin files. I wonder if there is a end2end test that I can run to verify this build before I upload to the router?
I'm quite tied up this weekend. Will try to check in all my build scripts to github. I have a image header verification tool as well.
Cool! The verification tool sounds fantastic.
Just an update: It seems the upgrade thru UI is broken on latest trunk. It was working fine around April (kernel 4.9.20). I think this has a lot to do with changes to these files
I've made some progress on the new firmware. I'm now using Optimized Archer C7 build as reference and I have been able to include all the features in the next build. Which includes ipsec. Full list is available in above link.
I can give a new build only if someone is comfortable upgrading in future using
mtd write /path/to/trxfile.trx firmware
Let me know. Or else we have to wait until upgrade is fixed in trunk. I've raised a bug report for the same.
Edit: Recompiled sources from May-20-2017. Upgrade works fine. Uploaded new build
Sounds good. I downloaded the package and will upgrade this weekend. Thanks for the effort!!
Nice build, all features are live. I have a question, how is dnsmasq different from dnsmasq-full? Some package I want depends on dnsmasq-full, which complaints that dnsmasq is already installed.
I wonder if there is a sym link trick to get pass it.
I just remove and install the desired package to get pass it. Now everything works perfectly. Thanks npcomplete.
I checked the log. these things are repeatedly logged:
Tue Jun 27 21:03:56 2017 daemon.notice netifd: wan6_4 (5412): Error: inet6 prefix is expected rather than "lookup".
Tue Jun 27 21:03:56 2017 daemon.notice netifd: Interface 'wan6_4' is now down
Tue Jun 27 21:03:56 2017 daemon.notice netifd: Interface 'wan6_4' is setting up now
Tue Jun 27 21:03:59 2017 daemon.notice netifd: wan6_4 (5434): cat: can't open '/tmp/464-wan6_4-anycast': No such file or directory
I wonder what these are?
It appears ipv6 over ip4 is broken. You can turn for ipv6 for now. I'll try to investigate.
Great work, npcomplete!
I am trying to also get an EA2700 to support LEDE. However, am trying to figure out how to create a proper firmware file using your info. Currently, I just overwrite both firmwares to make sure it loads...
Could you provide my some pointers, pls?
Here's the details:
system type : Broadcom BCM5357 chip rev 2
processor : 0
cpu model : MIPS 74K V4.9
BogoMIPS : 239.20
wait instruction : no
microsecond timers : yes
tlb_entries : 64
extra interrupt vector : no
hardware watchpoint : yes
ASEs implemented : mips16 dsp
VCED exceptions : not available
VCEI exceptions : not available
MemTotal: 59524 kB
dev: size erasesize name
mtd0: 00080000 00004000 "boot"
mtd1: 00180000 00004000 "nvram"
mtd2: 01200000 00004000 "linux"
mtd3: ffe232e4 00004000 "rootfs"
mtd4: 01200000 00004000 "linux2"
mtd5: 010232e4 00004000 "rootfs2"
mtd6: 01900000 00004000 "brcmnand"
CFE> show devices
Device Name Description
uart0 NS16550 UART at 0x18000300
nflash0 Hynix NAND flash size 65536KB
nflash0.boot Hynix NAND flash offset 00000000 size 512KB
nflash0.nvram Hynix NAND flash offset 00080000 size 1536KB
nflash0.trx Hynix NAND flash offset 00200000 size 1KB
nflash0.os Hynix NAND flash offset 0020001C size 18432KB
nflash0.trx2 Hynix NAND flash offset 01400000 size 1KB
nflash0.os2 Hynix NAND flash offset 0140001C size 18432KB
nflash1.boot Hynix NAND flash offset 00000000 size 512KB
nflash1.nvram Hynix NAND flash offset 00080000 size 1536KB
nflash1.trx Hynix NAND flash offset 00200000 size 18432KB
nflash1.trx2 Hynix NAND flash offset 01400000 size 18432KB
nflash1.brcmnand Hynix NAND flash offset 02600000 size 26624KB
eth0 Broadcom BCM47XX 10/100/1000 Mbps Ethernet Controller
Thanks a million!
@hvandrie How can I help you? Have you already managed to build a firmware? Have you taken apart the official firmware?
I had a quick look. The firmware is a standard TRX firmware plus linksys trailer (256 byte) appended.
This appears to be brcm47xx device. Apart from upgrading, everything should work. In fact upgrading should work as long as you stick to first partition.
Please start a new thread. We can discuss there. Thanks.
@npcomplete, thx. Started new thread. Basically am new to creating support for a device. Learning as I go. Thanks for any help/pointers provided!
I got another question. It appears that the new firmware has less space to install packages. The overlay folder has only 8.3M. Also, it appears that this space is disappearing fast by itself. Do you know what is the problem?
Let me verify this. Nothing has changed as far as I know.
The output of df-h on my router shows this:
Filesystem Size Used Available Use% Mounted on /dev/root 10.5M 10.5M 0 100% /rom tmpfs 124.7M 9.3M 115.5M 7% /tmp /dev/ubi0_1 8.3M 8.0M 0 100% /overlay overlayfs:/overlay 8.3M 8.0M 0 100% / tmpfs 512.0K 0 512.0K 0% /dev /dev/sda2 341.7G 104.2G 237.5G 30% /mnt/sda2
That definitely doesn't look good. Will investigate.
I bricked the device when trying to update to the latest firmware. I switched to the other firmware to get temporary internet. How should I fix it? I have linux, but no windows available.
I used this build in my EA9500 but I have a problem, I turned this router to access point but when I switch off this Access Point, my entire network loses connection for a few seconds then it turns back on. How do I prevent it from affecting my main router whenever I switch it on/off?
If the other firmware is not LEDE, unfortunately you have to use the serial cable.
That should not happen technically. You should raise a bug for LEDE. Or try to ask this on Installing and using LEDE thread. I'm sure someone with better understanding will respond.