lcd4linux-devel — lcd4linux development team

[Lcd4linux-devel] [Fwd: Re: display on WRAP-Board - how fast is i2c?]

[Luis C. <lfc...@lf...>]

Mailing lists @ sf.net suck!

Here it goes again...

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

Re: [Lcd4linux-devel] display on WRAP-Board - how fast is i2c?

[Michael R. <re...@eu...>]

Hi Luis,

>   I will need something in the lines of a uppercase_all plugin or
>   something similar, that would produce proper text output (everything
>   written in CAPS). Michael, any hints on this?

There's already a plugin_string.c, with only a strlen() function. A
toupper() and tolower() function would perfectly fit here (mabye the
name is wrong, but I could not find a  better one :-)

> The second delay for 4.1ms was wrong
Have you got any details about this one?


bye, Michael

-- 
Michael Reinelt <re...@eu...>
http://home.pages.at/reinelt
GPG-Key 0xDF13BA50
ICQ #288386781

Re: [Lcd4linux-devel] display on WRAP-Board - how fast is i2c?

[Luis C. <lfc...@lf...>]

Stefan Krister wrote:
> Hi all,
>
> success!
>
> I have blinking LEDs at the pcf8574 output lines while lcd4linux is
> running! My LCD is still 'dark' but that may be a other problem ...
>
> I'm not 100% sure, but i think, that
>
> insmod scx200_acb.ko base=0x810,0x820

  Yes, that was it!

  That is why the module we use was modified in the first place. For 2.4
  kernels there was no useable module, hence the need to modify it.

  I now also have my I2C module working as well, and this time also
  powered by 3.3V, it's blue backlight module i salvaged from an old HP
  printer (HD66710). Pity it won't do any lowercase characters...

  I will need something in the lines of a uppercase_all plugin or
  something similar, that would produce proper text output (everything
  written in CAPS). Michael, any hints on this?

  Stefan, i'm also finetuning the driver a bit, try this attached file,
  where i did some minor changes and bug fixes.

Update, sf.net is forbidding .ZIP file extensions, so i'll just copy 
past my changes here.

CHANGELOG:

drv_generic_i2c.c:

The exit code was not done properly.
p.s. there is still a need to properly detect the I2C slave device, 
which i'll do in some days along with the extension for full 8bit mode 
using two PCF8574. This is of course just a plan, knowing my previous 
time-to-market failed objectives :P

drv_HD44780.c:

The second delay for 4.1ms was wrong
4bit and 8bit code decision and initialization needs to be done also here.


------------------------------- CUT HERE -------------------------------


drv_generic_i2c.c:


int drv_generic_i2c_open(const char *section, const char *driver)
{
     int dev;
     char *bus, *device;
     udelay_init();
     Section = (char *) section;
     Driver = (char *) driver;
     bus = cfg_get(Section, "Port", NULL);
     device = cfg_get(Section, "Device", NULL);
     dev = atoi(device);
     info("%s: initializing I2C bus %s", Driver, bus);
     //info("device %d", dev);
     if ((i2c_device = open(bus, O_WRONLY)) < 0) {
			error("%s: I2C bus %s open failed !\n", Driver, bus);
			goto exit_error;
     }
     info("%s: selecting slave device 0x%x", Driver, dev);
     if (ioctl(i2c_device, I2C_SLAVE, dev) < 0) {
			error("%s: error selecting slave device 0x%x\n", Driver, dev);
			goto exit_error;
     }

     info("%s: initializing I2C slave device 0x%x", Driver, dev);
     if (i2c_smbus_write_quick(i2c_device, I2C_SMBUS_WRITE) < 0 ){
			error("%s: error initializing device 0x%x\n", Driver, dev);
			close(i2c_device);
		}

     return 0;

   exit_error:
     free(bus);
     free(device);
		close(i2c_device);
		return -1;
}


drv_HD44780.c

	change init sequence around linen 995 to this:

     /* initialize display */
     drv_HD_I2C_nibble(allControllers, 0x03);
     udelay(T_INIT1);		/* 4 Bit mode, wait 4.1 ms */
     drv_HD_I2C_nibble(allControllers, 0x03);
     udelay(T_INIT2);		/* 4 Bit mode, wait 100 us */
     drv_HD_I2C_nibble(allControllers, 0x03);
     udelay(T_INIT1);		/* 4 Bit mode, wait 4.1 ms */
     drv_HD_I2C_nibble(allControllers, 0x02);
     udelay(T_INIT2);		/* 4 Bit mode, wait 100 us */
     drv_HD_I2C_command(allControllers, 0x28, T_EXEC);	/* 4 Bit mode,\ 
1/16 duty cycle, 5x8 font */


