❗ Document OUT_REPORT_{CMD,DATA,CMD_DATA} ❗

[JamesTheAwesomeDude]

Progress is slow-going and annoying.

Why on earth isn't this documented?

[JamesTheAwesomeDude]

[2018-07-03]

Unfortunately, Jonathan McCrohan (the last person to make a commit on drv_picoLCDGraphic.c) no longer owns any PicoLCD devices, nor was he aware of any current sources of documentation on this device.

[JamesTheAwesomeDude]

From Mini-Box customer support:

[2018-07-05]
Dear James,

All the available information about the picoLCD-256x64 is posted on our website. If you have specific questions, i will ask our developers team.
Should you need other details, please contact us!

[2018-07-03]
Hello,
What documents are available regarding the actual USB interface to your "PicoLCD 256x64" product?

We require more control than the LCD4Linux-configuration API offers, and reverse-engineering the included drv_picoLCDGraphic.c driver has been not only extremely slow-going, but much less informative than we'd hoped.
(i.e., there are still mayn "complete unknowns" and pieces of code that, even after cleaning up and parceling out, are completely inscrutable.)

Thank you

I have replied:

[2018-07-05]
Specifically, I have a few questions about the source code file "drv_picoLCDGraphic.c"
(Line numbers are from SVN revision 1204, available at https://lcd4linux.bulix.org/browser/trunk/drv_picoLCDGraphic.c?rev=1204 )

My main question is: What is the actual specification which lines (i.e.,) 227–238, 242–246, 356–365, 342, and 399–402 implement?

For instance, what does the "chipselect" byte (lines 228,243, 358,376,399) control?

There seems to be excerpts of the original specification scattered throughout the code (e.g., lines 226,240,374,396), but the documentation off which the code is based is nowhere to be found.

I am looking for the actual interface specification to which the drv_picoLCDGraphic.c is complying.

So to speak, what are "the rules" for interfacing with the PicoLCD over a USB connection?

Thank you

(It would be really nice to get my hands on the original specification...)

[JamesTheAwesomeDude]

Other ideas: going through some of the email addresses at the top of the C file?

[JamesTheAwesomeDude]

Other ideas: going through some of the email addresses at the top of the C file?

• Michael Reinelt's domain doesn't even exist anymore; it seems to be owned now by a sketchy domain parker
• LCD4Linux Sourceforge email group is approximately dead (and would they care enough to help out with an attempt to re-implement and document their code?)
• Nicu Pavel may or may not be more helpful than the oblivious "Customer Support" person I've been interacting with, assuming he even still works there. Possibly worth a shot, once I've wrapped up my current interaction with an @mini-box.com address.

[JamesTheAwesomeDude]

cc5a038 should help a LOT with this, particularly the separating out on a logical level of the initial command bytes from the more complex "magic sauce" provided by cmd3 and cmd4.

[JamesTheAwesomeDude]

(This whole Issue is basically the "raison d'être" of this whole project. Need to find some way to Pin it or something)