Jump to content
Flirc Forums

jason

Administrators
  • Posts

    2,733
  • Joined

  • Last visited

  • Days Won

    117

Everything posted by jason

  1. 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.
  2. 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
  3. 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.
  4. 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.
  5. It's on flirc, you need to repair nothing. It should just work with your previously paired remote.
  6. Yes, shoot me a PM, let's connect over skype or gchat or whats app and lets get this worked out.
  7. 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.
  8. 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?
  9. 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.
  10. This is not working, we're messaging hours a part. I'll DM you my private contact info.
  11. Just saw this. Will look at this tomorrow. Definitely can't have the GUI open if you are doing this through the commandline
  12. 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.
  13. In your flirc.ini, can you make sure that libusb logging is enabled? libusb = false ; Log libusb events. <-- change this to true. I know my fix worked for a bunch of people, we can do a team viewer so I can look at it if the log doesn't show anything.
  14. I'm positive it's a firmware issue, but I can't for the life of me reproduce this. Can you guys post your OS version, your hardware version, whether it's USB 2.0 or 3.0 ports? Any other information. A picture of device manager when it boots into this 'bad state'. Etc. Here is the latest firmware, upload the correct sku for your hardware. Once I see the problem, I'll have a fix pushed in seconds, but there is no reason for you guys to keep waiting anymore. I'm really sorry. nemo.release.bin dori.release.bin
  15. Thanks for the extra info. I haven't been able to reproduce this yet with multiple flircs and pc's and usb ports. I must be missing something. Not to worry, I can always give you guys the old firmware, but let me continue looking, I'm sure I'll find it shortly. Today wasn't the best from a time perspective, I was split amongst a few things, but this is considered red hot urgent.
  16. In this state, does the GUI detect flirc and no buttons work? Or the GUI doesn't recognize it?
  17. If you go into file->advanced Can you tell me the sku you guys are using?
  18. I was not seeing these posts, I will see if I can figure this out immediately.
  19. no, but what's your intention?
  20. Oof, my bad. I released it. I never followed up here. Grab my latest version and then do a flirc_util record toggle
  21. yes, that's exactly how flirc-se works. Also, if you have a regular flirc, record the 'wake' key, and it'll only wake the computer with that paired key. It's on the keyboard controller next to F12
  22. http://flirc.io/config/ But you can't really figure out what remote button belongs to each hash... That's as good as I have at the moment. Let me know if it's of any help.
×
×
  • Create New...