------------------------------- CUT HERE -------------------------------

Have fun.

If I can, i'll prepare a small webcam video to illustrate how slow the 
I2C bus can be, speccially with scrolling widgets like 'OS'.

Luis Correia


-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

Re: [Lcd4linux-devel] Test

[Michael R. <re...@eu...>]

Hi there,

> and yes, the replies to the list were sluggish for the last days

There's a known impact on the SF mailing lists. Details can be found on
the SF site status page.

looks like no mails are lost, but delayed for a long time.


-- 
Michael Reinelt <re...@eu...>
http://home.pages.at/reinelt
GPG-Key 0xDF13BA50
ICQ #288386781

Re: [Lcd4linux-devel] Test

[Luis C. <lfc...@lf...>]

Michael Reinelt wrote:
> Test, please ignore

email ignored :)

and yes, the replies to the list were sluggish for the last days

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

Re: [Lcd4linux-devel] display on WRAP-Board - how fast is i2c?

[Stefan K. <ste...@cr...>]

Hi all,

success!

I have blinking LEDs at the pcf8574 output lines while lcd4linux is
running! My LCD is still 'dark' but that may be a other problem ...

I'm not 100% sure, but i think, that

insmod scx200_acb.ko base=0x810,0x820

was the right step.

MfG

Stefan

[Lcd4linux-devel] Test

[Michael R. <re...@eu...>]

Test, please ignore

Stefan Krister schrieb:
> kann es sein, da=DF die lcd4linux ML im Moment nicht funktioniert?
lets see...


--=20
Michael Reinelt <re...@eu...>
http://home.pages.at/reinelt
GPG-Key 0xDF13BA50
ICQ #288386781

Re: [Lcd4linux-devel] display on WRAP-Board - how fast is i2c?

[Stefan K. <ste...@cr...>]

Hi all,

success!

I have blinking LEDs at the pcf8574 output lines while lcd4linux is
running! My LCD is still 'dark' but that may be a other problem ...

I'm not 100% sure, but i think, that

insmod scx200_acb.ko base=0x810,0x820

was the right step.

MfG

Stefan

Re: [Lcd4linux-devel] display on WRAP-Board - how fast is i2c?

[Stefan K. <ste...@cr...>]

Hi all,

success!

I have blinking LEDs at the pcf8574 output lines while lcd4linux is
running! My LCD is still 'dark' but that may be a other problem ...

I'm not 100% sure, but i think, that

insmod scx200_acb.ko base=0x810,0x820

was the right step.

MfG

Stefan

Re: [Lcd4linux-devel] display on WRAP-Board - how fast is i2c?

[Stefan K. <ste...@cr...>]

Hi Luis,

Luis.F.Correia schrieb am 25.07.2006 17:26:
> 
> How are you powering the LCD?

I'm using a DOG-Module [1] which rus with 3.3V.

>> There are no messages ..
> 
> That is odd...

yes ..

> Can you send me a CF image that you are currently using, so that 
> I can test with my WRAP? Private email please. (if you get a 
> message too large, let me know, i'll provide another email 
> free from restrictions)

Yes - I zip it together after breakfast. A 4MB CF will be enough, I think.

Is there a bering-image I could use?

[1] http://www.lcd-module.de/eng/dog/dog.htm

MfG

Stefan

Re: [Lcd4linux-devel] display on WRAP-Board - how fast is i2c?

[Luis.F.Correia <Lui...@se...>]

Hi! 

> -----Original Message-----
> From: Stefan Krister [mailto:ste...@cr...] 
> 
> Hi Luis,
> 
> Luis.F.Correia schrieb am 25.07.2006 17:26:
> > 
> > How are you powering the LCD?
> 
> I'm using a DOG-Module [1] which rus with 3.3V.

Good, then forget about my other power level conversion comments :)

