Rawr! I love bit banging
-
There's little more satisfying than spelunking through a little MCU's hardware registers to try to eek some more performance out of its I/O. DMA, hardware SPI, SDMMC, here there be dragons. Every new platform is like unwrapping a new toy. Downside is my code is getting uglier and uglier as it supports more and more platforms, with little I can do about it. When it comes to driving LCD displays, one thing I did though was this. I decoupled the graphics driver itself, from the bus it uses, and both of those from the graphics library. library-->driver-->bus like that. So now, I improve the bus, say optimizing it to use the Teensy's DMA capabilities and blammo all of my drivers benefit. My code is unique in terms of IoT graphics libraries in that way. The bottom line is a little mess goes a long way and improves performance for all my driver code across the board. I've done it for the ESP32, and in part for the Teensy 4.x so far - the latter is a work in progress. It's deeply satisfying to cover that much ground by modifying one header file. And to do so by going back to the kind of coding I grew up with - smashing things up until i get to the wiring in the walls, figure out how it works, and tap right into the mains. It's delicious.
To err is human. Fortune favors the monsters.
-
There's little more satisfying than spelunking through a little MCU's hardware registers to try to eek some more performance out of its I/O. DMA, hardware SPI, SDMMC, here there be dragons. Every new platform is like unwrapping a new toy. Downside is my code is getting uglier and uglier as it supports more and more platforms, with little I can do about it. When it comes to driving LCD displays, one thing I did though was this. I decoupled the graphics driver itself, from the bus it uses, and both of those from the graphics library. library-->driver-->bus like that. So now, I improve the bus, say optimizing it to use the Teensy's DMA capabilities and blammo all of my drivers benefit. My code is unique in terms of IoT graphics libraries in that way. The bottom line is a little mess goes a long way and improves performance for all my driver code across the board. I've done it for the ESP32, and in part for the Teensy 4.x so far - the latter is a work in progress. It's deeply satisfying to cover that much ground by modifying one header file. And to do so by going back to the kind of coding I grew up with - smashing things up until i get to the wiring in the walls, figure out how it works, and tap right into the mains. It's delicious.
To err is human. Fortune favors the monsters.
-
There's little more satisfying than spelunking through a little MCU's hardware registers to try to eek some more performance out of its I/O. DMA, hardware SPI, SDMMC, here there be dragons. Every new platform is like unwrapping a new toy. Downside is my code is getting uglier and uglier as it supports more and more platforms, with little I can do about it. When it comes to driving LCD displays, one thing I did though was this. I decoupled the graphics driver itself, from the bus it uses, and both of those from the graphics library. library-->driver-->bus like that. So now, I improve the bus, say optimizing it to use the Teensy's DMA capabilities and blammo all of my drivers benefit. My code is unique in terms of IoT graphics libraries in that way. The bottom line is a little mess goes a long way and improves performance for all my driver code across the board. I've done it for the ESP32, and in part for the Teensy 4.x so far - the latter is a work in progress. It's deeply satisfying to cover that much ground by modifying one header file. And to do so by going back to the kind of coding I grew up with - smashing things up until i get to the wiring in the walls, figure out how it works, and tap right into the mains. It's delicious.
To err is human. Fortune favors the monsters.
Sounds like a hard drive related discussion, and maybe bad segments/sectors due to too much physical action.
-
Sounds like a hard drive related discussion, and maybe bad segments/sectors due to too much physical action.
What?
To err is human. Fortune favors the monsters.
-
There's little more satisfying than spelunking through a little MCU's hardware registers to try to eek some more performance out of its I/O. DMA, hardware SPI, SDMMC, here there be dragons. Every new platform is like unwrapping a new toy. Downside is my code is getting uglier and uglier as it supports more and more platforms, with little I can do about it. When it comes to driving LCD displays, one thing I did though was this. I decoupled the graphics driver itself, from the bus it uses, and both of those from the graphics library. library-->driver-->bus like that. So now, I improve the bus, say optimizing it to use the Teensy's DMA capabilities and blammo all of my drivers benefit. My code is unique in terms of IoT graphics libraries in that way. The bottom line is a little mess goes a long way and improves performance for all my driver code across the board. I've done it for the ESP32, and in part for the Teensy 4.x so far - the latter is a work in progress. It's deeply satisfying to cover that much ground by modifying one header file. And to do so by going back to the kind of coding I grew up with - smashing things up until i get to the wiring in the walls, figure out how it works, and tap right into the mains. It's delicious.
To err is human. Fortune favors the monsters.
Read the title and thought 'Ow Er Missus', mind you bit banging I find can be good for the soul... but I'm odd...
-
What?
To err is human. Fortune favors the monsters.
Did I say something impolite? I had read the title and I`ve let my imagination run wild. The title usually sets the tone so I made my comment with that in mind.
-
Did I say something impolite? I had read the title and I`ve let my imagination run wild. The title usually sets the tone so I made my comment with that in mind.
No I just didn't understand you, since what I wrote had nothing to do with hard drives, and I don't normally associate the phrase "bit banging" with them so it threw me.
To err is human. Fortune favors the monsters.
-
No I just didn't understand you, since what I wrote had nothing to do with hard drives, and I don't normally associate the phrase "bit banging" with them so it threw me.
To err is human. Fortune favors the monsters.
I went a little further down with reading (just one sentence), it looks like you`re still talking about the same earthly thing (or things). Since it`s about freedom I thought why not join the party, programmer style of course.
-
I went a little further down with reading (just one sentence), it looks like you`re still talking about the same earthly thing (or things). Since it`s about freedom I thought why not join the party, programmer style of course.
Well, I haven't had to wave a dead chicken over this code yet. I'm still researching it. First crawl, finally deal in the meta, and magic.
To err is human. Fortune favors the monsters.
-
No I just didn't understand you, since what I wrote had nothing to do with hard drives, and I don't normally associate the phrase "bit banging" with them so it threw me.
To err is human. Fortune favors the monsters.
Heh, I once considered trying to create a floppy drive emulator by bit-banging the IO on a raspberry Pi, but concluded that the IO was too slow. Is that close enough? :-)
-
Well, I haven't had to wave a dead chicken over this code yet. I'm still researching it. First crawl, finally deal in the meta, and magic.
To err is human. Fortune favors the monsters.
Quote:
dead chicken
the party turns ugly, I`m leaving. don`t want to learn what that syntax means. btw, you won`t see me as quest from now on. In the light of what you just said, spells and code no thanks.
-
Read the title and thought 'Ow Er Missus', mind you bit banging I find can be good for the soul... but I'm odd...
You're normal compared to some people I know on Discord.
What do you get when you cross a joke with a rhetorical question? The metaphorical solid rear-end expulsions have impacted the metaphorical motorized bladed rotating air movement mechanism. Do questions with multiple question marks annoy you???
-
There's little more satisfying than spelunking through a little MCU's hardware registers to try to eek some more performance out of its I/O. DMA, hardware SPI, SDMMC, here there be dragons. Every new platform is like unwrapping a new toy. Downside is my code is getting uglier and uglier as it supports more and more platforms, with little I can do about it. When it comes to driving LCD displays, one thing I did though was this. I decoupled the graphics driver itself, from the bus it uses, and both of those from the graphics library. library-->driver-->bus like that. So now, I improve the bus, say optimizing it to use the Teensy's DMA capabilities and blammo all of my drivers benefit. My code is unique in terms of IoT graphics libraries in that way. The bottom line is a little mess goes a long way and improves performance for all my driver code across the board. I've done it for the ESP32, and in part for the Teensy 4.x so far - the latter is a work in progress. It's deeply satisfying to cover that much ground by modifying one header file. And to do so by going back to the kind of coding I grew up with - smashing things up until i get to the wiring in the walls, figure out how it works, and tap right into the mains. It's delicious.
To err is human. Fortune favors the monsters.
-
Well, I haven't had to wave a dead chicken over this code yet. I'm still researching it. First crawl, finally deal in the meta, and magic.
To err is human. Fortune favors the monsters.
Quote:
I haven't had to wave a dead chicken over "this" code yet.
Which begs the question: What code has had dead chickens waved over it? So ... How many chickens do you have now? How many did you start out with?
-
Quote:
I haven't had to wave a dead chicken over "this" code yet.
Which begs the question: What code has had dead chickens waved over it? So ... How many chickens do you have now? How many did you start out with?
I never use my own chickens. ;P
To err is human. Fortune favors the monsters.
-
There's little more satisfying than spelunking through a little MCU's hardware registers to try to eek some more performance out of its I/O. DMA, hardware SPI, SDMMC, here there be dragons. Every new platform is like unwrapping a new toy. Downside is my code is getting uglier and uglier as it supports more and more platforms, with little I can do about it. When it comes to driving LCD displays, one thing I did though was this. I decoupled the graphics driver itself, from the bus it uses, and both of those from the graphics library. library-->driver-->bus like that. So now, I improve the bus, say optimizing it to use the Teensy's DMA capabilities and blammo all of my drivers benefit. My code is unique in terms of IoT graphics libraries in that way. The bottom line is a little mess goes a long way and improves performance for all my driver code across the board. I've done it for the ESP32, and in part for the Teensy 4.x so far - the latter is a work in progress. It's deeply satisfying to cover that much ground by modifying one header file. And to do so by going back to the kind of coding I grew up with - smashing things up until i get to the wiring in the walls, figure out how it works, and tap right into the mains. It's delicious.
To err is human. Fortune favors the monsters.
My favorite bit banging trick was setting up hardware sprites on the C64 with their pixels rendered from memory location 0x0000 or 0x0100(call stack). You could see system clock, etc like a heart beat of the machine. Also figuring out how to put a piece of electrical tape over certain pins on cartridges and plugging them in on a hot machine.
-
There's little more satisfying than spelunking through a little MCU's hardware registers to try to eek some more performance out of its I/O. DMA, hardware SPI, SDMMC, here there be dragons. Every new platform is like unwrapping a new toy. Downside is my code is getting uglier and uglier as it supports more and more platforms, with little I can do about it. When it comes to driving LCD displays, one thing I did though was this. I decoupled the graphics driver itself, from the bus it uses, and both of those from the graphics library. library-->driver-->bus like that. So now, I improve the bus, say optimizing it to use the Teensy's DMA capabilities and blammo all of my drivers benefit. My code is unique in terms of IoT graphics libraries in that way. The bottom line is a little mess goes a long way and improves performance for all my driver code across the board. I've done it for the ESP32, and in part for the Teensy 4.x so far - the latter is a work in progress. It's deeply satisfying to cover that much ground by modifying one header file. And to do so by going back to the kind of coding I grew up with - smashing things up until i get to the wiring in the walls, figure out how it works, and tap right into the mains. It's delicious.
To err is human. Fortune favors the monsters.
It is Delicious I agree. Done a lot of it over the years. It is success that makes it delicious. When you don't succeed it makes it more mundane. However the conversation that you had with @CalinCali was so funny. I now have visions of you waving someone else's dead chicken over your code, casting a spell, that puts a hex on it. Spells and coding has got to be good. For everyone.
"Rock journalism is people who can't write interviewing people who can't talk for people who can't read." Frank Zappa 1980
