Wednesday, April 25th 2018, 6:54am UTC+2

You are not logged in.

  • Login
  • Register

Dear visitor, welcome to SEGGER Forum. If this is your first visit here, please read the Help. It explains how this page works. You must be registered before you can use all the page's features. Please use the registration form, to register here or read more information about the registration process. If you are already registered, please login here.



Date of registration: Jan 22nd 2008

Posts: 1

Location: Belgium

Occupation: Instrumentation engineer - Instrument R&D


Tuesday, January 22nd 2008, 3:07pm

Device drivers vs. embOS

I've got a more general question,

I've writen a large amount of device drivers (UART, SPI, CAN, etc...) in the past. All of them use there specific interrupt system (thru VIC) to get serviced in time. They are not writen with any OS in mind, they only use the compiler specific instructions to enable/disable the interrupts and push/pop the registers on stack.

If I want to utilize embOS as my main operating system, then what is the risk hence amount of work involved in doing so keeping in mind that I want to re-use most of my devices drivers.




Super Moderator

Date of registration: Nov 21st 2007

Posts: 65


Saturday, February 2nd 2008, 11:08pm

Basically you should be able to leave the interrupt service routines as they are.
Only if these routines need to call embOS functions (such as OS_SignalEvent),
they need small modifications; they need to comply with whatever the manual
says for the processor you are using (sounds like an ARM7).
The required changes for this type of ISR should not be major either.
An easy way too see what needs to be done is to look at the tickhandler
(usually in RTOSInit.c)

Similar threads