> >> There are no messages ..
> > 
> > That is odd...
> 
> yes ..
> 
> > Can you send me a CF image that you are currently using, so 
> that I can 
> > test with my WRAP? Private email please. (if you get a message too 
> > large, let me know, i'll provide another email free from 
> restrictions)
> 
> Yes - I zip it together after breakfast. A 4MB CF will be 
> enough, I think.

I haven't got the time to test your image yet.

> Is there a bering-image I could use?

Bering-uClibc does not use an image per-se. It just boots from the
CF and reads all packages from it.

But I can prepare an image for you, once i get my stuff ready to
test. I've been fighting with I2C also.

Now i even discovered the 0.10.0 version we are packaging segfaults
on exiting... i'll have to take a good look into it, as it is difficult
to debug inside WRAP it self.

> 
> [1] http://www.lcd-module.de/eng/dog/dog.htm
> 
> MfG
> 
> Stefan

Luis

Re: [Lcd4linux-devel] display on WRAP-Board - how fast is i2c?

[Stefan K. <ste...@cr...>]

Hi Luis,

Luis.F.Correia schrieb am 25.07.2006 17:26:
> 
> How are you powering the LCD?

I'm using a DOG-Module [1] which rus with 3.3V.

>> There are no messages ..
> 
> That is odd...

yes ..

> Can you send me a CF image that you are currently using, so that 
> I can test with my WRAP? Private email please. (if you get a 
> message too large, let me know, i'll provide another email 
> free from restrictions)

Yes - I zip it together after breakfast. A 4MB CF will be enough, I think.

Is there a bering-image I could use?

[1] http://www.lcd-module.de/eng/dog/dog.htm

MfG

Stefan

Re: [Lcd4linux-devel] display on WRAP-Board - how fast is i2c?

[Luis.F.Correia <Lui...@se...>]

Hi! 

> -----Original Message-----
> From: Stefan Krister [mailto:ste...@cr...] 
> Sent: Tuesday, July 25, 2006 4:12 PM
> To: lcd...@li...
> Subject: Re: [Lcd4linux-devel] display on WRAP-Board - how 
> fast is i2c? ho w good is the lpc connector?
> 
> 
> Hi Luis,
> 
> Luis.F.Correia schrieb am 25.07.2006 15:27:
> > 
> > For the sake of completeness, here's an update to the schematics:
> > 
> > The PCF is powered by +5V, but the I2C inputs are biased to
> > +3.3v, which is the correct voltage level of the WRAP board.
> 
> My datasheet says that voltage between 2.5V and 6.0V are 
> valid. Must I provide 5V also? And where to take ...

How are you powering the LCD?

>From what I've seen, all LCD's I have only +5V power, and yes, I use
an additional power for it.

FYI, i use the power supply from an external 5 1/2 enclosure to 
power my LEAF board. While I could use only the +5V supply to power
all the board, I chose to power the board with the +12V and the +5V
for the LCD and other things i may need.

> > The messages around loading the i2c bus including the scx200_acb.
> 
> There are no messages ..

That is odd...

Can you send me a CF image that you are currently using, so that 
I can test with my WRAP? Private email please. (if you get a 
message too large, let me know, i'll provide another email 
free from restrictions)


Luis Correia   
Bering uClibc Team Member

PGP Fingerprint: BC44 D7DA 5A17 F92A CA21 9ABE DFF0 3540 2322 21F6 
Key Server: http://pgp.mit.edu

Re: [Lcd4linux-devel] display on WRAP-Board - how fast is i2c? ho w good is the lpc connector?

[Luis.F.Correia <Lui...@se...>]

Hi! 

> -----Original Message-----
> From: Ernst Bachmann [mailto:e.b...@xe...] 
> Sent: Tuesday, July 25, 2006 4:40 PM
> To: lcd...@li...
> Subject: Re: [Lcd4linux-devel] display on WRAP-Board - how 
> fast is i2c? ho w good is the lpc connector?
> 
> On Tuesday 25 July 2006 17:11, Stefan Krister wrote:
> > Hi Luis,
> >
> > Luis.F.Correia schrieb am 25.07.2006 15:27:
> > > For the sake of completeness, here's an update to the schematics:
> > >
> > > The PCF is powered by +5V, but the I2C inputs are biased to
> > > +3.3v, which is the correct voltage level of the WRAP board.
> >
> > My datasheet says that voltage between 2.5V and 6.0V are 
> valid. Must I 
> > provide 5V also? And where to take ...
> >
> 
> The I2C chips usually connect to the bus using open-collector 
> drivers, so its basically only important your PCF and the uC 
> share the same ground.
> 
> (The chips can only drive the bus lines low, its pulled up only by the
> pullup-resistors)
> 
> Of course, you should connect your i2c-pullup resistors to 
> the lowest Vcc in the system, in your case to 3.3V.
> 
> That way your i2c bus would operate on 3.3V, your PCF would 
> work on 5V, but will still recognize the logic levels on the 
> bus... As always, check the Datasheet to be sure.
> 

