You have made a bizarre assumption that your readers were aware of what
"NutOs" is. I assume you mean Nut/OS
(http://www.ethernut.de/en/software.html). You should probably always
post a link to any third party tool (i.e. not supplied with
WinARM/ARM-GCC distributions)

I would not expect any RTOS to prevent you from directly accessing
hardware registers, so there are no particular issues with using one and
doing low-level hardware access I/O is the job of your application not
particularly that of an RTOS, which is primarily concerned with
scheduling and communicating between tasks.

What you do need to be wary of however is mutual exclusion. When one
task is accessing a resource (such as an EEPROM or interface used to
communicate with one), other tasks must be prevented from doing so. The
usual method is to use an RTOS mutex semaphore. Nut/OS has
non-preemptive cooperative multi-threading, so you will not need to use
a mutex - just make sure an operation is complete before yielding, or
use flag to prevent access is an operation must yield mid-operation. The
simple approach is merely to restrict all access to the resource to a
single thread. Where multiple threads require the resource, you can use
a "server thread" that receives requests from other threads to access
the resource in a controlled and sequential manner.

Now how you actually communicate with your device is not possible to say
until you decide what device to use and how to connect it to your
processor. But is is a matter of reading the data sheet for both and
connecting the appropriate interface. Serial EEPROMS are typically
either I2C (TWI) or SPI devices.

Clifford

Yes, of course it is Nut/Os (ethernut) - http://www.ethernut.de