ArmadeusWiki - User contributions [en]

OneWire GPIO bus Master

2013-05-19T13:56:12Z

JanosA:

Informations and HOWTOs for ArmadeuS OneWire support.

Author: JanosA

== Supported Board and Software versions ==
* Use the latest Armadeus GIT/SF repository (the latest stable release Armadeus 5.2 don't have this patches)
* Currently only the APF28DEV board supported, but it's easy to add support to another boards. (Check linux-2.6.35.3/arch/arm/mach-mx28/apf28dev.c file)

== Software installation ==
* Recompile your Linux kernel with OneWire GPIO bus master (and some slave device) support.
<pre class="host">
$ make linux-menuconfig
</pre>
<pre class="config">
Device Drivers --->
<*> Dallas's 1-wire support --->
1-wire Bus Masters --->
<*> GPIO 1-wire busmaster
1-wire Slaves --->
<*> Thermal family implementation
</pre>
<pre class="host">
$ make
</pre>
* Reflash your Linux kernel

== Hardware Notes ==
* Connect the OneWire slave directly to the APF28_DEV board J9 connector:
* Vcc 3.3V is pin 1 on J9 connector
* DQ is pin 31 on J9 (LCD_D18 / GPIO 1_18)
* GND is pin 39 on J9
* Add an 1.2k pullup resistor between Vcc and DQ

== How it works ==
The OneWire bus master driver every 10 seconds scan the bus for new slave devices.

Each detected OneWire slave device have a sub-directory with it's unique ID in "/sys/devices/w1 bus master".

The sub-directory format is <2 digit family ID>-<12 digit unique ID>.
<pre class=apf>
# ls -la /sys/devices/w1\ bus\ master/
total 0
drwxr-xr-x 4 root root 0 Jan 1 01:06 .
drwxr-xr-x 6 root root 0 Jan 1 01:05 ..
drwxr-xr-x 3 root root 0 Jan 1 01:06 28-000001e68904
lrwxrwxrwx 1 root root 0 Jan 1 01:07 driver -> ../../bus/w1/drivers/w1_master_driver
drwxr-xr-x 2 root root 0 Jan 1 01:07 power
lrwxrwxrwx 1 root root 0 Jan 1 01:07 subsystem -> ../../bus/w1
-rw-r--r-- 1 root root 4096 Jan 1 01:07 uevent
-rw-rw-rw- 1 root root 4096 Jan 1 01:07 w1_master_add
-r--r--r-- 1 root root 4096 Jan 1 01:07 w1_master_attempts
-r--r--r-- 1 root root 4096 Jan 1 01:07 w1_master_max_slave_count
-r--r--r-- 1 root root 4096 Jan 1 01:07 w1_master_name
-r--r--r-- 1 root root 4096 Jan 1 01:07 w1_master_pointer
-rw-rw-rw- 1 root root 4096 Jan 1 01:07 w1_master_pullup
-rw-rw-rw- 1 root root 4096 Jan 1 01:07 w1_master_remove
-rw-rw-rw- 1 root root 4096 Jan 1 01:07 w1_master_search
-r--r--r-- 1 root root 4096 Jan 1 01:07 w1_master_slave_count
-r--r--r-- 1 root root 4096 Jan 1 01:07 w1_master_slaves
-r--r--r-- 1 root root 4096 Jan 1 01:07 w1_master_timeout
</pre>
You can list the detected slaves from this files:
<pre class=apf>
# cat /sys/devices/w1\ bus\ master/w1_master_slave_count
1
# cat /sys/devices/w1\ bus\ master/w1_master_slaves
28-000001e68904
</pre>
Let's read the temperature: (The 28-xxx family is a DS18B20 temperature sensor in this example.)
<pre class=apf>
# cat /sys/devices/w1\ bus\ master/28-000001e68904/w1_slave
dd 01 4b 46 7f ff 03 10 1e : crc=1e YES
dd 01 4b 46 7f ff 03 10 1e t=29812
</pre>
The t=29812 means, the temperature is: 29.812°C

OneWire GPIO bus Master

2013-05-19T13:47:37Z

JanosA:

Informations and HOWTOs for ArmadeuS OneWire support.

Author: JanosA

== Supported Board and Software versions ==
* Use the latest Armadeus GIT/SF repository (the latest stable release Armadeus 5.2 don't have this patches)
* Currently only the APF28DEV board supported, but it's easy to add support to another boards.

== Software installation ==
* Recompile your Linux kernel with OneWire GPIO bus master (and some slave device) support.
<pre class="host">
$ make linux-menuconfig
</pre>
<pre class="config">
Device Drivers --->
<*> Dallas's 1-wire support --->
1-wire Bus Masters --->
<*> GPIO 1-wire busmaster
1-wire Slaves --->
<*> Thermal family implementation
</pre>
<pre class="host">
$ make
</pre>
* Reflash your Linux kernel

== Hardware Notes ==
* Connect the OneWire slave directly to the APF28_DEV board J9 connector:
* Vcc 3.3V is pin 1 on J9 connector
* DQ is pin 31 on J9 (LCD_D18 / GPIO 1_18)
* GND is pin 39 on J9
* Add an 1.2k pullup resistor between Vcc and DQ

== How it works ==
The OneWire bus master driver every 10 seconds scan the bus for new slave devices.

Each detected OneWire slave device have a sub-directory with it's unique ID in "/sys/devices/w1 bus master".

The sub-directory format is <2 digit family ID>-<12 digit unique ID>.
<pre class=apf>
# ls -la /sys/devices/w1\ bus\ master/
total 0
drwxr-xr-x 4 root root 0 Jan 1 01:06 .
drwxr-xr-x 6 root root 0 Jan 1 01:05 ..
drwxr-xr-x 3 root root 0 Jan 1 01:06 28-000001e68904
lrwxrwxrwx 1 root root 0 Jan 1 01:07 driver -> ../../bus/w1/drivers/w1_master_driver
drwxr-xr-x 2 root root 0 Jan 1 01:07 power
lrwxrwxrwx 1 root root 0 Jan 1 01:07 subsystem -> ../../bus/w1
-rw-r--r-- 1 root root 4096 Jan 1 01:07 uevent
-rw-rw-rw- 1 root root 4096 Jan 1 01:07 w1_master_add
-r--r--r-- 1 root root 4096 Jan 1 01:07 w1_master_attempts
-r--r--r-- 1 root root 4096 Jan 1 01:07 w1_master_max_slave_count
-r--r--r-- 1 root root 4096 Jan 1 01:07 w1_master_name
-r--r--r-- 1 root root 4096 Jan 1 01:07 w1_master_pointer
-rw-rw-rw- 1 root root 4096 Jan 1 01:07 w1_master_pullup
-rw-rw-rw- 1 root root 4096 Jan 1 01:07 w1_master_remove
-rw-rw-rw- 1 root root 4096 Jan 1 01:07 w1_master_search
-r--r--r-- 1 root root 4096 Jan 1 01:07 w1_master_slave_count
-r--r--r-- 1 root root 4096 Jan 1 01:07 w1_master_slaves
-r--r--r-- 1 root root 4096 Jan 1 01:07 w1_master_timeout
</pre>
You can list the detected slaves from this files:
<pre class=apf>
# cat /sys/devices/w1\ bus\ master/w1_master_slave_count
1
# cat /sys/devices/w1\ bus\ master/w1_master_slaves
28-000001e68904
</pre>
Let's read the temperature: (The 28-xxx family is a DS18B20 temperature sensor in this example.)
<pre class=apf>
# cat /sys/devices/w1\ bus\ master/28-000001e68904/w1_slave
dd 01 4b 46 7f ff 03 10 1e : crc=1e YES
dd 01 4b 46 7f ff 03 10 1e t=29812
</pre>
The t=29812 means, the temperature is: 29.812°C

Functionalities

2013-05-19T13:42:35Z

JanosA: /* RS-485 */

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

===RS-485===
*[[RS-485]]: How to use the i.MX internal UART in RS-485 mode

===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_OTG]]
*[[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]]

===OneWire===
*[[OneWire GPIO bus Master]]

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

==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]]
*[[Power_management]]

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

User:JanosA

2013-05-19T13:39:25Z

JanosA: OneWire moved to main Wiki Tree

Functionalities

2013-05-19T13:35:36Z

JanosA: /* OneWire */

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

===RS-485===
*[[RS-485]]: How to use the RS-485 interface. Thanks JanosA

===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_OTG]]
*[[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]]

===OneWire===
*[[OneWire GPIO bus Master]]

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

==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]]
*[[Power_management]]

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

RS-485

2013-05-19T12:08:31Z

JanosA:

Informations and HOWTOs for ArmadeuS RS-485 support.

RS-485 mostly used in half duplex operation mode, and uses a differential balanced line over twisted pair. RS-485 drivers need to be put in transmit mode explicitly by asserting a signal to the driver. This allows RS-485 to implement linear topologies using only two wires, and it can span relatively large distances (up to 1,200m @ 100kbit/s).

Before the RS-485 related parts, please have a look on: [[Serial ports usage on Linux]]

Author: JanosA

