|Subject:||Re: [Qemu-arm] [Qemu-discuss] Custom board with DTS/DTB|
|Date:||Wed, 7 Dec 2016 16:34:51 -0500|
On 5 December 2016 at 17:51, James Hanley <address@hidden> wrote:
> 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.
The problem is that DTC is not designed for that job. It describes
those aspects of the hardware that the kernel cares about, which
overlaps with but isn't the same as the information that you would
need to build a complete model of the hardware. So the idea has been
suggested before but I think it would in practice be pretty unreliable
(and for 99% of dtb files it would just not work anyway, because QEMU doesn't
model the devices that the dtb describes).
> 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.
M-profile is different and doesn't generally use boot.c -- the board
model code ends up calling armv7m_init() which treats kernel_filename
as a random ELF file. (A profile --kernel will also treat an ELF
file as an ELF file, it just has special casing to handle Linux kernels and
assumes a raw binary is a kernel.)
If you're running one of the 2.8 rc candidates you can also use
-device loader to load an arbitrary file (see docs/generic-loader.txt).
|[Prev in Thread]||Current Thread||[Next in Thread]|