I’ve also begun working on something ultra cool, and I’ve got some of that up and running. For developers looking to integrate flirc into products, this actually means a lot. This doesn’t mean much for customers other than it’s the beginning of me getting back into firmware development. The host PC can ask flirc the current ‘state’ in a polled mode, which means that I don’t need a separate thread. Now, the flirc firmware uses a state machine for recording. This isn’t good and made my API terrible, confusing, and easy to get wrong when I release the software. Which means that in order to write the host side software, I needed a separate thread to wait in set_interrupt. Anyone familiar with libusb, set_interrupt(), this function blocking. Previously, the firmware would set an interrupt back to the host on the event of a button being recorded. I’ve also completely revamped things a bit so the firmware works differently. I’ve begun strengthening my algorithm to better support other remotes and so you don’t have to record keys twice with the RC6 protocol. I’m re-structuring all my code so I can solve these bugs with sleep, sticky buttons, and long presses. Getting stuck on a technical problem, I took a break from that and am working on firmware development.
#Flirc streacom edition software#
Not a big one today, I’m still working on the software build system, which isn’t done. I haven’t used it in quite a while.Īs promised, I wanted to give everyone an update. On a separate note, does anyone use twitter anymore? I occasionally get new followers and am curious if people actually like twitter as a line of communication.
![flirc streacom edition flirc streacom edition](https://static.tweaktown.com/content/7/4/7461_28_streacom-f12c-atx-htpc-chassis-review_full.jpg)
Should those be good, the first 100 pre-orders will go out immediately and I will start the next major build. I have a sample test batch coming wednesday which took the manufacturers way to long to make. My goal is to have major releases by the end of the month of both the firmware and the GUI.
#Flirc streacom edition how to#
My git repository was an absolute cluttered and broken mess with branches going no where.Īll this time I’ve been mapping out how to restructure the firmware. It was absolutely necessary that I fixed the build system before continuing development. I’m at the point now where I can start ripping apart the code and improving on it. I have static analyzers as part of the build system and many many more improvements.
![flirc streacom edition flirc streacom edition](https://hardzone.es/app/uploads-hardzone.es/2014/10/Streacom-Flirc-SE-480x233.jpg)
It’s sustainable, scalable, and will allow me to cross build, deploy, and solve all my shared library issues. I’ve pretty much solved all technical hurdles I was struggling with and have it about 85% complete. Things are going very well and I’ve made tremendous improvements to the build system.
#Flirc streacom edition update#
I failed to update the blog these past couple of weeks and I apologize for that. I thought I would at the very least give a brief update of progress.