== Supported Board and Software versions ==
* Use the latest Armadeus GIT/SF repository (the latest stable release Armadeus 5.2 don't have this patches)
* Currently only the APF28 (iMX28) board with Linux kernel v2.6.35.3 supported. (mxs-auart patch)
* Linux stty patch included in buildroot 2012.02 to only busybox v1.19.4
* Linux stty patch included in buildroot 2013.02 to all busybox versions starting from v1.19.4

== Changing port parameters ==
* Setup APF28 serial port for RS-485 communication:
<pre class=apf>
# stty -F /dev/ttySP0 9600
# stty -F /dev/ttySP0 raw
# stty -F /dev/ttySP0 -echo -echoe -echok
# stty -F /dev/ttySP0 rs485
</pre>

* Set extra delays (if needed) for TXEN/RTS signaling before and after the transmitted packet (in microseconds):
<pre class=apf>
# stty -F /dev/ttySP0 rs485delaybefore 100
# stty -F /dev/ttySP0 rs485delayafter 100
</pre>

* To get current RS-485 parameters. (If the port device supports the RS-485 options you will see the last two lines)
<pre class=apf>
# stty -F /dev/ttySP0
speed 9600 baud; line = 0;
intr = ^C; quit = ^\; erase = ^?; kill = ^U; eof = ^D; eol = <undef>;
eol2 = <undef>; swtch = <undef>; start = ^Q; stop = ^S; susp = ^Z; rprnt = ^R;
werase = ^W; lnext = ^V; flush = ^O; min = 1; time = 0;
-brkint -imaxbel
rs485 -rs485rtsonsend -rs485rtsaftersend -rs485rxduringtx
rs485delaybefore = 100; rs485delayafter = 100; rs485delaylastchartx = 1250;
</pre>
Please note:
* You can't set the "rs485delaylastchartx" parameter, it's calculated automatically from the baudrate.
Special notes for the APF28/iMX28 mxs-auart driver:
* All delays are in microseconds.
* The "rs485delaylastchartx" parameter is not used in DMA mode.
* The parameters: "rs485rtsonsend" "rs485rtsaftersend" "rs485rxduringtx" are not used. (Only used by atmel_serial.c and crisv10.c drivers)
* If the RS-485 mode is turned on, it will override (turn off) the RTS/CTS hardware flow settings of the uart, don't care what is configured.

== How to use it from C code ==
* The RS-485 mode can be turned on with ioctl calls from C code, here is the example:
<source lang="C">
#include <stdio.h>
#include <fcntl.h>
#include <linux/ioctl.h>
#include <linux/serial.h>
#include <asm-generic/ioctls.h> /* TIOCGRS485 + TIOCSRS485 ioctl definitions */

int main(void) {
struct serial_rs485 rs485conf;

int fd = open ("/dev/ttySP0", O_RDWR);
if (fd < 0) {
printf("Error: Can't open: /dev/ttySP0\n");
}

/* Don't forget to read first the current state of the RS-485 options with ioctl.
If You don't do this, You will destroy the rs485conf.delay_rts_last_char_tx
parameter which is automatically calculated by the driver when You opens the
port device. */
if (ioctl (fd, TIOCGRS485, &rs485conf) < 0) {
printf("Error: TIOCGRS485 ioctl not supported.\n");
}

/* Enable RS-485 mode: */
rs485conf.flags |= SER_RS485_ENABLED;

/* Set rts/txen delay before send, if needed: (in microseconds) */
rs485conf.delay_rts_before_send = 0;

/* Set rts/txen delay after send, if needed: (in microseconds) */
rs485conf.delay_rts_after_send = 0;

if (ioctl (fd, TIOCSRS485, &rs485conf) < 0) {
printf("Error: TIOCSRS485 ioctl not supported.\n");
}

fcntl(fd, F_SETFL, 0);
int n = write(fd, "ABC\r\n", 5);
if (n < 0) {
/* Error handling */
}

if (close (fd) < 0) {
printf("Error: Can't close: /dev/ttySP0\n");
}
}
</source>

== Hardware Notes ==
* The RS-485 Transmit Enable (TXEN) output will be the RTS pin of the uart.
* The TXEN/RTS output is _active low_, it must be inverted to use it with the popular RS-485 transceiver ICs.
* When the u-boot runs and the board start to boot, the RTS pin works as input, please add a pullup resistor to this pin before the inverter, to prevent RS-485 bus lockups.

RS-485

2013-05-19T11:48:46Z

JanosA:

Informations and HOWTOs for ArmadeuS RS-485 support.

Before the RS-485 related parts, please have a look on: [[Serial ports usage on Linux]]

Author: JanosA

== Supported Board and Software versions ==
* Use the latest Armadeus GIT/SF repository (the latest stable release Armadeus 5.2 don't have this patches)
* Currently only the APF28 (iMX28) board with Linux kernel v2.6.35.3 supported. (mxs-auart patch)
* Linux stty patch included in buildroot 2012.02 to only busybox v1.19.4
* Linux stty patch included in buildroot 2013.02 to all busybox versions starting from v1.19.4

== Changing port parameters ==
* Setup APF28 serial port for RS-485 communication:
<pre class=apf>
# stty -F /dev/ttySP0 9600
# stty -F /dev/ttySP0 raw
# stty -F /dev/ttySP0 -echo -echoe -echok
# stty -F /dev/ttySP0 rs485
</pre>

* Set extra delays (if needed) for TXEN/RTS signaling before and after the transmitted packet (in microseconds):
<pre class=apf>
# stty -F /dev/ttySP0 rs485delaybefore 100
# stty -F /dev/ttySP0 rs485delayafter 100
</pre>

* To get current RS-485 parameters. (If the port device supports the RS-485 options you will see the last two lines)
<pre class=apf>
# stty -F /dev/ttySP0
speed 9600 baud; line = 0;
intr = ^C; quit = ^\; erase = ^?; kill = ^U; eof = ^D; eol = <undef>;
eol2 = <undef>; swtch = <undef>; start = ^Q; stop = ^S; susp = ^Z; rprnt = ^R;
werase = ^W; lnext = ^V; flush = ^O; min = 1; time = 0;
-brkint -imaxbel
rs485 -rs485rtsonsend -rs485rtsaftersend -rs485rxduringtx
rs485delaybefore = 100; rs485delayafter = 100; rs485delaylastchartx = 1250;
</pre>
Please note:
* You can't set the "rs485delaylastchartx" parameter, it's calculated automatically from the baudrate.
Special notes for the APF28/iMX28 mxs-auart driver:
* All delays are in microseconds.
* The "rs485delaylastchartx" parameter is not used in DMA mode.
* The parameters: "rs485rtsonsend" "rs485rtsaftersend" "rs485rxduringtx" are not used. (Only used by atmel_serial.c and crisv10.c drivers)
* If the RS-485 mode is turned on, it will override (turn off) the RTS/CTS hardware flow settings of the uart, don't care what is configured.

== How to use it from C code ==
* The RS-485 mode can be turned on with ioctl calls from C code, here is the example:
<source lang="C">
#include <stdio.h>
#include <fcntl.h>
#include <linux/ioctl.h>
#include <linux/serial.h>
#include <asm-generic/ioctls.h> /* TIOCGRS485 + TIOCSRS485 ioctl definitions */

int main(void) {
struct serial_rs485 rs485conf;

int fd = open ("/dev/ttySP0", O_RDWR);
if (fd < 0) {
printf("Error: Can't open: /dev/ttySP0\n");
}

/* Don't forget to read first the current state of the RS-485 options with ioctl.
If You don't do this, You will destroy the rs485conf.delay_rts_last_char_tx
parameter which is automatically calculated by the driver when You opens the
port device. */
if (ioctl (fd, TIOCGRS485, &rs485conf) < 0) {
printf("Error: TIOCGRS485 ioctl not supported.\n");
}

/* Enable RS-485 mode: */
rs485conf.flags |= SER_RS485_ENABLED;

/* Set rts/txen delay before send, if needed: (in microseconds) */
rs485conf.delay_rts_before_send = 0;

/* Set rts/txen delay after send, if needed: (in microseconds) */
rs485conf.delay_rts_after_send = 0;

if (ioctl (fd, TIOCSRS485, &rs485conf) < 0) {
printf("Error: TIOCSRS485 ioctl not supported.\n");
}

fcntl(fd, F_SETFL, 0);
int n = write(fd, "ABC\r\n", 5);
if (n < 0) {
/* Error handling */
}

if (close (fd) < 0) {
printf("Error: Can't close: /dev/ttySP0\n");
}
}
</source>

== Hardware Notes ==
* The RS-485 Transmit Enable (TXEN) output will be the RTS pin of the uart.
* The TXEN/RTS output is _active low_, it must be inverted to use it with the popular RS-485 transceiver ICs.
* When the u-boot runs and the board start to boot, the RTS pin works as input, please add a pullup resistor to this pin before the inverter, to prevent RS-485 bus lockups.

RS-485

2013-05-15T19:07:30Z

JanosA: Add supported platforms

Informations and HOWTOs for ArmadeuS RS-485 support.

Author: JanosA

== Supported Board and Software versions ==
* Currently only the APF28 (iMX28) board with Linux kernel v2.6.35.3 supported. (mxs-auart patch)
* Linux stty patch included only in busybox v1.19.4 (Patch already submitted to the busybox mailing list)

== Linux stty ==
* Setup APF28 serial port for RS-485 communication:
<pre class=apf>
# stty -F /dev/ttySP0 raw
# stty -F /dev/ttySP0 -echo -echoe -echok
# stty -F /dev/ttySP0 rs485
</pre>

* Set extra delays (if needed) for TXEN/RTS signaling before and after the transmitted packet (in microseconds):
<pre class=apf>
# stty -F /dev/ttySP0 rs485delaybefore 100
# stty -F /dev/ttySP0 rs485delayafter 100
</pre>

* To get current RS-485 parameters. (If the port device supports the RS-485 options you will see the last two lines)
<pre class=apf>
# stty -F /dev/ttySP0
speed 9600 baud; line = 0;
intr = ^C; quit = ^\; erase = ^?; kill = ^U; eof = ^D; eol = <undef>;
eol2 = <undef>; swtch = <undef>; start = ^Q; stop = ^S; susp = ^Z; rprnt = ^R;
werase = ^W; lnext = ^V; flush = ^O; min = 1; time = 0;
-brkint -imaxbel
rs485 -rs485rtsonsend -rs485rtsaftersend -rs485rxduringtx
rs485delaybefore = 100; rs485delayafter = 100; rs485delaylastchartx = 1250;
</pre>
Please note:
* You can't set the "rs485delaylastchartx" parameter, it's calculated automatically from the baudrate.
Special notes for the APF28/iMX28 mxs-auart driver:
* All delays are in microseconds.
* The "rs485delaylastchartx" parameter is not used in DMA mode.
* The parameters: "rs485rtsonsend" "rs485rtsaftersend" "rs485rxduringtx" are not used. (Only used by atmel_serial.c and crisv10.c drivers)
* If the RS-485 mode is turned on, it will override (turn off) the RTS/CTS hardware flow settings of the uart, don't care what is configured.

== C code ==
* The RS-485 mode can be turned on with ioctl calls from C code, here is the example:
<source lang="C">
#include <stdio.h>
#include <fcntl.h>
#include <linux/ioctl.h>
#include <linux/serial.h>
#include <asm-generic/ioctls.h> /* TIOCGRS485 + TIOCSRS485 ioctl definitions */

int main(void) {
struct serial_rs485 rs485conf;

int fd = open ("/dev/ttySP0", O_RDWR);
if (fd < 0) {
printf("Error: Can't open: /dev/ttySP0\n");
}

/* Don't forget to read first the current state of the RS-485 options with ioctl.
If You don't do this, You will destroy the rs485conf.delay_rts_last_char_tx
parameter which is automatically calculated by the driver when You opens the
port device. */
if (ioctl (fd, TIOCGRS485, &rs485conf) < 0) {
printf("Error: TIOCGRS485 ioctl not supported.\n");
}

/* Enable RS-485 mode: */
rs485conf.flags |= SER_RS485_ENABLED;

/* Set rts/txen delay before send, if needed: (in microseconds) */
rs485conf.delay_rts_before_send = 0;

/* Set rts/txen delay after send, if needed: (in microseconds) */
rs485conf.delay_rts_after_send = 0;

if (ioctl (fd, TIOCSRS485, &rs485conf) < 0) {
printf("Error: TIOCSRS485 ioctl not supported.\n");
}

fcntl(fd, F_SETFL, 0);
int n = write(fd, "ABC\r\n", 5);
if (n < 0) {
/* Error handling */
}

if (close (fd) < 0) {
printf("Error: Can't close: /dev/ttySP0\n");
}
}
</source>

== Hardware Notes ==
* The RS-485 Transmit Enable (TXEN) output will be the RTS pin of the uart.
* The TXEN/RTS output is _active low_, it must be inverted to use it with the popular RS-485 transceiver ICs.
* When the u-boot runs and the board start to boot, the RTS pin works as input, please add a pullup resistor to this pin before the inverter, to prevent RS-485 bus lockups.

User:JanosA

2013-05-15T18:53:41Z

JanosA: RS-485 moved to main Wiki Tree

User:JanosA

2013-05-09T22:00:04Z

JanosA:

== About Me ==
I am IP Network and Datacenter engineer, currently I'm working for an Internet Service Provider in Hungary.

My hobby is programming embedded systems and creating my own small electronic boards.

=== Skills ===
* Assembly programming: PIC 8bit family
* C programming: PIC 8bit / PIC32MX family, Linux
* Perl, PHP, Javascript, Html programming with MySQL
* Linux system administration
* RS-232/485 serial communications: Ascii, Modbus, Saia Sbus, etc.
* IP networking

=== My ArmadeuS plans (APF28 based) ===
* Creating an universal home automation hardware for my friends, with easy programming in perl or PHP. :)
* Datacenter temperature monitoring, with RS-485 and OneWire communications.
* Data logger for Saia Sbus based intelligent power meters.

== RS485 ==
Informations and mini HOWTOs for my APF28/iMX28 mxs-auart and busybox stty patches.

=== Linux stty ===
* Setup APF28 serial port for RS485 communication:
<pre class=apf>
# stty -F /dev/ttySP0 raw
# stty -F /dev/ttySP0 -echo -echoe -echok
# stty -F /dev/ttySP0 rs485
</pre>

* Set extra delays for TXEN/RTS signaling before and after the transmitted packet (in microseconds):
<pre class=apf>
# stty -F /dev/ttySP0 rs485delaybefore 100
# stty -F /dev/ttySP0 rs485delayafter 100
</pre>

* To get current RS485 parameters. (If the port device supports the RS485 options you will see the last two lines)
<pre class=apf>
# stty -F /dev/ttySP0
speed 9600 baud; line = 0;
intr = ^C; quit = ^\; erase = ^?; kill = ^U; eof = ^D; eol = <undef>;
eol2 = <undef>; swtch = <undef>; start = ^Q; stop = ^S; susp = ^Z; rprnt = ^R;
werase = ^W; lnext = ^V; flush = ^O; min = 1; time = 0;
-brkint -imaxbel
rs485 -rs485rtsonsend -rs485rtsaftersend -rs485rxduringtx
rs485delaybefore = 100; rs485delayafter = 100; rs485delaylastchartx = 1250;
</pre>
Please note:
* You can't set the "rs485delaylastchartx" parameter, it's calculated automatically from the baudrate.
Special notes for the APF28/iMX28 mxs-auart driver:
* All delays are in microseconds.
* The "rs485delaylastchartx" parameter is not used in DMA mode.
* The parameters: "rs485rtsonsend" "rs485rtsaftersend" "rs485rxduringtx" are not used. (Only used by atmel_serial.c and crisv10.c drivers)
* If the RS485 mode is turned on, it will override (turn off) the RTS/CTS hardware flow settings of the uart, don't care what is configured.

=== C code ===
* The RS485 mode can be turned on with ioctl calls from C code, here is the example:
<source lang="C">
#include <stdio.h>
#include <fcntl.h>
#include <linux/ioctl.h>
#include <linux/serial.h>
#include <asm-generic/ioctls.h> /* TIOCGRS485 + TIOCSRS485 ioctl definitions */

int main(void) {
struct serial_rs485 rs485conf;

int fd = open ("/dev/ttySP0", O_RDWR);
if (fd < 0) {
printf("Error: Can't open: /dev/ttySP0\n");
}

/* Don't forget to read first the current state of the RS485 options with ioctl.
If You don't do this, You will destroy the rs485conf.delay_rts_last_char_tx
parameter which is automatically calculated by the driver when You opens the
port device. */
if (ioctl (fd, TIOCGRS485, &rs485conf) < 0) {
printf("Error: TIOCGRS485 ioctl not supported.\n");
}

/* Enable RS485 mode: */
rs485conf.flags |= SER_RS485_ENABLED;

/* Set rts/txen delay before send, if needed: (in microseconds) */
rs485conf.delay_rts_before_send = 0;

/* Set rts/txen delay after send, if needed: (in microseconds) */
rs485conf.delay_rts_after_send = 0;

if (ioctl (fd, TIOCSRS485, &rs485conf) < 0) {
printf("Error: TIOCSRS485 ioctl not supported.\n");
}

fcntl(fd, F_SETFL, 0);
int n = write(fd, "ABC\r\n", 5);
if (n < 0) {
/* Error handling */
}

if (close (fd) < 0) {
printf("Error: Can't close: /dev/ttySP0\n");
}
}
</source>

=== Hardware Notes ===
* The RS485 Transmit Enable (TXEN) output will be the RTS pin of the uart.
* The TXEN/RTS output is _active low_, it must be inverted to use it with the popular RS485 transceiver ICs.
* When the u-boot runs and the board start to boot, the RTS pin works as input, please add a pullup resistor to this pin before the inverter, to prevent RS485 bus lockups.

== OneWire ==
Informations and mini HOWTOs for my APF28DEV OneWire patch.

=== Software installation ===
* Recompile your Linux kernel with OneWire GPIO bus master (and some slave device) support.
<pre class="host">
$ make linux-menuconfig
</pre>
<pre class="config">
Device Drivers --->
<*> Dallas's 1-wire support --->
1-wire Bus Masters --->
<*> GPIO 1-wire busmaster
1-wire Slaves --->
<*> Thermal family implementation
</pre>
<pre class="host">
$ make
</pre>
* Reflash your Linux kernel

=== Hardware Notes ===
* Connect the OneWire slave directly to the APF28_DEV board J9 connector:
* Vcc 3.3V is pin 1 on J9 connector
* DQ is pin 31 on J9 (LCD_D18 / GPIO 1_18)
* GND is pin 39 on J9
* Add an 1.2k pullup resistor between Vcc and DQ

=== How it works ===
The OneWire bus master driver every 10 seconds scan the bus for new slave devices.

Each detected OneWire slave device have a sub-directory with it's unique ID in "/sys/devices/w1 bus master".

The sub-directory format is <2 digit family ID>-<12 digit unique ID>.
<pre class=apf>
# ls -la /sys/devices/w1\ bus\ master/
total 0
drwxr-xr-x 4 root root 0 Jan 1 01:06 .
drwxr-xr-x 6 root root 0 Jan 1 01:05 ..
drwxr-xr-x 3 root root 0 Jan 1 01:06 28-000001e68904
lrwxrwxrwx 1 root root 0 Jan 1 01:07 driver -> ../../bus/w1/drivers/w1_master_driver
drwxr-xr-x 2 root root 0 Jan 1 01:07 power
lrwxrwxrwx 1 root root 0 Jan 1 01:07 subsystem -> ../../bus/w1
-rw-r--r-- 1 root root 4096 Jan 1 01:07 uevent
-rw-rw-rw- 1 root root 4096 Jan 1 01:07 w1_master_add
-r--r--r-- 1 root root 4096 Jan 1 01:07 w1_master_attempts
-r--r--r-- 1 root root 4096 Jan 1 01:07 w1_master_max_slave_count
-r--r--r-- 1 root root 4096 Jan 1 01:07 w1_master_name
-r--r--r-- 1 root root 4096 Jan 1 01:07 w1_master_pointer
-rw-rw-rw- 1 root root 4096 Jan 1 01:07 w1_master_pullup
-rw-rw-rw- 1 root root 4096 Jan 1 01:07 w1_master_remove
-rw-rw-rw- 1 root root 4096 Jan 1 01:07 w1_master_search
-r--r--r-- 1 root root 4096 Jan 1 01:07 w1_master_slave_count
-r--r--r-- 1 root root 4096 Jan 1 01:07 w1_master_slaves
-r--r--r-- 1 root root 4096 Jan 1 01:07 w1_master_timeout
</pre>
You can list the detected slaves from this files:
<pre class=apf>
# cat /sys/devices/w1\ bus\ master/w1_master_slave_count
1
# cat /sys/devices/w1\ bus\ master/w1_master_slaves
28-000001e68904
</pre>
Let's read the temperature: (The 28-xxx family is a DS18B20 temperature sensor in this example.)
<pre class=apf>
# cat /sys/devices/w1\ bus\ master/28-000001e68904/w1_slave
dd 01 4b 46 7f ff 03 10 1e : crc=1e YES
dd 01 4b 46 7f ff 03 10 1e t=29812
</pre>
The t=29812 means, the temperature is: 29.812°C

User:JanosA

2013-05-09T20:23:19Z

JanosA:

== About Me ==
I am IP Network and Datacenter engineer, currently I'm working for an Internet Service Provider in Hungary.

My hobby is programming embedded systems and creating my own small electronic boards.

=== Skills ===
* Assembly programming: PIC 8bit family
* C programming: PIC 8bit / PIC32MX family, Linux
* Perl, PHP, Javascript, Html programming with MySQL
* Linux system administration
* RS-232/485 serial communications: Ascii, Modbus, Saia Sbus, etc.
* IP networking

=== My ArmadeuS plans (APF28 based) ===
* Creating an universal home automation hardware for my friends, with easy programming in perl or PHP. :)
* Datacenter temperature monitoring, with RS-485 and OneWire communications.
* Data logger for Saia Sbus based intelligent power meters.

