ArmadeusWiki - User contributions [en]

FAQ

2009-10-15T08:40:09Z

VeroniqueL:

==General Questions==

===What is the "Armadeus Project" intended for ?===
The goal of this project is to allow everyone to easily develop embedded Open Source systems.
When all the embedded systems in the world run open source software, life will be better ;-)

===What does "Armadeus" mean ?===
"Armadeus" is the contraction of "ARM" and "Amadeus". Indeed we chose ARM 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.

===How do I get help ?===
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 & Mulhouse who can provide help. For Swiss members, we can provide help in Basel, Lausanne & Zürich.

=== Why are there http://armadeus.org and http://armadeus.com ? Is there a company backing/hiding behind the association? ===

<http://armadeus.com> is the webpage dedicated to Armadeus Systems. 
The company develops and produces the main boards which are then available at a discount price to the association members (non commercial usage only!).

Historically the Armadeus Project (association) was founded before Armadeus Systems (company). 
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.

The association was started for our own pleasure and also to help universities and enthusiasts develop Linux embedded systems. 
It is a non profit association and works mostly on founders' free time.

The developments (hardware/firmware/software) performed within the association are under GPL/LGPL licence. 
The hardware funded by the association can not be used in a commercial product.

==Hardware Questions==
===Are the Armadeus boards RoHS compliant ?===
Yes

==Software Questions==
===Where are the sources ?===
We have a project on SourceForge: http://sourceforge.net/projects/armadeus/ with a [[GIT]] repository.

===What are the performances of your board ?===
[[Performances | Wiki page talking about board performances]]

===How do I get help/support===
[[Help:Contents]]

{{LanguageBar|FAQ|FAQ|FAQ}}

QemuMachineDevelopment

2009-09-01T15:23:29Z

VeroniqueL:

== Introduction ==
The aim of this project is to provide a fully functional and user-friendly way for developers and people interested in the Armadeus Project to test software as if it were running on a real board.

In a far-off time, the aim is to provide a small framework to build dynamic software tests and run them automatically (after a static analysis of code for instance in order to build a fully featured report).

'''See FireBoard project in the [[Contest | Contest 2008]] page.'''

== Armadeus boards devices ==

{| border="1" cellspacing="0" cellpadding="5"
|- style="background:#efefef;"
! Device || Implemented ?
|-
| Network interface || style="background:#ff0000;" |not implemented
|-
| SD/MMC card reader || style="background:#ff0000;" |not implemented
|-
| GPIO || style="background:#ff0000;" |not implemented
|-
| Led's || style="background:#ff0000;" |not implemented
|-
| CAN bus || style="background:#ff0000;" | not implemented
|-
| I2C bus || style="background:#ff0000;" | not implemented
|-
| ADC/DAC || style="background:#ff0000;" | not implemented
|-
| SPI || style="background:#ff0000;" | not implemented
|-
| SSI || style="background:#ff0000;" | not implemented
|-
| UART || style="background:#ff0000;" | not implemented
|-
| USB (slave/host) || style="background:#ff0000;" | not implemented
|-
| LCD || style="background:#ff0000;" | not implemented
|-
| FPGA || style="background:#ff0000;" | not implemented
|-
| SRAM || style="background:#ff0000;" | not implemented
|-
| CSI || style="background:#ff0000;" | not implemented
|-
| Touchscreen || style="background:#ff0000;" | not implemented
|}

== Qemu mechanisms : Qemu separated in three parts ==

Qemu is a wide software in which it could be difficult to land up. So a little explanation have to be done.

=== The code translation and the emulation system core ===

Qemu integrates a dynamic code translation "machine" which translates target instructions in host ones on the fly. They all are already implemented in Qemu, so we have not them to remake. But this part of code is heavy compact and need knowledge in both host and target instructions set in order to understand it.

All the code of the TCG (Tiny Code Generator) is placed in the tcg directory of the source tree and contains implementations independently of targets.

The entry point of Qemu is placed in the vl.c file. After reading it, you could see that the major part of Qemu is contained in it. Every function you should need to talk with the emulated environment is defined there. Consequently, the first point of our work is to understand the behavior of Qemu through these lines.

=== The Target specific code ===

It's not already clear to me where are placed the Qemu target specific code. So, at this time, it looks like there is mainly situated in the target-X directory (X have to be replaced by the target name, like "arm").

=== The hardware emulation layer ===

Despite of the hardware emulation layer is implemented both in the common emulation system and in an independent directory (named "hw"). It interacts with the emulation core through Qemu common functions each time. (see vl.c file)