Ernst, you are right with everything you say.

Electrically speaking it can be done in several ways without
needing any special and complex voltage conversion devices.


What I described works for me using the PCF8574 and the WRAP board.

> 
> HTH
> /Ernst


Luis Correia   
Bering uClibc Team Member

PGP Fingerprint: BC44 D7DA 5A17 F92A CA21 9ABE DFF0 3540 2322 21F6 
Key Server: http://pgp.mit.edu

Re: [Lcd4linux-devel] =?iso-8859-1?q?display_on_WRAP-Board_-_how_fast?= =?iso-8859-1?q?_is_i2c=3F=09ho_w_good_is_the_lpc_connector=3F?=

[Ernst B. <e.b...@xe...>]

On Tuesday 25 July 2006 17:11, Stefan Krister wrote:
> Hi Luis,
>
> Luis.F.Correia schrieb am 25.07.2006 15:27:
> > For the sake of completeness, here's an update to the schematics:
> >
> > The PCF is powered by +5V, but the I2C inputs are biased to
> > +3.3v, which is the correct voltage level of the WRAP board.
>
> My datasheet says that voltage between 2.5V and 6.0V are valid. Must I
> provide 5V also? And where to take ...
>

The I2C chips usually connect to the bus using open-collector drivers, so its 
basically only important your PCF and the uC share the same ground.

(The chips can only drive the bus lines low, its pulled up only by the 
pullup-resistors)

Of course, you should connect your i2c-pullup resistors to the lowest Vcc in 
the system, in your case to 3.3V.

That way your i2c bus would operate on 3.3V, your PCF would work on 5V, but 
will still recognize the logic levels on the bus... As always, check the 
Datasheet to be sure.


HTH
/Ernst

Re: [Lcd4linux-devel] display on WRAP-Board - how fast is i2c? ho w good is the lpc connector?

[Stefan K. <ste...@cr...>]

Hi Luis,

Luis.F.Correia schrieb am 25.07.2006 15:27:
> 
> For the sake of completeness, here's an update to the schematics:
> 
> The PCF is powered by +5V, but the I2C inputs are biased to
> +3.3v, which is the correct voltage level of the WRAP board.

My datasheet says that voltage between 2.5V and 6.0V are valid. Must I
provide 5V also? And where to take ...

>> > you'll need to add the specific /dev entries.
>> 
>> Be free to provide me wiht your major/minor numbers. My 
>> devices are currently
>> 
>> ls -al /dev/i2*
>> crw-r--r--    1 root     root      89,   0 Jul 25 13:06 /dev/i2c-0
>> crw-r--r--    1 root     root      89,   1 Jul 25 13:06 /dev/i2c-1

> If pcf8574 must _not_ be loaded. If it is, then lcd4linux will not work.

O.k.

> The messages around loading the i2c bus including the scx200_acb.

There are no messages ..

MfG

Stefan

Re: [Lcd4linux-devel] display on WRAP-Board - how fast is i2c? ho w good is the lpc connector?

[Luis.F.Correia <Lui...@se...>]

 Hi!

> -----Original Message-----
> From: Stefan Krister [mailto:ste...@cr...] 
> Sent: Tuesday, July 25, 2006 12:36 PM
> To: lcd...@li...
> Subject: Re: [Lcd4linux-devel] display on WRAP-Board - how 
> fast is i2c? ho w good is the lpc connector?
> 
> Hi Luis,
> 
> Luis.F.Correia schrieb am 25.07.2006 11:47:
> > 
> > They are needed to pull up the I2C lines at 3.3V, this is a 
> > requirement from the I2C specifications.
> 
> o.k. - for the rest of the readers - I provide your 
> schematics as ascii:

For the sake of completeness, here's an update to the schematics:

The PCF is powered by +5V, but the I2C inputs are biased to
+3.3v, which is the correct voltage level of the WRAP board.



 
   VCC         +5V
    + 3.3v     | .------------.     .------------.
    '----o---o .-|16         1|--.  |            |
         |   |   |    PCF8574 |  |  |        LCD |
        .-. .-.  |           2|--o  |            |
        | | | |  |            |  |  |            |
        | | | |  |           3|--o  |            |
        '-' '-'  |            |  |  |            |
         |   |   |            | === |            |
         |   |   |            | GND |            |
   SDA o-o---)---|15          |     |            |
             |   |           4|-----|D4          |
   SCL o-----o---|14          |     |            |
                 |           5|-----|D5          |
    .------------|8           |     |            |
    |            |           6|-----|D6          |
   ===           |            |     |            |
   GND           |           7|-----|D7          |
                 |            |     |            |
                 |      10  9 |     | RS  E   RW |
                 '------------'     '------------'
                        |   |         |   |   |
                        |   '---------'   |  ===
                        '-----------------'  GND

(Michael, you can add this to the wiki, if you like)


> >> I wired my display like yours. I configured lcd4linux as
> >> 
> >> Display DOG-16x3 {
> >>     Driver 'HD44780'
> >>     Model 'generic'
> >>     Bus 'i2c'
> >>     Device '64'
> 
> is that correct? It's the address of the chip?

I can't recall if we used decimal or hex notation in the config
definition. It does depend whether you are using the PCF8574 or
the PCF8574A, since they have different port addresses.
IIRC, mine is at hex:71, dec:112.

> That's wrong! It should be
> 
> Wire {
>      RW        'GND'
>      RS        'DB4'
>      ENABLE    'DB5'
> }
> 
> Isn't it?

Yes, this is correct.

> 
> > you'll need to add the specific /dev entries.
> 
> Be free to provide me wiht your major/minor numbers. My 
> devices are currently
> 
> ls -al /dev/i2*
> crw-r--r--    1 root     root      89,   0 Jul 25 13:06 /dev/i2c-0
> crw-r--r--    1 root     root      89,   1 Jul 25 13:06 /dev/i2c-1
> 
> > In WRAP, the temp sensor sits on bus 1, while the external 
> bus is bus 
> > 0. You are getting different results because you are using the in 
> > kernel I2C drivers. The WRAP board uses the 'worng' values 
> for the I2C 
> > AccessBus controllers. Please check in the driver I 
> previously sent to 
> > get the proper I/O ports. You may have to patch the I2C driver to 
> > match this board (scx200_acb i mean).
> 
> Don't know what you want me to do ... Sure I'm using the 
> in-kernel i2c driver. It works fine. I do not want to make 
> changes in the kernel modules.

Well, i can't help much, as LEAF currently uses a 2.4 series kernel and we
do provide the accessbus driver.

> > With lcd4linux, you will only need the i2c-core, i2c-dev, 
> i2c-proc and 
> > the access bud driver.
> > 
> > Nothing else is needed, because we do RAW chip access.
> 
> Do the already loadesd modules affect lcd4linux?

If pcf8574 must _not_ be loaded. If it is, then lcd4linux will not work.


> 
> > Can you post the dmesg messages?
> 
> No, there is no dmesg in fli4l - but I have a full bootlog - 
> what do you expect to see?

The messages around loading the i2c bus including the scx200_acb.

> MfG
> 
> Stefan

Luis

Re: [Lcd4linux-devel] display on WRAP-Board - how fast is i2c? ho w good is the lpc connector?

[Stefan K. <ste...@cr...>]

Hi Luis,

Luis.F.Correia schrieb am 25.07.2006 11:47:
> 
> They are needed to pull up the I2C lines at 3.3V, this is a requirement from
> the I2C specifications.

o.k. - for the rest of the readers - I provide your schematics as ascii:

  VCC
   +            .------------.     .------------.
   '----o---o---|16         1|--.  |            |
        |   |   |    PCF8574 |  |  |        LCD |
       .-. .-.  |           2|--o  |            |
       | | | |  |            |  |  |            |
       | | | |  |           3|--o  |            |
       '-' '-'  |            |  |  |            |
        |   |   |            | === |            |
        |   |   |            | GND |            |
  SDA o-o---)---|15          |     |            |
            |   |           4|-----|D4          |
  SCL o-----o---|14          |     |            |
                |           5|-----|D5          |
   .------------|8           |     |            |
   |            |           6|-----|D6          |
  ===           |            |     |            |
  GND           |           7|-----|D7          |
                |            |     |            |
                |      10  9 |     | RS  E   RW |
                '------------'     '------------'
                       |   |         |   |   |
                       |   '---------'   |  ===
                       '-----------------'  GND