== RS485 ==
Informations and mini HOWTOs for my APF28/iMX28 mxs-auart and busybox stty patches.

=== Linux stty ===
* Setup APF28 serial port for RS485 communication:
<pre class=apf>
# stty -F /dev/ttySP0 raw
# stty -F /dev/ttySP0 -echo -echoe -echok
# stty -F /dev/ttySP0 rs485
</pre>

* Set extra delays for TXEN/RTS signaling before and after the transmitted packet (in microseconds):
<pre class=apf>
# stty -F /dev/ttySP0 rs485delaybefore 100
# stty -F /dev/ttySP0 rs485delayafter 100
</pre>

* To get current RS485 parameters. (If the port device supports the RS485 options you will see the last two lines)
<pre class=apf>
# stty -F /dev/ttySP0
speed 9600 baud; line = 0;
intr = ^C; quit = ^\; erase = ^?; kill = ^U; eof = ^D; eol = <undef>;
eol2 = <undef>; swtch = <undef>; start = ^Q; stop = ^S; susp = ^Z; rprnt = ^R;
werase = ^W; lnext = ^V; flush = ^O; min = 1; time = 0;
-brkint -imaxbel
rs485 -rs485rtsonsend -rs485rtsaftersend -rs485rxduringtx
rs485delaybefore = 100; rs485delayafter = 100; rs485delaylastchartx = 1250;
</pre>
Please note:
* You can't set the "rs485delaylastchartx" parameter, it's calculated automatically from the baudrate.
Special notes for the APF28/iMX28 mxs-auart driver:
* All delays are in microseconds.
* The "rs485delaylastchartx" parameter is not used in DMA mode.
* The parameters: "rs485rtsonsend" "rs485rtsaftersend" "rs485rxduringtx" are not used. (Only used by atmel_serial.c and crisv10.c drivers)
* If the RS485 mode is turned on, it will override (turn off) the RTS/CTS hardware flow settings of the uart, don't care what is configured.

=== C code ===
* The RS485 mode can be turned on with ioctl calls from C code, here is the example:
<source lang="C">
#include <stdio.h>
#include <fcntl.h>
#include <linux/ioctl.h>
#include <linux/serial.h>
#include <asm-generic/ioctls.h> /* TIOCGRS485 + TIOCSRS485 ioctl definitions */

int main(void) {
struct serial_rs485 rs485conf;

int fd = open ("/dev/ttySP0", O_RDWR);
if (fd < 0) {
printf("Error: Can't open: /dev/ttySP0\n");
}

/* Don't forget to read first the current state of the RS485 options with ioctl.
If You don't do this, You will destroy the rs485conf.delay_rts_last_char_tx
parameter which is automatically calculated by the driver when You opens the
port device. */
if (ioctl (fd, TIOCGRS485, &rs485conf) < 0) {
printf("Error: TIOCGRS485 ioctl not supported.\n");
}

/* Enable RS485 mode: */
rs485conf.flags |= SER_RS485_ENABLED;

/* Set rts/txen delay before send, if needed: (in microseconds) */
rs485conf.delay_rts_before_send = 0;

/* Set rts/txen delay after send, if needed: (in microseconds) */
rs485conf.delay_rts_after_send = 0;

if (ioctl (fd, TIOCSRS485, &rs485conf) < 0) {
printf("Error: TIOCSRS485 ioctl not supported.\n");
}

fcntl(fd, F_SETFL, 0);
int n = write(fd, "ABC\r\n", 5);
if (n < 0) {
/* Error handling */
}

if (close (fd) < 0) {
printf("Error: Can't close: /dev/ttySP0\n");
}
}
</source>

