http://www.armadeus.org/wiki/api.php?action=feedcontributions&feedformat=atom&user=Salocin68 ArmadeusWiki - User contributions [en] 2026-04-29T17:08:46Z User contributions MediaWiki 1.26.3 http://www.armadeus.org/wiki/index.php?title=OPOS6UL_NANO&diff=14418 OPOS6UL NANO 2017-08-08T07:24:17Z <p>Salocin68: Created page with &quot;Category: OPOS6UL_NANO ==Description== File:OPOS6UL_NANO.png The OPOS6UL_NANO is a [https://en.wikipedia.org/wiki/Single-board_computer Single Board Computer]. Her...&quot;</p> <hr /> <div>[[Category: OPOS6UL_NANO]]<br /> ==Description==<br /> <br /> [[File:OPOS6UL_NANO.png]]<br /> <br /> <br /> The OPOS6UL_NANO is a [https://en.wikipedia.org/wiki/Single-board_computer Single Board Computer].<br /> <br /> Here is a list of the main features:<br /> * Processor: [http://www.nxp.com/products/microcontrollers-and-processors/arm-processors/i.mx-applications-processors/i.mx-6-processors/i.mx6qp/i.mx-6ultralite-processor-low-power-secure-arm-cortex-a7-core:i.MX6UL i.MX6UL] (i.MX6UL single A7 @ 538MHz, 696MHz in option)<br /> * RAM: DDR3 800Mbps. Default capacity is 256Mbytes.<br /> * Flash: [[EMMC OPOS6UL|eMMC]] 4GBytes to 32GBytes (default 4GB), 8 bits data bus.<br /> * Ethernet: onboard Physical (ready to use Ethernet 10/100Mbit link)<br /> * USB: High speed USB OTG (OnTheGo), software only<br /> * USB: High speed Host<br /> * TFT CMOS interface<br /> * Wi-Fi (option): b/g/n with u.FL antenna<br /> * Bluetooth (option): BT 4.1 (Low Energy compatible)<br /> * Only one external supply of 3.3V required.<br /> * Mechanical dimensions: 37 x 22 mm<br /> * Connector: NGFF (M.2) 67pts<br /> <br /> ==Resources==<br /> <br /> * [[Datasheet#OPOS6UL_NANO | Datasheet and schematics]]<br /> <br /> ==Workaround==<br /> * When you get that kind of error at Wi-Fi initialisation:<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> brcmfmac: brcmf_sdio_htclk: HT Avail timeout (1000000): clkctl 0x50<br /> &lt;/pre&gt;<br /> * You can try to unload/reload the driver:<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # modprobe -r brcmfmac<br /> # modprobe brcmfmac<br /> [ 1881.792273] brcmfmac: brcmf_c_preinit_dcmds: Firmware version = wl0: Aug 29 2016 20:48:16 version 7.45.41.26 (r640327) FWID 01-4527cfab<br /> [ 1881.850588] brcmfmac: brcmf_cfg80211_reg_notifier: not a ISO3166 code (0x30 0x30)<br /> &lt;/pre&gt;<br /> <br /> ==Feature list==<br /> * [[OPOS6UL_NANO Linux kernel status]]<br /> <br /> {| border=&quot;0&quot; cellpadding=&quot;5&quot; cellspacing=&quot;5&quot; summary=&quot;Hardware Add-Ons by functionnalities&quot;<br /> |----------------<br /> |- style=&quot;background:#f4f4f4; color:black; -moz-border-radius:18px;&quot;<br /> |<br /> ===Video===<br /> ====Video Out====<br /> * [[LCD]]<br /> * [[FrameBuffer]]<br /> <br /> ====Video In====<br /> *[[Camera interface]]<br /> <br /> ||<br /> <br /> ===Wired communication===<br /> * [[Uart|UART]]<br /> * [[SPI]]<br /> * [[I2C]]<br /> * [[USB_Host]]<br /> * [[USB_Gadget]]<br /> * [[USB_OTG]]<br /> * [[CAN_bus_Linux_driver|CAN bus]]<br /> <br /> ||<br /> <br /> ===Wireless communication===<br /> * [[Wifi|Wi-Fi usage on Linux]]<br /> * [[Bluetooth|Bluetooth usage on Linux]]<br /> <br /> ===Storage===<br /> <br /> * [[EMMC OPOS6UL|eMMC]]<br /> <br /> ===Other===<br /> * [[PWM]]<br /> * [[GPIOlib]]<br /> * [[Linux_Dynamic_Frequency_Scaling|Frequency scaling]]<br /> |}<br /> <br /> ==Development boards==<br /> * [[OPOS6ULDev]]<br /> <br /> [[Category:MainBoards]]<br /> [[Category:Hardware]]</div> Salocin68 http://www.armadeus.org/wiki/index.php?title=Hardware&diff=14417 Hardware 2017-08-08T07:20:08Z <p>Salocin68: /* Main Boards (APFxx and OPOSxx modules) */</p> <hr /> <div>==Armadeus Boards==<br /> The following boards are developed by [http://www.armadeus.com Armadeus Systems].&lt;br&gt; Members of the Armadeus Project association can purchase these products at discount prices. Take a look at the [[Association]] page for details.<br /> <br /> {| border=&quot;0&quot; cellpadding=&quot;5&quot; cellspacing=&quot;5&quot; summary=&quot;Hardware Add-Ons by functionnalities&quot;<br /> |----------------<br /> |- style=&quot;background:#f4f4f4; color:black; -moz-border-radius:18px;&quot;<br /> | width=&quot;50%&quot; |<br /> === Main Boards (APFxx and OPOSxx modules)===<br /> * [[APF9328]]: i.MXL based module<br /> * [[APF27]]: i.MX27 based module<br /> * [[APF51]]: i.MX51 based module<br /> * [[APF28]]: i.MX28 based module<br /> * [[APF6]]: i.MX6 based module<br /> * [[APF6_SP]] : i.MX6 based module with CycloneV FPGA<br /> * [[OPOS6UL]] : i.MX6UL based module<br /> * [[OPOS6UL_NANO]] : i.MX6UL based nano module<br /> * [[Footprints]] : Footprint available for APFxx module<br /> ||<br /> <br /> === Baseboards ===<br /> * [[OPOS6ULDev]]: full featured development board for the [[OPOS6UL]]<br /> * [[APF6Dev]]: full featured development board for the APF6<br /> * [[APF28Dev]]: full featured development board for the APF28<br /> * [[APF51Dev]]: full featured development board for the APF51<br /> * [[APF27Dev]]: full featured development board for the APF27 (with several options)<br /> * [[APF27 PPS]]/PPS: network applications development board for the APF27<br /> * [[PPS51]]: network applications development board for the APF51<br /> * No more available:<br /> ** [[APF9328DevLight]]: low cost development board for the APF9328<br /> ** [[APF9328DevFull]]: full featured development board for the APF9328<br /> |----------------<br /> |- style=&quot;background:#f4f4f4; color:black; -moz-border-radius:18px;&quot;<br /> | width=&quot;50%&quot; |<br /> <br /> === Extension Boards ===<br /> * [[Chimei_LW700|LW700AT_Adapt]]: Adapter for the Chimei LW700 TFT LCD<br /> * [[Wireless_extension_board|APW wireless board]]: Add WiFi &amp; Bluetooth &amp; GPS &amp; GSM to your [[APF27Dev]]<br /> * [[SP_VISION]]: Extension with Spartan6 FPGA, for video processing<br /> * No more available:<br /> ** [[LQ043_Adapt]]: Adapter for the Sharp LQ043 TFT LCD<br /> ** [[MTF-T035|MTF-T035_Adapt]]: Adapter for the Microtips MTF-T035 TFT LCD<br /> <br /> ||<br /> <br /> === Demo Boards ===<br /> * [[HMS Demo]]: industrial demo platform<br /> |}<br /> <br /> ==Tools==<br /> * [http://kicad-pcb.org/ Kicad EDA tool]</div> Salocin68 http://www.armadeus.org/wiki/index.php?title=Datasheet&diff=14076 Datasheet 2016-09-22T10:08:19Z <p>Salocin68: /* OPOS6UL_Dev */</p> <hr /> <div>= Armadeus datasheets and schemas =<br /> <br /> To see all documentation available for the board clic on the title.<br /> <br /> == [http://www.armadeus.com/_downloads/apf9328/ APF9328] ==<br /> * [http://www.armadeus.com/_downloads/apf9328/documentation/dataSheet_APF9328.pdf Datasheet]<br /> * [http://www.armadeus.com/_downloads/apf9328/hardware/apf_schema.pdf Schema]<br /> <br /> == [http://www.armadeus.com/_downloads/apf9328DevLight/ APF9328Devlight] ==<br /> * Datasheet [http://www.armadeus.com/_downloads/apf9328DevLight/documentation/dataSheet_APF9328_DevLight.pdf V1] [http://www.armadeus.com/_downloads/apf9328DevLight/documentation/dataSheet_APF9328_DevLight_V2.pdf V2]<br /> * Schemas [http://www.armadeus.com/_downloads/apf9328DevLight/hardware/dev_light_schema_v1.2.pdf V1.2] [http://www.armadeus.com/_downloads/apf9328DevLight/hardware/dev_light_schema.pdf V2]<br /> <br /> == [http://www.armadeus.com/_downloads/apf9328DevFull/ APF9328DevFull] ==<br /> * [http://www.armadeus.com/_downloads/apf9328DevFull/documentation/DataSheet_APF9328_DevFull.pdf Datasheet]<br /> * [http://www.armadeus.com/_downloads/apf9328DevFull/hardware/apf9328_dev_schematics_v1_1.pdf Schema]<br /> <br /> == [http://www.armadeus.com/_downloads/apf27/ APF27] ==<br /> * [http://www.armadeus.com/_downloads/apf27/documentation/datasheet_apf27.pdf Datasheet]<br /> * [http://www.armadeus.com/_downloads/apf27/hardware/apf27_V1.2.pdf Schema]<br /> <br /> == [http://www.armadeus.com/_downloads/apf27Dev/ APF27Dev] ==<br /> * [http://www.armadeus.com/_downloads/apf27Dev/documentation/dataSheet_APF27Dev.pdf Datasheet]<br /> * [http://www.armadeus.com/_downloads/apf27Dev/hardware/apf27_devfull_12.pdf Schema]<br /> <br /> == [http://www.armadeus.com/_downloads/apf27_PPS/ PPS (APF27)] ==<br /> * [http://www.armadeus.com/_downloads/apf27_PPS/documentation/datasheet_pps.pdf Datasheet]<br /> * [http://www.armadeus.com/_downloads/apf27_PPS/hardware/pps_v11.pdf Schema]<br /> <br /> == [http://www.armadeus.com/_downloads/apf28/ APF28] ==<br /> * [http://www.armadeus.com/_downloads/apf28/documentation/datasheet_apf28.pdf Datasheet]<br /> * [http://www.armadeus.com/_downloads/apf28/hardware/apf28_v10.pdf Schema]<br /> <br /> == [http://www.armadeus.com/_downloads/apf28_Dev/ APF28_DEV] ==<br /> * [http://www.armadeus.com/_downloads/apf28_Dev/documentation/dataSheet_APF28Dev.pdf Datasheet]<br /> * [http://www.armadeus.com/_downloads/apf28_Dev/hardware/apf28_dev_V10.pdf Schema]<br /> <br /> == [http://www.armadeus.com/_downloads/apf51/ APF51] ==<br /> * Datasheet<br /> ** [http://www.armadeus.com/_downloads/apf51/documentation/datasheet_apf51_V1.pdf APF51_V1]<br /> ** [http://www.armadeus.com/_downloads/apf51/documentation/datasheet_apf51_V2.pdf APF51_V2]<br /> * [http://www.armadeus.com/_downloads/apf51/hardware/apf51_v10.pdf Schema]<br /> <br /> == [http://www.armadeus.com/_downloads/apf51_Dev/ APF51Dev] ==<br /> * [http://www.armadeus.com/_downloads/apf51_Dev/documentation/dataSheet_APF51Dev.pdf Datasheet]<br /> * [http://www.armadeus.com/_downloads/apf51_Dev/hardware/apf51_dev_V12.pdf Schema]<br /> <br /> == [http://www.armadeus.com/_downloads/apf6/ APF6] ==<br /> * [http://www.armadeus.com/_downloads/apf6/documentation/datasheet_apf6.pdf Datasheet]<br /> <br /> == [http://www.armadeus.com/_downloads/apf6Dev/ APF6Dev] ==<br /> * [http://www.armadeus.com/_downloads/apf6Dev/documentation/dataSheet_APF6_Dev.pdf Datasheet]<br /> * [http://www.armadeus.com/_downloads/apf6Dev/hardware/apf6_dev_V2.pdf Schematics]<br /> <br /> == [http://www.armadeus.com/_downloads/apf6_SP/ APF6_SP] ==<br /> * [http://www.armadeus.com/_downloads/apf6_SP/documentation/datasheet_apf6SP.pdf Datasheet]<br /> <br /> == [http://www.armadeus.com/_downloads/opos6ul/ OPOS6UL] ==<br /> * [http://www.armadeus.com/_downloads/opos6ul/documentation/datasheet_opos6ul.pdf Datasheet]<br /> <br /> == [http://www.armadeus.com/_downloads/opos6ul_dev/ OPOS6UL_Dev] ==<br /> * [http://www.armadeus.com/_downloads/opos6ul_dev/documentation/datasheet_opos6ul_Dev.pdf Datasheet]<br /> * [http://www.armadeus.com/_downloads/opos6ul_dev/hardware/opos6UL_dev_V12.pdf Schema]<br /> <br /> == [http://www.armadeus.com/_downloads/sp6_vision/ SP_VISION] ==<br /> * [http://www.armadeus.com/_downloads/sp6_vision/datasheet_sp_vision.pdf Datasheet]<br /> * [http://www.armadeus.com/_downloads/sp6_vision/hardware/sp_vision_eval_board_V05.pdf Schema]<br /> <br /> == [http://www.armadeus.com/_downloads/lw700at_adapt/ LW700] ==<br /> * [http://www.armadeus.com/_downloads/lw700at_adapt/documentation/datasheet_lw700at_adapt.pdf Datasheet]<br /> * [http://www.armadeus.com/_downloads/lw700at_adapt/hardware/LW700AT_adapt_v0B.pdf Schema]<br /> <br /> == [http://www.armadeus.com/_downloads/apw/ APW] ==<br /> * [http://www.armadeus.com/_downloads/apw/documentation/datasheet_APW.pdf Datasheet]<br /> * [http://www.armadeus.com/_downloads/apw/hardware/apf27_wireless_V0C.pdf Schema]<br /> <br /> == [http://www.armadeus.com/_downloads/lcd_adapt_LQ043 LQ043] ==<br /> * [http://www.armadeus.com/_downloads/lcd_adapt_LQ043/documentation/datasheet_lq043_adapt.pdf Datasheet]<br /> * [http://www.armadeus.com/_downloads/lcd_adapt_LQ043/hardware/lq043_adapt_schematics_v0a.pdf Schema]<br /> <br /> = HMS Demo =<br /> * Datasheet<br /> * Schema</div> Salocin68 http://www.armadeus.org/wiki/index.php?title=Datasheet&diff=14075 Datasheet 2016-09-22T10:06:51Z <p>Salocin68: /* OPOS6UL_Dev */</p> <hr /> <div>= Armadeus datasheets and schemas =<br /> <br /> To see all documentation available for the board clic on the title.<br /> <br /> == [http://www.armadeus.com/_downloads/apf9328/ APF9328] ==<br /> * [http://www.armadeus.com/_downloads/apf9328/documentation/dataSheet_APF9328.pdf Datasheet]<br /> * [http://www.armadeus.com/_downloads/apf9328/hardware/apf_schema.pdf Schema]<br /> <br /> == [http://www.armadeus.com/_downloads/apf9328DevLight/ APF9328Devlight] ==<br /> * Datasheet [http://www.armadeus.com/_downloads/apf9328DevLight/documentation/dataSheet_APF9328_DevLight.pdf V1] [http://www.armadeus.com/_downloads/apf9328DevLight/documentation/dataSheet_APF9328_DevLight_V2.pdf V2]<br /> * Schemas [http://www.armadeus.com/_downloads/apf9328DevLight/hardware/dev_light_schema_v1.2.pdf V1.2] [http://www.armadeus.com/_downloads/apf9328DevLight/hardware/dev_light_schema.pdf V2]<br /> <br /> == [http://www.armadeus.com/_downloads/apf9328DevFull/ APF9328DevFull] ==<br /> * [http://www.armadeus.com/_downloads/apf9328DevFull/documentation/DataSheet_APF9328_DevFull.pdf Datasheet]<br /> * [http://www.armadeus.com/_downloads/apf9328DevFull/hardware/apf9328_dev_schematics_v1_1.pdf Schema]<br /> <br /> == [http://www.armadeus.com/_downloads/apf27/ APF27] ==<br /> * [http://www.armadeus.com/_downloads/apf27/documentation/datasheet_apf27.pdf Datasheet]<br /> * [http://www.armadeus.com/_downloads/apf27/hardware/apf27_V1.2.pdf Schema]<br /> <br /> == [http://www.armadeus.com/_downloads/apf27Dev/ APF27Dev] ==<br /> * [http://www.armadeus.com/_downloads/apf27Dev/documentation/dataSheet_APF27Dev.pdf Datasheet]<br /> * [http://www.armadeus.com/_downloads/apf27Dev/hardware/apf27_devfull_12.pdf Schema]<br /> <br /> == [http://www.armadeus.com/_downloads/apf27_PPS/ PPS (APF27)] ==<br /> * [http://www.armadeus.com/_downloads/apf27_PPS/documentation/datasheet_pps.pdf Datasheet]<br /> * [http://www.armadeus.com/_downloads/apf27_PPS/hardware/pps_v11.pdf Schema]<br /> <br /> == [http://www.armadeus.com/_downloads/apf28/ APF28] ==<br /> * [http://www.armadeus.com/_downloads/apf28/documentation/datasheet_apf28.pdf Datasheet]<br /> * [http://www.armadeus.com/_downloads/apf28/hardware/apf28_v10.pdf Schema]<br /> <br /> == [http://www.armadeus.com/_downloads/apf28_Dev/ APF28_DEV] ==<br /> * [http://www.armadeus.com/_downloads/apf28_Dev/documentation/dataSheet_APF28Dev.pdf Datasheet]<br /> * [http://www.armadeus.com/_downloads/apf28_Dev/hardware/apf28_dev_V10.pdf Schema]<br /> <br /> == [http://www.armadeus.com/_downloads/apf51/ APF51] ==<br /> * Datasheet<br /> ** [http://www.armadeus.com/_downloads/apf51/documentation/datasheet_apf51_V1.pdf APF51_V1]<br /> ** [http://www.armadeus.com/_downloads/apf51/documentation/datasheet_apf51_V2.pdf APF51_V2]<br /> * [http://www.armadeus.com/_downloads/apf51/hardware/apf51_v10.pdf Schema]<br /> <br /> == [http://www.armadeus.com/_downloads/apf51_Dev/ APF51Dev] ==<br /> * [http://www.armadeus.com/_downloads/apf51_Dev/documentation/dataSheet_APF51Dev.pdf Datasheet]<br /> * [http://www.armadeus.com/_downloads/apf51_Dev/hardware/apf51_dev_V12.pdf Schema]<br /> <br /> == [http://www.armadeus.com/_downloads/apf6/ APF6] ==<br /> * [http://www.armadeus.com/_downloads/apf6/documentation/datasheet_apf6.pdf Datasheet]<br /> <br /> == [http://www.armadeus.com/_downloads/apf6Dev/ APF6Dev] ==<br /> * [http://www.armadeus.com/_downloads/apf6Dev/documentation/dataSheet_APF6_Dev.pdf Datasheet]<br /> * [http://www.armadeus.com/_downloads/apf6Dev/hardware/apf6_dev_V2.pdf Schematics]<br /> <br /> == [http://www.armadeus.com/_downloads/apf6_SP/ APF6_SP] ==<br /> * [http://www.armadeus.com/_downloads/apf6_SP/documentation/datasheet_apf6SP.pdf Datasheet]<br /> <br /> == [http://www.armadeus.com/_downloads/opos6ul/ OPOS6UL] ==<br /> * [http://www.armadeus.com/_downloads/opos6ul/documentation/datasheet_opos6ul.pdf Datasheet]<br /> <br /> == [http://www.armadeus.com/_downloads/opos6ul_dev/ OPOS6UL_Dev] ==<br /> * [http://www.armadeus.com/_downloads/opos6ul_dev/documentation/dataSheet_opos6ul_Dev.pdf Datasheet]<br /> * [http://www.armadeus.com/_downloads/opos6ul_dev/hardware/opos6UL_Dev_V12.pdf Schema]<br /> <br /> == [http://www.armadeus.com/_downloads/sp6_vision/ SP_VISION] ==<br /> * [http://www.armadeus.com/_downloads/sp6_vision/datasheet_sp_vision.pdf Datasheet]<br /> * [http://www.armadeus.com/_downloads/sp6_vision/hardware/sp_vision_eval_board_V05.pdf Schema]<br /> <br /> == [http://www.armadeus.com/_downloads/lw700at_adapt/ LW700] ==<br /> * [http://www.armadeus.com/_downloads/lw700at_adapt/documentation/datasheet_lw700at_adapt.pdf Datasheet]<br /> * [http://www.armadeus.com/_downloads/lw700at_adapt/hardware/LW700AT_adapt_v0B.pdf Schema]<br /> <br /> == [http://www.armadeus.com/_downloads/apw/ APW] ==<br /> * [http://www.armadeus.com/_downloads/apw/documentation/datasheet_APW.pdf Datasheet]<br /> * [http://www.armadeus.com/_downloads/apw/hardware/apf27_wireless_V0C.pdf Schema]<br /> <br /> == [http://www.armadeus.com/_downloads/lcd_adapt_LQ043 LQ043] ==<br /> * [http://www.armadeus.com/_downloads/lcd_adapt_LQ043/documentation/datasheet_lq043_adapt.pdf Datasheet]<br /> * [http://www.armadeus.com/_downloads/lcd_adapt_LQ043/hardware/lq043_adapt_schematics_v0a.pdf Schema]<br /> <br /> = HMS Demo =<br /> * Datasheet<br /> * Schema</div> Salocin68 http://www.armadeus.org/wiki/index.php?title=Datasheet&diff=14074 Datasheet 2016-09-22T10:06:32Z <p>Salocin68: /* OPOS6UL */</p> <hr /> <div>= Armadeus datasheets and schemas =<br /> <br /> To see all documentation available for the board clic on the title.<br /> <br /> == [http://www.armadeus.com/_downloads/apf9328/ APF9328] ==<br /> * [http://www.armadeus.com/_downloads/apf9328/documentation/dataSheet_APF9328.pdf Datasheet]<br /> * [http://www.armadeus.com/_downloads/apf9328/hardware/apf_schema.pdf Schema]<br /> <br /> == [http://www.armadeus.com/_downloads/apf9328DevLight/ APF9328Devlight] ==<br /> * Datasheet [http://www.armadeus.com/_downloads/apf9328DevLight/documentation/dataSheet_APF9328_DevLight.pdf V1] [http://www.armadeus.com/_downloads/apf9328DevLight/documentation/dataSheet_APF9328_DevLight_V2.pdf V2]<br /> * Schemas [http://www.armadeus.com/_downloads/apf9328DevLight/hardware/dev_light_schema_v1.2.pdf V1.2] [http://www.armadeus.com/_downloads/apf9328DevLight/hardware/dev_light_schema.pdf V2]<br /> <br /> == [http://www.armadeus.com/_downloads/apf9328DevFull/ APF9328DevFull] ==<br /> * [http://www.armadeus.com/_downloads/apf9328DevFull/documentation/DataSheet_APF9328_DevFull.pdf Datasheet]<br /> * [http://www.armadeus.com/_downloads/apf9328DevFull/hardware/apf9328_dev_schematics_v1_1.pdf Schema]<br /> <br /> == [http://www.armadeus.com/_downloads/apf27/ APF27] ==<br /> * [http://www.armadeus.com/_downloads/apf27/documentation/datasheet_apf27.pdf Datasheet]<br /> * [http://www.armadeus.com/_downloads/apf27/hardware/apf27_V1.2.pdf Schema]<br /> <br /> == [http://www.armadeus.com/_downloads/apf27Dev/ APF27Dev] ==<br /> * [http://www.armadeus.com/_downloads/apf27Dev/documentation/dataSheet_APF27Dev.pdf Datasheet]<br /> * [http://www.armadeus.com/_downloads/apf27Dev/hardware/apf27_devfull_12.pdf Schema]<br /> <br /> == [http://www.armadeus.com/_downloads/apf27_PPS/ PPS (APF27)] ==<br /> * [http://www.armadeus.com/_downloads/apf27_PPS/documentation/datasheet_pps.pdf Datasheet]<br /> * [http://www.armadeus.com/_downloads/apf27_PPS/hardware/pps_v11.pdf Schema]<br /> <br /> == [http://www.armadeus.com/_downloads/apf28/ APF28] ==<br /> * [http://www.armadeus.com/_downloads/apf28/documentation/datasheet_apf28.pdf Datasheet]<br /> * [http://www.armadeus.com/_downloads/apf28/hardware/apf28_v10.pdf Schema]<br /> <br /> == [http://www.armadeus.com/_downloads/apf28_Dev/ APF28_DEV] ==<br /> * [http://www.armadeus.com/_downloads/apf28_Dev/documentation/dataSheet_APF28Dev.pdf Datasheet]<br /> * [http://www.armadeus.com/_downloads/apf28_Dev/hardware/apf28_dev_V10.pdf Schema]<br /> <br /> == [http://www.armadeus.com/_downloads/apf51/ APF51] ==<br /> * Datasheet<br /> ** [http://www.armadeus.com/_downloads/apf51/documentation/datasheet_apf51_V1.pdf APF51_V1]<br /> ** [http://www.armadeus.com/_downloads/apf51/documentation/datasheet_apf51_V2.pdf APF51_V2]<br /> * [http://www.armadeus.com/_downloads/apf51/hardware/apf51_v10.pdf Schema]<br /> <br /> == [http://www.armadeus.com/_downloads/apf51_Dev/ APF51Dev] ==<br /> * [http://www.armadeus.com/_downloads/apf51_Dev/documentation/dataSheet_APF51Dev.pdf Datasheet]<br /> * [http://www.armadeus.com/_downloads/apf51_Dev/hardware/apf51_dev_V12.pdf Schema]<br /> <br /> == [http://www.armadeus.com/_downloads/apf6/ APF6] ==<br /> * [http://www.armadeus.com/_downloads/apf6/documentation/datasheet_apf6.pdf Datasheet]<br /> <br /> == [http://www.armadeus.com/_downloads/apf6Dev/ APF6Dev] ==<br /> * [http://www.armadeus.com/_downloads/apf6Dev/documentation/dataSheet_APF6_Dev.pdf Datasheet]<br /> * [http://www.armadeus.com/_downloads/apf6Dev/hardware/apf6_dev_V2.pdf Schematics]<br /> <br /> == [http://www.armadeus.com/_downloads/apf6_SP/ APF6_SP] ==<br /> * [http://www.armadeus.com/_downloads/apf6_SP/documentation/datasheet_apf6SP.pdf Datasheet]<br /> <br /> == [http://www.armadeus.com/_downloads/opos6ul/ OPOS6UL] ==<br /> * [http://www.armadeus.com/_downloads/opos6ul/documentation/datasheet_opos6ul.pdf Datasheet]<br /> <br /> == [http://www.armadeus.com/_downloads/opos6ul_Dev/ OPOS6UL_Dev] ==<br /> * [http://www.armadeus.com/_downloads/opos6ul_Dev/documentation/dataSheet_opos6ul_Dev.pdf Datasheet]<br /> * [http://www.armadeus.com/_downloads/opos6ul_Dev/hardware/opos6UL_Dev_V12.pdf Schema]<br /> <br /> == [http://www.armadeus.com/_downloads/sp6_vision/ SP_VISION] ==<br /> * [http://www.armadeus.com/_downloads/sp6_vision/datasheet_sp_vision.pdf Datasheet]<br /> * [http://www.armadeus.com/_downloads/sp6_vision/hardware/sp_vision_eval_board_V05.pdf Schema]<br /> <br /> == [http://www.armadeus.com/_downloads/lw700at_adapt/ LW700] ==<br /> * [http://www.armadeus.com/_downloads/lw700at_adapt/documentation/datasheet_lw700at_adapt.pdf Datasheet]<br /> * [http://www.armadeus.com/_downloads/lw700at_adapt/hardware/LW700AT_adapt_v0B.pdf Schema]<br /> <br /> == [http://www.armadeus.com/_downloads/apw/ APW] ==<br /> * [http://www.armadeus.com/_downloads/apw/documentation/datasheet_APW.pdf Datasheet]<br /> * [http://www.armadeus.com/_downloads/apw/hardware/apf27_wireless_V0C.pdf Schema]<br /> <br /> == [http://www.armadeus.com/_downloads/lcd_adapt_LQ043 LQ043] ==<br /> * [http://www.armadeus.com/_downloads/lcd_adapt_LQ043/documentation/datasheet_lq043_adapt.pdf Datasheet]<br /> * [http://www.armadeus.com/_downloads/lcd_adapt_LQ043/hardware/lq043_adapt_schematics_v0a.pdf Schema]<br /> <br /> = HMS Demo =<br /> * Datasheet<br /> * Schema</div> Salocin68 http://www.armadeus.org/wiki/index.php?title=OPOS6ULDev&diff=14073 OPOS6ULDev 2016-09-22T09:58:43Z <p>Salocin68: /* Feature list */</p> <hr /> <div>[[Category: OPOS6UL]]<br /> <br /> ==Description==<br /> This is the Armadeus System's standard development board/baseboard for the [[OPOS6UL]] module.<br /> <br /> [[Image:OPOS6UL_Dev.png]]<br /> <br /> ==Errata==<br /> <br /> ==Resources==<br /> <br /> * [[Datasheet#APF6Dev | Datasheet and schematics]]<br /> * [http://www.armadeus.com/english/products-development_boards-apf6_dev.html Product page on Armadeus Systems website]<br /> <br /> ==Feature list==<br /> <br /> {| border=&quot;0&quot; cellpadding=&quot;5&quot; cellspacing=&quot;5&quot; summary=&quot;Hardware Add-Ons by functionnalities&quot;<br /> |----------------<br /> |- style=&quot;background:#f4f4f4; color:black; -moz-border-radius:18px;&quot;<br /> |<br /> <br /> ===Audio===<br /> * [[S/PDIF]]: audio in/out<br /> * [[ALSA]]<br /> <br /> ===Video Out===<br /> * [[LCD]]<br /> * [[BackLight]]<br /> * [[FrameBuffer]]<br /> <br /> ===Video In===<br /> *[[Camera interface]]<br /> ||<br /> ===User Input===<br /> * [[Tslib|Touchscreen]]<br /> <br /> ===Wired communication===<br /> * [[Uart|UART]]<br /> * [[SPI]]<br /> * [[I2C]]<br /> * [[USB Host]] <br /> * [[USB_OTG]]<br /> * [[USB_Gadget]]<br /> * [[CAN_bus_Linux_driver|CAN bus]]<br /> <br /> ===Storage===<br /> * [[MultiMediaCard]]<br /> ||<br /> <br /> ===Wireless communication===<br /> * [[Wifi|Wi-Fi usage on Linux]]<br /> * [[Bluetooth|Bluetooth usage on Linux]]<br /> <br /> ===Other===<br /> * [[GPIOlib]]<br /> * [[JTAG]]<br /> <br /> |}<br /> <br /> ==Connectors==<br /> * RPi compatible connector:<br /> {| class=&quot;wikitable&quot; border=&quot;1&quot; cellpadding=&quot;5&quot; summary=&quot;RPi compatible connector of OPOS6ULDev&quot;<br /> |- style=&quot;background:#efefef;&quot;<br /> ! Function !! Function !! Function !! RPi name !! Function !! JX Pin !! JX Pin !! Function !! RPi name !! Function !! Function !! Function<br /> |-<br /> | || || || || 3.3V || style=&quot;color:yellow;background:black;&quot; align=center | '''1''' || style=&quot;color:yellow;background:black;&quot; align=center | '''2''' || 5V || || || || <br /> |-<br /> | || || || SDA1 || I2C data|| style=&quot;color:yellow;background:black;&quot; align=center | '''3''' || style=&quot;color:yellow;background:black;&quot; align=center | '''4''' || 5V || || || || <br /> |-<br /> | || || || SCL1 || I2C clock || style=&quot;color:yellow;background:black;&quot; align=center | '''5''' || style=&quot;color:yellow;background:black;&quot; align=center | '''6''' || GND || || || || <br /> |-<br /> | || || || GPIO7 || GPIO|| style=&quot;color:yellow;background:black;&quot; align=center | '''7''' || style=&quot;color:yellow;background:black;&quot; align=center | '''8''' || UART Tx || TxD || || || <br /> |-<br /> | || || || || GND|| style=&quot;color:yellow;background:black;&quot; align=center | '''9''' || style=&quot;color:yellow;background:black;&quot; align=center | '''10''' || UART Rx || RxD || || || <br /> |-<br /> | || || || GPIO0 || GPIO || style=&quot;color:yellow;background:black;&quot; align=center | '''11''' || style=&quot;color:yellow;background:black;&quot; align=center | '''12''' || GPIO || || || || <br /> |-<br /> | || || || GPIO2 || GPIO || style=&quot;color:yellow;background:black;&quot; align=center | '''13''' || style=&quot;color:yellow;background:black;&quot; align=center | '''14''' || GND || || || || <br /> |-<br /> | || || || GPIO3 || GPIO || style=&quot;color:yellow;background:black;&quot; align=center | '''15''' || style=&quot;color:yellow;background:black;&quot; align=center | '''16''' || GPIO || || || || <br /> |-<br /> | || || || || 3,3V || style=&quot;color:yellow;background:black;&quot; align=center | '''17''' || style=&quot;color:yellow;background:black;&quot; align=center | '''18''' || GPIO || || || || <br /> |-<br /> | || || || || SPI MOSI || style=&quot;color:yellow;background:black;&quot; align=center | '''19''' || style=&quot;color:yellow;background:black;&quot; align=center | '''20''' || GND || || || || <br /> |-<br /> | || || || || SPI MISO || style=&quot;color:yellow;background:black;&quot; align=center | '''21''' || style=&quot;color:yellow;background:black;&quot; align=center | '''22''' || GPIO || || || ||<br /> |-<br /> | || || || || SPI CLK || style=&quot;color:yellow;background:black;&quot; align=center | '''23''' || style=&quot;color:yellow;background:black;&quot; align=center | '''24''' || || || || ||<br /> |-<br /> | || || || || GND || style=&quot;color:yellow;background:black;&quot; align=center | '''25''' || style=&quot;color:yellow;background:black;&quot; align=center | '''26''' || || || || ||<br /> |-<br /> | || || || || I2C Data || style=&quot;color:yellow;background:black;&quot; align=center | '''27''' || style=&quot;color:yellow;background:black;&quot; align=center | '''28''' || I2C clock || || || ||<br /> |-<br /> | || || || || GPIO || style=&quot;color:yellow;background:black;&quot; align=center | '''29''' || style=&quot;color:yellow;background:black;&quot; align=center | '''30''' || GND || || || || <br /> |-<br /> | || || || || GPIO || style=&quot;color:yellow;background:black;&quot; align=center | '''31''' || style=&quot;color:yellow;background:black;&quot; align=center | '''32''' || GPIO || || || ||<br /> |-<br /> | || || || || GPIO || style=&quot;color:yellow;background:black;&quot; align=center | '''33''' || style=&quot;color:yellow;background:black;&quot; align=center | '''34''' || GND || || || ||<br /> |-<br /> | || || || || GPIO || style=&quot;color:yellow;background:black;&quot; align=center | '''35''' || style=&quot;color:yellow;background:black;&quot; align=center | '''36''' || GPIO || || || ||<br /> |-<br /> | || || || || GPIO || style=&quot;color:yellow;background:black;&quot; align=center | '''37''' || style=&quot;color:yellow;background:black;&quot; align=center | '''38''' || GPIO || || || ||<br /> |-<br /> | || || || || GND || style=&quot;color:yellow;background:black;&quot; align=center | '''39''' || style=&quot;color:yellow;background:black;&quot; align=center | '''40''' || GPIO || || || || <br /> |}<br /> <br /> ==Tips==<br /> ===Bootstrap===<br /> * Put ''Boot0'' jumper to go in [[Bootstrap]] mode<br /> <br /> ===Linux===<br /> * to activate login in Framebuffer console, please uncomment ''/etc/inittab'' line 35 this way:<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # Set up a getty on LCD<br /> tty1::respawn:/sbin/getty 38400 tty1<br /> &lt;/pre&gt;<br /> <br /> [[Category:DevelopmentBoards]]<br /> [[Category:Hardware]]</div> Salocin68 http://www.armadeus.org/wiki/index.php?title=Datasheet&diff=14072 Datasheet 2016-09-22T09:57:37Z <p>Salocin68: </p> <hr /> <div>= Armadeus datasheets and schemas =<br /> <br /> To see all documentation available for the board clic on the title.<br /> <br /> == [http://www.armadeus.com/_downloads/apf9328/ APF9328] ==<br /> * [http://www.armadeus.com/_downloads/apf9328/documentation/dataSheet_APF9328.pdf Datasheet]<br /> * [http://www.armadeus.com/_downloads/apf9328/hardware/apf_schema.pdf Schema]<br /> <br /> == [http://www.armadeus.com/_downloads/apf9328DevLight/ APF9328Devlight] ==<br /> * Datasheet [http://www.armadeus.com/_downloads/apf9328DevLight/documentation/dataSheet_APF9328_DevLight.pdf V1] [http://www.armadeus.com/_downloads/apf9328DevLight/documentation/dataSheet_APF9328_DevLight_V2.pdf V2]<br /> * Schemas [http://www.armadeus.com/_downloads/apf9328DevLight/hardware/dev_light_schema_v1.2.pdf V1.2] [http://www.armadeus.com/_downloads/apf9328DevLight/hardware/dev_light_schema.pdf V2]<br /> <br /> == [http://www.armadeus.com/_downloads/apf9328DevFull/ APF9328DevFull] ==<br /> * [http://www.armadeus.com/_downloads/apf9328DevFull/documentation/DataSheet_APF9328_DevFull.pdf Datasheet]<br /> * [http://www.armadeus.com/_downloads/apf9328DevFull/hardware/apf9328_dev_schematics_v1_1.pdf Schema]<br /> <br /> == [http://www.armadeus.com/_downloads/apf27/ APF27] ==<br /> * [http://www.armadeus.com/_downloads/apf27/documentation/datasheet_apf27.pdf Datasheet]<br /> * [http://www.armadeus.com/_downloads/apf27/hardware/apf27_V1.2.pdf Schema]<br /> <br /> == [http://www.armadeus.com/_downloads/apf27Dev/ APF27Dev] ==<br /> * [http://www.armadeus.com/_downloads/apf27Dev/documentation/dataSheet_APF27Dev.pdf Datasheet]<br /> * [http://www.armadeus.com/_downloads/apf27Dev/hardware/apf27_devfull_12.pdf Schema]<br /> <br /> == [http://www.armadeus.com/_downloads/apf27_PPS/ PPS (APF27)] ==<br /> * [http://www.armadeus.com/_downloads/apf27_PPS/documentation/datasheet_pps.pdf Datasheet]<br /> * [http://www.armadeus.com/_downloads/apf27_PPS/hardware/pps_v11.pdf Schema]<br /> <br /> == [http://www.armadeus.com/_downloads/apf28/ APF28] ==<br /> * [http://www.armadeus.com/_downloads/apf28/documentation/datasheet_apf28.pdf Datasheet]<br /> * [http://www.armadeus.com/_downloads/apf28/hardware/apf28_v10.pdf Schema]<br /> <br /> == [http://www.armadeus.com/_downloads/apf28_Dev/ APF28_DEV] ==<br /> * [http://www.armadeus.com/_downloads/apf28_Dev/documentation/dataSheet_APF28Dev.pdf Datasheet]<br /> * [http://www.armadeus.com/_downloads/apf28_Dev/hardware/apf28_dev_V10.pdf Schema]<br /> <br /> == [http://www.armadeus.com/_downloads/apf51/ APF51] ==<br /> * Datasheet<br /> ** [http://www.armadeus.com/_downloads/apf51/documentation/datasheet_apf51_V1.pdf APF51_V1]<br /> ** [http://www.armadeus.com/_downloads/apf51/documentation/datasheet_apf51_V2.pdf APF51_V2]<br /> * [http://www.armadeus.com/_downloads/apf51/hardware/apf51_v10.pdf Schema]<br /> <br /> == [http://www.armadeus.com/_downloads/apf51_Dev/ APF51Dev] ==<br /> * [http://www.armadeus.com/_downloads/apf51_Dev/documentation/dataSheet_APF51Dev.pdf Datasheet]<br /> * [http://www.armadeus.com/_downloads/apf51_Dev/hardware/apf51_dev_V12.pdf Schema]<br /> <br /> == [http://www.armadeus.com/_downloads/apf6/ APF6] ==<br /> * [http://www.armadeus.com/_downloads/apf6/documentation/datasheet_apf6.pdf Datasheet]<br /> <br /> == [http://www.armadeus.com/_downloads/apf6Dev/ APF6Dev] ==<br /> * [http://www.armadeus.com/_downloads/apf6Dev/documentation/dataSheet_APF6_Dev.pdf Datasheet]<br /> * [http://www.armadeus.com/_downloads/apf6Dev/hardware/apf6_dev_V2.pdf Schematics]<br /> <br /> == [http://www.armadeus.com/_downloads/apf6_SP/ APF6_SP] ==<br /> * [http://www.armadeus.com/_downloads/apf6_SP/documentation/datasheet_apf6SP.pdf Datasheet]<br /> <br /> == [http://www.armadeus.com/_downloads/opos6UL/ OPOS6UL] ==<br /> * [http://www.armadeus.com/_downloads/opos6ul/documentation/datasheet_opos6ul.pdf Datasheet]<br /> <br /> == [http://www.armadeus.com/_downloads/opos6ul_Dev/ OPOS6UL_Dev] ==<br /> * [http://www.armadeus.com/_downloads/opos6ul_Dev/documentation/dataSheet_opos6ul_Dev.pdf Datasheet]<br /> * [http://www.armadeus.com/_downloads/opos6ul_Dev/hardware/opos6UL_Dev_V12.pdf Schema]<br /> <br /> == [http://www.armadeus.com/_downloads/sp6_vision/ SP_VISION] ==<br /> * [http://www.armadeus.com/_downloads/sp6_vision/datasheet_sp_vision.pdf Datasheet]<br /> * [http://www.armadeus.com/_downloads/sp6_vision/hardware/sp_vision_eval_board_V05.pdf Schema]<br /> <br /> == [http://www.armadeus.com/_downloads/lw700at_adapt/ LW700] ==<br /> * [http://www.armadeus.com/_downloads/lw700at_adapt/documentation/datasheet_lw700at_adapt.pdf Datasheet]<br /> * [http://www.armadeus.com/_downloads/lw700at_adapt/hardware/LW700AT_adapt_v0B.pdf Schema]<br /> <br /> == [http://www.armadeus.com/_downloads/apw/ APW] ==<br /> * [http://www.armadeus.com/_downloads/apw/documentation/datasheet_APW.pdf Datasheet]<br /> * [http://www.armadeus.com/_downloads/apw/hardware/apf27_wireless_V0C.pdf Schema]<br /> <br /> == [http://www.armadeus.com/_downloads/lcd_adapt_LQ043 LQ043] ==<br /> * [http://www.armadeus.com/_downloads/lcd_adapt_LQ043/documentation/datasheet_lq043_adapt.pdf Datasheet]<br /> * [http://www.armadeus.com/_downloads/lcd_adapt_LQ043/hardware/lq043_adapt_schematics_v0a.pdf Schema]<br /> <br /> = HMS Demo =<br /> * Datasheet<br /> * Schema</div> Salocin68 http://www.armadeus.org/wiki/index.php?title=Datasheet&diff=14071 Datasheet 2016-09-22T09:47:11Z <p>Salocin68: /* OPOS6UL */</p> <hr /> <div>= Armadeus datasheets and schemas =<br /> <br /> To see all documentation available for the board clic on the title.<br /> <br /> == [http://www.armadeus.com/_downloads/apf9328/ APF9328] ==<br /> * [http://www.armadeus.com/_downloads/apf9328/documentation/dataSheet_APF9328.pdf Datasheet]<br /> * [http://www.armadeus.com/_downloads/apf9328/hardware/apf_schema.pdf Schema]<br /> <br /> == [http://www.armadeus.com/_downloads/apf9328DevLight/ APF9328Devlight] ==<br /> * Datasheet [http://www.armadeus.com/_downloads/apf9328DevLight/documentation/dataSheet_APF9328_DevLight.pdf V1] [http://www.armadeus.com/_downloads/apf9328DevLight/documentation/dataSheet_APF9328_DevLight_V2.pdf V2]<br /> * Schemas [http://www.armadeus.com/_downloads/apf9328DevLight/hardware/dev_light_schema_v1.2.pdf V1.2] [http://www.armadeus.com/_downloads/apf9328DevLight/hardware/dev_light_schema.pdf V2]<br /> <br /> == [http://www.armadeus.com/_downloads/apf9328DevFull/ APF9328DevFull] ==<br /> * [http://www.armadeus.com/_downloads/apf9328DevFull/documentation/DataSheet_APF9328_DevFull.pdf Datasheet]<br /> * [http://www.armadeus.com/_downloads/apf9328DevFull/hardware/apf9328_dev_schematics_v1_1.pdf Schema]<br /> <br /> == [http://www.armadeus.com/_downloads/apf27/ APF27] ==<br /> * [http://www.armadeus.com/_downloads/apf27/documentation/datasheet_apf27.pdf Datasheet]<br /> * [http://www.armadeus.com/_downloads/apf27/hardware/apf27_V1.2.pdf Schema]<br /> <br /> == [http://www.armadeus.com/_downloads/apf27Dev/ APF27Dev] ==<br /> * [http://www.armadeus.com/_downloads/apf27Dev/documentation/dataSheet_APF27Dev.pdf Datasheet]<br /> * [http://www.armadeus.com/_downloads/apf27Dev/hardware/apf27_devfull_12.pdf Schema]<br /> <br /> == [http://www.armadeus.com/_downloads/apf27_PPS/ PPS (APF27)] ==<br /> * [http://www.armadeus.com/_downloads/apf27_PPS/documentation/datasheet_pps.pdf Datasheet]<br /> * [http://www.armadeus.com/_downloads/apf27_PPS/hardware/pps_v11.pdf Schema]<br /> <br /> == [http://www.armadeus.com/_downloads/apf28/ APF28] ==<br /> * [http://www.armadeus.com/_downloads/apf28/documentation/datasheet_apf28.pdf Datasheet]<br /> * [http://www.armadeus.com/_downloads/apf28/hardware/apf28_v10.pdf Schema]<br /> <br /> == [http://www.armadeus.com/_downloads/apf28_Dev/ APF28_DEV] ==<br /> * [http://www.armadeus.com/_downloads/apf28_Dev/documentation/dataSheet_APF28Dev.pdf Datasheet]<br /> * [http://www.armadeus.com/_downloads/apf28_Dev/hardware/apf28_dev_V10.pdf Schema]<br /> <br /> == [http://www.armadeus.com/_downloads/apf51/ APF51] ==<br /> * Datasheet<br /> ** [http://www.armadeus.com/_downloads/apf51/documentation/datasheet_apf51_V1.pdf APF51_V1]<br /> ** [http://www.armadeus.com/_downloads/apf51/documentation/datasheet_apf51_V2.pdf APF51_V2]<br /> * [http://www.armadeus.com/_downloads/apf51/hardware/apf51_v10.pdf Schema]<br /> <br /> == [http://www.armadeus.com/_downloads/apf51_Dev/ APF51Dev] ==<br /> * [http://www.armadeus.com/_downloads/apf51_Dev/documentation/dataSheet_APF51Dev.pdf Datasheet]<br /> * [http://www.armadeus.com/_downloads/apf51_Dev/hardware/apf51_dev_V12.pdf Schema]<br /> <br /> == [http://www.armadeus.com/_downloads/apf6/ APF6] ==<br /> * [http://www.armadeus.com/_downloads/apf6/documentation/datasheet_apf6.pdf Datasheet]<br /> <br /> == [http://www.armadeus.com/_downloads/apf6Dev/ APF6Dev] ==<br /> * [http://www.armadeus.com/_downloads/apf6Dev/documentation/dataSheet_APF6_Dev.pdf Datasheet]<br /> * [http://www.armadeus.com/_downloads/apf6Dev/hardware/apf6_dev_V2.pdf Schematics]<br /> <br /> == [http://www.armadeus.com/_downloads/apf6_SP/ APF6_SP] ==<br /> <br /> * [http://www.armadeus.com/_downloads/apf6_SP/documentation/datasheet_apf6SP.pdf Datasheet]<br /> <br /> == [http://www.armadeus.com/_downloads/opos6UL/ OPOS6UL] ==<br /> <br /> * [http://www.armadeus.com/_downloads/opos6ul/documentation/datasheet_opos6ul.pdf Datasheet]<br /> <br /> == [http://www.armadeus.com/_downloads/sp6_vision/ SP_VISION] ==<br /> * [http://www.armadeus.com/_downloads/sp6_vision/datasheet_sp_vision.pdf Datasheet]<br /> * [http://www.armadeus.com/_downloads/sp6_vision/hardware/sp_vision_eval_board_V05.pdf Schema]<br /> <br /> == [http://www.armadeus.com/_downloads/lw700at_adapt/ LW700] ==<br /> * [http://www.armadeus.com/_downloads/lw700at_adapt/documentation/datasheet_lw700at_adapt.pdf Datasheet]<br /> * [http://www.armadeus.com/_downloads/lw700at_adapt/hardware/LW700AT_adapt_v0B.pdf Schema]<br /> <br /> == [http://www.armadeus.com/_downloads/apw/ APW] ==<br /> * [http://www.armadeus.com/_downloads/apw/documentation/datasheet_APW.pdf Datasheet]<br /> * [http://www.armadeus.com/_downloads/apw/hardware/apf27_wireless_V0C.pdf Schema]<br /> <br /> == [http://www.armadeus.com/_downloads/lcd_adapt_LQ043 LQ043] ==<br /> * [http://www.armadeus.com/_downloads/lcd_adapt_LQ043/documentation/datasheet_lq043_adapt.pdf Datasheet]<br /> * [http://www.armadeus.com/_downloads/lcd_adapt_LQ043/hardware/lq043_adapt_schematics_v0a.pdf Schema]<br /> <br /> = HMS Demo =<br /> * Datasheet<br /> * Schema</div> Salocin68 http://www.armadeus.org/wiki/index.php?title=OPOS6UL&diff=14070 OPOS6UL 2016-09-22T09:46:00Z <p>Salocin68: /* Description */</p> <hr /> <div>[[Category: OPOS6UL]]<br /> ==Description==<br /> <br /> [[File:OPOS6UL_NoWB.png]]<br /> <br /> <br /> The OPOS6UL is a [https://en.wikipedia.org/wiki/Single-board_computer Single Board Computer].<br /> <br /> Here is a list of the main features:<br /> * Processor: [http://www.nxp.com/products/microcontrollers-and-processors/arm-processors/i.mx-applications-processors/i.mx-6-processors/i.mx6qp/i.mx-6ultralite-processor-low-power-secure-arm-cortex-a7-core:i.MX6UL i.MX6UL] (i.MX6UL single A7 @ 538MHz, 696MHz in option)<br /> * RAM: DDR3 800Mbps. Default capacity is 256Mbytes.<br /> * Flash: [[EMMC OPOS6UL|eMMC]] 4GBytes to 16GBytes (default 4GB), 8 bits data bus.<br /> * Ethernet: onboard Physical (ready to use Ethernet 10/100Mbit link)<br /> * USB: High speed USB OTG (OnTheGo)<br /> * USB: High speed Host<br /> * TFT CMOS/LVDS interface<br /> * Wi-Fi (option): b/g/n with u.FL antenna<br /> * Bluetooth (option): BT 4.1 (Low Energy compatible)<br /> * Only one external supply of 3.3V required.<br /> * Mechanical dimensions: 67.6 x 30 mm<br /> * Connectors: SODIMM 204 pins<br /> <br /> ==Resources==<br /> <br /> * [[Datasheet#OPOS6UL | Datasheet and schematics]]<br /> <br /> ==Feature list==<br /> * [[OPOS6UL Linux kernel status]]<br /> <br /> {| border=&quot;0&quot; cellpadding=&quot;5&quot; cellspacing=&quot;5&quot; summary=&quot;Hardware Add-Ons by functionnalities&quot;<br /> |----------------<br /> |- style=&quot;background:#f4f4f4; color:black; -moz-border-radius:18px;&quot;<br /> |<br /> ===Video===<br /> ====Video Out====<br /> * [[LCD]]<br /> * [[FrameBuffer]]<br /> <br /> ====Video In====<br /> *[[Camera interface]]<br /> <br /> ||<br /> <br /> ===Wired communication===<br /> * [[Uart|UART]]<br /> * [[SPI]]<br /> * [[I2C]]<br /> * [[USB_Host]]<br /> * [[USB_Gadget]]<br /> * [[USB_OTG]]<br /> * [[CAN_bus_Linux_driver|CAN bus]]<br /> <br /> ||<br /> <br /> ===Wireless communication===<br /> * [[Wl12xx_driver]]<br /> * [[Wifi|Wi-Fi usage on Linux]]<br /> * [[Bluetooth|Bluetooth usage on Linux]]<br /> <br /> ===Storage===<br /> <br /> * [[EMMC OPOS6UL|eMMC]]<br /> <br /> ===Other===<br /> * [[PWM]]<br /> * [[GPIOlib]]<br /> <br /> |}<br /> <br /> ==Development boards==<br /> * [[OPOS6ULDev]]<br /> <br /> [[Category:MainBoards]]<br /> [[Category:Hardware]]</div> Salocin68 http://www.armadeus.org/wiki/index.php?title=APF6&diff=12938 APF6 2015-01-28T13:50:06Z <p>Salocin68: /* Note for APF6 boards */</p> <hr /> <div>==Description==<br /> The APF6 is a high-end [https://en.wikipedia.org/wiki/Single-board_computer Single Board Computer] targeted for advanced GUI, intensive computation and extended connectivity.<br /> <br /> Here is a list of the main features:<br /> * Processor: [http://www.freescale.com/webapp/sps/site/taxonomy.jsp?code=IMX6X_SERIES i.MX6] (single, dual or quad core Cortex-A9 @ up to 1GHz)<br /> * RAM: DDR3 1066MHz. 512Mbytes to 2GBytes. 32 ot 64bits data bus. Default capacity will be 512Mbytes.<br /> * Flash: eMMC 4Gbytes, 8 bits data bus.<br /> * Ethernet: onboard Physical (ready to use Ethernet 10/100/1000Mbit link)<br /> * USB: High speed USB OTG (OnTheGo) with onboard Physical (ready to use USB OTG link)<br /> * USB: High speed Host with integrated PHY<br /> * PCIexpress Gen2<br /> * SATA II<br /> * DVI output<br /> * TFT CMOS/LVDS interface<br /> * WiFi (option): b/g/n with u.FL antenna<br /> * Bluetooth (option): BT 4.0<br /> * Only one external supply of 3.3V required.<br /> * Mechanical dimensions: 60x50mm<br /> <br /> All the i.MX6 peripherals can be accessed through two high density [[Hirose connectors]].<br /> <br /> == Note for APF6 boards ==<br /> For compatibility reasons with the APF6x_SP the PCIe support has been activated on U-Boot. A warning message appears during the boot startup indicating:<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> WARNING: Make sure the PCIe #PERST line is connected<br /> &lt;/pre&gt;<br /> Do not take care of it if you don't use PCIe commands from uboot.<br /> <br /> ==Resources==<br /> <br /> * [[Datasheet#APF6 | Datasheet and schematics]]<br /> <br /> ==Feature list==<br /> * [[APF6_Linux_kernel_status]]<br /> <br /> {| border=&quot;0&quot; cellpadding=&quot;5&quot; cellspacing=&quot;5&quot; summary=&quot;Hardware Add-Ons by functionnalities&quot;<br /> |----------------<br /> |- style=&quot;background:#f4f4f4; color:black; -moz-border-radius:18px;&quot;<br /> |<br /> ===Video===<br /> ====Video Out====<br /> * [[LCD]]<br /> * [[BackLight]]<br /> * [[FrameBuffer]]<br /> * [[DVI_/_HDMI|DVI/HDMI]]<br /> <br /> ====Video In====<br /> *[[Camera_interface]]<br /> <br /> ||<br /> ===Wired communication===<br /> * [[Uart]]<br /> * [[SPI]]<br /> * [[I2C]]<br /> * [[USB_Host]]<br /> * [[USB_Gadget]]<br /> * [[USB_OTG]]<br /> * [[CAN_bus_Linux_driver|CAN bus]]<br /> * [[PCIE]]<br /> <br /> ||<br /> ===Wireless communication===<br /> * [[Wl12xx_driver]]<br /> * [[Wifi|WiFi usage on Linux]]<br /> * [[Bluetooth|Bluetooth usage on Linux]]<br /> <br /> ===Storage===<br /> * [[MultiMediaCard]]<br /> * [[SATA]]<br /> * [[eMMC]]<br /> <br /> ===Other===<br /> * [[PWM]]<br /> * [[GPIOlib]]<br /> <br /> |}<br /> <br /> ==Development boards==<br /> * [[APF6Dev]]<br /> <br /> [[Category:MainBoards]]<br /> [[Category:Hardware]]</div> Salocin68 http://www.armadeus.org/wiki/index.php?title=APF6&diff=12937 APF6 2015-01-28T13:49:53Z <p>Salocin68: /* Note for APF6 boards */</p> <hr /> <div>==Description==<br /> The APF6 is a high-end [https://en.wikipedia.org/wiki/Single-board_computer Single Board Computer] targeted for advanced GUI, intensive computation and extended connectivity.<br /> <br /> Here is a list of the main features:<br /> * Processor: [http://www.freescale.com/webapp/sps/site/taxonomy.jsp?code=IMX6X_SERIES i.MX6] (single, dual or quad core Cortex-A9 @ up to 1GHz)<br /> * RAM: DDR3 1066MHz. 512Mbytes to 2GBytes. 32 ot 64bits data bus. Default capacity will be 512Mbytes.<br /> * Flash: eMMC 4Gbytes, 8 bits data bus.<br /> * Ethernet: onboard Physical (ready to use Ethernet 10/100/1000Mbit link)<br /> * USB: High speed USB OTG (OnTheGo) with onboard Physical (ready to use USB OTG link)<br /> * USB: High speed Host with integrated PHY<br /> * PCIexpress Gen2<br /> * SATA II<br /> * DVI output<br /> * TFT CMOS/LVDS interface<br /> * WiFi (option): b/g/n with u.FL antenna<br /> * Bluetooth (option): BT 4.0<br /> * Only one external supply of 3.3V required.<br /> * Mechanical dimensions: 60x50mm<br /> <br /> All the i.MX6 peripherals can be accessed through two high density [[Hirose connectors]].<br /> <br /> == Note for APF6 boards ==<br /> For compatibility reasons with the APF6x_SP the PCIe support has been activated on U-Boot. A warning message appears during the boot startup indicating:<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> WARNING: Make sure the PCIe #PERST line is connected<br /> &lt;/pre&gt;<br /> Do not take care of if you don't use PCIe commands from uboot.<br /> <br /> ==Resources==<br /> <br /> * [[Datasheet#APF6 | Datasheet and schematics]]<br /> <br /> ==Feature list==<br /> * [[APF6_Linux_kernel_status]]<br /> <br /> {| border=&quot;0&quot; cellpadding=&quot;5&quot; cellspacing=&quot;5&quot; summary=&quot;Hardware Add-Ons by functionnalities&quot;<br /> |----------------<br /> |- style=&quot;background:#f4f4f4; color:black; -moz-border-radius:18px;&quot;<br /> |<br /> ===Video===<br /> ====Video Out====<br /> * [[LCD]]<br /> * [[BackLight]]<br /> * [[FrameBuffer]]<br /> * [[DVI_/_HDMI|DVI/HDMI]]<br /> <br /> ====Video In====<br /> *[[Camera_interface]]<br /> <br /> ||<br /> ===Wired communication===<br /> * [[Uart]]<br /> * [[SPI]]<br /> * [[I2C]]<br /> * [[USB_Host]]<br /> * [[USB_Gadget]]<br /> * [[USB_OTG]]<br /> * [[CAN_bus_Linux_driver|CAN bus]]<br /> * [[PCIE]]<br /> <br /> ||<br /> ===Wireless communication===<br /> * [[Wl12xx_driver]]<br /> * [[Wifi|WiFi usage on Linux]]<br /> * [[Bluetooth|Bluetooth usage on Linux]]<br /> <br /> ===Storage===<br /> * [[MultiMediaCard]]<br /> * [[SATA]]<br /> * [[eMMC]]<br /> <br /> ===Other===<br /> * [[PWM]]<br /> * [[GPIOlib]]<br /> <br /> |}<br /> <br /> ==Development boards==<br /> * [[APF6Dev]]<br /> <br /> [[Category:MainBoards]]<br /> [[Category:Hardware]]</div> Salocin68 http://www.armadeus.org/wiki/index.php?title=APF6&diff=12936 APF6 2015-01-28T13:49:11Z <p>Salocin68: </p> <hr /> <div>==Description==<br /> The APF6 is a high-end [https://en.wikipedia.org/wiki/Single-board_computer Single Board Computer] targeted for advanced GUI, intensive computation and extended connectivity.<br /> <br /> Here is a list of the main features:<br /> * Processor: [http://www.freescale.com/webapp/sps/site/taxonomy.jsp?code=IMX6X_SERIES i.MX6] (single, dual or quad core Cortex-A9 @ up to 1GHz)<br /> * RAM: DDR3 1066MHz. 512Mbytes to 2GBytes. 32 ot 64bits data bus. Default capacity will be 512Mbytes.<br /> * Flash: eMMC 4Gbytes, 8 bits data bus.<br /> * Ethernet: onboard Physical (ready to use Ethernet 10/100/1000Mbit link)<br /> * USB: High speed USB OTG (OnTheGo) with onboard Physical (ready to use USB OTG link)<br /> * USB: High speed Host with integrated PHY<br /> * PCIexpress Gen2<br /> * SATA II<br /> * DVI output<br /> * TFT CMOS/LVDS interface<br /> * WiFi (option): b/g/n with u.FL antenna<br /> * Bluetooth (option): BT 4.0<br /> * Only one external supply of 3.3V required.<br /> * Mechanical dimensions: 60x50mm<br /> <br /> All the i.MX6 peripherals can be accessed through two high density [[Hirose connectors]].<br /> <br /> == Note for APF6 boards ==<br /> For compatibility reasons with the APF6x_SP the PCIe support has been activated on U-Boot. A warning message appears during the boot startup indicating:<br /> WARNING: Make sure the PCIe #PERST line is connected<br /> <br /> Do not take care of if you don't use PCIe commands from uboot.<br /> <br /> ==Resources==<br /> <br /> * [[Datasheet#APF6 | Datasheet and schematics]]<br /> <br /> ==Feature list==<br /> * [[APF6_Linux_kernel_status]]<br /> <br /> {| border=&quot;0&quot; cellpadding=&quot;5&quot; cellspacing=&quot;5&quot; summary=&quot;Hardware Add-Ons by functionnalities&quot;<br /> |----------------<br /> |- style=&quot;background:#f4f4f4; color:black; -moz-border-radius:18px;&quot;<br /> |<br /> ===Video===<br /> ====Video Out====<br /> * [[LCD]]<br /> * [[BackLight]]<br /> * [[FrameBuffer]]<br /> * [[DVI_/_HDMI|DVI/HDMI]]<br /> <br /> ====Video In====<br /> *[[Camera_interface]]<br /> <br /> ||<br /> ===Wired communication===<br /> * [[Uart]]<br /> * [[SPI]]<br /> * [[I2C]]<br /> * [[USB_Host]]<br /> * [[USB_Gadget]]<br /> * [[USB_OTG]]<br /> * [[CAN_bus_Linux_driver|CAN bus]]<br /> * [[PCIE]]<br /> <br /> ||<br /> ===Wireless communication===<br /> * [[Wl12xx_driver]]<br /> * [[Wifi|WiFi usage on Linux]]<br /> * [[Bluetooth|Bluetooth usage on Linux]]<br /> <br /> ===Storage===<br /> * [[MultiMediaCard]]<br /> * [[SATA]]<br /> * [[eMMC]]<br /> <br /> ===Other===<br /> * [[PWM]]<br /> * [[GPIOlib]]<br /> <br /> |}<br /> <br /> ==Development boards==<br /> * [[APF6Dev]]<br /> <br /> [[Category:MainBoards]]<br /> [[Category:Hardware]]</div> Salocin68 http://www.armadeus.org/wiki/index.php?title=APF28&diff=12935 APF28 2015-01-28T13:46:06Z <p>Salocin68: </p> <hr /> <div>==Description==<br /> The APF28 is a simple and low cost [https://en.wikipedia.org/wiki/Single-board_computer Single Board Computer] targeted for small GUI, communication and control process.<br /> <br /> Here is a list of the main features:<br /> * Processor: [http://www.freescale.com/webapp/sps/site/prod_summary.jsp?code=i.MX286 i.MX28x] (ARM9 @ 454MHz)<br /> * RAM: DDR2 400. 64 to 512MB. 16 bits data bus. Default capacity is 128MB.<br /> * Flash: NAND. 256MB to 4GB, 8 bits data bus. Default capacity is 256MB<br /> * Ethernet: onboard Physical (ready to use Ethernet 10/100Mbit link)<br /> * USB: High speed USB OTG (OnTheGo) with onboard Physical<br /> * USB: 1 High speed Hosts with integrated PHY<br /> * Touchscreen controler (4/5 wires)<br /> * Low speed ADCs (up to 7)<br /> * High speed ADC<br /> * RTC and Watchdog<br /> * Battery charger (Li-On/Li-Po)<br /> * Supplies: high end DC/DC converters and LDOs on board. Only one external supply required (5V, batterie or 3.3V).<br /> * Mechanical dimensions: ~43x25mm<br /> <br /> All the i.MX28 peripherals (LCD, SDIO, SPI, 6xSerial, I2C, 2xUSB, PWM, etc...) can be accessed through two high density [[Hirose connectors]].<br /> <br /> The APF28 module can be plugged on the [[APF28Dev]] docking board or your own custom devt board.<br /> <br /> == Note for APF28i (industrial) boards ==<br /> the support for the industrial nand used on the board, is ony available on recent GIT sources (GIT Head). Please don't use the 5.3 bsp until a newer BSP release is done. <br /> <br /> ==Resources==<br /> <br /> * [[Datasheet#APF28 | Datasheet and schematics]]<br /> <br /> ==Feature list==<br /> * [[APF28_Linux_kernel_status]]<br /> <br /> {| border=&quot;0&quot; cellpadding=&quot;5&quot; cellspacing=&quot;5&quot; summary=&quot;Hardware Add-Ons by functionnalities&quot;<br /> |----------------<br /> |- style=&quot;background:#f4f4f4; color:black; -moz-border-radius:18px;&quot;<br /> |<br /> ===Video Out===<br /> * [[LCD]]<br /> * [[BackLight]]<br /> * [[FrameBuffer]]<br /> <br /> ||<br /> ===Wired communication===<br /> * [[Uart]]<br /> * [[SPI]]<br /> * [[I2C]]<br /> * [[USB_OTG]]<br /> * [[USB_Host]]<br /> * [[USB_Gadget]]<br /> <br /> ===Storage===<br /> * [[MultiMediaCard]]<br /> ===Other===<br /> * [[PWM]]<br /> * [[GPIO_Driver]]<br /> * [[APF28_PMIC]] (Touchscreen, keypad, ADCs, Battery)<br /> ** [[LRADC]]<br /> * [[Power_management]]<br /> * [[RTC#APF28 | RTC]]<br /> |}<br /> <br /> ==Links==<br /> * [http://www.armadeus.com/english/products-processor_boards-apf28.html Product page at Armadeus Systems]<br /> <br /> [[Category:MainBoards]]<br /> [[Category:Hardware]]</div> Salocin68 http://www.armadeus.org/wiki/index.php?title=LinuxInstall&diff=12857 LinuxInstall 2014-12-17T09:08:13Z <p>Salocin68: /* Configure SDK/BSP options */</p> <hr /> <div>&lt;noinclude&gt;<br /> &lt;big&gt;How-To install Armadeus Software Development Kit (SDK) on Linux systems. This SDK is currently based on the (excellent) [http://buildroot.net/ Buildroot].&lt;/big&gt;<br /> &lt;/noinclude&gt;<br /> <br /> The installation was successfully tested on the following distributions:<br /> * Debian Lenny (5.0), Squeeze (6.0.x), wheezy (7.2)<br /> * X/KUbuntu Edgy Eft (6.10), Gutsy Gibbon (7.10), Hardy Heron (8.04) &amp; Jaunty Jackalope (9.04)<br /> * Ubuntu Lucid Lynx (10.04) (32 &amp; 64bits), 12.04 LTS (32 &amp; 64bits), 13.10 (32 &amp; 64bits)<br /> * Mandriva 2006<br /> * Fedora Core 3 &amp; 4, Fedora 10, Laughlin (14)<br /> * Red Hat Enterprise 5.2<br /> * Gentoo 10.0 (32 &amp; 64 bits)<br /> * SuSE 10.1, OpenSUSE 11.3 - 12.3<br /> <br /> '''The installation may fail on:'''<br /> * Ubuntu Karmic Koala (9.10): tslib fails to build<br /> <br /> '''APF28 requirements:'''<br /> * APF28 board requires a Linux distribution with (GNU) tar version 1.20 or later to compile the Linux Kernel - Please update or upgrade your Linux distribution. <br /> <br /> ==Prerequisites for Linux installation==<br /> {{Note|From here we assume that your Linux system has a ''make'' version '''greater or equal to''' 3.81. To check it: <br /> &lt;pre class=&quot;host&quot;&gt;<br /> $ make -v<br /> GNU Make 3.81<br /> ...<br /> &lt;/pre&gt;<br /> }}<br /> For armadeus up to 3.4, make should be '''strictly''' make-3.81 (make-3.82 is too strict). A Fedora (14 and 15) -specific solution can be found later; other recent distributions such as mageia1 also have make-3.82, and a generic solution, based on configure&amp;&amp; make&amp;&amp; sudo make install can be used to install make-3.81 (which can be retrieved from http://ftp.gnu.org/gnu/make/make-6.81.tar.gz) in /usr/local/bin (and , according to one's PATH, make 3-81 can be invoked directly or as /usr/local/bin/make). <br /> <br /> Depending on your distribution, some additional packages are required:<br /> <br /> ===Debian/Ubuntu based systems===<br /> [[Ubuntu/Debian installation prerequisites]]<br /> <br /> ===Mandriva based systems=== <br /> [[Mandriva installation prerequisites]]<br /> <br /> ===RPM-based systems (RedHat, Fedora, CentOS)===<br /> [[RedHat/Fedora installation prerequisites]]<br /> <br /> ===OpenSuse based systems===<br /> [[OpenSuse installation prerequisites]]<br /> <br /> ===Gentoo based systems===<br /> [[Gentoo installation prerequisites]]<br /> <br /> ==Get Armadeus software==<br /> * '''If you are a &quot;careful&quot; user''', then download [https://sourceforge.net/projects/armadeus/files/ the latest stable installation tarball from SourceForge] and detar it wherever you want:<br /> &lt;pre class=&quot;host&quot;&gt;<br /> $ tar xjvf armadeus-5.3.tar.bz2<br /> &lt;/pre&gt;<br /> * '''If you want the latest snapshot''', the whole development tree can be checked out from our [[GIT]] repository.<br /> &lt;pre class=&quot;host&quot;&gt;<br /> $ git clone git://git.code.sf.net/p/armadeus/code armadeus<br /> &lt;/pre&gt; <br /> <br /> * depending on your previous choice, a directory named ''armadeus/'' or ''armadeus-5.3/'' will be created on your hard-disk and will contain all the files you need.<br /> <br /> '''Remarks''':<br /> * '''Do not use spaces''' in the directory name !<br /> * '''Do not use a directory path beginning with /usr.''' It is a known bug of Buildroot (until BR2012.11, at 2012-12).<br /> * GIT write/push accesses are limited to the integrators ([[User:JulienB|JulienB]], [[User:Salocin68|Salocin68]], [[User:Jorasse|Jorasse]], [[User:FabienM|FabienM]])<br /> <br /> ==Configure SDK/BSP options==<br /> {{Note|If you are new to Armadeus and have troubles compiling armadeus-5.x using the following instructions, you may find some hints here: [[Armadeus 5.0 Troubleshots]], [[Armadeus 5.2 Troubleshots]], [[Armadeus 5.3 Troubleshots]]}}<br /> *Go to the directory where you put the Armadeus sources:<br /> &lt;pre class=&quot;host&quot;&gt;<br /> $ cd armadeus/ (or armadeus-5.3/)<br /> &lt;/pre&gt;<br /> *The first time you compile an Armadeus distribution you have to specify the target (here the APF9328) to work with. <br /> &lt;pre class=&quot;host&quot;&gt;<br /> $ make apf9328_defconfig<br /> &lt;/pre&gt;<br /> This command reloads the default configuration to support your target and automatically start a Buildroot's configuration menu.<br /> <br /> * Current valid default configurations are:<br /> &lt;pre class=&quot;host&quot;&gt;<br /> apf9328_defconfig apf27_defconfig pps_defconfig apf28_defconfig apf51_defconfig pps51_defconfig apf6_defconfig<br /> &lt;/pre&gt;<br /> <br /> For PPS boards, please see [[APF27_PPS]] or [[PPS51]] Wiki pages, as these boards have specific build.<br /> <br /> * After some downloads, you will get the Buildroot configuration interface:<br /> <br /> {{Note|If you ever made changes during the following steps, at any time, you can reload the default configuration with:<br /> $ make apfxx_defconfig (xx depending on your board)}}<br /> <br /> [[Image:Menuconfig3.png]]&lt;br&gt;<br /> *If you are not familiar with Buildroot here are some tips:<br /> *# you can move the highlighted item with the &quot;up&quot;/&quot;down&quot; arrow keys<br /> *# with the &quot;left&quot;/&quot;right&quot; arrow keys you can choose between &quot;Select&quot;, &quot;Exit&quot; or &quot;Help&quot; buttons<br /> *# &quot;space&quot;/&quot;enter&quot;:<br /> *#* selects the currently highlighted item if you are on the &quot;Select&quot; button<br /> *#* go back in previous menu if you are on &quot;Exit&quot; button<br /> *#* show you some Help for current item if you are on &quot;Help&quot; button<br /> *# for more Help about Buildroot commands, select &quot;Help&quot; in the main configuration screen<br /> <br /> * Update the memory configuration of your board ('''if needed'''; by default BSP is configured for the minimal memory configuration available on the corresponding board):<br /> <br /> :In menu:<br /> :&lt;pre class=&quot;config&quot;&gt;System configuration ---&gt; [*] Armadeus Device Support ---&gt;&lt;/pre&gt;<br /> <br /> :you can check and change the quantity of RAM available on your Armadeus board:<br /> :[[Image:Build_config_memory.png]]<br /> :For [[APF9328]] the memory can be either 16 or 32MiB (be sure to select 1 RAM chip)<br /> :For [[APF27]] it could be either 64MiB or 128MiB (2 x 64MiB) (in that case be sure to select 2 chips of 64MiB instead of 1 chip of 128MiB).<br /> :For [[APF51]] it could be either 256MiB or 512MiB (2x256MiB) (in such case be sure to select 2 chips of 256MiB instead of 1 chip of 512).<br /> :For [[APF28]] The memory can be 128, 256, 512 or 1024MiB (be sure to select 1 RAM chip)<br /> <br /> * You may decrease the compilation time by increasing the number of parallel jobs running simultaneously on your system (the result is not guaranteed). This option is located in:<br /> :&lt;pre class=&quot;config&quot;&gt;Build Options ---&gt; (0) Number of jobs to run simultaneously&lt;/pre&gt;<br /> 0 means that Buildroot will try to guess automatically how much parallel jobs it can launch.<br /> <br /> * During the SDK/BSP build, a lot of software archives are downloaded from Internet. The downloaded files are put by default in the ''armadeus/downloads/'' directory. '''If you have several views or plan to build the toolchain several times''', we advise you to put all the downloaded files in ''/local/downloads'' (for example). This is done by configuring Buildroot to use this directory for all your views. Nevertheless, Buildroot will be downloaded separately for each build environment you set up.<br /> :&lt;pre class=&quot;config&quot;&gt;Build options ---&gt; (...) Download dir&lt;/pre&gt;<br /> :[[Image:Build_config_download.png]]<br /> {{Note|Of course, ''/local/downloads'' should exists on your system and you should have writing rights on it !}}<br /> * In recent Buildroot you can also use the following method:<br /> export BUILDROOT_DL_DIR=/local/downloads<br /> <br /> * After the build, we advise you to copy all the files in ''downloads/'' / ''/local/downloads'' on a removable medium, in case you want to install the development tools on other systems, without to have to reload all the archives.<br /> <br /> * Now, Exit the configuration tool and save your configuration<br /> <br /> * You can come back to this configuration menu, by typing (your changes will be kept): <br /> &lt;pre class=&quot;host&quot;&gt;<br /> make menuconfig<br /> &lt;/pre&gt;<br /> <br /> ==Launch build==<br /> $ make<br /> The toolchain and the full distribution are automatically built. During this procedure, several files are downloaded from Internet. &lt;br&gt;<br /> '''Please wait for a while.... it takes at least one hour for the first run!'''&lt;br&gt;<br /> By default, the downloaded files/tarball are put in the ''armadeus/downloads/'' directory. Please see the previous chapter to know how to optimize that if you plan to build several views or want to build faster.<br /> <br /> ==Enjoy the result==<br /> The generated binary files can be found in the subdirectory ''buildroot/output/images'':<br /> *''apf9328-u-boot.brec'' (only on [[APF9328]]): BRecord image that can be used with the bootstrap, if U-Boot is not installed or not working (see [[BootLoader]] page)<br /> *''XX-u-boot.bin'': U-Boot image file to be used with U-Boot itself, (see [[BootLoader#Update_U-Boot | updating U-Boot]])<br /> *''XX-linux.bin'': Linux image to use with U-Boot, (see [[Target_Software_Installation#Linux_kernel_installation | updating Linux]])<br /> *''XX-rootfs.jffs2'': JFFS2 filesystem/rootfs image to use with U-Boot, (see [[Target_Software_Installation#Linux_rootfs_installation | updating rootfs]])<br /> *''XX-rootfs.ubi'' (not supported on [[APF9328]]): [[UBIFS|UBI]] filesystem/rootfs image to use with U-Boot, (see [[Target_Software_Installation#Linux_rootfs_installation | updating rootfs]])<br /> *''apfXX-rootfs.tar'': for an NFS/MMC based rootfs, (see [[Network_Configuration#Boot_from_NFS | Booting from NFS]] &amp; [[MultiMediaCard#Booting_from_MMC.2FSD | Booting from a MMC/SD]])<br /> <br /> '''Please note the new naming convention of binary files and directories (since Armadeus 4.0)'''<br /> <br /> *''buildroot/output/build'': contains all the build results for target filesystem, &lt;b&gt;linux&lt;/b&gt;, busybox and &lt;b&gt;u-boot&lt;/b&gt;...<br /> *''buildroot/output/toolchain/'': cross compilation toolchain's build dir. Binaries usable for cross-compilation are in ''buildroot/output/host/usr/bin''.<br /> *''buildroot/output/target/'': target filessytem before generating rootfs images<br /> <br /> More information is available in the [http://buildroot.uclibc.org/buildroot.html Buildroot's documentation]<br /> <br /> * Note: Previous versions (3.x) of Armadeus SDK stored the generated binary files at a different place: '' ''buildroot/binaries/XX/'' (where XX was the name of your board).<br /> <br /> &lt;noinclude&gt;<br /> <br /> You then copy the binary image to your server directory:<br /> &lt;pre class=&quot;host&quot;&gt;<br /> $ cp buildroot/output/images/* /tftpboot<br /> &lt;/pre&gt;<br /> <br /> <br /> ==To keep your local copy/repository up-to-date with the armadeus GIT repository==<br /> &lt;pre class=&quot;host&quot;&gt;<br /> $ git pull<br /> &lt;/pre&gt;<br /> This will update your working directory to the latest release.<br /> <br /> Note: if &quot;git pull&quot; fails because a directory or a file already exists, then do:<br /> $ rm -rf &lt;this-directory/file&gt;<br /> $ git pull<br /> <br /> You can do a:<br /> $ make apfXX_defconfig<br /> to have the latest features automatically activated.<br /> <br /> You have to do a '''make''' to rebuild binary files and then upload the binary files to your target.<br /> <br /> Note: if definitively everything goes wrong while it worked before the last update.<br /> You can apply the following procedure (all your modifications in buildroot will be lost):<br /> $ rm -rf buildroot/<br /> $ rm Makefile<br /> $ git pull<br /> $ make apfXX_defconfig<br /> $ make<br /> $ cp buildroot/output/images/* /tftpboot<br /> <br /> Enjoy!<br /> &lt;/noinclude&gt;</div> Salocin68 http://www.armadeus.org/wiki/index.php?title=Setup&diff=12856 Setup 2014-12-17T09:06:53Z <p>Salocin68: </p> <hr /> <div>On this page, you will find all the useful information to configure your Armadeus board for optimum usage.<br /> <br /> ==First StartUp==<br /> Just got your Armadeus board and want to start playing with it? &lt;br&gt;<br /> Follow these quick steps to setup your environment accordingly:<br /> # Connect your APF module to your development/docking board (custom one or ARMadeus Systems official one) (your system will be hereafter referred to as &quot;the Target&quot;)<br /> # '''On APF9328Dev/APF27Dev/PPS:''' connect your PC (= &quot;the Host&quot;) to your board with a [http://en.wikipedia.org/wiki/Null_modem null-modem RS-232 cable] (only Rx/Tx/Gnd signals are needed). If you don't have a RS-232 port on your Host, you can use a &quot;USB &lt;-&gt; serial&quot; converter (you'll still need the null-modem cable).<br /> # '''On APF51Dev/APF28Dev/APF6Dev:''' connect your PC (= &quot;the Host&quot;) to your board with a USB to miniUSB cable. On the APF use the &quot;Debug&quot; connector (between HDMI and USB Host ones)<br /> # [[Communicate | Install (minimum) tools to communicate with your APF from your Host.]]<br /> # Connect the power supply to your development board. (See the [[Datasheet]] of your *Dev board for more informations)<br /> # Verify your system is booting and starting Linux (In U-Boot console, type &quot;boot&quot; if bootdelay is too long). Several information will be displayed on your terminal like on this [[Linux start screenshot | screenshot]] (Default Linux login is &quot;root&quot; with an empty password). '''If your system is NOT starting''', walk through [[U-Boot communication quick check|this small checklist]].<br /> # If Linux has successfully started, your system is operational. If you want to add applications to your board or develop custom ones, then you can proceed with the Toolchain installation. [[Setup#Build_and_update_your_system | See Build and update your system]].<br /> <br /> ===Tutorial===<br /> If you want a more &quot;userfriendly&quot; procedure, you can try this (under construction) tutorial: [[Beginner's_tutorial]]<br /> <br /> ==Build and update your system==<br /> # [[Embedded Linux system basis]]<br /> # [[Toolchain| Install the development environment (=Toolchain) for your board and generate your Linux/rootfs images]]<br /> # [[Target Software Installation| Install/flash your U-Boot, Linux and rootfs freshly generated images on your board]]<br /> # [[Armadeus_3#How-to_develop_with_Armadeus_.2F_customize_your_SDK| Customize your Armadeus SDK]]<br /> <br /> <br /> {{Note| When a board is shipped, default factory binaries are flashed on it. It can be a legacy version of the armadeus BSP. So it's important to load the latest release binaries (&quot;Get latest release&quot; menu on side bar of this wiki), or build them yourself, and update all software with the following commands (on U-Boot assuming the image files have already been copied in /tftpboot):<br /> <br /> &lt;pre class=&quot;apf&quot;&gt;<br /> BIOS&gt; run update_uboot<br /> BIOS&gt; reset<br /> BIOS&gt; run flash_reset_env<br /> ...<br /> BIOS&gt; run update_kernel<br /> BIOS&gt; run update_rootfs<br /> &lt;/pre&gt;<br /> }}</div> Salocin68 http://www.armadeus.org/wiki/index.php?title=FPGA_loader&diff=12820 FPGA loader 2014-11-06T10:59:57Z <p>Salocin68: </p> <hr /> <div>On this page, you will find all the informations needed to use the Linux FPGA loader driver.<br /> This driver allows you to load the FPGA of your APF board from Linux userspace/shell (ie FPGA reprogrammation after Linux boot).<br /> <br /> == Driver installation==<br /> Driver is installed in default Armadeus rootfs.<br /> <br /> For the hackers, code is located in ''target/linux/modules/fpga/dev_tools/fpga_devtools/''.<br /> <br /> == Driver usage ==<br /> <br /> *To upload a new firmware, use the small helper script that can do all the job for you (load driver and then firmware). Just call it with the bitfile (.rbf for APF6SP and .bin for the other boards) as parameter. For example:<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # load_fpga bramtest_top_apf.bin<br /> &lt;/pre&gt;<br /> <br /> <br /> * [[Simple_blinking_LED | You can find some ready to use bitfiles in ''firmware/leds/blinking_led/bin/'' (blinking LED).]]<br /> {{Note| On apf9328_devfull and on apf27_dev a LED is already soldered on fpga. For apf27_dev the fpga bank1 must be powered with 3.3V (connect pin 39 and pin 1 on J20 header)}}<br /> <br /> ==Troubleshots==<br /> === APF51 ===<br /> * Use binary format '''.bin''', bitstream format '''.bit''' doesn't work.<br /> <br /> All the troubleshots are handled by the ''/usr/bin/load_fpga'' utility, mentionned above.<br /> <br /> [[Category:FPGA]]</div> Salocin68 http://www.armadeus.org/wiki/index.php?title=FAQ&diff=12818 FAQ 2014-11-05T15:07:59Z <p>Salocin68: /* What does &quot;Armadeus&quot; mean ? */</p> <hr /> <div>==General Questions==<br /> <br /> ===What is the &quot;Armadeus Project&quot; intended for ?===<br /> The goal of this project is to allow everyone to easily develop embedded Open Source systems.<br /> When all the embedded systems in the world run open source software, life will be better ;-)<br /> <br /> ===What does &quot;Armadeus&quot; mean ?===<br /> &quot;Armadeus&quot; is the contraction of a well know architecture and &quot;Amadeus&quot;. Indeed we chose this non x86 architecture for its simplicity and efficiency and our boards are as gifted to run embedded systems as Mozart was for composing music. Moreover the Armadeus Project was born in 2006, year of the 250th Mozart's Birthday.<br /> <br /> ===How do I get help ?===<br /> First take a look at the whole Wiki. If you can't find help contact us directly: [[Help:Contents]]. If you are located in France, we have members in Besançon, Montbéliard &amp; Mulhouse who can provide help. For Swiss members, we can provide help in Basel, Lausanne &amp; Zürich.<br /> <br /> === Why are there http://armadeus.org and http://armadeus.com ? Is there a company backing/hiding behind the project? ===<br /> <br /> &lt;http://armadeus.com&gt; is the webpage dedicated to Armadeus Systems. &lt;br&gt; <br /> The company develops and produces the main boards which are then available at a discount price to the association members (non commercial usage only!). <br /> <br /> Historically the Armadeus Project (association) was founded before Armadeus Systems (company). &lt;br&gt;<br /> After one year of existence we realized that it was quite impossible to achieve our goals without investing more time and more cash. That's why the company was founded.<br /> <br /> The association was started for our own pleasure and also to help universities and enthusiasts develop Linux embedded systems. &lt;br&gt;<br /> It is a non profit association and works mostly on founders' free time.<br /> <br /> The developments (hardware/firmware/software) performed within the association are under GPL/LGPL licence. &lt;br&gt;<br /> The hardware funded by the association can not be used in a commercial product.<br /> <br /> === Is there some rule to respect to contribute to the wiki? ===<br /> Yes there are few rules that help you to contribute to update the wiki there: [[WritingRules |HowTo write articles for armadeus wiki]] <br /> <br /> ==Hardware Questions==<br /> ===Are the Armadeus boards RoHS compliant ?===<br /> Yes<br /> <br /> ===I have an APF27 kit and my 7&quot; Chimei LW700 LCD is blinking (RGB colors), what can I do ?===<br /> You're probably running an old (&lt; 3.3) Armadeus BSP release and so default LCD is Sharp LQ043. You have to change your Linux configuration to support your LCD. Please follow instructions on [[FrameBuffer|this page]].<br /> <br /> == Firmware Question (FPGA) ==<br /> <br /> === My bitstream break my APF ===<br /> <br /> If you are using ISE13.x or upper, there is a bug loading script TCL file. When design is generated by POD, a script is sourced to make bitstream (myproject.tcl), the source commande ignore the constraint file (ucf) and FPGA pinout is done randomly. To avoid this, once tcl script sourced, re-run all design.<br /> <br /> ==Software Questions==<br /> ===Where are the sources ?===<br /> We have a project on SourceForge: http://sourceforge.net/projects/armadeus/ with a [[GIT]] repository.<br /> <br /> ===What are the performances of your board ?===<br /> [[Performances | Wiki page talking about board performances]]<br /> <br /> ===How do I get help/support===<br /> [[Help:Contents]]<br /> <br /> === How to register my interrupt routine in Linux application ? ===<br /> [[How to register my interrupt routine in Linux application ?]]<br /> <br /> === How to launch my application at startup ? ===<br /> See [[Automatically_launch_your_application | Automatically launch your application]] page.<br /> <br /> ===U-Boot seems ok but prints: *** Warning - bad CRC, using default environment - Is there something wrong?=== <br /> Everything is ok. It is an U-Boot feature that happens if the environment partition is empty.&lt;br&gt;<br /> Please read the U-Boot FAQ on this issue: http://www.denx.de/wiki/view/DULG/WarningBadCRCUsingDefaultEnvironment<br /> <br /> {{LanguageBar|FAQ|FAQ|FAQ}}</div> Salocin68 http://www.armadeus.org/wiki/index.php?title=GPIOlib&diff=12810 GPIOlib 2014-10-23T13:15:37Z <p>Salocin68: /* Datasheet gpio number correspondance */</p> <hr /> <div><br /> <br /> ==Introduction==<br /> With recent Linux kernel (&gt; 2.6.3x), there is an abstraction layer meant to ease GPIO usage: ''gpiolib''. We will explain here how to use it.<br /> <br /> For this purpose we will use the user LED and button of the button to let you operate the GPIO feature without any hardware modification.<br /> <br /> Linux provides specific drivers for [[GPIO_LEDS|LEDs]] and [[GPIO_keys|switches]] - as explained in the [http://www.kernel.org/doc/Documentation/gpio.txt Linux documentation of the GPIO] - &quot;that should be used instead of talking directly to the GPIOs; they integrate with kernel frameworks better than your userspace code could.&quot;<br /> <br /> == Datasheet gpio number correspondance ==<br /> <br /> Linux manage gpio with a simple number, but under datasheet GPIO are referenced with port number (or letter) and pin number. To convert in single integer, use following formula :<br /> <br /> * '''APF9328''': TODO.<br /> * '''APF27''': (port letter (A=0, B=1, ...) x 32 ) + pin number.<br /> ** Example : '''PF14''' = (5x32) + 14 = '''174'''<br /> * '''APF28''': (Bank number x 32) + pin number<br /> ** Example : '''GPIO_0_21''' = (0x32) + 21 = '''21'''<br /> * '''APF51''' and '''APF6''': ((Bank number - 1) x 32) + pin number<br /> ** Example : '''GPIO1_2''' = (0 x 32) + 2 = '''2'''<br /> <br /> ==Installation==<br /> * Configure Linux kernel:<br /> &lt;pre class=&quot;host&quot;&gt;<br /> $ make linux-menuconfig<br /> &lt;/pre&gt;<br /> * Enable the sysfs interface of the GPIOlib If not already done:<br /> &lt;pre class=&quot;config&quot;&gt;<br /> Device Drivers ---&gt;<br /> -*- GPIO Support ---&gt;<br /> [*] /sys/class/gpio/... (sysfs interface)<br /> &lt;/pre&gt;<br /> * In order to test the GPIOlib with the user LED and SWITCH of the board you will have to disable the [[GPIO_keys]] and [[GPIO_LEDS]] drivers that are the regular driver for such device.<br /> &lt;pre class=&quot;config&quot;&gt;<br /> Device Drivers ---&gt;<br /> Input device support ---&gt;<br /> [*] Keyboards ---&gt;<br /> &lt; &gt; GPIO Buttons (be sure GPIO Buttons is unchecked)<br /> &lt;/pre&gt;<br /> &lt;pre class=&quot;config&quot;&gt;<br /> Device Drivers ---&gt;<br /> [ ] LED Support ---&gt; (be sure &quot;LED Support&quot; or &quot;GPIO connected LEDs&quot; (hereafter) is unchecked)<br /> &lt; &gt; LED Support for GPIO connected LEDs<br /> &lt;/pre&gt;<br /> * Save your new configuration and rebuild your kernel (if needed)<br /> &lt;pre class=&quot;host&quot;&gt;<br /> $ make<br /> &lt;/pre&gt;<br /> * and reflash your kernel (if needed)<br /> <br /> ==Usage==<br /> ===Blink APFxxDev i.MX LED===<br /> * Find the GPIO number connected to the LED, eg:<br /> ** for APF27Dev: '''PF14 -&gt;''' PortF (n°6) pin 14 -&gt; (6-1)*32 + 14 -&gt; GPIO n°'''174'''<br /> ** for APF51Dev/APF6Dev: GPIO1_2 -&gt; Port 1 pin 2 -&gt; GPIO n° 2<br /> ** for APF28Dev: Bank 0, pin 21 -&gt; GPIO n° 21 (0*32 + 21)<br /> * Define envt variable (for portability):<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # export LED=174 (APF27Dev)<br /> or<br /> # export LED=2 (APF51Dev)<br /> or<br /> # export LED=21 (APF28Dev)<br /> &lt;/pre&gt;<br /> * Ask kernel to export the GPIO:<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # echo $LED &gt; /sys/class/gpio/export<br /> &lt;/pre&gt;<br /> * Access functions are created:<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # ls /sys/class/gpio/gpio$LED/<br /> active_low edge subsystem value<br /> direction power uevent<br /> &lt;/pre&gt;<br /> * Check GPIO direction and put in output:<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # cat /sys/class/gpio/gpio$LED/direction<br /> in<br /> # echo out &gt; /sys/class/gpio/gpio$LED/direction<br /> # cat /sys/class/gpio/gpio$LED/direction<br /> out<br /> &lt;/pre&gt;<br /> * Play with GPIO value to blink LED:<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # echo 1 &gt; /sys/class/gpio/gpio$LED/value<br /> # echo 0 &gt; /sys/class/gpio/gpio$LED/value<br /> &lt;/pre&gt;<br /> <br /> ===Get APFxxDev i.MX switch status===<br /> * Find the GPIO number connected to the switch, eg:<br /> ** for APF27Dev: '''PF13 -&gt;''' PortF (n°6) pin 13 -&gt; (6-1)*32 + 13 -&gt; '''GPIO n°173'''<br /> ** for APF51Dev/APF6Dev: '''GPIO1_3''' -&gt; Port 1 pin 3 -&gt; '''GPIO n°3''' ((1-1)*32 + 3)<br /> ** for APF28Dev: Bank 0, pin 17 -&gt; GPIO n° 17 (0*32 + 17)<br /> * Define envt variable (for portability):<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # export SWITCH=173 (APF27Dev)<br /> or<br /> # export SWITCH=3 (APF51Dev)<br /> or<br /> # export SWITCH=17 (APF28Dev)<br /> &lt;/pre&gt;<br /> * Ask kernel to export the GPIO:<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # echo $SWITCH &gt; /sys/class/gpio/export<br /> &lt;/pre&gt;<br /> * Access functions are created:<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # ls /sys/class/gpio/gpio$SWITCH/<br /> active_low edge subsystem value<br /> direction power uevent<br /> &lt;/pre&gt;<br /> * Check GPIO direction and put in output:<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # cat /sys/class/gpio/gpio$SWITCH/direction<br /> in<br /> &lt;/pre&gt;<br /> * Get switch status:<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # cat /sys/class/gpio/gpio$SWITCH/value<br /> 1 (released)<br /> ...<br /> # cat /sys/class/gpio/gpio$SWITCH/value<br /> 0 (pressed)<br /> &lt;/pre&gt;<br /> * Block until an event occur:<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # cat /sys/class/gpio/gpio$SWITCH/edge<br /> none<br /> # echo both &gt; /sys/class/gpio/gpio$SWITCH/edge<br /> &lt;/pre&gt;<br /> <br /> == AsGpio ==<br /> <br /> An example of AsDevices usage for GPIO in C can be found in armadeus BSP. To compile it:<br /> <br /> &lt;pre class=&quot;host&quot;&gt;<br /> $ cd target/demos/toggle_gpio<br /> $ make<br /> &lt;/pre&gt;<br /> <br /> ==Tips==<br /> * [[Linux_Debug#Using_DebugFS|Show already allocated GPIOS]]<br /> * ''/usr/bin/gpio_helpers.sh'' script contains 2 functions that can help usage of output GPIOs: gpio_direction_output() and gpio_set_value(). For example to set GPIO N°12 as output and set it to 0:<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # source /usr/bin/gpio_helpers.sh<br /> # gpio_direction_output 12 0<br /> &lt;/pre&gt;<br /> <br /> ==Links==<br /> * http://www.kernel.org/doc/Documentation/gpio.txt<br /> * [http://bec-systems.com/site/281/how-to-implement-an-interrupt-driven-gpio-input-in-linux how to implement an interrupt driven gpio input in linux]</div> Salocin68 http://www.armadeus.org/wiki/index.php?title=APF6&diff=12799 APF6 2014-10-21T16:23:29Z <p>Salocin68: /* Description */</p> <hr /> <div>==Description==<br /> The APF6 is a high-end [https://en.wikipedia.org/wiki/Single-board_computer Single Board Computer] targeted for advanced GUI, intensive computation and extended connectivity.<br /> <br /> Here is a list of the main features:<br /> * Processor: [http://www.freescale.com/webapp/sps/site/taxonomy.jsp?code=IMX6X_SERIES i.MX6] (single, dual or quad core Cortex-A9 @ up to 1GHz)<br /> * RAM: DDR3 1066MHz. 512Mbytes to 2GBytes. 32 ot 64bits data bus. Default capacity will be 512Mbytes.<br /> * Flash: eMMC 4Gbytes, 8 bits data bus.<br /> * Ethernet: onboard Physical (ready to use Ethernet 10/100/1000Mbit link)<br /> * USB: High speed USB OTG (OnTheGo) with onboard Physical (ready to use USB OTG link)<br /> * USB: High speed Host with integrated PHY<br /> * PCIexpress Gen2<br /> * SATA II<br /> * DVI output<br /> * TFT CMOS/LVDS interface<br /> * WiFi (option): b/g/n with u.FL antenna<br /> * Bluetooth (option): BT 4.0<br /> * Only one external supply of 3.3V required.<br /> * Mechanical dimensions: 60x50mm<br /> <br /> All the i.MX6 peripherals can be accessed through two high density [[Hirose connectors]].<br /> <br /> ==Resources==<br /> <br /> * [[Datasheet | Datasheet and schema]]<br /> <br /> ==Feature list==<br /> * [[APF6_Linux_kernel_status]]<br /> <br /> {| border=&quot;0&quot; cellpadding=&quot;5&quot; cellspacing=&quot;5&quot; summary=&quot;Hardware Add-Ons by functionnalities&quot;<br /> |----------------<br /> |- style=&quot;background:#f4f4f4; color:black; -moz-border-radius:18px;&quot;<br /> |<br /> ===Video===<br /> ====Video Out====<br /> * [[LCD]]<br /> * [[BackLight]]<br /> * [[FrameBuffer]]<br /> * [[DVI_/_HDMI|DVI/HDMI]]<br /> <br /> ====Video In====<br /> *[[Camera_interface]]<br /> <br /> ||<br /> ===Wired communication===<br /> * [[Uart]]<br /> * [[SPI]]<br /> * [[I2C]]<br /> * [[USB_Host]]<br /> * [[USB_Gadget]]<br /> * [[USB_OTG]]<br /> * [[CAN_bus_Linux_driver|CAN bus]]<br /> * [[PCIE]]<br /> <br /> ||<br /> ===Wireless communication===<br /> * [[TI driver |Jorjin chipset driver]]<br /> * [[Wifi|WiFi usage on Linux]]<br /> * [[Bluetooth|Bluetooth usage on Linux]]<br /> <br /> ===Storage===<br /> * [[MultiMediaCard]]<br /> * [[SATA]]<br /> * [[eMMC]]<br /> <br /> ===Other===<br /> * [[PWM]]<br /> * [[GPIOlib]]<br /> <br /> |}<br /> <br /> ==Development boards==<br /> * [[APF6Dev]]<br /> <br /> [[Category:MainBoards]]<br /> [[Category:Hardware]]</div> Salocin68 http://www.armadeus.org/wiki/index.php?title=GPIOlib&diff=12795 GPIOlib 2014-10-21T11:37:24Z <p>Salocin68: /* Get APFxxDev i.MX switch status */</p> <hr /> <div><br /> <br /> ==Introduction==<br /> With recent Linux kernel (&gt; 2.6.3x), there is an abstraction layer meant to ease GPIO usage: ''gpiolib''. We will explain here how to use it.<br /> <br /> For this purpose we will use the user LED and button of the button to let you operate the GPIO feature without any hardware modification.<br /> <br /> Linux provides specific drivers for [[GPIO_LEDS|LEDs]] and [[GPIO_keys|switches]] - as explained in the [http://www.kernel.org/doc/Documentation/gpio.txt Linux documentation of the GPIO] - &quot;that should be used instead of talking directly to the GPIOs; they integrate with kernel frameworks better than your userspace code could.&quot;<br /> <br /> == Datasheet gpio number correspondance ==<br /> <br /> Linux manage gpio with a simple number, but under datasheet GPIO are referenced with port number (or letter) and pin number. To convert in single integer, use following formula :<br /> <br /> * '''APF9328''': TODO.<br /> * '''APF27''': (port letter (A=0, B=1, ...) x 32 ) + pin number.<br /> ** Example : '''PF14''' = (5x32) + 14 = '''174'''<br /> * '''APF28''': (Bank number x 32) + pin number<br /> ** Example : '''GPIO_0_21''' = (0x32) + 21 = '''21'''<br /> * '''APF51''' et '''APF6''': ((Bank number - 1) x 32) + pin number<br /> ** Example : '''GPIO1_2''' = (0 x 32) + 2 = '''2'''<br /> <br /> ==Installation==<br /> * Configure Linux kernel:<br /> &lt;pre class=&quot;host&quot;&gt;<br /> $ make linux-menuconfig<br /> &lt;/pre&gt;<br /> * Enable the sysfs interface of the GPIOlib If not already done:<br /> &lt;pre class=&quot;config&quot;&gt;<br /> Device Drivers ---&gt;<br /> -*- GPIO Support ---&gt;<br /> [*] /sys/class/gpio/... (sysfs interface)<br /> &lt;/pre&gt;<br /> * In order to test the GPIOlib with the user LED and SWITCH of the board you will have to disable the [[GPIO_keys]] and [[GPIO_LEDS]] drivers that are the regular driver for such device.<br /> &lt;pre class=&quot;config&quot;&gt;<br /> Device Drivers ---&gt;<br /> Input device support ---&gt;<br /> [*] Keyboards ---&gt;<br /> &lt; &gt; GPIO Buttons (be sure GPIO Buttons is unchecked)<br /> &lt;/pre&gt;<br /> &lt;pre class=&quot;config&quot;&gt;<br /> Device Drivers ---&gt;<br /> [ ] LED Support ---&gt; (be sure &quot;LED Support&quot; or &quot;GPIO connected LEDs&quot; (hereafter) is unchecked)<br /> &lt; &gt; LED Support for GPIO connected LEDs<br /> &lt;/pre&gt;<br /> * Save your new configuration and rebuild your kernel (if needed)<br /> &lt;pre class=&quot;host&quot;&gt;<br /> $ make<br /> &lt;/pre&gt;<br /> * and reflash your kernel (if needed)<br /> <br /> ==Usage==<br /> ===Blink APFxxDev i.MX LED===<br /> * Find the GPIO number connected to the LED, eg:<br /> ** for APF27Dev: '''PF14 -&gt;''' PortF (n°6) pin 14 -&gt; (6-1)*32 + 14 -&gt; GPIO n°'''174'''<br /> ** for APF51Dev/APF6Dev: GPIO1_2 -&gt; Port 1 pin 2 -&gt; GPIO n° 2<br /> ** for APF28Dev: Bank 0, pin 21 -&gt; GPIO n° 21 (0*32 + 21)<br /> * Define envt variable (for portability):<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # export LED=174 (APF27Dev)<br /> or<br /> # export LED=2 (APF51Dev)<br /> or<br /> # export LED=21 (APF28Dev)<br /> &lt;/pre&gt;<br /> * Ask kernel to export the GPIO:<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # echo $LED &gt; /sys/class/gpio/export<br /> &lt;/pre&gt;<br /> * Access functions are created:<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # ls /sys/class/gpio/gpio$LED/<br /> active_low edge subsystem value<br /> direction power uevent<br /> &lt;/pre&gt;<br /> * Check GPIO direction and put in output:<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # cat /sys/class/gpio/gpio$LED/direction<br /> in<br /> # echo out &gt; /sys/class/gpio/gpio$LED/direction<br /> # cat /sys/class/gpio/gpio$LED/direction<br /> out<br /> &lt;/pre&gt;<br /> * Play with GPIO value to blink LED:<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # echo 1 &gt; /sys/class/gpio/gpio$LED/value<br /> # echo 0 &gt; /sys/class/gpio/gpio$LED/value<br /> &lt;/pre&gt;<br /> <br /> ===Get APFxxDev i.MX switch status===<br /> * Find the GPIO number connected to the switch, eg:<br /> ** for APF27Dev: '''PF13 -&gt;''' PortF (n°6) pin 13 -&gt; (6-1)*32 + 13 -&gt; '''GPIO n°173'''<br /> ** for APF51Dev/APF6Dev: '''GPIO1_3''' -&gt; Port 1 pin 3 -&gt; '''GPIO n°3''' ((1-1)*32 + 3)<br /> ** for APF28Dev: Bank 0, pin 17 -&gt; GPIO n° 17 (0*32 + 17)<br /> * Define envt variable (for portability):<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # export SWITCH=173 (APF27Dev)<br /> or<br /> # export SWITCH=3 (APF51Dev)<br /> or<br /> # export SWITCH=17 (APF28Dev)<br /> &lt;/pre&gt;<br /> * Ask kernel to export the GPIO:<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # echo $SWITCH &gt; /sys/class/gpio/export<br /> &lt;/pre&gt;<br /> * Access functions are created:<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # ls /sys/class/gpio/gpio$SWITCH/<br /> active_low edge subsystem value<br /> direction power uevent<br /> &lt;/pre&gt;<br /> * Check GPIO direction and put in output:<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # cat /sys/class/gpio/gpio$SWITCH/direction<br /> in<br /> &lt;/pre&gt;<br /> * Get switch status:<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # cat /sys/class/gpio/gpio$SWITCH/value<br /> 1 (released)<br /> ...<br /> # cat /sys/class/gpio/gpio$SWITCH/value<br /> 0 (pressed)<br /> &lt;/pre&gt;<br /> * Block until an event occur:<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # cat /sys/class/gpio/gpio$SWITCH/edge<br /> none<br /> # echo both &gt; /sys/class/gpio/gpio$SWITCH/edge<br /> &lt;/pre&gt;<br /> <br /> == AsGpio ==<br /> <br /> An example of AsDevices usage for GPIO in C can be found in armadeus BSP. To compile it:<br /> <br /> &lt;pre class=&quot;host&quot;&gt;<br /> $ cd target/demos/toggle_gpio<br /> $ make<br /> &lt;/pre&gt;<br /> <br /> ==Tips==<br /> * [[Linux_Debug#Using_DebugFS|Show already allocated GPIOS]]<br /> * ''/usr/bin/gpio_helpers.sh'' script contains 2 functions that can help usage of output GPIOs: gpio_direction_output() and gpio_set_value(). For example to set GPIO N°12 as output and set it to 0:<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # source /usr/bin/gpio_helpers.sh<br /> # gpio_direction_output 12 0<br /> &lt;/pre&gt;<br /> <br /> ==Links==<br /> * http://www.kernel.org/doc/Documentation/gpio.txt<br /> * [http://bec-systems.com/site/281/how-to-implement-an-interrupt-driven-gpio-input-in-linux how to implement an interrupt driven gpio input in linux]</div> Salocin68 http://www.armadeus.org/wiki/index.php?title=GPIOlib&diff=12794 GPIOlib 2014-10-21T11:37:05Z <p>Salocin68: /* Blink APFxxDev i.MX LED */</p> <hr /> <div><br /> <br /> ==Introduction==<br /> With recent Linux kernel (&gt; 2.6.3x), there is an abstraction layer meant to ease GPIO usage: ''gpiolib''. We will explain here how to use it.<br /> <br /> For this purpose we will use the user LED and button of the button to let you operate the GPIO feature without any hardware modification.<br /> <br /> Linux provides specific drivers for [[GPIO_LEDS|LEDs]] and [[GPIO_keys|switches]] - as explained in the [http://www.kernel.org/doc/Documentation/gpio.txt Linux documentation of the GPIO] - &quot;that should be used instead of talking directly to the GPIOs; they integrate with kernel frameworks better than your userspace code could.&quot;<br /> <br /> == Datasheet gpio number correspondance ==<br /> <br /> Linux manage gpio with a simple number, but under datasheet GPIO are referenced with port number (or letter) and pin number. To convert in single integer, use following formula :<br /> <br /> * '''APF9328''': TODO.<br /> * '''APF27''': (port letter (A=0, B=1, ...) x 32 ) + pin number.<br /> ** Example : '''PF14''' = (5x32) + 14 = '''174'''<br /> * '''APF28''': (Bank number x 32) + pin number<br /> ** Example : '''GPIO_0_21''' = (0x32) + 21 = '''21'''<br /> * '''APF51''' et '''APF6''': ((Bank number - 1) x 32) + pin number<br /> ** Example : '''GPIO1_2''' = (0 x 32) + 2 = '''2'''<br /> <br /> ==Installation==<br /> * Configure Linux kernel:<br /> &lt;pre class=&quot;host&quot;&gt;<br /> $ make linux-menuconfig<br /> &lt;/pre&gt;<br /> * Enable the sysfs interface of the GPIOlib If not already done:<br /> &lt;pre class=&quot;config&quot;&gt;<br /> Device Drivers ---&gt;<br /> -*- GPIO Support ---&gt;<br /> [*] /sys/class/gpio/... (sysfs interface)<br /> &lt;/pre&gt;<br /> * In order to test the GPIOlib with the user LED and SWITCH of the board you will have to disable the [[GPIO_keys]] and [[GPIO_LEDS]] drivers that are the regular driver for such device.<br /> &lt;pre class=&quot;config&quot;&gt;<br /> Device Drivers ---&gt;<br /> Input device support ---&gt;<br /> [*] Keyboards ---&gt;<br /> &lt; &gt; GPIO Buttons (be sure GPIO Buttons is unchecked)<br /> &lt;/pre&gt;<br /> &lt;pre class=&quot;config&quot;&gt;<br /> Device Drivers ---&gt;<br /> [ ] LED Support ---&gt; (be sure &quot;LED Support&quot; or &quot;GPIO connected LEDs&quot; (hereafter) is unchecked)<br /> &lt; &gt; LED Support for GPIO connected LEDs<br /> &lt;/pre&gt;<br /> * Save your new configuration and rebuild your kernel (if needed)<br /> &lt;pre class=&quot;host&quot;&gt;<br /> $ make<br /> &lt;/pre&gt;<br /> * and reflash your kernel (if needed)<br /> <br /> ==Usage==<br /> ===Blink APFxxDev i.MX LED===<br /> * Find the GPIO number connected to the LED, eg:<br /> ** for APF27Dev: '''PF14 -&gt;''' PortF (n°6) pin 14 -&gt; (6-1)*32 + 14 -&gt; GPIO n°'''174'''<br /> ** for APF51Dev/APF6Dev: GPIO1_2 -&gt; Port 1 pin 2 -&gt; GPIO n° 2<br /> ** for APF28Dev: Bank 0, pin 21 -&gt; GPIO n° 21 (0*32 + 21)<br /> * Define envt variable (for portability):<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # export LED=174 (APF27Dev)<br /> or<br /> # export LED=2 (APF51Dev)<br /> or<br /> # export LED=21 (APF28Dev)<br /> &lt;/pre&gt;<br /> * Ask kernel to export the GPIO:<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # echo $LED &gt; /sys/class/gpio/export<br /> &lt;/pre&gt;<br /> * Access functions are created:<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # ls /sys/class/gpio/gpio$LED/<br /> active_low edge subsystem value<br /> direction power uevent<br /> &lt;/pre&gt;<br /> * Check GPIO direction and put in output:<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # cat /sys/class/gpio/gpio$LED/direction<br /> in<br /> # echo out &gt; /sys/class/gpio/gpio$LED/direction<br /> # cat /sys/class/gpio/gpio$LED/direction<br /> out<br /> &lt;/pre&gt;<br /> * Play with GPIO value to blink LED:<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # echo 1 &gt; /sys/class/gpio/gpio$LED/value<br /> # echo 0 &gt; /sys/class/gpio/gpio$LED/value<br /> &lt;/pre&gt;<br /> <br /> ===Get APFxxDev i.MX switch status===<br /> * Find the GPIO number connected to the switch, eg:<br /> ** for APF27Dev: '''PF13 -&gt;''' PortF (n°6) pin 13 -&gt; (6-1)*32 + 13 -&gt; '''GPIO n°173'''<br /> ** for APF51Dev: '''GPIO1_3''' -&gt; Port 1 pin 3 -&gt; '''GPIO n°3''' ((1-1)*32 + 3)<br /> ** for APF28Dev: Bank 0, pin 17 -&gt; GPIO n° 17 (0*32 + 17)<br /> * Define envt variable (for portability):<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # export SWITCH=173 (APF27Dev)<br /> or<br /> # export SWITCH=3 (APF51Dev)<br /> or<br /> # export SWITCH=17 (APF28Dev)<br /> &lt;/pre&gt;<br /> * Ask kernel to export the GPIO:<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # echo $SWITCH &gt; /sys/class/gpio/export<br /> &lt;/pre&gt;<br /> * Access functions are created:<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # ls /sys/class/gpio/gpio$SWITCH/<br /> active_low edge subsystem value<br /> direction power uevent<br /> &lt;/pre&gt;<br /> * Check GPIO direction and put in output:<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # cat /sys/class/gpio/gpio$SWITCH/direction<br /> in<br /> &lt;/pre&gt;<br /> * Get switch status:<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # cat /sys/class/gpio/gpio$SWITCH/value<br /> 1 (released)<br /> ...<br /> # cat /sys/class/gpio/gpio$SWITCH/value<br /> 0 (pressed)<br /> &lt;/pre&gt;<br /> * Block until an event occur:<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # cat /sys/class/gpio/gpio$SWITCH/edge<br /> none<br /> # echo both &gt; /sys/class/gpio/gpio$SWITCH/edge<br /> &lt;/pre&gt;<br /> <br /> == AsGpio ==<br /> <br /> An example of AsDevices usage for GPIO in C can be found in armadeus BSP. To compile it:<br /> <br /> &lt;pre class=&quot;host&quot;&gt;<br /> $ cd target/demos/toggle_gpio<br /> $ make<br /> &lt;/pre&gt;<br /> <br /> ==Tips==<br /> * [[Linux_Debug#Using_DebugFS|Show already allocated GPIOS]]<br /> * ''/usr/bin/gpio_helpers.sh'' script contains 2 functions that can help usage of output GPIOs: gpio_direction_output() and gpio_set_value(). For example to set GPIO N°12 as output and set it to 0:<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # source /usr/bin/gpio_helpers.sh<br /> # gpio_direction_output 12 0<br /> &lt;/pre&gt;<br /> <br /> ==Links==<br /> * http://www.kernel.org/doc/Documentation/gpio.txt<br /> * [http://bec-systems.com/site/281/how-to-implement-an-interrupt-driven-gpio-input-in-linux how to implement an interrupt driven gpio input in linux]</div> Salocin68 http://www.armadeus.org/wiki/index.php?title=GPIOlib&diff=12793 GPIOlib 2014-10-21T11:36:04Z <p>Salocin68: /* Datasheet gpio number correspondance */</p> <hr /> <div><br /> <br /> ==Introduction==<br /> With recent Linux kernel (&gt; 2.6.3x), there is an abstraction layer meant to ease GPIO usage: ''gpiolib''. We will explain here how to use it.<br /> <br /> For this purpose we will use the user LED and button of the button to let you operate the GPIO feature without any hardware modification.<br /> <br /> Linux provides specific drivers for [[GPIO_LEDS|LEDs]] and [[GPIO_keys|switches]] - as explained in the [http://www.kernel.org/doc/Documentation/gpio.txt Linux documentation of the GPIO] - &quot;that should be used instead of talking directly to the GPIOs; they integrate with kernel frameworks better than your userspace code could.&quot;<br /> <br /> == Datasheet gpio number correspondance ==<br /> <br /> Linux manage gpio with a simple number, but under datasheet GPIO are referenced with port number (or letter) and pin number. To convert in single integer, use following formula :<br /> <br /> * '''APF9328''': TODO.<br /> * '''APF27''': (port letter (A=0, B=1, ...) x 32 ) + pin number.<br /> ** Example : '''PF14''' = (5x32) + 14 = '''174'''<br /> * '''APF28''': (Bank number x 32) + pin number<br /> ** Example : '''GPIO_0_21''' = (0x32) + 21 = '''21'''<br /> * '''APF51''' et '''APF6''': ((Bank number - 1) x 32) + pin number<br /> ** Example : '''GPIO1_2''' = (0 x 32) + 2 = '''2'''<br /> <br /> ==Installation==<br /> * Configure Linux kernel:<br /> &lt;pre class=&quot;host&quot;&gt;<br /> $ make linux-menuconfig<br /> &lt;/pre&gt;<br /> * Enable the sysfs interface of the GPIOlib If not already done:<br /> &lt;pre class=&quot;config&quot;&gt;<br /> Device Drivers ---&gt;<br /> -*- GPIO Support ---&gt;<br /> [*] /sys/class/gpio/... (sysfs interface)<br /> &lt;/pre&gt;<br /> * In order to test the GPIOlib with the user LED and SWITCH of the board you will have to disable the [[GPIO_keys]] and [[GPIO_LEDS]] drivers that are the regular driver for such device.<br /> &lt;pre class=&quot;config&quot;&gt;<br /> Device Drivers ---&gt;<br /> Input device support ---&gt;<br /> [*] Keyboards ---&gt;<br /> &lt; &gt; GPIO Buttons (be sure GPIO Buttons is unchecked)<br /> &lt;/pre&gt;<br /> &lt;pre class=&quot;config&quot;&gt;<br /> Device Drivers ---&gt;<br /> [ ] LED Support ---&gt; (be sure &quot;LED Support&quot; or &quot;GPIO connected LEDs&quot; (hereafter) is unchecked)<br /> &lt; &gt; LED Support for GPIO connected LEDs<br /> &lt;/pre&gt;<br /> * Save your new configuration and rebuild your kernel (if needed)<br /> &lt;pre class=&quot;host&quot;&gt;<br /> $ make<br /> &lt;/pre&gt;<br /> * and reflash your kernel (if needed)<br /> <br /> ==Usage==<br /> ===Blink APFxxDev i.MX LED===<br /> * Find the GPIO number connected to the LED, eg:<br /> ** for APF27Dev: '''PF14 -&gt;''' PortF (n°6) pin 14 -&gt; (6-1)*32 + 14 -&gt; GPIO n°'''174'''<br /> ** for APF51Dev: GPIO1_2 -&gt; Port 1 pin 2 -&gt; GPIO n° 2<br /> ** for APF28Dev: Bank 0, pin 21 -&gt; GPIO n° 21 (0*32 + 21)<br /> * Define envt variable (for portability):<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # export LED=174 (APF27Dev)<br /> or<br /> # export LED=2 (APF51Dev)<br /> or<br /> # export LED=21 (APF28Dev)<br /> &lt;/pre&gt;<br /> * Ask kernel to export the GPIO:<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # echo $LED &gt; /sys/class/gpio/export<br /> &lt;/pre&gt;<br /> * Access functions are created:<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # ls /sys/class/gpio/gpio$LED/<br /> active_low edge subsystem value<br /> direction power uevent<br /> &lt;/pre&gt;<br /> * Check GPIO direction and put in output:<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # cat /sys/class/gpio/gpio$LED/direction<br /> in<br /> # echo out &gt; /sys/class/gpio/gpio$LED/direction<br /> # cat /sys/class/gpio/gpio$LED/direction<br /> out<br /> &lt;/pre&gt;<br /> * Play with GPIO value to blink LED:<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # echo 1 &gt; /sys/class/gpio/gpio$LED/value<br /> # echo 0 &gt; /sys/class/gpio/gpio$LED/value<br /> &lt;/pre&gt;<br /> <br /> ===Get APFxxDev i.MX switch status===<br /> * Find the GPIO number connected to the switch, eg:<br /> ** for APF27Dev: '''PF13 -&gt;''' PortF (n°6) pin 13 -&gt; (6-1)*32 + 13 -&gt; '''GPIO n°173'''<br /> ** for APF51Dev: '''GPIO1_3''' -&gt; Port 1 pin 3 -&gt; '''GPIO n°3''' ((1-1)*32 + 3)<br /> ** for APF28Dev: Bank 0, pin 17 -&gt; GPIO n° 17 (0*32 + 17)<br /> * Define envt variable (for portability):<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # export SWITCH=173 (APF27Dev)<br /> or<br /> # export SWITCH=3 (APF51Dev)<br /> or<br /> # export SWITCH=17 (APF28Dev)<br /> &lt;/pre&gt;<br /> * Ask kernel to export the GPIO:<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # echo $SWITCH &gt; /sys/class/gpio/export<br /> &lt;/pre&gt;<br /> * Access functions are created:<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # ls /sys/class/gpio/gpio$SWITCH/<br /> active_low edge subsystem value<br /> direction power uevent<br /> &lt;/pre&gt;<br /> * Check GPIO direction and put in output:<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # cat /sys/class/gpio/gpio$SWITCH/direction<br /> in<br /> &lt;/pre&gt;<br /> * Get switch status:<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # cat /sys/class/gpio/gpio$SWITCH/value<br /> 1 (released)<br /> ...<br /> # cat /sys/class/gpio/gpio$SWITCH/value<br /> 0 (pressed)<br /> &lt;/pre&gt;<br /> * Block until an event occur:<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # cat /sys/class/gpio/gpio$SWITCH/edge<br /> none<br /> # echo both &gt; /sys/class/gpio/gpio$SWITCH/edge<br /> &lt;/pre&gt;<br /> <br /> == AsGpio ==<br /> <br /> An example of AsDevices usage for GPIO in C can be found in armadeus BSP. To compile it:<br /> <br /> &lt;pre class=&quot;host&quot;&gt;<br /> $ cd target/demos/toggle_gpio<br /> $ make<br /> &lt;/pre&gt;<br /> <br /> ==Tips==<br /> * [[Linux_Debug#Using_DebugFS|Show already allocated GPIOS]]<br /> * ''/usr/bin/gpio_helpers.sh'' script contains 2 functions that can help usage of output GPIOs: gpio_direction_output() and gpio_set_value(). For example to set GPIO N°12 as output and set it to 0:<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # source /usr/bin/gpio_helpers.sh<br /> # gpio_direction_output 12 0<br /> &lt;/pre&gt;<br /> <br /> ==Links==<br /> * http://www.kernel.org/doc/Documentation/gpio.txt<br /> * [http://bec-systems.com/site/281/how-to-implement-an-interrupt-driven-gpio-input-in-linux how to implement an interrupt driven gpio input in linux]</div> Salocin68 http://www.armadeus.org/wiki/index.php?title=APF6&diff=12792 APF6 2014-10-21T11:35:11Z <p>Salocin68: /* Feature list */</p> <hr /> <div>==Description==<br /> The APF51 is a high-end [https://en.wikipedia.org/wiki/Single-board_computer Single Board Computer] targeted for advanced GUI, intensive computation and extended connectivity.<br /> <br /> Here is a list of the main features:<br /> * Processor: [http://www.freescale.com/webapp/sps/site/taxonomy.jsp?code=IMX6X_SERIES i.MX6] (single, dual or quad core Cortex-A9 @ 1GHz)<br /> * RAM: DDR3 1086. 512Mbytes to 2GBytes. 32 ot 64bits data bus. Default capacity will be 512Mbytes.<br /> * Flash: eMMC 4Gbytes, 8 bits data bus.<br /> * Ethernet: onboard Physical (ready to use Ethernet 10/100/1000Mbit link)<br /> * USB: High speed USB OTG (OnTheGo) with onboard Physical (ready to use USB OTG link)<br /> * USB: High speed Host with integrated PHY<br /> * PCIexpress Gen2<br /> * SATA II<br /> * DVI output<br /> * TFT CMOS/LVDS interface<br /> * WiFi (option): b/g/n with u.FL antenna<br /> * Bluetooth (option): BT 4.0<br /> * Only one external supply of 3.3V required.<br /> * Mechanical dimensions: 60x50mm<br /> <br /> All the i.MX6 peripherals can be accessed through two high density [[Hirose connectors]].<br /> <br /> ==Resources==<br /> <br /> * [[Datasheet | Datasheet and schema]]<br /> <br /> ==Feature list==<br /> * [[APF6_Linux_kernel_status]]<br /> <br /> {| border=&quot;0&quot; cellpadding=&quot;5&quot; cellspacing=&quot;5&quot; summary=&quot;Hardware Add-Ons by functionnalities&quot;<br /> |----------------<br /> |- style=&quot;background:#f4f4f4; color:black; -moz-border-radius:18px;&quot;<br /> |<br /> ===Video===<br /> ====Video Out====<br /> * [[LCD]]<br /> * [[BackLight]]<br /> * [[FrameBuffer]]<br /> * [[DVI_/_HDMI|DVI/HDMI]]<br /> <br /> ====Video In====<br /> *[[Camera_interface]]<br /> <br /> ||<br /> ===Wired communication===<br /> * [[Uart]]<br /> * [[SPI]]<br /> * [[I2C]]<br /> * [[USB_Host]]<br /> * [[USB_Gadget]]<br /> * [[USB_OTG]]<br /> * [[CAN_bus_Linux_driver|CAN bus]]<br /> * [[PCIE]]<br /> <br /> ||<br /> ===Wireless communication===<br /> * [[TI driver |Jorjin chipset driver]]<br /> * [[Wifi|WiFi usage on Linux]]<br /> * [[Bluetooth|Bluetooth usage on Linux]]<br /> <br /> ===Storage===<br /> * [[MultiMediaCard]]<br /> * [[SATA]]<br /> * [[eMMC]]<br /> <br /> ===Other===<br /> * [[PWM]]<br /> * [[GPIOlib]]<br /> <br /> |}<br /> <br /> ==Development boards==<br /> * [[APF6Dev]]<br /> <br /> [[Category:MainBoards]]<br /> [[Category:Hardware]]</div> Salocin68 http://www.armadeus.org/wiki/index.php?title=APF6&diff=12791 APF6 2014-10-21T11:35:04Z <p>Salocin68: /* Feature list */</p> <hr /> <div>==Description==<br /> The APF51 is a high-end [https://en.wikipedia.org/wiki/Single-board_computer Single Board Computer] targeted for advanced GUI, intensive computation and extended connectivity.<br /> <br /> Here is a list of the main features:<br /> * Processor: [http://www.freescale.com/webapp/sps/site/taxonomy.jsp?code=IMX6X_SERIES i.MX6] (single, dual or quad core Cortex-A9 @ 1GHz)<br /> * RAM: DDR3 1086. 512Mbytes to 2GBytes. 32 ot 64bits data bus. Default capacity will be 512Mbytes.<br /> * Flash: eMMC 4Gbytes, 8 bits data bus.<br /> * Ethernet: onboard Physical (ready to use Ethernet 10/100/1000Mbit link)<br /> * USB: High speed USB OTG (OnTheGo) with onboard Physical (ready to use USB OTG link)<br /> * USB: High speed Host with integrated PHY<br /> * PCIexpress Gen2<br /> * SATA II<br /> * DVI output<br /> * TFT CMOS/LVDS interface<br /> * WiFi (option): b/g/n with u.FL antenna<br /> * Bluetooth (option): BT 4.0<br /> * Only one external supply of 3.3V required.<br /> * Mechanical dimensions: 60x50mm<br /> <br /> All the i.MX6 peripherals can be accessed through two high density [[Hirose connectors]].<br /> <br /> ==Resources==<br /> <br /> * [[Datasheet | Datasheet and schema]]<br /> <br /> ==Feature list==<br /> * [[APF6_Linux_kernel_status]]<br /> <br /> {| border=&quot;0&quot; cellpadding=&quot;5&quot; cellspacing=&quot;5&quot; summary=&quot;Hardware Add-Ons by functionnalities&quot;<br /> |----------------<br /> |- style=&quot;background:#f4f4f4; color:black; -moz-border-radius:18px;&quot;<br /> |<br /> ===Video===<br /> ====Video Out====<br /> * [[LCD]]<br /> * [[BackLight]]<br /> * [[FrameBuffer]]<br /> * [[DVI_/_HDMI|DVI/HDMI]]<br /> <br /> ====Video In====<br /> *[[Camera_interface]]<br /> <br /> ||<br /> ===Wired communication===<br /> * [[Uart]]<br /> * [[SPI]]<br /> * [[I2C]]<br /> * [[USB_Host]]<br /> * [[USB_Gadget]]<br /> * [[USB_OTG]]<br /> * [[CAN_bus_Linux_driver|CAN bus]]<br /> * [[PCIE]]<br /> <br /> ||<br /> ===Wireless communication===<br /> ** [[TI driver |Jorjin chipset driver]]<br /> * [[Wifi|WiFi usage on Linux]]<br /> * [[Bluetooth|Bluetooth usage on Linux]]<br /> <br /> ===Storage===<br /> * [[MultiMediaCard]]<br /> * [[SATA]]<br /> * [[eMMC]]<br /> <br /> ===Other===<br /> * [[PWM]]<br /> * [[GPIOlib]]<br /> <br /> |}<br /> <br /> ==Development boards==<br /> * [[APF6Dev]]<br /> <br /> [[Category:MainBoards]]<br /> [[Category:Hardware]]</div> Salocin68 http://www.armadeus.org/wiki/index.php?title=MultiMediaCard&diff=12790 MultiMediaCard 2014-10-21T11:27:10Z <p>Salocin68: /* Introduction */</p> <hr /> <div>Instructions to use the MultiMediaCard (MMC/SD) on your Armadeus board<br /> <br /> ==Introduction==<br /> <br /> You can use standard MMC/SD/miniSD/microSD cards with your Armadeus board:<br /> * with an APF9328 DevLight V1, you must have [[MMC/SD | the corresponding connector attached to your development board.]] and use an adaptor for miniSD and microSD,<br /> * with an APF9328 DevLight V2, you can use the onboard microSD connector,<br /> * with an [[APF9328DevFull]], you can use the MMC/SD onboard connector and an adaptor for miniSD and microSD,<br /> * with an [[APF27Dev]], an [[APF28Dev]], an [[APF51Dev]] or an [[APF6Dev]], you can use the onboard microSD connector.<br /> <br /> All needed drivers are included in the standard Armadeus Linux image.<br /> <br /> ==Card insertion==<br /> You should see something like that on the Linux console:<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # imx-mmc imx-mmc.0: card inserted<br /> mmc0: host does not support reading read-only switch. assuming write-enable.<br /> mmc0: new SD card at address 01b0<br /> mmcblk0: mmc0:01b0 SD512 500224KiB<br /> mmcblk0: p1<br /> &lt;/pre&gt;<br /> <br /> ==Mounting the MMC/SD==<br /> <br /> * Just mount the MMC like you will do on your PC:<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # mount /dev/mmcblk0p1 /media/mmc<br /> &lt;/pre&gt;<br /> * Then, you can access the MMC's files from the ''/media/mmc'' directory<br /> <br /> If you have problems with vfat code page, [[MultiMediaCard#VFAT_Code_Page|include the missing code page into the kernel]].<br /> <br /> ==Booting from MMC/SD==<br /> When your rootfs is too big to be put on the APF Flash, you can always use a MMC/SD like a Hard Drive and boot from it (this is possible because standard Armadeus kernel is compiled with the MMC driver built in).<br /> <br /> ===Prepare your card===<br /> * On your APF board (to avoid to crash your Host HD), create a good partition table:<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # /sbin/fdisk /dev/mmcblk0<br /> Delete all existing partion with 'd'<br /> Create a primary partion: 'n' then 'p' then '1'<br /> Change bootflag to Linux: 't' then '83'<br /> Save partition table: 'w'<br /> (To quit without saving: 'm')<br /> &lt;/pre&gt;<br /> * Then, on your PC, format your MMC with Ext2 filesystem (booting on FAT is bad :-) ):<br /> &lt;pre class=&quot;host&quot;&gt;<br /> $ sudo mkfs.ext2 /dev/sdX1 (replace X with your MMC reader drive letter, if your Laptop has an integrated<br /> MMC reader then use mmcblk0p1 instead of sdX1)<br /> &lt;/pre&gt;<br /> * If not automatically detected/mounted by your distribution, mount your MMC/SD on your Host filesystem (for example in ''/media/mmc''):<br /> &lt;pre class=&quot;host&quot;&gt;<br /> $ sudo mkdir -p /media/mmc<br /> $ sudo mount /dev/sdX1 /media/mmc (replace X with your MMC reader drive letter, if your Laptop has an integrated<br /> MMC reader then use mmcblk0p1 instead of sdX1)<br /> &lt;/pre&gt;<br /> <br /> ===Put your rootfs and Linux kernel on the MMC/SD===<br /> * Buildroot should be configured to generate a tar-ed rootfs '''(done by default)''', if not:<br /> &lt;pre class=&quot;host&quot;&gt;<br /> $ make menuconfig<br /> &lt;/pre&gt;<br /> <br /> &lt;pre class=&quot;config&quot;&gt;<br /> Filesystem images ---&gt;<br /> ...<br /> [*] tar the root filesystem<br /> Compression method (no compression) ---&gt;<br /> () other random options to pass to tar<br /> ...<br /> &lt;/pre&gt;<br /> <br /> &lt;pre class=&quot;host&quot;&gt;<br /> $ make<br /> &lt;/pre&gt;<br /> * and then uncompress the rootfs to the SD card (mounted as /media/mmc on your PC here). You can also copy the Linux kernel to the rootfs ''/boot'' folder:<br /> {{Note | The APF51 (with U-Boot version older than 2013.04) and the APF9328 do not load the kernel from the SD card but use the one in Flash instead. }}<br /> &lt;pre class=&quot;host&quot;&gt;<br /> $ make shell_env<br /> $ source armadeus_env.sh<br /> $ sudo tar xvf $ARMADEUS_ROOTFS_TAR -C /media/mmc<br /> $ sudo mkdir -p /media/mmct/boot<br /> $ sudo cp $ARMADEUS_BINARIES/$ARMADEUS_BOARD_NAME-linux.bin /media/mmc/boot<br /> $ sudo umount /media/mmc<br /> &lt;/pre&gt;<br /> <br /> ===Boot===<br /> * Insert the MMC/SD/microSD in the corresponding slot of your Armadeus board and then under U-Boot do:<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> BIOS&gt; run mmcboot<br /> &lt;/pre&gt;<br /> * if you want to automatically boot from SD at each startup, modify the ''bootcmd'' U-Boot macro:<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> BIOS&gt; setenv bootcmd run mmcboot<br /> BIOS&gt; saveenv<br /> &lt;/pre&gt;<br /> (default bootcmd when you receive your board is ''run jffsboot'' = boot from FLASH)<br /> <br /> ==Performances==<br /> * [[MMC/SD#Supported_Cards| Show tested cards performances]]<br /> <br /> ==Troubleshots==<br /> ===VFAT Code Page===<br /> If you encounter this message (or something similar):<br /> Unable to load NLS charset cp437<br /> FAT: codepage cp437 not found<br /> you have to add the charset to the supported kernel ones:<br /> $ make linux-menuconfig<br /> &lt;pre class=&quot;config&quot;&gt;<br /> File systems ---&gt; <br /> -*- Native language support ---&gt;<br /> &lt;*&gt; Codepage 437 (United States, Canada)<br /> ...<br /> &lt;*&gt; NLS ISO 8859-1 (Latin 1; Western European Languages)<br /> ...<br /> &lt;/pre&gt;<br /> <br /> ==U-Boot usage==<br /> SD cards can also be used with U-Boot.<br /> The following commands are useful:<br /> * Scan the MMC:<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> BIOS&gt; mmc rescan<br /> &lt;/pre&gt;<br /> * List the MMC content:<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> BIOS&gt; fatls mmc 0<br /> &lt;/pre&gt;<br /> * Load the file xxx.bin in RAM:<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> BIOS&gt; fatload mmc 0 ${loadaddr} xxx.bin<br /> &lt;/pre&gt;<br /> <br /> ==Links==<br /> <br /> * http://en.wikipedia.org/wiki/MultiMedia_Card<br /> <br /> [[Category:MassStorage]]</div> Salocin68 http://www.armadeus.org/wiki/index.php?title=APF6Dev&diff=12789 APF6Dev 2014-10-21T11:25:37Z <p>Salocin68: /* Feature list */</p> <hr /> <div>==Description==<br /> This is the Armadeus System's standard development board/baseboard for the [[APF6]] module.<br /> <br /> The following options are available:<br /> * [[GPS]]<br /> * [[Gsm|GSM]]<br /> <br /> ==Errata==<br /> <br /> <br /> ==Resources==<br /> <br /> * [[Datasheet | Datasheet and schema]]<br /> * [http://www.armadeus.com/english/products-development_boards-apf6_dev.html Product page on Armadeus Systems website]<br /> <br /> ==Feature list==<br /> <br /> {| border=&quot;0&quot; cellpadding=&quot;5&quot; cellspacing=&quot;5&quot; summary=&quot;Hardware Add-Ons by functionnalities&quot;<br /> |----------------<br /> |- style=&quot;background:#f4f4f4; color:black; -moz-border-radius:18px;&quot;<br /> |<br /> <br /> ===Audio===<br /> * [[SGTL5000]]: audio in/out<br /> * [[ALSA]]<br /> <br /> <br /> ===Video Out===<br /> * [[LCD]]<br /> * [[BackLight]]<br /> * [[FrameBuffer]]<br /> * [[DVI_/_HDMI|DVI/HDMI]]<br /> <br /> ===Video In===<br /> *[[Camera interface]]<br /> ||<br /> ===User Input===<br /> * [[SX8654|touchscreen]]<br /> <br /> ===Wired communication===<br /> * [[Uart|UART]]<br /> * [[SPI]]<br /> * [[I2C]]<br /> * [[USB Host]] <br /> * [[USB_OTG]]<br /> * [[USB_Gadget]]<br /> * [[CAN_bus_Linux_driver|CAN bus]]<br /> * [[PCIE]]<br /> <br /> ===Storage===<br /> * [[MultiMediaCard]]<br /> * [[SATA]]<br /> ||<br /> ===Realtime===<br /> * [[MCP79400|RTC]]<br /> <br /> ===Wireless communication===<br /> * [[Wifi|WiFi usage on Linux]]<br /> * [[Bluetooth|Bluetooth usage on Linux]]<br /> <br /> ===Other===<br /> * [[PWM]]: PWM output is on J22 pin 4 &lt;br&gt;(2.8V output, if configured as output)<br /> * [[GPIOlib]]<br /> * [[JTAG]]<br /> <br /> <br /> [[Category:DevelopmentBoards]]<br /> [[Category:Hardware]]</div> Salocin68 http://www.armadeus.org/wiki/index.php?title=APF6Dev&diff=12788 APF6Dev 2014-10-21T11:23:56Z <p>Salocin68: /* Feature list */</p> <hr /> <div>==Description==<br /> This is the Armadeus System's standard development board/baseboard for the [[APF6]] module.<br /> <br /> The following options are available:<br /> * [[GPS]]<br /> * [[Gsm|GSM]]<br /> <br /> ==Errata==<br /> <br /> <br /> ==Resources==<br /> <br /> * [[Datasheet | Datasheet and schema]]<br /> * [http://www.armadeus.com/english/products-development_boards-apf6_dev.html Product page on Armadeus Systems website]<br /> <br /> ==Feature list==<br /> <br /> {| border=&quot;0&quot; cellpadding=&quot;5&quot; cellspacing=&quot;5&quot; summary=&quot;Hardware Add-Ons by functionnalities&quot;<br /> |----------------<br /> |- style=&quot;background:#f4f4f4; color:black; -moz-border-radius:18px;&quot;<br /> |<br /> <br /> ===Audio===<br /> * [[SGTL5000]]: audio in/out<br /> * [[ALSA]]<br /> <br /> <br /> ===Video Out===<br /> * [[LCD]]<br /> * [[BackLight]]<br /> * [[FrameBuffer]]<br /> * [[DVI_/_HDMI|DVI/HDMI]]<br /> <br /> ===Video In===<br /> *[[Camera interface]]<br /> ||<br /> ===User Input===<br /> * [[Keypad]]<br /> * [[SX8654|touchscreen]]<br /> <br /> ===Wired communication===<br /> * [[Uart|UART]]<br /> * [[SPI]]<br /> * [[I2C]]<br /> * [[USB Host]] <br /> * [[USB_OTG]]<br /> * [[USB_Gadget]]<br /> * [[CAN_bus_Linux_driver|CAN bus]]<br /> * [[PCIE]]<br /> <br /> ===Storage===<br /> * [[MultiMediaCard]]<br /> * [[SATA]]<br /> ||<br /> ===Realtime===<br /> * [[MCP79400|RTC]]<br /> <br /> ===Wireless communication===<br /> * [[Wifi|WiFi usage on Linux]]<br /> * [[Bluetooth|Bluetooth usage on Linux]]<br /> <br /> ===Other===<br /> * [[PWM]]: PWM output is on J22 pin 4 &lt;br&gt;(2.8V output, if configured as output)<br /> * [[GPIOlib]]<br /> * [[JTAG]]<br /> <br /> <br /> [[Category:DevelopmentBoards]]<br /> [[Category:Hardware]]</div> Salocin68 http://www.armadeus.org/wiki/index.php?title=CAN_bus_Linux_driver&diff=12787 CAN bus Linux driver 2014-10-21T11:23:17Z <p>Salocin68: /* Driver installation */</p> <hr /> <div>The current CAN bus driver uses SocketCAN API which is now the official CAN API for Linux.<br /> SocketCAN is based on the Linux socket. Further details can be found on the links at the bottom of this page.<br /> <br /> {{Warning| Please ensure that you use the trunk version of armadeus (kernel version greater or equal to linux-2.6.38 is required) before trying the instructions described on this page ! With older kernel versions you may not be able to change the bitrate.}}<br /> <br /> ==Driver installation==<br /> * Nothing has to be done for the [[APF51Dev]], the [[APF28Dev]] and the [[APF6Dev]].<br /> * For the [[APF27Dev|APF27DevFull]]:<br /> &lt;pre class=&quot;host&quot;&gt;<br /> $ make linux-menuconfig<br /> &lt;/pre&gt;<br /> <br /> &lt;pre class=&quot;config&quot;&gt;<br /> Networking support ---&gt;<br /> &lt;M&gt; CAN bus subsystem support ---&gt; <br /> --- CAN bus subsystem support<br /> &lt;M&gt; Raw CAN Protocol (raw access with CAN-ID filtering)<br /> &lt;M&gt; Broadcast Manager CAN Protocol (with content filtering)<br /> CAN Device Drivers ---&gt;<br /> &lt;M&gt; Virtual Local CAN Interface (vcan)<br /> &lt;M&gt; Platform CAN drivers with Netlink support<br /> [*] CAN bit-timing calculation <br /> &lt;M&gt; Microchip 251x series SPI CAN Controller<br /> &lt;/pre&gt;<br /> <br /> &lt;pre class=&quot;host&quot;&gt;<br /> $ make linux<br /> $ make<br /> &lt;/pre&gt;<br /> * Reflash kernel and rootfs<br /> <br /> ==Usage==<br /> * Load all the needed drivers:<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> modprobe can<br /> modprobe can-dev<br /> modprobe can-raw <br /> modprobe mcp251x # on APF27 &amp; APF51 only<br /> modprobe flexcan # on APF6 only<br /> &lt;/pre&gt;<br /> * Set the bitrate before all operations<br /> Example:<br /> Set the bitrate of the can0 interface to 125kbps:<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # ip link set can0 up type can bitrate 125000<br /> &lt;/pre&gt;<br /> <br /> {{Note| An error occurs when you try to set the bitrate with an old Linux kernel. }}<br /> <br /> * If the following error occurs when you do the last instruction :<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> ip: either &quot;dev&quot; is duplicate, or &quot;type&quot; is garbage<br /> &lt;/pre&gt;<br /> <br /> check that this command:<br /> <br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # which ip<br /> &lt;/pre&gt;<br /> <br /> return this message:<br /> <br /> &lt;pre class=&quot;apf&quot;&gt;<br /> /sbin/ip<br /> &lt;/pre&gt;<br /> <br /> and not this one :<br /> <br /> &lt;pre class=&quot;apf&quot;&gt;<br /> /bin/ip<br /> &lt;/pre&gt;<br /> <br /> If the binary is installed in ''/bin'' instead of ''/sbin'', the executable file is a link to busybox and the command to set the bitrate doesn't work on busybox, so try the following instructions:<br /> <br /> &lt;pre class=&quot;host&quot;&gt;<br /> $ make busybox-clean<br /> $ make busybox-dirclean<br /> $ make menuconfig<br /> &lt;/pre&gt;<br /> <br /> &lt;pre class=&quot;config&quot;&gt;<br /> Package Selection for the target ---&gt;<br /> Networking applications ---&gt;<br /> [*] iproute2<br /> &lt;/pre&gt;<br /> <br /> &lt;pre class=&quot;host&quot;&gt;<br /> $ make <br /> &lt;/pre&gt;<br /> <br /> Then, reflash your rootfs.<br /> <br /> ==Quick test==<br /> Once the driver installed and the bitrate is set, the CAN interface has to be started like a standard net interface<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # ifconfig can0 up<br /> &lt;/pre&gt;<br /> and can be stopped like that:<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # ifconfig can0 down<br /> &lt;/pre&gt;<br /> The socketCAN version can be retrieved like that:<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # cat /proc/net/can/version<br /> &lt;/pre&gt;<br /> The socketCAN statistics can be retrieved like that:<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # cat /proc/net/can/stats<br /> &lt;/pre&gt;<br /> <br /> ==Userspace tools==<br /> Several tools are provided by socketCAN:<br /> *'''candump''': dump traffic on a CAN network<br /> The following command shows the received message from the CAN bus<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> candump can0<br /> &lt;/pre&gt;<br /> *'''cansend''': simple command line tool to send CAN-frames via CAN_RAW sockets <br /> exemple :<br /> The following command sends 3 bytes on the bus (0x1E, 0x10, 0x10) with the identifier 500.<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> cansend can0 500#1E.10.10<br /> &lt;/pre&gt;<br /> You can send a remote request message<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> cansend can0 500#R<br /> &lt;/pre&gt;<br /> The information with the identifier 500 will be available on the bus when the device receive the remote request message<br /> *'''cangen''': CAN frames generator for testing purpose<br /> *'''canplayer''': send CAN frames from a file to a CAN interface<br /> <br /> These tools can be compiled and installed on the target by means of the Buildroot menuconfig:<br /> &lt;pre class=&quot;host&quot;&gt;<br /> $ make menuconfig<br /> &lt;/pre&gt;<br /> &lt;pre class=&quot;config&quot;&gt;<br /> Package Selection for the target ---&gt;<br /> Networking ---&gt;<br /> [*] Socket CAN<br /> &lt;/pre&gt;<br /> &lt;pre class=&quot;host&quot;&gt;<br /> $ make<br /> &lt;/pre&gt;<br /> then, reflash your rootfs.<br /> <br /> ==Links==<br /> * https://www.ridgerun.com/developer/wiki/index.php/How_to_configure_and_use_CAN_bus (How to configure and use CAN bus)<br /> * http://developer.berlios.de/projects/socketcan/ (CAN Linux Driver)<br /> * http://ww1.microchip.com/downloads/en/DeviceDoc/21801e.pdf (MCP2515 datasheet)<br /> * http://www.kvaser.com/can/protocol/index.htm (CAN introduction)<br /> * http://www.armadeus.com/wiki/index.php?title=User:KevinJ#Communication_with_the_CAN_Bus_of_a_car (Communication with a car CAN bus)<br /> <br /> [[Category:Linux drivers]]<br /> [[Category:CAN bus]]</div> Salocin68 http://www.armadeus.org/wiki/index.php?title=APF6&diff=12785 APF6 2014-10-21T09:50:47Z <p>Salocin68: /* Description */</p> <hr /> <div>==Description==<br /> The APF51 is a high-end [https://en.wikipedia.org/wiki/Single-board_computer Single Board Computer] targeted for advanced GUI, intensive computation and extended connectivity.<br /> <br /> Here is a list of the main features:<br /> * Processor: [http://www.freescale.com/webapp/sps/site/taxonomy.jsp?code=IMX6X_SERIES i.MX6] (single, dual or quad core Cortex-A9 @ 1GHz)<br /> * RAM: DDR3 1086. 512Mbytes to 2GBytes. 32 ot 64bits data bus. Default capacity will be 512Mbytes.<br /> * Flash: eMMC 4Gbytes, 8 bits data bus.<br /> * Ethernet: onboard Physical (ready to use Ethernet 10/100/1000Mbit link)<br /> * USB: High speed USB OTG (OnTheGo) with onboard Physical (ready to use USB OTG link)<br /> * USB: High speed Host with integrated PHY<br /> * PCIexpress Gen2<br /> * SATA II<br /> * DVI output<br /> * TFT CMOS/LVDS interface<br /> * WiFi (option): b/g/n with u.FL antenna<br /> * Bluetooth (option): BT 4.0<br /> * Only one external supply of 3.3V required.<br /> * Mechanical dimensions: 60x50mm<br /> <br /> All the i.MX6 peripherals can be accessed through two high density [[Hirose connectors]].<br /> <br /> ==Resources==<br /> <br /> * [[Datasheet | Datasheet and schema]]<br /> <br /> ==Feature list==<br /> * [[APF6_Linux_kernel_status]]<br /> <br /> {| border=&quot;0&quot; cellpadding=&quot;5&quot; cellspacing=&quot;5&quot; summary=&quot;Hardware Add-Ons by functionnalities&quot;<br /> |----------------<br /> |- style=&quot;background:#f4f4f4; color:black; -moz-border-radius:18px;&quot;<br /> |<br /> ===Video===<br /> ====Video Out====<br /> * [[LCD]]<br /> * [[BackLight]]<br /> * [[FrameBuffer]]<br /> * [[DVI_/_HDMI|DVI/HDMI]]<br /> <br /> ====Video In====<br /> *[[Camera_interface]]<br /> <br /> ||<br /> ===Wired communication===<br /> * [[Uart]]<br /> * [[SPI]]<br /> * [[I2C]]<br /> * [[USB_Host]]<br /> * [[USB_Gadget]]<br /> * [[USB_OTG]]<br /> * [[CAN_bus_Linux_driver|CAN bus]]<br /> * [[PCIE]]<br /> <br /> ||<br /> ===Wireless communication===<br /> * [[Wifi|WiFi usage on Linux]]<br /> * [[Bluetooth|Bluetooth usage on Linux]]<br /> <br /> ===User Input===<br /> * [[Keypad]]<br /> ||<br /> <br /> ===Storage===<br /> * [[MultiMediaCard]]<br /> * [[SATA]]<br /> * [[eMMC]]<br /> <br /> ===Other===<br /> * [[PWM]]<br /> * [[GPIOlib]]<br /> <br /> |}<br /> <br /> ==Development boards==<br /> * [[APF6Dev]]<br /> <br /> [[Category:MainBoards]]<br /> [[Category:Hardware]]</div> Salocin68 http://www.armadeus.org/wiki/index.php?title=APF6&diff=12784 APF6 2014-10-21T09:49:55Z <p>Salocin68: /* Feature list */</p> <hr /> <div>==Description==<br /> The APF51 is a high-end [https://en.wikipedia.org/wiki/Single-board_computer Single Board Computer] targeted for advanced GUI, intensive computation and extended connectivity.<br /> <br /> Here is a list of the main features:<br /> * Processor: [http://www.freescale.com/webapp/sps/site/taxonomy.jsp?code=IMX6X_SERIES i.MX6] (single, dual or quad core Cortex-A9 @ 1GHz)<br /> * RAM: DDR3 1086. 512Mbytes to 2GBytes. 32 ot 64bits data bus. Default capacity will be 512Mbytes.<br /> * Flash: eMMC 4Gbytes, 8 bits data bus.<br /> * Ethernet: onboard Physical (ready to use Ethernet 10/100/1000Mbit link)<br /> * USB: High speed USB OTG (OnTheGo) with onboard Physical (ready to use USB OTG link)<br /> * USB: High speed Host with integrated PHY<br /> * WiFi (option): b/g/n with u.FL antenna<br /> * Bluetooth (option): BT 4.0<br /> * Only one external supply of 3.3V required.<br /> * Mechanical dimensions: 60x50mm<br /> <br /> All the i.MX6 peripherals can be accessed through two high density [[Hirose connectors]].<br /> <br /> ==Resources==<br /> <br /> * [[Datasheet | Datasheet and schema]]<br /> <br /> ==Feature list==<br /> * [[APF6_Linux_kernel_status]]<br /> <br /> {| border=&quot;0&quot; cellpadding=&quot;5&quot; cellspacing=&quot;5&quot; summary=&quot;Hardware Add-Ons by functionnalities&quot;<br /> |----------------<br /> |- style=&quot;background:#f4f4f4; color:black; -moz-border-radius:18px;&quot;<br /> |<br /> ===Video===<br /> ====Video Out====<br /> * [[LCD]]<br /> * [[BackLight]]<br /> * [[FrameBuffer]]<br /> * [[DVI_/_HDMI|DVI/HDMI]]<br /> <br /> ====Video In====<br /> *[[Camera_interface]]<br /> <br /> ||<br /> ===Wired communication===<br /> * [[Uart]]<br /> * [[SPI]]<br /> * [[I2C]]<br /> * [[USB_Host]]<br /> * [[USB_Gadget]]<br /> * [[USB_OTG]]<br /> * [[CAN_bus_Linux_driver|CAN bus]]<br /> * [[PCIE]]<br /> <br /> ||<br /> ===Wireless communication===<br /> * [[Wifi|WiFi usage on Linux]]<br /> * [[Bluetooth|Bluetooth usage on Linux]]<br /> <br /> ===User Input===<br /> * [[Keypad]]<br /> ||<br /> <br /> ===Storage===<br /> * [[MultiMediaCard]]<br /> * [[SATA]]<br /> * [[eMMC]]<br /> <br /> ===Other===<br /> * [[PWM]]<br /> * [[GPIOlib]]<br /> <br /> |}<br /> <br /> ==Development boards==<br /> * [[APF6Dev]]<br /> <br /> [[Category:MainBoards]]<br /> [[Category:Hardware]]</div> Salocin68 http://www.armadeus.org/wiki/index.php?title=APF6Dev&diff=12783 APF6Dev 2014-10-21T09:49:11Z <p>Salocin68: New page: ==Description== This is the Armadeus System's standard development board/baseboard for the APF6 module. The following options are available: * GPS * GSM ==Errata== ==Re...</p> <hr /> <div>==Description==<br /> This is the Armadeus System's standard development board/baseboard for the [[APF6]] module.<br /> <br /> The following options are available:<br /> * [[GPS]]<br /> * [[Gsm|GSM]]<br /> <br /> ==Errata==<br /> <br /> <br /> ==Resources==<br /> <br /> * [[Datasheet | Datasheet and schema]]<br /> * [http://www.armadeus.com/english/products-development_boards-apf6_dev.html Product page on Armadeus Systems website]<br /> <br /> ==Feature list==<br /> <br /> {| border=&quot;0&quot; cellpadding=&quot;5&quot; cellspacing=&quot;5&quot; summary=&quot;Hardware Add-Ons by functionnalities&quot;<br /> |----------------<br /> |- style=&quot;background:#f4f4f4; color:black; -moz-border-radius:18px;&quot;<br /> |<br /> <br /> ===Audio===<br /> * [[SGTL5000]]: audio in/out<br /> * [[ALSA]]<br /> <br /> ===Video===<br /> ====Video Out====<br /> * [[LCD]]<br /> * [[BackLight]]<br /> * [[FrameBuffer]]<br /> * [[DVI_/_HDMI|DVI/HDMI]]<br /> <br /> ====Video In====<br /> *[[Camera interface]]<br /> ||<br /> ===User Input===<br /> * [[Keypad]]<br /> * [[SX8654|touchscreen]]<br /> <br /> ===Wired communication===<br /> * [[Uart|UART]]<br /> * [[SPI]]<br /> * [[I2C]]<br /> * [[USB Host]] <br /> * [[USB_OTG]]<br /> * [[USB_Gadget]]<br /> * [[CAN_bus_Linux_driver|CAN bus]]<br /> * [[PCIE]]<br /> <br /> ===Storage===<br /> * [[MultiMediaCard]]<br /> * [[SATA]]<br /> ||<br /> ===Realtime===<br /> * [[MCP79400|RTC]]<br /> <br /> ===Wireless communication===<br /> * [[Wifi|WiFi usage on Linux]]<br /> * [[Bluetooth|Bluetooth usage on Linux]]<br /> <br /> ===Other===<br /> * [[PWM]]: PWM output is on J22 pin 4 &lt;br&gt;(2.8V output, if configured as output)<br /> * [[GPIOlib]]<br /> * [[JTAG]]<br /> <br /> <br /> [[Category:DevelopmentBoards]]<br /> [[Category:Hardware]]</div> Salocin68 http://www.armadeus.org/wiki/index.php?title=Datasheet&diff=12782 Datasheet 2014-10-21T09:45:28Z <p>Salocin68: </p> <hr /> <div>= Armadeus datasheets and schemas =<br /> <br /> To see all documentation available for the board clic on the title.<br /> <br /> == [http://www.armadeus.com/_downloads/apf9328/ APF9328] ==<br /> * [http://www.armadeus.com/_downloads/apf9328/documentation/dataSheet_APF9328.pdf Datasheet]<br /> * [http://www.armadeus.com/_downloads/apf9328/hardware/apf_schema.pdf Schema]<br /> <br /> == [http://www.armadeus.com/_downloads/apf9328DevLight/ APF9328Devlight] ==<br /> * Datasheet [http://www.armadeus.com/_downloads/apf9328DevLight/documentation/dataSheet_APF9328_DevLight.pdf V1] [http://www.armadeus.com/_downloads/apf9328DevLight/documentation/dataSheet_APF9328_DevLight_V2.pdf V2]<br /> * Schemas [http://www.armadeus.com/_downloads/apf9328DevLight/hardware/dev_light_schema_v1.2.pdf V1.2] [http://www.armadeus.com/_downloads/apf9328DevLight/hardware/dev_light_schema.pdf V2]<br /> <br /> == [http://www.armadeus.com/_downloads/apf9328DevFull/ APF9328DevFull] ==<br /> * [http://www.armadeus.com/_downloads/apf9328DevFull/documentation/DataSheet_APF9328_DevFull.pdf Datasheet]<br /> * [http://www.armadeus.com/_downloads/apf9328DevFull/hardware/apf9328_dev_schematics_v1_1.pdf Schema]<br /> <br /> == [http://www.armadeus.com/_downloads/apf27/ APF27] ==<br /> * [http://www.armadeus.com/_downloads/apf27/documentation/datasheet_apf27.pdf Datasheet]<br /> * [http://www.armadeus.com/_downloads/apf27/hardware/apf27_V1.2.pdf Schema]<br /> <br /> == [http://www.armadeus.com/_downloads/apf27Dev/ APF27Dev] ==<br /> * [http://www.armadeus.com/_downloads/apf27Dev/documentation/dataSheet_APF27Dev.pdf Datasheet]<br /> * [http://www.armadeus.com/_downloads/apf27Dev/hardware/apf27_devfull_12.pdf Schema]<br /> <br /> == [http://www.armadeus.com/_downloads/apf27_PPS/ PPS (APF27)] ==<br /> * [http://www.armadeus.com/_downloads/apf27_PPS/documentation/datasheet_pps.pdf Datasheet]<br /> * [http://www.armadeus.com/_downloads/apf27_PPS/hardware/pps_v11.pdf Schema]<br /> <br /> == [http://www.armadeus.com/_downloads/apf28/ APF28] ==<br /> * [http://www.armadeus.com/_downloads/apf28/documentation/datasheet_apf28.pdf Datasheet]<br /> * [http://www.armadeus.com/_downloads/apf28/hardware/apf28_v10.pdf Schema]<br /> <br /> == [http://www.armadeus.com/_downloads/apf28_Dev/ APF28_DEV] ==<br /> * [http://www.armadeus.com/_downloads/apf28_Dev/documentation/dataSheet_APF28Dev.pdf Datasheet]<br /> * [http://www.armadeus.com/_downloads/apf28_Dev/hardware/apf28_dev_V10.pdf Schema]<br /> <br /> == [http://www.armadeus.com/_downloads/apf51/ APF51] ==<br /> * [http://www.armadeus.com/_downloads/apf51/documentation/datasheet_apf51.pdf Datasheet]<br /> * [http://www.armadeus.com/_downloads/apf51/hardware/apf51_v10.pdf Schema]<br /> <br /> == [http://www.armadeus.com/_downloads/apf51_Dev/ APF51Dev] ==<br /> * [http://www.armadeus.com/_downloads/apf51_Dev/documentation/dataSheet_APF51Dev.pdf Datasheet]<br /> * [http://www.armadeus.com/_downloads/apf51_Dev/hardware/apf51_dev_V12.pdf Schema]<br /> <br /> == [http://www.armadeus.com/_downloads/apf6/ APF6] ==<br /> * [http://www.armadeus.com/_downloads/apf6/documentation/datasheet_apf6.pdf Datasheet]<br /> <br /> == [http://www.armadeus.com/_downloads/apf6_Dev/ APF6Dev] ==<br /> * [http://www.armadeus.com/_downloads/apf6_Dev/documentation/dataSheet_APF6Dev.pdf Datasheet]<br /> <br /> == [http://www.armadeus.com/_downloads/sp6_vision/ SP_VISION] ==<br /> * [http://www.armadeus.com/_downloads/sp6_vision/datasheet_sp_vision.pdf Datasheet]<br /> * [http://www.armadeus.com/_downloads/sp6_vision/hardware/sp_vision_eval_board_V05.pdf Schema]<br /> <br /> == [http://www.armadeus.com/_downloads/lw700at_adapt/ LW700] ==<br /> * [http://www.armadeus.com/_downloads/lw700at_adapt/documentation/datasheet_lw700at_adapt.pdf Datasheet]<br /> * [http://www.armadeus.com/_downloads/lw700at_adapt/hardware/LW700AT_adapt_v0B.pdf Schema]<br /> <br /> == [http://www.armadeus.com/_downloads/apw/ APW] ==<br /> * [http://www.armadeus.com/_downloads/apw/documentation/datasheet_APW.pdf Datasheet]<br /> * [http://www.armadeus.com/_downloads/apw/hardware/apf27_wireless_V0C.pdf Schema]<br /> <br /> == [http://www.armadeus.com/_downloads/lcd_adapt_LQ043 LQ043] ==<br /> * [http://www.armadeus.com/_downloads/lcd_adapt_LQ043/documentation/datasheet_lq043_adapt.pdf Datasheet]<br /> * [http://www.armadeus.com/_downloads/lcd_adapt_LQ043/hardware/lq043_adapt_schematics_v0a.pdf Schema]<br /> <br /> = HMS Demo =<br /> * Datasheet<br /> * Schema</div> Salocin68 http://www.armadeus.org/wiki/index.php?title=APF6&diff=12781 APF6 2014-10-21T09:43:28Z <p>Salocin68: New page: ==Description== The APF51 is a high-end [https://en.wikipedia.org/wiki/Single-board_computer Single Board Computer] targeted for advanced GUI, intensive computation and extended connectivi...</p> <hr /> <div>==Description==<br /> The APF51 is a high-end [https://en.wikipedia.org/wiki/Single-board_computer Single Board Computer] targeted for advanced GUI, intensive computation and extended connectivity.<br /> <br /> Here is a list of the main features:<br /> * Processor: [http://www.freescale.com/webapp/sps/site/taxonomy.jsp?code=IMX6X_SERIES i.MX6] (single, dual or quad core Cortex-A9 @ 1GHz)<br /> * RAM: DDR3 1086. 512Mbytes to 2GBytes. 32 ot 64bits data bus. Default capacity will be 512Mbytes.<br /> * Flash: eMMC 4Gbytes, 8 bits data bus.<br /> * Ethernet: onboard Physical (ready to use Ethernet 10/100/1000Mbit link)<br /> * USB: High speed USB OTG (OnTheGo) with onboard Physical (ready to use USB OTG link)<br /> * USB: High speed Host with integrated PHY<br /> * WiFi (option): b/g/n with u.FL antenna<br /> * Bluetooth (option): BT 4.0<br /> * Only one external supply of 3.3V required.<br /> * Mechanical dimensions: 60x50mm<br /> <br /> All the i.MX6 peripherals can be accessed through two high density [[Hirose connectors]].<br /> <br /> ==Resources==<br /> <br /> * [[Datasheet | Datasheet and schema]]<br /> <br /> ==Feature list==<br /> * [[APF6_Linux_kernel_status]]<br /> <br /> {| border=&quot;0&quot; cellpadding=&quot;5&quot; cellspacing=&quot;5&quot; summary=&quot;Hardware Add-Ons by functionnalities&quot;<br /> |----------------<br /> |- style=&quot;background:#f4f4f4; color:black; -moz-border-radius:18px;&quot;<br /> |<br /> ===Video===<br /> ====Video Out====<br /> * [[LCD]]<br /> * [[BackLight]]<br /> * [[FrameBuffer]]<br /> * [[DVI_/_HDMI|DVI/HDMI]]<br /> <br /> ====Video In====<br /> *[[Camera_interface]]<br /> <br /> ||<br /> ===Wired communication===<br /> * [[Uart]]<br /> * [[SPI]]<br /> * [[I2C]]<br /> * [[USB_Host]]<br /> * [[USB_Gadget]]<br /> * [[USB_OTG]]<br /> * [[CAN_bus_Linux_driver|CAN bus]]<br /> <br /> ||<br /> ===Wireless communication===<br /> * [[Wifi|WiFi usage on Linux]]<br /> * [[Bluetooth|Bluetooth usage on Linux]]<br /> <br /> ===User Input===<br /> * [[Keypad]]<br /> ||<br /> <br /> ===Storage===<br /> * [[MultiMediaCard]]<br /> ===Other===<br /> * [[PWM]]<br /> * [[GPIOlib]]<br /> <br /> |}<br /> <br /> ==Development boards==<br /> * [[APF6Dev]]<br /> <br /> [[Category:MainBoards]]<br /> [[Category:Hardware]]</div> Salocin68 http://www.armadeus.org/wiki/index.php?title=RTC&diff=11861 RTC 2013-06-20T16:13:02Z <p>Salocin68: /* Usage */</p> <hr /> <div>On this page, you will find useful informations to use the Real Time Clock of your boards (if chip is mounted).<br /> <br /> == Hardware ==<br /> ===APF9328/APF27===<br /> No permanent RTC is present on the [[APF9328]]/[[APF27]] modules, but you can have one (as an option) on the development boards or add it yourself if you are an electrician (it is not so complex to add a DS1374 (with integrated quartz) on the I2C bus). Do not forget to provide the two power-supply (VCC and Vbackup)).<br /> Currently only Maxim's DS1374 has been used but any I2C RTC, supported by Linux, should work the same way.<br /> <br /> ===APF51/APF28===<br /> [[APF51]] and [[APF28]] modules have an onboard PMIC with an integrated RTC.<br /> <br /> == Driver installation ==<br /> ===APF9328/APF27===<br /> DS1374 is by default included in standard Armadeus Linux kernel. To check if your board (Linux) has correctly detected the RTC:<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # dmesg | grep ds1374<br /> ds1374-legacy 0-0068: chip found, driver version 1.0<br /> ds1374-legacy 0-0068: rtc core: registered ds1374-legacy as rtc0<br /> ds1374-legacy 0-0068: setting system clock to 1970-01-01 00:00:07 UTC (7)<br /> &lt;/pre&gt;<br /> <br /> ===APF51===<br /> Driver is by default installed and launched. To check if your board (Linux) has correctly detected the RTC:<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # dmesg | grep rtc<br /> wm831x-rtc wm831x-rtc: rtc core: registered wm831x as rtc0<br /> wm831x-rtc wm831x-rtc: setting system clock to 2011-05-03 13:27:26 UTC (1304429246)<br /> &lt;/pre&gt;<br /> <br /> ===APF28===<br /> <br /> On APF28 the RTC is integrated under the [http://www.freescale.com/webapp/sps/site/taxonomy.jsp?code=IMX28_FAMILY i.MX28] processor. See the reference manual chapter 22 &quot;Real-Time Clock Alarm Watchdog Persistent Bits&quot;.<br /> <br /> There isn't button-lithium backup battery under APF28dev board, if we unplug the power, clock is not saved and then we could ask : what the interest of RTC if not backuped ?<br /> <br /> The interest is when we power the whole board with a battery and we poweroff the apf28 with the command :<br /> <br /> &lt;pre class=&quot;apf&quot;&gt;<br /> $ poweroff<br /> &lt;/pre&gt;<br /> <br /> The processor will be powered of ... except the RTC. Then we could power on the board pushing power switch and keep the clock up to date.<br /> <br /> {{Warning| To enable poweroff on APF28dev the board must be powered by battery (J10 pin 4) and the USB-powering must be disconnected. To disconnect it, just '''unsolder the self L7''' (behind the usb J3 connector)}}<br /> {{Note| Currently, the clock doesn't work in poweroff it must be fixed. The date and hour are keeped but not incremented}}<br /> <br /> ==== Clock ====<br /> <br /> To read the hardware value of clock use hwclock command on file /dev/rtc0:<br /> <br /> ==== Keep clock ====<br /> <br /> To power off the board type :<br /> <br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # poweroff<br /> The system is going down NOW!<br /> Sent SIGTERM to all processes<br /> Sent SIGKILL to all processes<br /> P<br /> Communications disconnect (Back at localhost)<br /> ----------------------------------------------------<br /> (/home/fabien/) C-Kermit&gt;<br /> &lt;/pre&gt;<br /> <br /> And to wake-up the board push the button 'ON'. The date and hour will be keeped when you type 'date' or 'hwclock'.<br /> <br /> == Usage ==<br /> {{Note|We recommand to store time in [[wikipedia:UTC|UTC]] format in the RTC; that will ease the timezone/summer time handling.}}<br /> * From Linux use the command '''hwclock''' to read, write, synchronize the RTC (here we pre-suppose that RTC is storing time in UTC format).<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # hwclock --help<br /> # hwclock -r -u to read hardware clock and print result (localtime)<br /> # hwclock -s -u to set the system time from the hardware clock<br /> # hwclock -w -u to set the hardware clock to the current system time (UTC)<br /> &lt;/pre&gt;<br /> {{Warning|Security &quot;features&quot; prevent to change RTC time more than 8 times per hour '''on the APF51''' !!}}<br /> * and '''date''' to read and update system date and time while running:<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # date --help for more information<br /> # date -R to read hardware clock and print result<br /> # date 013122302011 to sets the system date to january 31th 2011 22h30 (localtime)<br /> # date 2011.01.31-22:30:00 also do the job<br /> &lt;/pre&gt;<br /> * Then, when booting you will see something like this:<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> ds1374 0-0068: setting the system clock to 2011-xxxx<br /> or<br /> wm831x-rtc wm831x-rtc: setting system clock to 2011-xxxx<br /> &lt;/pre&gt;<br /> * TimeZone/Summer time handling can be configured in /etc/TZ:<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # cat /etc/TZ<br /> CET-1DST,M3.5.0/2:00,M10.5.0/3:00<br /> &lt;/pre&gt;<br /> * you can update RTC from a NTP (Network Time Protocol) server if your board is connected to internet or a NTP server <br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # ntpd -nqp 217.147.208.1<br /> ntpd: setting clock to Mon Apr 23 22:36:39 DST 2012 (offset 1335216961.855897s)<br /> # hwclock -wu # to set the hardware clock to the current system time (UTC)<br /> &lt;/pre&gt;<br /> * if Alarm/wakeup is supported by the RTC driver then the alarm/wakeup time may be set like that for a 60 sec delay with RTC0<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # sec=`date '+%s'`<br /> # let &quot;sec=$sec+60&quot;<br /> # echo $sec &gt; /sys/class/rtc/rtc0/wakealarm<br /> &lt;/pre&gt;<br /> * if the time specified in wakealarm is earlier than the current time, then the Alarm/wakeup is disabled<br /> <br /> == Links ==<br /> * [http://datasheets.maxim-ic.com/en/ds/DS1374-DS1374U.pdf Maxim's DS1374 datasheet]</div> Salocin68 http://www.armadeus.org/wiki/index.php?title=Configure_or_flash_FPGA%C2%A0%3F&diff=11860 Configure or flash FPGA ? 2013-06-13T06:57:38Z <p>Salocin68: </p> <hr /> <div>This article explain the difference between flashing FPGA and configuring FPGA.<br /> <br /> [[image:flash_configure_fpga.jpg|700px|center|thumb|'''figure 1''' - ''Flash and FPGA'']]<br /> <br /> * '''Configure''' FPGA : At power on, the FPGA is not configured. FPGA '''configuration''' is the action of transfering the bitstream from the processor RAM to the FPGA.<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> BIOS&gt; fpga load 0 ${loadaddr}<br /> &lt;/pre&gt;<br /> * '''Flash''' firmware : It is possible to save the FPGA configuration under the Flash memory of the APF. Flashing firmware is the action of transfering the bitstream from the processor RAM to the flash memory.<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> BIOS&gt; run flash_firmware<br /> &lt;/pre&gt;<br /> * '''Auto-load''' : It is possible to configure U-Boot to '''configure''' the FPGA with the configuration saved in Flash memory on the boot. To do that simply set the U-Boot environment variable '''firmware_autoload''' to 1 :<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> BIOS&gt; setenv firmware_autoload 1<br /> BIOS&gt; saveenv<br /> &lt;/pre&gt;<br /> <br /> {{Warning| '''Before setting the auto-load''' variable, be sure that your fpga binary file is correct. If not your board '''hang up''' at U-Boot starting and you will need an [[BootStrap | U-Boot recover]] to fix it.}}</div> Salocin68 http://www.armadeus.org/wiki/index.php?title=MultiMediaCard&diff=11533 MultiMediaCard 2013-01-15T09:39:23Z <p>Salocin68: /* Uboot usage */</p> <hr /> <div>Instructions to use the MultiMediaCard (MMC/SD) on your Armadeus board<br /> <br /> ==Introduction==<br /> <br /> You can use standard MMC/SD/miniSD/microSD cards with your Armadeus board:<br /> * with a DevLight V1, you must have [[MMC/SD | the corresponding connector attached to your development board.]] and use an adaptor for miniSD and microSD<br /> * with a DevLight V2, you can use the onboard microSD connector<br /> * with an [[APF9328DevFull]], you can use the MMC/SD onboard connector and an adaptor for miniSD and microSD<br /> * with an [[APF27Dev]], an [[APF28Dev]] or an [[APF51Dev]], you can use the onboard microSD connector<br /> <br /> All needed drivers are included in the standard Armadeus Linux image.<br /> <br /> ==Card insertion==<br /> You should see something like that on the Linux console:<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # imx-mmc imx-mmc.0: card inserted<br /> mmc0: host does not support reading read-only switch. assuming write-enable.<br /> mmc0: new SD card at address 01b0<br /> mmcblk0: mmc0:01b0 SD512 500224KiB<br /> mmcblk0: p1<br /> &lt;/pre&gt;<br /> <br /> Note :<br /> If the special files /dev/mmcblk0, /dev/mmcblk0p1 /dev/mmcblk0p2 ... /dev/mmcblk0p7 are NOT present on your filesystem,<br /> create them by hand :<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # mknod /dev/mmcblk0 b 179 0<br /> # mknod /dev/mmcblk0p1 b 179 1<br /> # mknod /dev/mmcblk0p2 b 179 2<br /> ...<br /> # mknod /dev/mmcblk0p7 b 179 7<br /> &lt;/pre&gt;<br /> (It happened to me after upgrading an APF9328+DevLight from version 2.3 to 3.1)<br /> <br /> ==Mounting the MMC/SD==<br /> <br /> * Just mount the MMC like you will do on your PC:<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # mount /dev/mmcblk0p1 /media/mmc<br /> &lt;/pre&gt;<br /> * Then, you can access the MMC's files from the ''/media/mmc'' directory<br /> <br /> If you have problems with vfat code page, [[MultiMediaCard#VFAT_Code_Page|include the missing code page into the kernel]].<br /> <br /> ==Booting from MMC/SD==<br /> When your rootfs is too big to be put on the APF Flash, you can always use a MMC/SD like a Hard Drive and boot from it (this is possible because standard Armadeus kernel is compiled with the MMC driver built in).<br /> <br /> ===Prepare your card===<br /> * On your APF board (to avoid to crash your Host HD), create a good partition table:<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # /sbin/fdisk /dev/mmcblk0<br /> Delete all existing partion with 'd'<br /> Create a primary partion: 'n' then 'p' then '1'<br /> Change bootflag to Linux: 't' then '83'<br /> Save partition table: 'w'<br /> (To quit without saving: 'm')<br /> &lt;/pre&gt;<br /> * Then, on your PC, format your MMC with Ext2 filesystem (booting on FAT is bad :-) ):<br /> &lt;pre class=&quot;host&quot;&gt;<br /> $ sudo mkfs.ext2 /dev/sdX1 (replace X with your MMC reader drive letter, if your Laptop has an integrated<br /> MMC reader then use mmcblk0p1 instead of sdX1)<br /> &lt;/pre&gt;<br /> * If not automatically detected/mounted by your distribution, mount your MMC/SD on your Host filesystem (for example in ''/media/mmc''):<br /> &lt;pre class=&quot;host&quot;&gt;<br /> $ sudo mkdir -p /media/mmc<br /> $ sudo mount /dev/sdX1 /media/mmc (replace X with your MMC reader drive letter, if your Laptop has an integrated<br /> MMC reader then use mmcblk0p1 instead of sdX1)<br /> &lt;/pre&gt;<br /> <br /> ===Put your rootfs and Linux kernel on the MMC/SD===<br /> * Buildroot should be configured to generate a tar-ed rootfs '''(done by default)''', if not:<br /> &lt;pre class=&quot;host&quot;&gt;<br /> $ make menuconfig<br /> &lt;/pre&gt;<br /> <br /> &lt;pre class=&quot;config&quot;&gt;<br /> Filesystem images ---&gt;<br /> ...<br /> [*] tar the root filesystem<br /> Compression method (no compression) ---&gt;<br /> () other random options to pass to tar<br /> ...<br /> &lt;/pre&gt;<br /> <br /> &lt;pre class=&quot;host&quot;&gt;<br /> $ make<br /> &lt;/pre&gt;<br /> * and then uncompress the rootfs to the SD card, also copy the linux kernel to the rootfs /boot folder:<br /> <br /> {{Note | The APF9328 and for the time being the APF51 do not load the kernel from the SD card but use the one in flash instead. }}<br /> &lt;pre class=&quot;host&quot;&gt;<br /> $ make shell_env<br /> $ source armadeus_env.sh<br /> $ sudo tar xvf $ARMADEUS_ROOTFS_TAR -C /media/mmc<br /> $ sudo mkdir -p /media/mmct/boot<br /> $ sudo cp $ARMADEUS_BINARIES/$ARMADEUS_BOARD_NAME-linux.bin /media/mmc/boot<br /> $ sudo umount /media/mmc<br /> &lt;/pre&gt;<br /> <br /> ===Boot===<br /> * Insert the MMC/SD/microSD in the corresponding slot of your Armadeus board and then under U-Boot do:<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> BIOS&gt; run mmcboot<br /> &lt;/pre&gt;<br /> * if you want to automatically boot from SD at each startup, modify the ''bootcmd'' U-Boot macro:<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> BIOS&gt; setenv bootcmd run mmcboot<br /> BIOS&gt; saveenv<br /> &lt;/pre&gt;<br /> (default bootcmd when you receive your board is ''run jffsboot'' = boot from FLASH)<br /> <br /> ==Performances==<br /> * [[MMC/SD#Supported_Cards| Show tested cards performances]]<br /> <br /> ==Troubleshots==<br /> ===VFAT Code Page===<br /> If you encounter this message (or something similar):<br /> Unable to load NLS charset cp437<br /> FAT: codepage cp437 not found<br /> you have to add the charset to the supported kernel ones:<br /> $ make linux26-menuconfig<br /> &lt;pre class=&quot;config&quot;&gt;<br /> File systems ---&gt; <br /> -*- Native language support ---&gt;<br /> &lt;*&gt; Codepage 437 (United States, Canada)<br /> ...<br /> &lt;*&gt; NLS ISO 8859-1 (Latin 1; Western European Languages)<br /> ...<br /> &lt;/pre&gt;<br /> <br /> ==U-Boot usage==<br /> SD cards can altough be used with U-Boot.<br /> The following commands are usefull:<br /> <br /> &lt;pre class=&quot;apf&quot;&gt;<br /> mmc rescan #scan the mmc<br /> fatls mmc 0 # list the mmc containt<br /> fatload mmc 0 ${loadaddr} xxx.bin #load in ram the file xxx.bin<br /> &lt;/pre&gt;<br /> <br /> ==Links==<br /> <br /> * http://en.wikipedia.org/wiki/MultiMedia_Card<br /> <br /> [[Category:MassStorage]]</div> Salocin68 http://www.armadeus.org/wiki/index.php?title=USB_Host&diff=11532 USB Host 2013-01-15T09:37:59Z <p>Salocin68: /* U-Boot usage */</p> <hr /> <div>How-To use the USB Host functionnality of Armadeus boards under Linux.<br /> <br /> == Controller ==<br /> * [[APF9328DevFull|APF9328DevFull]]: it is equipped with a USB 2.0 Host controller (ISP1761) featuring three USB high speed ports. The ISP1761 driver is already configured with armadeus version 3. For older versions refer to the [[ISP1761_Linux_driver |how to install USB Host Linux driver for the DevFull]] page <br /> * [[APF27]] and [[APF27Dev]]: two Host ports are available. The controllers are integrated in the i.MX27 processor. Nothing has to be done to configure the controller. No special operation has to be done to use both USB ports (driver is included in default kernel).<br /> * [[APF27 PPS]]: one Host port and one OTG port (that can be forced to Host mode). Default Linux kernel has all the needed drivers compiled in.<br /> * [[APF51Dev]]: 2 Host ports and one OTG port (that can be forced to Host mode). Default Linux kernel has all the needed drivers compiled in.<br /> * [[PPS51]] one Host port and one OTG port (that can be forced to Host mode). Default Linux kernel has all the needed drivers compiled in.<br /> * [[APF28Dev]]: one Host port and one OTG port (Host/slave mode automatically switched depending on cable). Default Linux kernel has all the needed drivers compiled in.<br /> <br /> == Forcing an OTG controller to Host mode (APF27 and APF51)==<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> BIOS&gt; setenv extrabootargs otg_mode=host<br /> BIOS&gt; saveenv<br /> BIOS&gt; boot<br /> &lt;/pre&gt;<br /> <br /> == Using USB devices ==<br /> <br /> === USB keyboard/mouse (HID: Human Interface Device) ===<br /> ==== Driver installation ====<br /> * [[Talk:USB_Host|Done by default]] in recent releases<br /> <br /> ====Plug the keyboard====<br /> * you should see on console (here on APF9328 for example):<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> usb 1-1.1: new low speed USB device using isp1761 and address 3<br /> usb 1-1.1: configuration #1 chosen from 1 choice<br /> input: NOVATEK USB Keyboard as /class/input/input0<br /> input: USB HID v1.10 Keyboard [NOVATEK USB Keyboard] on usb-platform-1.1<br /> input: NOVATEK USB Keyboard as /class/input/input1<br /> input: USB HID v1.10 Mouse [NOVATEK USB Keyboard] on usb-platform-1.1<br /> &lt;/pre&gt;<br /> * To change keyboard keymap (by default US one is used):<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # loadkmap &lt; /etc/i18n/fr.kmap<br /> &lt;/pre&gt;<br /> <br /> ====Plug the mouse====<br /> * you should see on console (here on APF9328 for example):<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> usb 1-1.2: new low speed USB device using isp1761 and address 6<br /> usb 1-1.2: configuration #1 chosen from 1 choice<br /> input: Logitech USB-PS/2 Optical Mouse as /class/input/input6<br /> input: USB HID v1.10 Mouse [Logitech USB-PS/2 Optical Mouse] on usb-platform-1.2<br /> &lt;/pre&gt;<br /> <br /> === USB Flash memory / USB key / USB card reader / USB Hard Drive=== <br /> ==== Driver installation ====<br /> * [[Talk:USB_Host|Done by default]] in recent releases.<br /> <br /> ==== Plug the storage device ====<br /> * You should see (for example):<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> usb 1-1.2: new high speed USB device using isp1761 and address 6<br /> usb 1-1.2: configuration #1 chosen from 1 choice<br /> scsi0 : SCSI emulation for USB Mass Storage devices<br /> usb 1-1.2: reset high speed USB device using isp1761 and address 6<br /> scsi 0:0:0:0: Direct-Access Hama Card Reader CF 1.9C PQ: 0 ANSI: 0 CCS<br /> sd 0:0:0:0: [sda] Attached SCSI removable disk<br /> &lt;/pre&gt;<br /> <br /> ==== Additional configuration ====<br /> * If /dev/sdaX does not exist, then create it:<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # mknod /dev/sda b 8 0<br /> # mknod /dev/sda1 b 8 1<br /> # mknod /dev/sda2 b 8 2<br /> &lt;/pre&gt;<br /> * Create a mount directory &quot;usbdisk&quot;<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # mkdir -m 777 /mnt/usbdisk<br /> &lt;/pre&gt;<br /> <br /> ==== Mount the device ====<br /> * Mount the USB Mass Storage device<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # mount -t vfat /dev/sda1 /mnt/usbdisk<br /> &lt;/pre&gt;<br /> * Check what is present on the USB Mass Storage device:<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # ls -al /mnt/usbdisk<br /> &lt;/pre&gt;<br /> * And if it is well mounted (for example):<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # mount<br /> rootfs on / type rootfs (rw)<br /> /dev/root on / type jffs2 (rw)<br /> proc on /proc type proc (rw)<br /> devpts on /dev/pts type devpts (rw)<br /> tmpfs on /tmp type tmpfs (rw)<br /> sysfs on /sys type sysfs (rw)<br /> /dev/sda1 on /mnt/usbdisk type msdos (rw,fmask=0022,dmask=0022,codepage=cp437)<br /> &lt;/pre&gt;<br /> <br /> === USB &lt;--&gt; Serial adapters ===<br /> * See [[USB_to_serial_adapter]]<br /> <br /> === USB &lt;--&gt; WiFi adapters ===<br /> * See [[USB_to_WiFi_adapter]]<br /> <br /> ==U-Boot usage==<br /> USB storage can altough be used with U-Boot.<br /> The following commands are usefull:<br /> <br /> &lt;pre class=&quot;apf&quot;&gt;<br /> usb start #start/restart the usb<br /> usb info # show available usb devices<br /> fatls usb 0 # list the usb dongle containt (mass storage only)<br /> fatload usb 0 ${loadaddr} xxx.bin #load in ram the file xxx.bin<br /> &lt;/pre&gt;<br /> <br /> == Links ==<br /> * Any links ?<br /> <br /> [[Category:BoardConnectivity]]<br /> [[Category:Linux drivers]]<br /> [[Category:USB]]</div> Salocin68 http://www.armadeus.org/wiki/index.php?title=USB_Host&diff=11531 USB Host 2013-01-15T09:37:29Z <p>Salocin68: /* Uboot usage */</p> <hr /> <div>How-To use the USB Host functionnality of Armadeus boards under Linux.<br /> <br /> == Controller ==<br /> * [[APF9328DevFull|APF9328DevFull]]: it is equipped with a USB 2.0 Host controller (ISP1761) featuring three USB high speed ports. The ISP1761 driver is already configured with armadeus version 3. For older versions refer to the [[ISP1761_Linux_driver |how to install USB Host Linux driver for the DevFull]] page <br /> * [[APF27]] and [[APF27Dev]]: two Host ports are available. The controllers are integrated in the i.MX27 processor. Nothing has to be done to configure the controller. No special operation has to be done to use both USB ports (driver is included in default kernel).<br /> * [[APF27 PPS]]: one Host port and one OTG port (that can be forced to Host mode). Default Linux kernel has all the needed drivers compiled in.<br /> * [[APF51Dev]]: 2 Host ports and one OTG port (that can be forced to Host mode). Default Linux kernel has all the needed drivers compiled in.<br /> * [[PPS51]] one Host port and one OTG port (that can be forced to Host mode). Default Linux kernel has all the needed drivers compiled in.<br /> * [[APF28Dev]]: one Host port and one OTG port (Host/slave mode automatically switched depending on cable). Default Linux kernel has all the needed drivers compiled in.<br /> <br /> == Forcing an OTG controller to Host mode (APF27 and APF51)==<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> BIOS&gt; setenv extrabootargs otg_mode=host<br /> BIOS&gt; saveenv<br /> BIOS&gt; boot<br /> &lt;/pre&gt;<br /> <br /> == Using USB devices ==<br /> <br /> === USB keyboard/mouse (HID: Human Interface Device) ===<br /> ==== Driver installation ====<br /> * [[Talk:USB_Host|Done by default]] in recent releases<br /> <br /> ====Plug the keyboard====<br /> * you should see on console (here on APF9328 for example):<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> usb 1-1.1: new low speed USB device using isp1761 and address 3<br /> usb 1-1.1: configuration #1 chosen from 1 choice<br /> input: NOVATEK USB Keyboard as /class/input/input0<br /> input: USB HID v1.10 Keyboard [NOVATEK USB Keyboard] on usb-platform-1.1<br /> input: NOVATEK USB Keyboard as /class/input/input1<br /> input: USB HID v1.10 Mouse [NOVATEK USB Keyboard] on usb-platform-1.1<br /> &lt;/pre&gt;<br /> * To change keyboard keymap (by default US one is used):<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # loadkmap &lt; /etc/i18n/fr.kmap<br /> &lt;/pre&gt;<br /> <br /> ====Plug the mouse====<br /> * you should see on console (here on APF9328 for example):<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> usb 1-1.2: new low speed USB device using isp1761 and address 6<br /> usb 1-1.2: configuration #1 chosen from 1 choice<br /> input: Logitech USB-PS/2 Optical Mouse as /class/input/input6<br /> input: USB HID v1.10 Mouse [Logitech USB-PS/2 Optical Mouse] on usb-platform-1.2<br /> &lt;/pre&gt;<br /> <br /> === USB Flash memory / USB key / USB card reader / USB Hard Drive=== <br /> ==== Driver installation ====<br /> * [[Talk:USB_Host|Done by default]] in recent releases.<br /> <br /> ==== Plug the storage device ====<br /> * You should see (for example):<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> usb 1-1.2: new high speed USB device using isp1761 and address 6<br /> usb 1-1.2: configuration #1 chosen from 1 choice<br /> scsi0 : SCSI emulation for USB Mass Storage devices<br /> usb 1-1.2: reset high speed USB device using isp1761 and address 6<br /> scsi 0:0:0:0: Direct-Access Hama Card Reader CF 1.9C PQ: 0 ANSI: 0 CCS<br /> sd 0:0:0:0: [sda] Attached SCSI removable disk<br /> &lt;/pre&gt;<br /> <br /> ==== Additional configuration ====<br /> * If /dev/sdaX does not exist, then create it:<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # mknod /dev/sda b 8 0<br /> # mknod /dev/sda1 b 8 1<br /> # mknod /dev/sda2 b 8 2<br /> &lt;/pre&gt;<br /> * Create a mount directory &quot;usbdisk&quot;<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # mkdir -m 777 /mnt/usbdisk<br /> &lt;/pre&gt;<br /> <br /> ==== Mount the device ====<br /> * Mount the USB Mass Storage device<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # mount -t vfat /dev/sda1 /mnt/usbdisk<br /> &lt;/pre&gt;<br /> * Check what is present on the USB Mass Storage device:<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # ls -al /mnt/usbdisk<br /> &lt;/pre&gt;<br /> * And if it is well mounted (for example):<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # mount<br /> rootfs on / type rootfs (rw)<br /> /dev/root on / type jffs2 (rw)<br /> proc on /proc type proc (rw)<br /> devpts on /dev/pts type devpts (rw)<br /> tmpfs on /tmp type tmpfs (rw)<br /> sysfs on /sys type sysfs (rw)<br /> /dev/sda1 on /mnt/usbdisk type msdos (rw,fmask=0022,dmask=0022,codepage=cp437)<br /> &lt;/pre&gt;<br /> <br /> === USB &lt;--&gt; Serial adapters ===<br /> * See [[USB_to_serial_adapter]]<br /> <br /> === USB &lt;--&gt; WiFi adapters ===<br /> * See [[USB_to_WiFi_adapter]]<br /> <br /> ==U-Boot usage==<br /> USB storage can altough be used with U-Boot.<br /> The following commands are usefull:<br /> <br /> usb start #start/restart the usb<br /> usb info # show available usb devices<br /> fatls usb 0 # list the usb dongle containt (mass storage only)<br /> fatload usb 0 ${loadaddr} xxx.bin #load in ram the file xxx.bin<br /> <br /> == Links ==<br /> * Any links ?<br /> <br /> [[Category:BoardConnectivity]]<br /> [[Category:Linux drivers]]<br /> [[Category:USB]]</div> Salocin68 http://www.armadeus.org/wiki/index.php?title=USB_Host&diff=11515 USB Host 2013-01-11T12:57:05Z <p>Salocin68: </p> <hr /> <div>How-To use the USB Host functionnality of Armadeus boards under Linux.<br /> <br /> == Controller ==<br /> * [[APF9328DevFull|APF9328DevFull]]: it is equipped with a USB 2.0 Host controller (ISP1761) featuring three USB high speed ports. The ISP1761 driver is already configured with armadeus version 3. For older versions refer to the [[ISP1761_Linux_driver |how to install USB Host Linux driver for the DevFull]] page <br /> * [[APF27]] and [[APF27Dev]]: two Host ports are available. The controllers are integrated in the i.MX27 processor. Nothing has to be done to configure the controller. No special operation has to be done to use both USB ports (driver is included in default kernel).<br /> * [[APF27 PPS]]: one Host port and one OTG port (that can be forced to Host mode). Default Linux kernel has all the needed drivers compiled in.<br /> * [[APF51Dev]]: 2 Host ports and one OTG port (that can be forced to Host mode). Default Linux kernel has all the needed drivers compiled in.<br /> * [[PPS51]] one Host port and one OTG port (that can be forced to Host mode). Default Linux kernel has all the needed drivers compiled in.<br /> * [[APF28Dev]]: one Host port and one OTG port (Host/slave mode automatically switched depending on cable). Default Linux kernel has all the needed drivers compiled in.<br /> <br /> == Forcing an OTG controller to Host mode (APF27 and APF51)==<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> BIOS&gt; setenv extrabootargs otg_mode=host<br /> BIOS&gt; saveenv<br /> BIOS&gt; boot<br /> &lt;/pre&gt;<br /> <br /> == Using USB devices ==<br /> <br /> === USB keyboard/mouse (HID: Human Interface Device) ===<br /> ==== Driver installation ====<br /> * [[Talk:USB_Host|Done by default]] in recent releases<br /> <br /> ====Plug the keyboard====<br /> * you should see on console (here on APF9328 for example):<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> usb 1-1.1: new low speed USB device using isp1761 and address 3<br /> usb 1-1.1: configuration #1 chosen from 1 choice<br /> input: NOVATEK USB Keyboard as /class/input/input0<br /> input: USB HID v1.10 Keyboard [NOVATEK USB Keyboard] on usb-platform-1.1<br /> input: NOVATEK USB Keyboard as /class/input/input1<br /> input: USB HID v1.10 Mouse [NOVATEK USB Keyboard] on usb-platform-1.1<br /> &lt;/pre&gt;<br /> * To change keyboard keymap (by default US one is used):<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # loadkmap &lt; /etc/i18n/fr.kmap<br /> &lt;/pre&gt;<br /> <br /> ====Plug the mouse====<br /> * you should see on console (here on APF9328 for example):<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> usb 1-1.2: new low speed USB device using isp1761 and address 6<br /> usb 1-1.2: configuration #1 chosen from 1 choice<br /> input: Logitech USB-PS/2 Optical Mouse as /class/input/input6<br /> input: USB HID v1.10 Mouse [Logitech USB-PS/2 Optical Mouse] on usb-platform-1.2<br /> &lt;/pre&gt;<br /> <br /> === USB Flash memory / USB key / USB card reader / USB Hard Drive=== <br /> ==== Driver installation ====<br /> * [[Talk:USB_Host|Done by default]] in recent releases.<br /> <br /> ==== Plug the storage device ====<br /> * You should see (for example):<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> usb 1-1.2: new high speed USB device using isp1761 and address 6<br /> usb 1-1.2: configuration #1 chosen from 1 choice<br /> scsi0 : SCSI emulation for USB Mass Storage devices<br /> usb 1-1.2: reset high speed USB device using isp1761 and address 6<br /> scsi 0:0:0:0: Direct-Access Hama Card Reader CF 1.9C PQ: 0 ANSI: 0 CCS<br /> sd 0:0:0:0: [sda] Attached SCSI removable disk<br /> &lt;/pre&gt;<br /> <br /> ==== Additional configuration ====<br /> * If /dev/sdaX does not exist, then create it:<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # mknod /dev/sda b 8 0<br /> # mknod /dev/sda1 b 8 1<br /> # mknod /dev/sda2 b 8 2<br /> &lt;/pre&gt;<br /> * Create a mount directory &quot;usbdisk&quot;<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # mkdir -m 777 /mnt/usbdisk<br /> &lt;/pre&gt;<br /> <br /> ==== Mount the device ====<br /> * Mount the USB Mass Storage device<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # mount -t vfat /dev/sda1 /mnt/usbdisk<br /> &lt;/pre&gt;<br /> * Check what is present on the USB Mass Storage device:<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # ls -al /mnt/usbdisk<br /> &lt;/pre&gt;<br /> * And if it is well mounted (for example):<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # mount<br /> rootfs on / type rootfs (rw)<br /> /dev/root on / type jffs2 (rw)<br /> proc on /proc type proc (rw)<br /> devpts on /dev/pts type devpts (rw)<br /> tmpfs on /tmp type tmpfs (rw)<br /> sysfs on /sys type sysfs (rw)<br /> /dev/sda1 on /mnt/usbdisk type msdos (rw,fmask=0022,dmask=0022,codepage=cp437)<br /> &lt;/pre&gt;<br /> <br /> === USB &lt;--&gt; Serial adapters ===<br /> * See [[USB_to_serial_adapter]]<br /> <br /> === USB &lt;--&gt; WiFi adapters ===<br /> * See [[USB_to_WiFi_adapter]]<br /> <br /> ==Uboot usage==<br /> USB storage can altough be used with uBoot.<br /> The following commands are usefull:<br /> <br /> usb start #start/restart the usb<br /> usb info # show available usb devices<br /> fatls usb 0 # list the usb dongle containt (mass storage only)<br /> fatload usb 0 ${loadaddr} xxx.bin #load in ram the file xxx.bin<br /> <br /> == Links ==<br /> * Any links ?<br /> <br /> [[Category:BoardConnectivity]]<br /> [[Category:Linux drivers]]<br /> [[Category:USB]]</div> Salocin68 http://www.armadeus.org/wiki/index.php?title=MultiMediaCard&diff=11514 MultiMediaCard 2013-01-11T12:54:08Z <p>Salocin68: </p> <hr /> <div>Instructions to use the MultiMediaCard (MMC/SD) on your Armadeus board<br /> <br /> ==Introduction==<br /> <br /> You can use standard MMC/SD/miniSD/microSD cards with your Armadeus board:<br /> * with a DevLight V1, you must have [[MMC/SD | the corresponding connector attached to your development board.]] and use an adaptor for miniSD and microSD<br /> * with a DevLight V2, you can use the onboard microSD connector<br /> * with an [[APF9328DevFull]], you can use the MMC/SD onboard connector and an adaptor for miniSD and microSD<br /> * with an [[APF27Dev]], an [[APF28Dev]] or an [[APF51Dev]], you can use the onboard microSD connector<br /> <br /> All needed drivers are included in the standard Armadeus Linux image.<br /> <br /> ==Card insertion==<br /> You should see something like that on the Linux console:<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # imx-mmc imx-mmc.0: card inserted<br /> mmc0: host does not support reading read-only switch. assuming write-enable.<br /> mmc0: new SD card at address 01b0<br /> mmcblk0: mmc0:01b0 SD512 500224KiB<br /> mmcblk0: p1<br /> &lt;/pre&gt;<br /> <br /> Note :<br /> If the special files /dev/mmcblk0, /dev/mmcblk0p1 /dev/mmcblk0p2 ... /dev/mmcblk0p7 are NOT present on your filesystem,<br /> create them by hand :<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # mknod /dev/mmcblk0 b 179 0<br /> # mknod /dev/mmcblk0p1 b 179 1<br /> # mknod /dev/mmcblk0p2 b 179 2<br /> ...<br /> # mknod /dev/mmcblk0p7 b 179 7<br /> &lt;/pre&gt;<br /> (It happened to me after upgrading an APF9328+DevLight from version 2.3 to 3.1)<br /> <br /> ==Mounting the MMC/SD==<br /> <br /> * Just mount the MMC like you will do on your PC:<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # mount /dev/mmcblk0p1 /media/mmc<br /> &lt;/pre&gt;<br /> * Then, you can access the MMC's files from the ''/media/mmc'' directory<br /> <br /> If you have problems with vfat code page, [[MultiMediaCard#VFAT_Code_Page|include the missing code page into the kernel]].<br /> <br /> ==Booting from MMC/SD==<br /> When your rootfs is too big to be put on the APF Flash, you can always use a MMC/SD like a Hard Drive and boot from it (this is possible because standard Armadeus kernel is compiled with the MMC driver built in).<br /> <br /> ===Prepare your card===<br /> * On your APF board (to avoid to crash your Host HD), create a good partition table:<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # /sbin/fdisk /dev/mmcblk0<br /> Delete all existing partion with 'd'<br /> Create a primary partion: 'n' then 'p' then '1'<br /> Change bootflag to Linux: 't' then '83'<br /> Save partition table: 'w'<br /> (To quit without saving: 'm')<br /> &lt;/pre&gt;<br /> * Then, on your PC, format your MMC with Ext2 filesystem (booting on FAT is bad :-) ):<br /> &lt;pre class=&quot;host&quot;&gt;<br /> $ sudo mkfs.ext2 /dev/sdX1 (replace X with your MMC reader drive letter, if your Laptop has an integrated<br /> MMC reader then use mmcblk0p1 instead of sdX1)<br /> &lt;/pre&gt;<br /> * If not automatically detected/mounted by your distribution, mount your MMC/SD on your Host filesystem (for example in ''/media/mmc''):<br /> &lt;pre class=&quot;host&quot;&gt;<br /> $ sudo mkdir -p /media/mmc<br /> $ sudo mount /dev/sdX1 /media/mmc (replace X with your MMC reader drive letter, if your Laptop has an integrated<br /> MMC reader then use mmcblk0p1 instead of sdX1)<br /> &lt;/pre&gt;<br /> <br /> ===Put your rootfs and Linux kernel on the MMC/SD===<br /> * Buildroot should be configured to generate a tar-ed rootfs '''(done by default)''', if not:<br /> &lt;pre class=&quot;host&quot;&gt;<br /> $ make menuconfig<br /> &lt;/pre&gt;<br /> <br /> &lt;pre class=&quot;config&quot;&gt;<br /> Filesystem images ---&gt;<br /> ...<br /> [*] tar the root filesystem<br /> Compression method (no compression) ---&gt;<br /> () other random options to pass to tar<br /> ...<br /> &lt;/pre&gt;<br /> <br /> &lt;pre class=&quot;host&quot;&gt;<br /> $ make<br /> &lt;/pre&gt;<br /> * and then uncompress the rootfs to the SD card, also copy the linux kernel to the rootfs /boot folder:<br /> <br /> {{Note | The APF9328 and for the time being the APF51 do not load the kernel from the SD card but use the one in flash instead. }}<br /> &lt;pre class=&quot;host&quot;&gt;<br /> $ make shell_env<br /> $ source armadeus_env.sh<br /> $ sudo tar xvf $ARMADEUS_ROOTFS_TAR -C /media/mmc<br /> $ sudo mkdir -p /media/mmct/boot<br /> $ sudo cp $ARMADEUS_BINARIES/$ARMADEUS_BOARD_NAME-linux.bin /media/mmc/boot<br /> $ sudo umount /media/mmc<br /> &lt;/pre&gt;<br /> <br /> ===Boot===<br /> * Insert the MMC/SD/microSD in the corresponding slot of your Armadeus board and then under U-Boot do:<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> BIOS&gt; run mmcboot<br /> &lt;/pre&gt;<br /> * if you want to automatically boot from SD at each startup, modify the ''bootcmd'' U-Boot macro:<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> BIOS&gt; setenv bootcmd run mmcboot<br /> BIOS&gt; saveenv<br /> &lt;/pre&gt;<br /> (default bootcmd when you receive your board is ''run jffsboot'' = boot from FLASH)<br /> <br /> ==Performances==<br /> * [[MMC/SD#Supported_Cards| Show tested cards performances]]<br /> <br /> ==Troubleshots==<br /> ===VFAT Code Page===<br /> If you encounter this message (or something similar):<br /> Unable to load NLS charset cp437<br /> FAT: codepage cp437 not found<br /> you have to add the charset to the supported kernel ones:<br /> $ make linux26-menuconfig<br /> &lt;pre class=&quot;config&quot;&gt;<br /> File systems ---&gt; <br /> -*- Native language support ---&gt;<br /> &lt;*&gt; Codepage 437 (United States, Canada)<br /> ...<br /> &lt;*&gt; NLS ISO 8859-1 (Latin 1; Western European Languages)<br /> ...<br /> &lt;/pre&gt;<br /> <br /> ==Uboot usage==<br /> SD cards can altough be used with uBoot.<br /> The following commands are usefull:<br /> <br /> mmc rescan #scan the mmc<br /> fatls mmc 0 # list the mmc containt<br /> fatload mmc 0 ${loadaddr} xxx.bin #load in ram the file xxx.bin<br /> <br /> <br /> ==Links==<br /> <br /> * http://en.wikipedia.org/wiki/MultiMedia_Card<br /> <br /> [[Category:MassStorage]]</div> Salocin68 http://www.armadeus.org/wiki/index.php?title=USB_Gadget&diff=11456 USB Gadget 2012-12-05T13:47:26Z <p>Salocin68: </p> <hr /> <div>Instructions on how to use the USB device (or OTG) port of your Armadeus board to communicate with your PC; ie see your board from your PC like an USB device.<br /> <br /> ==Introduction==<br /> <br /> You can connect your APF board to your PC using its USB Device port ([[APF9328DevFull]]), a modified USB host port ([[APF27Dev]]), or an USB OTG port put in device mode ([[APF27 PPS]], [[APF51Dev]] &amp; [[APF28Dev]]), and it can be &quot;enumerated&quot; as most common USB devices (depending on the type of communication you want to use):<br /> * serial device<br /> * net device<br /> * mass storage device<br /> <br /> === Hardware specifics for the APF27Dev ===<br /> At first, an USB A male / A male cable has to be used like this one: http://fr.farnell.com/pro-signal/psg90024/lead-usb-2-0-am-am-2m-black/dp/1494745<br /> <br /> Do not use USB cable with integrated ferrite bead !!<br /> <br /> The APF27dev board is equipped with two USB host ports. '''Only the High Speed Host port (top connector)''' can be configured as an USB Device.<br /> <br /> {{Warning|DO NOT CONNECT TWO HOST PORTS TOGETHER AND TAKE CARE TO USE THE RIGHT USB PORT ON THE APF27DEV !!}}<br /> <br /> === Software specifics for the APF27Dev, APF27 PPS, APF51Dev ===<br /> In order to activate the device mode, a new parameter has to be added to the U-Boot console variable:<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> BIOS&gt; setenv extrabootargs otg_mode=device<br /> BIOS&gt; saveenv<br /> BIOS&gt; boot<br /> &lt;/pre&gt;<br /> <br /> Your port will now work as an USB device.<br /> <br /> ==Installation==<br /> <br /> * The drivers are now installed by default (since armadeus-3.0)<br /> * you should have following modules in your kernel source tree:<br /> '''/lib/modules/`uname -r`/kernel/drivers/usb/gadget/gadgetfs.ko''' For test<br /> '''/lib/modules/`uname -r`/kernel/drivers/usb/gadget/g_ether.ko''' Ethernet emulation on USB<br /> '''/lib/modules/`uname -r`/kernel/drivers/usb/gadget/g_file_storage.ko''' Mass storage<br /> '''/lib/modules/`uname -r`/kernel/drivers/usb/gadget/g_serial.ko''' Serial emulation on USB<br /> '''/lib/modules/`uname -r`/kernel/drivers/usb/gadget/g_zero.ko''' For test<br /> * If not here is how to add the missing one: [[Talk:USB_Gadget]]<br /> <br /> ==Usage==<br /> <br /> ===To emulate a mass storage device:===<br /> * [[USB_Gadget#Links |create]] or get a &quot;backing storage file&quot; ([http://dl.free.fr/q9IKqqweK for example])<br /> * copy this file (uncompressed) in the '''/tmp''' directory of your board (here my Host PC has 192.168.0.20 as IP @):<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # tftp -g -r backing_file.gz -l /tmp/backing_file.gz 192.168.0.20<br /> # gunzip /tmp/backing_file.gz<br /> &lt;/pre&gt;<br /> * load ''g_file_storage'' or ''g_mass_storage'' module (depending on your Linux version):<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # modprobe g_file_storage file=/tmp/backing_file<br /> g_file_storage gadget: File-backed Storage Gadget, version: 28 November 2005<br /> g_file_storage gadget: Number of LUNs=1<br /> g_file_storage gadget-lun0: ro=0, file: /tmp/backing_file<br /> &lt;/pre&gt;<br /> * connect target's USB cable to your PC and, <br /> On your Linux Host:<br /> * If you have a recent Linux distribution, your device should be automatically mounted. Otherwise:<br /> ** as root, launch ''dmesg'' and find the ''/dev/sdaX'' device assigned to your board:<br /> ... usb 1-1.4: new full speed USB device using uhci_hcd and address 7<br /> ... usb 1-1.4: configuration #1 chosen from 1 choice<br /> ... scsi1 : SCSI emulation for USB Mass Storage devices<br /> ... Vendor: Linux Model: File-Stor Gadget Rev: 0314<br /> ... Type: Direct-Access ANSI SCSI revision: 02<br /> ... SCSI device sda: 8192 512-byte hdwr sectors (4 MB)<br /> ... sda: Write Protect is off<br /> ... SCSI device sda: 8192 512-byte hdwr sectors (4 MB)<br /> ... sda: Write Protect is off<br /> ... sda: sda1<br /> ... sd 1:0:0:0: Attached scsi disk sda<br /> ... sd 1:0:0:0: Attached scsi generic sg0 type 0<br /> *<br /> ** then mount the device and enjoy file sharing:<br /> &lt;pre class=&quot;host&quot;&gt;<br /> $ sudo mount /dev/sda1 /mnt/tmp<br /> $ cd /mnt/tmp<br /> $ showimage /mnt/tmp/test.jpg<br /> &lt;/pre&gt;<br /> <br /> ===To emulate a serial link===<br /> * On your Host PC (if '''usbserial''' module is not already loaded):<br /> &lt;pre class=&quot;host&quot;&gt;<br /> $ sudo modprobe usbserial vendor=0x0525 product=0xA4A6<br /> &lt;/pre&gt;<br /> or you can automate it by modifying ''/etc/modprobe.d/options'' file (Tested on *Ubuntu):<br /> &lt;pre class=&quot;host&quot;&gt;<br /> $ sudo vim /etc/modprobe.d/options<br /> ...<br /> options usbserial vendor=0x0525 product=0xA4A6<br /> &lt;/pre&gt;<br /> * on your APF:<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # modprobe g_serial<br /> g_serial gadget: Gadget Serial v2.4<br /> g_serial gadget: g_serial ready<br /> fsl-usb2-udc: bind to driver g_serial<br /> g_serial gadget: high speed config #2: CDC ACM config<br /> <br /> # mknod /dev/ttyGS0 c 249 0 (if not created)<br /> &lt;/pre&gt;<br /> * then connect the USB cable between your PC and your APF and you should see on your Host:<br /> &lt;pre class=&quot;host&quot;&gt;<br /> $ tail -f /var/log/messages<br /> Sep 27 10:06:38 ... usb 2-1.3: new high speed USB device using ehci_hcd and address 14<br /> Sep 27 10:06:38 ... usb 2-1.3: configuration #2 chosen from 1 choice<br /> Sep 27 10:06:38 ... cdc_acm 2-1.3:2.0: ttyACM0: USB ACM device<br /> Sep 27 10:06:38 ... usbcore: registered new interface driver cdc_acm<br /> Sep 27 10:06:38 ... cdc_acm: v0.26:USB Abstract Control Model driver for USB modems and ISDN adapters<br /> &lt;/pre&gt;<br /> * you should now be able to send/receive data through ''/dev/ttyACM0'' (PC) and ''/dev/ttyGS0'' (APF):<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # cat /dev/ttyGS0<br /> &lt;/pre&gt;<br /> &lt;pre class=&quot;host&quot;&gt;<br /> [armadeus]$ echo &quot;COUCOU&quot; &gt; /dev/ttyACM0<br /> &lt;/pre&gt;<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> COUCOU<br /> &lt;/pre&gt;<br /> <br /> ===To emulate an Ethernet link===<br /> * On your Target:<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # modprobe g_ether<br /> ether gadget: using random self ethernet address<br /> ether gadget: using random host ethernet address<br /> usb0: Ethernet Gadget, version: May Day 2005<br /> usb0: using imx_udc, OUT ep2out-bulk IN ep1in-bulk STATUS ep4in-int<br /> usb0: MAC be:df:31:95:16:e0<br /> usb0: HOST MAC 3e:86:1e:94:eb:84<br /> usb0: RNDIS ready<br /> &lt;/pre&gt;<br /> Now an IP address has to be assigned to the USB0 ethernet port <br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # ifconfig usb0 192.168.10.1<br /> &lt;/pre&gt;<br /> <br /> <br /> * On your PC:<br /> ** On '''Linux''' systems:&lt;pre class=&quot;host&quot;&gt;$ sudo modprobe cdc_ether&lt;/pre&gt;<br /> ** On '''Windows''' systems: &lt;br/&gt;When the target is detected, you will be asked to give the right driver. &lt;br/&gt;You will find it here: [http://www.armadeus.com/_downloads/apf27_PPS/windrivers/ APF27 PPS Windrivers].<br /> <br /> ==Links==<br /> <br /> * http://www.linux-usb.org/gadget/<br /> * http://www.linux-usb.org/usbtest/#gadgets<br /> * http://www.linux-usb.org/gadget/file_storage.html<br /> * http://lxr.linux.no/source/Documentation/usb/gadget_serial.txt<br /> * [[Serial_Transfer]]<br /> * http://www.linux-usb.org/usbnet/<br /> * http://wiki.gp2x.org/wiki/UsbNet_on_Linux<br /> <br /> [[Category:Linux drivers]]<br /> [[Category:USB]]</div> Salocin68 http://www.armadeus.org/wiki/index.php?title=USB_Host&diff=11455 USB Host 2012-12-05T13:45:58Z <p>Salocin68: </p> <hr /> <div>How-To use the USB Host functionnality of Armadeus boards under Linux.<br /> <br /> == Controller ==<br /> * [[APF9328DevFull|APF9328DevFull]]: it is equipped with a USB 2.0 Host controller (ISP1761) featuring three USB high speed ports. The ISP1761 driver is already configured with armadeus version 3. For older versions refer to the [[ISP1761_Linux_driver |how to install USB Host Linux driver for the DevFull]] page <br /> * [[APF27]] and [[APF27Dev]]: two Host ports are available. The controllers are integrated in the i.MX27 processor. Nothing has to be done to configure the controller. No special operation has to be done to use both USB ports (driver is included in default kernel).<br /> * [[APF27 PPS]]: one Host port and one OTG port (that can be forced to Host mode). Default Linux kernel has all the needed drivers compiled in.<br /> * [[APF51Dev]]: 2 Host ports and one OTG port (that can be forced to Host mode). Default Linux kernel has all the needed drivers compiled in.<br /> * [[PPS51]] one Host port and one OTG port (that can be forced to Host mode). Default Linux kernel has all the needed drivers compiled in.<br /> * [[APF28Dev]]: one Host port and one OTG port (Host/slave mode automatically switched depending on cable). Default Linux kernel has all the needed drivers compiled in.<br /> <br /> == Forcing an OTG controller to Host mode (APF27 and APF51)==<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> BIOS&gt; setenv extrabootargs otg_mode=host<br /> BIOS&gt; saveenv<br /> BIOS&gt; boot<br /> &lt;/pre&gt;<br /> <br /> == Using USB devices ==<br /> <br /> === USB keyboard/mouse (HID: Human Interface Device) ===<br /> ==== Driver installation ====<br /> * [[Talk:USB_Host|Done by default]] in recent releases<br /> <br /> ====Plug the keyboard====<br /> * you should see on console (here on APF9328 for example):<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> usb 1-1.1: new low speed USB device using isp1761 and address 3<br /> usb 1-1.1: configuration #1 chosen from 1 choice<br /> input: NOVATEK USB Keyboard as /class/input/input0<br /> input: USB HID v1.10 Keyboard [NOVATEK USB Keyboard] on usb-platform-1.1<br /> input: NOVATEK USB Keyboard as /class/input/input1<br /> input: USB HID v1.10 Mouse [NOVATEK USB Keyboard] on usb-platform-1.1<br /> &lt;/pre&gt;<br /> * To change keyboard keymap (by default US one is used):<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # loadkmap &lt; /etc/i18n/fr.kmap<br /> &lt;/pre&gt;<br /> <br /> ====Plug the mouse====<br /> * you should see on console (here on APF9328 for example):<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> usb 1-1.2: new low speed USB device using isp1761 and address 6<br /> usb 1-1.2: configuration #1 chosen from 1 choice<br /> input: Logitech USB-PS/2 Optical Mouse as /class/input/input6<br /> input: USB HID v1.10 Mouse [Logitech USB-PS/2 Optical Mouse] on usb-platform-1.2<br /> &lt;/pre&gt;<br /> <br /> === USB Flash memory / USB key / USB card reader / USB Hard Drive=== <br /> ==== Driver installation ====<br /> * [[Talk:USB_Host|Done by default]] in recent releases.<br /> <br /> ==== Plug the storage device ====<br /> * You should see (for example):<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> usb 1-1.2: new high speed USB device using isp1761 and address 6<br /> usb 1-1.2: configuration #1 chosen from 1 choice<br /> scsi0 : SCSI emulation for USB Mass Storage devices<br /> usb 1-1.2: reset high speed USB device using isp1761 and address 6<br /> scsi 0:0:0:0: Direct-Access Hama Card Reader CF 1.9C PQ: 0 ANSI: 0 CCS<br /> sd 0:0:0:0: [sda] Attached SCSI removable disk<br /> &lt;/pre&gt;<br /> <br /> ==== Additional configuration ====<br /> * If /dev/sdaX does not exist, then create it:<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # mknod /dev/sda b 8 0<br /> # mknod /dev/sda1 b 8 1<br /> # mknod /dev/sda2 b 8 2<br /> &lt;/pre&gt;<br /> * Create a mount directory &quot;usbdisk&quot;<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # mkdir -m 777 /mnt/usbdisk<br /> &lt;/pre&gt;<br /> <br /> ==== Mount the device ====<br /> * Mount the USB Mass Storage device<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # mount -t vfat /dev/sda1 /mnt/usbdisk<br /> &lt;/pre&gt;<br /> * Check what is present on the USB Mass Storage device:<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # ls -al /mnt/usbdisk<br /> &lt;/pre&gt;<br /> * And if it is well mounted (for example):<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # mount<br /> rootfs on / type rootfs (rw)<br /> /dev/root on / type jffs2 (rw)<br /> proc on /proc type proc (rw)<br /> devpts on /dev/pts type devpts (rw)<br /> tmpfs on /tmp type tmpfs (rw)<br /> sysfs on /sys type sysfs (rw)<br /> /dev/sda1 on /mnt/usbdisk type msdos (rw,fmask=0022,dmask=0022,codepage=cp437)<br /> &lt;/pre&gt;<br /> <br /> === USB &lt;--&gt; Serial adapters ===<br /> * See [[USB_to_serial_adapter]]<br /> <br /> === USB &lt;--&gt; WiFi adapters ===<br /> * See [[USB_to_WiFi_adapter]]<br /> <br /> == Links ==<br /> * Any links ?<br /> <br /> [[Category:BoardConnectivity]]<br /> [[Category:Linux drivers]]<br /> [[Category:USB]]</div> Salocin68 http://www.armadeus.org/wiki/index.php?title=GSM/GPRS&diff=11428 GSM/GPRS 2012-11-19T13:01:15Z <p>Salocin68: /* Usage */</p> <hr /> <div>This page will summarize informations to use the GSM/GPRS/3G module of the [[Wireless_extension_board|APF27Wireless board]] and the [[APF51Dev]] (optional).<br /> <br /> ==Introduction==<br /> GSM/GPRS are generally driven through the RS-232 bus. AT commands are used to dialog with the module.<br /> * GSM MODEM of the [[Wireless_extension_board|APF27Wireless extension board (APW)]] is connected to the UART2 (/dev/ttySMX1) of the [[APF27]].<br /> * GSM/3G MODEM of the [[APF51Dev]] is connected to the i.MX processor through an UART implemented in the FPGA. So the corresponding bitfile has to loaded before trying to access the MODEM.<br /> Both are using a Sagem's Hilo module. Hilo AT commands can be found [http://www.libelium.com/tienda/catalog/images/arduino/AT_Commands.pdf here]<br /> <br /> ==Linux configuration (APF27Dev only)==<br /> * Linux will have to be configured in order to tell that an APW is connected to your [[APF27Dev]]:<br /> &lt;pre class=&quot;host&quot;&gt;<br /> $ make linux26-menuconfig<br /> &lt;/pre&gt;<br /> &lt;pre class=&quot;config&quot;&gt;<br /> System Type ---&gt;<br /> Freescale MXC Implementations ---&gt;<br /> ...<br /> Extension board (Wireless (APW)) ---&gt;<br /> [*] GSM/GPRS Modem (NEW)<br /> [ ] Bluetooth &amp; WiFi module (NEW)<br /> [ ] CSI (Camera) pass-through (NEW)<br /> [ ] GPS module (NEW)<br /> &lt;/pre&gt;<br /> <br /> &lt;pre class=&quot;host&quot;&gt;<br /> $ make linux26<br /> &lt;/pre&gt;<br /> * reflash you Linux kernel<br /> <br /> ==Configure serial port==<br /> ====APF27====<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # export GSM_DEVICE=/dev/ttySMX1 (or /dev/ttymxc1 on recent kernels)<br /> # stty -F $GSM_DEVICE raw -echo -echoe -echok 115200<br /> &lt;/pre&gt;<br /> <br /> ====APF51Dev====<br /> <br /> {{Note|Don't forget to put &quot;Wireless&quot; J42 jumper (near microSD connector) '''AND''' power on FPGA Bank 3 (with corresponding J39 jumper).}}<br /> * On APF51Dev, GSM/3G module is accessed through serial ports synthetized in APF51's FPGA. So we have to load it first. (Needed dual UARTs FPGA firmware can be found under armadeus-4.0 distribution in ''firmware/pod_scripts'' directory, with the [[POD]] script needed to regenerate it, and is by default installed in rootfs).<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # load_fpga /lib/firmware/fpga/apf51_gsm_gps_firmware.bin<br /> &lt;/pre&gt;<br /> * Once firmware loaded, drivers related to FPGA can be used :<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # modprobe irq_ocore<br /> # modprobe 8250<br /> Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled<br /> # modprobe twin_uarts_irq_mng<br /> # modprobe twin_uarts_16750<br /> serial8250.0: ttyS0 at MMIO 0xb8000020 (irq = 320) is a TI16750<br /> serial8250.0: ttyS1 at MMIO 0xb8000040 (irq = 321) is a TI16750<br /> &lt;/pre&gt;<br /> * Bring MODEM out of reset state (POK_IN/PWON pin, connected to [[APF51_PMIC#GPIO|PMIC GPIO6]]):<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # modprobe wm831x-gpio<br /> # echo 245 &gt; /sys/class/gpio/export<br /> # echo out &gt; /sys/class/gpio/gpio245/direction<br /> # echo 1 &gt; /sys/class/gpio/gpio245/value<br /> &lt;/pre&gt;<br /> * Configure serial port:<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # ls /dev/ttyS*<br /> /dev/ttyS0 /dev/ttyS1 /dev/ttyS2 /dev/ttyS3<br /> &lt;/pre&gt;<br /> <br /> * If the /dev/ttyS[0-1] files don't exist, create it/them with ''mknod'' :<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # mknod /dev/ttyS0 c 4 64<br /> # mknod /dev/ttyS1 c 4 65<br /> &lt;/pre&gt;<br /> Then :<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # export GSM_DEVICE=/dev/ttyS0<br /> # stty -F $GSM_DEVICE -echo -echoe -echok 115200<br /> &lt;/pre&gt;<br /> <br /> ==Basic Usage==<br /> ===Sending AT commands &quot;manually&quot;===<br /> * Sending AT commands with ''minicom'' utility (one of the command coming with [[busybox]]):<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # minicom $GSM_DEVICE<br /> &lt;/pre&gt;<br /> ( To exit ''minocom'' you will have to type '''&lt;CTRL-x&gt;''' )<br /> * Check module presence:<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> ATI3<br /> SAGEM HiC,A.005.00<br /> <br /> OK<br /> &lt;/pre&gt;<br /> <br /> {{Note| If no echo are printed on serial console: you can't see what you're typing. In that case, to reactivate the echo, use:<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> ATE1<br /> &lt;/pre&gt;<br /> }}<br /> <br /> {{Note| By default, the module starts in auto baudrate. This mays result in loss of communication with baud rate higher than 19200 bauds. To avoid problems, the baud rate has to be fixed (here to 115200 bauds):<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> AT+IPR=115200<br /> &lt;/pre&gt;<br /> }}<br /> <br /> * Get constructor name:<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> AT+CGMI<br /> SAGEM<br /> <br /> OK<br /> &lt;/pre&gt;<br /> * Get model name:<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> AT+CGMM<br /> HILO GPRS<br /> <br /> OK<br /> &lt;/pre&gt;<br /> * Enter PIN code (here 0000). '''!! Use your own and beware that you will only get 3 tries !!:'''<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> AT+CPIN=&quot;0000&quot;<br /> <br /> OK<br /> &lt;/pre&gt;<br /> * Check PIN code status:<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> AT+CPIN?<br /> +CPIN: READY<br /> <br /> OK<br /> &lt;/pre&gt;<br /> {{Note|Don't launch further AT commands if PIN code wasn't entered successfully}}<br /> <br /> * Check module status (0 Ready, 1 Unavailable, 2 Status unknown, 3 Ringing, 4 Call in progress, 5 Asleep):<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> AT+CPAS<br /> +CPAS: 0<br /> <br /> OK<br /> &lt;/pre&gt;<br /> * Get Indicator control (&lt;battchg&gt;[0-4],&lt;signal&gt;[0-4],&lt;service&gt;0/1,&lt;message&gt;0/1,&lt;call&gt;0/1,&lt;smsfull&gt;0/1):<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> AT+CIND?<br /> +CIND: 0,4,1,0,0,0,1<br /> <br /> OK<br /> &lt;/pre&gt;<br /> * Get signal quality (should be better than 12/99):<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> AT+CSQ<br /> +CSQ: 24,99<br /> <br /> OK<br /> &lt;/pre&gt;<br /> * Voice call &quot;123456789&quot; (; is important here to signify a voice call, otherwise a data call is tried and may fail if you don't have the right subscribe)<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> ATD&quot;123456789&quot;;<br /> OK<br /> &lt;/pre&gt;<br /> * Terminate current call:<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> ATH<br /> OK<br /> &lt;/pre&gt;<br /> <br /> ===Sending AT commands in shell scripts===<br /> <br /> &lt;source lang=&quot;bash&quot;&gt;<br /> GSM_DEVICE=/dev/ttyXXX<br /> send_at_cmd()<br /> {<br /> echo -e -n &quot;$1\015&quot; &gt; $GSM_DEVICE<br /> sleep 1 # Adjustable ! (usleep)<br /> }<br /> <br /> send_at_cmd AT<br /> &lt;/source&gt;<br /> <br /> * See ''target/test/test_gsm.sh'' for more details<br /> <br /> ==Sending SMS==<br /> * Supposing you are already connected to the modem with cu<br /> * Check if you can send SMS with your SIM card (you should get +CMGF: (0,1))<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> AT+CMGF=?<br /> &lt;/pre&gt;<br /> * If OK, switch to SMS sending mode:<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> AT+CMGF=1<br /> &lt;/pre&gt;<br /> * Write a message for 0661234567 phone number:<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> AT+CMGW=&quot;0661326109&quot;<br /> <br /> &gt; Hey ! How are you doing ??<br /> &gt; &lt;-- Ctrl+z to end SMS here<br /> <br /> +CMGW: 8<br /> &lt;/pre&gt;<br /> * +CMGW give you the number of your SMS saved in SIM card or phone memory<br /> * Then, at anytime, you can send your SMS with (pass previous number as parameter):<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> AT+CMSS=8<br /> &lt;/pre&gt;<br /> <br /> ==Tools to look at==<br /> * http://www.developershome.com/sms/freeLibForSMS.asp<br /> * http://www.gnokii.org/<br /> * http://www.alamin.org/en/index.html<br /> * http://www.gammu.org/wiki/index.php?title=Gammu:Main_Page<br /> * http://gatling.ikk.sztaki.hu/~kissg/gsm/index.html<br /> <br /> ==Data tranfers (EDGE/3G)==<br /> <br /> ===PPP installation (done by default on APF51)===<br /> &lt;pre class=&quot;host&quot;&gt;<br /> $ make linux26-menuconfig<br /> &lt;/pre&gt;<br /> <br /> &lt;pre class=&quot;config&quot;&gt;<br /> Device Drivers ---&gt;<br /> [*] Network device support ---&gt;<br /> &lt;M&gt; PPP (point-to-point protocol) support<br /> [ ] PPP multilink support (EXPERIMENTAL)<br /> [ ] PPP filtering<br /> &lt;M&gt; PPP support for async serial ports<br /> &lt; &gt; PPP support for sync tty ports<br /> &lt; &gt; PPP Deflate compression<br /> &lt; &gt; PPP BSD-Compress compression<br /> &lt; &gt; PPP MPPE compression (encryption) (EXPERIMENTAL)<br /> &lt; &gt; PPP over Ethernet (EXPERIMENTAL)<br /> &lt;/pre&gt;<br /> <br /> &lt;pre class=&quot;host&quot;&gt;<br /> $ make menuconfig<br /> &lt;/pre&gt;<br /> <br /> &lt;pre class=&quot;config&quot;&gt;<br /> Package Selection for the target ---&gt;<br /> Networking applications ---&gt;<br /> [*] pppd<br /> [ ] filtering<br /> [ ] radius<br /> &lt;/pre&gt;<br /> <br /> &lt;pre class=&quot;host&quot;&gt;<br /> $ make linux26 &amp;&amp; make<br /> &lt;/pre&gt;<br /> <br /> * reflash kernel &amp; rootfs<br /> <br /> ===PPP configuration===<br /> {{Note|Following instructions are given for the French operator &quot;Bouygtel&quot; and may need to be ajusted accordingly, depending on your operator/country}}<br /> <br /> * Create a &quot;chat&quot; script that will be used to initiate MODEM dialup (here we use the &quot;cat &gt; xxxx &lt;&lt; EOF trick&quot; to automatically create the file, but you can also manually edit it with ''vi'' or ''nano''):<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # mkdir -p /etc/chatscripts/<br /> # cat &gt; /etc/chatscripts/bouygtel &lt;&lt;EOF<br /> ABORT BUSY ABORT 'NO CARRIER' ABORT VOICE ABORT 'NO DIALTONE' ABORT 'NO ANSWER' ABORT DELAYED ABORT ERROR<br /> '' AT<br /> OK AT+IPR=115200<br /> OK AT+CPIN=&quot;0000&quot;<br /> OK AT+CFUN=1<br /> OK AT+COPS?<br /> OK AT+CSQ<br /> OK 'AT+CGDCONT=1,&quot;IP&quot;,&quot;ebouygtel.com&quot;,&quot;&quot;,0,0'<br /> OK 'AT&amp;FE0Q0V1'<br /> OK 'ATD*99#'<br /> CONNECT &quot;&quot;<br /> EOF<br /> &lt;/pre&gt;<br /> * Don't forget to set the baudrate (default: 115200) to have a stable communication between the modem and the processor<br /> * Don't forget to update &quot;AT+CPIN=&quot; with your real PIN code and &quot;AT+CGDCONT&quot; and &quot;ATD*99#&quot; with your operator parameters.<br /> * If you want to test your chat script (verbose mode -v, on console -s, with 5 second timeout by default for commands -t 5), then launch:<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # /usr/sbin/chat -v -s -t 5 -f /etc/chatscripts/bouygtel &gt; $GSM_DEVICE &lt; $GSM_DEVICE<br /> &lt;/pre&gt;<br /> * If this test was OK, you may have to poweroff/poweron the MODEM to bring it to its initial state and go further.<br /> <br /> ====For '''APF51'''====<br /> * create the PPPd config files (''/etc/ppp/peers/bouygtel'' and ''/etc/ppp/options.ttyS0''):<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # mkdir -p /etc/ppp/peers/<br /> # cat &gt; /etc/ppp/peers/bouygtel &lt;&lt;EOF<br /> noauth<br /> connect &quot;/usr/sbin/chat -v -t 5 -f /etc/chatscripts/bouygtel&quot;<br /> debug<br /> ttyS0<br /> defaultroute<br /> noipdefault<br /> usepeerdns<br /> EOF<br /> <br /> # cat &gt; /etc/ppp/options.ttyS0 &lt;&lt;EOF<br /> 115200<br /> EOF<br /> &lt;/pre&gt;<br /> <br /> ====For '''APF27'''====<br /> {{Note| Check if /dev/ttySMX1 exists, if not create it with :<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> mknod /dev/ttySMX1 c 204 42<br /> &lt;/pre&gt;<br /> }}<br /> * create the PPPd config files (''/etc/ppp/peers/bouygtel'' and ''/etc/ppp/options.ttySMX1''):<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # mkdir -p /etc/ppp/peers/<br /> # cat &gt; /etc/ppp/peers/bouygtel &lt;&lt;EOF<br /> noauth<br /> connect &quot;/usr/sbin/chat -v -t 5 -f /etc/chatscripts/bouygtel&quot;<br /> debug<br /> ttySMX1<br /> defaultroute<br /> noipdefault<br /> usepeerdns<br /> EOF<br /> <br /> # cat &gt; /etc/ppp/options.ttySMX1 &lt;&lt;EOF<br /> 115200<br /> EOF<br /> &lt;/pre&gt;<br /> <br /> ===PPP Usage===<br /> * Load PPP module:<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # modprobe ppp (APF27)<br /> or<br /> # modprobe ppp_async (APF51)<br /> &lt;/pre&gt;<br /> * Setup serial port name depending on your platform (''/dev/ttyS0'' on APF51, ''/dev/ttySMX1'' on APF27)<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # export GSM_DEVICE=/dev/ttyS0<br /> or<br /> # export GSM_DEVICE=/dev/ttySMX1<br /> &lt;/pre&gt;<br /> <br /> * Launch the beast:<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # pppd $GSM_DEVICE 115200 call bouygtel<br /> &lt;/pre&gt;<br /> <br /> ===Test===<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # ping www.google.fr<br /> &lt;/pre&gt;<br /> <br /> === Troubleshots ===<br /> * Might be needed after a successful IP setup:<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # cp /etc/ppp/resolv.conf /etc/resolv.conf<br /> # route add default ppp0 (due to defaultroute option in ppp ?)<br /> &lt;/pre&gt;<br /> <br /> * To see what happened after having launched ''pppd'' or ''chat'':<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # tail -f /var/log/messages<br /> &lt;/pre&gt;<br /> <br /> ==GSM Muxing==<br /> ===Why ?===<br /> * By default AT commands usage is single threaded, ie only one program can open MODEM serial port and send AT commands at a given time. However it could be interesting to be able to send multiple AT commands from multiple programs at the same time, for example in order to: have a PPP link, send SMS and monitor network signal quality.<br /> * This can be done by a &quot;GSM mux&quot;, if your MODEM support the GSM 07.10 muxing norm (which is the case with our HiLo modules).<br /> ===Build gsmmux===<br /> * To build GSM mux (if not already done):<br /> &lt;pre class=&quot;host&quot;&gt;<br /> $ make menuconfig<br /> &lt;/pre&gt;<br /> &lt;pre class=&quot;config&quot;&gt;<br /> Package Selection for the target ---&gt;<br /> Hardware handling ---&gt;<br /> [*] gsmmux<br /> Version to use (sagem) ---&gt;<br /> &lt;/pre&gt;<br /> &lt;pre class=&quot;host&quot;&gt;<br /> $ make<br /> &lt;/pre&gt;<br /> <br /> ===Use it===<br /> * If you have access to Sagem's version (you will get as much as virtual serial port as times you pass ''/dev/ptmx'' to the daemon):<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # gsmMuxd -p $GSM_DEVICE -b 115200 -x /dev/ptmx /dev/ptmx /dev/ptmx<br /> &lt;/pre&gt;<br /> * Virtual serial ports will be created in ''/dev/pts/'':<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> /dev/pts/0 /dev/pts/1 /dev/pts/2<br /> &lt;/pre&gt;<br /> * to know how ''/dev/ptmx'' &amp; ''/dev/pts/x'' is working: [http://linux.die.net/man/4/ptmx]<br /> * If you have telnet or SSH sessions running ''/dev/pts/0'' may already be used ans so virtual serial ports will be allocated from ''/dev/pts/1'', etc...<br /> <br /> ===Going further===<br /> * In recent Linux kernels, there is also a driver to hanlde GSM muxing: n_gsm<br /> * People wanting to do a &quot;real&quot; phone can take a look at [http://ofono.org/documentation ofono]<br /> <br /> ==SMS using SMS server tools 3==<br /> simple AT commands can be used to sent SMS. If you need more flexibility or advanced management of your SMS, you can use SMS Server Tools 3.<br /> SMS Server Tools 3 is a SMS Gateway software which can send and receive short messages through GSM modems and mobile phones.<br /> <br /> ===Build SMS Server Tools3===<br /> * To build SMS Server Tools 3:<br /> &lt;pre class=&quot;host&quot;&gt;<br /> $ make menuconfig<br /> &lt;/pre&gt;<br /> &lt;pre class=&quot;config&quot;&gt;<br /> Package Selection for the target ---&gt;<br /> Hardware handling ---&gt;<br /> [*] SMS Server Tools3<br /> &lt;/pre&gt;<br /> &lt;pre class=&quot;host&quot;&gt;<br /> $ make<br /> &lt;/pre&gt;<br /> <br /> === Configuration ===<br /> The SMS server can be configured by using a configuration file (smsd.conf) located on the target in the /etc/smsd directory.<br /> The following parameters have to be verified:<br /> * device: uart port used to communicate with the modem. If GSMUX is used, then this parameter is of form /dev/pts/x where is x is the number of the virtual port<br /> * baudrate: baudrate of the uart port<br /> * rtscts: must be yes<br /> * incoming: yes if you want to receive SMS<br /> <br /> === Usage ===<br /> start the sms deamon:<br /> &lt;pre class=&quot;host&quot;&gt;<br /> smsd -c /etc/smsd/smsd.conf<br /> &lt;/pre&gt;<br /> Then put a SMS file in the /var/spool/outgoing directory. Once placed a SMS will be sent.<br /> <br /> Incoming SMS can be read in the /var/spool/incoming directory.<br /> <br /> Reports and logs are also generated.<br /> <br /> ==Links==<br /> * [http://support.sagemcom.com/site/modele_fax.php?page=produit&amp;numero_type=22&amp;produit=877 HiLo 3G documentation at Sagem]<br /> * [http://www.libelium.com/tienda/catalog/images/arduino/AT_Commands.pdf HiLo AT Commands]<br /> * [http://www.developershome.com/sms/ SMS tutorial]<br /> * http://wiki.openmoko.org/wiki/Neo_1973_and_Neo_FreeRunner_gsm_modem<br /> * [http://www.anotherurl.com/library/at_test.htm AT Test commands]<br /> * http://www.gsm-modem.de/gsm-faq.html<br /> * [http://www.technologuepro.com/gsm/commande_at.htm Les commandes AT]<br /> * [http://smstools3.kekekasvi.com SMS Server Tools 3]<br /> <br /> [[Category:Wireless]]</div> Salocin68 http://www.armadeus.org/wiki/index.php?title=GSM/GPRS&diff=11427 GSM/GPRS 2012-11-19T13:00:59Z <p>Salocin68: /* SMS using SMS server tools 3 */</p> <hr /> <div>This page will summarize informations to use the GSM/GPRS/3G module of the [[Wireless_extension_board|APF27Wireless board]] and the [[APF51Dev]] (optional).<br /> <br /> ==Introduction==<br /> GSM/GPRS are generally driven through the RS-232 bus. AT commands are used to dialog with the module.<br /> * GSM MODEM of the [[Wireless_extension_board|APF27Wireless extension board (APW)]] is connected to the UART2 (/dev/ttySMX1) of the [[APF27]].<br /> * GSM/3G MODEM of the [[APF51Dev]] is connected to the i.MX processor through an UART implemented in the FPGA. So the corresponding bitfile has to loaded before trying to access the MODEM.<br /> Both are using a Sagem's Hilo module. Hilo AT commands can be found [http://www.libelium.com/tienda/catalog/images/arduino/AT_Commands.pdf here]<br /> <br /> ==Linux configuration (APF27Dev only)==<br /> * Linux will have to be configured in order to tell that an APW is connected to your [[APF27Dev]]:<br /> &lt;pre class=&quot;host&quot;&gt;<br /> $ make linux26-menuconfig<br /> &lt;/pre&gt;<br /> &lt;pre class=&quot;config&quot;&gt;<br /> System Type ---&gt;<br /> Freescale MXC Implementations ---&gt;<br /> ...<br /> Extension board (Wireless (APW)) ---&gt;<br /> [*] GSM/GPRS Modem (NEW)<br /> [ ] Bluetooth &amp; WiFi module (NEW)<br /> [ ] CSI (Camera) pass-through (NEW)<br /> [ ] GPS module (NEW)<br /> &lt;/pre&gt;<br /> <br /> &lt;pre class=&quot;host&quot;&gt;<br /> $ make linux26<br /> &lt;/pre&gt;<br /> * reflash you Linux kernel<br /> <br /> ==Configure serial port==<br /> ====APF27====<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # export GSM_DEVICE=/dev/ttySMX1 (or /dev/ttymxc1 on recent kernels)<br /> # stty -F $GSM_DEVICE raw -echo -echoe -echok 115200<br /> &lt;/pre&gt;<br /> <br /> ====APF51Dev====<br /> <br /> {{Note|Don't forget to put &quot;Wireless&quot; J42 jumper (near microSD connector) '''AND''' power on FPGA Bank 3 (with corresponding J39 jumper).}}<br /> * On APF51Dev, GSM/3G module is accessed through serial ports synthetized in APF51's FPGA. So we have to load it first. (Needed dual UARTs FPGA firmware can be found under armadeus-4.0 distribution in ''firmware/pod_scripts'' directory, with the [[POD]] script needed to regenerate it, and is by default installed in rootfs).<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # load_fpga /lib/firmware/fpga/apf51_gsm_gps_firmware.bin<br /> &lt;/pre&gt;<br /> * Once firmware loaded, drivers related to FPGA can be used :<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # modprobe irq_ocore<br /> # modprobe 8250<br /> Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled<br /> # modprobe twin_uarts_irq_mng<br /> # modprobe twin_uarts_16750<br /> serial8250.0: ttyS0 at MMIO 0xb8000020 (irq = 320) is a TI16750<br /> serial8250.0: ttyS1 at MMIO 0xb8000040 (irq = 321) is a TI16750<br /> &lt;/pre&gt;<br /> * Bring MODEM out of reset state (POK_IN/PWON pin, connected to [[APF51_PMIC#GPIO|PMIC GPIO6]]):<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # modprobe wm831x-gpio<br /> # echo 245 &gt; /sys/class/gpio/export<br /> # echo out &gt; /sys/class/gpio/gpio245/direction<br /> # echo 1 &gt; /sys/class/gpio/gpio245/value<br /> &lt;/pre&gt;<br /> * Configure serial port:<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # ls /dev/ttyS*<br /> /dev/ttyS0 /dev/ttyS1 /dev/ttyS2 /dev/ttyS3<br /> &lt;/pre&gt;<br /> <br /> * If the /dev/ttyS[0-1] files don't exist, create it/them with ''mknod'' :<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # mknod /dev/ttyS0 c 4 64<br /> # mknod /dev/ttyS1 c 4 65<br /> &lt;/pre&gt;<br /> Then :<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # export GSM_DEVICE=/dev/ttyS0<br /> # stty -F $GSM_DEVICE -echo -echoe -echok 115200<br /> &lt;/pre&gt;<br /> <br /> ==Basic Usage==<br /> ===Sending AT commands &quot;manually&quot;===<br /> * Sending AT commands with ''minicom'' utility (one of the command coming with [[busybox]]):<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # minicom $GSM_DEVICE<br /> &lt;/pre&gt;<br /> ( To exit ''minocom'' you will have to type '''&lt;CTRL-x&gt;''' )<br /> * Check module presence:<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> ATI3<br /> SAGEM HiC,A.005.00<br /> <br /> OK<br /> &lt;/pre&gt;<br /> <br /> {{Note| If no echo are printed on serial console: you can't see what you're typing. In that case, to reactivate the echo, use:<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> ATE1<br /> &lt;/pre&gt;<br /> }}<br /> <br /> {{Note| By default, the module starts in auto baudrate. This mays result in loss of communication with baud rate higher than 19200 bauds. To avoid problems, the baud rate has to be fixed (here to 115200 bauds):<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> AT+IPR=115200<br /> &lt;/pre&gt;<br /> }}<br /> <br /> * Get constructor name:<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> AT+CGMI<br /> SAGEM<br /> <br /> OK<br /> &lt;/pre&gt;<br /> * Get model name:<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> AT+CGMM<br /> HILO GPRS<br /> <br /> OK<br /> &lt;/pre&gt;<br /> * Enter PIN code (here 0000). '''!! Use your own and beware that you will only get 3 tries !!:'''<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> AT+CPIN=&quot;0000&quot;<br /> <br /> OK<br /> &lt;/pre&gt;<br /> * Check PIN code status:<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> AT+CPIN?<br /> +CPIN: READY<br /> <br /> OK<br /> &lt;/pre&gt;<br /> {{Note|Don't launch further AT commands if PIN code wasn't entered successfully}}<br /> <br /> * Check module status (0 Ready, 1 Unavailable, 2 Status unknown, 3 Ringing, 4 Call in progress, 5 Asleep):<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> AT+CPAS<br /> +CPAS: 0<br /> <br /> OK<br /> &lt;/pre&gt;<br /> * Get Indicator control (&lt;battchg&gt;[0-4],&lt;signal&gt;[0-4],&lt;service&gt;0/1,&lt;message&gt;0/1,&lt;call&gt;0/1,&lt;smsfull&gt;0/1):<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> AT+CIND?<br /> +CIND: 0,4,1,0,0,0,1<br /> <br /> OK<br /> &lt;/pre&gt;<br /> * Get signal quality (should be better than 12/99):<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> AT+CSQ<br /> +CSQ: 24,99<br /> <br /> OK<br /> &lt;/pre&gt;<br /> * Voice call &quot;123456789&quot; (; is important here to signify a voice call, otherwise a data call is tried and may fail if you don't have the right subscribe)<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> ATD&quot;123456789&quot;;<br /> OK<br /> &lt;/pre&gt;<br /> * Terminate current call:<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> ATH<br /> OK<br /> &lt;/pre&gt;<br /> <br /> ===Sending AT commands in shell scripts===<br /> <br /> &lt;source lang=&quot;bash&quot;&gt;<br /> GSM_DEVICE=/dev/ttyXXX<br /> send_at_cmd()<br /> {<br /> echo -e -n &quot;$1\015&quot; &gt; $GSM_DEVICE<br /> sleep 1 # Adjustable ! (usleep)<br /> }<br /> <br /> send_at_cmd AT<br /> &lt;/source&gt;<br /> <br /> * See ''target/test/test_gsm.sh'' for more details<br /> <br /> ==Sending SMS==<br /> * Supposing you are already connected to the modem with cu<br /> * Check if you can send SMS with your SIM card (you should get +CMGF: (0,1))<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> AT+CMGF=?<br /> &lt;/pre&gt;<br /> * If OK, switch to SMS sending mode:<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> AT+CMGF=1<br /> &lt;/pre&gt;<br /> * Write a message for 0661234567 phone number:<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> AT+CMGW=&quot;0661326109&quot;<br /> <br /> &gt; Hey ! How are you doing ??<br /> &gt; &lt;-- Ctrl+z to end SMS here<br /> <br /> +CMGW: 8<br /> &lt;/pre&gt;<br /> * +CMGW give you the number of your SMS saved in SIM card or phone memory<br /> * Then, at anytime, you can send your SMS with (pass previous number as parameter):<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> AT+CMSS=8<br /> &lt;/pre&gt;<br /> <br /> ==Tools to look at==<br /> * http://www.developershome.com/sms/freeLibForSMS.asp<br /> * http://www.gnokii.org/<br /> * http://www.alamin.org/en/index.html<br /> * http://www.gammu.org/wiki/index.php?title=Gammu:Main_Page<br /> * http://gatling.ikk.sztaki.hu/~kissg/gsm/index.html<br /> <br /> ==Data tranfers (EDGE/3G)==<br /> <br /> ===PPP installation (done by default on APF51)===<br /> &lt;pre class=&quot;host&quot;&gt;<br /> $ make linux26-menuconfig<br /> &lt;/pre&gt;<br /> <br /> &lt;pre class=&quot;config&quot;&gt;<br /> Device Drivers ---&gt;<br /> [*] Network device support ---&gt;<br /> &lt;M&gt; PPP (point-to-point protocol) support<br /> [ ] PPP multilink support (EXPERIMENTAL)<br /> [ ] PPP filtering<br /> &lt;M&gt; PPP support for async serial ports<br /> &lt; &gt; PPP support for sync tty ports<br /> &lt; &gt; PPP Deflate compression<br /> &lt; &gt; PPP BSD-Compress compression<br /> &lt; &gt; PPP MPPE compression (encryption) (EXPERIMENTAL)<br /> &lt; &gt; PPP over Ethernet (EXPERIMENTAL)<br /> &lt;/pre&gt;<br /> <br /> &lt;pre class=&quot;host&quot;&gt;<br /> $ make menuconfig<br /> &lt;/pre&gt;<br /> <br /> &lt;pre class=&quot;config&quot;&gt;<br /> Package Selection for the target ---&gt;<br /> Networking applications ---&gt;<br /> [*] pppd<br /> [ ] filtering<br /> [ ] radius<br /> &lt;/pre&gt;<br /> <br /> &lt;pre class=&quot;host&quot;&gt;<br /> $ make linux26 &amp;&amp; make<br /> &lt;/pre&gt;<br /> <br /> * reflash kernel &amp; rootfs<br /> <br /> ===PPP configuration===<br /> {{Note|Following instructions are given for the French operator &quot;Bouygtel&quot; and may need to be ajusted accordingly, depending on your operator/country}}<br /> <br /> * Create a &quot;chat&quot; script that will be used to initiate MODEM dialup (here we use the &quot;cat &gt; xxxx &lt;&lt; EOF trick&quot; to automatically create the file, but you can also manually edit it with ''vi'' or ''nano''):<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # mkdir -p /etc/chatscripts/<br /> # cat &gt; /etc/chatscripts/bouygtel &lt;&lt;EOF<br /> ABORT BUSY ABORT 'NO CARRIER' ABORT VOICE ABORT 'NO DIALTONE' ABORT 'NO ANSWER' ABORT DELAYED ABORT ERROR<br /> '' AT<br /> OK AT+IPR=115200<br /> OK AT+CPIN=&quot;0000&quot;<br /> OK AT+CFUN=1<br /> OK AT+COPS?<br /> OK AT+CSQ<br /> OK 'AT+CGDCONT=1,&quot;IP&quot;,&quot;ebouygtel.com&quot;,&quot;&quot;,0,0'<br /> OK 'AT&amp;FE0Q0V1'<br /> OK 'ATD*99#'<br /> CONNECT &quot;&quot;<br /> EOF<br /> &lt;/pre&gt;<br /> * Don't forget to set the baudrate (default: 115200) to have a stable communication between the modem and the processor<br /> * Don't forget to update &quot;AT+CPIN=&quot; with your real PIN code and &quot;AT+CGDCONT&quot; and &quot;ATD*99#&quot; with your operator parameters.<br /> * If you want to test your chat script (verbose mode -v, on console -s, with 5 second timeout by default for commands -t 5), then launch:<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # /usr/sbin/chat -v -s -t 5 -f /etc/chatscripts/bouygtel &gt; $GSM_DEVICE &lt; $GSM_DEVICE<br /> &lt;/pre&gt;<br /> * If this test was OK, you may have to poweroff/poweron the MODEM to bring it to its initial state and go further.<br /> <br /> ====For '''APF51'''====<br /> * create the PPPd config files (''/etc/ppp/peers/bouygtel'' and ''/etc/ppp/options.ttyS0''):<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # mkdir -p /etc/ppp/peers/<br /> # cat &gt; /etc/ppp/peers/bouygtel &lt;&lt;EOF<br /> noauth<br /> connect &quot;/usr/sbin/chat -v -t 5 -f /etc/chatscripts/bouygtel&quot;<br /> debug<br /> ttyS0<br /> defaultroute<br /> noipdefault<br /> usepeerdns<br /> EOF<br /> <br /> # cat &gt; /etc/ppp/options.ttyS0 &lt;&lt;EOF<br /> 115200<br /> EOF<br /> &lt;/pre&gt;<br /> <br /> ====For '''APF27'''====<br /> {{Note| Check if /dev/ttySMX1 exists, if not create it with :<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> mknod /dev/ttySMX1 c 204 42<br /> &lt;/pre&gt;<br /> }}<br /> * create the PPPd config files (''/etc/ppp/peers/bouygtel'' and ''/etc/ppp/options.ttySMX1''):<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # mkdir -p /etc/ppp/peers/<br /> # cat &gt; /etc/ppp/peers/bouygtel &lt;&lt;EOF<br /> noauth<br /> connect &quot;/usr/sbin/chat -v -t 5 -f /etc/chatscripts/bouygtel&quot;<br /> debug<br /> ttySMX1<br /> defaultroute<br /> noipdefault<br /> usepeerdns<br /> EOF<br /> <br /> # cat &gt; /etc/ppp/options.ttySMX1 &lt;&lt;EOF<br /> 115200<br /> EOF<br /> &lt;/pre&gt;<br /> <br /> ===PPP Usage===<br /> * Load PPP module:<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # modprobe ppp (APF27)<br /> or<br /> # modprobe ppp_async (APF51)<br /> &lt;/pre&gt;<br /> * Setup serial port name depending on your platform (''/dev/ttyS0'' on APF51, ''/dev/ttySMX1'' on APF27)<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # export GSM_DEVICE=/dev/ttyS0<br /> or<br /> # export GSM_DEVICE=/dev/ttySMX1<br /> &lt;/pre&gt;<br /> <br /> * Launch the beast:<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # pppd $GSM_DEVICE 115200 call bouygtel<br /> &lt;/pre&gt;<br /> <br /> ===Test===<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # ping www.google.fr<br /> &lt;/pre&gt;<br /> <br /> === Troubleshots ===<br /> * Might be needed after a successful IP setup:<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # cp /etc/ppp/resolv.conf /etc/resolv.conf<br /> # route add default ppp0 (due to defaultroute option in ppp ?)<br /> &lt;/pre&gt;<br /> <br /> * To see what happened after having launched ''pppd'' or ''chat'':<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # tail -f /var/log/messages<br /> &lt;/pre&gt;<br /> <br /> ==GSM Muxing==<br /> ===Why ?===<br /> * By default AT commands usage is single threaded, ie only one program can open MODEM serial port and send AT commands at a given time. However it could be interesting to be able to send multiple AT commands from multiple programs at the same time, for example in order to: have a PPP link, send SMS and monitor network signal quality.<br /> * This can be done by a &quot;GSM mux&quot;, if your MODEM support the GSM 07.10 muxing norm (which is the case with our HiLo modules).<br /> ===Build gsmmux===<br /> * To build GSM mux (if not already done):<br /> &lt;pre class=&quot;host&quot;&gt;<br /> $ make menuconfig<br /> &lt;/pre&gt;<br /> &lt;pre class=&quot;config&quot;&gt;<br /> Package Selection for the target ---&gt;<br /> Hardware handling ---&gt;<br /> [*] gsmmux<br /> Version to use (sagem) ---&gt;<br /> &lt;/pre&gt;<br /> &lt;pre class=&quot;host&quot;&gt;<br /> $ make<br /> &lt;/pre&gt;<br /> <br /> ===Use it===<br /> * If you have access to Sagem's version (you will get as much as virtual serial port as times you pass ''/dev/ptmx'' to the daemon):<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # gsmMuxd -p $GSM_DEVICE -b 115200 -x /dev/ptmx /dev/ptmx /dev/ptmx<br /> &lt;/pre&gt;<br /> * Virtual serial ports will be created in ''/dev/pts/'':<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> /dev/pts/0 /dev/pts/1 /dev/pts/2<br /> &lt;/pre&gt;<br /> * to know how ''/dev/ptmx'' &amp; ''/dev/pts/x'' is working: [http://linux.die.net/man/4/ptmx]<br /> * If you have telnet or SSH sessions running ''/dev/pts/0'' may already be used ans so virtual serial ports will be allocated from ''/dev/pts/1'', etc...<br /> <br /> ===Going further===<br /> * In recent Linux kernels, there is also a driver to hanlde GSM muxing: n_gsm<br /> * People wanting to do a &quot;real&quot; phone can take a look at [http://ofono.org/documentation ofono]<br /> <br /> ==SMS using SMS server tools 3==<br /> simple AT commands can be used to sent SMS. If you need more flexibility or advanced management of your SMS, you can use SMS Server Tools 3.<br /> SMS Server Tools 3 is a SMS Gateway software which can send and receive short messages through GSM modems and mobile phones.<br /> <br /> ===Build SMS Server Tools3===<br /> * To build SMS Server Tools 3:<br /> &lt;pre class=&quot;host&quot;&gt;<br /> $ make menuconfig<br /> &lt;/pre&gt;<br /> &lt;pre class=&quot;config&quot;&gt;<br /> Package Selection for the target ---&gt;<br /> Hardware handling ---&gt;<br /> [*] SMS Server Tools3<br /> &lt;/pre&gt;<br /> &lt;pre class=&quot;host&quot;&gt;<br /> $ make<br /> &lt;/pre&gt;<br /> <br /> === Configuration ===<br /> The SMS server can be configured by using a configuration file (smsd.conf) located on the target in the /etc/smsd directory.<br /> The following parameters have to be verified:<br /> * device: uart port used to communicate with the modem. If GSMUX is used, then this parameter is of form /dev/pts/x where is x is the number of the virtual port<br /> * baudrate: baudrate of the uart port<br /> * rtscts: must be yes<br /> * incoming: yes if you want to receive SMS<br /> <br /> === Usage ===<br /> start the sms deamon:<br /> &lt;pre class=&quot;host&quot;&gt;<br /> smsd -c /etc/smsd/smsd.conf<br /> &lt;/pre&gt;<br /> Then put a SMS file in the /var/spool/outgoing directory. Once placed a SMS will be sent.<br /> Incoming SMS can be read in the /var/spool/incoming directory.<br /> Reports and logs are also generated.<br /> <br /> ==Links==<br /> * [http://support.sagemcom.com/site/modele_fax.php?page=produit&amp;numero_type=22&amp;produit=877 HiLo 3G documentation at Sagem]<br /> * [http://www.libelium.com/tienda/catalog/images/arduino/AT_Commands.pdf HiLo AT Commands]<br /> * [http://www.developershome.com/sms/ SMS tutorial]<br /> * http://wiki.openmoko.org/wiki/Neo_1973_and_Neo_FreeRunner_gsm_modem<br /> * [http://www.anotherurl.com/library/at_test.htm AT Test commands]<br /> * http://www.gsm-modem.de/gsm-faq.html<br /> * [http://www.technologuepro.com/gsm/commande_at.htm Les commandes AT]<br /> * [http://smstools3.kekekasvi.com SMS Server Tools 3]<br /> <br /> [[Category:Wireless]]</div> Salocin68 http://www.armadeus.org/wiki/index.php?title=GSM/GPRS&diff=11426 GSM/GPRS 2012-11-19T12:57:42Z <p>Salocin68: /* Usage */</p> <hr /> <div>This page will summarize informations to use the GSM/GPRS/3G module of the [[Wireless_extension_board|APF27Wireless board]] and the [[APF51Dev]] (optional).<br /> <br /> ==Introduction==<br /> GSM/GPRS are generally driven through the RS-232 bus. AT commands are used to dialog with the module.<br /> * GSM MODEM of the [[Wireless_extension_board|APF27Wireless extension board (APW)]] is connected to the UART2 (/dev/ttySMX1) of the [[APF27]].<br /> * GSM/3G MODEM of the [[APF51Dev]] is connected to the i.MX processor through an UART implemented in the FPGA. So the corresponding bitfile has to loaded before trying to access the MODEM.<br /> Both are using a Sagem's Hilo module. Hilo AT commands can be found [http://www.libelium.com/tienda/catalog/images/arduino/AT_Commands.pdf here]<br /> <br /> ==Linux configuration (APF27Dev only)==<br /> * Linux will have to be configured in order to tell that an APW is connected to your [[APF27Dev]]:<br /> &lt;pre class=&quot;host&quot;&gt;<br /> $ make linux26-menuconfig<br /> &lt;/pre&gt;<br /> &lt;pre class=&quot;config&quot;&gt;<br /> System Type ---&gt;<br /> Freescale MXC Implementations ---&gt;<br /> ...<br /> Extension board (Wireless (APW)) ---&gt;<br /> [*] GSM/GPRS Modem (NEW)<br /> [ ] Bluetooth &amp; WiFi module (NEW)<br /> [ ] CSI (Camera) pass-through (NEW)<br /> [ ] GPS module (NEW)<br /> &lt;/pre&gt;<br /> <br /> &lt;pre class=&quot;host&quot;&gt;<br /> $ make linux26<br /> &lt;/pre&gt;<br /> * reflash you Linux kernel<br /> <br /> ==Configure serial port==<br /> ====APF27====<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # export GSM_DEVICE=/dev/ttySMX1 (or /dev/ttymxc1 on recent kernels)<br /> # stty -F $GSM_DEVICE raw -echo -echoe -echok 115200<br /> &lt;/pre&gt;<br /> <br /> ====APF51Dev====<br /> <br /> {{Note|Don't forget to put &quot;Wireless&quot; J42 jumper (near microSD connector) '''AND''' power on FPGA Bank 3 (with corresponding J39 jumper).}}<br /> * On APF51Dev, GSM/3G module is accessed through serial ports synthetized in APF51's FPGA. So we have to load it first. (Needed dual UARTs FPGA firmware can be found under armadeus-4.0 distribution in ''firmware/pod_scripts'' directory, with the [[POD]] script needed to regenerate it, and is by default installed in rootfs).<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # load_fpga /lib/firmware/fpga/apf51_gsm_gps_firmware.bin<br /> &lt;/pre&gt;<br /> * Once firmware loaded, drivers related to FPGA can be used :<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # modprobe irq_ocore<br /> # modprobe 8250<br /> Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled<br /> # modprobe twin_uarts_irq_mng<br /> # modprobe twin_uarts_16750<br /> serial8250.0: ttyS0 at MMIO 0xb8000020 (irq = 320) is a TI16750<br /> serial8250.0: ttyS1 at MMIO 0xb8000040 (irq = 321) is a TI16750<br /> &lt;/pre&gt;<br /> * Bring MODEM out of reset state (POK_IN/PWON pin, connected to [[APF51_PMIC#GPIO|PMIC GPIO6]]):<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # modprobe wm831x-gpio<br /> # echo 245 &gt; /sys/class/gpio/export<br /> # echo out &gt; /sys/class/gpio/gpio245/direction<br /> # echo 1 &gt; /sys/class/gpio/gpio245/value<br /> &lt;/pre&gt;<br /> * Configure serial port:<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # ls /dev/ttyS*<br /> /dev/ttyS0 /dev/ttyS1 /dev/ttyS2 /dev/ttyS3<br /> &lt;/pre&gt;<br /> <br /> * If the /dev/ttyS[0-1] files don't exist, create it/them with ''mknod'' :<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # mknod /dev/ttyS0 c 4 64<br /> # mknod /dev/ttyS1 c 4 65<br /> &lt;/pre&gt;<br /> Then :<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # export GSM_DEVICE=/dev/ttyS0<br /> # stty -F $GSM_DEVICE -echo -echoe -echok 115200<br /> &lt;/pre&gt;<br /> <br /> ==Basic Usage==<br /> ===Sending AT commands &quot;manually&quot;===<br /> * Sending AT commands with ''minicom'' utility (one of the command coming with [[busybox]]):<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # minicom $GSM_DEVICE<br /> &lt;/pre&gt;<br /> ( To exit ''minocom'' you will have to type '''&lt;CTRL-x&gt;''' )<br /> * Check module presence:<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> ATI3<br /> SAGEM HiC,A.005.00<br /> <br /> OK<br /> &lt;/pre&gt;<br /> <br /> {{Note| If no echo are printed on serial console: you can't see what you're typing. In that case, to reactivate the echo, use:<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> ATE1<br /> &lt;/pre&gt;<br /> }}<br /> <br /> {{Note| By default, the module starts in auto baudrate. This mays result in loss of communication with baud rate higher than 19200 bauds. To avoid problems, the baud rate has to be fixed (here to 115200 bauds):<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> AT+IPR=115200<br /> &lt;/pre&gt;<br /> }}<br /> <br /> * Get constructor name:<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> AT+CGMI<br /> SAGEM<br /> <br /> OK<br /> &lt;/pre&gt;<br /> * Get model name:<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> AT+CGMM<br /> HILO GPRS<br /> <br /> OK<br /> &lt;/pre&gt;<br /> * Enter PIN code (here 0000). '''!! Use your own and beware that you will only get 3 tries !!:'''<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> AT+CPIN=&quot;0000&quot;<br /> <br /> OK<br /> &lt;/pre&gt;<br /> * Check PIN code status:<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> AT+CPIN?<br /> +CPIN: READY<br /> <br /> OK<br /> &lt;/pre&gt;<br /> {{Note|Don't launch further AT commands if PIN code wasn't entered successfully}}<br /> <br /> * Check module status (0 Ready, 1 Unavailable, 2 Status unknown, 3 Ringing, 4 Call in progress, 5 Asleep):<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> AT+CPAS<br /> +CPAS: 0<br /> <br /> OK<br /> &lt;/pre&gt;<br /> * Get Indicator control (&lt;battchg&gt;[0-4],&lt;signal&gt;[0-4],&lt;service&gt;0/1,&lt;message&gt;0/1,&lt;call&gt;0/1,&lt;smsfull&gt;0/1):<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> AT+CIND?<br /> +CIND: 0,4,1,0,0,0,1<br /> <br /> OK<br /> &lt;/pre&gt;<br /> * Get signal quality (should be better than 12/99):<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> AT+CSQ<br /> +CSQ: 24,99<br /> <br /> OK<br /> &lt;/pre&gt;<br /> * Voice call &quot;123456789&quot; (; is important here to signify a voice call, otherwise a data call is tried and may fail if you don't have the right subscribe)<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> ATD&quot;123456789&quot;;<br /> OK<br /> &lt;/pre&gt;<br /> * Terminate current call:<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> ATH<br /> OK<br /> &lt;/pre&gt;<br /> <br /> ===Sending AT commands in shell scripts===<br /> <br /> &lt;source lang=&quot;bash&quot;&gt;<br /> GSM_DEVICE=/dev/ttyXXX<br /> send_at_cmd()<br /> {<br /> echo -e -n &quot;$1\015&quot; &gt; $GSM_DEVICE<br /> sleep 1 # Adjustable ! (usleep)<br /> }<br /> <br /> send_at_cmd AT<br /> &lt;/source&gt;<br /> <br /> * See ''target/test/test_gsm.sh'' for more details<br /> <br /> ==Sending SMS==<br /> * Supposing you are already connected to the modem with cu<br /> * Check if you can send SMS with your SIM card (you should get +CMGF: (0,1))<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> AT+CMGF=?<br /> &lt;/pre&gt;<br /> * If OK, switch to SMS sending mode:<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> AT+CMGF=1<br /> &lt;/pre&gt;<br /> * Write a message for 0661234567 phone number:<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> AT+CMGW=&quot;0661326109&quot;<br /> <br /> &gt; Hey ! How are you doing ??<br /> &gt; &lt;-- Ctrl+z to end SMS here<br /> <br /> +CMGW: 8<br /> &lt;/pre&gt;<br /> * +CMGW give you the number of your SMS saved in SIM card or phone memory<br /> * Then, at anytime, you can send your SMS with (pass previous number as parameter):<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> AT+CMSS=8<br /> &lt;/pre&gt;<br /> <br /> ==Tools to look at==<br /> * http://www.developershome.com/sms/freeLibForSMS.asp<br /> * http://www.gnokii.org/<br /> * http://www.alamin.org/en/index.html<br /> * http://www.gammu.org/wiki/index.php?title=Gammu:Main_Page<br /> * http://gatling.ikk.sztaki.hu/~kissg/gsm/index.html<br /> <br /> ==Data tranfers (EDGE/3G)==<br /> <br /> ===PPP installation (done by default on APF51)===<br /> &lt;pre class=&quot;host&quot;&gt;<br /> $ make linux26-menuconfig<br /> &lt;/pre&gt;<br /> <br /> &lt;pre class=&quot;config&quot;&gt;<br /> Device Drivers ---&gt;<br /> [*] Network device support ---&gt;<br /> &lt;M&gt; PPP (point-to-point protocol) support<br /> [ ] PPP multilink support (EXPERIMENTAL)<br /> [ ] PPP filtering<br /> &lt;M&gt; PPP support for async serial ports<br /> &lt; &gt; PPP support for sync tty ports<br /> &lt; &gt; PPP Deflate compression<br /> &lt; &gt; PPP BSD-Compress compression<br /> &lt; &gt; PPP MPPE compression (encryption) (EXPERIMENTAL)<br /> &lt; &gt; PPP over Ethernet (EXPERIMENTAL)<br /> &lt;/pre&gt;<br /> <br /> &lt;pre class=&quot;host&quot;&gt;<br /> $ make menuconfig<br /> &lt;/pre&gt;<br /> <br /> &lt;pre class=&quot;config&quot;&gt;<br /> Package Selection for the target ---&gt;<br /> Networking applications ---&gt;<br /> [*] pppd<br /> [ ] filtering<br /> [ ] radius<br /> &lt;/pre&gt;<br /> <br /> &lt;pre class=&quot;host&quot;&gt;<br /> $ make linux26 &amp;&amp; make<br /> &lt;/pre&gt;<br /> <br /> * reflash kernel &amp; rootfs<br /> <br /> ===PPP configuration===<br /> {{Note|Following instructions are given for the French operator &quot;Bouygtel&quot; and may need to be ajusted accordingly, depending on your operator/country}}<br /> <br /> * Create a &quot;chat&quot; script that will be used to initiate MODEM dialup (here we use the &quot;cat &gt; xxxx &lt;&lt; EOF trick&quot; to automatically create the file, but you can also manually edit it with ''vi'' or ''nano''):<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # mkdir -p /etc/chatscripts/<br /> # cat &gt; /etc/chatscripts/bouygtel &lt;&lt;EOF<br /> ABORT BUSY ABORT 'NO CARRIER' ABORT VOICE ABORT 'NO DIALTONE' ABORT 'NO ANSWER' ABORT DELAYED ABORT ERROR<br /> '' AT<br /> OK AT+IPR=115200<br /> OK AT+CPIN=&quot;0000&quot;<br /> OK AT+CFUN=1<br /> OK AT+COPS?<br /> OK AT+CSQ<br /> OK 'AT+CGDCONT=1,&quot;IP&quot;,&quot;ebouygtel.com&quot;,&quot;&quot;,0,0'<br /> OK 'AT&amp;FE0Q0V1'<br /> OK 'ATD*99#'<br /> CONNECT &quot;&quot;<br /> EOF<br /> &lt;/pre&gt;<br /> * Don't forget to set the baudrate (default: 115200) to have a stable communication between the modem and the processor<br /> * Don't forget to update &quot;AT+CPIN=&quot; with your real PIN code and &quot;AT+CGDCONT&quot; and &quot;ATD*99#&quot; with your operator parameters.<br /> * If you want to test your chat script (verbose mode -v, on console -s, with 5 second timeout by default for commands -t 5), then launch:<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # /usr/sbin/chat -v -s -t 5 -f /etc/chatscripts/bouygtel &gt; $GSM_DEVICE &lt; $GSM_DEVICE<br /> &lt;/pre&gt;<br /> * If this test was OK, you may have to poweroff/poweron the MODEM to bring it to its initial state and go further.<br /> <br /> ====For '''APF51'''====<br /> * create the PPPd config files (''/etc/ppp/peers/bouygtel'' and ''/etc/ppp/options.ttyS0''):<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # mkdir -p /etc/ppp/peers/<br /> # cat &gt; /etc/ppp/peers/bouygtel &lt;&lt;EOF<br /> noauth<br /> connect &quot;/usr/sbin/chat -v -t 5 -f /etc/chatscripts/bouygtel&quot;<br /> debug<br /> ttyS0<br /> defaultroute<br /> noipdefault<br /> usepeerdns<br /> EOF<br /> <br /> # cat &gt; /etc/ppp/options.ttyS0 &lt;&lt;EOF<br /> 115200<br /> EOF<br /> &lt;/pre&gt;<br /> <br /> ====For '''APF27'''====<br /> {{Note| Check if /dev/ttySMX1 exists, if not create it with :<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> mknod /dev/ttySMX1 c 204 42<br /> &lt;/pre&gt;<br /> }}<br /> * create the PPPd config files (''/etc/ppp/peers/bouygtel'' and ''/etc/ppp/options.ttySMX1''):<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # mkdir -p /etc/ppp/peers/<br /> # cat &gt; /etc/ppp/peers/bouygtel &lt;&lt;EOF<br /> noauth<br /> connect &quot;/usr/sbin/chat -v -t 5 -f /etc/chatscripts/bouygtel&quot;<br /> debug<br /> ttySMX1<br /> defaultroute<br /> noipdefault<br /> usepeerdns<br /> EOF<br /> <br /> # cat &gt; /etc/ppp/options.ttySMX1 &lt;&lt;EOF<br /> 115200<br /> EOF<br /> &lt;/pre&gt;<br /> <br /> ===PPP Usage===<br /> * Load PPP module:<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # modprobe ppp (APF27)<br /> or<br /> # modprobe ppp_async (APF51)<br /> &lt;/pre&gt;<br /> * Setup serial port name depending on your platform (''/dev/ttyS0'' on APF51, ''/dev/ttySMX1'' on APF27)<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # export GSM_DEVICE=/dev/ttyS0<br /> or<br /> # export GSM_DEVICE=/dev/ttySMX1<br /> &lt;/pre&gt;<br /> <br /> * Launch the beast:<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # pppd $GSM_DEVICE 115200 call bouygtel<br /> &lt;/pre&gt;<br /> <br /> ===Test===<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # ping www.google.fr<br /> &lt;/pre&gt;<br /> <br /> === Troubleshots ===<br /> * Might be needed after a successful IP setup:<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # cp /etc/ppp/resolv.conf /etc/resolv.conf<br /> # route add default ppp0 (due to defaultroute option in ppp ?)<br /> &lt;/pre&gt;<br /> <br /> * To see what happened after having launched ''pppd'' or ''chat'':<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # tail -f /var/log/messages<br /> &lt;/pre&gt;<br /> <br /> ==GSM Muxing==<br /> ===Why ?===<br /> * By default AT commands usage is single threaded, ie only one program can open MODEM serial port and send AT commands at a given time. However it could be interesting to be able to send multiple AT commands from multiple programs at the same time, for example in order to: have a PPP link, send SMS and monitor network signal quality.<br /> * This can be done by a &quot;GSM mux&quot;, if your MODEM support the GSM 07.10 muxing norm (which is the case with our HiLo modules).<br /> ===Build gsmmux===<br /> * To build GSM mux (if not already done):<br /> &lt;pre class=&quot;host&quot;&gt;<br /> $ make menuconfig<br /> &lt;/pre&gt;<br /> &lt;pre class=&quot;config&quot;&gt;<br /> Package Selection for the target ---&gt;<br /> Hardware handling ---&gt;<br /> [*] gsmmux<br /> Version to use (sagem) ---&gt;<br /> &lt;/pre&gt;<br /> &lt;pre class=&quot;host&quot;&gt;<br /> $ make<br /> &lt;/pre&gt;<br /> <br /> ===Use it===<br /> * If you have access to Sagem's version (you will get as much as virtual serial port as times you pass ''/dev/ptmx'' to the daemon):<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # gsmMuxd -p $GSM_DEVICE -b 115200 -x /dev/ptmx /dev/ptmx /dev/ptmx<br /> &lt;/pre&gt;<br /> * Virtual serial ports will be created in ''/dev/pts/'':<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> /dev/pts/0 /dev/pts/1 /dev/pts/2<br /> &lt;/pre&gt;<br /> * to know how ''/dev/ptmx'' &amp; ''/dev/pts/x'' is working: [http://linux.die.net/man/4/ptmx]<br /> * If you have telnet or SSH sessions running ''/dev/pts/0'' may already be used ans so virtual serial ports will be allocated from ''/dev/pts/1'', etc...<br /> <br /> ===Going further===<br /> * In recent Linux kernels, there is also a driver to hanlde GSM muxing: n_gsm<br /> * People wanting to do a &quot;real&quot; phone can take a look at [http://ofono.org/documentation ofono]<br /> <br /> ==SMS using SMS server tools 3==<br /> simple AT commands can be used to sent SMS. If you need more flexibility or advanced management of your SMS, you can use SMS Server Tools 3.<br /> SMS Server Tools 3 is a SMS Gateway software which can send and receive short messages through GSM modems and mobile phones.<br /> <br /> ===Build SMS Server Tools3===<br /> * To build SMS Server Tools 3:<br /> &lt;pre class=&quot;host&quot;&gt;<br /> $ make menuconfig<br /> &lt;/pre&gt;<br /> &lt;pre class=&quot;config&quot;&gt;<br /> Package Selection for the target ---&gt;<br /> Hardware handling ---&gt;<br /> [*] SMS Server Tools3<br /> &lt;/pre&gt;<br /> &lt;pre class=&quot;host&quot;&gt;<br /> $ make<br /> &lt;/pre&gt;<br /> <br /> === Configuration ===<br /> The SMS server can be configured by using a configuration file (smsd.conf) located on the target in the /etc/smsd directory.<br /> The following parameters have to be verified:<br /> * device: uart port used to communicate with the modem. If GSMUX is used, then this parameter is of form /dev/pts/x where is x is the number of the virtual port<br /> * baudrate: baudrate of the uart port<br /> * rtscts: must be yes<br /> * incoming: yes if you want to receive SMS<br /> <br /> === Usage ===<br /> start the sms deamon:<br /> smsd -c /etc/smsd/smsd.conf<br /> <br /> ==Links==<br /> * [http://support.sagemcom.com/site/modele_fax.php?page=produit&amp;numero_type=22&amp;produit=877 HiLo 3G documentation at Sagem]<br /> * [http://www.libelium.com/tienda/catalog/images/arduino/AT_Commands.pdf HiLo AT Commands]<br /> * [http://www.developershome.com/sms/ SMS tutorial]<br /> * http://wiki.openmoko.org/wiki/Neo_1973_and_Neo_FreeRunner_gsm_modem<br /> * [http://www.anotherurl.com/library/at_test.htm AT Test commands]<br /> * http://www.gsm-modem.de/gsm-faq.html<br /> * [http://www.technologuepro.com/gsm/commande_at.htm Les commandes AT]<br /> * [http://smstools3.kekekasvi.com SMS Server Tools 3]<br /> <br /> [[Category:Wireless]]</div> Salocin68 http://www.armadeus.org/wiki/index.php?title=GSM/GPRS&diff=11425 GSM/GPRS 2012-11-19T12:52:48Z <p>Salocin68: /* Configuration */</p> <hr /> <div>This page will summarize informations to use the GSM/GPRS/3G module of the [[Wireless_extension_board|APF27Wireless board]] and the [[APF51Dev]] (optional).<br /> <br /> ==Introduction==<br /> GSM/GPRS are generally driven through the RS-232 bus. AT commands are used to dialog with the module.<br /> * GSM MODEM of the [[Wireless_extension_board|APF27Wireless extension board (APW)]] is connected to the UART2 (/dev/ttySMX1) of the [[APF27]].<br /> * GSM/3G MODEM of the [[APF51Dev]] is connected to the i.MX processor through an UART implemented in the FPGA. So the corresponding bitfile has to loaded before trying to access the MODEM.<br /> Both are using a Sagem's Hilo module. Hilo AT commands can be found [http://www.libelium.com/tienda/catalog/images/arduino/AT_Commands.pdf here]<br /> <br /> ==Linux configuration (APF27Dev only)==<br /> * Linux will have to be configured in order to tell that an APW is connected to your [[APF27Dev]]:<br /> &lt;pre class=&quot;host&quot;&gt;<br /> $ make linux26-menuconfig<br /> &lt;/pre&gt;<br /> &lt;pre class=&quot;config&quot;&gt;<br /> System Type ---&gt;<br /> Freescale MXC Implementations ---&gt;<br /> ...<br /> Extension board (Wireless (APW)) ---&gt;<br /> [*] GSM/GPRS Modem (NEW)<br /> [ ] Bluetooth &amp; WiFi module (NEW)<br /> [ ] CSI (Camera) pass-through (NEW)<br /> [ ] GPS module (NEW)<br /> &lt;/pre&gt;<br /> <br /> &lt;pre class=&quot;host&quot;&gt;<br /> $ make linux26<br /> &lt;/pre&gt;<br /> * reflash you Linux kernel<br /> <br /> ==Configure serial port==<br /> ====APF27====<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # export GSM_DEVICE=/dev/ttySMX1 (or /dev/ttymxc1 on recent kernels)<br /> # stty -F $GSM_DEVICE raw -echo -echoe -echok 115200<br /> &lt;/pre&gt;<br /> <br /> ====APF51Dev====<br /> <br /> {{Note|Don't forget to put &quot;Wireless&quot; J42 jumper (near microSD connector) '''AND''' power on FPGA Bank 3 (with corresponding J39 jumper).}}<br /> * On APF51Dev, GSM/3G module is accessed through serial ports synthetized in APF51's FPGA. So we have to load it first. (Needed dual UARTs FPGA firmware can be found under armadeus-4.0 distribution in ''firmware/pod_scripts'' directory, with the [[POD]] script needed to regenerate it, and is by default installed in rootfs).<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # load_fpga /lib/firmware/fpga/apf51_gsm_gps_firmware.bin<br /> &lt;/pre&gt;<br /> * Once firmware loaded, drivers related to FPGA can be used :<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # modprobe irq_ocore<br /> # modprobe 8250<br /> Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled<br /> # modprobe twin_uarts_irq_mng<br /> # modprobe twin_uarts_16750<br /> serial8250.0: ttyS0 at MMIO 0xb8000020 (irq = 320) is a TI16750<br /> serial8250.0: ttyS1 at MMIO 0xb8000040 (irq = 321) is a TI16750<br /> &lt;/pre&gt;<br /> * Bring MODEM out of reset state (POK_IN/PWON pin, connected to [[APF51_PMIC#GPIO|PMIC GPIO6]]):<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # modprobe wm831x-gpio<br /> # echo 245 &gt; /sys/class/gpio/export<br /> # echo out &gt; /sys/class/gpio/gpio245/direction<br /> # echo 1 &gt; /sys/class/gpio/gpio245/value<br /> &lt;/pre&gt;<br /> * Configure serial port:<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # ls /dev/ttyS*<br /> /dev/ttyS0 /dev/ttyS1 /dev/ttyS2 /dev/ttyS3<br /> &lt;/pre&gt;<br /> <br /> * If the /dev/ttyS[0-1] files don't exist, create it/them with ''mknod'' :<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # mknod /dev/ttyS0 c 4 64<br /> # mknod /dev/ttyS1 c 4 65<br /> &lt;/pre&gt;<br /> Then :<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # export GSM_DEVICE=/dev/ttyS0<br /> # stty -F $GSM_DEVICE -echo -echoe -echok 115200<br /> &lt;/pre&gt;<br /> <br /> ==Basic Usage==<br /> ===Sending AT commands &quot;manually&quot;===<br /> * Sending AT commands with ''minicom'' utility (one of the command coming with [[busybox]]):<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # minicom $GSM_DEVICE<br /> &lt;/pre&gt;<br /> ( To exit ''minocom'' you will have to type '''&lt;CTRL-x&gt;''' )<br /> * Check module presence:<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> ATI3<br /> SAGEM HiC,A.005.00<br /> <br /> OK<br /> &lt;/pre&gt;<br /> <br /> {{Note| If no echo are printed on serial console: you can't see what you're typing. In that case, to reactivate the echo, use:<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> ATE1<br /> &lt;/pre&gt;<br /> }}<br /> <br /> {{Note| By default, the module starts in auto baudrate. This mays result in loss of communication with baud rate higher than 19200 bauds. To avoid problems, the baud rate has to be fixed (here to 115200 bauds):<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> AT+IPR=115200<br /> &lt;/pre&gt;<br /> }}<br /> <br /> * Get constructor name:<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> AT+CGMI<br /> SAGEM<br /> <br /> OK<br /> &lt;/pre&gt;<br /> * Get model name:<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> AT+CGMM<br /> HILO GPRS<br /> <br /> OK<br /> &lt;/pre&gt;<br /> * Enter PIN code (here 0000). '''!! Use your own and beware that you will only get 3 tries !!:'''<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> AT+CPIN=&quot;0000&quot;<br /> <br /> OK<br /> &lt;/pre&gt;<br /> * Check PIN code status:<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> AT+CPIN?<br /> +CPIN: READY<br /> <br /> OK<br /> &lt;/pre&gt;<br /> {{Note|Don't launch further AT commands if PIN code wasn't entered successfully}}<br /> <br /> * Check module status (0 Ready, 1 Unavailable, 2 Status unknown, 3 Ringing, 4 Call in progress, 5 Asleep):<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> AT+CPAS<br /> +CPAS: 0<br /> <br /> OK<br /> &lt;/pre&gt;<br /> * Get Indicator control (&lt;battchg&gt;[0-4],&lt;signal&gt;[0-4],&lt;service&gt;0/1,&lt;message&gt;0/1,&lt;call&gt;0/1,&lt;smsfull&gt;0/1):<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> AT+CIND?<br /> +CIND: 0,4,1,0,0,0,1<br /> <br /> OK<br /> &lt;/pre&gt;<br /> * Get signal quality (should be better than 12/99):<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> AT+CSQ<br /> +CSQ: 24,99<br /> <br /> OK<br /> &lt;/pre&gt;<br /> * Voice call &quot;123456789&quot; (; is important here to signify a voice call, otherwise a data call is tried and may fail if you don't have the right subscribe)<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> ATD&quot;123456789&quot;;<br /> OK<br /> &lt;/pre&gt;<br /> * Terminate current call:<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> ATH<br /> OK<br /> &lt;/pre&gt;<br /> <br /> ===Sending AT commands in shell scripts===<br /> <br /> &lt;source lang=&quot;bash&quot;&gt;<br /> GSM_DEVICE=/dev/ttyXXX<br /> send_at_cmd()<br /> {<br /> echo -e -n &quot;$1\015&quot; &gt; $GSM_DEVICE<br /> sleep 1 # Adjustable ! (usleep)<br /> }<br /> <br /> send_at_cmd AT<br /> &lt;/source&gt;<br /> <br /> * See ''target/test/test_gsm.sh'' for more details<br /> <br /> ==Sending SMS==<br /> * Supposing you are already connected to the modem with cu<br /> * Check if you can send SMS with your SIM card (you should get +CMGF: (0,1))<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> AT+CMGF=?<br /> &lt;/pre&gt;<br /> * If OK, switch to SMS sending mode:<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> AT+CMGF=1<br /> &lt;/pre&gt;<br /> * Write a message for 0661234567 phone number:<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> AT+CMGW=&quot;0661326109&quot;<br /> <br /> &gt; Hey ! How are you doing ??<br /> &gt; &lt;-- Ctrl+z to end SMS here<br /> <br /> +CMGW: 8<br /> &lt;/pre&gt;<br /> * +CMGW give you the number of your SMS saved in SIM card or phone memory<br /> * Then, at anytime, you can send your SMS with (pass previous number as parameter):<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> AT+CMSS=8<br /> &lt;/pre&gt;<br /> <br /> ==Tools to look at==<br /> * http://www.developershome.com/sms/freeLibForSMS.asp<br /> * http://www.gnokii.org/<br /> * http://www.alamin.org/en/index.html<br /> * http://www.gammu.org/wiki/index.php?title=Gammu:Main_Page<br /> * http://gatling.ikk.sztaki.hu/~kissg/gsm/index.html<br /> <br /> ==Data tranfers (EDGE/3G)==<br /> <br /> ===PPP installation (done by default on APF51)===<br /> &lt;pre class=&quot;host&quot;&gt;<br /> $ make linux26-menuconfig<br /> &lt;/pre&gt;<br /> <br /> &lt;pre class=&quot;config&quot;&gt;<br /> Device Drivers ---&gt;<br /> [*] Network device support ---&gt;<br /> &lt;M&gt; PPP (point-to-point protocol) support<br /> [ ] PPP multilink support (EXPERIMENTAL)<br /> [ ] PPP filtering<br /> &lt;M&gt; PPP support for async serial ports<br /> &lt; &gt; PPP support for sync tty ports<br /> &lt; &gt; PPP Deflate compression<br /> &lt; &gt; PPP BSD-Compress compression<br /> &lt; &gt; PPP MPPE compression (encryption) (EXPERIMENTAL)<br /> &lt; &gt; PPP over Ethernet (EXPERIMENTAL)<br /> &lt;/pre&gt;<br /> <br /> &lt;pre class=&quot;host&quot;&gt;<br /> $ make menuconfig<br /> &lt;/pre&gt;<br /> <br /> &lt;pre class=&quot;config&quot;&gt;<br /> Package Selection for the target ---&gt;<br /> Networking applications ---&gt;<br /> [*] pppd<br /> [ ] filtering<br /> [ ] radius<br /> &lt;/pre&gt;<br /> <br /> &lt;pre class=&quot;host&quot;&gt;<br /> $ make linux26 &amp;&amp; make<br /> &lt;/pre&gt;<br /> <br /> * reflash kernel &amp; rootfs<br /> <br /> ===PPP configuration===<br /> {{Note|Following instructions are given for the French operator &quot;Bouygtel&quot; and may need to be ajusted accordingly, depending on your operator/country}}<br /> <br /> * Create a &quot;chat&quot; script that will be used to initiate MODEM dialup (here we use the &quot;cat &gt; xxxx &lt;&lt; EOF trick&quot; to automatically create the file, but you can also manually edit it with ''vi'' or ''nano''):<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # mkdir -p /etc/chatscripts/<br /> # cat &gt; /etc/chatscripts/bouygtel &lt;&lt;EOF<br /> ABORT BUSY ABORT 'NO CARRIER' ABORT VOICE ABORT 'NO DIALTONE' ABORT 'NO ANSWER' ABORT DELAYED ABORT ERROR<br /> '' AT<br /> OK AT+IPR=115200<br /> OK AT+CPIN=&quot;0000&quot;<br /> OK AT+CFUN=1<br /> OK AT+COPS?<br /> OK AT+CSQ<br /> OK 'AT+CGDCONT=1,&quot;IP&quot;,&quot;ebouygtel.com&quot;,&quot;&quot;,0,0'<br /> OK 'AT&amp;FE0Q0V1'<br /> OK 'ATD*99#'<br /> CONNECT &quot;&quot;<br /> EOF<br /> &lt;/pre&gt;<br /> * Don't forget to set the baudrate (default: 115200) to have a stable communication between the modem and the processor<br /> * Don't forget to update &quot;AT+CPIN=&quot; with your real PIN code and &quot;AT+CGDCONT&quot; and &quot;ATD*99#&quot; with your operator parameters.<br /> * If you want to test your chat script (verbose mode -v, on console -s, with 5 second timeout by default for commands -t 5), then launch:<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # /usr/sbin/chat -v -s -t 5 -f /etc/chatscripts/bouygtel &gt; $GSM_DEVICE &lt; $GSM_DEVICE<br /> &lt;/pre&gt;<br /> * If this test was OK, you may have to poweroff/poweron the MODEM to bring it to its initial state and go further.<br /> <br /> ====For '''APF51'''====<br /> * create the PPPd config files (''/etc/ppp/peers/bouygtel'' and ''/etc/ppp/options.ttyS0''):<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # mkdir -p /etc/ppp/peers/<br /> # cat &gt; /etc/ppp/peers/bouygtel &lt;&lt;EOF<br /> noauth<br /> connect &quot;/usr/sbin/chat -v -t 5 -f /etc/chatscripts/bouygtel&quot;<br /> debug<br /> ttyS0<br /> defaultroute<br /> noipdefault<br /> usepeerdns<br /> EOF<br /> <br /> # cat &gt; /etc/ppp/options.ttyS0 &lt;&lt;EOF<br /> 115200<br /> EOF<br /> &lt;/pre&gt;<br /> <br /> ====For '''APF27'''====<br /> {{Note| Check if /dev/ttySMX1 exists, if not create it with :<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> mknod /dev/ttySMX1 c 204 42<br /> &lt;/pre&gt;<br /> }}<br /> * create the PPPd config files (''/etc/ppp/peers/bouygtel'' and ''/etc/ppp/options.ttySMX1''):<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # mkdir -p /etc/ppp/peers/<br /> # cat &gt; /etc/ppp/peers/bouygtel &lt;&lt;EOF<br /> noauth<br /> connect &quot;/usr/sbin/chat -v -t 5 -f /etc/chatscripts/bouygtel&quot;<br /> debug<br /> ttySMX1<br /> defaultroute<br /> noipdefault<br /> usepeerdns<br /> EOF<br /> <br /> # cat &gt; /etc/ppp/options.ttySMX1 &lt;&lt;EOF<br /> 115200<br /> EOF<br /> &lt;/pre&gt;<br /> <br /> ===PPP Usage===<br /> * Load PPP module:<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # modprobe ppp (APF27)<br /> or<br /> # modprobe ppp_async (APF51)<br /> &lt;/pre&gt;<br /> * Setup serial port name depending on your platform (''/dev/ttyS0'' on APF51, ''/dev/ttySMX1'' on APF27)<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # export GSM_DEVICE=/dev/ttyS0<br /> or<br /> # export GSM_DEVICE=/dev/ttySMX1<br /> &lt;/pre&gt;<br /> <br /> * Launch the beast:<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # pppd $GSM_DEVICE 115200 call bouygtel<br /> &lt;/pre&gt;<br /> <br /> ===Test===<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # ping www.google.fr<br /> &lt;/pre&gt;<br /> <br /> === Troubleshots ===<br /> * Might be needed after a successful IP setup:<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # cp /etc/ppp/resolv.conf /etc/resolv.conf<br /> # route add default ppp0 (due to defaultroute option in ppp ?)<br /> &lt;/pre&gt;<br /> <br /> * To see what happened after having launched ''pppd'' or ''chat'':<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # tail -f /var/log/messages<br /> &lt;/pre&gt;<br /> <br /> ==GSM Muxing==<br /> ===Why ?===<br /> * By default AT commands usage is single threaded, ie only one program can open MODEM serial port and send AT commands at a given time. However it could be interesting to be able to send multiple AT commands from multiple programs at the same time, for example in order to: have a PPP link, send SMS and monitor network signal quality.<br /> * This can be done by a &quot;GSM mux&quot;, if your MODEM support the GSM 07.10 muxing norm (which is the case with our HiLo modules).<br /> ===Build gsmmux===<br /> * To build GSM mux (if not already done):<br /> &lt;pre class=&quot;host&quot;&gt;<br /> $ make menuconfig<br /> &lt;/pre&gt;<br /> &lt;pre class=&quot;config&quot;&gt;<br /> Package Selection for the target ---&gt;<br /> Hardware handling ---&gt;<br /> [*] gsmmux<br /> Version to use (sagem) ---&gt;<br /> &lt;/pre&gt;<br /> &lt;pre class=&quot;host&quot;&gt;<br /> $ make<br /> &lt;/pre&gt;<br /> <br /> ===Use it===<br /> * If you have access to Sagem's version (you will get as much as virtual serial port as times you pass ''/dev/ptmx'' to the daemon):<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # gsmMuxd -p $GSM_DEVICE -b 115200 -x /dev/ptmx /dev/ptmx /dev/ptmx<br /> &lt;/pre&gt;<br /> * Virtual serial ports will be created in ''/dev/pts/'':<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> /dev/pts/0 /dev/pts/1 /dev/pts/2<br /> &lt;/pre&gt;<br /> * to know how ''/dev/ptmx'' &amp; ''/dev/pts/x'' is working: [http://linux.die.net/man/4/ptmx]<br /> * If you have telnet or SSH sessions running ''/dev/pts/0'' may already be used ans so virtual serial ports will be allocated from ''/dev/pts/1'', etc...<br /> <br /> ===Going further===<br /> * In recent Linux kernels, there is also a driver to hanlde GSM muxing: n_gsm<br /> * People wanting to do a &quot;real&quot; phone can take a look at [http://ofono.org/documentation ofono]<br /> <br /> ==SMS using SMS server tools 3==<br /> simple AT commands can be used to sent SMS. If you need more flexibility or advanced management of your SMS, you can use SMS Server Tools 3.<br /> SMS Server Tools 3 is a SMS Gateway software which can send and receive short messages through GSM modems and mobile phones.<br /> <br /> ===Build SMS Server Tools3===<br /> * To build SMS Server Tools 3:<br /> &lt;pre class=&quot;host&quot;&gt;<br /> $ make menuconfig<br /> &lt;/pre&gt;<br /> &lt;pre class=&quot;config&quot;&gt;<br /> Package Selection for the target ---&gt;<br /> Hardware handling ---&gt;<br /> [*] SMS Server Tools3<br /> &lt;/pre&gt;<br /> &lt;pre class=&quot;host&quot;&gt;<br /> $ make<br /> &lt;/pre&gt;<br /> <br /> === Configuration ===<br /> The SMS server can be configured by using a configuration file (smsd.conf) located on the target in the /etc/smsd directory.<br /> The following parameters have to be verified:<br /> * device: uart port used to communicate with the modem. If GSMUX is used, then this parameter is of form /dev/pts/x where is x is the number of the virtual port<br /> * baudrate: baudrate of the uart port<br /> * rtscts: must be yes<br /> * incoming: yes if you want to receive SMS<br /> <br /> === Usage ===<br /> <br /> <br /> ==Links==<br /> * [http://support.sagemcom.com/site/modele_fax.php?page=produit&amp;numero_type=22&amp;produit=877 HiLo 3G documentation at Sagem]<br /> * [http://www.libelium.com/tienda/catalog/images/arduino/AT_Commands.pdf HiLo AT Commands]<br /> * [http://www.developershome.com/sms/ SMS tutorial]<br /> * http://wiki.openmoko.org/wiki/Neo_1973_and_Neo_FreeRunner_gsm_modem<br /> * [http://www.anotherurl.com/library/at_test.htm AT Test commands]<br /> * http://www.gsm-modem.de/gsm-faq.html<br /> * [http://www.technologuepro.com/gsm/commande_at.htm Les commandes AT]<br /> * [http://smstools3.kekekasvi.com SMS Server Tools 3]<br /> <br /> [[Category:Wireless]]</div> Salocin68 http://www.armadeus.org/wiki/index.php?title=GSM/GPRS&diff=11424 GSM/GPRS 2012-11-19T12:42:19Z <p>Salocin68: /* Build SMS Server Tools3 */</p> <hr /> <div>This page will summarize informations to use the GSM/GPRS/3G module of the [[Wireless_extension_board|APF27Wireless board]] and the [[APF51Dev]] (optional).<br /> <br /> ==Introduction==<br /> GSM/GPRS are generally driven through the RS-232 bus. AT commands are used to dialog with the module.<br /> * GSM MODEM of the [[Wireless_extension_board|APF27Wireless extension board (APW)]] is connected to the UART2 (/dev/ttySMX1) of the [[APF27]].<br /> * GSM/3G MODEM of the [[APF51Dev]] is connected to the i.MX processor through an UART implemented in the FPGA. So the corresponding bitfile has to loaded before trying to access the MODEM.<br /> Both are using a Sagem's Hilo module. Hilo AT commands can be found [http://www.libelium.com/tienda/catalog/images/arduino/AT_Commands.pdf here]<br /> <br /> ==Linux configuration (APF27Dev only)==<br /> * Linux will have to be configured in order to tell that an APW is connected to your [[APF27Dev]]:<br /> &lt;pre class=&quot;host&quot;&gt;<br /> $ make linux26-menuconfig<br /> &lt;/pre&gt;<br /> &lt;pre class=&quot;config&quot;&gt;<br /> System Type ---&gt;<br /> Freescale MXC Implementations ---&gt;<br /> ...<br /> Extension board (Wireless (APW)) ---&gt;<br /> [*] GSM/GPRS Modem (NEW)<br /> [ ] Bluetooth &amp; WiFi module (NEW)<br /> [ ] CSI (Camera) pass-through (NEW)<br /> [ ] GPS module (NEW)<br /> &lt;/pre&gt;<br /> <br /> &lt;pre class=&quot;host&quot;&gt;<br /> $ make linux26<br /> &lt;/pre&gt;<br /> * reflash you Linux kernel<br /> <br /> ==Configure serial port==<br /> ====APF27====<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # export GSM_DEVICE=/dev/ttySMX1 (or /dev/ttymxc1 on recent kernels)<br /> # stty -F $GSM_DEVICE raw -echo -echoe -echok 115200<br /> &lt;/pre&gt;<br /> <br /> ====APF51Dev====<br /> <br /> {{Note|Don't forget to put &quot;Wireless&quot; J42 jumper (near microSD connector) '''AND''' power on FPGA Bank 3 (with corresponding J39 jumper).}}<br /> * On APF51Dev, GSM/3G module is accessed through serial ports synthetized in APF51's FPGA. So we have to load it first. (Needed dual UARTs FPGA firmware can be found under armadeus-4.0 distribution in ''firmware/pod_scripts'' directory, with the [[POD]] script needed to regenerate it, and is by default installed in rootfs).<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # load_fpga /lib/firmware/fpga/apf51_gsm_gps_firmware.bin<br /> &lt;/pre&gt;<br /> * Once firmware loaded, drivers related to FPGA can be used :<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # modprobe irq_ocore<br /> # modprobe 8250<br /> Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled<br /> # modprobe twin_uarts_irq_mng<br /> # modprobe twin_uarts_16750<br /> serial8250.0: ttyS0 at MMIO 0xb8000020 (irq = 320) is a TI16750<br /> serial8250.0: ttyS1 at MMIO 0xb8000040 (irq = 321) is a TI16750<br /> &lt;/pre&gt;<br /> * Bring MODEM out of reset state (POK_IN/PWON pin, connected to [[APF51_PMIC#GPIO|PMIC GPIO6]]):<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # modprobe wm831x-gpio<br /> # echo 245 &gt; /sys/class/gpio/export<br /> # echo out &gt; /sys/class/gpio/gpio245/direction<br /> # echo 1 &gt; /sys/class/gpio/gpio245/value<br /> &lt;/pre&gt;<br /> * Configure serial port:<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # ls /dev/ttyS*<br /> /dev/ttyS0 /dev/ttyS1 /dev/ttyS2 /dev/ttyS3<br /> &lt;/pre&gt;<br /> <br /> * If the /dev/ttyS[0-1] files don't exist, create it/them with ''mknod'' :<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # mknod /dev/ttyS0 c 4 64<br /> # mknod /dev/ttyS1 c 4 65<br /> &lt;/pre&gt;<br /> Then :<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # export GSM_DEVICE=/dev/ttyS0<br /> # stty -F $GSM_DEVICE -echo -echoe -echok 115200<br /> &lt;/pre&gt;<br /> <br /> ==Basic Usage==<br /> ===Sending AT commands &quot;manually&quot;===<br /> * Sending AT commands with ''minicom'' utility (one of the command coming with [[busybox]]):<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # minicom $GSM_DEVICE<br /> &lt;/pre&gt;<br /> ( To exit ''minocom'' you will have to type '''&lt;CTRL-x&gt;''' )<br /> * Check module presence:<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> ATI3<br /> SAGEM HiC,A.005.00<br /> <br /> OK<br /> &lt;/pre&gt;<br /> <br /> {{Note| If no echo are printed on serial console: you can't see what you're typing. In that case, to reactivate the echo, use:<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> ATE1<br /> &lt;/pre&gt;<br /> }}<br /> <br /> {{Note| By default, the module starts in auto baudrate. This mays result in loss of communication with baud rate higher than 19200 bauds. To avoid problems, the baud rate has to be fixed (here to 115200 bauds):<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> AT+IPR=115200<br /> &lt;/pre&gt;<br /> }}<br /> <br /> * Get constructor name:<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> AT+CGMI<br /> SAGEM<br /> <br /> OK<br /> &lt;/pre&gt;<br /> * Get model name:<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> AT+CGMM<br /> HILO GPRS<br /> <br /> OK<br /> &lt;/pre&gt;<br /> * Enter PIN code (here 0000). '''!! Use your own and beware that you will only get 3 tries !!:'''<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> AT+CPIN=&quot;0000&quot;<br /> <br /> OK<br /> &lt;/pre&gt;<br /> * Check PIN code status:<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> AT+CPIN?<br /> +CPIN: READY<br /> <br /> OK<br /> &lt;/pre&gt;<br /> {{Note|Don't launch further AT commands if PIN code wasn't entered successfully}}<br /> <br /> * Check module status (0 Ready, 1 Unavailable, 2 Status unknown, 3 Ringing, 4 Call in progress, 5 Asleep):<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> AT+CPAS<br /> +CPAS: 0<br /> <br /> OK<br /> &lt;/pre&gt;<br /> * Get Indicator control (&lt;battchg&gt;[0-4],&lt;signal&gt;[0-4],&lt;service&gt;0/1,&lt;message&gt;0/1,&lt;call&gt;0/1,&lt;smsfull&gt;0/1):<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> AT+CIND?<br /> +CIND: 0,4,1,0,0,0,1<br /> <br /> OK<br /> &lt;/pre&gt;<br /> * Get signal quality (should be better than 12/99):<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> AT+CSQ<br /> +CSQ: 24,99<br /> <br /> OK<br /> &lt;/pre&gt;<br /> * Voice call &quot;123456789&quot; (; is important here to signify a voice call, otherwise a data call is tried and may fail if you don't have the right subscribe)<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> ATD&quot;123456789&quot;;<br /> OK<br /> &lt;/pre&gt;<br /> * Terminate current call:<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> ATH<br /> OK<br /> &lt;/pre&gt;<br /> <br /> ===Sending AT commands in shell scripts===<br /> <br /> &lt;source lang=&quot;bash&quot;&gt;<br /> GSM_DEVICE=/dev/ttyXXX<br /> send_at_cmd()<br /> {<br /> echo -e -n &quot;$1\015&quot; &gt; $GSM_DEVICE<br /> sleep 1 # Adjustable ! (usleep)<br /> }<br /> <br /> send_at_cmd AT<br /> &lt;/source&gt;<br /> <br /> * See ''target/test/test_gsm.sh'' for more details<br /> <br /> ==Sending SMS==<br /> * Supposing you are already connected to the modem with cu<br /> * Check if you can send SMS with your SIM card (you should get +CMGF: (0,1))<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> AT+CMGF=?<br /> &lt;/pre&gt;<br /> * If OK, switch to SMS sending mode:<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> AT+CMGF=1<br /> &lt;/pre&gt;<br /> * Write a message for 0661234567 phone number:<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> AT+CMGW=&quot;0661326109&quot;<br /> <br /> &gt; Hey ! How are you doing ??<br /> &gt; &lt;-- Ctrl+z to end SMS here<br /> <br /> +CMGW: 8<br /> &lt;/pre&gt;<br /> * +CMGW give you the number of your SMS saved in SIM card or phone memory<br /> * Then, at anytime, you can send your SMS with (pass previous number as parameter):<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> AT+CMSS=8<br /> &lt;/pre&gt;<br /> <br /> ==Tools to look at==<br /> * http://www.developershome.com/sms/freeLibForSMS.asp<br /> * http://www.gnokii.org/<br /> * http://www.alamin.org/en/index.html<br /> * http://www.gammu.org/wiki/index.php?title=Gammu:Main_Page<br /> * http://gatling.ikk.sztaki.hu/~kissg/gsm/index.html<br /> <br /> ==Data tranfers (EDGE/3G)==<br /> <br /> ===PPP installation (done by default on APF51)===<br /> &lt;pre class=&quot;host&quot;&gt;<br /> $ make linux26-menuconfig<br /> &lt;/pre&gt;<br /> <br /> &lt;pre class=&quot;config&quot;&gt;<br /> Device Drivers ---&gt;<br /> [*] Network device support ---&gt;<br /> &lt;M&gt; PPP (point-to-point protocol) support<br /> [ ] PPP multilink support (EXPERIMENTAL)<br /> [ ] PPP filtering<br /> &lt;M&gt; PPP support for async serial ports<br /> &lt; &gt; PPP support for sync tty ports<br /> &lt; &gt; PPP Deflate compression<br /> &lt; &gt; PPP BSD-Compress compression<br /> &lt; &gt; PPP MPPE compression (encryption) (EXPERIMENTAL)<br /> &lt; &gt; PPP over Ethernet (EXPERIMENTAL)<br /> &lt;/pre&gt;<br /> <br /> &lt;pre class=&quot;host&quot;&gt;<br /> $ make menuconfig<br /> &lt;/pre&gt;<br /> <br /> &lt;pre class=&quot;config&quot;&gt;<br /> Package Selection for the target ---&gt;<br /> Networking applications ---&gt;<br /> [*] pppd<br /> [ ] filtering<br /> [ ] radius<br /> &lt;/pre&gt;<br /> <br /> &lt;pre class=&quot;host&quot;&gt;<br /> $ make linux26 &amp;&amp; make<br /> &lt;/pre&gt;<br /> <br /> * reflash kernel &amp; rootfs<br /> <br /> ===PPP configuration===<br /> {{Note|Following instructions are given for the French operator &quot;Bouygtel&quot; and may need to be ajusted accordingly, depending on your operator/country}}<br /> <br /> * Create a &quot;chat&quot; script that will be used to initiate MODEM dialup (here we use the &quot;cat &gt; xxxx &lt;&lt; EOF trick&quot; to automatically create the file, but you can also manually edit it with ''vi'' or ''nano''):<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # mkdir -p /etc/chatscripts/<br /> # cat &gt; /etc/chatscripts/bouygtel &lt;&lt;EOF<br /> ABORT BUSY ABORT 'NO CARRIER' ABORT VOICE ABORT 'NO DIALTONE' ABORT 'NO ANSWER' ABORT DELAYED ABORT ERROR<br /> '' AT<br /> OK AT+IPR=115200<br /> OK AT+CPIN=&quot;0000&quot;<br /> OK AT+CFUN=1<br /> OK AT+COPS?<br /> OK AT+CSQ<br /> OK 'AT+CGDCONT=1,&quot;IP&quot;,&quot;ebouygtel.com&quot;,&quot;&quot;,0,0'<br /> OK 'AT&amp;FE0Q0V1'<br /> OK 'ATD*99#'<br /> CONNECT &quot;&quot;<br /> EOF<br /> &lt;/pre&gt;<br /> * Don't forget to set the baudrate (default: 115200) to have a stable communication between the modem and the processor<br /> * Don't forget to update &quot;AT+CPIN=&quot; with your real PIN code and &quot;AT+CGDCONT&quot; and &quot;ATD*99#&quot; with your operator parameters.<br /> * If you want to test your chat script (verbose mode -v, on console -s, with 5 second timeout by default for commands -t 5), then launch:<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # /usr/sbin/chat -v -s -t 5 -f /etc/chatscripts/bouygtel &gt; $GSM_DEVICE &lt; $GSM_DEVICE<br /> &lt;/pre&gt;<br /> * If this test was OK, you may have to poweroff/poweron the MODEM to bring it to its initial state and go further.<br /> <br /> ====For '''APF51'''====<br /> * create the PPPd config files (''/etc/ppp/peers/bouygtel'' and ''/etc/ppp/options.ttyS0''):<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # mkdir -p /etc/ppp/peers/<br /> # cat &gt; /etc/ppp/peers/bouygtel &lt;&lt;EOF<br /> noauth<br /> connect &quot;/usr/sbin/chat -v -t 5 -f /etc/chatscripts/bouygtel&quot;<br /> debug<br /> ttyS0<br /> defaultroute<br /> noipdefault<br /> usepeerdns<br /> EOF<br /> <br /> # cat &gt; /etc/ppp/options.ttyS0 &lt;&lt;EOF<br /> 115200<br /> EOF<br /> &lt;/pre&gt;<br /> <br /> ====For '''APF27'''====<br /> {{Note| Check if /dev/ttySMX1 exists, if not create it with :<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> mknod /dev/ttySMX1 c 204 42<br /> &lt;/pre&gt;<br /> }}<br /> * create the PPPd config files (''/etc/ppp/peers/bouygtel'' and ''/etc/ppp/options.ttySMX1''):<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # mkdir -p /etc/ppp/peers/<br /> # cat &gt; /etc/ppp/peers/bouygtel &lt;&lt;EOF<br /> noauth<br /> connect &quot;/usr/sbin/chat -v -t 5 -f /etc/chatscripts/bouygtel&quot;<br /> debug<br /> ttySMX1<br /> defaultroute<br /> noipdefault<br /> usepeerdns<br /> EOF<br /> <br /> # cat &gt; /etc/ppp/options.ttySMX1 &lt;&lt;EOF<br /> 115200<br /> EOF<br /> &lt;/pre&gt;<br /> <br /> ===PPP Usage===<br /> * Load PPP module:<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # modprobe ppp (APF27)<br /> or<br /> # modprobe ppp_async (APF51)<br /> &lt;/pre&gt;<br /> * Setup serial port name depending on your platform (''/dev/ttyS0'' on APF51, ''/dev/ttySMX1'' on APF27)<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # export GSM_DEVICE=/dev/ttyS0<br /> or<br /> # export GSM_DEVICE=/dev/ttySMX1<br /> &lt;/pre&gt;<br /> <br /> * Launch the beast:<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # pppd $GSM_DEVICE 115200 call bouygtel<br /> &lt;/pre&gt;<br /> <br /> ===Test===<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # ping www.google.fr<br /> &lt;/pre&gt;<br /> <br /> === Troubleshots ===<br /> * Might be needed after a successful IP setup:<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # cp /etc/ppp/resolv.conf /etc/resolv.conf<br /> # route add default ppp0 (due to defaultroute option in ppp ?)<br /> &lt;/pre&gt;<br /> <br /> * To see what happened after having launched ''pppd'' or ''chat'':<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # tail -f /var/log/messages<br /> &lt;/pre&gt;<br /> <br /> ==GSM Muxing==<br /> ===Why ?===<br /> * By default AT commands usage is single threaded, ie only one program can open MODEM serial port and send AT commands at a given time. However it could be interesting to be able to send multiple AT commands from multiple programs at the same time, for example in order to: have a PPP link, send SMS and monitor network signal quality.<br /> * This can be done by a &quot;GSM mux&quot;, if your MODEM support the GSM 07.10 muxing norm (which is the case with our HiLo modules).<br /> ===Build gsmmux===<br /> * To build GSM mux (if not already done):<br /> &lt;pre class=&quot;host&quot;&gt;<br /> $ make menuconfig<br /> &lt;/pre&gt;<br /> &lt;pre class=&quot;config&quot;&gt;<br /> Package Selection for the target ---&gt;<br /> Hardware handling ---&gt;<br /> [*] gsmmux<br /> Version to use (sagem) ---&gt;<br /> &lt;/pre&gt;<br /> &lt;pre class=&quot;host&quot;&gt;<br /> $ make<br /> &lt;/pre&gt;<br /> <br /> ===Use it===<br /> * If you have access to Sagem's version (you will get as much as virtual serial port as times you pass ''/dev/ptmx'' to the daemon):<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # gsmMuxd -p $GSM_DEVICE -b 115200 -x /dev/ptmx /dev/ptmx /dev/ptmx<br /> &lt;/pre&gt;<br /> * Virtual serial ports will be created in ''/dev/pts/'':<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> /dev/pts/0 /dev/pts/1 /dev/pts/2<br /> &lt;/pre&gt;<br /> * to know how ''/dev/ptmx'' &amp; ''/dev/pts/x'' is working: [http://linux.die.net/man/4/ptmx]<br /> * If you have telnet or SSH sessions running ''/dev/pts/0'' may already be used ans so virtual serial ports will be allocated from ''/dev/pts/1'', etc...<br /> <br /> ===Going further===<br /> * In recent Linux kernels, there is also a driver to hanlde GSM muxing: n_gsm<br /> * People wanting to do a &quot;real&quot; phone can take a look at [http://ofono.org/documentation ofono]<br /> <br /> ==SMS using SMS server tools 3==<br /> simple AT commands can be used to sent SMS. If you need more flexibility or advanced management of your SMS, you can use SMS Server Tools 3.<br /> SMS Server Tools 3 is a SMS Gateway software which can send and receive short messages through GSM modems and mobile phones.<br /> <br /> ===Build SMS Server Tools3===<br /> * To build SMS Server Tools 3:<br /> &lt;pre class=&quot;host&quot;&gt;<br /> $ make menuconfig<br /> &lt;/pre&gt;<br /> &lt;pre class=&quot;config&quot;&gt;<br /> Package Selection for the target ---&gt;<br /> Hardware handling ---&gt;<br /> [*] SMS Server Tools3<br /> &lt;/pre&gt;<br /> &lt;pre class=&quot;host&quot;&gt;<br /> $ make<br /> &lt;/pre&gt;<br /> <br /> === Configuration ===<br /> <br /> === Usage ===<br /> <br /> <br /> ==Links==<br /> * [http://support.sagemcom.com/site/modele_fax.php?page=produit&amp;numero_type=22&amp;produit=877 HiLo 3G documentation at Sagem]<br /> * [http://www.libelium.com/tienda/catalog/images/arduino/AT_Commands.pdf HiLo AT Commands]<br /> * [http://www.developershome.com/sms/ SMS tutorial]<br /> * http://wiki.openmoko.org/wiki/Neo_1973_and_Neo_FreeRunner_gsm_modem<br /> * [http://www.anotherurl.com/library/at_test.htm AT Test commands]<br /> * http://www.gsm-modem.de/gsm-faq.html<br /> * [http://www.technologuepro.com/gsm/commande_at.htm Les commandes AT]<br /> * [http://smstools3.kekekasvi.com SMS Server Tools 3]<br /> <br /> [[Category:Wireless]]</div> Salocin68 http://www.armadeus.org/wiki/index.php?title=GSM/GPRS&diff=11423 GSM/GPRS 2012-11-19T12:41:56Z <p>Salocin68: </p> <hr /> <div>This page will summarize informations to use the GSM/GPRS/3G module of the [[Wireless_extension_board|APF27Wireless board]] and the [[APF51Dev]] (optional).<br /> <br /> ==Introduction==<br /> GSM/GPRS are generally driven through the RS-232 bus. AT commands are used to dialog with the module.<br /> * GSM MODEM of the [[Wireless_extension_board|APF27Wireless extension board (APW)]] is connected to the UART2 (/dev/ttySMX1) of the [[APF27]].<br /> * GSM/3G MODEM of the [[APF51Dev]] is connected to the i.MX processor through an UART implemented in the FPGA. So the corresponding bitfile has to loaded before trying to access the MODEM.<br /> Both are using a Sagem's Hilo module. Hilo AT commands can be found [http://www.libelium.com/tienda/catalog/images/arduino/AT_Commands.pdf here]<br /> <br /> ==Linux configuration (APF27Dev only)==<br /> * Linux will have to be configured in order to tell that an APW is connected to your [[APF27Dev]]:<br /> &lt;pre class=&quot;host&quot;&gt;<br /> $ make linux26-menuconfig<br /> &lt;/pre&gt;<br /> &lt;pre class=&quot;config&quot;&gt;<br /> System Type ---&gt;<br /> Freescale MXC Implementations ---&gt;<br /> ...<br /> Extension board (Wireless (APW)) ---&gt;<br /> [*] GSM/GPRS Modem (NEW)<br /> [ ] Bluetooth &amp; WiFi module (NEW)<br /> [ ] CSI (Camera) pass-through (NEW)<br /> [ ] GPS module (NEW)<br /> &lt;/pre&gt;<br /> <br /> &lt;pre class=&quot;host&quot;&gt;<br /> $ make linux26<br /> &lt;/pre&gt;<br /> * reflash you Linux kernel<br /> <br /> ==Configure serial port==<br /> ====APF27====<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # export GSM_DEVICE=/dev/ttySMX1 (or /dev/ttymxc1 on recent kernels)<br /> # stty -F $GSM_DEVICE raw -echo -echoe -echok 115200<br /> &lt;/pre&gt;<br /> <br /> ====APF51Dev====<br /> <br /> {{Note|Don't forget to put &quot;Wireless&quot; J42 jumper (near microSD connector) '''AND''' power on FPGA Bank 3 (with corresponding J39 jumper).}}<br /> * On APF51Dev, GSM/3G module is accessed through serial ports synthetized in APF51's FPGA. So we have to load it first. (Needed dual UARTs FPGA firmware can be found under armadeus-4.0 distribution in ''firmware/pod_scripts'' directory, with the [[POD]] script needed to regenerate it, and is by default installed in rootfs).<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # load_fpga /lib/firmware/fpga/apf51_gsm_gps_firmware.bin<br /> &lt;/pre&gt;<br /> * Once firmware loaded, drivers related to FPGA can be used :<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # modprobe irq_ocore<br /> # modprobe 8250<br /> Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled<br /> # modprobe twin_uarts_irq_mng<br /> # modprobe twin_uarts_16750<br /> serial8250.0: ttyS0 at MMIO 0xb8000020 (irq = 320) is a TI16750<br /> serial8250.0: ttyS1 at MMIO 0xb8000040 (irq = 321) is a TI16750<br /> &lt;/pre&gt;<br /> * Bring MODEM out of reset state (POK_IN/PWON pin, connected to [[APF51_PMIC#GPIO|PMIC GPIO6]]):<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # modprobe wm831x-gpio<br /> # echo 245 &gt; /sys/class/gpio/export<br /> # echo out &gt; /sys/class/gpio/gpio245/direction<br /> # echo 1 &gt; /sys/class/gpio/gpio245/value<br /> &lt;/pre&gt;<br /> * Configure serial port:<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # ls /dev/ttyS*<br /> /dev/ttyS0 /dev/ttyS1 /dev/ttyS2 /dev/ttyS3<br /> &lt;/pre&gt;<br /> <br /> * If the /dev/ttyS[0-1] files don't exist, create it/them with ''mknod'' :<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # mknod /dev/ttyS0 c 4 64<br /> # mknod /dev/ttyS1 c 4 65<br /> &lt;/pre&gt;<br /> Then :<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # export GSM_DEVICE=/dev/ttyS0<br /> # stty -F $GSM_DEVICE -echo -echoe -echok 115200<br /> &lt;/pre&gt;<br /> <br /> ==Basic Usage==<br /> ===Sending AT commands &quot;manually&quot;===<br /> * Sending AT commands with ''minicom'' utility (one of the command coming with [[busybox]]):<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # minicom $GSM_DEVICE<br /> &lt;/pre&gt;<br /> ( To exit ''minocom'' you will have to type '''&lt;CTRL-x&gt;''' )<br /> * Check module presence:<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> ATI3<br /> SAGEM HiC,A.005.00<br /> <br /> OK<br /> &lt;/pre&gt;<br /> <br /> {{Note| If no echo are printed on serial console: you can't see what you're typing. In that case, to reactivate the echo, use:<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> ATE1<br /> &lt;/pre&gt;<br /> }}<br /> <br /> {{Note| By default, the module starts in auto baudrate. This mays result in loss of communication with baud rate higher than 19200 bauds. To avoid problems, the baud rate has to be fixed (here to 115200 bauds):<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> AT+IPR=115200<br /> &lt;/pre&gt;<br /> }}<br /> <br /> * Get constructor name:<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> AT+CGMI<br /> SAGEM<br /> <br /> OK<br /> &lt;/pre&gt;<br /> * Get model name:<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> AT+CGMM<br /> HILO GPRS<br /> <br /> OK<br /> &lt;/pre&gt;<br /> * Enter PIN code (here 0000). '''!! Use your own and beware that you will only get 3 tries !!:'''<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> AT+CPIN=&quot;0000&quot;<br /> <br /> OK<br /> &lt;/pre&gt;<br /> * Check PIN code status:<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> AT+CPIN?<br /> +CPIN: READY<br /> <br /> OK<br /> &lt;/pre&gt;<br /> {{Note|Don't launch further AT commands if PIN code wasn't entered successfully}}<br /> <br /> * Check module status (0 Ready, 1 Unavailable, 2 Status unknown, 3 Ringing, 4 Call in progress, 5 Asleep):<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> AT+CPAS<br /> +CPAS: 0<br /> <br /> OK<br /> &lt;/pre&gt;<br /> * Get Indicator control (&lt;battchg&gt;[0-4],&lt;signal&gt;[0-4],&lt;service&gt;0/1,&lt;message&gt;0/1,&lt;call&gt;0/1,&lt;smsfull&gt;0/1):<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> AT+CIND?<br /> +CIND: 0,4,1,0,0,0,1<br /> <br /> OK<br /> &lt;/pre&gt;<br /> * Get signal quality (should be better than 12/99):<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> AT+CSQ<br /> +CSQ: 24,99<br /> <br /> OK<br /> &lt;/pre&gt;<br /> * Voice call &quot;123456789&quot; (; is important here to signify a voice call, otherwise a data call is tried and may fail if you don't have the right subscribe)<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> ATD&quot;123456789&quot;;<br /> OK<br /> &lt;/pre&gt;<br /> * Terminate current call:<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> ATH<br /> OK<br /> &lt;/pre&gt;<br /> <br /> ===Sending AT commands in shell scripts===<br /> <br /> &lt;source lang=&quot;bash&quot;&gt;<br /> GSM_DEVICE=/dev/ttyXXX<br /> send_at_cmd()<br /> {<br /> echo -e -n &quot;$1\015&quot; &gt; $GSM_DEVICE<br /> sleep 1 # Adjustable ! (usleep)<br /> }<br /> <br /> send_at_cmd AT<br /> &lt;/source&gt;<br /> <br /> * See ''target/test/test_gsm.sh'' for more details<br /> <br /> ==Sending SMS==<br /> * Supposing you are already connected to the modem with cu<br /> * Check if you can send SMS with your SIM card (you should get +CMGF: (0,1))<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> AT+CMGF=?<br /> &lt;/pre&gt;<br /> * If OK, switch to SMS sending mode:<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> AT+CMGF=1<br /> &lt;/pre&gt;<br /> * Write a message for 0661234567 phone number:<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> AT+CMGW=&quot;0661326109&quot;<br /> <br /> &gt; Hey ! How are you doing ??<br /> &gt; &lt;-- Ctrl+z to end SMS here<br /> <br /> +CMGW: 8<br /> &lt;/pre&gt;<br /> * +CMGW give you the number of your SMS saved in SIM card or phone memory<br /> * Then, at anytime, you can send your SMS with (pass previous number as parameter):<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> AT+CMSS=8<br /> &lt;/pre&gt;<br /> <br /> ==Tools to look at==<br /> * http://www.developershome.com/sms/freeLibForSMS.asp<br /> * http://www.gnokii.org/<br /> * http://www.alamin.org/en/index.html<br /> * http://www.gammu.org/wiki/index.php?title=Gammu:Main_Page<br /> * http://gatling.ikk.sztaki.hu/~kissg/gsm/index.html<br /> <br /> ==Data tranfers (EDGE/3G)==<br /> <br /> ===PPP installation (done by default on APF51)===<br /> &lt;pre class=&quot;host&quot;&gt;<br /> $ make linux26-menuconfig<br /> &lt;/pre&gt;<br /> <br /> &lt;pre class=&quot;config&quot;&gt;<br /> Device Drivers ---&gt;<br /> [*] Network device support ---&gt;<br /> &lt;M&gt; PPP (point-to-point protocol) support<br /> [ ] PPP multilink support (EXPERIMENTAL)<br /> [ ] PPP filtering<br /> &lt;M&gt; PPP support for async serial ports<br /> &lt; &gt; PPP support for sync tty ports<br /> &lt; &gt; PPP Deflate compression<br /> &lt; &gt; PPP BSD-Compress compression<br /> &lt; &gt; PPP MPPE compression (encryption) (EXPERIMENTAL)<br /> &lt; &gt; PPP over Ethernet (EXPERIMENTAL)<br /> &lt;/pre&gt;<br /> <br /> &lt;pre class=&quot;host&quot;&gt;<br /> $ make menuconfig<br /> &lt;/pre&gt;<br /> <br /> &lt;pre class=&quot;config&quot;&gt;<br /> Package Selection for the target ---&gt;<br /> Networking applications ---&gt;<br /> [*] pppd<br /> [ ] filtering<br /> [ ] radius<br /> &lt;/pre&gt;<br /> <br /> &lt;pre class=&quot;host&quot;&gt;<br /> $ make linux26 &amp;&amp; make<br /> &lt;/pre&gt;<br /> <br /> * reflash kernel &amp; rootfs<br /> <br /> ===PPP configuration===<br /> {{Note|Following instructions are given for the French operator &quot;Bouygtel&quot; and may need to be ajusted accordingly, depending on your operator/country}}<br /> <br /> * Create a &quot;chat&quot; script that will be used to initiate MODEM dialup (here we use the &quot;cat &gt; xxxx &lt;&lt; EOF trick&quot; to automatically create the file, but you can also manually edit it with ''vi'' or ''nano''):<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # mkdir -p /etc/chatscripts/<br /> # cat &gt; /etc/chatscripts/bouygtel &lt;&lt;EOF<br /> ABORT BUSY ABORT 'NO CARRIER' ABORT VOICE ABORT 'NO DIALTONE' ABORT 'NO ANSWER' ABORT DELAYED ABORT ERROR<br /> '' AT<br /> OK AT+IPR=115200<br /> OK AT+CPIN=&quot;0000&quot;<br /> OK AT+CFUN=1<br /> OK AT+COPS?<br /> OK AT+CSQ<br /> OK 'AT+CGDCONT=1,&quot;IP&quot;,&quot;ebouygtel.com&quot;,&quot;&quot;,0,0'<br /> OK 'AT&amp;FE0Q0V1'<br /> OK 'ATD*99#'<br /> CONNECT &quot;&quot;<br /> EOF<br /> &lt;/pre&gt;<br /> * Don't forget to set the baudrate (default: 115200) to have a stable communication between the modem and the processor<br /> * Don't forget to update &quot;AT+CPIN=&quot; with your real PIN code and &quot;AT+CGDCONT&quot; and &quot;ATD*99#&quot; with your operator parameters.<br /> * If you want to test your chat script (verbose mode -v, on console -s, with 5 second timeout by default for commands -t 5), then launch:<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # /usr/sbin/chat -v -s -t 5 -f /etc/chatscripts/bouygtel &gt; $GSM_DEVICE &lt; $GSM_DEVICE<br /> &lt;/pre&gt;<br /> * If this test was OK, you may have to poweroff/poweron the MODEM to bring it to its initial state and go further.<br /> <br /> ====For '''APF51'''====<br /> * create the PPPd config files (''/etc/ppp/peers/bouygtel'' and ''/etc/ppp/options.ttyS0''):<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # mkdir -p /etc/ppp/peers/<br /> # cat &gt; /etc/ppp/peers/bouygtel &lt;&lt;EOF<br /> noauth<br /> connect &quot;/usr/sbin/chat -v -t 5 -f /etc/chatscripts/bouygtel&quot;<br /> debug<br /> ttyS0<br /> defaultroute<br /> noipdefault<br /> usepeerdns<br /> EOF<br /> <br /> # cat &gt; /etc/ppp/options.ttyS0 &lt;&lt;EOF<br /> 115200<br /> EOF<br /> &lt;/pre&gt;<br /> <br /> ====For '''APF27'''====<br /> {{Note| Check if /dev/ttySMX1 exists, if not create it with :<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> mknod /dev/ttySMX1 c 204 42<br /> &lt;/pre&gt;<br /> }}<br /> * create the PPPd config files (''/etc/ppp/peers/bouygtel'' and ''/etc/ppp/options.ttySMX1''):<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # mkdir -p /etc/ppp/peers/<br /> # cat &gt; /etc/ppp/peers/bouygtel &lt;&lt;EOF<br /> noauth<br /> connect &quot;/usr/sbin/chat -v -t 5 -f /etc/chatscripts/bouygtel&quot;<br /> debug<br /> ttySMX1<br /> defaultroute<br /> noipdefault<br /> usepeerdns<br /> EOF<br /> <br /> # cat &gt; /etc/ppp/options.ttySMX1 &lt;&lt;EOF<br /> 115200<br /> EOF<br /> &lt;/pre&gt;<br /> <br /> ===PPP Usage===<br /> * Load PPP module:<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # modprobe ppp (APF27)<br /> or<br /> # modprobe ppp_async (APF51)<br /> &lt;/pre&gt;<br /> * Setup serial port name depending on your platform (''/dev/ttyS0'' on APF51, ''/dev/ttySMX1'' on APF27)<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # export GSM_DEVICE=/dev/ttyS0<br /> or<br /> # export GSM_DEVICE=/dev/ttySMX1<br /> &lt;/pre&gt;<br /> <br /> * Launch the beast:<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # pppd $GSM_DEVICE 115200 call bouygtel<br /> &lt;/pre&gt;<br /> <br /> ===Test===<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # ping www.google.fr<br /> &lt;/pre&gt;<br /> <br /> === Troubleshots ===<br /> * Might be needed after a successful IP setup:<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # cp /etc/ppp/resolv.conf /etc/resolv.conf<br /> # route add default ppp0 (due to defaultroute option in ppp ?)<br /> &lt;/pre&gt;<br /> <br /> * To see what happened after having launched ''pppd'' or ''chat'':<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # tail -f /var/log/messages<br /> &lt;/pre&gt;<br /> <br /> ==GSM Muxing==<br /> ===Why ?===<br /> * By default AT commands usage is single threaded, ie only one program can open MODEM serial port and send AT commands at a given time. However it could be interesting to be able to send multiple AT commands from multiple programs at the same time, for example in order to: have a PPP link, send SMS and monitor network signal quality.<br /> * This can be done by a &quot;GSM mux&quot;, if your MODEM support the GSM 07.10 muxing norm (which is the case with our HiLo modules).<br /> ===Build gsmmux===<br /> * To build GSM mux (if not already done):<br /> &lt;pre class=&quot;host&quot;&gt;<br /> $ make menuconfig<br /> &lt;/pre&gt;<br /> &lt;pre class=&quot;config&quot;&gt;<br /> Package Selection for the target ---&gt;<br /> Hardware handling ---&gt;<br /> [*] gsmmux<br /> Version to use (sagem) ---&gt;<br /> &lt;/pre&gt;<br /> &lt;pre class=&quot;host&quot;&gt;<br /> $ make<br /> &lt;/pre&gt;<br /> <br /> ===Use it===<br /> * If you have access to Sagem's version (you will get as much as virtual serial port as times you pass ''/dev/ptmx'' to the daemon):<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # gsmMuxd -p $GSM_DEVICE -b 115200 -x /dev/ptmx /dev/ptmx /dev/ptmx<br /> &lt;/pre&gt;<br /> * Virtual serial ports will be created in ''/dev/pts/'':<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> /dev/pts/0 /dev/pts/1 /dev/pts/2<br /> &lt;/pre&gt;<br /> * to know how ''/dev/ptmx'' &amp; ''/dev/pts/x'' is working: [http://linux.die.net/man/4/ptmx]<br /> * If you have telnet or SSH sessions running ''/dev/pts/0'' may already be used ans so virtual serial ports will be allocated from ''/dev/pts/1'', etc...<br /> <br /> ===Going further===<br /> * In recent Linux kernels, there is also a driver to hanlde GSM muxing: n_gsm<br /> * People wanting to do a &quot;real&quot; phone can take a look at [http://ofono.org/documentation ofono]<br /> <br /> ==SMS using SMS server tools 3==<br /> simple AT commands can be used to sent SMS. If you need more flexibility or advanced management of your SMS, you can use SMS Server Tools 3.<br /> SMS Server Tools 3 is a SMS Gateway software which can send and receive short messages through GSM modems and mobile phones.<br /> <br /> ===Build SMS Server Tools3===<br /> * To build SMS Server Tools 3:<br /> &lt;pre class=&quot;host&quot;&gt;<br /> $ make menuconfig<br /> &lt;/pre&gt;<br /> &lt;pre class=&quot;config&quot;&gt;<br /> Package Selection for the target ---&gt;<br /> Hardware handling ---&gt;<br /> [*] gsmmux<br /> Version to use (sagem) ---&gt;<br /> &lt;/pre&gt;<br /> &lt;pre class=&quot;host&quot;&gt;<br /> $ make<br /> &lt;/pre&gt;<br /> <br /> === Configuration ===<br /> <br /> === Usage ===<br /> <br /> <br /> ==Links==<br /> * [http://support.sagemcom.com/site/modele_fax.php?page=produit&amp;numero_type=22&amp;produit=877 HiLo 3G documentation at Sagem]<br /> * [http://www.libelium.com/tienda/catalog/images/arduino/AT_Commands.pdf HiLo AT Commands]<br /> * [http://www.developershome.com/sms/ SMS tutorial]<br /> * http://wiki.openmoko.org/wiki/Neo_1973_and_Neo_FreeRunner_gsm_modem<br /> * [http://www.anotherurl.com/library/at_test.htm AT Test commands]<br /> * http://www.gsm-modem.de/gsm-faq.html<br /> * [http://www.technologuepro.com/gsm/commande_at.htm Les commandes AT]<br /> * [http://smstools3.kekekasvi.com SMS Server Tools 3]<br /> <br /> [[Category:Wireless]]</div> Salocin68 http://www.armadeus.org/wiki/index.php?title=Armadeus_5.0_Troubleshots&diff=11235 Armadeus 5.0 Troubleshots 2012-08-28T07:53:07Z <p>Salocin68: </p> <hr /> <div>* TFT flickering<br /> ** This effect is due to the dynamic frequency scaling Linux feature which is activated by default. Please try this command: echo userspace &gt; /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor. If the problem is solved, the feature can be deactivated in Linux menuconfig: http://www.armadeus.com/wiki/index.php?title=Talk:USB_to_WiFi_adapter (end of page)<br /> <br /> * USB random disconnection<br /> ** USB problems may appear due to the dynamic frequency scaling Linux feature which is activated by default. Please try this command: echo userspace &gt; /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor. If the problem is solved, the feature can be deactivated in Linux menuconfig: http://www.armadeus.com/wiki/index.php?title=Talk:USB_to_WiFi_adapter (end of page)</div> Salocin68 http://www.armadeus.org/wiki/index.php?title=SP_VISION&diff=11234 SP VISION 2012-08-20T16:38:33Z <p>Salocin68: /* On the APF*_Dev */</p> <hr /> <div>= Introduction =<br /> <br /> The SP_Vision board is an extension of [[APF27Dev]] and [[APF51Dev]] with a Spartan6 and two DDR. It is designed for real-time video processing.<br /> <br /> = Configure the sp_vision fpga =<br /> <br /> SP_Vision FPGA configuration is done through APF* FPGA, then to configure the SP_Vision FPGA you will need a configuration virtual component called ''sp_vision_configure'' under the APF*'s onboard FPGA.<br /> This virtual component is available in [http://periphondemand.git.sourceforge.net/git/gitweb.cgi?p=periphondemand/periphondemand;a=tree;f=src/library/components/sp_vision_configure;h=babdb0b05178267c1a8d077b0a1c5737820dea0e;hb=HEAD POD library], but if you don't want to make special design just for configuration, a standard design is provided in armadeus tree.<br /> <br /> == On the APF*_Dev ==<br /> <br /> * First select the driver for sp_vision_configuraton under linux-menuconfig :<br /> <br /> &lt;pre class=&quot;host&quot;&gt;<br /> [ ]$ make linux26-menuconfig<br /> &lt;/pre&gt;<br /> <br /> &lt;pre class=&quot;config&quot;&gt;<br /> Device Drivers ---&gt; <br /> Armadeus specific drivers ---&gt;<br /> FPGA Drivers ---&gt;<br /> [...]<br /> [*] virtual components<br /> [...]<br /> [*] Board designs<br /> [...]<br /> &lt;M&gt; board driver for sp_vision fpga loader<br /> &lt;/pre&gt;<br /> <br /> then<br /> &lt;pre class=&quot;host&quot;&gt;<br /> [ ]$ make linux26<br /> [...]<br /> [ ]$ make<br /> [...]<br /> &lt;/pre&gt;<br /> <br /> The configuration bitstream can be found under the directory ''firmware/pod_scripts/'' and it's named '''apf27_spvision_loader.bit''' for APF27 and '''apf51_spvision_loader.bin''' for APF51. To configure the second (sp_vision) FPGA, first FPGA on APF* must be configured with this bitstream.<br /> * Configure the first fpga (if you transfer files by nfs):<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # modprobe fpgaloader<br /> &lt;/pre&gt;<br /> On APF27:<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # load_fpga apf27_spvision_loader.bit<br /> &lt;/pre&gt;<br /> On APF51:<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # load_fpga apf51_spvision_loader.bin<br /> &lt;/pre&gt;<br /> <br /> * Once the first FPGA configured, just do :<br /> &lt;pre class=&quot;apf&quot;&gt;<br /> # modprobe sploader<br /> # modprobe sploader_prober<br /> # dd if=your_sp_vision_bitstream.bit of=/dev/sp_loader<br /> &lt;/pre&gt;<br /> <br /> = Communicate with sp_vision =<br /> {{Under_Construction}}</div> Salocin68