Posts by GKollmann

Thanks for information.

Is it an Atmel problem or a Linux problem with the TWI/irq 'bug'?

But I think Atmels world is SPI, and TWI owns NXP.

And the speed-issue, how is the delay-time between a falling and rising edge realized in the kernels driver?
Using timer/interrupts than I beleave that increasing speed increase cpu-time.

On the other hand I need the hardware information by scanning the i2c chips and control their outpout pins.
That's an important part of the application.

best regards
Günter

Hi

I like to add i2c chips to the i2c bus.
The support for this chips is given (PCA9554A), other chips from this type allreadey running and I just add some at free addresses .

Normally the chips and pins are discriped in /etc/libugpio.conf
If I add my new chips there I can't get access with the tools gpio-get NAME, an error appears.

what else must I do to be able to use my new chips?

thanks and greetings
Günter

Thanks a lot, l'll try top find there someting to control the speed

But other work need my attention so I will check it out soon...

best regards
Günter

Hi at all

is it possible to drive the i2c clock with 400Khz?

and if yes, where can I adjust the clock speed for the i2c?

thanks and greetings
Günter

Hello

I've a question for the i2c driver and timing.

If I use the ugpio-API to set a output pin from a I2C device, can I count on it that if the function call ugpio_set_value(x) returns the pin is set to the new value?

Or is it possible that the call returns before the hardware-pin is change cause a queue or something else is involved?

best regards
Günter

Hi

I've rotated dthe transformator on a Starterkit (Rev 1.10) and it works.
After this I did it on a custom board with the strange behaviour and now it works too.

U-Boot starts witout any problem, loads the Linux kernel over NFS and Linux itself mounts the rootfs immediately!

Thanks for motivation to do this!

greetings
Günter

Hi

Thanks for reply

the major is 60 for fsio0 to fsio6
the minor is 0 to 6

I haven't changed anything at the boot parameters.
What should it be?

And is this sure that both methodes not working together?

I need ugpio definitely cause and old application use it.

greetings
Günter

Hi at all

I try to use the fsioX option to access the gpios from the picoCOM1-board.

Using ugpio works... like in the emlix-docu desripted.

In the PDF picoCOM1.pdf in 8.12 (General Purpose IO) is an other option to handle IOs.

Using fsio0 to fsio6 should open a device driver.
This 6 drivers appear in the /dev directory
/dev/fsio0
...
/dev/fsio6

But if I try to open one of them I get the eroor message : "No such device or address"

What can cause this message?
What must I do to have access like the docu promise?

It doesn't matter which number I use, from fsio0 to fsio6 the same messages.

Thanks for any idea

greetings
Günter

I've also a picoCOM1-Board and U-Boot works fine with the ethernet.

The transformator is in the wrong way mounted and U-Boot configure the EMAC in a way that works.
U-Boot loads the Linux kernel over ethernet without problems.
after unpacking the kernel starts and while the IP-CONFIG: appears at the com-console the LINK-light from the attached ethernet-switch go out....
the kernel try to auto-negotiate but after a few seconds the watchdog reset the µC.

It seams to be a Linux config problem with the EMAC/PHY

Have anybody a solution for this?

greetings
Günter