File:Capture anybus tools mailbox.png

2011-07-27T09:01:56Z

KevinJ: Print screen anybus tools mailbox interface

Print screen anybus tools mailbox interface

File:Capture anybus tools edit input.png

2011-07-27T09:00:35Z

KevinJ: Print screen of the anybus tools edit input

Print screen of the anybus tools edit input

2011-05-11T21:17:22Z

KevinJ: /* Links */

This page explain how to use Infrared USB HID Remote on APF board. Some (but not all) are supported by the Linux kernel.

==Driver installation==

We have to know the model of your USB device under Linux. Connect it on a PC with Linux running, open a console and type:

<pre class="host">
$ dmesg
</pre>

You should obtain something like that :

<pre class="host">
[ 8893.213869] generic-usb 0003:062A:0000.0005: input,hidraw0: USB HID v1.10 Mouse [HID 062a:0000] on usb-0000:00:1d.0-2/input0
[ 9739.616076] usb 3-2: new low speed USB device using uhci_hcd and address 5
[ 9739.942974] zydacron 0003:13EC:0006.0006: fixing up zydacron remote control report descriptor
[ 9739.978243] input: HID 13ec:0006 as /devices/pci0000:00/0000:00:1d.1/usb3/3-2/3-2:1.0/input/input16
[ 9739.979060] zydacron 0003:13EC:0006.0006: input,hiddev0,hidraw1: USB HID v1.10 Keyboard [HID 13ec:0006] on usb-0000:00:1d.1-2/input0
</pre>

The last line give the model and the identifier of the product : "Zydacron"
If you don't see anything about the model of your HID device, copy/paste the identifier in google. The identifier must be something like that : 13ec:0006
It always be composed of 4 characters, ":", and 4 characters again.

Then, configure your Linux configuration in your armadeus directory
<pre class="host">
$ make linux26-menuconfig
</pre>

<pre class="config">
Device Drivers --->
[*] HID Devices --->
Special HID drivers --->
</pre>

And then, search your driver (Zydacron in our case).
<pre class="config">
<M> Zydacron remote control support
</pre>

Reflash kernel and rootfs.

==Load the driver==

You must know the module name of the driver.
For Zydacron it is "hid_zydacron".

If you don't know the name of your Linux driver:

<pre class="apf">
# ls /lib/modules/$(uname -r)/kernel/drivers/hid/
</pre>

{{Note| $(uname -r) will be replaced with your kernel version. }}

You should see some or one file(s) with the ".ko" extension, like your_hid_driver.ko (hid_zydacron.ko in our case).

then :
<pre class="apf">
#modprobe your_hid_driver
</pre>

in our case:
<pre class="apf">
# modprobe hid_zydacron
</pre>

==Usage==

Plug the usb receiver of your remote on APF board and type
<pre class="apf">
# modprobe dmsg
</pre>

If you read the model name of your device and something like "eventX" where X is the event number, the Linux input is ready.

Check if the event is correctly set in the input directory:
<pre class="apf">
# ls /dev/input/
</pre>

You should read the event of your device.

Check if the communication is set (replace X by your event number, usualy 0 if no hid device other than your remote has been plugged)
<pre class="apf">
# od -x /dev/input/eventX
</pre>
Push a button on your remote. You should see some incomprehensible characters on the screen, don't worry it sounds good!

==Application example==

The USB HID remote device is configured in Linux like a keyboard.

Here a little example of application in langage C :
<source lang="c">
#include <linux/input.h>
#include <sys/types.h>
#include <sys/stat.h>
#include <fcntl.h>
#include <stdio.h>
#include <unistd.h>

/* Replace X by the number of your event */
char input[] = "/dev/input/eventX";

int main(void)
{
int fd;
struct input_event remote_event;
fd = open(input, O_RDONLY); /* Open the event file */

if(fd == -1) {
printf("Can not open the input device!\n");
return 1;
}
else {
while (1) {
read(fd, &remote_event, sizeof(struct input_event)); /* read the last event */
if(remote_event.type == EV_KEY && remote_event.value == 1) { /* Check if a key was pressed */
if(remote_event.code==103) { /* Compare with key up code */
printf("Key up was pressed\n");
}
else if(remote_event.code==108) { /* Compare with key down code */
printf("Key down was pressed\n");
}
/* ... */
else {
printf("Unknown button with code %d was pressed\n", remote_event.code); /* Print code */
}
}
}
}

return 0;
}
</source>

