Mouse working in OPENWRT

In order to get the mouse to work in OpenWRT, you need to have all the proper USB modules loaded. I have covered this in the past in showing how to get the Pegasus joystick to work. After everything is loaded, if you have done it right, if you plug in the mouse into the router and check dmesg the mouse should show up, but it will not be registered under /dev/mouse0. In order to get that part to work you have to go under make kernel_menuconfig and go to
Device Drivers
->input device support
[M] Mouse

remake the kernel make all V=99

After that is done the kernel module is found under
Kamikaze/trunk/build_dir/linux-brcm47xx/linux-2.6.30.8/drivers/input/mousedev.ko

just scp that over to root@OpenWrt:/lib/modules/2.6.30.8

yours may vary slightly if you have a newer kernel

Then go to

root@OpenWrt:/etc/modules.d

then
vi 72-mouse

and insert by pressing i, type
mousedev

then exit and save by typing :wq! (basic vi)

then reboot the router and try plugging in a mouse

then test it by using

cat /dev/mouse0

I left the mouse stuck in and it didn't work so I unplugged it and replugged it and it worked just fine. I can look into this issue in the future.

Arduino 168 3.3 ttl serial

I've been trying to get my rbbb to communicate with my router which outputs 3.3 volt serial. In all reality I only need receive to work. However connecting it directly did not work. I went through the trouble of bulding a level shifte using a mosfet I bought at radioshack. I carefully put it together and used my parallax oscilloscope to look at the waves. It was dead on. I then tried connecting it to the arduino and it worked. I then soldered up a cable so that it would connect in place of the ftdi cable and it did not work. Something happens to the serial signal from input to rx input, As oppose to connecting a tx line directly to a pin. I have to check and see what is going on.

Ugh, found out what the problem was. On the RBBB the tx label actually stands for the tx label on the connector not the chip. So I probably could connect directly with 3.3v ttl without an issue. I will have to check this.

i2c

i2c-core
i2c-dev
i2c-algo

i2c-gpio-custom
i2c-gpio

Remote Desktop Error 1702 getting session names. Error [1702]: The binding handle is invalid.

I have it working now, if you can't get Remote Desktop working. AKA it was working before and it suddenly stopped, an update may have gotten you. After some googling and a bit of fiddling I brought up the cmd prompt and got the Error[1702] error when typing qwinsta. The problem ended up being that somehow my Terminal Services were disabled.

I fixed it by going to control panel -> Administrative Tools -> Services

Scroll down to terminal services right click, go to properties and set to automatic, then right click and click start service. This may work for you, it did for me.

controlling pins on Openwr Kamikaze

Just for those people, (reminder to myself), looking for a way to easily control LEDs and other lights on a OpenWRT router running Kamikaze. Login to the router and install kmod-gpio-dev


$>opkg install kmod-gpio-dev
$>cd /proc/diag
$>cd leds
$>echo 0 > power


This should cause your power light to start blinking. You can send 0 or 1 to any of these LEDs listed in LEDs.

kmod-leds-gpio is not available

I was trying to compile the package kmod-leds-gpio in Kamikaze but it didn't show up. It seems that there is an issue with the latest version of default kernel_config for that module, in order to get it to work type


$>make kernel_menuconfig


Then go to

[*] LED support -->
[M] LED support for GPIO connected Pins

OpenWRT Kamikaze compile single package

I found the solution to this on this site
openwrt building

You have to type the following to compile a package without compiling the entire build tree


$> make package/i2c-gpio-custom/{clean,compile,install} V=99 DEVELOPER=1


This is from the top directory of Kamikaze.