>> I wired my display like yours. I configured lcd4linux as
>> 
>> Display DOG-16x3 {
>>     Driver 'HD44780'
>>     Model 'generic'
>>     Bus 'i2c'
>>     Device '64'

is that correct? It's the address of the chip?

>>     Port '/dev/i2c-0'
>>     Icons '8'
>>     Size '16x3'
>> 
>>     Wire {
>>         RW        'GND'
>>         RS        'AUTOFD'
>>         ENABLE    'STROBE'
>>     }

That's wrong! It should be

Wire {
     RW        'GND'
     RS        'DB4'
     ENABLE    'DB5'
}

Isn't it?

> you'll need to add the specific /dev entries.

Be free to provide me wiht your major/minor numbers. My devices are
currently

ls -al /dev/i2*
crw-r--r--    1 root     root      89,   0 Jul 25 13:06 /dev/i2c-0
crw-r--r--    1 root     root      89,   1 Jul 25 13:06 /dev/i2c-1

> In WRAP, the temp sensor sits on bus 1, while the external bus is
> bus 0. You are getting different results because you are using the 
> in kernel I2C drivers. The WRAP board uses the 'worng' values for the
> I2C AccessBus controllers. Please check in the driver I previously
> sent to get the proper I/O ports. You may have to patch the I2C 
> driver to match this board (scx200_acb i mean).

Don't know what you want me to do ... Sure I'm using the in-kernel i2c
driver. It works fine. I do not want to make changes in the kernel modules.

> With lcd4linux, you will only need the i2c-core, i2c-dev, i2c-proc 
> and the access bud driver.
> 
> Nothing else is needed, because we do RAW chip access.

Do the already loadesd modules affect lcd4linux?

> Can you post the dmesg messages?

No, there is no dmesg in fli4l - but I have a full bootlog - what do you
expect to see?

MfG

Stefan

Re: [Lcd4linux-devel] display on WRAP-Board - how fast is i2c? ho w good is the lpc connector?

[Luis.F.Correia <Lui...@se...>]

Hi! 

I added back the list ;)

> -----Original Message-----
> From: Stefan Krister [mailto:ste...@cr...] 
> Sent: Tuesday, July 25, 2006 10:39 AM
> To: Luis.F.Correia
> Subject: Re: [Lcd4linux-devel] display on WRAP-Board - how 
> fast is i2c? ho w good is the lpc connector?
> 
> 
> Hi Luis,
> 
> Luis.F.Correia schrieb am 24.07.2006 15:41:
> > 
> > was this information usefull?
> 
> yes, a little ... are there 10kOhm resistors? And what for are they?

They are needed to pull up the I2C lines at 3.3V, this is a requirement from
the I2C specifications.

