Hi Kent, It seems that the problem was indeed that the device was being passed through to the VM. In the `device.camkes` file, I had to remove `{"path": "/soc/pwm@12dd0000"}` from the `vm.dtb` list (I'm not sure what this corresponds to in hardware, I only found it through the process of elimination). I'm now able to build a camkes component using a TimeServer, and the VM is still able to boot. I'm surprised that removing the device from the VM didn't seem to have an adverse effect on its operation. This is all on an Odroid-XU4 (exynos5422 chip). Thanks, Grant Jurgensen On Thu, Apr 16, 2020 at 12:50 AM Mcleod, Kent (Data61, Kensington NSW) < Kent.Mcleod@data61.csiro.au> wrote:
Hi Grant,
I'm not sure what to make of this error. The only major difference between my project and the reference above is that I am building atop the camkes-arm-vm project. Could the VM be interfering here?
The interrupt is likely allocated already either because you are using a camkes-arm-vm configuration that's using a virtual console configuration and an instance of the TimeServer alreay exists as a dependency of the SerialServer component. Or as was already suggested, one of the devices being configured as passed through to the VM is the same timer device that the TimeServer is trying to use. Which platform are you targeting?
Kent.