I am getting this router later today (saving it from going into the garbage)https://openwrt.org/docs/techref/hardware/soc/soc.broadcom.bcm33xx?s[]=bcm3383 that leads me to https://github.com/tch-opensrc/TC72XX_LxG1.0.10mp5_OpenSrc
to search for a supported device you must use the table of supported hardware https://openwrt.org/supported_devices
and a search for that model shows nothing https://openwrt.org/toh/start?dataflt[Model*~]=TC7200
This device is not supported, you must first write the code to add support for it, and test on your device with serial console https://www.boards.ie/discussion/2057147563/upc-technicolor-tc7200-serial-console
see other people adding support for a new device as an example https://github.com/openwrt/openwrt/pull/3996
The github page you found is the source for original firmware and can be useful to read to get the information and specifications to add support in OpenWrt.
Thanks. Ill check this out and see what i can make of it. I dont have a serial cable. This might be over my head.
I got OpenWrt working on BCM3383:
main ← rikka0w0:bcm3380-20241014
opened 08:31AM - 03 Jan 25 UTC
# New SoC target support
1. Add necessary build scripts with `make menuconfig` … support to build images for BCM3380
2. Give you the option to choose the image packer between `hcsmakeimage` and `Broadcom's aeolus ProgramStore`. See `BCM33xx image packer` in `Target Images` option.
The `hcsmakeimage` uses its own lzma decompressor. For some reason, it is extremely slow. Luckily, Broadcom open-sourced the [Aeolus utility](https://github.com/Broadcom/aeolus), which allows us to utilize the built-in lzma decompressor of the stock bootloader. The image produced by Aeolus is smaller and loads faster.
__The original Aeolus only works on Linux x86 32-bit hosts. In this PR, it has been patched to work on both 32-bit and 64-bit hosts.__
# What works
1. After applying these patches, you can build a bootable initramfs OpenWrt image. You need to open the case and connect the serial console to your PC (115200, 8n1). You need to interrupt the boot process and use tftp to upload and boot the initramfs image.
2. The initramfs OpenWrt image will give you an interactive console over the serial connection.
3. CPU cache and SMP work. Both cores can run at their full strength.
4. SPI, OpenWrt can now access the on-board flash. (Updated on 2025/01/13)
5. OpenWrt can now detect the on-board ethernet switch (BCM53115). (Updated on 2025/01/14)
6. Ethernet works ~~(to some extent)~~ with my new Unimac driver.
__The Unimac driver is now interrupt-driven. It passes the iperf2 stress test, with a throughput of around 122 Mbit/s.
(Updated on 2026/07/08)__
7. USB, `lsusb` displays the VID and PID of the connected USB device. The USB OTG peripheral on this SoC is a thin wrapper around the Synopsys DWC2 controller, so the existing DWC2 USB driver in the kernel can be reused to support this SoC. (Updated on 2026/07/08)
# What does not work
Sort by priority. GPIO and pinmux may be easier to support.
1. ~~As of 2025/Feb/09, the ethernet driver uses polling for Rx, which adds unnecessary latency and high CPU usage.~~
2. GPIO and pinmux. Don't know how to test it. ~~Need to change a mux position in order to detect BCM53115~~.
The BCM53115 can be detected on the SPI bus, and its PHY status can be read. However, on this board, BCM53115 Port 4 is connected to the BCM3380 Unimac1 GPHY, and Broadcom-tagged packets cannot be passed to Unimac1 because this feature is only supported by the IMP and Port 5. As a result, the BCM53115 can only be used as an unmanaged switch on this board. Unimac0 does not have a PHY and is not used on this board.
3. ~~USB. The SoC has a different USB peripheral compared to BCM63xx. The biggest difference is that BCM3380 seems to support USB-OTG.~~ A driver has been implemented to support host-mode USB. (Updated on 2026/07/08)
4. PCIE. Dont have time to look at it. However, if we get the PCIE to work, having Wifi on CG3100D can be very straight forward, at the PCIE Wifi card already has mainline Linux support.
5. Cable model. Never expect this to work.
~~We can declare a victory if we can make the ethernet work...~~ Ethernet now works as expected.
More process can be found here:
https://gist.github.com/rikka0w0/4e4d5feb3a50a8b64224750140f859ef#file-cg3100-md
Boot log:
https://openwrt.org/inbox/toh/openwrt/netgear_cg3100d_v3
__Any help is welcomed.__