ArmadeusWiki - User contributions [en]

Functionalities

2012-05-02T18:14:51Z

GaelJ: /* Other */

=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]]

===HMS Modules===
*[[HMS_anybus_Linux|HMS Anybus]]
||

==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
*[[GPIO keys]]: User button connected to a GPIO
*[[Joystick]]: still under construction ?
*[[PS/2]]: APF9328 only
*[[TSC2102_Linux_driver| Touchscreen]]: TSC210x 4 wires resistive touch controler
*[[APF51_PMIC|touchscreen]]: APF51 PMIC 4/5 wires resistive touch controler
*[[APF28_PMIC|touchscreen]]: APF28 PMIC 4/5 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]]
*[[GPIO LEDS]]
*[[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]]
* [[USB_Boot|Boot linux from a USB key]]
* [[Connection_with_U-Boot_under_Windows|Connection with U-Boot under Windows]]
* [[U-Boot_communication_quick_check|U-Boot communication quick check]]
* [[Uboot_FPGA_firmware_update_from_Linux|Uboot FPGA firmware update from Linux]]

||

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

GPIO LEDS

2012-05-02T18:13:48Z

GaelJ: /* Introduction */

How to use leds-gpio driver to manage states of connected leds of your Armadeus board.

==Introduction==

You can manage a led connected to a GPIO pin. The managing is similar with the standard GPIO sysfs driver, but you have some new features like triggers (e.g. LED blinks based on disk access) .

==Configuration==

First, you need to enable the leds-gpio driver in your kernel.

<pre class="config">
Device Drivers --->
--- LED support
[*] LED Class Support
<*> LED Support for GPIO connected LEDs
[*] Platform device bindings for GPIO LEDs
</pre>

Then, in your ''apf27-dev.c'', you need to define your LED before the variable ''platform_devices[]''.

<source lang="c">
/* GPIO LED */
#if 1

/* PORTF_14 used as leds-gpio (GPIO used as LED) */
static struct gpio_led apf27_gpio_leds[] = {
{
.name = "portf14",
.default_trigger = "none",
.gpio = (GPIO_PORTF | 14),
//.active_low = 1,
//.retain_state_suspended = 1,
//.default_state = LEDS_GPIO_DEFSTATE_ON,
},
};

static struct gpio_led_platform_data apf27_gpio_leds_platform_data = {
.leds = apf27_gpio_leds,
.num_leds = ARRAY_SIZE(apf27_gpio_leds),
};

static struct platform_device apf27_gpio_leds_device = {
.name = "leds-gpio",
.id = 0,
.dev = {
.platform_data = &apf27_gpio_leds_platform_data,
},
};
# define LEDS_GPIO &apf27_gpio_leds_device,
#else
# define LEDS_GPIO
#endif
</source>

Add the button to get it recognized by the card.

<source lang="c">
static struct platform_device *platform_devices[] __initdata = {
ALSA_SOUND
LEDS_GPIO
};
</source>

<pre class="apf">
# ls /sys/class/leds/portf14/
brightness max_brightness subsystem uevent
device power trigger
</pre>

GPIO LEDS

2012-05-02T18:12:12Z

GaelJ: New page: How to use leds-gpio driver to manage states of connected leds of your Armadeus board. ==Introduction== You can manage a led connected to a GPIO pin. The managing is similar with the sta...

How to use leds-gpio driver to manage states of connected leds of your Armadeus board.

==Introduction==

You can manage a led connected to a GPIO pin. The managing is similar with the standard GPIO sysfs driver, but you have some new features like triggers.

==Configuration==

First, you need to enable the leds-gpio driver in your kernel.

<pre class="config">
Device Drivers --->
--- LED support
[*] LED Class Support
<*> LED Support for GPIO connected LEDs
[*] Platform device bindings for GPIO LEDs
</pre>

Then, in your ''apf27-dev.c'', you need to define your LED before the variable ''platform_devices[]''.

<source lang="c">
/* GPIO LED */
#if 1

/* PORTF_14 used as leds-gpio (GPIO used as LED) */
static struct gpio_led apf27_gpio_leds[] = {
{
.name = "portf14",
.default_trigger = "none",
.gpio = (GPIO_PORTF | 14),
//.active_low = 1,
//.retain_state_suspended = 1,
//.default_state = LEDS_GPIO_DEFSTATE_ON,
},
};

static struct gpio_led_platform_data apf27_gpio_leds_platform_data = {
.leds = apf27_gpio_leds,
.num_leds = ARRAY_SIZE(apf27_gpio_leds),
};

static struct platform_device apf27_gpio_leds_device = {
.name = "leds-gpio",
.id = 0,
.dev = {
.platform_data = &apf27_gpio_leds_platform_data,
},
};
# define LEDS_GPIO &apf27_gpio_leds_device,
#else
# define LEDS_GPIO
#endif
</source>

Add the button to get it recognized by the card.

<source lang="c">
static struct platform_device *platform_devices[] __initdata = {
ALSA_SOUND
LEDS_GPIO
};
</source>

