Jump to content
Flirc Forums


  • Posts

  • Joined

  • Last visited

  • Days Won


Everything posted by jason

  1. Save the log file to disk and attach it here.
  2. Here is some software, there is accompanying firmware in each. You should not have to re-learn any buttons. The firmware upgrade is only to support another USB HID key used by nvidia. There is a new controller which adds the new keys. Do any buttons work for you at the moment and you are just lacking support for the new buttons? I’ll spend some time on it today. I did see some buttons working on my shield, but I had to change the way USB reports back to the host, which would mean if that’s the direction I need to go in, customers would need to re-learn buttons. Linux: https://flirc.io/nightly/Flirc GUI/linux/Flirc-3.24.3-3-g6e0058d.tar.gz Mac: https://flirc.io/nightly/Flirc GUI/mac/Flirc-3.24.3-3-g6e0058d.dmg Windows: https://flirc.io/nightly/Flirc GUI/win/Flirc-3.24.3-3-g6e0058d.tar.gz @Rojma I have been reaching out to Logitech without success. I have a lot of updates for them. I’m trying. I guess people will just have to hang tight for my remote... ssh
  3. @fizban I'm having a bit of a tough time. I'm not sure if my shield is not new enough, my shield software is not new enough, or they somehow broke compatibility. I'm building some beta software, I'll post it here for you. Risk is minimal, I've just added a GUI controller with the buttons, and updated the firmware to support the 'netflix' key. Even with the original firmware, my shield is acting really funny. I don't remember if mine is one a grabbed from the lab there, or if I bought it. I'll post a link shortly.
  4. I'll try to send them out tomorrow. I ran into a couple issues that's eating my time. They are on my desk and I got to finish off a bit of code. Almost there.
  5. I'm not going to troubleshoot the gen1 device. Send me a PM, I'll send you a new unit. ** EDIT ** to clarify, I'll get you a new deivce.
  6. @Amack001 go to controllers->media keys I believe you are looking at the streacom controller
  7. @Peter Stone Can you send me a pic of your remote? Can you also open up my GUI, and go to file->advanced, enable IR debugging. Press and hold one of the buttons. I'll help get support in for that remote.
  8. Got the codes from NVIDIA, I’m hoping to release a GUI update asap this week.
  9. Currently available on my site and on amazon.
  10. Your tracking number was https://www.fedex.com/apps/fedextrack/?action=track&language=english&tracknumbers=776421745270 Fedex never received the package, you notified me and requested a refund, so I sent a refund rather than trying to resend it. This happens more than usual, I drop off a lot of orders at Fedex, and they lose or misplace some. I don't know why. I'm sorry for the inconvenience, but there is no reason to attempt to publicly shame me, I refunded your money back immediately. If I didn't that would be the scam.
  11. Grab my latest GUI, grab this firmware, and go to File->Upgrade and select the dori.release-4.8.2.bin Close my GUI once you've got the firmware loaded. Grab the latest beta of remote buddy 2. Remote buddy only supports a handful of remotes at the moment. Make sure you are using one of the supported. Then you can use the remote buddy app to specifically control the specific app you'd like. Let me know where you are stuck.
  12. I'm sorry, it's my mistake, the currently released 3.24.2 is the correct one.
  13. NOTE - This firmware has been publicly released, feel free to keep posting feedback here. Firmware v4.8.2 Supports Wake up features with remote buddy Custom single command Multiple buttons ir_transmitter updates, ability to kill a running transmission Possible bug fixes in XMP protocol To update, make sure you have at least GUI version 3.24.2, release date November 19th, 2019 First, backup and save your configuration. Head over to File->Advanced. Check which SKU you have, it should be either dori, or nemo. Then do File->Upgrade and point to one of the images attached. Note - You do not have to quit the remote buddy application to update your firmware. This firmware is only required for sleep/wake functionality extended specifically through remote buddy. Flirc/Remote Buddy 2 support has been baked in and tested since v4.6.x, this update is not necessary to use Flirc with Remote Buddy. Please feel free to report any findings here. Bugs specific to this version of firmware. dori.release-4.8.2.bin nemo.release-4.8.2.bin
  14. To those who sent me a private message. Hang in there. I need to do a couple more firmware features and tests before sending. I should send them in the next couple days.
  15. Flirc doesn’t support a mouse and keyboard as those are usually Bluetooth. Flirc is only IR. Let me know if I misunderstood that.
  16. Yes, you need a USB on the go adapter. However, I have an new product with one built in. Any chance you’d want one for free in exchange for some helpful feedback?
  17. I pushed an update that addressed a couple other issues, general cleanup, and improved IR transmission flexibility. Thanks again for all the help.
  18. 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.
  19. 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
  20. 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.
  21. 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.
  • Create New...