Do you want to explore your router and do the porting, it might be very similar to other device plus two modems.
you want find a better offer than that .. anywhere. Get a serial connection and provide him with what he asks for to do the port. It likely won't take him but a day to complete it if you provide him the information about the device
What info is needed
A peek at the bootlog to start things off ...
yeah, and this is where it'll crash and burn ...
Let’s begin with the output of the following and zipped file of the /lib/firmware directory:
dmesg (for boot log)
cat /proc/mtd
find /sys/ | grep fdt (and send that over)
so ?
still no IPQ50xx in mainline, and def not in 5.15, means it's probably a QSDK, or someone ported the IPQ50xx code to 5.15, which is still useless, since it needs to be in 6.6.
new devices are added to master, not the current stable.
why not provide what was requested to get your device supported, and quit wasting time on the stock stuff. Your intention is to have openwrt running on your device is it not ?
.... which will get you exactly nowhere.
You know, cudy provides source code and you just need to forward engineer it using code editing.
Thank you for the AI generated content.
We knew all this already, you're (the AI really) kicking in an open door.
Ever heard of PCs booting without u-boot ?
In process of building Openwrt 18.06
Will update to latest openwrt version
Once I have built working firmware for device
Cudy source is not OpenWRT. You can build minix2 as well for same no-op effect.
Most people would have dropped the building, when they were told there's no SoC support in mainline...
You should change your forum name to Sysiphus.
ipq50xx-qsdk-kernel-5.4-openwrt-21.02-qsdk-11.5.05.841.1029
most up-to-date stable Openwrt version
I possibly could build with
Pointless, as you were told a week ago.
Enjoy your outdated, unsupported, QSDK based "Openwrt" release.
Mate, this is pointless as the gpl source is not OpenWRT, it’s a heavily modified, outdated, qsdk based version. If you have the dts, or at least have serial access and provide me with the info I requested earlier, I can add an initial image for your board which you can further customize if needed, based on current snapshot..
I do have a dts file
Link to dts file
You can't emulate an existing plastic router with qemu. These are embedded devices, ARMv8 is only one puzzle piece, everything else (hardware drivers, GPIOs, pinmux, clocks, etc.) are SOC specific and not emulated by qemu (but exactly those matter most (>>98%), if you want to confirm if your device support patches are actually working), which does not know anything about ipq50xx nor your device.
--
Yes, it is not technically impossible to write a semi-accurate emulation of ipq50xx or your device, but that would be a very major undertaking - much harder than getting your device working on OpenWrt in the first place (and even then the accuracy is probably hit or miss). This is merely a theoretical idea, not realistically going to happen - or possible.