> I wired my display like yours. I configured lcd4linux as
> 
> Display DOG-16x3 {
>     Driver 'HD44780'
>     Model 'generic'
>     Bus 'i2c'
>     Device '64'
>     Port '/dev/i2c0'
>     Icons '8'
>     Size '16x3'
> 
>     Wire {
>         RW        'GND'
>         RS        'AUTOFD'
>         ENABLE    'STROBE'
>     }
> }
> 
> but I'm getting errors at start:
> 
> lcd4linux -f lcd4linux.conf -Fvv
> Version 0.10.1-CVS starting
> plugin_cfg.c: Variable halfminute = '30000' (30000)
> plugin_cfg.c: Variable minute = '60000' (60000)
> plugin_cfg.c: Variable tack = '100' (100)
> plugin_cfg.c: Variable tick = '500' (500)
> lcd4linux.c: initializing driver HD44780
> HD44780: $Revision: 1.62 $
> HD44780: using model 'generic'
> HD44780: using I2C bus
> HD44780: using 1 Controller(s)
> HD44780: using 4 bit mode
> udelay: CPU supports Time Stamp Counter
> udelay: CPU runs at 266.661000 MHz
> udelay: using TSC delay loop, 267 ticks per microsecond
> HD44780: initializing I2C bus /dev/i2c0
> device 64
> HD44780: I2C bus /dev/i2c0 open failed !
> 
> HD44780: could not initialize i2c attached device!
> HD44780: start display failed!
> 
> 
> Something with my i2c is going wrong ...
> 
> I'm using kernel 2.6.16.20 with loaded modules: i2c_core, 
> scx200_acb, lm77. Reading the WRAP temperature works fine 
> with this commandline:
> 
> sed 's/\([0-9]\{3\}\)$/.\1/' /sys/bus/i2c/devices/0-0048/temp1_input
> 
> but there is no other i2c-chip 'in sight' - I think, the i2c 
> core 'scans' the bus for chips?
> 
> And I don't have any /dev/i2c* files - I createt some, but 
> with no luck.

you'll need to add the specific /dev entries.

In WRAP, the temp sensor sits on bus 1, while the external bus is
bus 0. You are getting different results because you are using the 
in kernel I2C drivers. The WRAP board uses the 'worng' values for the
I2C AccessBus controllers. Please check in the driver I previously
sent to get the proper I/O ports. You may have to patch the I2C 
driver to match this board (scx200_acb i mean).

With lcd4linux, you will only need the i2c-core, i2c-dev, i2c-proc 
and the access bud driver.

Nothing else is needed, because we do RAW chip access.

> 
> I tried to load the pcf8574.ko module, which should print the 
> found chips - but nothing. The module loads but doesn't print 
> out anything.

This is useless, and if it won't find the chip is just because
the BUS assignments are wrong.

Can you post the dmesg messages?

> 
> MfG
> 
> Stefan
> 

Luis

Re: [Lcd4linux-devel] [lcd4linux] Fwd: LCD2USB

[Till H. <ti...@ha...>]

Hi,

On Sunday 23 July 2006 23:06, Michael Reinelt wrote:
> > Do you know if anything was ever done with these to support an interface
> > with windows?
>
> I don't know. Best would be if Till could answer this question...
I didn't see the question to this answer, but my guess is that someone asked
for Windows drivers for my lcd2usb.

As stated on the lcd2usb page i do have a demo application included that runs 
under Linux, Windows and MacOS-X. It comes with full source and will allow 
you to integrate e.g. a matching driver to your favourite Windows LCD tool 
(as long as you can get hold of its sourcecode of course).

I don't know of any LCD driver software besides lcd4linux including support 
for the LCD2USB yet. But if your want to give it a try i'd gladly help you if 
you need any help. A port should be fairly simple and straight forward.

Regards,
  Till

-- 
Dr.Ing. Till Harbaum <ti...@ha...>
http://www.harbaum.org/till

Re: [Lcd4linux-devel] display on WRAP-Board - how fast is i2c? ho w good is the lpc connector?

[Stefan K. <ste...@cr...>]

Hi Luis,

Luis.F.Correia schrieb:
>=20
[HD44780 on single/dual PCF8574 I2C I/O Expander]

>> may I ask you for a circuit-schematic?
>=20
> Well, i don't have then done with any schematic software...
>=20
> Will you accept a hand drawn one?

Again, yes please.

Today, I ordered 4 PCF8574 - I hope they arrive on monday. Could you
please feed me with your schematics?

>>> I also had some thoughts on using the GPIO pins, but found
>> it way too
>>> tricky to be done correclty (at least from me).
>> ;-))

Tricky ... I don't understand the sc1100.pdf ... so I'm not able to do
the GPIO-stuff now. I'll try to get help from my coworkers at fli4l.


MfG

Stefan
--=20
WRAP-Geh=E4use: http://wiki.port23.de/index.php/Creative.chaos.de
Bilder: http://gallery.port23.de/v/bastard/wrap/gehaeuse/

Re: [Lcd4linux-devel] what buildsystem to use?

[Michael R. <re...@eu...>]

sorry if this message reaches you twide, but I've got some problems with
my provider's MX registered at SpamCop....

Hi Stefan,

