The bootlog you put on pastebin seems to throw out some garbage earlyboot ( uboot )
So, either it's some sort of obfuscation i'm not familiar with or you'd need to have your serial device on another setting ( common cause of scrambling then unscrambling ) during the early boot stage to interrupt ( if it's possible - most are )
Search up on your device..... re: bootloader baud changes and interrupt key sequences.
( next common one to try would be 38xxx whatever it is..... and then 56xxx )
Oh, I understood. This is why it wasn't accepting any sort of command.
Anyway, now the descrambled part of the bootlog is showing some memory addresses and more filesystem info. Is it of enough help for at least some test builds?
TEST being the operable word.... Without an initramfs recipe and / or a way to boot from tftp / usb .... Physical access and someone who knows seama / dlink firmware idiosyncrasies would be advisable.
Glad to hear this, but if I understood right: testing is not done by "cooking" bin's and flashing them in emergency/recovery mode (which accepts "any" firmware)? There shouldn't be a need for tftp.
Sorry if I appear too simple, but: take openwrt from dir-859 (edit: 869 also similar, all revisions?), put qca9888 driver and the hw addresses found in bootlog. And done. It should just work, isn't it?
This is where my limited knowledge and availability of tools ends. Advanced software and hardware is something that I won't be able to help with. I can learn and acquire them, but it takes time and money.
However I am perfectly willing to:
Try and find someone to do a hexdump on the memory, in the process desoldering it and destroying the router.
Mail it in Europe (or even somewhere else not too far away from Romania) via post service, it's dirt cheap.
Risk bricking the device with even the most poorly built firmware, with the poorest of boot tricks stuck-together.
The C2 support has been merged into master. That image should work on C1 as well.
If someone is ready to test, it is quite easy to add official C1 support.
Mainly because the USB on C1 can be modded with some soldering skills. So people wont have to recompile the image if they have a modded C1, they just have to install kmod-usb2
This is not the way it is normally done. Those who can solder USB can also build an image with modified dts.
Otherwise I don't see a reason of having a separate image for c1. We could have one for both c1 and c2 since the only diff is the USB.
Has anyone actually confirmed that GPIO 15 is correct for the power / status LED ?
I'm just wondering why it's constantly on during boot, rather than showing the typical OpenWRT flash pattern to allow for entering failsafe mode.
Also I noticed that 2.4 GHz wifi will use the label mac in OpenWRT (i.e. the same as for LAN), rather than the WAN mac as the stock firmware would do. Is this intended behaviour so that wifi would use the same MAC as LAN?