Re: Getting started with bare-board development

["Jeffrey R. Carter" <spam.jrcarter.not@spam.not.acm.org>]

On 11/13/2016 01:03 PM, Adam Jensen wrote:
>
> When writing device drivers, how do you mock the memory map of the
> target hardware?
>
> In the mocked the hardware, how is timing controlled?
>
> When extending and mapping run-time support to the mocked hardware, how
> does that fit into the run-time system for the native platform (your
> workstation)?

You seem to be thinking at too low a level. There isn't any "mocked H/W", only 
mocked behavior. The H/W simulation bodies give the information or have the 
effect expected of the devices given the state of the reality modeled in the 
environment pkg, but they need have no similarity to the real bodies, and 
usually don't. The device may be memory mapped, but there's no reason for the 
simulation to be. If access the device takes appreciable time, that's usually 
simulated using a delay. There's usually no reason to limit these parts of the 
S/W to the constraints of the target run time.

-- 
Jeff Carter
"Beyond 100,000 lines of code you
should probably be coding in Ada."
P. J. Plauger
26