On Sun, 24 Dec 2017 13:45:40 +0100, R.Wieser wrote:
>
> Also, the fact that you think you need to know the device means you are
> probably oblivious to where my/the problem is located (hint, its not
> anywhere near the device).

Correct I am oblivious to your problem because your question is
confusing, tell me the device you want to talk to & I may be able to tell
you how to talk to it
>
>> you will find you resolve your problem much faster if you provide all
>> information.
>
> Experience tells me otherwise.

This suggest that you are not very good at asking questions
>
>
> But, I'm accepting your challenge (for no othe reason than to enable you
> to see the erring of your assumption):
>
> My device is an SSD1306 128 x 64 bit I2C OLED display.  I need be able
> to write a few bytes (representing a bit pattern of a single 6x8
> character/symbol), but also a "refresh" a single-or-few 128-byte
> "line(s)" (outof 8), or the whole display if need be.  I would also like
> to be able to write a repeatable, multibyte pattern over part of, or the
> whole of the display.
>
The data sheet seems prety clear. I suspect you need to use memory
addressing mode

> Lets see if that info enables you to actually answer my question.   I
> don't think it will.   The only question to me is if you will fess up to
> it.
>
> Just so you know: *any* answer which is specific to that device and
> cannot be used in a generic way means you automatically loose.
>
then this is an impossible challenge as any solution has to be specific
to this family of devices

> Yes, I'm quite the brutal asshole when challenged.  So sue me. :-)

only when challenged?

>
> Regards,
> Rudy Wieser





--
Home on the Range was originally written in beef-flat.

--- SoupGate-Win32 v1.05