Flash memory access

Hello,=20
I am an embedded systems engineering student (I should get my diploma in Se=
ptember 2008) and I was wondering how one does to configure for example a d=
isplay driver?=20
More clearly:
I would like to save the hardware configuration parameters of my hardware (=
the display driver) somwhere in the phones flash memory in a way that gives=
mle access to these parameters to easily change them if i change the platf=
orme or display (without having to retype the drivers source code)

For example where one enters the parameters concerning the communication bu=
s between the driver and the flash memory or RAM. Where one entered the par=
ameters of screen orientation, size, default color, resolution, signal pola=
rity, timing and so on.=20
Are these kinf of parameters actually saved in the flash memory and so on? =
and if one needs to change them is there a way to re enter the flash memory=
and change. Or else is there a specific memory for these kind of "hardware=
" parameters?
I hope my question is not too unclear=20
Thanks for your help in advance
Best

The LCD HAL provides a user-side API for controlling the screen mode, setti=
ng the brightness, getting the screen info etc, however these APIs appear t=
o be restricted to device creators. I will check whether this is correct.

Note also that the configuration is not necesarily stored in flash - it is =
up to the creator of the dsiplay driver how they handle these functions.

If you are just looking for some general persistent storage then you might =
want to check out the following example of how to use the central repositor=
y.

» [Symbian OS v9.x|http://developer.symbian.com/index.html] » [=
Examples|http://developer.symbian.com/index.html] » [System Library e=
xample code|http://developer.symbian.com/forum/index.html] »=20
CentRepExample: Using central repository for persistent storage

rgds

Adam

Hello,=20

Thanks for your help. I'll reposte my thread on the API section just incase=
:-)

best,

I am not an expect in the UI area but I think the reason for this restricti=
on might be that it is just the UI (S60, UIQ, MOAP) that is expected to acc=
ess this info directly. I would check your UI documentation to see what inf=
ormation the UI makes available to the application programmer.

rgds

Adam

<div>I agree with adamj. I think that is right, but we must see=20

Santi
</div>