What do you mean with further patching? Because I´ve got lirc running with my USBIR Toy on my Raspberry Pi with help of the two patches. Everything is running fine. Except I can only send one RAW Code every 15 seconds or so. It seems lirc is waiting for something after sending, but then gets a timeout and I can send again. RC5 codes are running without any Problems. I don´t think it´s the firmware because the codes are running fine with WinLirc.
After that comes an confirmation but too fast to read. And that´s it.
Also are you flasinhg in Windows or an linux distribution?
Is the IRToy right now in bootloader mode? (led is continuously on when connected) Disconnect the IRToy and shorten the PGC and PGD pins with a jumper/wire and then stick it in the usb port again. This puts it in bootloader mode. Then try flashing again. After flashing disconnect the Toy and remove the jumper.
If you find someone who pays for that... Every signing of the driver costs about 250$ for each Windows version. Also you have to pay for resigning with every change of the driver. And you have to send them the hardware to test the driver.
The testing for the signing is also a lot of work. You have to test it with every Windows Version you want it to have signed it with. (Home, Professional, Ultimate, x86, x64 etc) But you can also let them test it. But you can think of it. Costs extra.
That is one of the reasons why drivers for several devices often are not published very fast... At least in Windows.
Well you could sign the driver yourself using private signing. But if you have an official driver everybody can downaload that´s no solution.
Thanks alot for this little advice. Also made it like this. The only difference is using the USBIRToy.source.r1611.v22.zip for downloading the source code.
Seems there is a problem in the SVN Repository? Because when I compile the SVN code the file only has 37 Kb and isn´t working.
SO I´ve compared the code and found out the SVN Code doesn´t include the USB Stack but tries to include it by itself? In general the code seems to be very different. Maybe it´s a work in Progress? But then why is it in the trunk folder of SVN?
I copied the in the project missing files into the root folder and started the compiler. The compiler got through without any errors. But the created hexfile only has 37 kb and apparently doesn´t work.
Now I´m looking further to find out what the problem is.
You can use WinLirc with such Hexcodes. A config would look like below. (Example for one of my Remotes) The Problem here will be the Header with the data of your remote. If all your configs are in RawMode my config won´t help you I think. But you can try to create a header with irrecord from WinLirc. Also you can record the signals with irrecord if the hexcodes won´t work.
I just checked the code out from the SVN repo and compiled it.
It seems only the IRToy.dll files in the Download Section from WinLirc on Sourceforge have that Problem with Raw Codes. I can´t tell what the difference is, because I don´t know the code of the Downloadable dll.
Shouldn´t it be the same? Maybe you have already fixed this, but didn´t Upload a new file. That´s my guess.
But I already tried that. Recording in Raw Mode gives the same errors.
Because it won´t work under Linux (tried several settings and solutions I found on the net), I´ve installed a virtual machine with Windows XP and used an older version of irrecord.
Seems that the driver has severe Problems when used under Windows 8 for recording.
With that it was possible to Record one of the two problematic Remotes with Space/Pulse coding.
The other Remote (Sony RM-AAU0020) still is making troubles. I could record it in RAW Mode, but every button gives some errors before it records. (Signal length not uneven or too long.)
And WinLirc can´t play the config after that. When sending commands it just gives an error "Not supported".
Now I´m still trying to figure out how the raw hex codes from IRToy Rec/Play can be converted to the raw Integer values of WinLirc, but I can´t see a pattern yet.
The IRToy Rec/Play hex codes look something like this. (Not the actual values)
00 2C 00 27 00 54 00 51 00 2A ... and so on.
So i thought the Integer values should always consist of two bytes (00 and 2C). So I´ve written a converter that takes always two bytes and converts them to integer. But the numbers won´t make any sense...
Now I´m searching for a documentation of the WinLirc config in RAW mode or anything that can help me with that.
Edit: Can´t find Docs about this so I´m going through the code of irrecord and WinLirc.