The Lounge is rated Safe For Work. If you're about to post something inappropriate for a shared office environment, then don't post it. No ads, no abuse, and no programming questions. Trolling, (political, climate, religious or whatever) will result in your account being removed.
I was in class, and a classmate shared it with our teacher(btw this is a virtual school, the classroom being the "science lab") and the teacher in there was doing it. He started using WordHippo and the student started yelling "That's Cheating", and everyone agreed, including the two other teachers in the room .
"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!
It's an all in one system, with the display panel deeply embedded into how the whole thing operates, and that's where it gets weird design-wise.
When I say deeply embedded I mean something like 14 pins on the main system are tied up to driving the display. Meanwhile, the display itself has a framebuffer which must be stored in the SoC's extended PSRAM in order to function. And finally, to drive the display requires hardware specific to the ESP32 SoC it's attached to. (Though I guess someone particularly ambitious could get it to work on a STM32 but there wouldn't be enough RAM)
There's no way I'm driving this e-paper panel outside this unit itself.
The whole thing is deeply integrated, to where it doesn't really make sense to segregate the display code from the hardware it runs on. For example, all my pin assignments can be hard coded, because they are hardwired on this device. I can assume 4MB of RAM (16 really, but 4 available under the Arduino framework), and I can make specific calls into the SoC's RTOS.
This shouldn't be causing me design issues, but every instinct in me is crying out to compartmentalize this code - like not assume pin assignments or the presence of an ESP32 WROVER, or anything like that. That's silly. I have no reason to do it. It doesn't make sense to do it. So why such a strong pull in that direction?
So I'm sitting here, tapping at VS Code in fits and starts, and I don't really know where to begin because I have to work against my instincts as a developer.
Maybe I *should* compartmentalize it just so I can operate within my normal parameters, but that would greatly complicate a lot of the code.
One problem with coding all my life is my instincts are too strong at this point.
This is my own project, but my job does entail work much like this, and I actually use work product from my own projects in my commercial endeavors, so there's a lot of cross over. There's a fair chance something I learn building this will benefit me professionally later on.
"the debugger doesn't tell me anything because this code compiles just fine" - random QA comment
"Facebook is where you tell lies to your friends. Twitter is where you tell the truth to strangers." - chriselst
"I don't drink any more... then again, I don't drink any less." - Mike Mullikins uncle
Last Visit: 31-Dec-99 18:00 Last Update: 11-Aug-22 20:55