Searduino - Arduino simulator and C/C++ devel environment
This is a modal window.
The media could not be loaded, either because the server or network failed or because the format is not supported.
Formal Metadata
| Title |
| |
| Title of Series | ||
| Number of Parts | 90 | |
| Author | ||
| License | CC Attribution 2.0 Belgium: You are free to use, adapt and copy, distribute and transmit the work or content in adapted or unchanged form for any legal purpose as long as the work is attributed to the author in the manner specified by the author or licensor. | |
| Identifiers | 10.5446/40321 (DOI) | |
| Publisher | ||
| Release Date | ||
| Language |
Content Metadata
| Subject Area | ||
| Genre | ||
| Abstract |
|
FOSDEM 201320 / 90
2
5
8
10
12
13
14
15
17
19
21
24
25
28
29
31
32
34
36
39
40
43
44
46
50
51
52
54
55
57
58
62
65
66
67
78
79
87
88
00:00
Moment (mathematics)Embedded systemNP-hardWhiteboardUniverse (mathematics)Multiplication signThresholding (image processing)Java appletIntegrated development environmentComputer hardwareComputer programmingLine (geometry)Perfect groupProjective planeComputer animation
00:58
Student's t-testComputer programmingHeegaard splittingLine (geometry)Execution unitStudent's t-testMultiplication signComputer fileLecture/Conference
01:36
Hausdorff spaceWhiteboardExecution unitComputer programmingLine (geometry)Endliche ModelltheorieUnit testing
02:00
PlastikkarteWhiteboardDegree (graph theory)Software testingSoftware testingIntegrated development environmentQuicksortComputer programming1 (number)Functional (mathematics)Universe (mathematics)Lecture/ConferenceJSON
02:35
Unit testingComputer hardwareComputer programmingElectronic mailing listJava appletExecution unit1 (number)Presentation of a groupInterface (computing)Personal identification numberoutputExtension (kinesiology)WritingCodeStudent's t-testStandard deviationComputer simulationTouchscreenLecture/Conference
04:12
Computer programmingLie groupReading (process)Function (mathematics)Line (geometry)Personal identification numberSource codeXMLProgram flowchart
04:47
Vapor barrierIntegrated development environmentLecture/Conference
05:31
Function (mathematics)Personal identification numberPlotterStudent's t-testComputer simulationText editorCodeLine (geometry)Computer programmingWhiteboardNP-hardMultiplication signDreizehnMaxima and minimaDigitizingRight angleObject (grammar)System callGoodness of fitSource code
08:10
Type theoryBuffer solutionComputer fileRevision controlLibrary (computing)Lecture/Conference
08:30
Computer simulationJava appletSource code
08:47
TouchscreenRight angleGroup actionMultiplication signComputer simulationDigitizingFunctional (mathematics)FeedbackObject (grammar)outputStudent's t-testPersonal identification numberSource code
09:40
Personal identification numberFunction (mathematics)Source codeComputer animation
10:11
PRINCE2outputFunction (mathematics)Computer simulationComputer programmingDigitizingPersonal identification numberSimilarity (geometry)CodeSource code
11:17
Social classJava appletComputer simulationSocial classObject (grammar)WhiteboardProcess (computing)Computer programmingComputer architectureMultiplication signQuicksortInterface (computing)Java appletCodeJSON
12:29
Error correction modelDirection (geometry)Computer fileMultiplication signOnline helpComputer simulationImplementationComputer programmingPlug-in (computing)WebsiteWeightProjective plane
13:40
ImplementationStructural loadProjective planeLecture/Conference
14:01
Programming languageWebsiteComputer animation
14:24
Keyboard shortcutSerial portPersonal identification numberBound stateComputer simulationAnalogySerial communicationUser interfaceChemical equationSoftware testingInstance (computer science)Condition numberLecture/Conference
Transcript: English(auto-generated)
00:00
waste too much of my time. This is basically me. Let's get this over with. It's my role at the university. Oh, you want me to speak in this one. I always move around. But I get the rock star kind of feeling here. We, in one of our courses on embedded programming,
00:20
we switched and started to use Arduino. It was perfect, it was easy to get started with. The IDE lowers the threshold. When we introduce the Arduino or other hardware and show that to people who are new to programming,
00:42
they've just learned Java and all of a sudden we show them the command line, we show them scary tools, we noticed that when we introduced them to Arduino using the IDE, it was perfect, way easier. But, doing that, we faced some problems.
01:01
The problem is I usually read here, but I can't do it right now. So I'm going to show you my back. When we made a bigger project, not the example you see in the Arduino, it was a couple of hundred, couple of thousand lines long program split into many smaller files,
01:22
developed by several students at the same time, we had a problem. We tried using Git and cut, paste and blah, blah, blah, it didn't work. We missed unit testing a lot. We... It's not as if you are recommended to use malloc and calloc in embedded programming.
01:45
Still, it's good to do some unit testing every now and then to check the logic. And we noticed that it's pretty lame. You're developing this 4,000 lines long program,
02:01
you spent hours, weeks, and all of a sudden, the lead doesn't blink anymore. So you have to debug it, sometimes using, well, code review. So we had a problem with that. And we also needed to automate the tests. So we realized that we...
02:24
We had to write a sort of a fake environment. So basically, we took the Arduino API, implemented every fun... Oh, not every, but almost every function, the ones we use at the university. So we could create a program that could run by itself with no hardware.
02:46
And then we added some small standard out, standard in interface to it. So we could set, for example, input pin one to one and see what happened in the code. But after a while, when we did that, we realized that we were almost done writing a simulator.
03:08
So we finished one, we wrote one. And we got some complaints from students that didn't want to write unit tests in C.
03:20
So we wrote a Python extension to it, so they could write the unit tests in Python. And for the fun of it, I added a Java extension, because I needed to refresh my almost totally forgotten Java skills.
03:50
I want to show the classic Hello World example. It doesn't do good, because there is no screen here. So I'm going to do it using a Blinken list.
04:02
So let's see what happens here. I'm afraid of this presentation program. So here is a Blinken-led program. Also, there's some reading of one pin to another.
04:21
But if we focus on these lines here, it basically puts the output on pin 13 to one and takes it down again to zero. So it should blink. If how many have done these kind of things in front of a live audience and gotten away with it,
04:48
now it blinks. But let's try and upload this one. I'm going to show one of the most used features of the simulator. This is, by the way, the Arduino IDE, which is lovely.
05:03
It really helps people to get over the first barrier. So I'm not here to bash this IDE in any way. But let's upload it. And let's see when the LED blinks. Problem is that it doesn't blink.
05:20
And this was something we... Excuse me? Oh, damn it. Oh, no, you weren't supposed to see this. Damn, what a disaster.
05:42
I'm going home. Problem is my flight is on Monday. If I only can see my mouse again. Anyhow, plot is I'm going home. A lot of times, I'll never do that, which I just proved.
06:02
A lot of times, the students forgot to say what kind of pin 13 should be, or whatever pin you want to talk with. And if you don't set the output to 13, oh, sorry, this pin 13 to an output pin, you cannot write to it. So this code is writing to the LED, but nothing happens.
06:25
So now I'm going to show the simulator and how we develop code.
06:40
I'm using my favorite editor. Some of you may recognize it. It's Emacs. It's the only one I know. OK, so this is basically the same code. It's writing to digital pin 13, first a 1 and then a 0. Basically, that's all that happens.
07:02
So that's it. So I'm going to show you how we develop that. This is kind of hard.
07:21
The only thing I do, I write a couple of, these are all the lines that I need to write as a makefile. And I here put the board. I want the program for UNO, but since the program didn't work, we are programming for something we used to call stub.
07:42
It's not a stub anymore, but the name is still here. So what we are doing is we are basically saying that don't produce code for the actual Arduino, but produce code to be run locally on this one. How am I doing on time?
08:03
Good, but good depends on how much more I have to say. Perfect, thanks. So what the program does, or what Arduino does for me now is given the C file that you saw in my Emacs buffer and the small make file, it produces a shared object, basically dynamic library.
08:22
And somewhere in the history here, I should have had, I have an installed version here, and I do type crappy.
08:41
So I fire up the Java simulator. It's a big one today on this screen. I open up the newly freshly compiled shared object. And what we can see here is, this time it's actually
09:05
not a flaw in the simulator. You're seeing a lot of printouts here. It's warning. You're trying to write with a function digitalWrite to pin 13. Let's stop it and look at the rest.
09:23
Which is an input pin. This was great value for the students. All of a sudden, they could get feedback from the simulator saying that, oh, you're writing to pin 13, which is an input pin. So some of them ask me, what do we do now?
09:42
And yeah, simple answer was, you need to initialize it as an output pin. And this is what I do here. So if I recompile it now as a shared library
10:07
and open it up again, I can choose board here. But let's continue with.
10:20
All of a sudden, we don't have any warnings. And we can see the pin 13 going berserk. So we can actually test that it is working. Nice, fine. And if we would have made a similar mistake as before, we would still see some warnings here.
10:42
I just want to show you that we can also read the input pins. So in the program, if I click input 10 goes high, digital output pin 11 should also go high.
11:01
And in a rather slow fashion, it does. It's not due to the simulator, but the code that the simulator is running. So let's try and quick.
11:25
With this program, you develop C, C++ code that you run on the Arduino. You build it for Arduino, any board. You can run it as a standalone program. Basically, an ELF program, you run it.
11:42
Or the best way, if you want to use the simulator, produce a shared object, upload it to the simulator, and run it. This is the basic. There's a couple of other simulators. But I'm running out of time, so I'm just going to show the Java sort of architecture here.
12:04
This is the Arduino code built as a shared object. It's loaded by Serduino. We have a simulator API called CSIM. On top of that, we have a Java class that wraps all the simulator into a Java interface.
12:22
And Jerduino, we're not very good at names, is the Java simulator. That's it. We've done that. This, I'm happy that you can see.
12:41
It would be great to have some people join us to develop this program further. We need more implementation of the Arduino API. I think it would be pretty cool to have an Eclipse plug-in. Somehow, I don't know how. Make it possible to load Arduino's .ino files.
13:02
Basically, the Arduino files you get with the Arduino is C++ files, but they are called .ino. It would be pretty cool if you could load them into a simulator directly. What we've done so far is we can take an .ino file
13:20
and convert that into a C file, create some make files around it. So we're almost there, but we need some more help. We're running out of time. Given the amount of time I have given the three kids and everything else I do, we shouldn't
13:42
have an active project. But it's listed on one of the sites, ollo.net, that it's very active. So it is active, I think. We are building it every night using this tool, VMM, which is going to be, they are here. They're going to present something tomorrow.
14:03
Why the name? C, as in the programming language C. And one of my favorite book was called Deep Sea Secrets, so I thought the joke was so funny. So I wanted to have C. Well, you get the joke. I think, do we have any Swedes here?
14:24
OK, sorry. I'm from Gothenburg, and Gothenburg are known and hated by the rest of Sweden for their crappy jokes, and we always want to play around with stupid names. And this is a result, so don't kill me. Sorry. I apologize. Questions?
14:41
Nothing. OK. Yeah. Yes. Can you simulate analog conditions, like analog voltages and, for instance, spin button bounds and things like that?
15:02
What was it? Pin button? Sorry? I couldn't. Can you say it again? I mean, can you simulate analog inputs? Not analog out, because it's PVM, but yeah.
15:21
And things like button bounds, for instance, that would be useful to try? I don't know. Perhaps it is possible. I don't know. The serial interface, for example, is implemented. And that is not answering your question.
15:41
So let's talk afterwards. I just want to say a stupid mistake, because I implemented the hit, the human interface thing. So I have a Leonardo, which was stolen the other day. And you can now simulate the mouse and keyboard stuff. But it turned out that when I did that using the simulator,
16:02
it grabbed my mouse. So I couldn't stop the simulator anymore. And it kept running forever.