Timeline for Designing Embedded Software
Current License: CC BY-SA 3.0
5 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Jul 30, 2012 at 16:35 | comment | added | Wouter van Ooijen | "most RTOS's are not written in an object oriented language" Indeed. But for a course in real-time modeling and implementation we use a simple (non-preemptive) RTOS in C++. | |
Jul 30, 2012 at 1:55 | comment | added | Cassio | Yes, I'm still getting familiar with the RTOS features. And thanks for the suggested approach! Will do it! And as I said before, I'm new to embedded software, I'm not really sure what's necessary. It would be nice to have an Embedded Software Architecture or Design Document. Would you have one of those? | |
Jul 30, 2012 at 0:53 | comment | added | Jon L | @Cassio, I'm not telling you to do one thing or another, that's really up to you. Just try to do what's necessary. If you're unfamiliar with your RTOS, I think just getting started with it first and how you're supposed to use it would be a good place to start. Then you can start designing your tasks around it. | |
Jul 29, 2012 at 23:45 | comment | added | Cassio | Thanks @JonL. So, in order to have a nice Design Document, I would just need to design the tasks involved in my application? Also, I'm not very familiar with a scheduling algorithm, I've never have to deal with it. I'm using RTEMS. | |
Jul 29, 2012 at 18:17 | history | answered | Jon L | CC BY-SA 3.0 |