==Links==
Getting started with uinput [http://thiemonge.org/getting-started-with-uinput]

A little example of code in C [http://thiemonge.org/getting-started-with-uinput]

IR HID USB Remote

2011-05-11T21:15:50Z

KevinJ: New page: This page explain how to use Infrared USB HID Remote on APF board. Some (but not all) are supported by the Linux kernel. ==Driver installation== We have to know the model of your USB de...

This page explain how to use Infrared USB HID Remote on APF board. Some (but not all) are supported by the Linux kernel.

==Driver installation==

We have to know the model of your USB device under Linux. Connect it on a PC with Linux running, open a console and type:

<pre class="host">
$ dmesg
</pre>

You should obtain something like that :

<pre class="host">
[ 8893.213869] generic-usb 0003:062A:0000.0005: input,hidraw0: USB HID v1.10 Mouse [HID 062a:0000] on usb-0000:00:1d.0-2/input0
[ 9739.616076] usb 3-2: new low speed USB device using uhci_hcd and address 5
[ 9739.942974] zydacron 0003:13EC:0006.0006: fixing up zydacron remote control report descriptor
[ 9739.978243] input: HID 13ec:0006 as /devices/pci0000:00/0000:00:1d.1/usb3/3-2/3-2:1.0/input/input16
[ 9739.979060] zydacron 0003:13EC:0006.0006: input,hiddev0,hidraw1: USB HID v1.10 Keyboard [HID 13ec:0006] on usb-0000:00:1d.1-2/input0
</pre>

The last line give the model and the identifier of the product : "Zydacron"
If you don't see anything about the model of your HID device, copy/paste the identifier in google. The identifier must be something like that : 13ec:0006
It always be composed of 4 characters, ":", and 4 characters again.

Then, configure your Linux configuration in your armadeus directory
<pre class="host">
$ make linux26-menuconfig
</pre>

<pre class="config">
Device Drivers --->
[*] HID Devices --->
Special HID drivers --->
</pre>

And then, search your driver (Zydacron in our case).
<pre class="config">
<M> Zydacron remote control support
</pre>

Reflash kernel and rootfs.

==Load the driver==

You must know the module name of the driver.
For Zydacron it is "hid_zydacron".

If you don't know the name of your Linux driver:

<pre class="apf">
# ls /lib/modules/$(uname -r)/kernel/drivers/hid/
</pre>

{{Note| $(uname -r) will be replaced with your kernel version. }}

You should see some or one file(s) with the ".ko" extension, like your_hid_driver.ko (hid_zydacron.ko in our case).

then :
<pre class="apf">
#modprobe your_hid_driver
</pre>

in our case:
<pre class="apf">
# modprobe hid_zydacron
</pre>

==Usage==

Plug the usb receiver of your remote on APF board and type
<pre class="apf">
# modprobe dmsg
</pre>

If you read the model name of your device and something like "eventX" where X is the event number, the Linux input is ready.

Check if the event is correctly set in the input directory:
<pre class="apf">
# ls /dev/input/
</pre>

You should read the event of your device.

Check if the communication is set (replace X by your event number, usualy 0 if no hid device other than your remote has been plugged)
<pre class="apf">
# od -x /dev/input/eventX
</pre>
Push a button on your remote. You should see some incomprehensible characters on the screen, don't worry it sounds good!

==Application example==

The USB HID remote device is configured in Linux like a keyboard.

Here a little example of application in langage C :
<source lang="c">
#include <linux/input.h>
#include <sys/types.h>
#include <sys/stat.h>
#include <fcntl.h>
#include <stdio.h>
#include <unistd.h>

/* Replace X by the number of your event */
char input[] = "/dev/input/eventX";

int main(void)
{
int fd;
struct input_event remote_event;
fd = open(input, O_RDONLY); /* Open the event file */

if(fd == -1) {
printf("Can not open the input device!\n");
return 1;
}
else {
while (1) {
read(fd, &remote_event, sizeof(struct input_event)); /* read the last event */
if(remote_event.type == EV_KEY && remote_event.value == 1) { /* Check if a key was pressed */
if(remote_event.code==103) { /* Compare with key up code */
printf("Key up was pressed\n");
}
else if(remote_event.code==108) { /* Compare with key down code */
printf("Key down was pressed\n");
}
/* ... */
else {
printf("Unknown button with code %d was pressed\n", remote_event.code); /* Print code */
}
}
}
}

return 0;
}
</source>

==Links==
Getting started with uinput [http://thiemonge.org/getting-started-with-uinput]
A little example of code in C [http://thiemonge.org/getting-started-with-uinput]

Functionalities

2011-05-11T20:11:10Z

KevinJ: /* IR */

=Functionalities=
This page lists all the hardware/software functionnalities available on the boards.

{| border="0" cellpadding="5" cellspacing="5" summary="Hardware Add-Ons by functionnalities"
|----------------
|- style="background:#f4f4f4; color:black; -moz-border-radius:18px;"
|
==Audio==
===Audio Out===
*[[TSC2102_Linux_driver | Audio codec]]: TSC2102/TSC2101 audio codec
*[[Audio_with_PWM|PWM]]: sound generation using a PWM
*[[MAX9768| Amplifier]]: MAX9768 10W mono class D audio amplifier

===Audio In===
*[[TSC2102_Linux_driver|Audio codec]]: TSC2101 audio codec

===Software===
*[[ALSA]]: Advanced Linux Sound Architecture
*[[Madplay]]: Audio player for Unixes
*[[SDL]]: cross-platform multimedia library
*[[Gstreamer]]
*[[Flite]]: fast run-time voice synthesis engine
*[[Speex]]: speech codec
*[[Imxssi]]: simple low level I2S development/debug tool

||

==Video==
===Video Out===
*[[LCD]]
*[[BackLight]]
*[[DVI_/_HDMI]]
*[[TV_Output]]
*[[FrameBuffer]]

===Video In===
*[[Camera_interface]]:
*[[C38A]]: CMOS sensor module (OV7620)
*[[GscpaWebcam]]: GSPCA compatible USB webcams
*[[PWC_Webcams]]
*[[USB_Webcams]]

===Software===
*[[Video_for_Linux]]: Video 4 Linux
*[[Qt/Embedded]]: cross-platform general purpose API
*[[SDL]]: cross-platform multimedia library
*[[Gstreamer]]
*[[OpenCV]]
*[[FBGrab]]: Frame Buffer Grabber
*[[Mesa]]: Mesa 3D Graphics library
*[[Using_the_i.MX27_video_codec]]
*[[LCD4linux]]: driving low cost text and graphical LCD displays

|----------------
|- style="background:#f4f4f4; color:black; -moz-border-radius:18px;"
|

==Wired Communication==
===UART/RS232===
*[[RS-232]]: global description
*[[Activate_i.MX_internal_UARTs]]
*[[Serial_ports_usage_on_Linux]]
*[[Serial_port_selection_generalities]]: to be merged with previous entry. text ok ??, copied in usb serial
*[[OpenCore_16550_IP_Linux_driver|Linux driver for the 16C550 FPGA IP (from OpenCore)]]
*[[USB_to_serial_adapter]]
*[[USB_Gadget#To_emulate_a_serial_link| USB gadget serial emulation]]
*[[Cu/uucp]] To Be Completed
*[[RS232_Terminal_configuration]]: host applications to take control of your RS232 link
*[[Serial_Transfer|Serial transfers from Linux]]

===I2C===
*[[I2C]]
*[[I2cread.c]]
*[[I2cwrite.c]]

===SPI===
*[[SPI]]: To be completed (spi_dev modif in platform)

===Ethernet / Network===
* manque une page pour décrire l'interface ethernet + commandes de bases sous linux/uboot
*[[Ethernet_MAC_address]]
*[[USB_to_Ethernet_adapter]]
*[[USB_Gadget#To_emulate_an_Ethernet_link|USB gadget ethernet emulation]]
*[[FTP]], [[NFS]], [[SSH]], [[Telnet]], [[Tftpboot]]
*[[Boa]]: BOA web server
*[[Ethernet console]] (in U-Boot)
*[[Network interface bandwidth measurement]]

===USB===
*[[USB]]: create USB_OTG entry and delete this one
*[[USB_Host]]
*[[USB_Gadget]]
*[[USB_to_Ethernet_adapter]]
*[[USB_to_WiFi_adapter]]
*[[USB_to_serial_adapter]]: still under construction ?
*[[USB Boot]] (Linux)
*[[USB Webcams]]
*[[USB to Playstation joypad adapter]]

===CAN Bus===
*[[CAN_bus_Linux_driver|MCP251X CAN bus controller]]
*[[CAN_bus_demo_MCP25020|Communication with a Microchip MCP25020 CAN I/O Expander]]
*[[CAN_bus_Linux_sja1000|SJA1000 CAN Bus controller]]
||

==Wireless==
===Wifi===
*[[WiFi|WiFi general usage (from Linux)]]
*[[USB_to_WiFi_adapter|How to use USB to WiFi adapters on your boards]]
*[[Libertas_driver]]: Marvell Technology Group's Libertas chipset drivers
*[[WPA supplicant]]

===GSM/GPRS===
*[[GSM/GPRS]]

===Bluetooth===
*[[Bluetooth]]
*[[OBEX]]
*[[TCP/IP_with_Bluetooth]]
*[[Wiimote]]

===GPS===
*[[GPS]]
*[[GPS_daemon]]: service daemon monitoring one or more GPSes or AIS receivers

===IR===
*[[IR_HID_USB_Remote|Infrared USB HID remote ]]
|----------------
|- style="background:#f4f4f4; color:black; -moz-border-radius:18px;"
|

==Storage / File System==
*[[MultiMediaCard]]
*[[USB_Host#USB_Flash_memory_.2F_USB_key_.2F_USB_card_reader_.2F_USB_Hard_Drive|USB drive/dongle usage]]
*[[USB_Gadget#To_emulate_a_mass_storage_device:|USB gadget mass storage emulation]]
*[[Create_a_FLASH_partition_to_store_user's_HOME]]
*[[UBIFS]]
*[[Using_Initial_RAM_disk]]: still nder construction ?
*[[Samba]]: access Windows remote partitions
*[[Network_File_System_configuration|Network File System (NFS)]]
||

==Realtime==
===Xenomai===
*[[Xenomai]]: real time co-kernel which cooperate with Linux via Adeos
*[[Xenomai:Blinking_LEDs]]: Xenomai:examples_usage
*[[Xenomai_manual_installation]]
*[[Adeos]]

===RTC===
*[[RTC]]
*[[Watchdog]]

|----------------
|- style="background:#f4f4f4; color:black; -moz-border-radius:18px;"
|

==User Input==
*[[USB_Host#USB_keyboard.2Fmouse_.28HID:_Human_Interface_Device.29| USB input device]]
*[[Keypad]]: keypad based on GPIO matrix
*[[Joystick]]: still under construction ?
*[[PS/2]]: APF9328 only
*[[TSC2102_Linux_driver| Touchscreen]]: TSC210x 4 wires resistive touch controler
*[[GPM]]: mouse support for Linux on the console
*[[Wiimote]]
*[[Tslib]]: Linux touchscreen interface
*[[USB to Playstation joypad adapter]]
||

==Other==
*[[AS1531|AS1531]]: 8 channels 12bits ADC (SPI)
* [[MCP4912|MCP4912]]: 2 channels 10bits DAC (SPI)
*[[ADC_max1027|MAX1027]]: 8 channels 10bits ADC (SPI)
*[[Max5821|MAX5821]]: 2 channels 10bits DAC (I2C)
*[[BQ27x00]]: series of battery gas gauge
*[[GPIO Driver]]
*[[JTAG]]
*[[Led_sensor|Using a LED as a light sensor]]
*[[URG_laser]]
*[[PWM]]
*[[Watchdog]]

|----------------
|- style="background:#f4f4f4; color:black; -moz-border-radius:18px;"
|

==Bootloader==
*[[BootLoader | U-Boot useful tips]]
||

==Bootstrap==
* [[BootStrap | Install U-Boot from scratch or recover your U-Boot if it was corrupted]]