Virtual machine for developing and testing target code for hardware designs
A host computer includes a memory storing a proxy VM, and a host CPU. The proxy VM emulates target hardware having an incomplete design. The proxy VM includes a virtual processor for emulating a target processor. The proxy VM includes an emulated memory coupled to the virtual processor over a virtual memory bus. The emulated memory includes at least one portion storing the target code. The host CPU is configured to execute the proxy VM to emulate the target hardware. The proxy VM, upon execution by the host CPU, is configured to execute, by the virtual processor, the target code.
1. A host computer comprising:
a memory configured to store a proxy virtual machine (VM) for emulating target hardware having an incomplete design, the proxy VM including:
an emulated Ethernet controller;
a virtual processor for emulating a target processor; and
emulated memory in communication with the virtual processor via a virtual memory bus, the emulated memory including at least one portion storing target code; and
a host central processing unit (CPU) configured to:
execute the proxy VM to emulate the target hardware, wherein the proxy VM, upon execution by the host CPU, is configured to execute, by the virtual processor, the target code to interact with at least the emulated Ethernet controller; and
update the proxy VM to omit the emulated Ethernet controller and to include a target hardware I/O device, wherein the updated proxy VM is reconfigured to execute, by the virtual processor, the target code to interact with at least the target hardware I/O device.
2. The host computer of claim 1 , wherein the proxy VM, upon execution by the host CPU, is further configured to execute at least one target code development tool.
3. The host computer of claim 1 , wherein the target code comprises at least one functional application that interacts with at least one peripheral hardware abstraction layer, and does not interact with corresponding peripheral hardware omitted from the incomplete design.
4. The host computer of claim 1 , further comprising a peripheral hardware device included in the target hardware, wherein the proxy VM further includes a hardware abstraction layer corresponding to the peripheral hardware device and configured to use host drivers for the peripheral hardware device upon execution of the target code by the proxy VM.
5. The host computer of claim 1 , wherein the proxy VM includes a virtualized peripheral hardware device corresponding to peripheral hardware that is not included in a complete design of the target hardware.
6. The host computer of claim 1 , wherein the proxy VM further comprises a virtual peripheral bus coupling the proxy VM emulated I/O devices and physical host I/O devices.
7. The host computer of claim 1 , wherein the emulated memory further includes a portion storing an operating system (OS) and a board support package (BSP).
8. The host computer of claim 1 , wherein the emulated Ethernet controller is coupled to an emulated peripheral bus, wherein the emulated memory further includes a portion storing test input data, and wherein the proxy VM, upon execution by the host CPU, is further configured to:
execute, by the virtual processor, the target code to operate on the test input data; and
write-out test output data over the emulated Ethernet controller in response to execution of the target code.
9. A method of executing target code for target hardware having an incomplete design, the method comprising:
executing a proxy virtual machine (VM) for emulating the target hardware for the incomplete design, the proxy VM including a virtual processor, an emulated memory, and a virtual communication interface comprising an emulated Ethernet controller;
executing, within the proxy VM, the target code stored in the emulated memory to interact with at least the emulated Ethernet controller;
gaining access to input data within the proxy VM;
operating, by the target code, on the input data;
writing output data over the virtual communication interface in response to execution of the target code;
updating the virtual communication interface to omit the emulated Ethernet controller and to include a target hardware I/O device; and
executing, within the proxy VM, the target code in the emulated memory to interact with at least the target hardware I/O device.
10. The method of claim 9 further comprising gaining access, by a host processor, to output data over a virtual bus within the proxy VM.
11. The method of claim 9 , further comprising executing, within the proxy VM, an operating system (OS) stored in the emulated memory.
12. The method of claim 11 , wherein the proxy VM further includes a bootloader coupled to the virtual processor and configured to load the OS and a board support package (BSP) from a portion of the emulated memory at startup of the proxy VM.
13. The method of claim 9 , further comprising executing at least one target code development tool coupled to the proxy VM over the virtual communication interface.
14. The method of claim 9 , wherein executing the target code comprises executing, within the proxy VM, at least one functional application that interacts with at least one peripheral hardware abstraction layer, and does not interact with corresponding peripheral hardware omitted from the incomplete design.
15. A non-transitory computer-readable memory storing a proxy virtual machine (VM) for emulating target hardware having an incomplete design, the proxy VM including:
a virtual processor for emulating a target processor;
emulated memory coupled to the virtual processor over a virtual memory bus, the emulated memory including at least one portion storing a board support package (BSP) and target code; and
a virtual communication interface coupled to virtual processor via an emulated peripheral bus, wherein the virtual communication interface comprises an emulated Ethernet controller;
wherein the proxy VM, upon execution by a host central processing unit (CPU), is configured to:
execute the target code stored in the emulated memory to interact with at least the emulated Ethernet controller;
gain access to input data within the proxy VM;
operate, by the target code, on the input data;
write output data over the virtual communication interface in response to execution of the target code;
update the virtual communication interface to omit the emulated Ethernet controller and to include a target hardware I/O device; and
execute the target code in the emulated memory to interact with at least the target hardware I/O device.
16. The non-transitory computer-readable memory of claim 15 , wherein the emulated memory of the proxy VM includes:
virtual random access memory (RAM) coupled to the virtual processor over the virtual memory bus; and
virtual non-volatile memory coupled to the virtual memory bus and storing the BSP and the target code.
17. The non-transitory computer-readable memory of claim 16 , wherein the proxy VM further includes a bootloader coupled to the virtual processor and configured to load an operating system (OS) and the BSP from the virtual non-volatile memory at startup.
18. The non-transitory computer-readable memory of claim 15 , wherein the target hardware and the proxy VM each do not include device drivers for peripheral hardware.
19. The non-transitory computer-readable memory of claim 15 , wherein the target processor and an operating system (OS) form the incomplete design.
20. The computer-readable memory of claim 15 , wherein the proxy VM includes a virtualized peripheral hardware device corresponding to peripheral hardware that is not included in a complete design of the target hardware.
21. A host computer comprising:
a memory configured to store a proxy virtual machine (VM) for emulating target hardware, the proxy VM including:
a virtual communication interface comprising an emulated Ethernet controller;
a virtual processor for emulating a target processor; and
emulated memory coupled to the virtual processor over a virtual memory bus, the emulated memory including at least one portion storing target code; and
a host central processing unit (CPU) configured to:
execute the proxy VM to emulate the target hardware, wherein the proxy VM, upon execution by the host CPU, is configured to execute, by the virtual processor, the target code to interact with at least the emulated Ethernet controller; and
update the virtual communication interface to omit the emulated Ethernet controller, wherein the updated proxy VM is reconfigured to execute the target code to interact with at least a target hardware I/O device.
22. A trainer system for a target hardware device, the trainer system comprising:
a user interface configured to receive input data from a user;
a host computer coupled to the user interface, the host computer comprising:
a memory configured to store a proxy virtual machine (VM) for emulating the target hardware device, the proxy VM including:
an emulated Ethernet controller;
a virtual processor for emulating a target processor; and
emulated memory coupled to the virtual processor over a virtual memory bus, the emulated memory including at least one portion storing target code; and
a host central processing unit (CPU) configured to:
execute the proxy VM to emulate the target hardware, wherein the proxy VM, upon execution by the host CPU, is configured to execute, by the virtual processor, the target code to interact with at least the emulated Ethernet controller; and
update the proxy VM to omit the emulated Ethernet controller and to include a target hardware I/O device, wherein the updated proxy VM is reconfigured to execute the target code to interact with at least the target hardware I/O device.
23. A test bench for an embedded system, the test bench comprising:
a host computer comprising:
a host communication interface configured to receive input test data;
a memory configured to store a proxy virtual machine (VM) for emulating a target hardware device having an incomplete design, the proxy VM including:
an emulated Ethernet controller;
a virtual processor for emulating a target processor; and
emulated memory coupled to the virtual processor over a virtual memory bus, the emulated memory including at least one portion storing target code; and
a host central processing unit (CPU) configured to:
execute the proxy VM to emulate the target hardware, wherein the proxy VM, upon execution by the host CPU, is configured to execute, by the virtual processor, the target code to interact with at least the emulated Ethernet controller to operate on the input test data; and
update the proxy VM to omit the emulated Ethernet controller and to include a target hardware I/O device, wherein the updated proxy VM is reconfigured to execute the target code to interact with at least the target hardware I/O device.