> 1st it's now working ...
Great! So now you can compile yurself?

> but it seems that
> 
> Widget ImageTest {
>     class 'Image'
> ...
> 
> doesn't work on that display - correct? Or missed I a compile switch? My
> syslog shows

> Jul 18 11:38:28 dell LCD4Linux[30460]: widget 'ImageTest': class 'Image'
> not supported

Looks like the image driver has been disabled by configure. This happens
if configure cannot find libgd headers and/or libraries...


HTH, Michael

-- 
Michael Reinelt <re...@eu...>
http://home.pages.at/reinelt
GPG-Key 0xDF13BA50
ICQ #288386781

Re: [Lcd4linux-devel] what buildsystem to use?

[Stefan K. <ste...@cr...>]

Hi,

1st it's now working ...

I'm using

Display HP12542R {
    Driver 'serdisplib'
    Port '0x378'
    Model 'HP12542R'
    Options ''
}

but it seems that

Widget ImageTest {
    class 'Image'
...

doesn't work on that display - correct? Or missed I a compile switch? My
syslog shows

Jul 18 11:38:25 dell LCD4Linux[30460]: lcd4linux.c: initializing driver
serdisplib
Jul 18 11:38:25 dell LCD4Linux[30460]: serdisplib: $Revision: 1.10 $
Jul 18 11:38:25 dell LCD4Linux[30460]: serdisplib: header  version 1.97
Jul 18 11:38:25 dell LCD4Linux[30460]: serdisplib: library version 1.97
Jul 18 11:38:25 dell LCD4Linux[30460]: serdisplib: using model 'HP12542R'
Jul 18 11:38:25 dell LCD4Linux[30460]: serdisplib: using options ''
Jul 18 11:38:25 dell LCD4Linux[30460]: serdisplib: display size 128x64
Jul 18 11:38:28 dell LCD4Linux[30460]: initializing layout 'TestImage'
Jul 18 11:38:28 dell LCD4Linux[30460]: widget 'ImageTest': class 'Image'
not supported
Jul 18 11:38:28 dell LCD4Linux[30460]: lcd4linux.c: starting main loop
Jul 18 11:38:28 dell LCD4Linux[30460]: huh? not one single timer to
process? dazed and confused...
Jul 18 11:38:28 dell LCD4Linux[30460]: lcd4linux.c: leaving main loop
Jul 18 11:38:28 dell LCD4Linux[30460]: serdisplib: shutting down.

MfG

Stefan

Re: [Lcd4linux-devel] what buildsystem to use?

[Michael R. <re...@eu...>]

Hi Stefan,


> I tried it with knoppix 5 - there is no aclocal-1.9.

which version of aclocal (autoconf) do they use? I suppose lcd4linux
should work with every version of autoconf. Maybe you have to use the
./bootstrap script to get rid of my autoconf stuff (which is in CVS,
too, for people who don't have all the autconf devel stuff installed)


> I tried it on the developer-server from fli4l/eisfair - there comes this:
> 
> make
> cd . && aclocal-1.9
> /usr/share/aclocal/libmcrypt.m4:17: warning: underquoted definition of
> AM_PATH_LIBMCRYPT
>   run info '(automake)Extending aclocal'
>   or see http://sources.redhat.com/automake/automake.html#Extending-aclocal
> configure.in:25: error: Autoconf version 2.59e or higher is required

Huh?

Maybe you've got an older version of autoconf. Try to edit configure.in
and change the line

AC_PREREQ(2.59e)

to the version you're using.


HTH, Michael

-- 
Michael Reinelt <re...@eu...>
http://home.pages.at/reinelt
GPG-Key 0xDF13BA50
ICQ #288386781

Re: [Lcd4linux-devel] what buildsystem to use?

[Stefan K. <ste...@cr...>]

Hi Michael,

Michael Reinelt schrieb am 17.07.2006 17:54:
> 
> Sure I could do so. But why the heck don't you compile yourself? Do you
> need or have a special setup?

I tried it, but with no luck. It seems that I have to build a
compile-only machine ...

The target-System is libc.so.6 based (eisfair). I own the Pollin hyundai
hp12542r display module kit [1]. And please activate all the plugins.

[1] http://serdisplib.sourceforge.net/ser/hp12542r.html

Thanks

Stefan