| Real OSGi Programmers Do Embedded! (Tutorial) |
| [Approval Rating 93%: 14 Positive, 1 Neutral, 0 Negative] | See the official EclipseCon session information… |
Much of the emphasis on OSGi in the Eclipse community is focused on the desktop and the server. But OSGi brings many advantages to the world of embedded as well. This tutorial introduces attendees to the best practices in applying OSGi to embedded applications by walking through building a simple embedded application.
The day will cover best practices, suggested workflows, tooling usage, Equinox runtime launching, and client management. Provided with a simulated sensor device, access to some real devices, a user interface shell, a client bundle manager, and an off-board communications channel, attendees with build and deploy an embedded application.
| Get the papers! | ||
 |
M0 Setting Up Your IDE (1.7 MB) | |
|
M1 Running the Simulation (1.2 MB) | |
|
M2 Put On A Happy Face (1.6 MB) | |
|
M3 The Rubber Hits the Road (2.2 MB) | |
|
M4 Creating a Programmable Thermostat (1.2 MB) | |
|
M5 Adding a Fan Control (212 kB) | |
| Take the Fat Man Off Your Application (Long Talk) |
| [Approval Rating 95%: 54 Positive, 3 Neutral, 0 Negative] | See the official EclipseCon session information… |
Why does your application run so slowly? I bet you think its the algorithms, or the fact that you are starting all your services instead of using extension points. It runs so slowly because there is carrying a fat man sitting on it. No one can run fast when they are carrying that much dead weight. Experience has shown me that the performance problems are never where I expect them to be. The things that I initially think will be problems often never even show up in the trace, and code blocks that I can’t believe often dominate the execution time. Over time I have found many of same blocks showing up very high in the trace. These are fat men and they need to be removed before we can find the performance problems in our algorithms.
In this talk we will look at profiling a real world embedded Java/OSGi application to remove the fat men, and maybe even some of algorithm problems in my code. The application ran fine on my laptop but took over a minute to start and ran out of memory when put on its intended embedded target. By the time it was deployed it started up fine, and ran for days without running out of memory. It will be part experience report, part best practices, all fun!
| Get the papers! | ||
 |
Take the Fat Man Off Your Application (6.7 MB) | |
| Eclipse as an Automotive Runtime Platform (Birds of a Feather Session) |
| [Approval Rating Unrated] | See the official EclipseCon session information… |
Some people think it’s crazy to conceive of running Eclipse and Equinox as a runtime platform for in vehicle computing. If you know anything about the Eclipse Community, you know that nothing is impossible when the right people come together to tackle a problem. Eventually, they will make something interesting happen. Several Eclipse community companies are cooperating to demonstrate Eclipse as a runtime platform for automotive telematics and infotainment applications. In doing so, we hope to:
- Validate Eclipse/Equinox for runtime applications for embedded telematics and infotainment
- Showcase Eclipse Community collaboration by involving several Eclipse companies
- Highlight component architecture and platform flexibility with one hardware platform, one application, multiple operating systems