I'm moving my query to QEMU-Arm since it seems more applicable here.
1) It seems that the -dtb option is not what I thought it was, but would something like what I thought was the intent of the option be of value to QEMU, that is to define the board support package for the system using DTC to compile and pass into QEMU to define a generic board from the tree, rather then defining the hardware within the code base of QEMU? I understand that there will always be some need for device support and deginition from within the codebase, but this was more to allow the user to define hardware board profiles without having to change source code.
2) Right now, I'm trying to run our embedded application (EmbOS RTOS with DLib with our application support all targeted for Cortex-M4 MPU) and it seems like QEMU (at least from variable names) wants to believe that under boot.c and loader.c that the passed in application (using --kernel option) is linux. Is this proper behavior - or is there someway to pass the statically linked code-flash binary to execute? Our binary is note Linux, and is running EmbOS an RTOS. Note that this CM4 module executes from code flash.
Thanks much,
-Jim