=== Hardware Notes ===
* The RS485 Transmit Enable (TXEN) output will be the RTS pin of the uart.
* The TXEN/RTS output is _active low_, it must be inverted to use it with the popular RS485 transceiver ICs.
* When the u-boot runs and the board start to boot, the RTS pin works as input, please add a pullup resistor to this pin before the inverter, to prevent RS485 bus lockups.

== OneWire ==
Informations and mini HOWTOs for my APF28DEV OneWire patch.

=== Software installation ===
* Recompile your Linux kernel with OneWire GPIO bus master (and some slave device) support.
* The driver works only in static compiled mode. (Load as module did not work.)
<pre class="host">
$ make linux-menuconfig
</pre>
<pre class="config">
Device Drivers --->
<*> Dallas's 1-wire support --->
1-wire Bus Masters --->
<*> GPIO 1-wire busmaster
1-wire Slaves --->
<*> Thermal family implementation
</pre>
<pre class="host">
$ make
</pre>
* Reflash your Linux kernel

=== Hardware Notes ===
* Connect the OneWire slave directly to the APF28_DEV board J9 connector:
* Vcc 3.3V is pin 1 on J9 connector
* DQ is pin 31 on J9 (LCD_D18 / GPIO 1_18)
* GND is pin 39 on J9
* Add an 1.2k pullup resistor between Vcc and DQ

=== How it works ===
The OneWire bus master driver every 10 seconds scan the bus for new slave devices.

Each detected OneWire slave device have a sub-directory with it's unique ID in "/sys/devices/w1 bus master".

The sub-directory format is <2 digit family ID>-<12 digit unique ID>.
<pre class=apf>
# ls -la /sys/devices/w1\ bus\ master/
total 0
drwxr-xr-x 4 root root 0 Jan 1 01:06 .
drwxr-xr-x 6 root root 0 Jan 1 01:05 ..
drwxr-xr-x 3 root root 0 Jan 1 01:06 28-000001e68904
lrwxrwxrwx 1 root root 0 Jan 1 01:07 driver -> ../../bus/w1/drivers/w1_master_driver
drwxr-xr-x 2 root root 0 Jan 1 01:07 power
lrwxrwxrwx 1 root root 0 Jan 1 01:07 subsystem -> ../../bus/w1
-rw-r--r-- 1 root root 4096 Jan 1 01:07 uevent
-rw-rw-rw- 1 root root 4096 Jan 1 01:07 w1_master_add
-r--r--r-- 1 root root 4096 Jan 1 01:07 w1_master_attempts
-r--r--r-- 1 root root 4096 Jan 1 01:07 w1_master_max_slave_count
-r--r--r-- 1 root root 4096 Jan 1 01:07 w1_master_name
-r--r--r-- 1 root root 4096 Jan 1 01:07 w1_master_pointer
-rw-rw-rw- 1 root root 4096 Jan 1 01:07 w1_master_pullup
-rw-rw-rw- 1 root root 4096 Jan 1 01:07 w1_master_remove
-rw-rw-rw- 1 root root 4096 Jan 1 01:07 w1_master_search
-r--r--r-- 1 root root 4096 Jan 1 01:07 w1_master_slave_count
-r--r--r-- 1 root root 4096 Jan 1 01:07 w1_master_slaves
-r--r--r-- 1 root root 4096 Jan 1 01:07 w1_master_timeout
</pre>
You can list the detected slaves from this files:
<pre class=apf>
# cat /sys/devices/w1\ bus\ master/w1_master_slave_count
1
# cat /sys/devices/w1\ bus\ master/w1_master_slaves
28-000001e68904
</pre>
Let's read the temperature: (The 28-xxx family is a DS18B20 temperature sensor in this example.)
<pre class=apf>
# cat /sys/devices/w1\ bus\ master/28-000001e68904/w1_slave
dd 01 4b 46 7f ff 03 10 1e : crc=1e YES
dd 01 4b 46 7f ff 03 10 1e t=29812
</pre>
The t=29812 means, the temperature is: 29.812°C

User:JanosA

2013-05-09T20:20:11Z

JanosA:

== About Me ==
I am IP Network and Datacenter engineer, currently I'm working for an Internet Service Provider in Hungary.

My hobby is programming embedded systems and creating my own small electronic boards.

=== Skills ===
* Assembly programming: PIC 8bit family
* C programming: PIC 8bit / PIC32MX family, Linux
* Perl, PHP, Javascript, Html programming with MySQL
* Linux system administration
* RS-232/485 serial communications: Ascii, Modbus, Saia Sbus, etc.
* IP networking

=== My ArmadeuS plans (APF28 based) ===
* Creating an universal home automation hardware for my friends, with easy programming in perl or PHP. :)
* Datacenter temperature monitoring, with RS-485 and OneWire communications.
* Data logger for Saia Sbus based intelligent power meters.

=== Currently I working on: ===
* RS485 support for driver: mxs-auart.c (APF28 2.6.35.3+ kernel)
* Next will be: Integrate and test the Linux kernel's one wire (w1) driver with APF28.

== RS485 ==
Informations and mini HOWTOs for my APF28/iMX28 mxs-auart and busybox stty patches.

=== Linux stty ===
* Setup APF28 serial port for RS485 communication:
<pre class=apf>
# stty -F /dev/ttySP0 raw
# stty -F /dev/ttySP0 -echo -echoe -echok
# stty -F /dev/ttySP0 rs485
</pre>

* Set extra delays for TXEN/RTS signaling before and after the transmitted packet (in microseconds):
<pre class=apf>
# stty -F /dev/ttySP0 rs485delaybefore 100
# stty -F /dev/ttySP0 rs485delayafter 100
</pre>

* To get current RS485 parameters. (If the port device supports the RS485 options you will see the last two lines)
<pre class=apf>
# stty -F /dev/ttySP0
speed 9600 baud; line = 0;
intr = ^C; quit = ^\; erase = ^?; kill = ^U; eof = ^D; eol = <undef>;
eol2 = <undef>; swtch = <undef>; start = ^Q; stop = ^S; susp = ^Z; rprnt = ^R;
werase = ^W; lnext = ^V; flush = ^O; min = 1; time = 0;
-brkint -imaxbel
rs485 -rs485rtsonsend -rs485rtsaftersend -rs485rxduringtx
rs485delaybefore = 100; rs485delayafter = 100; rs485delaylastchartx = 1250;
</pre>
Please note:
* You can't set the "rs485delaylastchartx" parameter, it's calculated automatically from the baudrate.
Special notes for the APF28/iMX28 mxs-auart driver:
* All delays are in microseconds.
* The "rs485delaylastchartx" parameter is not used in DMA mode.
* The parameters: "rs485rtsonsend" "rs485rtsaftersend" "rs485rxduringtx" are not used. (Only used by atmel_serial.c and crisv10.c drivers)
* If the RS485 mode is turned on, it will override (turn off) the RTS/CTS hardware flow settings of the uart, don't care what is configured.

=== C code ===
* The RS485 mode can be turned on with ioctl calls from C code, here is the example:
<source lang="C">
#include <stdio.h>
#include <fcntl.h>
#include <linux/ioctl.h>
#include <linux/serial.h>
#include <asm-generic/ioctls.h> /* TIOCGRS485 + TIOCSRS485 ioctl definitions */

int main(void) {
struct serial_rs485 rs485conf;

int fd = open ("/dev/ttySP0", O_RDWR);
if (fd < 0) {
printf("Error: Can't open: /dev/ttySP0\n");
}

/* Don't forget to read first the current state of the RS485 options with ioctl.
If You don't do this, You will destroy the rs485conf.delay_rts_last_char_tx
parameter which is automatically calculated by the driver when You opens the
port device. */
if (ioctl (fd, TIOCGRS485, &rs485conf) < 0) {
printf("Error: TIOCGRS485 ioctl not supported.\n");
}

/* Enable RS485 mode: */
rs485conf.flags |= SER_RS485_ENABLED;

/* Set rts/txen delay before send, if needed: (in microseconds) */
rs485conf.delay_rts_before_send = 0;

/* Set rts/txen delay after send, if needed: (in microseconds) */
rs485conf.delay_rts_after_send = 0;

if (ioctl (fd, TIOCSRS485, &rs485conf) < 0) {
printf("Error: TIOCSRS485 ioctl not supported.\n");
}

fcntl(fd, F_SETFL, 0);
int n = write(fd, "ABC\r\n", 5);
if (n < 0) {
/* Error handling */
}

if (close (fd) < 0) {
printf("Error: Can't close: /dev/ttySP0\n");
}
}
</source>

=== Hardware Notes ===
* The RS485 Transmit Enable (TXEN) output will be the RTS pin of the uart.
* The TXEN/RTS output is _active low_, it must be inverted to use it with the popular RS485 transceiver ICs.
* When the u-boot runs and the board start to boot, the RTS pin works as input, please add a pullup resistor to this pin before the inverter, to prevent RS485 bus lockups.

== OneWire ==
Informations and mini HOWTOs for my APF28DEV OneWire patches.

=== Software installation ===
* Recompile your Linux kernel with OneWire GPIO bus master (and some slave device) support.
* The driver works only in static compiled mode. (Load as module did not work.)
<pre class="host">
$ make linux-menuconfig
</pre>
<pre class="config">
Device Drivers --->
<*> Dallas's 1-wire support --->
1-wire Bus Masters --->
<*> GPIO 1-wire busmaster
1-wire Slaves --->
<*> Thermal family implementation
</pre>
<pre class="host">
$ make
</pre>
* Reflash your Linux kernel

=== Hardware Notes ===
* Connect the OneWire slave directly to the APF28_DEV board J9 connector:
* Vcc 3.3V is pin 1 on J9 connector
* DQ is pin 31 on J9 (LCD_D18 / GPIO 1_18)
* GND is pin 39 on J9
* Add an 1.2k pullup resistor between Vcc and DQ

=== How it works ===
The OneWire bus master driver every 10 seconds scan the bus for new slave devices.

Each detected OneWire slave device have a sub-directory with it's unique ID in "/sys/devices/w1 bus master".

The sub-directory format is <2 digit family ID>-<12 digit unique ID>.
<pre class=apf>
# ls -la /sys/devices/w1\ bus\ master/
total 0
drwxr-xr-x 4 root root 0 Jan 1 01:06 .
drwxr-xr-x 6 root root 0 Jan 1 01:05 ..
drwxr-xr-x 3 root root 0 Jan 1 01:06 28-000001e68904
lrwxrwxrwx 1 root root 0 Jan 1 01:07 driver -> ../../bus/w1/drivers/w1_master_driver
drwxr-xr-x 2 root root 0 Jan 1 01:07 power
lrwxrwxrwx 1 root root 0 Jan 1 01:07 subsystem -> ../../bus/w1
-rw-r--r-- 1 root root 4096 Jan 1 01:07 uevent
-rw-rw-rw- 1 root root 4096 Jan 1 01:07 w1_master_add
-r--r--r-- 1 root root 4096 Jan 1 01:07 w1_master_attempts
-r--r--r-- 1 root root 4096 Jan 1 01:07 w1_master_max_slave_count
-r--r--r-- 1 root root 4096 Jan 1 01:07 w1_master_name
-r--r--r-- 1 root root 4096 Jan 1 01:07 w1_master_pointer
-rw-rw-rw- 1 root root 4096 Jan 1 01:07 w1_master_pullup
-rw-rw-rw- 1 root root 4096 Jan 1 01:07 w1_master_remove
-rw-rw-rw- 1 root root 4096 Jan 1 01:07 w1_master_search
-r--r--r-- 1 root root 4096 Jan 1 01:07 w1_master_slave_count
-r--r--r-- 1 root root 4096 Jan 1 01:07 w1_master_slaves
-r--r--r-- 1 root root 4096 Jan 1 01:07 w1_master_timeout
</pre>
You can list the detected slaves from this files:
<pre class=apf>
# cat /sys/devices/w1\ bus\ master/w1_master_slave_count
1
# cat /sys/devices/w1\ bus\ master/w1_master_slaves
28-000001e68904
</pre>
Let's read the temperature: (The 28-xxx family is a DS18B20 temperature sensor in this example.)
<pre class=apf>
# cat /sys/devices/w1\ bus\ master/28-000001e68904/w1_slave
dd 01 4b 46 7f ff 03 10 1e : crc=1e YES
dd 01 4b 46 7f ff 03 10 1e t=29812
</pre>
The t=29812 means, the temperature is: 29.812°C

