Tingo: added Category

2016-06-07T22:05:47Z

added Category

← Older revision		Revision as of 22:05, 7 June 2016
Line 64:		Line 64:
	Since the function called for IOX is passed the IOX number as its		Since the function called for IOX is passed the IOX number as its
	only parameter, every device can thus find it's own datastructure.		only parameter, every device can thus find it's own datastructure.

			[[Category:ND100 emulator project]]

Roger: Created page with "==Coding for the IO/devices part of nd100em== To code for nd100em this document gives some information on how to add functionality easily to the emulator. IO functionality is ba..."

2011-07-15T06:15:29Z

Created page with "==Coding for the IO/devices part of nd100em== To code for nd100em this document gives some information on how to add functionality easily to the emulator. IO functionality is ba..."

New page

==Coding for the IO/devices part of nd100em==
To code for nd100em this document gives some information on
how to add functionality easily to the emulator.

IO functionality is basically done in two steps. The main
cpu threads executes IOX calls and thus for a device you
need a function for these IOX calls that return suitable
values or sets variables for the device. The actual device
then runs as a separate thread and does the real work.
To avoid race conditions we use a semaphore whenever we
access information in the common device structure created for
that device.

To add a new thread there is basically 2 functions we need
to consider:
<pre>
pthread_t add_thread(void *funcpointer, bool is_jointype);
void start_threads(void);
</pre>
The first one is the one actually initializing and starting the
thread, and the second is the main point where the emulator starts
all needed threads. This is where we would add a new device thread.
add_thread is called with two parameters:
* a pointer to our function, which from now on will run as a separate thread.
* and a boolean variable that if true tells the emulator the thread be waited for to join when it quits. If zero it is instead killed.

For example, the main cpu routine thread addition looks like this:
<pre>
thread_id = add_thread(&cpu_thread,1);
if (debug) fprintf(debugfile,"Added thread id: %d as cpu_thread\n",thread_id);
if (debug) fflush(debugfile);
</pre>
The main functionality for the cpu thread is done in another way.
Basically we have one array of 64k containing functionpointers:
<pre>
void (*ioarr[65536])(ushort);
</pre>
They are default initialised to a default function that fails
the IOX call after ~ 10uSec, as per real ND100 behaviour:
<pre>
void Default_IO(ushort ioadd);
</pre>
The routine that adds new IOX "device" functions is:
<pre>
void Setup_IO_Handlers ();
</pre>
We can take an example from currently added devices, the
onboard rtc on the cpu clock. It resides at IOX 10-13 octal,
and to add that one we have in the above routine:
<pre>
IO_Handler_Add(8,11,&RTC_IO,NULL);
</pre>
The parameters are start IO address, end IO adress (decimal),
pointer to function that handles device, and pointer to device
data structure. Last one is however not implemented, but thats
the way we will go.

We also have then the structure:
<pre>
void (*iodata[65536]);
</pre>
This if for the future IO device handling, as it allows reusing
the same function for multiple identical devices.
Since the function called for IOX is passed the IOX number as its
only parameter, every device can thus find it's own datastructure.

README-CODING-IO - Revision history

Tingo: added Category

Roger: Created page with "==Coding for the IO/devices part of nd100em== To code for nd100em this document gives some information on how to add functionality easily to the emulator. IO functionality is ba..."