Hello,
I hope someone besides me has had a similar problem. I am currently in a situation of either going back to OpenWRT 22 and being able to use my dtb file. In fact, I have only increased the operating frequencies in it from 1.5GHz/1.8GHz to 1.8GHz/2.2GHz. Yes, this is at my risk, from overheating the system. But I do this, and I have a definite idea of what I'm doing.
I think I had assigned MAC addresses to each card so they wouldn't change on a reboot.
Or to stay on OpenWRT 23, where the dtb file is apparently written directly to the disk itself.
It is unusual for me that a platform that is designed to be modeled according to the needs of the person working with the system does not allow such things.
I realize the idea that maybe there are people who are not very into it. But these people will not work with dtb files or anything else that would damage the system.
Another open source platform I didn't expect this from.
The source is there, you can modify it and build the resulting image.
Disclaimer: I have no personal experience with rockchip SOCs, so I have no idea if there are other approaches - and I guess that applies to a lot of other readers.
Thank you for your answer.
But I didn't understand why the boot architecture was changed and is there any way to do what I need.
Yes, I'll probably start compiling everything from scratch at some point, but that's a bit of a pain. Years ago, perhaps because of such proposals and decisions, LEDE appeared.
I personally am not a fan of many branches, distributions and sub-distributions, but this is my personal opinion and I do not bind anyone to it.
I've always admired how I can do with OpenWRT everything that other platforms don't offer. I was just pleasantly surprised at how this was changed. And it is not so much whether I will use my dtb file, but that such things are done. Will there not be other changes in the future that would prevent you from creating what you need.