Activity for Jonas Bertels
-
Jonas Bertels posted a comment on ticket #349
Ok, then consider it closed. I personally no longer have a problem since I now have a plethora of controllers that actually do work, thanks to some scavenging around the company. Thanks for helping me! It got me a lot of information that I would have otherwise probably missed.
-
Okay, was able to reproduce with a R724075 but not with a RM368701 nor a TSFP-IR01 (R724075 has the same output as my R8769195 when using mode 2, so it likely uses RC5, while if I switch the R8769195 to NEC, it returns the same mode2 values as the RM358801.) So TL,DR: if you use a (Barco?) RC5 controller, you can reproduce. EDIT: Samsung TM1781A works, but I think this is not 36 kHz (cannot reproduce seg fault)
-
Okay, was able to reproduce with a R724075 but not with a RM368701 nor a TSFP-IR01 (R724075 has the same output as my R8769195 when using mode 2, so it likely uses RC5, while if I switch the R8769195 to NEC, it returns the same mode2 values as the RM358801.) So TL,DR: if you use a (Barco?) RC5 controller, you can reproduce. EDIT: Samsung TM1781A works (cannot reproduce seg fault)
-
Okay, was able to reproduce with a R724075 but not with a RM368701 nor a TSFP-IR01 (R724075 has the same output as my R8769195 when using mode 2, so it likely uses RC5, while if I switch the R8769195 to NEC, it returns the same mode2 values as the RM358801.) So TL,DR: if you use a (Barco?) RC5 controller, you can reproduce.
-
Okay, was able to reproduce with a R724075 but not with a RM368701 nor a TSFP-IR01 (although I think these are both NEC. I'm trying to find some more RC5 remotes).
-
Okay, used the oscilloscope and the signal is indeed not modulated (just bits)(EDIT Ignore this, I'm an idiot, it's modulated at 36 kHz for RC5 and 38 kHz for NEC). LIRC does seem capable of reading this though, but it's very unstable. When I started using it, there were never any segmentation faults, and now, even after flashing my SD card with the original image and replacing my odroid C2, it continually gives segmentation faults, which I really don't understand.
-
ok, thanks! What should I do to reduce the possibillities further? EDIT: To make sure it's perfectly clear for other people, here is what you need to do to reproduce: 1) Get an Odroid C2 (not sure if hardware effects this) and a Barco RC5 remote (R8769195) 2) "modprobe ir-meson" 3) "irrecord" 4) follow the instruction and during the part of random button presses, press at least one key that is not 0-9 5) This should create a segmentation fault after 2 lines have been created. EDIT2: I'm hunting for...
-
ok, thanks! What should I do to reduce the possibillities further? EDIT: To make sure it's perfectly clear for other people, here is what you need to do to reproduce: 1) Get an Odroid C2 (not sure if hardware effects this) and a Barco RC5 remote (R8769195) 2) "modprobe ir-meson" 3) "irrecord" 4) follow the instruction and during the part of random button presses, press at least one key that is not 0-9 5) This should create a segmentation fault after 2 lines have been created.
-
EDIT: I can't use IrScrutinizer right now because I have no access to the tools necessary to recompile the kernel with IrScrutinzer added. Ran mode2 while still in NEC mode (facepalm) let me try with RC5. EDIT2: Ran mode2 in RC5, cannot reproduce, gives pulses and spaces length for both numeric and non-numeric keys. With irrecord, it seems to recognize buttons being send, and doesn't crash it immediately, it's only if you send it 2 full lines of keys in irrecord that it crashes with a segmentation...
-
ok, thanks! What should I do to reduce the possibillities further?
-
EDIT: I can't use IrScrutinizer right now because I have no access to the tools necessary to recompile the kernel with IrScrutinzer added. Ran mode2 while still in NEC mode (facepalm) let me try with RC5. EDIT2: Ran mode2 in RC5, cannot reproduce, gives pulses and spaces length for both numeric and non-numeric keys. Just like with irrecord, it seems to recognize buttons being send, and doesn't crash it immediately, it's only if you send it 2 full lines of keys in irrecord that it crashes with a segmentation...
-
EDIT: I can't use IrScrutinizer right now because I have no access to the tools necessary to recompile the kernel with IrScrutinzer added. Ran mode2 while still in NEC mode (facepalm) let me try with RC5.
-
Cannot reproduce with mode 2, when just running "mode2" I get pulses and spaces whether pressing numbers or otherwise. Same when using "mode2 --driver=default". "mode2 --driver=devinput" throws "read() failed," There are no segmentation faults EDIT: I can't use IrScrutinizer right now because I have no access to the tools necessary to recompile the kernel with IrScrutinzer added.
-
Cannot reproduce with mode 2, when just running "mode2" I get pulses and spaces whether pressing numbers or otherwise. Same when using "mode2 --driver=default". "mode2 --driver=devinput" throws "read() failed," There are no segmentation faults
-
Okay, after some more testing, I'm unable to reproduce the segmentation fault with NEC. Maybe I accidently switched back to RC5 when recieving my segmentation fault, so I'll consider NEC working. That means the segmentation fault must be, as you suggested, caused by a demodulation problem. My reciever demodulates 37.9 kHz, while in RC5 mode, my remote transmits on a 36 kHz carrier frequency. Thanks for helping me, and if you wish, you can close this ticket, my problem has been fixed. I'll just have...
-
Okay, after some more testing, I'm unable to reproduce the segmentation fault with NEC. Maybe I accidently switched back to RC5 when recieving my segmentation fault, so I'll consider NEC working. That means the segmentation fault must be, as you suggested, caused by a demodulation problem. My reciever demodulates 37.9 kHz, while in RC5 mode, my remote transmits on a 36 kHz carrier frequency. Thanks for helping me, and if you wish, you can close this ticket, my problem has been fixed. I'll just have...
-
Besides, it must have something to do with Lirc, because while I'm undoubtedly doing something wrong with the signals I'm sending to Lirc, I don't understand how I can cause segmentation errors by doing this. I didn't just get segmentation errors with the 36 kHZ RC5 demodulated with 38 kHz (which is obviously wrong), but also with the NEC, which according to the specs is 38 kHz
-
Besides, it must have something to do with Lirc, because while I'm undoubtedly doing something wrong with the signals I'm sending to Lirc, I don't understand how I can cause segmentation errors by doing this. I didn't just get segmentation errors with the 36 kHZ RC5 demodulated with 38 kHz (which is obviously wrong), but also with the NEC, which according to the specs is 38 kHz
-
Besides, it must have something to do with Lirc, because while I'm undoubtedly doing something wrong with the signals I'm sending to Lirc, I don't understand how I can cause segmentation errors by doing this.
-
It certainly can be done on the odroid (replacing the hardware part on the odroid with a software-only reciever is kind of the point of this project). However, I was using the oscilloscope incorrectly: (Sorry for the confusion) The Barco signal DOES get modulated (at least according to the guy who designed the remote control) with 36 kHZ for the RC5 (which is probably what gets me into trouble with the 38 kHz demodulation) and 38 kHZ for NEC (this should work but it still results in segmentation...
-
Okay, used the oscilloscope and the signal is indeed not modulated (just bits). LIRC does seem capable of reading this though, but it's very unstable. When I started using it, there were never any segmentation faults, and now, even after flashing my SD card with the original image and replacing my odroid C2, it continually gives segmentation faults, which I really don't understand.
-
The hardware I'm using is an Odroid c2 with a kernel my collegues built using buildroot.
-
Thanks! I'll ask around (I'm currently working at Barco). I do remember getting a 38kHZ reading while using the oscilloscope but I'll check again.
-
Segmentation error during irrecord when recording non-numeric buttons during startup
-
Acutally,... I've just used my reomte control with NEC. the first time it worked, except when I was trying to log the power button. It wouldn't log the power button , I used up all my retries, and had to start over. When I started over, it began throwing segmentation errors again in the same manner as described for RC5 (only accepts numbers in the first stage)
-
BARCO RC5 Remote (R8769195) causes segmentation fault during irrecord initial stage
1