==Links==
* [http://softgun.sourceforge.net/ Softgun ARM emulator (already has many i.MX21/i.MX1 devices)]
* [http://www.simtec.co.uk/products/SWLINUX/files/booting_article.html Low level ARM booting]
* [http://www.arm.linux.org.uk/ Linux on all arm machines]

[[Category:Emulation]]

LCD

2009-09-01T15:16:17Z

VeroniqueL:

On this page, you will find all the information needed to use Liquid Crystal Display (LCD) with your Armadeus board.

== Hardware interface ==
LCDs can be divided into 2 main categories:
* "intelligent" LCD with a built-in controller
* LCD without controller

===LCDs with integrated controller===
* your LCD has a built-in controller with a parallel interface -> usage of i.MXL LCD pins as GPIOs and emulation of a PC parallel port to reuse existing software
* your LCD has a built-in controller with a serial interface (not tested yet):
** RS232 -> connect this serial interface to the 2nd serial port of the i.MXL. Don't forget to check signal level compatibility before !
** SPI -> connect it to SPI port n°?

===LCDs without controller===
These LCDs can be used with i.MX internal LCD controller, ie direct connection between LCD & i.MX pins. Tested LCDs are:
* [[LQ043_Adapt | Sharp LQ043 (480x270) TFT ]] (Default 256k colors TFT for Armadeus Project)
* [[MTF-T035|Microtips MTF-035 (320x240) TFT]]
* [[MotLCD|Motorola A910 (240x320) TFT]]
* [[LQ057|Sharp LQ057 (320x240) TFT]]
5v logic one:
* Tianma STN Monochrome 320x240
* Ampire/xxx STN Monochrome 240x128

==Software API==
Generally on Linux you would need a kernel part (=driver) and a user space part (=library) to control and use your LCD in a reusable way.

{| border="1" cellpadding="5" cellspacing="0" summary="LCD software APIs"
|- style="background:#efefef;"
! ''' Built-in Controller ''' || ''' Interface ''' || '''Driver''' || '''Library''' || '''Working?'''
|----------------
| HD44780 || // 4 bits data || [[GPIO_Driver]] + PPDEV || LCD4Linux || style="background:#00ff55;" | Yes
|----------------
| KS0108 || // 8 bits data || [[GPIO_Driver]] + PPDEV || ?? || style="background:#ddff00;" | Not tested
|----------------
| || || || ||
|----------------
| None (use i.MXL one) || RGB datas + control signals || [[FrameBuffer]] || SDL / Qt / ... || style="background:#00ff55;" | Yes
|----------------
| || || || ||
|----------------
|}

===LCDs with controller===
====Parallel interface====
Driver:
Use Linux Armadeus [[GPIO_Driver|GPIO driver with it's PPDEV emulation]]
User space:
Use either [[LCD4linux]] or Lcdproc depending on your application

Text:
- HD 44780 (tested with GpioDriver driver (+ppdev emulation) and LCD4Linux

Graphic:
- KS0108 (Nico and Juju have one sample, not tested yet because LC4Linux don't support it)
- ?

=== User space tools / library found to control // LCD ===

[[LCD4linux]]
Cool but mainly to display system information, not very customizable for user GUI

Lcdproc ??
(Not tested)

Other idea ??

[[Image:FrenchFlag.png]] [[Fr:LCD | Cette page en français]]

[[Category:Displays]]
[[Category:LCD]]

TSC2102

2009-09-01T15:08:06Z

VeroniqueL:

Informations about the hardware interface between the i.MXL and the TSC2102.

==Introduction==

This chip is a "SMART" 4-Wire Touch Screen Controller with Stereo DAC and HP Amplifier. It is used on the DevFull board but any good electronics engineer should be able to add it to its DevLight.
It is although possible to solder this chip directly on your [[LQ043_Adapt|LQ043 adapter board]], if you have one.

==Hardware interface with the i.MXL==
===Touchscreen===
Configuration and data exchange is done through the SPI bus n°2 (SPI2). 
The SPI 2 port is shared with the LCD interface of the i.MXL (these signals are present on the DevLight V2 LCD connector).

===Audio===
Configuration is done through SPI2 bus and audio data exchange through SSIA

===Signals===

{| border="1" cellpadding="5" cellspacing="0" summary="Signal connections"
|- style="background:#efefef;"
! ''' i.MXL/DevLight ''' || ''' TSC2102 ''' || '''Functionality'''
|----------------
| SPI2_SCLK/'''REV''' || SCLK || SPI clock
|----------------
| SPI2_TXD/'''SPL_SPR''' || MOSI || SPI MasterOut SlaveIn
|----------------
| SPI2_RXD_1/'''PS''' || MISO || SPI MasterIn SlaveOut
|----------------
| PortB 17/'''SSI1_TXDAT''' || SSn || SPI Chip select
|----------------
| SPI2_SS/PortD 8/'''CLS''' || PINT/DAVn || Interrupt
|----------------
| Reset (on Reset switch) || RESETn || Global reset signal
|-
|}
'''Remark:'''
* i.MXL/DevLight SPI Chip Select signals are not used by Linux SPI infrastructure; it needs multiple chip select (one for each chip connected on the bus), and so GPIOs are used for that purpose.
* Chip interrupt is on Port D because Port B has already some and interrupt are shared on the same port.

==Drivers==
* [[TSC2102 Linux driver| TSC2102 Linux driver details ]]

==Self-made adapter board==
For those who would like to test this component on their [[APF9328DevLight|DevLight]] or their custom boards, take a look at this link: http://www.farnell.fr and type '[http://fr.farnell.com/jsp/Supports+CI,+cartes+prototypes+et+protection+antistatique/Cartes+prototypes/ROTH+ELEKTRONIK/RE933-07/displayProduct.jsp?sku=1426186&_requestid=343396 1426186]' as part to search. 
This is a small pcb converting a tssop32 to 2 rows of 2.54mm holes...

==SSI test tool==
Use a special release of tsc2102 driver and imxssi for audio development purpose. Available under buildroot menuconfig->hardware-handling

* Requirements:
TSC2102 mclk: 16MHZ 
FS rate: 32KHz 

* U-Boot: Enable register debug from U-Boot:
<pre class="apf">
BIOS> run unlock_regs
</pre>

* Linux: Load tsc driver
<pre class="apf">
modprobe tsc2102
</pre>

* imxssi: generate ssi signal
Special release of imxssi can generate an audio signal. 
just use imxssi with three parameters:
<pre class="apf">
# imxregs param1 param2 param3
param1 can be 0: triangular signal or 1: sinusoïdal signal.
param2: period of the signal in number of samples per channel.
param3: Signal level coefficient [0.0 .. 1.0].
</pre>

For example to produce a 300Hz 5v(pk-pk) sinusoid:
<pre class="apf">
# imxssi 1 50 0.15
</pre>

* next step: dma transfer

==Links==
* [http://focus.ti.com/docs/prod/folders/print/tsc2102.html TSC2102 Web page at Texas Instruments]
 

{{LanguageBar|TSC2102|TSC2102|TSC2102}}

[[Category:UserInput]]
[[Category:Audio]]

TSC2101

2009-09-01T15:03:14Z

VeroniqueL:

Information about the hardware interface between the i.MX27 and the TSC2101.

==Introduction==

This chip is a "SMART" 4-Wire Touch Screen Controller with Stereo DAC (Audio Out), Mono ADC (Audio In) and HP Amplifier. It is used on the [[APF27]] development board.

==Hardware interface with the i.MX27==
===Touchscreen===
Configuration and data exchange is done through the SPI bus n°2 (SPI2). 
The SPI 2 port is shared with the LCD interface of the i.MXL (these signals are present on the DevLight V2 LCD connector).

===Audio===
Configuration is done through SPI2 bus and audio data exchange through SSIA

===Signals===

{| border="1" cellpadding="5" cellspacing="0" summary="Signal connections"
|- style="background:#efefef;"
! ''' i.MX27 ''' || ''' TSC2101 ''' || '''Functionality'''
|----------------
| SPI2_SCLK/'''REV''' || SCLK || SPI clock
|----------------
| SPI2_TXD/'''SPL_SPR''' || MOSI || SPI MasterOut SlaveIn
|----------------
| SPI2_RXD_1/'''PS''' || MISO || SPI MasterIn SlaveOut
|----------------
| PortB 17/'''SSI1_TXDAT''' || SSn || SPI Chip select
|----------------
| SPI2_SS/PortD 8/'''CLS''' || PINT/DAVn || Interrupt
|----------------
| Reset (on Reset switch) || RESETn || Global reset signal
|-
|}
'''Remark:'''
* i.MX27 SPI Chip Select signals are not used by Linux SPI infrastructure; it needs multiple chip select (one for each chip connected on the bus), and so GPIOs are used for that purpose.
* Chip interrupt is on Port D because Port B has already some and interrupt are shared on the same port.

==Drivers==
* [[TSC2102 Linux driver| TSC2102 Linux driver details ]]

==SSI test tool==
Use a special release of tsc2102 driver and imxssi for audio development purpose. Available under buildroot menuconfig->hardware-handling

* Requirements:
TSC2102 mclk: 16MHZ 
FS rate: 32KHz 

* uboot: Enable register debug from u-boot:
BIOS> mw.l 0x00200008 0
BIOS> mw.l 0x00210008 0

* linux: Load spi/tsc drivers
modprobe spi_imx
modprobe tsc2102

* imxssi: generate ssi signal
Special release of imxssi can generate an audio signal. 
just use imxssi with three parameters:
# imxregs param1 param2 param3
param1 can be 0: triangular signal or 1: sinusoïdal signal. 
param2: period of the signal in number of samples per channel. 
param3: Signal level coefficient [0.0 .. 1.0]. 

For example to produce a 300Hz 5v(pk-pk) sinusoid:
# imxssi 1 50 0.15

* next step: dma transfer

==Links==
* [http://focus.ti.com/docs/prod/folders/print/tsc2101.html TSC2101 Web page at Texas Instruments]
 

{{LanguageBar|TSC2101|TSC2101|TSC2101}}

[[Category:UserInput]]
[[Category:Audio]]

TSC2102 Linux driver

2009-09-01T14:47:33Z

VeroniqueL:

This page details the installation and the usage of the Linux drivers for the [[TSC2102|TSC210x chips]] (touch & temp/voltage control). Sound (ALSA) specific part [[ALSA|can be found here.]]

==Driver Installation==
These drivers are now installed by default in standard Armadeus rootfs. [[Talk:TSC2102_Linux_driver|Here]] you will find instructions to know how we configured Linux to activate these drivers (may be useful if you want to deactivate them).

==Architecture==

{| border="1" cellpadding="5" cellspacing="0" summary="Driver Architecture"
|- style="background:#efffff;"
! '''Touchscreen (tsc2102_ts.ko)''' || '''HWmon''' || '''ALSA'''
|---------------- style="background:#efefef;"
| colspan="3" align="center" | TSC210x Main (SPI) driver (tsc2102.ko)
|---------------- style="background:#dfdfdf;"
| colspan="3" align="center" | Linux API
|-
|}

==Usage==
* load all the needed drivers:
<pre class="apf">
# modprobe tsc2102_ts
TI TSC2102 driver initializing
input: TSC2102 Touchscreen as /class/input/input0
TSC2102 touchscreen driver initialized
</pre>

===Touchscreen===
Before use, the touchscreen has to be (at least one time) calibrated:
<pre class="apf">
# ts_calibrate
</pre>
[[Image:Tslib_calibrate.png]]

Then it can be tested with:
<pre class="apf">
# ts_test
</pre>
[[Image:Tslib_test.png]]

If it does not work you can quickly check driver functionality; touch the screen and check that tsc2102 interrupts count is increasing:
<pre class="apf">
# cat /proc/interrupts
CPU0
26: 0 MPU IMX-uart
29: 17 MPU IMX-uart
30: 22 MPU IMX-uart
35: 12 MPU imx-mmc
39: 14 MPU I2C_IMX
40: 16 MPU imx-spi.2
41: 0 MPU imx-spi.1
59: 3682 MPU i.MX Timer Tick
60: 0 MPU DMA
61: 0 MPU DMA
110: 0 GPIO eth0
168: 0 GPIO tsc2102 <<<<--------
Err: 0
#
</pre>

Further information concerning the tslib can be found [[tslib | here]]

===Audio===

You can play sounds through [[ALSA| ALSA interface]].

===Miscellaneous===
* get temperature and voltage with [http://lxr.linux.no/source/Documentation/hwmon/sysfs-interface?v=2.6.18 hwmon] (Hardware Monitoring) interface. For example, get board temperature from TSC210x:
<pre class="apf">
# modprobe hwmon
# cat /sys/class/hwmon/hwmon0/device/temp1_input -- result in m°C
</pre>

==Links==
* [http://source.mvista.com/git/gitweb.cgi?p=linux-omap-2.6.git;a=log;t=7 Driver for OMAP] (search for TSC2102)
* [http://www.avr32linux.org/archives/kernel/2007-August/000209.html Driver for AVR32]
* http://osdir.com/ml/linux.ports.arm.omap/2006-08/msg00183.html
* [http://docs.blackfin.uclinux.org/doku.php?id=touchscreen Touchscreen usage on Blackfin]
* [http://doc.trolltech.com/qtopia4.1/syscust-3rdparty.html#compiling-tslib Compiling TSlib]
* http://www.opentom.org/Tslib
* http://www.openembedded.org/filebrowser/org.openembedded.packaged-staging/packages/tslib

[[Category:Linux drivers]]

Domos Project

2009-08-27T15:22:46Z

VeroniqueL:

The domos project aims are to provide a global, low cost, and open source solution for home automation. 
A first proposition can be found here: [] 
Three developers are currently registered.
* Guillaume Trannoy (endpoint prototype)
* Nicolas Aguirre (endpoint/APF protocol)
* Nicolas Colombain (support)

=Subprojects=
* Endpoint / controller communication (LS_Link)
* Controller/controller/server communication (HS_Link)

==1. LS_Link==
===Zigbee===
A zigbee solution is foreseen for the wireless communication. 
A presentation concerning Zigbee can be found here: [http://www.armadeus.com/assos_downloads/zigbee_slides.pdf]
and here: [http://www.diku.dk/~bonnet/ba.zigbee.pdf] 
This has to be evaluated. 
In order to be able to benefit from the complete Zigbee services, two Microchip ICs will be used (PIC18Fxx and the MRF) as the Zigbee stack is provided for free [http://www.armadeus.com/assos_downloads/domos_zigbee_stack.pdf]. 

MRF24J40 Transceiver [http://ww1.microchip.com/downloads/en/DeviceDoc/39776a.pdf] 

Next steps:
* 2 zigbee prototype boards with a PIC and the MRF. One will be used for the endpoint and the other will be connected to the APF through the RS232 (TTL) interface.
* Specification of the communication protocol between the APF and the endpoint (datagram based ?). Evolution of the actual solutions.
* Development of a small application on the APF side to communicate with the zigbee board by using the communication protocol previously defined.
* Test of the Zigbee stack provided by Microchip. A simple program has to be written. Default Microchip environment has to be used.

===RS485===
Wireless communication is the best way to connect Endpoints and controller. But sometimes wired connexion will be needed for direct or faster access. We could considerate RS485 connexion.
With RS485 nom we can connect up to 32 controllers on one bus.

Next steps:
* APF with RS485 transceiver with a PIC and the same transceiver.
* Needs to connect APF to a RS485 bus : Linux driver development? UART driver ?
* Schematics for connecting a pic to RS485 bus
* Specification of the communication protocol between APF and endpoint. Application protocol can be shared with Zigbee high level protocol or, must we develop a new protocol ?
* Development of a small application on the APF and on the PIC to test communication.

===Endpoint prototype board===
In order to develop and test endpoint protocols, a prototype board is under-development. This board must allow connections between boards, PC to proto-board and APF to proto-board.

Hardware
* Microcontroller PIC 18FXXX
* Transceiver IEEE 802.15.4 (to implement the zigbee stack)
* Transceiver RS232 (connection to APF or PC)
* Transceiver RS485
* Transceiver CAN
* USB connectors (and adaptor USB-RS232 by a FTDI chip)
* Buttons and LCD
=> Soon a description of the hardware would be available.

Software
* Stack Zibgbee
* RS485 protocol library to develop
* Empty main program
* HID library (Human Interface Device)

==2. HS_Link==

This high level of the home automation allows transfer of large data packets like audio/video streams. It can be centralized by a main supervisor to configure more easily the whole network or access to other ways of communication like Internet or phone.

===Wired===

We need a good and fast connection between controller/supervisor. Ethernet connection has been chosen because it's compatible with routers and PC which will be used for interaction and access to Internet.

===Wireless===

WIFI is a reliable wireless way of communication to high data rates. Multimedia controller will be able to proposed audio/video streams and phone communications thanks the WIFI.

==End Point List==
* Temperature sensor
* Humidity sensor
* Rain sensor (difference with the previous one is maybe thin)
* Pressure sensor
* Movement detector
* Light sensor
* Noise sensor (child crying ?)
* State actuator
* On/Off button
* graduator
* "Fil Pilote" actuator (electric heating control)
* Remote control

==Useful Links==
* http://www.homeautomationindex.com/
* http://misterhouse.sourceforge.net/
* http://heyu.tanj.com/
* http://mywebpages.comcast.net/ncherry/
* http://linuxha.sourceforge.net/

Armadeus 3

2009-08-27T15:11:12Z

VeroniqueL:

This page will help you use the Armadeus 3.0 software release. It also provides you with information about changes compared to the previous 2.x versions of Armadeus.

==Introduction==

Armadeus 3 adds many new features, including the following:

*Some architectural changes to support different hardware targets: [[APF9328]] and [[APF27]]
*New versions of U-Boot (1.3.4), Linux kernel (2.6.27), GCC (4.2.1), Busybox (1.12.1) and also a recent version of Buildroot
*New naming convention of files
*New Flash partition mapping on the target
*TBC

==Important Information regarding documentation==

{{Note|With the introduction of the Armadeus 3 SDK, the Wiki documentation has moved to support the new software. Nevertheless you can download the following HTML dump to have the Armadeus 2.x compatible documentation: [http://www.armadeus.com/assos_downloads/wiki/wiki_assoc_html_dump_03_12_2008.tar.gz Armadeus 2.x wiki]. Wiki will also moved in the next weeks so to have an always Armadeus 3.0 compatible HTML dump [http://www.armadeus.com/assos_downloads/wiki/wiki_assoc_html_dump_02_03_2009.tar.gz it's here]
}}

To summarize the documentation changes, here are the rules to adapt the documentation according to your target and version of Armadeus.
* First Armadeus configuration once you have downloaded the Armadeus package found somewhere in First Setup pages:
: Armadeus 3 first command to use according to your <board> (apf9328 or apf27): make <board>_defconfig
: Armadeus 2 first command for apf9328: make

* Binary files location according to your <board> (apf9328 or apf27):
: Armadeus 3 is buildroot/binaries/<board>/
: Armadeus 2 was buildroot/armadeus/

* Armadeus 3 binary files naming convention according to your <board> (apf9328 or apf27):
: <board>-u-boot.brec
: <board>-u-boot.bin
: <board>-linux.bin
: <board>-rootfs.arm.jffs2
: <board>-rootfs.arm.tar

* Armadeus 2 binary files naming convention for apf9328 only:
: u-boot.brec
: u-boot.bin
: linux-kernel-2.6.xx.x-arm.bin
: rootfs.arm.jffs2
: rootfs.arm.tar

* Non configurable users-space tools including compiler for your board (apf9328 or apf27):
: Armadeus 3 tools for the apf9328 are located at buildroot/build_armv4t/
: Armadeus 3 tools for the apf27 are located at buildroot/build_armv5te/
: Armadeus 2 tools are located at buildroot/build_arm/

* Configurable user-space tools (Linux, rootfs, U-Boot, Busybox...) for your board (apf9328 or apf27):
: Armadeus 3 tools for the apf9328 are located at buildroot/project_build_armv4t/apf9328/
: Armadeus 3 tools for the apf27 are located at buildroot/project_build_armv5te/apf27/
: Armadeus 2 tools are located at buildroot/project_build_arm/armadeus/

* cross compilation toolchain for your board (apf9328 or apf27):
: Armadeus 3 source toolchain for the apf9328 is located at buildroot/toolchain_build_armv4t/
: Armadeus 3 source toolchain for the apf27 is located at buildroot/toolchain_build_armv5te/
: Armadeus 2 toolchain is located at buildroot/toolchain_build_arm/

Keeping these rules in mind, you are ready to use any wiki page as a guideline whatever you are working with: Armadeus 2.x or 3.

==How-to obtain the Armadeus 3==

The third generation of Armadeus is either available on the GIT repository: git://armadeus.git.sourceforge.net/gitroot/armadeus or by download: https://sourceforge.net/project/showfiles.php?group_id=122057

You can checkout the new version of armadeus or update your working version of armadeus. '''We strongly suggest you to checkout the new version of Armadeus because the new naming convention of files will produce a second directory structure of toolchain, projects, build and image files that could be a source of confusion.'''

* Checkout the new version:

<pre class="host">
git clone git://armadeus.git.sourceforge.net/gitroot/armadeus/armadeus armadeus
</pre>

this commmand will download the latest version of Armadeus.

'''Remarks''': '''Do not use spaces''' in the directory name !

* Update your working version of armadeus

'''WARNING: Do not use a simple "git checkout" because some legacy buildroot patches will break your compilation!'''

<pre class="host">
cd armadeus
rm -rf buildroot/package
rm -rf buildroot/target
rm -rf buildroot/toolchain
git checkout -f
make apf9328_defconfig or make apf27_defconfig
</pre>

'''WARNING: the latest command (make <board>_defconfig ) is very important to start with an up to date configuration!'''

At any time you can cleanup the old directories built with armadeus 2:

<pre class="host">
rm -rf buildroot/binaries/armadeus
rm -rf buildroot/build_arm
rm -rf buildroot/project_build_arm
rm -rf buildroot/toolchain_build_arm
</pre>

* How-to obtain the legacy Armadeus 2 (If you're not ready to upgrade your target):

<pre class="host">
svn co https://armadeus.svn.sourceforge.net/svnroot/armadeus/trunk@914 armadeus2
</pre>

==How-to configure and build Armadeus 3==

* After changing the directory to ''armadeus'', you have to configure Armadeus software for the APF target.

<pre class="host">
cd armadeus/
make '''apf9328_defconfig''' or make '''apf27_defconfig'''
</pre>

The '<board>_defconfig' configuration option is the first difference with the previous releases of Armadeus.
This configuration has to be done only once after a checkout or after an update from an older version Armadeus. This command configures Armadeus for the apf board then launches the regular Buildroot configuration menu:

[[Image:Menuconfig3.png]] 

* Configure Armadeus

In Target options ---> Armadeus Device Support menu, you can check and change the quantity of RAM available on your Armadeus board. (Default value 16MB is just fine with all APF9328 boards and 64MB for the smallest apf27).

In Target filesystem options --> for each type of filesystems to build you have the option to copy the binary file to secondary location like your tftp server folder (for exemple /tftpboot).

In Target filesystem options --> You will find U-Boot options at the end of this menu including the option to copy U-Boot to a secondary location like /tftpboot

In Kernel --> Destination for linux kernel binaries --> You will find options to copy linux to a secondary location like /tftpboot

* Exit the configuration tool and save your configuration

* Launch the build process and enjoy a cup of coffee for the next hour

<pre class="host">
make
</pre>

The toolchain is built automatically. During this procedure, several files are downloaded from Internet. Please wait for a while.... it takes at least one hour to compile everything! 

* Enjoy the result

The generated binary files can be found in the new subdirectory ''buildroot/binaries/<board>/'':

: '''apf9328-u-boot.brec''' (apf9328 BRecord image that can be used with the bootstrap, if U-Boot is not installed or not working, see [[BootLoader]] page)
: '''<board>-u-boot.bin''' (U-Boot image file to be used with U-Boot itself, see [[BootLoader#Update_U-Boot | updating U-Boot]])
: '''<board>-linux.bin''' (Linux image to use with U-Boot, see [[Target_Software_Installation#Linux_kernel_installation | InstallLinux]])
: '''<board>-rootfs.arm.jffs2''' (FileSystem/RootFS image to use with U-Boot, see [[Target_Software_Installation#Linux_rootfs_installation | RootFS flashing]])
: '''<board>-rootfs.arm.tar''' (for an NFS/MMC RootFS, see [[Network_Configuration#Boot_from_NFS|Booting from NFS]] & [[MultiMediaCard#Booting_from_MMC.2FSD | Booting from a MMC/SD]])

 Please note the new naming convention of binary files and directories

The toolchain and project files share a new nameing convention too:
: '''buildroot/build_armv<x>t''' (contains all non configurable user-space tools)
: '''buildroot/project_build_armv<x>t/<board>''' (contains all configurable user-space tools: target filesystem, linux, busybox and u-boot...)
: '''buildroot/toolchain_build_armv<x>t''' (cross compilation toolchain)

More information is available in the [http://buildroot.uclibc.org/buildroot.html buildroot documentation]

* Prepare binary images for download

The simplest method to prepare binary files for a download to target is to copy them in the tftpboot public directory (for example /tftpboot). You can do it manually:

<pre class="host">
cp -f buildroot/binaries/<board>/* /tftpboot
</pre>

Or you can configure buildroot to copy the image files automatically as described hereabove in '''Configure Armadeus'''. 
From here we will suppose all the image files are available at the root of your tftp server

==How-to upgrade the apf9328 target==

To prepare the upgrade of the target you have to copy binary files from ''buildroot/binaries/apf9328/'' to your ''/tftpboot'' folder or make this process automatic using the command: '''make menuconfig'''. The communication with target is fully compatible with previous versions of Armadeus, as explained in [[Communicate| communicate with the target]]

===update U-Boot (on the target)===

Using the command '''printenv''' check the target IP variables:
BIOS> printenv
bootcmd=run jffsboot
bootdelay=20
...
gatewayip=192.168.0.1
netmask=255.255.255.0
ipaddr=192.168.0.10
serverip=192.168.0.2

'''ipaddr''' is the target IP address and '''serverip''' is the one of the Host PC running the tftp server. The page [[Target_Software_Installation]] will help you to set these variables.

If everything is fine you should be ready to download the new release of u-boot:

* '''Load the new U-Boot code in RAM'''

You can use the following commands to download U-boot: 
With Ethernet and a TFTP server:

BIOS> tftpboot 08000000 apf9328-u-boot.bin

dm9000 i/o: 0x15c00000, id: 0x90000a46
DM9000: running in 16 bit mode
MAC: 00:1e:ac:00:00:02
operating at 100M full duplex mode
TFTP from server 192.168.0.2; our IP address is 192.168.0.10
Filename 'apf9328-u-boot.bin'.
Load address: 0x8000000
Loading: ##################################
done
Bytes transferred = 173036 (2a3ec hex)

Or with Ethernet and a NFS server:
BIOS> nfs 08000000 ${serverip}:/nfs_path_to_buildroot/binaries/apf9328/apf9328-u-boot.bin
Or with the kermit and a serial line
BIOS> loadb 08000000
<CTRL><ALT GR>\
c
send path_to_buildroot/binaries/apf9328/apf9328-u_boot.bin
c

* '''Test the downloaded version of u-boot'''

BIOS> go 08000000

## Starting application at 0x08000000 ...

U-Boot 1.3.4 (Dec 2 2008 - 18:44:41) apf9328 patch 3.3

I2C: ready
DRAM: 16 MB
Flash: 8 MB
In: serial
Out: serial
Err: serial

Hit any key to stop autoboot: 0
BIOS>

* '''Transfer code from RAM to Flash memory'''

There is a simple U-Boot command/script to do that:
BIOS> run flash_uboot

.. done
Un-Protected 2 sectors

.. done
Erased 2 sectors
Copy to Flash... done
.. done
Protected 2 sectors
Flashing uboot succeed
BIOS>

Advanced informations can be found at the [[BootLoader]] wiki page.

* '''Reset the environment variables and reset the board'''

Note: This is important to support the new flash memory mapping. '''!! You will loose all the variables you had defined before !!'''

BIOS> run flash_reset_env

. done
Un-Protected 1 sectors

. done
Erased 1 sectors
Erasing of flash environment variables done!
BIOS>

And do not forget to reset the board by hardware or software.

BIOS> reset

U-Boot 1.3.4 (Dec 2 2008 - 18:44:41) apf9328 patch 3.3

I2C: ready
DRAM: 16 MB
Flash: 8 MB
...

===update linux and rootfs (on the target)===

* Check and set the IP variables:

BIOS> printenv
bootcmd=run jffsboot
bootdelay=20
...
gatewayip=192.168.0.1
netmask=255.255.255.0
ipaddr=192.168.0.10
serverip=192.168.0.2

'''ipaddr''' is the target IP address and '''serverip''' is the one of the Host PC running the tftp server. The page [[Target_Software_Installation]] will help you to set these variables.

You can use the '''dhcp''' command to automatically configure these variables from your DHCP server. You probably will have to adjust the '''serverip''' variable manually.

BIOS> dhcp
dm9000 i/o: 0x15c00000, id: 0x90000a46
MAC: 00:0e:32:00:00:02
operating at 100M full duplex mode
BOOTP broadcast 1
DHCP client bound to address 192.168.0.10
BIOS> setenv serverip 192.168.0.2
BIOS> saveenv

Do not forget to save your changes in FLASH, to have them available at next power up:
BIOS> saveenv

* Update Linux (still on the target)

Using the new release of U-Boot, it is quite simple to update Linux kernel and rootfs using the news scripts included in the release:

BIOS> run update_kernel

dm9000 i/o: 0x15c00000, id: 0x90000a46
DM9000: running in 16 bit mode
MAC: 00:1e:ac:00:00:02
operating at 100M full duplex mode
TFTP from server 192.168.0.2; our IP address is 192.168.0.10
Filename 'apf9328-linux.bin'.
Load address: 0x8000000
Loading: #################################################################
#################################################################
#################################################################
#################################################################
##############################################
done
Bytes transferred = 1564776 (17e068 hex)

................ done
Erased 16 sectors
Copy to Flash... done
Flashing kernel succeed

* Update rootfs (still on the target)

BIOS> run update_rootfs

dm9000 i/o: 0x15c00000, id: 0x90000a46
DM9000: running in 16 bit mode
MAC: 00:1e:ac:00:00:02
operating at 100M full duplex mode
TFTP from server 192.168.0.2; our IP address is 192.168.0.10
Filename 'apf9328-rootfs.arm.jffs2'.
Load address: 0x8000000
Loading: #################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
######################################################
done
Bytes transferred = 3932160 (3c0000 hex)

........................................... done
Erased 43 sectors
Copy to Flash... done
Flashing rootfs succeed
BIOS>

===update your fpga firmware (on the target)===

Please follow the standard procedure [[InstallTargetSoftware#FPGA_firmware_installation | Firmware installation]]

==How-to develop with Armadeus / customize your SDK==

Your new Armadeus 3 is running fine on the target. Now you probably would like to customize the target for your project. 
If you are a Buildroot user, the following instructions should sound familiar.

===How-to add a software package===

Use the command '''make menuconfig'''':
<pre class="host">
$ make menuconfig
</pre>

[[Image:menuconfig_package.png]]

Select your package in the menu "package", save the configuration and compile a new rootfs
<pre class="host">
$ make
</pre>

{{Note|For a given release, not all packages are tested/running. You can consult the list of the working packages [[Buildroot-20081103_integration| here]].}}

On the target, download and flash the new rootfs:
<pre class="apf">
BIOS> run update_rootfs
...
BIOS> boot
</pre>

===How-to remove a package===

Supposing you would like to remove an unwanted package from the target.
* The first step is to use the command '''make menuconfig''' to unselect this package but this command will not remove the package from the rootfs. You have to use the ''clean'' command of buildroot. In the lines hereafter replace the word <package> with the real name of your package.
<pre class="host">
$ make menuconfig
... deselect your <package>
$ make <package>-clean
$ make
</pre>
Your new rootfs is now ready to use - Enjoy

* Some packages do not support any uninstall behavior. In such a case you can rebuild your environment using the global clean command. This command requests to compile almost everything and therefore will take time.
<pre class="host">
$ make menuconfig
... deselect your <package>
$ make clean
$ make
</pre>

{{Warning|Using this method you will lose any modification you could have done directly in the directory buildroot/project_build_armvYY/apfXX/root.
Please read the chapter [[Armadeus_3#How-to_modify_root_filesystem| How-to modify root filesystem]] hereafter.}}

Your new rootfs is ready to use - Enjoy

* A faster method exists to force to rebuild rootfs. You can delete the root directory. Unfortunately some libraries (ie c++ lib) are not reinstalled using this method.
<pre class="host">
$ make menuconfig
... deselect your <package>
$ rm -rf buildroot/project_build_armv4t/apf9328/root
$ rm -rf buildroot/project_build_armv4t/apf9328/.root
$ make
</pre>

{{Warning|Using this method you will lose any modification you could have done directly in the directory buildroot/project_build_armvYY/apfXX/root.
Please read the chapter [[Armadeus_3#How-to_modify_root_filesystem| How-to modify root filesystem]] hereafter.}}

Your new rootfs is ready to use - Enjoy

===How-to modify a software===

You would like to modify a package and test your modification on the target. The command '''make <package>-clean''' will force to rebuild the package you modified:
<pre class="host">
$ make <package>-clean
$ make
</pre>
Your new rootfs is ready to use - Enjoy

===How-to create a buildroot package===

The creation of a new buildroot package is described more in depth in the specific wiki page [[Buildroot_Packages]] and in the [http://buildroot.uclibc.org/buildroot.html buildroot documentation]

===How-to modify root filesystem===

There are different methods to modify the rootfs of the apf9328:
# modify files directly on the target (ideal solution for first trials)
# modify files in buildroot/project_build_armv4t/apf9328/root/ (to validate your modification with armadeus)
# modify files in buildroot/target/device/aramdeus/rootfs/target_skeleton (your modifcation will support a '''make clean''' )
# create a patch file in armadeus/patches (your modification will support a '''git checkout''')

===How-to modify Linux kernel===

To rebuild the kernel or any kernel driver you can use the command '''make linux26-clean; make'''.
please note the new package name use by buildroot for Linux: linux26
<pre class="host">
$ make linux26-clean
$ make
</pre>

your new Linux kernel and rootfs containing drivers are ready to use - Enjoy

There is another method to rebuild the kernel faster than the previous one:
<pre class="host">
$ make linux26
$ make
</pre>
With this method only the modified files are compiled.

===How-to configure a Linux kernel===

There is a command to modify the linux kernel configuration:
<pre class="host">
$make linux26-menuconfig
</pre>
Modify your kernel configuration, save your change and rebuild Armadeus in few seconds:
<pre class="host">
$make
</pre>

===How-to configure U-Boot===

you can change the U-Boot configuration using the buildroot command '''make menuconfig'''. U-Boot options are in the sub-menu '''target filesystem options'''. In order to rebuild U-Boot with new options it is necessary to remove U-Boot first:
<pre class="host">
$make menuconfig
...
$make u-boot-dirclean
$make
</pre>

{{Warning| the command '''make u-boot-dirclean''' delete the U-Boot directory and any modification you did in this directory.}}

===How-to modify U-Boot===

To rebuild U-Boot you can use the command '''make u-boot-clean; make'''.
<pre class="host">
$ make u-boot-clean
$ make
</pre>
your new U-Boot is ready to use - Enjoy

If you modify the config file ''apf9328.h'' located in ''buildroot/project_build_armv4t/apf9328/u-boot-1.3.4/include/configs/apf9328.h'', then we suggest you to rebuild the whole u-boot package:
<pre class="host">
$ make u-boot-distclean
$ make
</pre>

===How-to configure busybox===
It also possible to modify the Busybox configuration to add or remove some features:
<pre class="host">
$make busybox-menuconfig
</pre>

To be continued...

==Links==
* [http://buildroot.uclibc.org/buildroot.html Buildroot's documentation]

[[Category:Software]]

APF27 FPGA-IMX interface description

2009-08-27T14:58:54Z

VeroniqueL:

This article describe the interface between IMX and Spartan3A on APF27.
Documentation of i.MX interface can be found in the iMX reference manual, chapter 17,
«Wireless External Interface Module ('''WEIM''')».

== Hardware ==

The detailed electronic schematics of apf27 fpga interface can be found on
[http://www.armadeus.com/_downloads/apf27/hardware/apf27_V1.2.pdf this document] page 11. A simplified schema is shown below on figure 1.

[[image:fpgaimx_wire.png|center|500px|thumb|'''figure 1''' - ''FPGA-i.MXL wiring'']]

The signals used in the design are:

* '''CLKO''': Clock generated by i.MX. Used as general clock by the FPGA.
* '''DATA[16]''': 16 bits data bus.
* '''ADDR[13]''': 12 bits address bus, least significant bit (ADDR[0]) is not used because only word access are done.
* '''CS4N_DTACK''': '''C'''hip '''S'''elect 4 or '''D'''ata '''T'''ransmit '''ACK'''nowledge.
* '''CS5''','''CS1''': '''C'''hip '''S'''elect 5 and 1.
* '''EB0N''' and '''EB1N''': For '''E'''nable '''B'''yte, write signal for lower byte and upper byte on data bus.
* '''OEN''': For '''O'''utput '''E'''nable bit, read signal.
* '''DMA_GRANT#''' and '''DMA_REQ#''': Signals to use DMA on i.MX.

Each chip select has its own configuration (timing, address range, ...) that can be used for different slaves in the FPGA.

'''CLKO''' is by default configured to run at 133MHz to be synchronous with the '''WEIM''' bus that is internally clocked at 133MHz, too.

== Chip Select Timings configuration ==

===Present configuration (static timing)===
The default configuration uses '''CS5''' for accessing the FPGA. 32 bits register CS5
is used to configure all timing for this chip select. It's default
configuration is:
* CS5U (Upper 16bits, see page 521 of reference manual ): mw D8002050 00000600
This will add 6 waits state on access to read value correctly (WSC: Wait
State Control).
* CS5L (Lower 16bits,see page 525 of reference manual): mw D8002054 00000D01
Enable chip select (CSEN), Enable for only write access EB[] (EBC) and select data port size to
16bits (DSZ: Data port SiZe).
* CS5A (additionnal register, page 528): mw D8002058 0

* WCR (WEIM Configuration Register): mw D8002060 00002000
Address unshifted for CS5 (AUS5)

[[image:timingstatic.png|center|500px|thumb|'''figure 2''' - ''Static timings chronograms'']]

With this configuration, the access time (read/write) to the FPGA is set to 44ns.

This configuration is interesting because all timings are under control. But
the problem is that to be perfectly synchronous, the FPGA is clocked at 133MHz
like WEIM and some IP design doesn't work at this frequency.

===Alternative configuration (with DTACK)===

To solve the problem, another solution can be the DTACK signal (asynchronous protocol). The DTACK signal
is emitted by the slave to master when write/read is done.
With this solution, access time is variable and the timing is not static any more.

==== i.MX registers configuration ====

To configure CS5N access using dtack, the gpio PF21 must be configured on input with a_out :
<pre class="apf">
md 10015500 1 # read direction register PTF_DDIR
md 10015510 1 # read register PTF_ICONFA2
</pre>
By default, configuration is ok, we just have to select gpio in use :
<pre class="apf">
mw 10015520 FFBF1E80 # PTF_GIUS
</pre>

==== FPGA design ====

On design, the wishbone signal ack is returned to dtack pin. Here a sample code used to test the dtack :

<source lang="VHDL">

library IEEE;
use IEEE.std_logic_1164.all;
use IEEE.numeric_std.all;

-- ----------------------------------------------------------------------------
Entity imx27_wb16_wrapper is
-- ----------------------------------------------------------------------------
port
(
-- i.MX Signals
imx_address : in std_logic_vector(11 downto 0);
imx_data : inout std_logic_vector(15 downto 0);
imx_cs_n : in std_logic;
imx_oe_n : in std_logic;
imx_eb3_n : in std_logic;

imx_dtack : out std_logic ;

data0_out : out std_logic ;
addr1_out : out std_logic ;
cs_n_out : out std_logic ;
oe_n_out : out std_logic ;
eb3_n_out : out std_logic ;
dtack_out : out std_logic ;

-- Global Signals
gls_reset : in std_logic;
gls_clk : in std_logic

);
end entity;

-- ----------------------------------------------------------------------------
Architecture RTL of imx27_wb16_wrapper is
-- ----------------------------------------------------------------------------

constant DELAY : natural := 2;

signal write : std_logic;
signal read : std_logic;
signal strobe : std_logic;
signal writedata : std_logic_vector(15 downto 0);
signal address : std_logic_vector(12 downto 0);

signal reg1 : std_logic_vector(15 downto 0);
signal reg2 : std_logic_vector(15 downto 0);

signal write_ack : std_logic ;
signal read_ack : std_logic ;

signal wbm_address : std_logic_vector(12 downto 0);
signal wbm_writedata: std_logic_vector(15 downto 0);
signal wbm_readdata: std_logic_vector(15 downto 0);
signal wbm_strobe : std_logic ;
signal wbm_write : std_logic ;
signal wbm_cycle : std_logic ;

signal dtack_s : std_logic ; -- dtack
signal dtack_d : std_logic ; -- dtack delayed
signal dtack_reg : std_logic_vector( DELAY-1 downto 0);
--i signal dtack_old: std_logic_vector( DELAY-1 downto 0);
signal dtack_old : std_logic ;

begin

dtack_s <= write_ack or read_ack;

-- imx_dtack <= dtack_d;
-- dtack_out <= dtack_d;

data0_out <= imx_data(0);
addr1_out <= imx_address(1);
cs_n_out <= imx_cs_n;
oe_n_out <= imx_oe_n;
eb3_n_out <= imx_eb3_n;

-- ----------------------------------------------------------------------------
-- External signals synchronization process
-- ----------------------------------------------------------------------------
process(gls_clk, gls_reset)
begin
if(gls_reset='1') then
write <= '0';
read <= '0';
strobe <= '0';
writedata <= (others => '0');
address <= (others => '0');
elsif(rising_edge(gls_clk)) then
strobe <= not (imx_cs_n) and not(imx_oe_n and imx_eb3_n);
write <= not (imx_cs_n or imx_eb3_n);
read <= not (imx_cs_n or imx_oe_n);
address <= imx_address & '0';
writedata <= imx_data;
end if;
end process;

wbm_address <= address when (strobe = '1') else (others => '0');
wbm_writedata <= writedata when (write = '1') else (others => '0');
wbm_strobe <= strobe;
wbm_write <= write;
wbm_cycle <= strobe;

sync_p : process (gls_clk,gls_reset)
variable ack: std_logic ;
begin
if gls_reset = '1' then
imx_data <= (others => 'Z');
imx_dtack <= '0';
dtack_old <= '0';
elsif rising_edge(gls_clk) then
if read = '1' then
imx_data <= wbm_readdata;
dtack_old <= (read_ack or write_ack);
imx_dtack <= dtack_old;
dtack_out <= dtack_old;
else
imx_data <= (others => 'Z');
dtack_old <= '0';
imx_dtack <= '0';
dtack_out <= '0';

end if;

end if;
end process sync_p;

register_write : process(gls_clk,gls_reset)
begin
if gls_reset = '1' then
reg1 <= x"caca";
reg2 <= x"5599";
elsif rising_edge(gls_clk) then
if (wbm_strobe = '1') and (wbm_cycle = '1') and (wbm_write = '1') then
if wbm_address = "0000000000000" then
write_ack <= '1';
reg1 <= wbm_writedata;
elsif wbm_address = "0000000000010" then
write_ack <= '1';
reg2 <= wbm_writedata;
end if;
else
write_ack <= '0';
end if;
end if;
end process register_write;

register_read : process(gls_clk,gls_reset)
begin
if gls_reset = '1' then
wbm_readdata <= (others => '0');
elsif rising_edge(gls_clk) then
if (wbm_strobe = '1') and (wbm_cycle = '1') and (wbm_write = '0') then
if wbm_address = "0000000000000" then
read_ack <= '1';
wbm_readdata <= reg1;
elsif wbm_address = "0000000000010" then
read_ack <= '1';
wbm_readdata <= reg2;
end if;
else
read_ack <= '0';
end if;
end if;
end process register_read;

end architecture RTL;
</source>

With ucf ;

<source lang="bash">
# Constraint file
#
NET "gls_clk" TNM_NET = "gls_clk";
TIMESPEC "TS_rstgen_syscon00_ext_clk" = PERIOD "gls_clk" 7.5188 ns HIGH 50 %;

NET "gls_clk" LOC="N9" | IOSTANDARD=LVCMOS18;# CLK0
NET "imx_cs_n" LOC="P10" | IOSTANDARD=LVCMOS18;# CS5N
NET "imx_eb3_n" LOC="P9" | IOSTANDARD=LVCMOS18;# EB0N
NET "imx_oe_n" LOC="R9" | IOSTANDARD=LVCMOS18;# OEN
NET "imx_dtack" LOC="R3" | IOSTANDARD=LVCMOS18 | DRIVE=8;# CS4N_DTACK

NET "imx_address<0>" LOC="N5" | IOSTANDARD=LVCMOS18;# ADDR1
NET "imx_address<1>" LOC="L7" | IOSTANDARD=LVCMOS18;# ADDR2
NET "imx_address<2>" LOC="M7" | IOSTANDARD=LVCMOS18;# ADDR3
NET "imx_address<3>" LOC="M8" | IOSTANDARD=LVCMOS18;# ADDR4
NET "imx_address<4>" LOC="L8" | IOSTANDARD=LVCMOS18;# ADDR5
NET "imx_address<5>" LOC="L9" | IOSTANDARD=LVCMOS18;# ADDR6
NET "imx_address<6>" LOC="L10" | IOSTANDARD=LVCMOS18;# ADDR7
NET "imx_address<7>" LOC="M11" | IOSTANDARD=LVCMOS18;# ADDR8
NET "imx_address<8>" LOC="P11" | IOSTANDARD=LVCMOS18;# ADDR9
NET "imx_address<9>" LOC="N11" | IOSTANDARD=LVCMOS18;# ADDR10
NET "imx_address<10>" LOC="N12" | IOSTANDARD=LVCMOS18;# ADDR11
NET "imx_address<11>" LOC="P13" | IOSTANDARD=LVCMOS18;# ADDR12

NET "imx_data<0>" LOC="T5" | IOSTANDARD=LVCMOS18 | DRIVE=8;# DATA0
NET "imx_data<1>" LOC="T6" | IOSTANDARD=LVCMOS18 | DRIVE=8;# DATA1
NET "imx_data<2>" LOC="P7" | IOSTANDARD=LVCMOS18 | DRIVE=8;# DATA2
NET "imx_data<3>" LOC="N8" | IOSTANDARD=LVCMOS18 | DRIVE=8;# DATA3
NET "imx_data<4>" LOC="P12" | IOSTANDARD=LVCMOS18 | DRIVE=8;# DATA4
NET "imx_data<5>" LOC="T13" | IOSTANDARD=LVCMOS18 | DRIVE=8;# DATA5
NET "imx_data<6>" LOC="R13" | IOSTANDARD=LVCMOS18 | DRIVE=8;# DATA6
NET "imx_data<7>" LOC="T14" | IOSTANDARD=LVCMOS18 | DRIVE=8;# DATA7
NET "imx_data<8>" LOC="P5" | IOSTANDARD=LVCMOS18 | DRIVE=8;# DATA8
NET "imx_data<9>" LOC="N6" | IOSTANDARD=LVCMOS18 | DRIVE=8;# DATA9
NET "imx_data<10>" LOC="T3" | IOSTANDARD=LVCMOS18 | DRIVE=8;# DATA10
NET "imx_data<11>" LOC="T11" | IOSTANDARD=LVCMOS18 | DRIVE=8;# DATA11
NET "imx_data<12>" LOC="T4" | IOSTANDARD=LVCMOS18 | DRIVE=8;# DATA12
NET "imx_data<13>" LOC="R5" | IOSTANDARD=LVCMOS18 | DRIVE=8;# DATA13
NET "imx_data<14>" LOC="M10" | IOSTANDARD=LVCMOS18 | DRIVE=8;# DATA14
NET "imx_data<15>" LOC="T10" | IOSTANDARD=LVCMOS18 | DRIVE=8;# DATA15

NET "data0_out" LOC="D16" | IOSTANDARD=LVCMOS18 | DRIVE=12;#IO_L22P_1
NET "addr1_out" LOC="D15" | IOSTANDARD=LVCMOS18 | DRIVE=12;#IO_L22N_1
NET "cs_n_out" LOC="N3" | IOSTANDARD=LVCMOS18 | DRIVE=12;#IO_L24P_3
NET "oe_n_out" LOC="R1" | IOSTANDARD=LVCMOS18 | DRIVE=12;#IO_L23P_3
NET "eb3_n_out" LOC="N2" | IOSTANDARD=LVCMOS18 | DRIVE=12;#IO_L22P_3
NET "dtack_out" LOC="M1" | IOSTANDARD=LVCMOS18 | DRIVE=8;#IO_L20P_3

#end
</source>

==== Timings ====

The main problem with this solution is that i.MX wait a too long time (~42ns) after dtack rise to de-assert its chip select.

[[image:dtack.png|center|500px|thumb|'''figure 3''' - ''Read access using dtack'']]

=== Synchronous access with FPGA at 100MHz ===

The main problem with fpga clocked at 100MHz is that wishbone will not be synchronous with WEIM interface (clocked at 133MHz).

==== Simulation ====

To unsure that interface work well, we will simulate it. To reproduce this simulation, ask [[User:FabienM]] that will give you the project (~/podtree/trunk/src/tests/testbus).

[[image:static_fpga100.jpg|center|500px|thumb|'''figure 4''' - ''Timings simulation with FPGA clock at 100MHz, with WSC=6'']]

==== Registers configuration ====

''Changing CLK0 to 100MHz:''

To change CLK0 to 100MHz, we will use HCLK (400MHz) divided by 4.

Selecting HCLK (CCSR)
<pre class="apf">
mw 10027028 00008305 # HCLK Source (MPLL 2x clock output / 3) := 400MHz
</pre>

Divide by 4 (PCDR0);
<pre class="apf">
mw 10027018 12C41083 # divide by 4
</pre>

And we have to add one more clock cycle for CS (CSCR5U):
<pre class="apf">
mw.l D8002050 00000600
</pre>

===Timing register configuration===

All register configurations for external memory are done in u-boot.
Configuration file can be found in
''buildroot/project_build_armv5te/<project_name>/u-boot-1.3.4/include/configs/apf27.h''
And is saved in armadeus tree at
''buildroot/target/device/armadeus/apf27/apf27.h

Web

2009-08-27T14:51:30Z

VeroniqueL:

==Browser==
* [[Links]]

==Chat server==
===Tiny chat server with select() function (no thread) for the armadeus board.===
* C Programming language
* Multi-Users
* Console oriented client in C programming language for Linux, windows ...
* Graphic oriented client in Java ?
Project will continue if people are interested.

===For the moment:===
* Chat server is done, run under armadeus card, windows, linux ...
* Oriented console client is done... (bug with linux, take a lot of ressources)
* Has been tested with Visual Studio 2005 and Code::blocks (mingw) under windows and gcc under linux

=== Download ===
Sources can be found [http://www.surfprotector.org/armadeus/iterativ_chat/ here]

==HTTP Server==
* [[Boa|Boa (Embedded Webserver)]]

==Misc==
* [[Flot|Flot plotting library]]

[[Category:Web]]

Boa

2009-08-27T14:43:45Z

VeroniqueL:

How-to install and configure the Boa Web server on your Armadeus board 

[[Image:boa.png|right]]
 
==Installation==
* Launch Buildroot's configuration:
$ make menuconfig
* Select: ''Package Selection for the Target -> Networking -> boa''
* Save the configuration
* Then build the binaries and the default filesystem. This will be useful later to perform the configuration:
$ make

==Configuration==

=== Generalities ===

To apply a permanent configuration, be sure not to change anything on the board filesystem: that would be erased the next time you reflash the rootfs. 
Instead, do all changes on the filesystem located on the Host, i.e. on ''buildroot/project_build_armv4t/apf9328/root/'' for the APF9328 or ''buildroot/project_build_armv5te/apf27/root/'' for the [[APF27]].

The Boa configuration file is located in ''/etc/boa/boa.conf'' on the board; this means that to permanently change the configuration, you need to edit the file ''buildroot/project_build_armvXX/apfXX/root/etc/boa/boa.conf'' '''on the Host'''. 

As the root directory name is dependent of the target, there is a way to find it automatically:
$ make shell_env && source armadeus_env.sh
Then the directory can be accessed with ''$ARMADEUS_ROOTFS_DIR''.

=== Create a Dummy page ===

*By default, DocumentRoot is set to /var/www, so let's add a dummy file here to test our configuration:

$ mkdir $ARMADEUS_ROOTFS_DIR/var/www
$ vim $ARMADEUS_ROOTFS_DIR/var/www/index.html

*And fill the file with:
<source lang="html4strict">
<html>
<head>
<title> Welcome on the Armadeus Board </title>
</head>
<body>
<nowiki><h1> Welcome on the Armadeus Board </h1></nowiki>
</body>
</html>
</source>

=== Enable hostname resolution ===

*Boa has to be able to resolve the hostname to work, so let's do:

$ echo "127.0.0.1 `cat $ARMADEUS_ROOTFS_DIR/etc/hostname`" >> $ARMADEUS_ROOTFS_DIR/etc/hosts

=== Create the access log directory ===

*By default, Boa logs will be stored in ''/var/log/boa/'' on the card. If you did not change this setting, you will need to perform the following :
$ ls -l $ARMADEUS_ROOTFS_DIR/var/log/

*If this is a link to ''/tmp'', then
$ rm -f $ARMADEUS_ROOTFS_DIR/var/log/ && mkdir $ARMADEUS_ROOTFS_DIR/var/log/

*Then, create the boa directory :
$ mkdir $ARMADEUS_ROOTFS_DIR/var/log/boa

-----
Why shoud I delete the symbolink link? 
This is because during the filesystem creation, mkfs.jffs2 will keep the link from ''/var/log'' to ''/tmp'' on the board.
Thus, once on the board, you will have:
<pre class=apf>
# ls -l /var/log
lrwxrwxrwx 1 root root 4 Apr 15 2007 /var/log -> /tmp
</pre>

With such a behavior, even if you fill the directory ''$ARMADEUS_ROOTFS_DIR/var/log/'' on your host
(which actually fill ''/tmp'' on your host), nothing will be saved once the filesystem will be flashed on your board.

== Test the result ==

*Create the final rootfs:
$ make

*Then [[Target_Software_Installation | update the rootfs]] on your board. Reboot it, and start Boa:
<pre class=apf>
# boa
</pre>

*To access your web page, use a browser:
http://''<your board's IP Address>''/

You should see the page ! 
If not, check the file ''/var/log/boa/error_log'' on your board

[[Image:Boa_welcome.png]]

== Working with cgi ==

*First, check the ''boa.conf'' file. Once more, you should use the one located on your host before changing anything.
$ vi $ARMADEUS_ROOTFS_DIR/etc/boa/boa.conf

*Be sure to have an uncommented line like this:
ScriptAlias /cgi-bin/ /usr/lib/cgi-bin/

*Now, let's write a dummy cgi:

$ mkdir $ARMADEUS_ROOTFS_DIR/usr/lib/cgi-bin
$ vim $ARMADEUS_ROOTFS_DIR/usr/lib/cgi-bin/get_ipconfig.sh

*And add the following :
<source lang="bash">
#!/bin/sh
echo -e "Content-type: text/html\r\n\r\n";
echo -e `/sbin/ifconfig eth0 | grep 'inet addr'`;
</source>
The script have to be executable:
$ chmod a+x $ARMADEUS_ROOTFS_DIR/usr/lib/cgi-bin/get_ipconfig.sh

*Then change your index.html page to add a link to the cgi:

$ vi $ARMADEUS_ROOTFS_DIR/var/www/index.html
<source lang="html4strict">
<html>
<head>
<title> Welcome on the Armadeus Board </title>
</head>
<body>
<h1> Welcome on the Armadeus Board </h1>
 
<a href=http://<Your board IP Address>/cgi-bin/get_ipconfig.sh> Get the board ip config </a>
 
</body>
</html>
</source>

*Create the new rootfs:
$ make

*Finally, [[Target_Software_Installation | transfer the rootfs]] to the board & flash it.

You can now access to the new web page and click on the cgi link !

==Links==
* [http://www.boa.org The Boa Web page]

[[Category:Network]]
[[Category:Web]]

Entertainment

2009-08-27T14:38:10Z

VeroniqueL:

=Portable gaming/media playing platform=
Currently, we have all the necessary hardware interfaces on an APF9328 to develop a high level portable gaming platform, (except probably for sound generation which needs more testing yet). An article explaining how to build that platform has been published in the [http://www.unixgarden.com/index.php/embarque/perles-de-mongueurs-analyse-de-logs-2 Mars 2007 edition of the French Magazine: GLMF (GNU/Linux Magazine France)]. 
I will open a Wiki page to handle user request about technical details (if needed)...

==Native Games==
Current games working on that platform are:
{| border="0" cellpadding="5" cellspacing="0" align="center"
|-
| [[Armanoid]]
| [[PrBoom]]
| [[Castle Wolfenstein]]
|-
| [[Quake]]
| other ideas ?
|-
|}

==Retro Gaming==

===SNES Emulation===
Some tries have been made recently with '''snes9x''' emulator. Tested games are playable without sound emulation but there is still a lot of work.
snes9x uses 16bpp, reducing it to 8bpp could help. Vsync synchro could also be nice. 
Work is not fully commited yet.
Putting sound emulation in FPGA could make it really usable.

===Amiga Emulation===
Coming soon

===Nice ideas to look at===
* http://www.fpga4fun.com/
* http://home.freeuk.com/fpgaarcade/platforms.htm
* http://www.amiga.org/modules/newbb/viewtopic.php?topic_id=27988&forum=8&viewmode=flat&order=ASC&start=0

 
'''At least everything done on GP32 or NintendoDS console should be possible with Armadeus boards.'''

Ask JulienB for more information.

==Detailed capacities==
* display JPEG, PNG
* accept SD/MMC cards
* plays MP3, Ogg music
* display ID3 Tags
* remote control
* access network music server

==PDA==
* Based on the game platform a PDA could be built relatively fast.
* [[Android| Running Android on the APF27]]

Development

2009-08-27T14:27:44Z

VeroniqueL:

On this page you will find useful information to develop software for your Armadeus board
 
==Project==
* [[Sources organisation | Armadeus project sources organisation]]
* [[SVN#Providing_modifications | How to submit patches with your modifications]]

==Tools==
* [[Toolchain|C/C++ Cross Compiler (Toolchain) installation]]
* [[SVN|SVN usage on Armadeus]] and the way to inform us about your changes
* [[GDB|Debugging with GDB and GDBserver]]
* [[QEMU | Simulate an Armadeus system under QEMU]]
* [[Eclipse| Eclipse IDE with GDB debugger]]
* [[ JTAG | Support JTAGKey and BDI2000 JTAG probes]]

==Linux==
{| border="0" cellpadding="5" cellspacing="5" summary="Hardware Add-Ons by functionnalities"
|----------------
|
===Userland applications===
* [[HelloWorld | How to create your first Linux C application for your board]]
* [[HelloWorldCpp |How to create your first Linux C++ application for your board]]
* [[Automatically launch your application]]
||
===Linux kernel development===
* [[kernel drivers status list|Kernel driver status list for the APF boards]]
* [[Linux Debug |Tips to debug under Linux]]
* [[Linux drivers development|Instructions to develop Linux drivers for Armadeus]]
* [[Linux on i.MXL|Resources available on i.MXL Linux kernel development]]
* [[Oops, Linux crashes | Interpreting Linux kernel Oops (crashes)]]
|----------------
|

===Graphical User Interface / Games===
* [[Qt/Embedded]] (Qtopia core 4.2)
* [[EFL|Enlightenment Foundation Libraries]]
* [[SDL Development|SDL]]
* [[Allegro|Allegro]]
* [[Mesa| Mesa 3D graphics library (OpenGL compatible)]]
||

===Scripts===
* [[Perl development | Perl]]
* [[Python development | Python]]
* [[Lua development | Lua]]
|----------------
|
===Realtime applications===
* [[Xenomai]]

|----------------
|}

==Miscellaneous software packages==
* [[Buildroot Packages | Adding packages to Buildroot]]
* [[Samba]]

==Links==
* Things to know when porting x86 software to ARM: http://www.handhelds.org/minihowto/porting-software.html

Development

2009-08-27T14:26:57Z

VeroniqueL:

On this page you will find useful information to develop software for your Armadeus board
 
==Project==
* [[Sources organisation | Armadeus project sources organisation]]
* [[SVN#Providing_modifications | How to submit patches with your modifications]]

==Tools==
* [[Toolchain|C/C++ Cross Compiler (Toolchain) installation]]
* [[SVN|SVN usage on Armadeus]] and the way to inform us about your changes
* [[GDB|Debugging with GDB and GDBserver]]
* [[QEMU | Simulate an Armadeus system under QEMU]]
* [[Eclipse| Eclipse IDE with GDB debugger]]
* [[ JTAG | Support JTAGKey and BDI2000 JTAG probes]]

==Linux==
{| border="0" cellpadding="5" cellspacing="5" summary="Hardware Add-Ons by functionnalities"
|----------------
|
===Userland applications===
* [[HelloWorld | How to create your first Linux C application for your board]]
* [[HelloWorldCpp |How to create your first Linux C++ application for your board]]
* [[Automatically launch your application]]
||
===Linux kernel development===
* [[kernel drivers status list|Kernel driver status list for the APF boards]]
* [[Linux Debug |Tips to debug under Linux]]
* [[Linux drivers development|Instructions to develop Linux drivers for Armadeus]]
* [[Linux on i.MXL|Ressources available on i.MXL Linux kernel development]]
* [[Oops, Linux crashes | Interpreting Linux kernel Oops (crashes)]]
|----------------
|

===Graphical User Interface / Games===
* [[Qt/Embedded]] (Qtopia core 4.2)
* [[EFL|Enlightenment Foundation Libraries]]
* [[SDL Development|SDL]]
* [[Allegro|Allegro]]
* [[Mesa| Mesa 3D graphics library (OpenGL compatible)]]
||

===Scripts===
* [[Perl development | Perl]]
* [[Python development | Python]]
* [[Lua development | Lua]]
|----------------
|
===Realtime applications===
* [[Xenomai]]

|----------------
|}

==Miscellaneous software packages==
* [[Buildroot Packages | Adding packages to Buildroot]]
* [[Samba]]

==Links==
* Things to know when porting x86 software to ARM: http://www.handhelds.org/minihowto/porting-software.html

Development

2009-08-27T14:25:35Z

VeroniqueL:

On this page you will find useful information to develop software for your Armadeus board
 
==Project==
* [[Sources organisation | Armadeus project sources organisation]]
* [[SVN#Providing_modifications | How to submit patches with your modifications]]

==Tools==
* [[Toolchain|C/C++ Cross Compiler (Toolchain) installation]]
* [[SVN|SVN usage on Armadeus]] and the way to provide us your modifications
* [[GDB|Debugging with GDB and GDBserver]]
* [[QEMU | Simulate an Armadeus system under QEMU]]
* [[Eclipse| Eclipse IDE with GDB debugger]]
* [[ JTAG | Support JTAGKey and BDI2000 JTAG probes]]

==Linux==
{| border="0" cellpadding="5" cellspacing="5" summary="Hardware Add-Ons by functionnalities"
|----------------
|
===Userland applications===
* [[HelloWorld | How to create your first Linux C application for your board]]
* [[HelloWorldCpp |How to create your first Linux C++ application for your board]]
* [[Automatically launch your application]]
||
===Linux kernel development===
* [[kernel drivers status list|Kernel driver status list for the APF boards]]
* [[Linux Debug |Tips to debug under Linux]]
* [[Linux drivers development|Instructions to develop Linux drivers for Armadeus]]
* [[Linux on i.MXL|Ressources available on i.MXL Linux kernel development]]
* [[Oops, Linux crashes | Interpreting Linux kernel Oops (crashes)]]
|----------------
|

===Graphical User Interface / Games===
* [[Qt/Embedded]] (Qtopia core 4.2)
* [[EFL|Enlightenment Foundation Libraries]]
* [[SDL Development|SDL]]
* [[Allegro|Allegro]]
* [[Mesa| Mesa 3D graphics library (OpenGL compatible)]]
||

===Scripts===
* [[Perl development | Perl]]
* [[Python development | Python]]
* [[Lua development | Lua]]
|----------------
|
===Realtime applications===
* [[Xenomai]]

|----------------
|}

==Miscellaneous software packages==
* [[Buildroot Packages | Adding packages to Buildroot]]
* [[Samba]]

==Links==
* Things to know when porting x86 software to ARM: http://www.handhelds.org/minihowto/porting-software.html

Setup

2009-08-27T14:24:09Z

VeroniqueL:

On this page, you will find all the useful information to configure your Armadeus board for optimum usage.

==First StartUp==
Just got your Armadeus board and want to start playing with it? Follow these quick steps to setup your environment accordingly:
# Connect your APF to your development board (custom or [[APF9328DevLight|DevLight]]/[[APF9328DevFull|DevFull]]) (your system will be hereafter referred to as "the Target") --->> [[Image:Apf_on_devlight.png|40px]]
# Connect your PC (= "the Host") to your board with a [http://en.wikipedia.org/wiki/Null_modem null-modem RS232 cable] (only Rx/Tx/Gnd signals are needed). If you don't have a RS232 port on your Host, you can use a "USB <-> serial" converter (you'll still need the null-modem cable).
# [[Communicate | Install (minimum) tools to communicate with your APF from your Host.]]
# [[Development_boards_power_supply | Connect the power supply to your development board.]]
# Verify your system is booting by starting Linux: In U-Boot console, type "boot". Several information will be displayed on your terminal like on this [[Linux start screenshot | screenshot ]] (Default Linux login is "root" with an empty password). '''IF NOT''', walk through [[U-Boot communication quick check|this small checklist]].
# 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#Basics | See Basics below]].

===Tutorial===
If you want a more "userfriendly" procedure, you can try this (under construction) tutorial: [[Beginner's_tutorial]]

==Basics for customizing your board==
# [[Toolchain| Install the development environment (=Toolchain) for your board and generate your Linux/rootfs images]]
# [[Target Software Installation| Install/flash your U-Boot, Linux and rootfs freshly generated images on your board]]
# [[Armadeus_3#How-to_develop_with_Armadeus_.2F_customize_your_SDK| Customize your Armadeus SDK]]

==Going further with your board==
* [[Armadeus 3]]: How to use the third generation of Armadeus SDK at a glance (notably for 2.x users). Newcomers can particularly find the chapter [[Armadeus_3#How-to_develop_with_Armadeus_.2F_customize_your_SDK| How-to customize your Armadeus SDK]] interesting.
* [[Network File System configuration| How to configure NFS on Host and Target]]
* [[MultiMediaCard | How to use MMC/SD/microSD cards from Linux on your Armadeus board]]
* [[ALSA|How to play sound with your board]]
* [[Mplayer|How to play videos on your board]]

* [[FrameBuffer]]: How to configure and use the framebuffer for new LCDs
* [[BackLight| How to control the backlight of you graphical LCD (if it supports it)]]
* [[GPIO Driver]]: How to configure the GPIO driver
* [[Boa]]: How to install and configure the boa Web server on your board
* [[USB Gadget]]: How to configure your Armadeus board to use it as a USB device (aka Gadget in Linux language)
* [[DAC|Digital to Analog Convertion]]: How to configure and use the DAC on your board
* [[ADC max1027|Analog to Digital Converter]]: How to install and use the on board ADC (max1027)
* [[PWM]]: How to use the i.MX integrated PWM
* [[RTC]]: How to use an external Real Time Clock (Maxim DS1374)
* [[Watchdog]]: How to configure and use the i.MX integrated Watchdog
* [[TV Output]]: How to use the SVideo output of the APF9328DevFull
* [[USB Host]]: How to use USB Host controllers of the APF9328DevFull and APF27
* [[TSC2102 Linux driver| Touchscreen ]]: How to configure and use the touchscreen controller
* [[CAN bus Linux driver]]: How to configure and use the CAN controller of the DevFull
* [[DVI / HDMI]]: How to configure and use the DVI/HDMI controller of the apf27DevFull
* [http://txlab.wordpress.com/2009/03/20/mounting-the-lcd-touchscreen-on-top-of-armadeus-devboard Low cost assembly of LCD & apf27 development board ]: How to mount the LCD touchscreen on top of Armadeus devboard (Thx to Stanislav)

==Advanced==
* [[Ethernet_MAC_address|How to change your board Ethernet MAC address]] (Thanks to Julien Catalano)
* [[BootLoader]]: (U-Boot useful tips)
* [[BootStrap]]: Install U-Boot from scratch or recover your U-Boot if it was corrupted
* [[ JTAG | Support JTAGKey and BDI2000 JTAG probes]]
* [[Serial Transfer| How to transfer files between your Host and your Armadeus board's Linux with the RS232 link]] (if you don't have Ethernet/NFS/TFTP/MMC/USB)

{{LanguageBar|Setup|Configuration|Konfiguration}}

Using FPGA

2009-08-27T14:18:53Z

VeroniqueL:

__NOTOC__

== First recommended readings ==
* [[FPGA | FPGA on APF introduction]]

==Developing on the APF FPGA==

{| border="0" cellpadding="5" cellspacing="5" summary="Hardware Add-Ons by functionalities" width="100%"
|----------------
|- style="background:#f4f4f4; color:black; -moz-border-radius:18px;"

| width="50%" |
=== Design Tools===
Description of tools used to simulate, to synthesize, and to download/configure FGPA.

* [[ISE WebPack installation on Linux| ISE WebPack (Xilinx's free devt tool) installation]]
* [[How_to_make_a_VHDL_design_in_Ubuntu/Debian| How to setup the FPGA toolchain in Ubuntu/Debian]]
* [[How to simulate post synthesis and post place & route design with GHDL]]

| width="50%" |

===Using ARMadeus FPGA===
Manage the FGPA from ARMadeus distribution.

* [[FPGA_loader | Configure the FPGA from Linux]]
* [[Target_Software_Installation#FPGA_firmware_installation|Configure the FPGA from U-Boot]]
* [[FPGA_register | Access the FPGA address domain from Linux]]
* [[Ho! No FPGA-reset button on armadeus card.]]

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

| width="50%" |

===Designs examples===

These examples give the basis to make VHDL design for FPGA.

* [[Simple blinking LED | LED]]
* [[FPGA and led | Button and LED]]
* [[A simple design with Wishbone bus | Button, Linux drivers, Wishbone bus communication and LED]]

For complex projects, POD should be used to simplify design.

| width="50%" |

===VHDL ===

* [[VHDL coding styles]]
* [http://www.xess.com/ho03000.html Nice ideas/examples to look at]
* [http://www.opencores.org www.opencores.org]
* [http://www.gmvhdl.com/VHDL.html An Introductory VHDL Tutorial]

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

| width="50%" |

===[[Peripherals On Demand]]===

| width="50%" |

===Links===
Some useful links.

''' Wishbone '''
* [http://www.opencores.org/projects.cgi/web/wishbone/wbspec_b3.pdf official Wishbone specifications]
* [http://en.wikipedia.org/wiki/Wishbone_%28computer_bus%29 Wikipedia Wishbone doc]

''' Spartan '''
* [http://www.xilinx.com/support/documentation/data_sheets/ds099.pdf Spartan-3 FPGA Family Data Sheet]

''' Orchestra '''
* [http://osocgen.berlios.de/ Orchestra website]
* [http://developer.berlios.de/projects/osocgen/ Orchestra project page]

|}

Using FPGA

2009-08-27T14:17:25Z

VeroniqueL:

__NOTOC__

== First recommended readings ==
* [[FPGA | FPGA on APF introduction]]

==Developing on the APF FPGA==

{| border="0" cellpadding="5" cellspacing="5" summary="Hardware Add-Ons by functionnalities" width="100%"
|----------------
|- style="background:#f4f4f4; color:black; -moz-border-radius:18px;"

| width="50%" |
=== Design Tools===
Description of tools used to simulate, to synthesize and to download/configure FGPA.

* [[ISE WebPack installation on Linux| ISE WebPack (Xilinx's free devt tool) installation]]
* [[How_to_make_a_VHDL_design_in_Ubuntu/Debian| How to setup the FPGA toolchain in Ubuntu/Debian]]
* [[How to simulate post synthesis and post place & route design with GHDL]]

| width="50%" |

===Using ARMadeus FPGA===
Manage the FGPA from ARMadeus distribution.

* [[FPGA_loader | Configure the FPGA from Linux]]
* [[Target_Software_Installation#FPGA_firmware_installation|Configure the FPGA from U-Boot]]
* [[FPGA_register | Access the FPGA address domain from Linux]]
* [[Ho! No FPGA-reset button on armadeus card.]]

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

| width="50%" |

===Designs examples===

These examples give the basis to make VHDL design for FPGA.

* [[Simple blinking LED | LED]]
* [[FPGA and led | Button and LED]]
* [[A simple design with Wishbone bus | Button, Linux drivers, Wishbone bus communication and LED]]

For complex projects, POD should be used to simplify design.

| width="50%" |

===VHDL ===

* [[VHDL coding styles]]
* [http://www.xess.com/ho03000.html Nice ideas/examples to look at]
* [http://www.opencores.org www.opencores.org]
* [http://www.gmvhdl.com/VHDL.html An Introductory VHDL Tutorial]

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

| width="50%" |

===[[Peripherals On Demand]]===

| width="50%" |

===Links===
Some useful links.

''' Wishbone '''
* [http://www.opencores.org/projects.cgi/web/wishbone/wbspec_b3.pdf official Wishbone specifications]
* [http://en.wikipedia.org/wiki/Wishbone_%28computer_bus%29 Wikipedia Wishbone doc]

''' Spartan '''
* [http://www.xilinx.com/support/documentation/data_sheets/ds099.pdf Spartan-3 FPGA Family Data Sheet]

''' Orchestra '''
* [http://osocgen.berlios.de/ Orchestra website]
* [http://developer.berlios.de/projects/osocgen/ Orchestra project page]

|}

Hardware

2009-08-27T14:15:16Z

VeroniqueL:

==Armadeus Boards==
The following boards are developed by [http://www.armadeus.com Armadeus Systems]. Members of the Armadeus Project association can purchase these products at discount prices. Take a look at the [[Association]] page for details.

{| border="0" cellpadding="5" cellspacing="5" summary="Hardware Add-Ons by functionnalities"
|----------------
|- style="background:#f4f4f4; color:black; -moz-border-radius:18px;"
| width="50%" |
=== Main Boards ===
* [[APF9328]]: i.MXL based board
* [[APF27]]: i.MX27 based board
||

=== Development Boards ===
* [[APF9328DevLight]]: low cost development board for the APF9328
* [[APF9328DevFull]]: full featured development board for the APF9328 (no more available)
* [[APF27Dev]]: full featured development board for the APF27 (with several options)
|----------------
|- style="background:#f4f4f4; color:black; -moz-border-radius:18px;"
| width="50%" |
=== Extension Boards ===
* [[LQ043_Adapt]]: Adapter board for the LQ043 color TFT display from Sharp
* [[MTF-T035|Microtips 320x240 TFT]]: Adapter board for the MTF-T035 color TFT display from Microtips (no more available)
|}

==Hardware Add-Ons by functionalities==
{| border="0" cellpadding="5" cellspacing="5" summary="Hardware Add-Ons by functionnalities"
|----------------
|- style="background:#f4f4f4; color:black; -moz-border-radius:18px;"
|
===User input===
* [[IR Receiver | InfraRed Receiver]]
* [[PS/2 | Connect PS/2 devices to your board]]
* [[Keypad | Connect a keypad to your board]]
* [[TSC2102 | Touchscreen controller of APF9328 DevFull]]
* [[TSC2101 | Touchscreen controller of APF27]]
* [[GPIO_Driver | General Purposes I/Os]]
||

===Display===
* [[LCD | Connect LCDs (graphic & text) to your board]]
* [[TV Output | Use the SVideo output of the DevFull]]
||

===Audio===
* [[Audio with PWM | PC speakers directly on PWM output]]
* [[TSC2102 | Audio playback chip of APF9328DevFull]]
* [[TSC2101 | Audio playback chip of APF27Dev]]

|----------------
|- style="background:#f4f4f4; color:black; -moz-border-radius:18px;"
|
===Mass storage===
* [[MMC/SD | Connect MMC/SD devices to your board]]
||

===External devices control===
* [[Max5821 | Use the optionnal DAC (Digital to Analog)]]
* [[ADC_max1027 | Use the optionnal ADC (Analog to Digital)]]
* Stepping motor controller
||

===Extending board connectivity===
* [[USB Host | USB Host controller]]
* [[GPS | GPS receivers]]
|----------------
|}

==Supported Bus informations==
{| cellspacing=5 cellpadding=5 border=0 width=100%
{{IconLink|USB|USB|usb.png|Universal Serial Bus}}
{{IconLink|I2C|I2C|I2C.png|Inter Integrated Circuit communication bus}}
|-
{{IconLink|SDIO|SDIO|SDIO.png|SD bus}}
{{IconLink|PS/2|PS/2|ps2.png|Input Device bus}}
|-
{{IconLink|Controller Area Network|CAN Bus|CAN_Bus.png|Most used field bus}}
{{IconLink|RS-232|RS-232|RS232_icon.png|Old but still very used/usefull serial bus}}
|}

==Tools==
* [http://kicad.sourceforge.net/ Kicad EDA tool]

ArmadeusWiki:Community Portal

2009-08-27T14:02:54Z

VeroniqueL:

Our project is hosted by Sourceforge: http://sourceforge.net/projects/armadeus 
There you will find our bug manager, our mailing list, and our SVN repository.

Discussions are often held in the evening on IRC: irc://irc.rezosup.org/#Armadeus and irc://irc.rezosup.org/#Armadeus_eng for our English speaking friends. Feel free to join us!

[[Image:FrenchFlag.png]] 
Notre projet est hébergé sur Sourceforge: http://sourceforge.net/projects/armadeus 
Vous y trouverez notre gestionnaire de bug, notre liste de diffusion et notre dépôt SVN.

Nous discutons souvent le soir de sujets et d'autres sur IRC: irc://irc.rezosup.org/#Armadeus et irc://irc.rezosup.org/#Armadeus_eng pour nos amis anglophones. N'hésitez pas à passer nous voir !

Help:Contents

2009-08-27T13:58:41Z

VeroniqueL:

===You are lost/disappointed and need help?===

* Please first read the [[FAQ]].

* HowTo write articles for [[WritingRules | armadeus wiki]].

* There are some very interesting presentations about Linux usage in embedded context here: http://free-electrons.com

* You can send an email on the sourceforge mailing list: https://lists.sourceforge.net/lists/listinfo/armadeus-forum

* For the past few months we have had 2 dedicated IRC channels where we talk together in the evening and during the weekend: irc://irc.rezosup.org/#Armadeus and a second to talk in English irc://irc.rezosup.org/#Armadeus_eng.
* If you are searching an IRC client, [http://en.wikipedia.org/wiki/Comparison_of_Internet_Relay_Chat_clients here is a complete list]. Chatzilla, Irssi, Mibbit and Quassel are good candidates.

* '''as last resort''', you can contact us directly: '''wiki (at) armadeus (dot) com'''

 
[[Image:FrenchFlag.png]]

===Vous êtes perdus et avez besoin d'aide ?===

* en premier lieu, lisez attentivement la [[Fr:FAQ|FAQ]]
* Il y a des présentations très intéressantes sur l'utilisation de Linux dans le domaine de l'embarqué ici: http://free-electrons.com
* vous pouvez envoyer un courriel sur la liste de diffusion ou les forums de SourceForge: https://lists.sourceforge.net/lists/listinfo/armadeus-forum
* depuis peu nous avons 2 canaux IRC dédiés où nous discutons souvent le soir et/ou le WE: irc://irc.rezosup.org/#Armadeus et le second pour les discussions en anglais irc://irc.rezosup.org/#Armadeus_eng.
* Clients IRC testés:
** Linux: Chatzilla, Irssi, Quassel
** Web: [http://www.mibbit.com/ Mibbit]
** [http://en.wikipedia.org/wiki/Comparison_of_Internet_Relay_Chat_clients La liste complète des clients IRC pour chaque plateforme]
* '''en dernier recours''', contactez nous directement par courriel: '''support (chez) armadeus (point) com'''

Help:Contents

2009-08-27T13:57:14Z

VeroniqueL:

===You are lost/disappointed and need help?===

* Please first read the [[FAQ]].

* HowTo write articles for [[WritingRules | armadeus wiki]].

* There are some very interesting presentations of Linux usage in embedded context here: http://free-electrons.com

* You can send an email on the sourceforge mailing list: https://lists.sourceforge.net/lists/listinfo/armadeus-forum

* For the past few months we have had 2 dedicated IRC channels where we talk together in the evening and during the weekend: irc://irc.rezosup.org/#Armadeus and a second to talk in english irc://irc.rezosup.org/#Armadeus_eng.
* If you are searching an IRC client, [http://en.wikipedia.org/wiki/Comparison_of_Internet_Relay_Chat_clients here is a complete list]. Chatzilla, Irssi, Mibbit and Quassel are good candidates.

* '''as last resort''', you can contact us directly: '''wiki (at) armadeus (dot) com'''

 
[[Image:FrenchFlag.png]]

===Vous êtes perdus et avez besoin d'aide ?===

* en premier lieu, lisez attentivement la [[Fr:FAQ|FAQ]]
* Il y a des présentations très intéressantes sur l'utilisation de Linux dans le domaine de l'embarqué ici: http://free-electrons.com
* vous pouvez envoyer un courriel sur la liste de diffusion ou les forums de SourceForge: https://lists.sourceforge.net/lists/listinfo/armadeus-forum
* depuis peu nous avons 2 canaux IRC dédiés où nous discutons souvent le soir et/ou le WE: irc://irc.rezosup.org/#Armadeus et le second pour les discussions en anglais irc://irc.rezosup.org/#Armadeus_eng.
* Clients IRC testés:
** Linux: Chatzilla, Irssi, Quassel
** Web: [http://www.mibbit.com/ Mibbit]
** [http://en.wikipedia.org/wiki/Comparison_of_Internet_Relay_Chat_clients La liste complète des clients IRC pour chaque plateforme]
* '''en dernier recours''', contactez nous directement par courriel: '''support (chez) armadeus (point) com'''

Help:Contents

2009-08-27T13:52:50Z

VeroniqueL:

===You are lost/disappointed and need Help?===

* Please first read the [[FAQ]].

* HowTo write articles for [[WritingRules | armadeus wiki]].

* There are some very interesting presentations of Linux usage in embedded context here: http://free-electrons.com

* You can send an email on the sourceforge mailing list: https://lists.sourceforge.net/lists/listinfo/armadeus-forum

* For the past few months we have had 2 dedicated IRC channels where we talk together in the evening and during the weekend: irc://irc.rezosup.org/#Armadeus and a second to talk in english irc://irc.rezosup.org/#Armadeus_eng.
* If you are searching an IRC client, [http://en.wikipedia.org/wiki/Comparison_of_Internet_Relay_Chat_clients here is a complete list]. Chatzilla, Irssi, Mibbit and Quassel are good candidates.

* '''as last resort''', you can contact us directly: '''wiki (at) armadeus (dot) com'''

 
[[Image:FrenchFlag.png]]

===Vous êtes perdus et avez besoin d'aide ?===

* en premier lieu, lisez attentivement la [[Fr:FAQ|FAQ]]
* Il y a des présentations très intéressantes sur l'utilisation de Linux dans le domaine de l'embarqué ici: http://free-electrons.com
* vous pouvez envoyer un courriel sur la liste de diffusion ou les forums de SourceForge: https://lists.sourceforge.net/lists/listinfo/armadeus-forum
* depuis peu nous avons 2 canaux IRC dédiés où nous discutons souvent le soir et/ou le WE: irc://irc.rezosup.org/#Armadeus et le second pour les discussions en anglais irc://irc.rezosup.org/#Armadeus_eng.
* Clients IRC testés:
** Linux: Chatzilla, Irssi, Quassel
** Web: [http://www.mibbit.com/ Mibbit]
** [http://en.wikipedia.org/wiki/Comparison_of_Internet_Relay_Chat_clients La liste complète des clients IRC pour chaque plateforme]
* '''en dernier recours''', contactez nous directement par courriel: '''support (chez) armadeus (point) com'''

FAQ

2009-08-27T13:48:09Z

VeroniqueL:

==General Questions==

===What is the "Armadeus Project" intended for ?===
The goal of this project is to allow everyone to easily develop embedded Open Source systems.
When all the embedded systems in the world will run open source software, life will be better ;-)

===What does "Armadeus" mean ?===
"Armadeus" is the contraction of "ARM" and "Amadeus". Indeed we choosed ARM 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.

===How do I get help ?===
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 & Mulhouse who can provide help. For Swiss members, we can provide help in Basel, Lausanne & Zürich.

=== Why are there http://armadeus.org and http://armadeus.com ? Is there a company backing/hiding behind the association? ===

<http://armadeus.com> is the webpage dedicated to Armadeus Systems. 
The company develops and produces the main boards which are then available at a discount price to the association members (non commercial usage only!).

Historically the Armadeus Project (association) was founded before Armadeus Systems (company). 
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.

The association was started for our own pleasure and also to help universities and enthusiasts develop Linux embedded systems. 
It is a non profit association and works mostly on founders' free time.

The developments (hardware/firmware/software) performed within the association are under GPL/LGPL licence. 
The hardware funded by the association can not be used in a commercial product.

==Hardware Questions==
===Are the Armadeus boards RoHS compliant ?===
Yes

==Software Questions==
===Where are the sources ?===
We have a project on SourceForge: http://sourceforge.net/projects/armadeus/ with a SVN repository
 

===What are the performances of your board ?===
[[Performances | Wiki page talking about board performances]]

===How do I get help/support===
[[Help:Contents]]

{{LanguageBar|FAQ|FAQ|FAQ}}

Association

2009-08-27T13:42:32Z

VeroniqueL:

==Legal status of the association==
The "Armadeus Project" is a French non-profit association (law 1901) that was founded in Mulhouse, France (68). We accept members from everywhere.
The production of the development boards used by the association is done by a privately owned company, which is independent of the project. Board reselling is done by the [http://www.armadeus.com armadeus systems] company, founded by Armadeus Project leaders.

==To become a member==

* At first, you must fill the [http://www.armadeus.com/assos_downloads/adhesion2008_en.pdf following membership form] and send it back either by mail (see form) or e-mail (adhesion(at)armadeus(dot)org).
* Then, go to the armadeus systems online shop and [https://ssl3.ovh.net/~armadeus/onlineshop/catalog/create_account.php?language=en create an account] (Do not buy any products just yet!!). '''IMPORTANT: Check Association Armadeus Project membership option when creating the account !!'''
* Then, after a few days (max. 3), the following message should appear when you log in:

[[Image:Imamember.png]]

* Now you can buy your boards. You become a member as soon as you purchase at least one main board (here an APF9328). This will ensure that new members will develop on the same basis. After that you will receive your userid and your password to participate to this Wiki and project activities. '''Everyone is welcome!'''

[[Members|Geographical position of the members]]

[[MemberList|Active members list]]

==Why become a member?==
* Benefit from special prices on the products (the goal of the association is not to make money)
* Participate to the development of new boards
* Increase your experience
* Enjoy working with other developers

==Restrictions==
* The boards bought through the association membership can not be used in a commercial product unless this product belongs to the association.
* The software/firmware developments realized within the association have to be GPL/LGPL compliant.
* The Armadeus Project association is not responsible for the misuse or malfunction of the developments performed within the association.

==Buying hardware==

Minimum system is composed of an APF9328 and a DevLight V2. These boards can be bought online. Note that the displayed prices are the "commercial" ones and that the discounts are applied to association members only. Ex.: 22 euros discount on an APF9328_Dev_Light V2, visible by browsing the product information and '''only if the member is logged in'''. Therefore, in this case, the price will be 45 euros (not including taxes) for the members:

[[Image:devlightV2.png]]

==Association prices (not including taxes)==

{| border="0" cellpadding="1" cellspacing="0" summary="Armadeus members special prices"
|-
|* APF9328-M16F16-EFA: || || 105,00 €
|-
|* APF9328_Dev_Light V2: |||| 45,00 €
|-
|* LQ043_adapt (LCD kit): || || 79,50 €
|-
|* Kit_APF9328_Light: || || 139,00 €
|-
|* APF27-M64F256-EU: || || 121,00 €
|-
|* APF27-M128F256-EUF200: || || 139,50 €
|-
|* APF27-DevLight: || || 129,50 €
|-
|* APF27-DevFull: || || 184,50 €
|}

Note: ''French VAT (19.6%) _not_ included''

==Remarks==
* No accessories (cable, power supply...) are delivered with the boards. You can purchase them at your favorite supplier for a few $
* Grouped orders can be organized for some special components, such as LCDs, special connectors...

 
{{LanguageBar|Association|Association|Verein}}

[[Category:Association]]

Association

2009-08-27T13:39:52Z

VeroniqueL:

==Legal status of the association==
The "Armadeus Project" is a French non-profit association (law 1901) that was founded in Mulhouse, France (68). We accept members from everywhere.
The production of the development boards used by the association is done by a privately owned company, which is independent of the project. Board reselling is done by the [http://www.armadeus.com armadeus systems] company, founded by Armadeus Project leaders.

==To become a member==

* At first, you must fill the [http://www.armadeus.com/assos_downloads/adhesion2008_en.pdf following membership form] and send it back either by mail (see form) or e-mail (adhesion(at)armadeus(dot)org).
* Then, go to the armadeus systems online shop and [https://ssl3.ovh.net/~armadeus/onlineshop/catalog/create_account.php?language=en create an account] (Do not buy any products just yet!!). '''IMPORTANT: Check Association Armadeus Project membership option when creating the account !!'''
* Then, after a few days (max. 3), the following message should appear when you log in:

[[Image:Imamember.png]]

* Now you can buy your boards. You become a member as soon as you purchase at least one main board (here an APF9328). This will ensure that new members will develop on the same basis. After that you will receive your userid and your password to participate to this Wiki and project activities. '''Everyone is welcome!'''

[[Members|Geographical position of the members]]

[[MemberList|Active members list]]

==Why become a member?==
* Benefit from special prices on the products (the goal of the association is not to make money)
* Participate to the development of new boards
* Increase your experience
* Enjoy working with other developers

==Restrictions==
* The boards bought through the association membership can not be used in a commercial product unless this product belongs to the association.
* The software/firmware developments realized within the association have to be GPL/LGPL compliant.
* The Armadeus Project association can not be blamed for the misuse or malfunction of the developments performed within the association.

==Buying hardware==

Minimum system is composed of an APF9328 and a DevLight V2. These boards can be bought online. Note that the displayed prices are the "commercial" ones and that the discounts are applied to association members only. Ex.: 22 euros discount on an APF9328_Dev_Light V2, visible by browsing the product information and '''only if the member is logged in'''. Therefore, in this case, the price will be 45 euros (not including taxes) for the members:

[[Image:devlightV2.png]]

==Association prices (not including taxes)==

{| border="0" cellpadding="1" cellspacing="0" summary="Armadeus members special prices"
|-
|* APF9328-M16F16-EFA: || || 105,00 €
|-
|* APF9328_Dev_Light V2: |||| 45,00 €
|-
|* LQ043_adapt (LCD kit): || || 79,50 €
|-
|* Kit_APF9328_Light: || || 139,00 €
|-
|* APF27-M64F256-EU: || || 121,00 €
|-
|* APF27-M128F256-EUF200: || || 139,50 €
|-
|* APF27-DevLight: || || 129,50 €
|-
|* APF27-DevFull: || || 184,50 €
|}

Note: ''French VAT (19.6%) _not_ included''

==Remarks==
* No accessories (cable, power supply...) are delivered with the boards. You can purchase them at your favorite supplier for a few $
* Grouped orders can be organized for some special components, such as LCDs, special connectors...

 
{{LanguageBar|Association|Association|Verein}}

[[Category:Association]]

Association

2009-08-27T13:36:23Z

VeroniqueL:

==Legal status of the association==
The "Armadeus Project" is a French non-profit association (law 1901) that was founded in Mulhouse, France (68). We accept members from everywhere.
The production of the development boards used by the association is done by a privately owned company, which is independent of the project. Board reselling is done by the [http://www.armadeus.com armadeus systems] company, founded by Armadeus Project leaders.

==To become a member==

* At first, you must fill the [http://www.armadeus.com/assos_downloads/adhesion2008_en.pdf following membership form] and send it back either per mail (see form) or per e-mail (adhesion(at)armadeus(dot)org).
* Then, go to the armadeus systems online shop and [https://ssl3.ovh.net/~armadeus/onlineshop/catalog/create_account.php?language=en create an account] (Do not buy any products just yet!!). '''IMPORTANT: Check Association Armadeus Project membership option when creating the account !!'''
* Then, after a few days (max. 3), the following message should appear when you log in:

[[Image:Imamember.png]]

* Now you can buy your boards. You become a member as soon as you purchase at least one main board (here an APF9328). This will ensure that new members will develop on the same basis. After that you will receive your userid and your password to participate to this Wiki and project activities. '''Everyone is welcome!'''

[[Members|Geographical position of the members]]

[[MemberList|Active members list]]

==Why become a member?==
* Benefit from special prices on the products (the goal of the association is not to make money)
* Participate to the development of new boards
* Increase your experience
* Enjoy working with other developers

==Restrictions==
* The boards bought through the association membership can not be used in a commercial product unless this product belongs to the association.
* The software/firmware developments realized within the association have to be GPL/LGPL compliant.
* The Armadeus Project association can not be blamed for the misuse or malfunction of the developments performed within the association.

==Buying hardware==

Minimum system is composed of an APF9328 and a DevLight V2. These boards can be bought online. Note that the displayed prices are the "commercial" ones and that the discounts are applied to association members only. Ex.: 22 euros discount on an APF9328_Dev_Light V2, visible by browsing the product information and '''only if the member is logged in'''. Therefore, in this case, the price will be 45 euros (not including taxes) for the members:

[[Image:devlightV2.png]]

==Association prices (not including taxes)==

{| border="0" cellpadding="1" cellspacing="0" summary="Armadeus members special prices"
|-
|* APF9328-M16F16-EFA: || || 105,00 €
|-
|* APF9328_Dev_Light V2: |||| 45,00 €
|-
|* LQ043_adapt (LCD kit): || || 79,50 €
|-
|* Kit_APF9328_Light: || || 139,00 €
|-
|* APF27-M64F256-EU: || || 121,00 €
|-
|* APF27-M128F256-EUF200: || || 139,50 €
|-
|* APF27-DevLight: || || 129,50 €
|-
|* APF27-DevFull: || || 184,50 €
|}

Note: ''French VAT (19.6%) _not_ included''

==Remarks==
* No accessories (cable, power supply...) are delivered with the boards. You can purchase them at your favorite supplier for a few $
* Grouped orders can be organized for some special components, such as LCDs, special connectors...

 
{{LanguageBar|Association|Association|Verein}}

[[Category:Association]]

Association

2009-08-27T13:35:23Z

VeroniqueL:

==Legal status of the association==
The "Armadeus Project" is a French non-profit association (law 1901) from Mulhouse, France (68). We accept members from everywhere.
The production of the development boards used by the association is done by a privately owned company, which is independent of the project. Board reselling is done by the [http://www.armadeus.com armadeus systems] company, founded by Armadeus Project leaders.

==To become a member==

* At first, you must fill the [http://www.armadeus.com/assos_downloads/adhesion2008_en.pdf following membership form] and send it back either per mail (see form) or per e-mail (adhesion(at)armadeus(dot)org).
* Then, go to the armadeus systems online shop and [https://ssl3.ovh.net/~armadeus/onlineshop/catalog/create_account.php?language=en create an account] (Do not buy any products just yet!!). '''IMPORTANT: Check Association Armadeus Project membership option when creating the account !!'''
* Then, after a few days (max. 3), the following message should appear when you log in:

[[Image:Imamember.png]]

* Now you can buy your boards. You become a member as soon as you purchase at least one main board (here an APF9328). This will ensure that new members will develop on the same basis. After that you will receive your userid and your password to participate to this Wiki and project activities. '''Everyone is welcome!'''

[[Members|Geographical position of the members]]

[[MemberList|Active members list]]

==Why become a member?==
* Benefit from special prices on the products (the goal of the association is not to make money)
* Participate to the development of new boards
* Increase your experience
* Enjoy working with other developers

==Restrictions==
* The boards bought through the association membership can not be used in a commercial product unless this product belongs to the association.
* The software/firmware developments realized within the association have to be GPL/LGPL compliant.
* The Armadeus Project association can not be blamed for the misuse or malfunction of the developments performed within the association.

==Buying hardware==

Minimum system is composed of an APF9328 and a DevLight V2. These boards can be bought online. Note that the displayed prices are the "commercial" ones and that the discounts are applied to association members only. Ex.: 22 euros discount on an APF9328_Dev_Light V2, visible by browsing the product information and '''only if the member is logged in'''. Therefore, in this case, the price will be 45 euros (not including taxes) for the members:

[[Image:devlightV2.png]]

==Association prices (not including taxes)==

{| border="0" cellpadding="1" cellspacing="0" summary="Armadeus members special prices"
|-
|* APF9328-M16F16-EFA: || || 105,00 €
|-
|* APF9328_Dev_Light V2: |||| 45,00 €
|-
|* LQ043_adapt (LCD kit): || || 79,50 €
|-
|* Kit_APF9328_Light: || || 139,00 €
|-
|* APF27-M64F256-EU: || || 121,00 €
|-
|* APF27-M128F256-EUF200: || || 139,50 €
|-
|* APF27-DevLight: || || 129,50 €
|-
|* APF27-DevFull: || || 184,50 €
|}

Note: ''French VAT (19.6%) _not_ included''

==Remarks==
* No accessories (cable, power supply...) are delivered with the boards. You can purchase them at your favorite supplier for a few $
* Grouped orders can be organized for some special components, such as LCDs, special connectors...

 
{{LanguageBar|Association|Association|Verein}}

[[Category:Association]]

Association

2009-08-27T13:34:15Z

VeroniqueL:

==Legal status of the association==
The "Armadeus Project" is a French non-profit association (law 1901) from Mulhouse, France (68). We accept members from everywhere.
The production of the development boards used by the association is done by a privately owned company, which is independent of the project. Board reselling is done by the [http://www.armadeus.com armadeus systems] company, founded by Armadeus Project leaders.

==To become a member==

* At first, you must fill the [http://www.armadeus.com/assos_downloads/adhesion2008_en.pdf following membership form] and send it back either per mail (see form) or per e-mail (adhesion(at)armadeus(dot)org).
* Then, go to the armadeus systems online shop and [https://ssl3.ovh.net/~armadeus/onlineshop/catalog/create_account.php?language=en create an account] (Do not buy any products just yet!!). '''IMPORTANT: Check Association Armadeus Project membership option when creating the account !!'''
* Then, after a few days (max. 3), the following message should appear when you log in:

[[Image:Imamember.png]]

* Now you can buy your boards. You become a member as soon as you purchase at least one main board (here an APF9328). This will ensure that new members will develop on the same basis. After that you will receive your userid and your password to participate to this Wiki and project activities. '''Everyone is welcome!'''

[[Members|Geographical position of the members]]

[[MemberList|Active members list]]

==Why become a member ?==
* Benefit from special prices on the products (the goal of the association is not to make money)
* Participate to the development of new boards
* Increase your experience
* Enjoy working with other developers

==Restrictions==
* The boards bought through the association membership can not be used in a commercial product unless this product belongs to the association.
* The software/firmware developments realized within the association have to be GPL/LGPL compliant.
* The Armadeus Project association can not be blamed for the misuse or malfunction of the developments performed within the association.

==Buying hardware==

Minimum system is composed of an APF9328 and a DevLight V2. These boards can be bought online. Note that the displayed prices are the "commercial" ones and that the discounts are applied to association members only. Ex.: 22 euros discount on an APF9328_Dev_Light V2, visible by browsing the product information and '''only if the member is logged in'''. Therefore, in this case, the price will be 45 euros (not including taxes) for the members:

[[Image:devlightV2.png]]

==Association prices (not including taxes)==

{| border="0" cellpadding="1" cellspacing="0" summary="Armadeus members special prices"
|-
|* APF9328-M16F16-EFA: || || 105,00 €
|-
|* APF9328_Dev_Light V2: |||| 45,00 €
|-
|* LQ043_adapt (LCD kit): || || 79,50 €
|-
|* Kit_APF9328_Light: || || 139,00 €
|-
|* APF27-M64F256-EU: || || 121,00 €
|-
|* APF27-M128F256-EUF200: || || 139,50 €
|-
|* APF27-DevLight: || || 129,50 €
|-
|* APF27-DevFull: || || 184,50 €
|}

Note: ''French VAT (19.6%) _not_ included''

==Remarks==
* No accessories (cable, power supply...) are delivered with the boards. You can purchase them at your favorite supplier for a few $
* Grouped orders can be organized for some special components, such as LCDs, special connectors...

 
{{LanguageBar|Association|Association|Verein}}

[[Category:Association]]

Association

2009-08-27T13:25:11Z

VeroniqueL:

==Legal status of the association==
The "Armadeus Project" is a French non-profit association (law 1901) from Mulhouse, France (68). We accept members from everywhere.
The production of the development boards used by the association is done by a privately owned company, which is independent of the project. Board reselling is done by the [http://www.armadeus.com armadeus systems] company, founded by Armadeus Project leaders.

==To become a member==

* At first, you must fill the [http://www.armadeus.com/assos_downloads/adhesion2008_en.pdf following membership form] and send it back either per mail (see form) or per e-mail (adhesion(at)armadeus(dot)org).
* Then, go to the armadeus systems online shop and [https://ssl3.ovh.net/~armadeus/onlineshop/catalog/create_account.php?language=en create an account] (Do not buy any products just yet!!). '''IMPORTANT: Check Association Armadeus Project membership option when creating the account !!'''
* Then, after a few days (max. 3), the following message should appear when you log in :

[[Image:Imamember.png]]

* Now you can buy your boards. You definitively become a member as soon as you purchase at least one main board (here an APF9328). This will ensure that new members will develop on the same basis. After that you will receive your userid and your password to participate to this Wiki and project activities. '''Everyone is welcome!'''

[[Members|Geographical position of the members]]

[[MemberList|Active members list]]

==Why become a member ?==
* Benefit from special prices on the products (the goal of the association is not to make money)
* Participate to the development of new boards
* Increase your experience
* Enjoy working with other developers.

==Restrictions==
* The boards bought through the association membership can not be used in a commercial product unless this product belongs to the association
* The software/firmware developments realized within the association have to be GPL/LGPL compliant
* The Armadeus Project association can not be blamed for the wrong usage or malfunction of the developments performed within the association

==Buying hardware==

Minimum system is composed of an APF9328 and a DevLight V2. Theses boards can be bought online. Note that the displayed prices are the "commercial" ones and the discounts are applied only to the recognized association members. Ex: 22 euros discount on an APF9328_Dev_Light V2, visible by browsing the product informations and '''only if the member is logged in'''. Therefore, in this case, the price will be 45 euros (ex. taxes) for the members:

[[Image:devlightV2.png]]

==Association prices (excluding taxes)==

{| border="0" cellpadding="1" cellspacing="0" summary="Armadeus members special prices"
|-
|* APF9328-M16F16-EFA: || || 105,00 €
|-
|* APF9328_Dev_Light V2: |||| 45,00 €
|-
|* LQ043_adapt (LCD kit): || || 79,50 €
|-
|* Kit_APF9328_Light: || || 139,00 €
|-
|* APF27-M64F256-EU: || || 121,00 €
|-
|* APF27-M128F256-EUF200: || || 139,50 €
|-
|* APF27-DevLight: || || 129,50 €
|-
|* APF27-DevFull: || || 184,50 €
|}

Note: ''French VAT (19.6%) _not_ included''

==Remarks==
* No accessories (cable, power supply...) are delivered with the boards. You can purchase them by your favorite distributor for a few $
* Grouped orders can be organized for some special components like LCDs, special connectors...

 
{{LanguageBar|Association|Association|Verein}}

[[Category:Association]]