ESP32 + ls013b4dn04 2.7" Sharp Memory Display #921
-
|
After going through wiring up some buttons and writing a bit of code I ordered the 2.7" Sharp Memory Display - Adafruit Sharp Memory Display. I have a few ESP32 boards, but for this I'm using the There are examples for the manifest.json: {
"include" : [
"$(MODDABLE)/examples/manifest_base.json",
"$(MODULES)/drivers/ls013b4dn04/manifest.json",
"$(MODULES)/base/instrumentation/manifest.json"
],
"config": {
"screen": "ls013b4dn04",
"touch": "",
"format": "Gray256"
},
"resources": {
"*": [
"./moddable-white"
]
},
"defines": {
"ls013b4dn04": {
"width": 400,
"height": 240,
"hz": 3500000,
"cs_pin": 4,
"spi_port": 23
}
},
"modules": {
"commodetto/Poco": "$(COMMODETTO)/commodettoPoco",
"commodetto/*": "$(COMMODETTO)/commodettoPocoBlit",
"commodetto/parseBMF": "$(COMMODETTO)/commodettoParseBMF",
"commodetto/parseBMP": "$(COMMODETTO)/commodettoParseBMP",
"commodetto/Bitmap": "$(COMMODETTO)/commodettoBitmap",
"Resource": "$(MODDABLE)/modules/files/resource/Resource",
"*": "./main"
},
"preload": [
"commodetto/*",
"Resource",
"instrumentation",
"pins",
"spi",
"main"
]
}main.js: import LS013B4DN04 from "ls013b4dn04";
import Poco from "commodetto/Poco";
import Resource from "Resource";
import parseBMP from "commodetto/parseBMP";
import Timer from "timer";
debugger;
const TIMER_MS = 5000;
export default function() {
// Took this example from the moddable example for ls013b4dn04 (removing sleep)
const logo = parseBMP(new Resource("moddable-white.bmp"));
const width = 400, height = 240;
let render = new Poco(new LS013B4DN04({ width: width, height: height }));
let black = render.makeColor(0, 0, 0);
let white = render.makeColor(255, 255, 255);
let index = 0;
let timer = Timer.repeat(() => {
index ^= 1;
render.begin(0, 0, width, height);
render.fillRectangle(index ? white : black, 0, 0, width, height);
render.drawGray(logo, index ? black : white, 0, 30);
render.end();
}, TIMER_MS);
}Run: Error in the terminal: Click to view the full output... |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 16 replies
-
|
The Commodetto Font Engine (CFE) isn't being included, which is causing a link error The easiest way to resolve that is to include {
"include" : [
"$(MODDABLE)/examples/manifest_base.json",
"$(MODDABLE)/examples/manifest_commodetto.json",
"$(MODULES)/drivers/ls013b4dn04/manifest.json"
],
"config": {
"screen": "ls013b4dn04",
"touch": "",
"format": "Gray256"
},
"resources": {
"*": [
"./moddable-white"
]
},
"defines": {
"ls013b4dn04": {
"width": 96,
"height": 96,
"hz": 3500000
}
},
"modules": {
"Resource": "$(MODDABLE)/modules/files/resource/Resource",
"*": "./main"
},
"preload": [
"Resource",
"main"
],
"strip":"*"
} |
Beta Was this translation helpful? Give feedback.
-
|
Pasted below it looks fine. It is including (offtopic:
PXL_20220706_035308436_2_Trim.mp4 |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for the video! The big screen is great. I really like how quickly it refreshes. The dump of You can override the use of ILI9341 by in the "config": {
"screen": "ls013b4dn04"
}Since you are including |
Beta Was this translation helpful? Give feedback.
-
|
It took a bit to test, long day then started playing around with ideas to make it work.
By the way I'm running |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for the additional info. Good that we can rule interference from the ILI9341 driver out. I don't have a display connected to test with, but I ran a few tests on the ESP32 today to see the behavior of the CS pin (GPIO 15). It behaves as expected, of course. ;) I tried to puzzle out what your change to set GPIO 15 high outside the driver. The only effect that I can see is that it causes GPIO 15 to be set high earlier than it would otherwise. You are running on an ESP32, which is relatively fast compared to the ESP8266 and Gecko hardware we have used with the Sharp Memory Displays. Checking the data sheet for the ls013b4dn04, there is a relatively long time required for CS to settle.
Maybe on the faster ESP32, there isn't a long enough elapsed time between setting CS high and beginning to transmit pixel data. Your change effectively extends that. A quick hack can test the theory: in the driver, wait a little after setting CS high. This change waits much longer than should be necessary: void ls013b4dn04ChipSelect(uint8_t active, modSPIConfiguration config)
{
ls013b4dn04 ls = (ls013b4dn04)(((char *)config) - offsetof(ls013b4dn04Record, spiConfig));
if (active) {
SCREEN_CS_ACTIVE;
modDelayMilliseconds(2);
}
else
SCREEN_CS_DEACTIVE;
} |
Beta Was this translation helpful? Give feedback.
-
|
@phoddie Does not fix the issue, but does create a sort of 1 second render effect from top to bottom filling in rows. This still requires me to click the button once to send the PXL_20220707_200358224.mp4. |
Beta Was this translation helpful? Give feedback.
-
|
Too bad. The super slo-mo is nice though. I'm out of ideas. You should at least be able to move your workaround out of script and into the driver. At the end of the native constructor, SCREEN_CS_ACTIVE;The call to |
Beta Was this translation helpful? Give feedback.
-
|
Weird enough but that also didn't work either. NBD, you got everything working enough for my project! Very excited to start coding more on this (connecting a i2c fuel gauge next while designing a UI for this mono display). One suggestion though I think it would make sense to remove the default screen and the include from the
I'll sign the CLA and make a PR to update the docs with more details for ESP32 / Wiring for these 2 adafruit breakouts. |
Beta Was this translation helpful? Give feedback.
-
Very strange. There's some mystery here. When you figure it out, please let me know. ;)
There are many ways to implement and integrate sensors, like an I²C fuel gauge. The Moddable SDK is moving in the direction of using the Ecma-419 for that. It defines IO for both pure I²C and SMBus. The Sensor Class Pattern specifies a common API for all sensors with extensibility. We have a collection of compatible sensor drivers with more on the way. Anyway... do whatever works for you, but we've found the Ecma-419 stuff work well and packages the implementation for easy re-use. All the Ecma-419 foundation bits are already in the Moddable SDK.
That makes sense. The ESP32-Thing doesn't have a built-in display. I think the reason it is there is from our testing when bringing up the port. Do you want to make that chance?
Thank you. We received that. |
Beta Was this translation helpful? Give feedback.
-
|
Will mess around more debugging the I'll submit a PR to update the target for the Thanks for the additional info for the I²C stuff and Ecma-419. I'm sure as I get into this more it will be more clear (little bit of a learning curve). |
Beta Was this translation helpful? Give feedback.
The Commodetto Font Engine (CFE) isn't being included, which is causing a link error The easiest way to resolve that is to include
manifest_commodetto.json. Here's a revisited manifest that builds for ESP8266 (and should work for ESP32 as well).{ "include" : [ "$(MODDABLE)/examples/manifest_base.json", "$(MODDABLE)/examples/manifest_commodetto.json", "$(MODULES)/drivers/ls013b4dn04/manifest.json" ], "config": { "screen": "ls013b4dn04", "touch": "", "format": "Gray256" }, "resources": { "*": [ "./moddable-white" ] }, "defines": { "ls013b4dn04": { "width": 96, "height": 96, "hz": 3500000 } }, "modules": { "Resource": "$(MODDABLE)/modules/files/res…