I did a quick search, so I’m basically an expert now. imaginary hair flip
So, some flashlights have multiple brightness modes. I guess that’s controlled via a tiny, low power microprocessor.
And if it’s a computer, it can be hacked!
So the firmware does things, depending on the capabilities of the hardware in the flashlight, but you can set it to override defaults for brightness, change how many levels of brightness you have, add (or remove) a blinky SOS mode, sleep timers in case it’s accidentally left on, and even add a way to check the battery percentage via a button press pattern, that the flashlight responds to with a series of blinks.
No lie, kind of fascinating stuff. I like to hack other stuff, like smart appliances (replacing firmware so it doesn’t share my data, but I still get to use it as a smart device). I don’t think I would be into talking to my flashlight via Morse code, but I can see the appeal as both a hobby, and for folks who need flashlights as safety equipment.
Why the hell make it with a microprocessor when something simple like brightness levels and simple blinking patterns can be made with much simpler digital electronics without the need for any programming whatsoever leaving the whole hacking-issue out of the equation.
Because you could design all of those feature in analog, and make custom boards for every change or have one board you update every few years based on supply, cost, and maybe power performance, but make and adjust features on a minute by minute basis if want to.
The driver, power source, etc can all be more easily separated from the logic too. It could be tiny, or massive. Same software, same controller.
Its a flashlight, not exactly a field in raging development.
Honestly I’m thinking it’s because it’s cheaper to have programmers doing simple FW programming for things than it is to have engineers design the required circuits. There are so many things with microprocessors in today that just does not actually need it but it was the lazy option. It opens stupid avoidable avenues of vulnerabilities.
My girlfriend asked why I carry a gun around the house?
I looked her dead in the eye and said, “the motherfucking decepticons”. She laughed, I laughed, the toaster laughed, I shot the toaster, it was a good time.
…. I don’t know. It’s just what came to mind when I thought of household appliances being hijacked.
Or you use one GreenPak device and OTP it based on the model and have it cheaper and more reliable, any supporting circuits like drivers, FETs, bulk capacitance, etc… Would have to be designed per-model anyway on MCU based design.
Why the hell would a flashlight need firmware?
I did a quick search, so I’m basically an expert now. imaginary hair flip
So, some flashlights have multiple brightness modes. I guess that’s controlled via a tiny, low power microprocessor.
And if it’s a computer, it can be hacked!
So the firmware does things, depending on the capabilities of the hardware in the flashlight, but you can set it to override defaults for brightness, change how many levels of brightness you have, add (or remove) a blinky SOS mode, sleep timers in case it’s accidentally left on, and even add a way to check the battery percentage via a button press pattern, that the flashlight responds to with a series of blinks.
No lie, kind of fascinating stuff. I like to hack other stuff, like smart appliances (replacing firmware so it doesn’t share my data, but I still get to use it as a smart device). I don’t think I would be into talking to my flashlight via Morse code, but I can see the appeal as both a hobby, and for folks who need flashlights as safety equipment.
Why the hell make it with a microprocessor when something simple like brightness levels and simple blinking patterns can be made with much simpler digital electronics without the need for any programming whatsoever leaving the whole hacking-issue out of the equation.
Because you could design all of those feature in analog, and make custom boards for every change or have one board you update every few years based on supply, cost, and maybe power performance, but make and adjust features on a minute by minute basis if want to.
The driver, power source, etc can all be more easily separated from the logic too. It could be tiny, or massive. Same software, same controller.
Its a flashlight, not exactly a field in raging development.
Honestly I’m thinking it’s because it’s cheaper to have programmers doing simple FW programming for things than it is to have engineers design the required circuits. There are so many things with microprocessors in today that just does not actually need it but it was the lazy option. It opens stupid avoidable avenues of vulnerabilities.
…. I don’t know. It’s just what came to mind when I thought of household appliances being hijacked.
I love it,keep up the good work Scotty!
Or you use one GreenPak device and OTP it based on the model and have it cheaper and more reliable, any supporting circuits like drivers, FETs, bulk capacitance, etc… Would have to be designed per-model anyway on MCU based design.