Jump to content
Flirc Forums


  • Content Count

  • Joined

  • Last visited

  • Days Won


jason last won the day on August 1

jason had the most liked content!

Community Reputation

156 Excellent

About jason

  • Rank

Profile Information

  • Gender
  • Location
    Santa Clara
  • Interests
    flirc, that's all I have time for.

Recent Profile Visitors

14,135 profile views
  1. I pushed an update that addressed a couple other issues, general cleanup, and improved IR transmission flexibility. Thanks again for all the help.
  2. you guys rock, thanks for the patience, and the help. I've got an update with a bunch of other bug fixes I've had stashed. I'm hoping to get this out shortly.
  3. Took a little longer to verify the the actual problem and best solutino What happened was that the motherboard would send down control requests, 'get report descriptor', but for some reason, the endpoint out transfers were no getting received by the host. So the host would request the same descriptor again, and fail again. Eventually, it would pass, but for some reason, so many transfers to the host would fail. The hosts typically sends down an endpoint reset, but this was after dozens of fails, which is way too late. The device uses a 512 byte SRAM area in memory for the DMA transfers to the host. Without the endpoint reset, which would reset our endpoint frame back down to the bottom of the 512 SRAM, we would overflow, corrupt our stack pointer, and eventually crash. Along with some other bug fixes yet to deploy, this version treats the 512 byte DMA area as a circular buffer. So it just wraps around if the hosts never sends down an endpoint reset. Really hard to debug. All real time and any GDB operations, the host disconnects the device and transfers stop. dori.release-4.6.6.bin nemo.release-4.6.6.bin
  4. I got this mother fucking bug. That was rough. I’ll post an update for you guys tomorrow. Thanks to @dborn and @putefabio for the excellent help in letting me use their resources.
  5. I'm trying to solve this as quickly as possible now. I have a big release soon, and it's critical that this firmware is 100% stable, so I will need to issue a fix in the next 2 weeks. I'm looking to buy a system that this is happening on so I can reproduce locally.
  6. It's on flirc, you need to repair nothing. It should just work with your previously paired remote.
  7. Yes, shoot me a PM, let's connect over skype or gchat or whats app and lets get this worked out.
  8. I’ll need a volunteer to help pin this down. Not much time, but a good amount of interaction on trying various firmware images. Let me know who’s up for it. I’ll compensate with a refund and some additional products, some which will be released within the next few days and weeks.
  9. Yeah, I'm at a loss. I can't reproduce this. @arabesc Can you please let me know if this is happening with you and if W3CB suggestion work?
  10. That’s correct, go to file->upgrade firmware Not to worry, if it’s the wrong one, it wont upload. You can’t brick it.
  11. This is not working, we're messaging hours a part. I'll DM you my private contact info.
  12. Just saw this. Will look at this tomorrow. Definitely can't have the GUI open if you are doing this through the commandline
  13. I'm around right now, we're probably on different time zones. (I'm in PST) I'm also available most of tomorrow. Let me know what works.
  • Create New...