Skip to main content ↑ ↓

Messages

This section allows you to view all Messages made by this member. Note that you can only see Messages made in areas you currently have access to.

Messages - JessH

2
USB Infrared Toy / Re: OLS: no such port error after each capture.
Okay, much better with the right settings. Certain sample rates also cause it to lose the device. Found the new config file in the irtoy package. It sets the sample rate to 10.040khz. Is that still correct? The results of using the measure clock tool on the raw ir channel seems way off with this sample rate(1.7khz instead of 36khz) but if I change the samplerate to 100khz results are a lot closer to those expected. Of course the problem could actually be something else entirely(including me not knowing how to use the tool properly)

~Jess
4
USB Infrared Toy / Re: Using Frequency Report
Okay. Just wanted to make sure im not reinventing the wheel.

Is the reason the IR Toy doesn't have a more user friendly commandline style interface like the bus pirate because the chip is lacking space or is it because you didn't expect it to be used that way/it hasn't been implemented?
5
USB Infrared Toy / Re: fw_update not working in linux or OS X
Sorry about that. Did a make clean and make distclean but didn't do a proper check of what all might be hanging around. Not a lot of free time these days so I just have a few minutes here and there to work on stuff. I will try to clean it up tomorrow and will post a new link when I do.
6
USB Infrared Toy / OLS: no such port error after each capture.
Ir Toy V2 with v22 firmware. OLS 0.9.5 running in Funtoo(Gentoo) Linux.
When I try to capture a signal all I get is a blank line. When I try to rerun the capture I get "I/O problem: No Such Port!"
dmesg gives me: "tty_port_close_start: tty->count = 1 port count = 0."
The device still exists but if I try to open it with a terminal emulator I get "cannot open /dev/ttyACM0: Input/output error"
If I unplug and replug in the IR Toy it will let me try to capture again but then the exact same thing happens.

Ideas? I seem to be running into every possible problem with this thing...

~Jess
7
USB Infrared Toy / Using Frequency Report
Is there any software that uses the frequency reading abilities of the IR toy? I need to be able to find the frequencies that various remotes transmit at. The docs seem to cover the commands involved but am I going to have to write my own software to use it or is there something out there?
8
USB Infrared Toy / Re: fw_update not working in linux or OS X
I got fw_update working by taking the fixes from the version of it from the logic sniffer git tree. This means that it now compiles with newer versions of gcc and can actually find the ir toy in linux. The source is available here: http://jesshaas.com/software/IRToy-fw_update.tar.gz This really should be put in the irtoy package and the docs should be updated.

robots-Would love to get your loader working as it would be nice if there was one loader for the various devices. Unfortunately I don't really have any more time to futz with it right now. Maybe if I get some more time later on I will try to get it working.

-Jess
9
USB Infrared Toy / Re: fw_update not working in linux or OS X
Yes. I changes it to 6000 as in the origional diolan fw_updater. Didn't fix the problem. Changing  OLS_FLASH_TOTSIZE to an arbitrarily large value bypasses the error but things don't work properly. Verify gives me lots of lines like this:
Diff @0x3d7d (Is 0xff should be 0xec)
Diff @0x3d7e (Is 0xff should be 0x17)
Diff @0x3d7f (Is 0xff should be 0xf0)
Diff @0x3d80 (Is 0xff should be 0xfb)

And I still don't have a working device.
10
USB Infrared Toy / Re: fw_update not working in linux or OS X
Based on the source of the other loader looks like 32 should be the right number:
size_t PicBootloader::page_size(PicBootloader::MemoryType memory)
{
        switch (memory)
        {
                case MEM_FLASH:
                        return 32;
                case MEM_EEPROM:
                        return 8;
                case MEM_ID:
                        return BOOT_ID_LEN;
                default:
                        return 8;
        }
}

Made those changes but I am getting the following error:
~user/Downloads/robots-ols-fwloader-fb4a14a/src/ols_fwloader -d -f BOOT -W -w ~user/Downloads/IRToy/firmware/USBIRToy.v22.hexBootloader version 0.2.2
Bootloader version 0.2.2
Reading file '/home/user/Downloads/IRToy/firmware/USBIRToy.v22.hex'
Data won't fit into buffer (size= 4000 want 4010)
Error reading file - skipping write
11
USB Infrared Toy / Re: fw_update not working in linux or OS X
I knew it wasn't intended for the irtoy but it seemed to be based on the same source and more up to date so I figured that I would see if it could find it. It did. Was planning on diffing the sources but your pointers most likely just saved me a whole lot of time.
13
USB Infrared Toy / Re: fw_update not working in linux or OS X
I tried the ols-fw-update binary from the latest open logic sniffer package and it finds the device, erases and writes the firmware but then fails at the verify step. I took away the -v option and it erased, wrote and rebooted but the irtoys serial device never shows up.So looks like the diolan's firmware_update utility linked from the irtoy docs is broken(atleast with modern linux and gcc) and the ols-fw-update doesn't work properly with the irtoy.

Ideas?

-Jess
14
USB Infrared Toy / fw_update not working in linux or OS X
I compiled fw_update in both linux and Mac OS X. In both cases it can't find the ir toy and this is all I get:
# fw_update -e -w -v -m flash -vid 0x04d8 -pid 0xfd0b -ix USBIRToy.v22.hex
U2IO flash erasing: FAILED.
Device is not found.
Operation aborted.

I put the ir toy in to update mode with $ and the light is on. Linux does see the device. This is my current dmesg:
[31831.451058] usb 3-1: new full-speed USB device number 4 using ohci_hcd
[31831.651078] usb 3-1: New USB device found, idVendor=04d8, idProduct=fd0b
[31831.651089] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[31831.651098] usb 3-1: Product: Diolan
[31831.651103] usb 3-1: Manufacturer: Diolan
[31831.664076] generic-usb 0003:04D8:FD0B.0003: claimed by neither input, hiddev nor hidraw

I originally had hidraw enabled in the kernel and the message was slightly different and /dev/hidraw0 (or something like that) was created. It didn't see the device so I thought maybe the driver was conflicting with libusb. removing it didn't fix it.

I am currently stuck in update mode and my brand new ir toy is useless. Any ideas?

~Jess

( ! ) Fatal error: Uncaught exception 'Elk_Exception' with message 'Please try again. If you come back to this error screen, report the error to an administrator.' in /var/www/dangerousprototypes/forum/sources/database/Db-mysql.class.php on line 696
( ! ) Elk_Exception: Please try again. If you come back to this error screen, report the error to an administrator. in /var/www/dangerousprototypes/forum/sources/database/Db-mysql.class.php on line 696
Call Stack
#TimeMemoryFunctionLocation
10.01522425072session_write_close ( )...(null):0
20.01552556672ElkArte\sources\subs\SessionHandler\DatabaseHandler->write( )...(null):0
30.01552557448Database_MySQL->query( ).../DatabaseHandler.php:119
40.05722696192Database_MySQL->error( ).../Db-mysql.class.php:273