User:JanosA

2013-05-09T20:17:53Z

JanosA:

== About Me ==
I am IP Network and Datacenter engineer, currently I'm working for an Internet Service Provider in Hungary.

My hobby is programming embedded systems and creating my own small electronic boards.

=== Skills ===
* Assembly programming: PIC 8bit family
* C programming: PIC 8bit / PIC32MX family, Linux
* Perl, PHP, Javascript, Html programming with MySQL
* Linux system administration
* RS-232/485 serial communications: Ascii, Modbus, Saia Sbus, etc.
* IP networking

=== My ArmadeuS plans (APF28 based) ===
* Creating an universal home automation hardware for my friends, with easy programming in perl or PHP. :)
* Datacenter temperature monitoring, with RS-485 and OneWire communications.
* Data logger for Saia Sbus based intelligent power meters.

=== Currently I working on: ===
* RS485 support for driver: mxs-auart.c (APF28 2.6.35.3+ kernel)
* Next will be: Integrate and test the Linux kernel's one wire (w1) driver with APF28.

== RS485 ==
Informations and mini HOWTOs for my APF28/iMX28 mxs-auart and busybox stty patches.

=== Linux stty ===
* Setup APF28 serial port for RS485 communication:
<pre class=apf>
# stty -F /dev/ttySP0 raw
# stty -F /dev/ttySP0 -echo -echoe -echok
# stty -F /dev/ttySP0 rs485
</pre>

* Set extra delays for TXEN/RTS signaling before and after the transmitted packet (in microseconds):
<pre class=apf>
# stty -F /dev/ttySP0 rs485delaybefore 100
# stty -F /dev/ttySP0 rs485delayafter 100
</pre>

* To get current RS485 parameters. (If the port device supports the RS485 options you will see the last two lines)
<pre class=apf>
# stty -F /dev/ttySP0
speed 9600 baud; line = 0;
intr = ^C; quit = ^\; erase = ^?; kill = ^U; eof = ^D; eol = <undef>;
eol2 = <undef>; swtch = <undef>; start = ^Q; stop = ^S; susp = ^Z; rprnt = ^R;
werase = ^W; lnext = ^V; flush = ^O; min = 1; time = 0;
-brkint -imaxbel
rs485 -rs485rtsonsend -rs485rtsaftersend -rs485rxduringtx
rs485delaybefore = 100; rs485delayafter = 100; rs485delaylastchartx = 1250;
</pre>
Please note:
* You can't set the "rs485delaylastchartx" parameter, it's calculated automatically from the baudrate.
Special notes for the APF28/iMX28 mxs-auart driver:
* All delays are in microseconds.
* The "rs485delaylastchartx" parameter is not used in DMA mode.
* The parameters: "rs485rtsonsend" "rs485rtsaftersend" "rs485rxduringtx" are not used. (Only used by atmel_serial.c and crisv10.c drivers)
* If the RS485 mode is turned on, it will override (turn off) the RTS/CTS hardware flow settings of the uart, don't care what is configured.

=== C code ===
* The RS485 mode can be turned on with ioctl calls from C code, here is the example:
<source lang="C">
#include <stdio.h>
#include <fcntl.h>
#include <linux/ioctl.h>
#include <linux/serial.h>
#include <asm-generic/ioctls.h> /* TIOCGRS485 + TIOCSRS485 ioctl definitions */

int main(void) {
struct serial_rs485 rs485conf;

int fd = open ("/dev/ttySP0", O_RDWR);
if (fd < 0) {
printf("Error: Can't open: /dev/ttySP0\n");
}

/* Don't forget to read first the current state of the RS485 options with ioctl.
If You don't do this, You will destroy the rs485conf.delay_rts_last_char_tx
parameter which is automatically calculated by the driver when You opens the
port device. */
if (ioctl (fd, TIOCGRS485, &rs485conf) < 0) {
printf("Error: TIOCGRS485 ioctl not supported.\n");
}

/* Enable RS485 mode: */
rs485conf.flags |= SER_RS485_ENABLED;

/* Set rts/txen delay before send, if needed: (in microseconds) */
rs485conf.delay_rts_before_send = 0;

/* Set rts/txen delay after send, if needed: (in microseconds) */
rs485conf.delay_rts_after_send = 0;

if (ioctl (fd, TIOCSRS485, &rs485conf) < 0) {
printf("Error: TIOCSRS485 ioctl not supported.\n");
}

fcntl(fd, F_SETFL, 0);
int n = write(fd, "ABC\r\n", 5);
if (n < 0) {
/* Error handling */
}

if (close (fd) < 0) {
printf("Error: Can't close: /dev/ttySP0\n");
}
}
</source>

=== Hardware Notes ===
* The RS485 Transmit Enable (TXEN) output will be the RTS pin of the uart.
* The TXEN/RTS output is _active low_, it must be inverted to use it with the popular RS485 transceiver ICs.
* When the u-boot runs and the board start to boot, the RTS pin works as input, please add a pullup resistor to this pin before the inverter, to prevent RS485 bus lockups.

== OneWire ==
Informations and mini HOWTOs for my APF28DEV OneWire patches.

=== Software installation ===
* Recompile your Linux kernel with OneWire GPIO bus master (and some slave device) support.
* The driver works only in static compiled mode. (Load as module did not work.)
<pre class="host">
$ make linux-menuconfig
</pre>
<pre class="config">
Device Drivers --->
<*> Dallas's 1-wire support --->
1-wire Bus Masters --->
<*> GPIO 1-wire busmaster
1-wire Slaves --->
<*> Thermal family implementation
</pre>
<pre class="host">
$ make
</pre>
* Reflash your Linux kernel

=== Hardware Notes ===
* Connect the OneWire slave directly to the APF28_DEV board J9 connector:
* Vcc 3.3V is pin 1 on J9 connector
* DQ is pin 31 on J9 (LCD_D18 / GPIO 1_18)
* GND is pin 39 on J9
* Add an 1.2k pullup resistor between Vcc and DQ

=== How it works ===
The OneWire bus master driver every 10 seconds scan the bus for new slave devices.

Each detected OneWire slave device have a sub-directory with it's unique ID in "/sys/devices/w1 bus master".

The sub-directory format is <2 digit family ID>-<12 digit unique ID>.
<pre class=apf>
# ls -la /sys/devices/w1\ bus\ master/
total 0
drwxr-xr-x 4 root root 0 Jan 1 01:06 .
drwxr-xr-x 6 root root 0 Jan 1 01:05 ..
drwxr-xr-x 3 root root 0 Jan 1 01:06 28-000001e68904
lrwxrwxrwx 1 root root 0 Jan 1 01:07 driver -> ../../bus/w1/drivers/w1_master_driver
drwxr-xr-x 2 root root 0 Jan 1 01:07 power
lrwxrwxrwx 1 root root 0 Jan 1 01:07 subsystem -> ../../bus/w1
-rw-r--r-- 1 root root 4096 Jan 1 01:07 uevent
-rw-rw-rw- 1 root root 4096 Jan 1 01:07 w1_master_add
-r--r--r-- 1 root root 4096 Jan 1 01:07 w1_master_attempts
-r--r--r-- 1 root root 4096 Jan 1 01:07 w1_master_max_slave_count
-r--r--r-- 1 root root 4096 Jan 1 01:07 w1_master_name
-r--r--r-- 1 root root 4096 Jan 1 01:07 w1_master_pointer
-rw-rw-rw- 1 root root 4096 Jan 1 01:07 w1_master_pullup
-rw-rw-rw- 1 root root 4096 Jan 1 01:07 w1_master_remove
-rw-rw-rw- 1 root root 4096 Jan 1 01:07 w1_master_search
-r--r--r-- 1 root root 4096 Jan 1 01:07 w1_master_slave_count
-r--r--r-- 1 root root 4096 Jan 1 01:07 w1_master_slaves
-r--r--r-- 1 root root 4096 Jan 1 01:07 w1_master_timeout
</pre>
You can list the detected slaves from this files:
<pre class=apf>
# cat /sys/devices/w1\ bus\ master/w1_master_slave_count
1
# cat /sys/devices/w1\ bus\ master/w1_master_slaves
28-000001e68904
</pre>
Let's read the temperature:
<pre class=apf>
# cat /sys/devices/w1\ bus\ master/28-000001e68904/w1_slave
dd 01 4b 46 7f ff 03 10 1e : crc=1e YES
dd 01 4b 46 7f ff 03 10 1e t=29812
</pre>
The t=29812 means, the temperature is: 29.812°C

User:JanosA

2013-05-09T19:09:23Z

JanosA: Adding OneWire Informations

== About Me ==
I am IP Network and Datacenter engineer, currently I'm working for an Internet Service Provider in Hungary.

My hobby is programming embedded systems and creating my own small electronic boards.

=== Skills ===
* Assembly programming: PIC 8bit family
* C programming: PIC 8bit / PIC32MX family, Linux
* Perl, PHP, Javascript, Html programming with MySQL
* Linux system administration
* RS-232/485 serial communications: Ascii, Modbus, Saia Sbus, etc.
* IP networking

=== My ArmadeuS plans (APF28 based) ===
* Creating an universal home automation hardware for my friends, with easy programming in perl or PHP. :)
* Datacenter temperature monitoring, with RS-485 and OneWire communications.
* Data logger for Saia Sbus based intelligent power meters.

=== Currently I working on: ===
* RS485 support for driver: mxs-auart.c (APF28 2.6.35.3+ kernel)
* Next will be: Integrate and test the Linux kernel's one wire (w1) driver with APF28.

== RS485 ==
Informations and mini HOWTOs for my APF28/iMX28 mxs-auart and busybox stty patches.

=== Linux stty ===
* Setup APF28 serial port for RS485 communication:
<pre class=apf>
# stty -F /dev/ttySP0 raw
# stty -F /dev/ttySP0 -echo -echoe -echok
# stty -F /dev/ttySP0 rs485
</pre>

* Set extra delays for TXEN/RTS signaling before and after the transmitted packet (in microseconds):
<pre class=apf>
# stty -F /dev/ttySP0 rs485delaybefore 100
# stty -F /dev/ttySP0 rs485delayafter 100
</pre>

