simduino

Here's a chat regarding Simduino...

11:50 Where did the simulator come from?

Carl 11:50 AM simavr is a project on github 11:50 It’s fairly widely used.

David Peterson 11:50 AM cool

Carl 11:50 AM The simulator engine is an XPC service that mostly just wraps simavr. 11:51 It’s one of the few parts of S4A that’s open source, because it links simavr directly, so it has to be as per the GPL 3 license. 🙂

David Peterson 11:51 AM Hah, right

Carl 11:51 AM https://github.com/swiftforarduino

Swift For Arduino Community Where we can come together and share ideas and code for the Swift for Arduino platform. Repositories 6 https://github.com/swiftforarduino|@swiftforarduino@swiftforarduino | Aug 2nd, 2017 | Added by GitHub 11:52 Here you can see a couple of other interesting repositories, as well as the main (community) site.

David Peterson 11:52 AM I noticed that simduino tends to consume a lot of CPU in the background

Carl 11:52 AM a fork of simavr, the simduino XPC service and some sample projects

David Peterson 11:52 AM Is it possible to turn it off completely when I’m not actually testing stuff?

Carl 11:52 AM Yes, simavr is a CPU pig, like a lot of emulators. 11:53 yes, you can shut it down 11:54 Simduino should close when not used. The debug panels at the bottom of each project open a serial port connection either to a board or to the simulator’s virtual UART. In order to shut down the simduino and stop it burning your laptop battery, close the debug panels on any project that’s connected to the simulator, and also make sure the simduino “virtual board” window (with a picture of a virtual board) is closed. 11:55 That should result in a “simduino closed” message on the build panel and you should see the CPU usage drop.

David Peterson 11:55 AM Ah ok 11:55 I haven’t been closing the debug panel

Carl 11:56 AM Do you mind if I drop the contents of this chat on the wiki? One of the core team pointed out whenever I do a brain dump on a subject like this that might be useful for others, I should try to put it on the wiki, to make up for the lack of documentation a bit!

David Peterson 11:56 AM Sure, no problem