How to: setup wakeup with your IR remote control

jernej · Published in 2016-10-20 00:42:24

giaur500 replied at 2016-10-19 17:31
What do you mean by reboot? It was booted after sd card inserted after replacing script.bin on PC. M ...

Well, there is more than one way to replace script.bin and not all require to take out SD card. Anyway, try with 0xB24D instead of 0x4D.

giaur500 · Published in 2016-10-20 01:01:50

Still not working. So, this soultion is not universal. It sometimes may work, sometimes not

jernej · Published in 2016-10-20 01:30:25

giaur500 replied at 2016-10-19 18:01
Still not working. So, this soultion is not universal. It sometimes may work, sometimes not

I don't think there is another one. You may try another key. From what I know, it doesn't need to be KEY_SLEEP. For me, it works as KEY_POWER, but you can try also KEY_0 or any other. As last resort, you can backup lircd.conf and try from scratch again. Did you make some other script.bin change too?

giaur500 · Published in 2016-10-20 01:37:11

No, no other changes

giaur500 · Published in 2016-10-20 02:26:56

Edited by giaur500 at 2016-10-20 02:29

Is lircd.conf read during boot? If not, key mapping should not matter. I guess the only requirement is to have hardware in sleep state and make neccesary script.bin changes. Abd then device should wake up, right? Or it's also related to lirc config as well?
Maybe only some amount of codes are supported? Should I try with other remote?

jernej · Published in 2016-10-20 04:40:21

giaur500 replied at 2016-10-19 19:26
Is lircd.conf read during boot? If not, key mapping should not matter. I guess the only requirement ...

Not in the driver, but systemd service load it, so yes, it doesn't matter. I partly reverse engineered ARISC IR driver and I can tell you that it looks almost the same as original Allwinner IR driver. I would say that codes don't matter really.

Definetly try with another one, as long as it outputs NEC protocol.

andreq · Published in 2016-10-20 06:29:37

jernej replied at 2016-10-20 00:42
Well, there is more than one way to replace script.bin and not all require to take out SD card. An ...

I'd be interested in knowning those other ways as I just installed everything on the build-in emmc and I think changing the script.bin might be a pain now :S

jernej · Published in 2016-10-20 13:26:56

andreq replied at 2016-10-19 23:29
I'd be interested in knowning those other ways as I just installed everything on the build-in emmc ...

First make flash folder writable:

mount -o remount,rw /flash

Copy code

and then copy script.bin with scp, for which you have to have ssh enabled. For example, on host PC for command line tool on Linux:

scp script.bin root@192.168.0.10:/flash

Copy code

For Windows, there is graphical tool WinSCP.

andreq · Published in 2016-10-21 04:46:29

jernej replied at 2016-10-20 13:26
First make flash folder writable:and then copy script.bin with scp, for which you have to have ssh ...

Thanks a lot!
I'm using a samba share to copy to my windows pc already hehe.
Cant wait to have sunxi tools are included in the build, I won't be needing to go back and forth Kodibox -> Window PC -> Linux VM -> Windows PC -> KodiBox

bir8339e · Published in 2016-10-23 03:39:39

glaur500,

Unlike mine, your lircd.conf indicates that the key streams are not of a constant length. Please follow these instructions so we can find out what your remote is sending out:

1. Connect to the board through SSH.
2. Kill the lircd process and record just the stream for the POWER key like this:

killall lircd
irrecord -f test.conf

Copy code

3. Follow the instructions carefully but record just the POWER key.
4. Once you're done copy the 'test.conf' file out through the Samba share (or a USB pen drive) and post it here.
5. Reboot the board from the SSH prompt (type 'reboot' and press ENTER) to restart everything again (just don't unplug it without any kind of controlled shutdown).

This is the file I got:

begin remote
name test.cfg
flags RAW_CODES
eps 30
aeps 100
gap 129815
begin raw_codes
name KEY_SLEEP
9040 4528 552 560 576 560
528 1728 544 608 504 624
536 568 568 584 504 632
528 568 576 1712 536 560
576 1696 552 1704 520 1728
544 608 504 1728 576 560
520 616 552 1696 520 1728
576 1704 544 568 568 568
520 632 528 1704 520 1728
576 576 504 616 552 560
576 1696 552 1704 520 1728
568 75543 9016 2256 576

Copy code

What's represented are times in microseconds for logical level pairs (one followed by zero). So the first two are the header and the next read as (check the NEC protocol definition on the first post):

0 0 1 0 0 0 0 0 = 0x20
0 1 0 1 1 1 0 1 = 0x5D
0 0 1 1 1 0 0 0 = 0x38
1 1 0 0 0 1 1 1 = 0xC7

The last line is the time until and the key release and can be ignored. This is where those codes in my 'lircd.conf' are coming from. Please share your file so we can find out why your remote is not recognized.