<pre class="apf">
# ls /sys/class/leds/portf14/
brightness max_brightness subsystem uevent
device power trigger
</pre>

GPIO keys

2012-05-02T18:02:16Z

GaelJ: /* Test */

How to use gpio-keys driver to read states of the user switch of your Armadeus board (APF51)

==Introduction==

Your APF51 board features a user switch connected to a GPIO pin (GPIO1_3). The driver gpio-keys translates GPIO events in key/button events.

==Test==
<pre class="apf">
# cat /dev/input/event0
</pre>
Then you should see weirds characters '''when pressing''' the user button of the apf51_dev board:
<pre class="apf">
T
��T
�T
�
��T
%�
</pre>
* if the test wiped out your console, you can get it back with:
<pre class="apf">
# reset
</pre>

You also can use the tool ''evtest''.

<pre class="config">
Hardware handling --->
[*] input-tools
[*] evtest
</pre>

<pre class="apf">
# evtest /dev/input/event0
...
Event: time 1335981358.550329, type 22 (EV_PWR), code 0 (), value 1
Event: time 1335981358.550330, -------------- SYN_REPORT ------------
Event: time 1335981358.550329, type 22 (EV_PWR), code 0 (), value 0
Event: time 1335981358.550330, -------------- SYN_REPORT ------------

</pre>

==For APF27==

First, you need to enable the gpio_keys in your kernel.

<pre class="config">
Device Drivers --->
Input device support --->
<*> Event interface
[*] Keyboards --->
<*> GPIO Buttons
</pre>

Then, in your ''apf27-dev.c'', you need to define your GPIO button before the variable ''platform_devices[]''.

<source lang="c">
/* GPIO KEYS */
#if 1

/* PORTA_6 used as gpio_keys (GPIO used as input event) */
static struct gpio_keys_button apf27_gpio_keys[] = {
{
.code = EV_PWR, /* See include/linux/input.h for more event code */
.gpio = (GPIO_PORTA | 6), /* GPIO number */
.active_low = 0,
.desc = "Notification when the AC is deconnected", /* Button description*/
.type = 0, /* See include/linux/input.h for more type code */
},
};

static struct gpio_keys_platform_data apf27_gpio_keys_data = {
.buttons = apf27_gpio_keys,
.nbuttons = ARRAY_SIZE(apf27_gpio_keys),
};

static struct platform_device apf27_gpio_keys_device = {
.name = "gpio-keys",
.id = 0,
.dev = {
.platform_data = &apf27_gpio_keys_data,
},
};
# define GPIO_KEYS &apf27_gpio_keys_device,
#else
# define GPIO_KEYS
#endif
</source>

Add the button to get it recognized by the card.

<source lang="c">
static struct platform_device *platform_devices[] __initdata = {
ALSA_SOUND
GPIO_KEYS
};
</source>

[[Category:UserInput]]

GPIO keys

2012-05-02T17:45:49Z

GaelJ: /* Test */

How to use gpio-keys driver to read states of the user switch of your Armadeus board (APF51)

==Introduction==

Your APF51 board features a user switch connected to a GPIO pin (GPIO1_3). The driver gpio-keys translates GPIO events in key/button events.

==Test==
<pre class="apf">
# cat /dev/input/event0
</pre>
Then you should see weirds characters '''when pressing''' the user button of the apf51_dev board:
<pre class="apf">
T
��T
�T
�
��T
%�
</pre>
* if the test wiped out your console, you can get it back with:
<pre class="apf">
# reset
</pre>
==For APF27==

First, you need to enable the gpio_keys in your kernel.

<pre class="config">
Device Drivers --->
Input device support --->
<*> Event interface
[*] Keyboards --->
<*> GPIO Buttons
</pre>

Then, in your ''apf27-dev.c'', you need to define your GPIO button before the variable ''platform_devices[]''.

<source lang="c">
/* GPIO KEYS */
#if 1

/* PORTA_6 used as gpio_keys (GPIO used as input event) */
static struct gpio_keys_button apf27_gpio_keys[] = {
{
.code = EV_PWR, /* See include/linux/input.h for more event code */
.gpio = (GPIO_PORTA | 6), /* GPIO number */
.active_low = 0,
.desc = "Notification when the AC is deconnected", /* Button description*/
.type = 0, /* See include/linux/input.h for more type code */
},
};

static struct gpio_keys_platform_data apf27_gpio_keys_data = {
.buttons = apf27_gpio_keys,
.nbuttons = ARRAY_SIZE(apf27_gpio_keys),
};

static struct platform_device apf27_gpio_keys_device = {
.name = "gpio-keys",
.id = 0,
.dev = {
.platform_data = &apf27_gpio_keys_data,
},
};
# define GPIO_KEYS &apf27_gpio_keys_device,
#else
# define GPIO_KEYS
#endif
</source>

Add the button to get it recognized by the card.

<source lang="c">
static struct platform_device *platform_devices[] __initdata = {
ALSA_SOUND
GPIO_KEYS
};
</source>

[[Category:UserInput]]