Jump to content

HiGhLaNdeR

Members
  • Posts

    11
  • Joined

  • Last visited

Everything posted by HiGhLaNdeR

  1. So far everything is working :) I plugged the Flirc in the Acer Aspire Revo r3600 and turned it on. The Flirc was detected and the long keypress was working too. Ah! Before I plugged the Flirc in the Acer I programmed one or two keys in the Toshiba Laptop so the problem of taking it from the Windows 7 x64 and plug in the XBMCbuntu is gone too. The weekend will tell us more about the firmware and the earlier problems. More time for watching movies :) Thanks for all the tips and support. Cheers!
  2. Hi Jason. Took the Flirc to work and tested on a workstation with Ubuntu 11.10. Installed the Flirc and XBMC to test it out. Did what you said, programmed the wake v6 and thing seemed to work well. Did a few reboots and the Flirc never went to bootloader. The only bad thing that happened was the long keypress stopped working in the end of the day after a shutdown and a turn on ... I had to format again, put the wake v6 again and did all the key saving again. Now I'm going to test it out in the XBMC on the living room. I'll keep in touch. Thanks.
  3. Same with fw_1.0.bin ... My XBMCbuntu has LIRC running... can it affect Flirc in any way? [ 2652.480082] usb 2-6: new low speed USB device number 27 using ohci_hcd highlander@XBMC-SALA:~$ lsusb Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 002: ID 046d:c058 Logitech, Inc. M115 Mouse Bus 002 Device 003: ID 04f2:0402 Chicony Electronics Co., Ltd Genius LuxeMate i200 Keyboard Bus 002 Device 027: ID 20a0:0000 Clay Logic highlander@XBMC-SALA:~$ flirc version Flirc Version 1.0.2 [c6ade381b9852122] Bootloader Detected: v1.400000 highlander@XBMC-SALA:~$
  4. Everytime I unplug the Flirc from the PC it gets into bootloader... Sometimes with reboot\shutdown it gets into the bootloader... I'm using the fw_repeat.bin.
  5. Ok I found, let's call it, a bug in the whole proccess. Everytime I take the Flirc from Windows7 x64 to XBMCbuntu it stays in the bootloader. To make it work again with the long keypress FW (fw_repeat.bin) I first have to put the fw_1.0.bin firmware. Only after that I can put the fw_repeat.bin and load the keys config I have saved. I had to do the same proccess in Windows 7 x64 to make it work again. Here is a log of what I've done in XBMCbuntu: highlander@XBMC-SALA:~$ flirc version Flirc Version 1.0.2 [c6ade381b9852122] Bootloader Detected: v1.400000 highlander@XBMC-SALA:~$ flirc format Formatting Device, please wait...can't execute command, device in bootloader highlander@XBMC-SALA:~$ flirc upgrade fw_ fw_1.0.bin fw_repeat.bin fw_wake_v6.bin highlander@XBMC-SALA:~$ flirc upgrade fw_1.0.bin Uploading image: fw_1.0.bin to "flirc.tv" 0x20A0 [DEVICE] Waiting [DEVICE] Bootloader Detected [DEVICE] Uploading [uPLOADING] ------------------------------------------------------------------ Pages Total Pages Progress 0x03b80 ... 0x03c00 [========================================>] 100% -------------------------------------------------------------------------------- [DEVICE] Waiting. [DEVICE] FW Detected [DEVICE] EOK highlander@XBMC-SALA:~$ flirc format Formatting Device, please wait... Done! highlander@XBMC-SALA:~$ flirc loadconfig good_flirc_xbmc_final.fcfg Loading Configuration File 'good_flirc_xbmc_final.fcfg' to Device [========================================>] 100% Configuration File Loaded Successfully highlander@XBMC-SALA:~$ flirc format Formatting Device, please wait... Done! highlander@XBMC-SALA:~$ flirc upgrade fw_repeat.bin Uploading image: fw_repeat.bin to "flirc.tv" 0x20A0 [DEVICE] Waiting [DEVICE] FW Detected [DEVICE] Setting DFU [DEVICE] Waiting. [DEVICE] Bootloader Detected [DEVICE] Uploading [uPLOADING] ------------------------------------------------------------------ Pages Total Pages Progress 0x03b80 ... 0x03c00 [========================================>] 100% -------------------------------------------------------------------------------- [DEVICE] Waiting. [DEVICE] FW Detected [DEVICE] EOK highlander@XBMC-SALA:~$ flirc loadconfig good_flirc_xbmc_final.fcfg Loading Configuration File 'good_flirc_xbmc_final.fcfg' to Device [========================================>] 100% Configuration File Loaded Successfully After all this, the Flirc is working fine in XBMCbuntu. BUG? I guess I have to do the same for the other beta firmwares if I want to test them. Cheers!
  6. highlander@XBMC-SALA:~$ flirc version Flirc Version 1.0.2 [c6ade381b9852122] Bootloader Detected: v1.400000 highlander@XBMC-SALA:~$ flirc upgrade fw_repeat.bin Uploading image: fw_repeat.bin to "flirc.tv" 0x20A0 [DEVICE] Waiting [DEVICE] Bootloader Detected [DEVICE] Uploading [uPLOADING] ------------------------------------------------------------------ Pages Total Pages Progress 0x03b80 ... 0x03c00 [========================================>] 100% -------------------------------------------------------------------------------- [DEVICE] Waiting. [DEVICE] FW Detected [DEVICE] EOK highlander@XBMC-SALA:~$ flirc loadconfig good_flirc_xbmc_final.fcfg Loading Configuration File 'good_flirc_xbmc_final.fcfg' to Device [========================================>] 100% Configuration File Loaded Successfully highlander@XBMC-SALA:~$ flirc version Flirc Version 1.0.2 [c6ade381b9852122] Firmware Version: 255.1 10-02-2011 No long press after doing it on Ubuntu. Removing the Flirc and going back to Windows 7 x64 the long press doesn't happen either. Why? What causes Flirc being in bootloader when plugged in linux? What causes Flirc not working with long key presses in windows 7 x64 after being programmed in linux with the same fw and keys config?
  7. When I plugged the Flirc into XBMCbuntu I get this: highlander@XBMC-SALA:~$ flirc version Flirc Version 1.0.2 [c6ade381b9852122] Bootloader Detected: v1.400000 highlander@XBMC-SALA:~$ pwd /home/highlander highlander@XBMC-SALA:~$ flirc saveconfig xbox_long_press Saving Configuration File 'xbox_long_press.fcfg' to Disk can't execute command, device in bootloader Last time I had to re-write the firmware for it to work again. What causes Flirc to get into bootloader after removing from windows and plug into linux? Thanks.
  8. I just "upgraded" to the fw_repeat.bin and seems back to normal the repeat rate, long key press is working in Windows 7 x64. I'll plug into XBMCbuntu and check it out. I'll be back! :)
  9. Back after a few tests. After I plugged the Flirc into XBMCbuntu the WDTV remote stopped repeating while the button is pressed which makes my finger get stronger (joke) and tired. Why would the remote work correctly in Windows 7 x64 and not on linux? After I re-plugged into Windows the remote repeating was the same as in linux, no repeat, just a key press. Been trying all the firmwares and remapping the keys to get the repeated keypress to work again. Any ideias why this is happening?
  10. Playing with Flirc!

  11. Hello all, I've received the Flirc and I've tested a few remotes. If I get my hands on more remotes I'll post them here. The setup was made in a Winblows 7 Laptop running x64bits. Used the beta firmware fw_wake_v6.bin that gave me better results, faster with the cursor buttons if long pressed. After everything was done the Flirc went to it's place, the Acer Revo 3600 running XBMCbuntu. Here's the list of the tested remotes: OLD XBOX 1 Remote - Doesn't work properly (which is a shame unfortunaly) MEO BOX Remote (Portuguese CableTV Microsoft Box) - the "cross" doesn't work properly WDTV (ver 1) - Works flawless mapping with the full keyboard in the controller menu. WDTV Remote - > Controllers Menu POWER -> S in Full Keyboard (Shutdown Menu) HOME -> HOME in XBMC UP -> UP Arrow in Full Keyboard LEFT -> LEFT Arrow in Full Keyboard DOWN -> DOWN Arrow in Full Keyboard RIGHT -> RIGHT Arrow in Full Keyboard BACK -> BACKSPACE in Full Keyboard (Parent) STOP -> X Arrow in Full Keyboard (Stop) OPTION -> C in Full Keyboard (Title\Right Mouse Button) REV -> TAB in Full Keyboard (Explorer while playing) PAUSE/PLAY -> P in Full Keyboard (Pause/Play) FF -> O in Full Keyboard (Codec Info) PREV -> Volume Down NEXT -> Volume UP SEARCH -> I in Full Keyboard (Info) EJECT -> M in Full Keyboard (Menu)
×
×
  • Create New...