Hi there. I'm relatively new to ARM SBCs, however 3 or 4 boards I used to work with gave easy and sensible way to manage peripherals: uEnv.txt for uBoot in Texas Instruments, or at least boot.cmd in sunxi.
Here (nanopc-T4) we have hidden bootloader AND kernel, and if someone needs to add (or better DEBUG) a device, he encounters lots of pain having to recompile everything each time - and flashing the image! Being a noob I lost my root system once already.
Is this cumbersome, opaque and inconvenient boot arch the property of the CPU boot manner, or is it Ubuntu? Is there a way to config peripherals just by editing a text file like everywhere, or at least by compiling a dts and putting it onto filesystem, not hidden flash area?! Surely uBoot can do this. Where's the obstacle???
Or am i too dumb to not see some obvious things? Thank you.
Here (nanopc-T4) we have hidden bootloader AND kernel, and if someone needs to add (or better DEBUG) a device, he encounters lots of pain having to recompile everything each time - and flashing the image! Being a noob I lost my root system once already.
Is this cumbersome, opaque and inconvenient boot arch the property of the CPU boot manner, or is it Ubuntu? Is there a way to config peripherals just by editing a text file like everywhere, or at least by compiling a dts and putting it onto filesystem, not hidden flash area?! Surely uBoot can do this. Where's the obstacle???
Or am i too dumb to not see some obvious things? Thank you.