aaand it's really stupid..... upstream kernel already have offload api... so qca keep using they own ancient code that requires major kernel patch is not sane at this point....
for this exact reason reintroducing sfa logic doesn't make any sense since we already use the offload path of the upstream kernel.
(or they are starting using the ppe directly without using nss to set them up... )
@robimarko our suspicion was right... looks like nss was actually doing some ppe stuff under the hood and now they just had the big idea of just dropping the nss complexity and just leave the kernel handle all the stuff... pathetic the thing that with now 4 soc based on the same damn switch they still didn't consider the idea of creating a correct dsa driver...
If you installed QSDK then that fiddles with the partitions and then running the Mi repair tool results in at least a soft brick. I think I've read somewhere (but may be completely imagining it too!) that the repair tool also resets uart_en back to the default of 0, but then I'd expect it to also reset boot_wait as well but your boot_wait still looks to be enabled.
There isn't any chance you accidentally hooked up something not 1.8V to the router's RX?
At this point unfortunately you look to have a hard brick and the only fix would be to reprogram the NAND, not such an easy job.
we should really understand how to enter the real recovery mode... we had some doubt ipq806x had this kind of mode... but ipq807x? 100% it does have it. It's based on ancient cpu stuff but still it's ""modern"" so qca must have put some kind of debug/flash way that are enabled with the first stage of boot. Problem is lack of any documentation but we should try and check if any of these recovery mode are present following how it's implemented in comparable qcom phones.
In a perfect world yes, but as in the case of my bricked AX9000 with a borked DEVCFG partition, there is no logic in the boot sequence to try the identical DEVCFG_1 partition. The bootloader is fully aware DEVCFG is bad, and rather than think to try DEVCFG_1 it just gives up.
There may be JTAG, but on these consumer devices that's more an afterthought. I don't imagine Xiaomi put any effort in making these recoverable beyond the repair tool.
There is really little detail on the IPQ95xx, it would be extremely weird if they moved away from using NSS as the cores are still there.
Why would they use SFE again compared to the whole NSS ecosystem, maybe they have a big customer that doesnt want it or something.
IPQ807x has a USB recovery mode, but it requires tools that are under NDA and all of the DEVCFG, etc blobs
Mhhh i assume the tools are the same used by the phones... aka special cable with specific resistance. but rip for all the other tools. Also i assume for ax3600 no usb so someone has to search the pinout...
mhhh don't know the fact that they are working on ath12k (wifi 7) and probably them finally using more modern cpu makes me think they are just starting from scratch and dropping nss for good
No, the tools are just SW but are under NDA for whatever reason.
But it's pretty much meant for development as you need SW binaries that you would only have as the vendor.
Other than that you can use JTAG, but only scripts provided are for Lauterbach Trace32, otherwise you need to manually enable the DDR clock and some other basic stuff to be able to load the U-boot to memory and run it to flash whatever you need
Its hard to guess why QCA does stuff, I would be really like really surprised if they stopped using NSS.
I have an AX6 auto-bricked with uart off on the shelf waiting for a recovery method for a few months ago...
I have seen a interesting method with xiaomi AX6S (MediaTek) for get u-boot with UART enabled interrupting tftp recovery process a few days ago. I know it is other soc but I would try it. Since AX3600 firmwares do not have u-boot partition whitin I think the risk for get things worse is low...
Anyway this is just an idea I am not sure at all and if someone thinks that this is dangerous or anything, please tell me soon. (* I can not try this in my AX6 because it does not even start tftp recovery proccess.)
*Do not use openwrt images or anything else of AX6S thread, it is only about the tftp recovery proccess interruption.
when enabling the qca crypto device, qca-nss-drv is enabled by default. Is there any hint for me, how to get this compiled for 5.15? the old patch from @Ansuel for 5.10 doesn't work for me.
I've tried different time!
1 when finished uploading
2 when begin to erase
But when repluge power begin countdown and i can't send any command
putty log https://bit.ly/3OJSnLV
I made mistake about one configuration. When i made a dump Ap mode i forgot to go on my main router and configure the dhcp within a range 2-254 . I used 2 to 220. And the ax3600 dump was 254. Thanks anyway sqrwv.
Because i am a noob my question is how can i install package for extra module like openvpn etc. ?? Can i install from ssh via console or via the opkg installer inside the menu of openwrt?