|
Are the commands proprietary, and that's why they're not publicly documented?
The difficult we do right away...
...the impossible takes slightly longer.
|
|
|
|
|
I don't think it's proprietary. Either I haven't found the full datasheet, which is possibly not in English, or the Datasheet they provided is simply not complete.
To err is human. Fortune favors the monsters.
|
|
|
|
|
There's a 53 page pdf in Chinese at several places on the web (for instance https://www.alldatasheet.com/view.jsp?Searchword=AXP192[^]) . Looks like it has some information that might be of use. The section entitled "Registers" is almost half the whole thing, so there is probably good stuff in there if you can decode it (or find someone who can).
Cheers,
Peter
Software rusts. Simon Stephenson, ca 1994. So does this signature. me, 2012
|
|
|
|
|
This is what I get when I try to view it.
Warning[^]
Edit: Never mind, it's back up now. Thanks!
To err is human. Fortune favors the monsters.
|
|
|
|
|
Wordle 393 5/6
⬜⬜⬜⬜⬜
⬜⬜⬜⬜⬜
⬜🟩⬜⬜🟩
⬜🟩⬜⬜🟩
🟩🟩🟩🟩🟩
"If we don't change direction, we'll end up where we're going"
|
|
|
|
|
Wordle 393 4/6
🟨⬜⬜⬜⬜
⬜⬜⬜⬜⬜
⬜⬜⬜🟩🟩
🟩🟩🟩🟩🟩
My third starter is usually for elimination....
Software rusts. Simon Stephenson, ca 1994. So does this signature. me, 2012
|
|
|
|
|
Wordle 393 6/6
🟨⬜⬜⬜⬜
⬜🟩⬜⬜⬜
⬜🟩⬜⬜⬜
⬜🟩⬜⬜⬜
⬜🟩⬜⬜🟩
🟩🟩🟩🟩🟩
Just made it.
|
|
|
|
|
Not an easy one!
Wordle 393 5/6
⬜⬜⬜⬜🟨
⬜⬜🟨⬜⬜
⬜🟩⬜⬜🟩
⬜🟩🟨🟩🟩
🟩🟩🟩🟩🟩
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
"Common sense is so rare these days, it should be classified as a super power" - Random T-shirt
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
Wordle 393 3/6
🟨⬛🟨⬛⬛
⬛⬛🟩🟨⬛
🟩🟩🟩🟩🟩
|
|
|
|
|
Wordle 393 4/6
⬜🟨⬜⬜⬜
⬜⬜⬜⬜🟩
⬜⬜⬜⬜🟩
🟩🟩🟩🟩🟩
a lucky guess
Life should not be a journey to the grave with the intention of arriving safely in a pretty and well-preserved body, but rather to skid in broadside in a cloud of smoke, thoroughly used up, totally worn out, and loudly proclaiming “Wow! What a Ride!" - Hunter S Thompson - RIP
|
|
|
|
|
Quote: grey grey grey
I don`t know for sure what you had in mind when you wrote that, but if it is what I think it is than your statement is accurate for the most part except the ending, the ending does have color and diversity.
|
|
|
|
|
Wordle 393 3/6
⬛🟩🟨⬛⬛
🟨🟩⬛⬛🟩
🟩🟩🟩🟩🟩
Get me coffee and no one gets hurt!
|
|
|
|
|
Wordle 393 6/6
⬜⬜⬜⬜⬜
🟨⬜⬜⬜⬜
⬜⬜⬜⬜🟩
🟨🟩⬜⬜🟩
⬜🟩⬜🟨⬜
🟩🟩🟩🟩🟩
PHEW!
|
|
|
|
|
Wordle 393 4/6
⬛⬛🟨⬛⬛
⬛🟩⬛⬛⬛
⬛🟩⬛🟩🟩
🟩🟩🟩🟩🟩
|
|
|
|
|
|
I am consistently 0/0.
>64
Some days the dragon wins. Suck it up.
|
|
|
|
|
Wordle 393 4/6
⬜⬜⬜⬜⬜
🟩⬜⬜⬜🟩
🟩⬜🟨⬜⬜
🟩🟩🟩🟩🟩
"A little time, a little trouble, your better day"
Badfinger
|
|
|
|
|
I just got a neat little IoT widget but the screen appears to have been wired up to it at gunpoint.
A critical control line (RST on the display) is connected not directly to the MCU, but to a control line (IO4) on the power management circuit for the device. Because of this, the display has to be in part indirectly operated by fiddling with the power system on the device. My existing display drivers simply don't account for such a situation, so I have to fork a driver just for this device.
The source code provided for this device is not accurate to the device - meaning it doesn't work with it. I suspect there was an earlier edition of this device that was wired differently.
I'm in one of those positions where I have to write a bunch of code only to hope it will work when I'm done with it.
And a question just occurred to me.
I have a core driver that is general purpose but mostly works with this device. I could take a callback as one of the template parameters to mess with the RST pin but it adds complexity to the general purpose driver.
The other option is forking the driver for this device.
Anyone have any opinions on that?
To err is human. Fortune favors the monsters.
modified 16-Jul-22 10:52am.
|
|
|
|
|
And as soon as you finish they'll correct their mistake and it all will be for naught.
The most expensive tool is a cheap tool. Gareth Branwyn
JaxCoder.com
|
|
|
|
|
Mike Hanley said And as soon as you finish they'll correct their mistake and it all will be for naught.
So true. . .
But, if you don’t complete the work, they’ll never correct their mistake.
~Engineer’s Paradox
|
|
|
|
|
raddevus wrote: But, if you don’t complete the work, they’ll never correct their mistake.
~Engineer’s Paradox
The most expensive tool is a cheap tool. Gareth Branwyn
JaxCoder.com
|
|
|
|
|
A display that has to be partially controlled by fiddling with the device's power system?!
Either you have a high tolerance for nonsense or you love a challenge. Probably both.
|
|
|
|
|
The power system apparently has 4 controllable GPIO on it. They've hooked the reset line up to it. I think I found a way to hack it without modifying my driver by simply toggling the LCD's reset GPIO on startup outside the LCD driver itself.
To err is human. Fortune favors the monsters.
|
|
|
|
|
Seems the quality control for the display is lacking.
Perhaps, you can sell your fixes before you share.
"A little time, a little trouble, your better day"
Badfinger
|
|
|
|
|
I think it was probably a design decision they made due to limited I/O available on the MCU. In IoT there are often compromises made, some severe - and I believe this is one of those cases.
To err is human. Fortune favors the monsters.
|
|
|
|