* To get current RS485 parameters. (If the port device supports the RS485 options you will see the last two lines)
<pre class=apf>
# stty -F /dev/ttySP0
speed 9600 baud; line = 0;
intr = ^C; quit = ^\; erase = ^?; kill = ^U; eof = ^D; eol = <undef>;
eol2 = <undef>; swtch = <undef>; start = ^Q; stop = ^S; susp = ^Z; rprnt = ^R;
werase = ^W; lnext = ^V; flush = ^O; min = 1; time = 0;
-brkint -imaxbel
rs485 -rs485rtsonsend -rs485rtsaftersend -rs485rxduringtx
rs485delaybefore = 100; rs485delayafter = 100; rs485delaylastchartx = 1250;
</pre>
Please note:
* You can't set the "rs485delaylastchartx" parameter, it's calculated automatically from the baudrate.
Special notes for the APF28/iMX28 mxs-auart driver:
* All delays are in microseconds.
* The "rs485delaylastchartx" parameter is not used in DMA mode.
* The parameters: "rs485rtsonsend" "rs485rtsaftersend" "rs485rxduringtx" are not used. (Only used by atmel_serial.c and crisv10.c drivers)
* If the RS485 mode is turned on, it will override (turn off) the RTS/CTS hardware flow settings of the uart, don't care what is configured.

=== C code ===
* The RS485 mode can be turned on with ioctl calls from C code, here is the example:
<source lang="C">
#include <stdio.h>
#include <fcntl.h>
#include <linux/ioctl.h>
#include <linux/serial.h>
#include <asm-generic/ioctls.h> /* TIOCGRS485 + TIOCSRS485 ioctl definitions */

int main(void) {
struct serial_rs485 rs485conf;

int fd = open ("/dev/ttySP0", O_RDWR);
if (fd < 0) {
printf("Error: Can't open: /dev/ttySP0\n");
}

/* Don't forget to read first the current state of the RS485 options with ioctl.
If You don't do this, You will destroy the rs485conf.delay_rts_last_char_tx
parameter which is automatically calculated by the driver when You opens the
port device. */
if (ioctl (fd, TIOCGRS485, &rs485conf) < 0) {
printf("Error: TIOCGRS485 ioctl not supported.\n");
}

/* Enable RS485 mode: */
rs485conf.flags |= SER_RS485_ENABLED;

/* Set rts/txen delay before send, if needed: (in microseconds) */
rs485conf.delay_rts_before_send = 0;

/* Set rts/txen delay after send, if needed: (in microseconds) */
rs485conf.delay_rts_after_send = 0;

if (ioctl (fd, TIOCSRS485, &rs485conf) < 0) {
printf("Error: TIOCSRS485 ioctl not supported.\n");
}

fcntl(fd, F_SETFL, 0);
int n = write(fd, "ABC\r\n", 5);
if (n < 0) {
/* Error handling */
}

if (close (fd) < 0) {
printf("Error: Can't close: /dev/ttySP0\n");
}
}
</source>

=== Hardware Notes ===
* The RS485 Transmit Enable (TXEN) output will be the RTS pin of the uart.
* The TXEN/RTS output is _active low_, it must be inverted to use it with the popular RS485 transceiver ICs.
* When the u-boot runs and the board start to boot, the RTS pin works as input, please add a pullup resistor to this pin before the inverter, to prevent RS485 bus lockups.

== OneWire ==
Informations and mini HOWTOs for my APF28DEV OneWire patches.

=== Software installation ===
* Recompile your Linux kernel with OneWire GPIO bus master (and some slave device) support:
<pre class="host">
$ make linux-menuconfig
</pre>
<pre class="config">
Device Drivers --->
<*> Dallas's 1-wire support --->
1-wire Bus Masters --->
<*> GPIO 1-wire busmaster
1-wire Slaves --->
<*> Thermal family implementation
</pre>
<pre class="host">
$ make
</pre>
* Reflash your Linux kernel

=== Hardware Notes ===
* Connect the OneWire slave directly to the APF28_DEV board J9 connector:
* Vcc 3.3V is pin 1 on J9 connector
* DQ is pin 31 on J9 (LCD_D18 / GPIO 1_18)
* GND is pin 39 on J9
* Add an 1.2k pullup resistor between Vcc and DQ

=== How it works ===
The OneWire bus master driver every 10 seconds scan the bus for new slave devices.

Each detected OneWire slave device have a sub-directory with it's unique ID in "/sys/devices/w1 bus master".

The sub-directory format is <2 digit family ID>-<12 digit unique ID>.
<pre class=apf>
# ls -la /sys/devices/w1\ bus\ master/
total 0
drwxr-xr-x 4 root root 0 Jan 1 01:06 .
drwxr-xr-x 6 root root 0 Jan 1 01:05 ..
drwxr-xr-x 3 root root 0 Jan 1 01:06 28-000001e68904
lrwxrwxrwx 1 root root 0 Jan 1 01:07 driver -> ../../bus/w1/drivers/w1_master_driver
drwxr-xr-x 2 root root 0 Jan 1 01:07 power
lrwxrwxrwx 1 root root 0 Jan 1 01:07 subsystem -> ../../bus/w1
-rw-r--r-- 1 root root 4096 Jan 1 01:07 uevent
-rw-rw-rw- 1 root root 4096 Jan 1 01:07 w1_master_add
-r--r--r-- 1 root root 4096 Jan 1 01:07 w1_master_attempts
-r--r--r-- 1 root root 4096 Jan 1 01:07 w1_master_max_slave_count
-r--r--r-- 1 root root 4096 Jan 1 01:07 w1_master_name
-r--r--r-- 1 root root 4096 Jan 1 01:07 w1_master_pointer
-rw-rw-rw- 1 root root 4096 Jan 1 01:07 w1_master_pullup
-rw-rw-rw- 1 root root 4096 Jan 1 01:07 w1_master_remove
-rw-rw-rw- 1 root root 4096 Jan 1 01:07 w1_master_search
-r--r--r-- 1 root root 4096 Jan 1 01:07 w1_master_slave_count
-r--r--r-- 1 root root 4096 Jan 1 01:07 w1_master_slaves
-r--r--r-- 1 root root 4096 Jan 1 01:07 w1_master_timeout
</pre>
You can list the detected slaves from this files:
<pre class=apf>
# cat /sys/devices/w1\ bus\ master/w1_master_slave_count
1
# cat /sys/devices/w1\ bus\ master/w1_master_slaves
28-000001e68904
</pre>
Let's read the temperature:
<pre class=apf>
# cat /sys/devices/w1\ bus\ master/28-000001e68904/w1_slave
dd 01 4b 46 7f ff 03 10 1e : crc=1e YES
dd 01 4b 46 7f ff 03 10 1e t=29812
</pre>
The t=29812 means, the temperature is: 29.812°C

User:JanosA

2013-05-06T21:55:37Z

JanosA:

User:JanosA

2013-05-06T21:50:19Z

JanosA:

User:JanosA

2013-05-06T21:46:08Z

JanosA:

I am IP Network and Datacenter engineer, currently I'm working for an Internet Service Provider in Hungary.

My hobby is programming embedded systems and creating my own small electronic boards.

== Skills ==
* Assembly programming: PIC 8bit family
* C programming: PIC 8bit / PIC32MX family, Linux
* Perl, PHP, Javascript, Html programming with MySQL
* Linux system administration
* RS-232/485 serial communications: Ascii, Modbus, Saia Sbus, etc.
* IP networking

== My ArmadeuS plans (APF28 based) ==
* Creating an universal home automation hardware for my friends, with easy programming in perl or PHP. :)
* Datacenter temperature monitoring, with RS-485 and OneWire communications.
* Data logger for Saia Sbus based intelligent power meters.

== RS485 ==
Informations and mini HOWTOs for my APF28/iMX28 mxs-auart and busybox stty patches.

=== Linux stty ===
* Setup APF28 serial port for RS485 communication:
<pre class=apf>
# stty -F /dev/ttySP0 raw
# stty -F /dev/ttySP0 -echo -echoe -echok
# stty -F /dev/ttySP0 rs485
</pre>

* Set extra delays for TXEN/RTS signaling before and after the transmitted packet (in microseconds):
<pre class=apf>
# stty -F /dev/ttySP0 rs485delaybefore 100
# stty -F /dev/ttySP0 rs485delayafter 100
</pre>

* To get current RS485 parameters. (If the port device supports the RS485 options you will see the last two lines)
<pre class=apf>
# stty -F /dev/ttySP0
speed 9600 baud; line = 0;
intr = ^C; quit = ^\; erase = ^?; kill = ^U; eof = ^D; eol = <undef>;
eol2 = <undef>; swtch = <undef>; start = ^Q; stop = ^S; susp = ^Z; rprnt = ^R;
werase = ^W; lnext = ^V; flush = ^O; min = 1; time = 0;
-brkint -imaxbel
rs485 -rs485rtsonsend -rs485rtsaftersend -rs485rxduringtx
rs485delaybefore = 100; rs485delayafter = 100; rs485delaylastchartx = 1250;
</pre>
Please note:
* You can't set the "rs485delaylastchartx" parameter, it's calculated automatically from the baudrate.
Special notes for the APF28/iMX28 mxs-auart driver:
* All delays are in microseconds.
* The "rs485delaylastchartx" parameter is not used in DMA mode.
* The parameters: "rs485rtsonsend" "rs485rtsaftersend" "rs485rxduringtx" are not used.
* If the RS485 mode is turned on, it will override (turn off) the RTS/CTS hardware flow settings of the uart, don't care what is configured.

=== C code ===
* The RS485 mode can be turned on with ioctl calls from C code, here is the example:
<source lang="C">
#include <stdio.h>
#include <fcntl.h>
#include <linux/ioctl.h>
#include <linux/serial.h>
#include <asm-generic/ioctls.h> /* TIOCGRS485 + TIOCSRS485 ioctl definitions */

int main(void) {
struct serial_rs485 rs485conf;

int fd = open ("/dev/ttySP0", O_RDWR);
if (fd < 0) {
printf("Error: Can't open: /dev/ttySP0\n");
}

/* Don't forget to read first the current state of the RS485 options with ioctl.
If You don't do this, You will destroy the rs485conf.delay_rts_last_char_tx
parameter which is automatically calculated by the driver when You opens the
port device. */
if (ioctl (fd, TIOCGRS485, &rs485conf) < 0) {
printf("Error: TIOCGRS485 ioctl not supported.\n");
}

/* Enable RS485 mode: */
rs485conf.flags |= SER_RS485_ENABLED;

/* Set rts/txen delay before send, if needed: (in microseconds) */
rs485conf.delay_rts_before_send = 0;

/* Set rts/txen delay after send, if needed: (in microseconds) */
rs485conf.delay_rts_after_send = 0;

if (ioctl (fd, TIOCSRS485, &rs485conf) < 0) {
printf("Error: TIOCSRS485 ioctl not supported.\n");
}

fcntl(fd, F_SETFL, 0);
int n = write(fd, "ABC\r\n", 5);
if (n < 0) {
/* Error handling */
}

if (close (fd) < 0) {
printf("Error: Can't close: /dev/ttySP0\n");
}
}
</source>

=== Hardware Notes ===
* The RS485 Transmit Enable (TXEN) output will be the RTS pin of the uart.
* The TXEN/RTS output is _active low_, it must be inverted to use it with the popular RS485 transceiver ICs.
* When the u-boot runs and the board start to boot, the RTS pin works as input, please add a pullup resistor to this pin before the inverter, to prevent RS485 bus lockups.

User:JanosA

2013-05-06T21:26:59Z

JanosA:

I am IP Network and Datacenter engineer, currently I'm working for an Internet Service Provider in Hungary.

My hobby is programming embedded systems and creating my own small electronic boards.

