I agreed that it is not OpenWRT issue but we have posted here if someone had faced this type of issues at his or her end.
We have checked that default boot loader is working fine with reset command but when we updated boot loader with compiled boot loader at that time reset is failed to work.
Same issue we have faced after updating sysupgrade image as well like reboot command is not working
Let us know if anyone has faced and resolved that type of issue into current boot loader build.
OpenWrt = hardware + bootloader + openwrt firmware.
Although the bootloader not maintained by openwrt team, but it's a very important part of openwrt system also.
You are absolutely correct. We assumed that Boot Loader is not part of OpenWRT fully but partially it is part of OpenWRT as without boot loader we can't move further.
I understood your concern. But practially i have posted thread over here to help us if anyone has faced this type of issue while using compiled version of boot loader into AI7688H based modules or chips.
Also I would let you know that AI7688 Update Issue has been resolved from our end and we are able to update boot loader and sysupgrade image successfully from boot loader using loadb command.And that is totally different compare to issue which we have right now posted to get help if anyone has faced it.
Hope you can understand it our concern and query for the same
Compiling uboot isn't really all that difficult for the MT7688, even if one just grabbed mainline uboot instead of the preconfigured setup these guys are using, so I am just dying to know what did they mess up to break reset? The curiosity is killing me.
I think it's a tad harsh to ask for them to be banned, just because they're looking for help in multiple places.
OpenWrt-forums ain't exactly the most correct one, sure, but trying here is somewhat logical, considering how many of us here do have some programming-experience and may even have dealt with uboot as well.
That’s certainly fair enough, the multiple postings of exactly the same content rubs me up the wrong way, as well as not acknowledging that the vendor had already responded through the correct channel.
But we do support the power supply also in this forum😄
Not to mention what high voltage symbol to use for the wiki warning a while back.
I don’t see the point of banning a question that actually is inside the physical hardcover of the devices we support. If we do that it will come back and hit us.
Firmware dev isn’t that black and white.
We have the support treads of BanIP and AdBlock in this forum also, why do we allow them? They are not OpenWrt.