[ECOS] I2C Driver not initializing

[ECOS] I2C Driver not initializing

[Alexandre]

Hello all,

Would anyone happend to know what i'd have to do for a driver to init ?
I've linked my i2c init function to the generic i2c interface but my
specific function is never called. I don't think the I2C interface
init function is called anyway, i supposed it would happen
automatically after configuring I2C in the ecos config tool but this
isn't the case.

Do I have to call the init function myself in cyg_user_start() ?

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

Re: [ECOS] I2C Driver not initializing

[Andrew Lunn]

On Tue, Sep 11, 2007 at 04:06:30PM +0200, Alexandre wrote:
> Hello all,
> 
> Would anyone happend to know what i'd have to do for a driver to init ?
> I've linked my i2c init function to the generic i2c interface but my
> specific function is never called. I don't think the I2C interface
> init function is called anyway, i supposed it would happen
> automatically after configuring I2C in the ecos config tool but this
> isn't the case.

Is this a I2C device driver you have written yourself? Or is it one of
the existing device drivers?

What do you have in the cdl file for the driver?

compile       -library=libextras.a my_i2c.c

Im wondering if the linker has throw the driver out because it is not
being used. By adding the -library=libextras.a the linker cannot throw
it away.

   Andrew

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

Re: [ECOS] I2C Driver not initializing

[Alexandre]

> Is this a I2C device driver you have written yourself? Or is it one of
> the existing device drivers?

Well it's one I've written myself as i didn't found any driver for the
LPC2XXX port.

> What do you have in the cdl file for the driver?

Actually, nothing, the driver part is style in my user code as I
wanted to test it before even trying to include it in eCos.
I added the package "I2C Support" to my package build and tried to
link my functions to it. Everything compiles just fine and i can
access the generic I2C functions as the headers are added to my
source.

> compile       -library=libextras.a my_i2c.c

libextras.a already exists in my config and contains my serial devices
configuration. It does not contain anything about i2c however, should
it ?

> Im wondering if the linker has throw the driver out because it is not
> being used. By adding the -library=libextras.a the linker cannot throw
> it away.

Well even the generic I2C driver code is not initialized so I think I
made a mistake by forgetting something or misunderstanding the whole
concept ^^

Alex

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

Re: [ECOS] I2C Driver not initializing

[Andrew Lunn]

> Well even the generic I2C driver code is not initialized so I think I
> made a mistake by forgetting something or misunderstanding the whole
> concept ^^

Do you call any I2C function? If nothing is using I2C it will all get
throw out by the linker.

Take a look at the functions which are actually in your
image. 

arm-elf-objdump --syms myprog

Is the i2c code there?

   Andrew

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

Re: [ECOS] I2C Driver not initializing

[Alexandre]

Ok that was the problem, the i2c file was rejected by the linker and
not included in the code since considered unused, it works now ...

I feel shame ^^

Thanks a lot Andrew, as usual :)

On 9/11/07, Andrew Lunn <andrew@lunn.ch> wrote:
> > Well even the generic I2C driver code is not initialized so I think I
> > made a mistake by forgetting something or misunderstanding the whole
> > concept ^^
>
> Do you call any I2C function? If nothing is using I2C it will all get
> throw out by the linker.
>
> Take a look at the functions which are actually in your
> image.
>
> arm-elf-objdump --syms myprog
>
> Is the i2c code there?
>
>    Andrew
>

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss