On Mon, Jul 14, 2014 at 12:20 AM, Alexander Graf <a...@antistatix.de> wrote: > Hi, > > I developed a software in the loop simulator for the Lego Mindstorms NXT > brick. It uses the Qemu ARM emulator to run the Robot's Firmware. I plan to > release the simulator as an open source project. Now, I wonder if it makes > sense to integrate the Qemu board implementation back into Qemu mainline or > simply maintain it as an external set of patches. > > The problem is that the qemu board I designed is not self-contained. It > allows the firmware to read/write IO memory in order to read back sensor > values from the simulated environment and to control actuators. The > environment simulator is an external program which is connected to several > qemu instances via posix named pipes using a simple communication protocol.
> Without pipe interaction the emulator can still be used to debug NXT > firmware images without sensor/actuator interaction. > Sounds like self contained functionality to me :) People have gone-to-list with less. > I'm happy to prepare a patch, but do you think it is of any value to > integrate code that is not 100% self contained? > Many first-round series are not self contained and tend be not much more that "boot the bare minimum software and lets add I/O features later". Regards, Peter > Best Regards > Alexander >