== Skills ==
* Assembly programming: PIC 8bit family
* C programming: PIC 8bit / PIC32MX family, Linux
* Perl, PHP, Javascript, Html programming with MySQL
* Linux system administration
* RS-232/485 serial communications: Ascii, Modbus, Saia Sbus, etc.
* IP networking

== My ArmadeuS plans (APF28 based) ==
* Creating an universal home automation hardware for my friends, with easy programming in perl or PHP. :)
* Datacenter temperature monitoring, with RS-485 and OneWire communications.
* Data logger for Saia Sbus based intelligent power meters.

== RS485 ==
Mini HOWTOs for my APF28/iMX28 mxs-auart and busybox stty patches.

* Setup APF28 serial port for RS485 communication:
<pre class=apf>
# stty -F /dev/ttySP0 raw
# stty -F /dev/ttySP0 -echo -echoe -echok
# stty -F /dev/ttySP0 rs485
</pre>

* Set extra delays for TXEN/RTS signaling before and after the transmitted packet (in microseconds):
<pre class=apf>
# stty -F /dev/ttySP0 rs485delaybefore 100
# stty -F /dev/ttySP0 rs485delayafter 100
</pre>

* To get current RS485 parameters. (If the port device supports the RS485 options you will see the last two lines)
<pre class=apf>
# stty -F /dev/ttySP0
speed 9600 baud; line = 0;
intr = ^C; quit = ^\; erase = ^?; kill = ^U; eof = ^D; eol = <undef>;
eol2 = <undef>; swtch = <undef>; start = ^Q; stop = ^S; susp = ^Z; rprnt = ^R;
werase = ^W; lnext = ^V; flush = ^O; min = 1; time = 0;
-brkint -imaxbel
rs485 -rs485rtsonsend -rs485rtsaftersend -rs485rxduringtx
rs485delaybefore = 100; rs485delayafter = 100; rs485delaylastchartx = 1250;
</pre>
Please note:
* You can't set the "rs485delaylastchartx" parameter, it's calculated automatically from the baudrate.
Special notes only for APF28/iMX28 mxs-auart driver:
* All delays are in microseconds.
* The "rs485delaylastchartx" parameter is not used in DMA mode.
* The parameters: "rs485rtsonsend" "rs485rtsaftersend" "rs485rxduringtx" are not used.

* The RS485 mode can be turned on with ioctl calls from C code, here is the example:
<source lang="C">
#include <stdio.h>
#include <fcntl.h>
#include <linux/ioctl.h>
#include <linux/serial.h>
#include <asm-generic/ioctls.h> /* TIOCGRS485 + TIOCSRS485 ioctl definitions */

int main(void) {
struct serial_rs485 rs485conf;

int fd = open ("/dev/ttySP0", O_RDWR);
if (fd < 0) {
printf("Error: Can't open: /dev/ttySP0\n");
}

/* Don't forget to read first the current state of the RS485 options with ioctl.
If You don't do this, You will destroy the rs485conf.delay_rts_last_char_tx
parameter which is automatically calculated by the driver when You opens the
port device. */
if (ioctl (fd, TIOCGRS485, &rs485conf) < 0) {
printf("Error: TIOCGRS485 ioctl not supported.\n");
}

/* Enable RS485 mode: */
rs485conf.flags |= SER_RS485_ENABLED;

/* Set rts/txen delay before send, if needed: (in microseconds) */
rs485conf.delay_rts_before_send = 0;

/* Set rts/txen delay after send, if needed: (in microseconds) */
rs485conf.delay_rts_after_send = 0;

if (ioctl (fd, TIOCSRS485, &rs485conf) < 0) {
printf("Error: TIOCSRS485 ioctl not supported.\n");
}

fcntl(fd, F_SETFL, 0);
int n = write(fd, "ABC\r\n", 5);
if (n < 0) {
/* Error handling */
}

if (close (fd) < 0) {
printf("Error: Can't close: /dev/ttySP0\n");
}
}
</source>

User:JanosA

2013-05-06T21:04:30Z

JanosA:

Members

2013-04-26T10:13:49Z

JanosA: /* Google Map */

==Google Map==

<googlemap lat="47" lon="6" width=640 height=480 zoom=4>
47.270377, 6.025314, [[User:JulienB]] Besancon
47.752598,7.301788, ARMadeus Systems
47.760791, 7.339897, [[User:Salocin68]] Mulhouse
47.734392,7.316975, [[User:FabienM]] Mulhouse
46.946161,7.517052, [[User:Jorasse]] Gümligen
47.681108, 7.390366, [[User:Carbure]] Helfranzkirch
47.436448, 8.429947, [[User:SonZerro]] Baden
44.653992, 6.176672, [[User:JulienN]] Chabottes
48.573342, 7.911476, [[User:KroMignon]] Legelshurst
42.734405, 2.894211, ELIAUS Perpignan
47.653363, 6.862335, UTBM Belfort
45.689589, 5.026395, [[User:OlivierT]] St Bonnet de Mure
48.879619, 2.351074, Paris - 21 members
43.622159, 1.442642, Toulouse - 2 members
-21.115141, 55.536384, La Réunion - 1 member
14.551684, -60.912323, La Martinique - 1 member
48.682805, 2.169186, [[User:BrunoL]] Les Ulis
47.399744, 8.53775, Zurich - 1 member
46.810282, 7.151241, Fribourg
47.574904, 7.580566, Basel
48.839250, 2.392584, [[User:jmn12]] Paris
60.187238, 24.819231, [[User:EemeliA]] Espoo
53.371859, -6.2677, Dublin - 1 member
50.637704, 5.608521, Liège - 1 member
50.67, 3.48, Velaines - 1 member
48.199964, 11.57959, Munich - 1 member
48.109588, -1.678752, Rennes - 1 member
47.750109, -3.366339, [[User:MatthieuT]] Lorient
48.70,2.03, [[User:JulienPeeters]] Chevreuse
45.190325, 5.700316, [[User:NicolasL]] Fontaine
49.279296, 2.472973 [[User:DavidC]] Nogent sur Oise
46.208644, 6.130027, [[User:EugeneR]] Genève
48.667158, 2.706585, [[User:BernardR]] Soignolles en Brie, France
45.188963, 5.709822, [[User:OlivierS]], [[User:HugoP|Hugo Petit]] - Grenoble, France
47.214613, -0.737329, [[User:BrunoS]] Chemillé, France
47.225164, -1.556625, [[User:KevinP]] Nantes, France
43.609234, 1.442642, [[User:PierreBa]] Toulouse, France
41.668809, -0.87616, [[User:AntonioMB]] Zaragoza, España
49.200145, 0.407136, [[User:JeanFrancoisR]] - Asnières
48.109588, -1.678752, [[User:MichelTe]] - Rennes
49.163073, 2.550201, [[User:JulienBa]] - Pontarmé
43.488299, 5.494709, [[User:FrankA]] - Meyreuil
43.622159, 1.442642, [[User:PierreAlexandreS]] - Toulouse, France
51.46513, -0.9692, [[User:AlexG]] - Reading, UK
43.312439, 10.517693, [[User:PaoloB]] - Cecina, Italy
52.63, 4.75, Alkmaar - 1 member
50.776093, 14.632759, [[User:PetrD]] - Cvikov, ČR
48.42097, -4.471693, [[User:OlivierR]] - Brest, France
48.575244, -4.563446, [[User:JeanChristopheL]] - Brest, France
49.417767, 2.826945, [[User:PhilippeL]] - Compiègne, France
48.806044, 2.347512, [[User:PierreDe]] - Arcueil, France
50.803050, 4.358533, [[User:SebastienVC]] - Bruxelles, Belgique
45.535213, -73.668823, [[User:PhilBB]] - Montreal, Canada
48.830759, 2.359204, [[User:Théo179]] - Arcueil, France
48.694563, 2.184605, [[User:IdrissB|Idriss]] - Courbevoie, France
41.563161, 2.020814, [[User:JaumeF|Jaume Figueras]] - Terrassa, Catalunya, Spain
35.415303,139.595332, [[User:HiroshiM]] - Yokohama, Japan
45.203191,5.716288, [[User:GaelV|Gaël Vanderbruggen]] - St Martin le Vinoux, France
48.700223, 2.22766, [[User:JeanMarcM| pieddemamouth/ Jean-Marc Montanier]] - Villebon-sur-Yvette, France
48.419351, -4.469765, [[User:MohamedS]] - Brest, FRANCE
47.319276, 0.285645, [[User:StephaneD]] - Joué les Tours, FRANCE
49.183274,-0.37096,[[User:ArnaudB]] - Caen, France
40.416691,-3.700345, [[User:AntonioD]] - Madrid, Spain
49.674442,-1.736793, [[User:FrancoisL]] - Urville-Nacqueville, France
-1.45502,-48.502368, [[User:MarcusF]] - Belém-PA, Brazil
47.219335,-1.555939, [[User:PhilippeLe]] - Nantes, France
49.652024,3.28098, [[User:JeremieG|Jeremie Girouard]] - Vouel
49.119666,6.176905, [[User:PierreB]] - Metz, France
38.895308,-77.036133, [[User:KennethM]] - Washington DC, United States
45.35510,6.30504, [[User:VincentC]] - Saint-Avre, France
47.0667,6.75,[[User:FlorianM]] - Le Locle, Suisse
50.063606,19.943039,[[User:VascoB]] - Kraków, Poland
39.656225,-8.575344,[[User:VascoB]] - Ourém, Portugal
47.49772,19.039993,[[User:JanosA]] - Budapest, Hungary
</googlemap>
<br>

===How to add your position===
* go to http://maps.google.com/
* type in the name of your town and launch "Search Google Maps", for example:
[[Image:Google_maps_search.png]]
* right click on "Get URL of this page" and copy the URL
[[Image:Google_maps_url.png]]
* you should get something like that:
<pre>
http://maps.google.com/maps?f=q&hl=fr&geocode=&q=besan%C3%A7on&ie=UTF8&ll=47.257796,6.025314&spn=0.216236,0.601501&z=11&iwloc=addr
</pre>
* the data between ''&ll='' and ''&spn'' are the needed one (latitude/longitude)
* extract them and copy them in the "Edit" of this wiki page. Add it you wiki name and your town. For example:
<pre>
<googlemap lat="47" lon="6" width=640 height=480 zoom=4>
...
Others coordinates
...
47.257796, 6.025314, [[User:YourID|YourName]] - Your Town
</googlemap>
</pre>

[[Category:Association]]

MemberList

2013-04-26T10:10:46Z

JanosA: /* Here is the list of the (active) members and their skills */

==Here is the list of the (active) members and their skills==

This list is maintained by the users themself.

*0: Novice
*1: Notions. At least one successfull experiment
*2: Confirmed
<br>

{| border="1" cellpadding="5" cellspacing="0" summary="Signal connections"
|- style="background:#efefef;"
! '''Name / IRC Nickname''' || '''Linux Apps'''|| '''Linux Drivers'''|| '''FPGA''' || '''Board Design''' || '''Projet/Domain'''
|----------------
|[[User:Salocin68|Nicolas Colombain / Salocin]] || 1 || 1 || 1 || 2 || domotics
|----------------
|[[User:JulienB|Julien Boibessot / Artemys]] || 2 || 2 || 0 || 1 || multimedia
|----------------
|[[User:JeanBaptisteM|Jean-Baptiste Mayer / JiBee]] || 2 || 1 || 1 || 1 || robotics
|----------------
|[[User:NicolasA|Nicolas Aguirre]] || 2 || 0 || 1 || 1 || multimedia
|----------------
|[[User:BenoitC|Benoît Canet]] || 2 || 0 || 0 || 0 || multimedia
|----------------
|[[User:SonZerro|Sonzerro]] || 0 || 0 || 1 || 2 || domotics
|----------------
|[[User:HenriG|Henri Geist]] || 1 || 1 || 0 || 1 || robotics
|----------------
|[[User:BorredonB|Bernard Borredon]] || 2 || 1 || 0 || 1 || domotics
|----------------
|[[User:ThomasB|Thomas Bores]] || 2 || 0 || 0 || 1 || Entertainment
|----------------
|[[User:FabriceM|Fabrice Mousset / KroMignon]] || 1 || 1 || 2 || 1 || Domotics & multimedia
|----------------
|[[User:AmineH|Amine EL HEDADI]] || 2 || 2 || 0 || 0 || domotics & robotics
|----------------
|[[User:PhilippeM|Philippe Monteil]] || 2 || 0 || 0 || 0 || multimedia
|----------------
|[[User:CedricZ|Cédric Zmyj]] || 0 || 0 || 0 || 0 || domotics & robotics
|----------------
|[[User:JeanMichelN|Jean Michel Naimo / jeanmi12 ]] || 2 || 1 || 1 || 1 || Domotics & entertainment
|----------------
|[[User:OlivierC|Olivier Coutanceau]] || 1 || 0 || 0 || 0 || multimedia
|----------------
|[[User:ArnaudC|Arnaud COFFINET]] || 0 || 0 || 1 || 2 || multimedia & domotics
|----------------
|[[User:SylvainP|Sylvain PARRINO]] || 2 || 1 || 0 || 0 || robotics
|----------------
|[[User:AurelienH|Aurélien HIRON]] || 2 || 0 || 0 || 1 || robotics
|----------------
|[[User:GuillaumeT|Guillaume TRANNOY]] || 0 || 0 || 0 || 2 || domotics & robotics
|----------------
|[[User:JulienN|Julien NICOLAS / jujun]] || 2 || 1 || 0 || 1 || multimedia & network
|----------------
|[[User:StephaneF|Stéphane Falck]] || 0 || 0 || 0 || 0 || multimedia & robotics & domotics
|----------------
|[[User:GillesD|Gilles DUSSIN/ Sellig]] || 1 || 0 || 1 || 1 || robotics
|----------------
|[[User:MaximeL|Maxime Liron]] || 0 || 0 || 0 || 0 || domotics, robotics & multimedia
|----------------
|[[User:NicolasC|Nicolas CHARLERY/ realniko]] || 2 || 0 || 0 || 0 || electronic
|----------------
|[[User:BenoitJ|Benoit JESTER]] || 0 || 0 || 0 || 0 || robotics
|----------------
|[[User:FabienM|Fabien MARTEAU/ FabM]] || 1 || 2 || 1 || 1 || robotics,domotics
|----------------
|[[User:XavierA|Xavier AZNAR]] || 1 || 1 || 0 || 0 || environment, entertainment, domotic
|----------------
|[[User:AlbericA|Albéric AUBLANC / PoueT]] || 2 || 0 || 1 || 0 || domotics & multimedia, robotics, entertainment,
|----------------
|[[User:FredericB| Frédéric Blain / creber]] || 2 || 1 || 0 || 0 || system, domotics
|----------------
|[[User:JeanBaptisteMa| Jean-Baptiste Maillet]] || 2 || 1 || 0 || 0 || system
|----------------
|[[User:JeanFrancoisR| Jean-François Rousval]] || 2 || 1 || 0 || 1 ||
|----------------
|[[User:JulienPeeters| Julien Peeters]] || 2 || 1 || 0 || 0 || domotics, real-time, entertainment, network
|----------------
|[[User:YoannC| Yoann Congal / Alpheb]] || 0 || 0 || 0 || 1 || robotics
|----------------
|[[User:MatthieuT| Matthieu Texier / weeber]] || 1 || 0 || 1 || 0 || robotics, real-time
|----------------
|[[User:MartialG| Martial Guex]] || 2 || 1 || 1 || 2 || transceiver RF, real-time, wireless
|----------------
|[[User:NicolasL| Nicolas Lantz]] || 2 || 2 || 1 || 1 ||
|----------------
|[[User:GuillaumeD| Guillaume DELVIT]] || 1 || 1 || 1 || 1 || system, asynchronous CPU
|----------------
|[[User:BernardR|Bernard REMOND ]] || x || x || x || x ||
|----------------
|[[User:SamirH| Samir HAMNACHE]] || 0 || 0 || 0 || 1 || électronique
|----------------
|[[User:OlivierT|Olivier TARDIEU]] || 0 || 0 || 0 || 1 || électronique,robotics,domotics
|----------------
|[[User:ThibautR|Thibault Rétornaz]] || 1 || 1 || 1 || 0 || bio-med, électronique
|----------------
|[[User:FrancoisM|Francois Minaud]] || 1 || 1 || 1 || 0 || domotics, real-time, network
|----------------
|[[User:BrunoS|Bruno Suarez]] || 2 || 0 || 0 || 0 || électronique, Network
|----------------
|[[User:guillaumeDe|Guillaume Denis]] || 0 || 0 || 2 || 1 || Electronique numérique, FPGA
|----------------
|[[User:KevinP|Kévin PETIT]] || 1 || 0 || 1 || 1 || Multimedia
|----------------
|[[User:PierreBa|Pierre Baudemont / b4ud3]] || 2 || 0 || 1 || 0 || domotics, robotics
|----------------
|[[User:BrunoL|Bruno Landré]] || 0 || 0 || 0 || 0 || robotics
|----------------
|[[User:AntonioMB|Antonio Meléndez]] || 0 || 0 || 1 || 2 || domotics, robotics, eletcronics
|----------------
|[[User:MichelTe|Michel Le Mer]] || 0 || 0 || 2 || 2 || electronics, software
|----------------
|[[User:JulienBa|Julien Baley]] || 0 || 0 || 0 || 0 ||
|----------------
|[[User:FrankA|Frank ANJEAUX]] || 1 || 0 || 0 || 1 || software,robotics, domotics, electronics
|----------------
|[[User:JulienViaud|Julien viaud/polric]] || 2 || 0 || 1 || 1 ||
|----------------
|[[User:NicolasCa|Nicolas CARTIER]] || 1 || 1 || 0 || 2 || domotics & robotics
|----------------
|[[User:PierreAlexandreS|Pierre Alexandre SCHEMBRI]] || 2 || 1 || 2 || 2 || electronics, board design, embedded software, FPGA, robotics, low power
|----------------
|[[User:AlexG|Alex GONZALEZ]] || 2 || 2 || 0 || 1 || telecommunications, network & multimedia
|----------------
|[[User:JulienL|Julien Lefrique / apapi]] || 1 || 0 || 1 || 1 ||
|----------------
|[[User:PaoloB|Paolo Bernini / nihil84]] || 2 || 1 || 0 || 0 || robotics, real-time
|----------------
|[[User:MichielE|Michiel Ettema]] || 0 || 0 || 0 || 1 || telecommunications, networking
|----------------
|[[User:NicolasD|Nicolas Duclos]] || 2 || 1 || 0 || 0 || telecommunications, domotics and funs
|----------------
|[[User:SebastienP|Sebastien Philippe]] || 1 || 2 || 1 || 2 || electronics, board design, embedded linux
|----------------
|[[User:PaulM|Paul MONSINJON]] || 1 || 1 || 2 || 1 || robotics, fpga, embedded linux
|----------------
|[[User:OlivierR|Olivier REYNET]] || 1 || 0 || 0 || 0 || robotics, linux, networking
|----------------
|[[User:HugoP|Hugo Petit]] || 0 || 0 || 1 || 2 || electronics, automotive, board design, embedded software
|----------------
|[[User:PhilippeL|Philippe Leduc]] || 1 || 0 || 1 || 1 || robotics, real-time, embedded software, domotic
|----------------
|[[User:PierreDe|Pierre Delarboulas]] || 1 || 1 || 0 || 0 || robotics, domotic
|----------------
|[[User:WilliamB|William Benharbone]] || 0 || 0 || 1 || 1 || electronics, board design and funs
|----------------
|[[User:JeanJacquesP|JeanJacques Pitrolle]] || 2 || 1 || 0 || 0 || embedded software, robotics
|----------------
|[[User:SebastienVC|Sébastien Van Cauwenberghe]] || 2 || 2 || 2 || 0 || Power Electronics, Embedded Systems, FPGA's
|----------------
|[[User:PhilBB|Phil Bergeron-Burns]] || 0 || 0 || 2 || 0 || bio-medical
|----------------
|[[User:JaumeF|Jaume Figueras i Jové]] || 0 || 0 || 2 || 0 || academic, mapping
|----------------
|[[User:MathieuB|Mathieu Boucher]] || 1 || 2 || 1 || 0 ||
|----------------
|[[User:SamuelM|Samuel Martin / smartin]] || 2 || 0 || 1 || 1 || embedded systems, real-time, robotics, multimedia
|----------------
|[[User:GaelV|Gaël Vanderbruggen]] || 1 || 0 || 0 || 0 || bio-medical, robotics, multimedia
|----------------
|[[User:JeanMarcM| pieddemamouth/Jean-Marc Montanier]] || 1 || 0 || 0 || 1 || robotics
|----------------
|[[User:ChaoyiH| Chaoyi HU]] || 1 || 0 || 0 || 2 || entertainement, telecommunications, electronic
|----------------
|[[User:FrancoisG| Francois Goudal / Fanfwe]] || 2 || 2 || 1 || 1 || robotics, telecommunications
|----------------
|[[User:PhilippeLe| Philippe Le Rhun]] || 1 || 0 || 0 || 2 || entertainement, robotics, domotic
|----------------
|[[User:JeremieG| Jeremie Girouard]] || 0 || 0 || 0 || 0 || expérimentations,learning, Embedded Systems
|----------------
|[[User:RafalK| Rafal Kapela]] || 2 || 0 || 2 || 0 || Multimedia, real-time video content processing
|----------------
|[[User:XavierB| Xavier Bruhière]] || 1 || 1 || 1 || 1 || Robotics, domotic, learning
|----------------
||[[User:HerveDa| Dang Hervé]] || 0 || 0 || 0 || 0 || Robotics, aeronautics...
|----------------
||[[User:SergioB| Sergio Borghese]] || 2 || 1 || 0 || 0 || Networking, cryptography, embedded
|----------------
||[[User:KennethM| Ken Cracraft]] || 2 || 1 || 2 || 0 || embedded systems, FPGA, telecommunications, linux, networking
|----------------
||[[User:DimitriL| Dimitri Labouesse]] || 0 || 0 || 0 || 0 || domotics
|----------------
||[[User:VincentC| Vincent Cagnard]] || 2 || 1 || 0 || 1 || robotics, multimedia, aeronautics
|----------------
||[[User:SouleB| Soule Ba]] || 2 || 0 || 1 || 0||
|----------------
||[[User:VascoB| Vasco Baptista]] || 0 || 1 || 0 || 2 || domotics, electronics, IEEE802.15.4, PCB design
|----------------
||[[User:JanosA| Janos Angeli]] || 1 || 1 || 0 || 1 || home automation, serial communications, networking
|}

==Links==
* [[Members | Geographical position of the members]]

[[Category:Association]]

User:JanosA

2013-02-25T19:06:33Z

JanosA: /* Skills */

User:JanosA

2013-02-25T19:04:26Z

JanosA: New page: I am IP Network and Datacenter engineer, currently I'm working for an Internet Service Provider in Hungary. My hobby is programming embedded systems and creating my own small electronic b...