ArmadeusWiki - User contributions [en]

I2C

2009-07-18T22:48:47Z

JeanBaptisteM: /* APF9328 I2C bus logic 5v level adaptation (if necessary) */ Addition of low-cost level shifter pointer.

This page will summarize the informations to use the I2C bus on our boards.

==Overview==
The I2C bus is a simple & widely used two wires synchronous bus. It has been developped by [http://www.nxp.com Philips (now NXP)]. 
The standard frequency is 100kHz but 400kHz devices can be found (for example the i.MX).
Single and multi masters are supported. Only the single master configuration will be discussed here.

The bus is based on two signals: SDA and SCL.
* SDA: bidirectional line for data
* SCL: unidirectional line for the clock (provided by the master)

Details can be found in the specification [http://www.nxp.com/acrobat_download/literature/9398/39340011.pdf here.]

==Linux configuration==
By default the I2C bus is activated in the Armadeus distrib.
If you need to deactivate it, take a look at the linux menuconfig (make linux-menuconfig)

==Linux user space C code==
You can find a sample code under ''target/packages/ch7024ctrl/'' of the Armadeus distribution ( [http://armadeus.svn.sourceforge.net/viewvc/armadeus/trunk/target/packages/ch7024ctrl/ or here through SF's SVN browsing] )

==Tested I2C chips==
* RTC: DS1327
* DAC: [[Max5821]]
* Misc: [[TV_Output | CH7024]]
* EEPROM:

==APF9328 I2C bus logic 5v level adaptation (if necessary)==
On the APF9328 the I2C bus has a 3,3V logic level so '''if you want to use 5V I2C devices you have to add a level converter''', for example a PCA9306 from NXP:
* Connect pin 1 to the local GND
* Connect pin 2 to the local 3.3V
* Connect pin 3 to the SCL output of the APF
* Connect pin 4 to the SDA input/ouput of the APF
* Connect pin 7 and 8 together and the add a 200K resistor in parallel to a 100nF capacitor to GND
* Connect a pullup of 1.7K to the 5V SCL line (pin 6)
* Connect a pullup of 1.7K to the 5V SDA line (pin 5)

For more details, take a look at the [http://www.nxp.com/acrobat_download/datasheets/PCA9306_2.pdf PCA9306 datasheet].
This chip is the one that can be mounted by users on the DevFull board.

As a low-cost alternative, a level shifter can be built with a pair of N-channel mosfets (such as a BS170). See the [http://www.nxp.com/acrobat_download/applicationnotes/AN97055.pdf Application Note 97055].

==Links==
* [http://mbouget.club.fr/i2c-faq.html Vincent Himpe I2C FAQ mirror]
* [http://www.nxp.com/acrobat_download/literature/9398/39340011.pdf I2C specification]
* [http://www.lm-sensors.org/wiki/man/i2cset I2C Linux test tools of Lm-Sensors]
* [http://codesink.org/eeprog.html eeprog, a tool to program I2C EEPROMs]
* http://www.stlinux.com/docs/manual/distribution/distribution_guide6.php

Target Software Installation

2009-06-05T16:11:45Z

JeanBaptisteM: Added internal link to flash memory map and allowed size for RootFS

==Configure U-Boot==

===Environment variables===
U-Boot can be customized in a flexible way with the use of "environment variables/scripts".
The command '''printenv''' shows you most of them and their current value:
<pre class="apf">
BIOS> printenv
bootcmd=run jffsboot
bootdelay=20
baudrate=115200
ethaddr=
autoload=no
...
</pre>
The command '''setenv''' is used to change these variables. For example, to set the IP address (don't do it yet):
<pre class="apf">
BIOS> setenv ipaddr 192.168.0.10
</pre>
The command '''saveenv''' is used to save the state of your environment variables in FLASH memory; that way they will be available at next boot:
<pre class="apf">
BIOS> saveenv
Saving Environment to Flash...
. done
Un-Protected 1 sectors
Erasing Flash...
. done
Erased 1 sectors
Writing to Flash... done
. done
Protected 1 sectors
</pre>

===Network configuration===
In order to use the U-Boot's network features, you have to set the network environment variables:
<pre class="apf">
BIOS> setenv netmask 255.255.255.0 (this default value should be fine in most situations)
BIOS> setenv ipaddr 192.168.0.10
BIOS> setenv serverip 192.168.0.2 (the IP address of your tftp server/PC hosting the files to download)
BIOS> setenv rootpath "/tftpboot/apf9328-root" (to boot Linux over NFS)
</pre>
You can use the '''dhcp''' command to configure these variables from your DHCP server. You probably will have to adjust the '''serverip''' variable manually.
<pre class="apf">
BIOS> dhcp
dm9000 i/o: 0x15c00000, id: 0x90000a46
MAC: 00:0e:32:00:00:01
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
</pre>
Do not forget to save your changes in FLASH, to have them available at next power up:
<pre class="apf">
BIOS> saveenv
</pre>
In case of troubles you can use the following U-Boot script to reset the variables to the "factory"/default settings:
<pre class="apf">
BIOS> run flash_reset_env
</pre>

==Linux kernel installation==

* check that your Armadeus kernel image size is smaller than the U-Boot partition (2MB with Armadeus 3):
<pre class="host">
[armadeus]$ ls -al buildroot/binaries/apf*/
</pre>
* if yes, copy it to your TFTP server directory (here ''/tftpboot/''); replace XX with your board name (apf9328 or apf27):
<pre class="host">
[armadeus]$ cp buildroot/binaries/apfXX/apfXX-linux.bin /tftpboot/
</pre>
* Load kernel image with U-Boot through network:
<pre class="apf">
BIOS> tftpboot ${loadaddr} apfXX-linux.bin
</pre>
or with the serial line:
<pre class="apf">
BIOS> loadb ${loadaddr}
''Ctrl+Altgr+\+c to access kermit command line then:''
(/home/.../) C-Kermit>send /tftpboot/apf9328-linux.bin
''After download is completed, you can type the c command to reconnect to the terminal:''
(/home/.../) C-Kermit>c
Connecting to /dev/ttyUSB0, speed 115200
Escape character: Ctrl-\ (ASCII 28, FS): enabled
Type the escape character followed by C to get back,
or followed by ? to see other options.
----------------------------------------------------
## Total Size = 0x0013d0b0 = 1298608 Bytes
## Start Addr = 0x08000000
BIOS>
</pre>

----
{{Warning|If the loaded kernel image is too large, the following operation can destroy data that are stored after the partition limits (e.g. RootFS)}}
Check that transfered size value is less than 2097152 (0x200000 hex) with armadeus 3
<pre class="apf">
Bytes transferred = 1313216 (1409c0 hex)
</pre>
----

* You can test your new kernel image without flashing it with; if so you will have to reload it again after test:
<pre class="apf">
BIOS> bootm ${loadaddr}
</pre>
* Flash kernel image with:
<pre class="apf">
BIOS> run flash_kernel
</pre>
* To make it easier, you can use automatic scripts that will download the image and flash it. So next time you will only launch:
<pre class="apf">
BIOS> run update_kernel
</pre>
* If you only want to try a new kernel without flashing the kernel image you can launch it directly from RAM:
<pre class="apf">
BIOS> setenv bootargs ${console} ${mtdparts}; run addjffsargs addipargs; bootm
(the kernel image you want to try must have been loaded at ${loadaddr})
</pre>

==rootfs installation==

* check that your Armadeus RootFS image size is smaller than the RootFS partition (see [[#Flash_memory_partitions|Flash Memory Partitions]] for size allowances):
<pre class="host">
[armadeus]$ ls -al buildroot/binaries/apf9328/
...
[armadeus]$ cp buildroot/binaries/apf9328/apf9328-rootfs.arm.jffs2 /tftpboot/
</pre>
* Load RootFS image with U-Boot through network:
<pre class="apf">
BIOS> tftpboot ${loadaddr} apf9328-rootfs.arm.jffs2
</pre>
or serial line:
<pre class="apf">
BIOS> loadb ${loadaddr}
Ctrl+Altgr+\+c to access kermit command line then...
send pathtoyourhostedbuildrootdir/rootfs.arm.jffs2
</pre>
then you can type the c command to reconnect to the terminal

* Flash RootFS image with:
<pre class="apf">
BIOS> run flash_rootfs
</pre>
* Now you should be ready to test Linux:
<pre class="apf">
BIOS> boot
</pre>
* To make it easier, you can use automatic scripts. So next time you will only launch:
<pre class="apf">
BIOS> run update_rootfs
</pre>

==FPGA firmware installation==

The FPGA firmwares are all located in the ''firmware/'' directory of your Armadeus view:
[armadeus]$ ls firmware/
apf_pkg BRAMTest bus_led led PS2 PS2_Opencore servo sram_test wishbone_example Xtools
You can make some trials with the ''firmware/PS2/ps2_top.bit'' file. 
 

{{Warning| Check that your bitfile size is smaller than the firmware partition size (256KB) before trying the following commands or you may corrupt your Linux kernel FLASH partition !!!}}

* Load FPGA firmware image file with U-Boot through: 
Ethernet:
<pre class="apf">
BIOS> tftpboot ${loadaddr} fpgafirmware.bit
</pre>
''fpgafirmware.bit'' is of course the name of your bitfile stored in your TFTP shared directory (''/tftpboot/'')

or serial line:
<pre class="apf">
BIOS> loadb ${loadaddr}
Ctrl+Altgr+\+c to access kermit command line then...
C-Kermit> send path_to_your_tftp/fpgafirmware.bit
</pre>
then you can type the c command to reconnect to the terminal

* Test your new FPGA firmware's downloading:
<pre class="apf">
BIOS> fpga load 0 ${loadaddr} ${firmware_len}
</pre>
* Flash your firmware image with:
<pre class="apf">
BIOS> run flash_firmware
</pre>
* When your are satisfied with your firmware you can make it "autoloaded" at power up:
<pre class="apf">
BIOS> setenv firmware_autoload 1
BIOS> saveenv
</pre>

==Update U-Boot==

There are two steps to update 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:
<pre class="apf">
BIOS> tftpboot ${loadaddr} apf9328-u-boot.bin
</pre>
With Ethernet and a NFS server:
<pre class="apf">
BIOS> nfs ${loadaddr} host_ip_addr:/nfs_path_to_buildroot/apf9328-u-boot.bin
</pre>
With the kermit and a serial line
<pre class="apf">
BIOS> loadb ${loadaddr}
<CTRL><ALT GR>\
c
send path_to_buildroot/apf9328-u-boot.bin
c
</pre>

===Transfer code from RAM to Flash memory===
There is a simple U-Boot command/script to do that:
<pre class="apf">
BIOS> run flash_uboot
</pre>

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

==Flash memory partitions==
===APF9328 Flash memory partitions===
{| border="1" cellpadding="5" cellspacing="0" summary="Signal connections"
|- style="background:#efefef;" align="center"
! width="40%" | Armadeus 2.x address range (index from FLASH physical @ 0x10000000) !! width="40%" | Armadeus 3 address range (index from FLASH physical @ 0x10000000) !! Type
|- align="center"
|0x000000 - 0x03FFFF ( 256KB )
|0x000000 - 0x03FFFF ( 256KB )
| U-Boot
|- align="center"
|0x040000 - 0x5FFFF ( 128KB )
|0x040000 - 0x5FFFF ( 128KB )
| U-Boot environment variables
|- align="center"
|0x060000 - 0x9FFFF ( 256KB )
|0x060000 - 0x9FFFF ( 256KB )
| FPGA bitfile
|- align="center"
|0x0A0000 - '''0x21FFFF ( 1.5MB )'''
|0x0A0000 - '''0x29FFFF ( 2MB )'''
| Linux kernel image
|- align="center"
|'''0x220000''' - End of FLASH ( ~6 MB or ~14MB )
|'''0x2A0000''' - End of FLASH ( ~5.5 MB or ~13.5MB )
| Root filesystem
|}
 

===APF27 Flash memory partitions===
{| border="1" cellpadding="5" cellspacing="0" summary="Signal connections"
|- style="background:#efefef;" align="center"
! width="80%" | NAND flash address range !! Type
|- align="center"
|0x00000000 - 0x0009FFFF ( 640KiB including NAND SPL and 384kiB spare memory for bad blocks)
| U-Boot
|- align="center"
|0x000A0000 - 0x000FFFFF ( 384kiB )
| U-Boot environment variables
|- align="center"
| 0x00100000 - 0x0017FFFF ( 512 kiB )
| FPGA bitfile
|- align="center"
| 0x00180000 - 0x0067FFFF ( 5 MiB )
| Linux kernel image
|- align="center"
| 0x00680000 - End of FLASH ( >~250MiB )
| Root filesystem
|}

FAQ

2007-04-06T17:24:23Z

JeanBaptisteM:

==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 symplicity and efficiency and our boards are as gifted to run embedded systems as Mozart was for composing music. Moreover, Armadeus project is 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 you 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 a more 'professionnal' webpage built to help founders find backing for the project (like device samples, board manufacturing). It is easier to obtain those with a this professionnal-looking webpage.

We have founded (litteraly) the association for our own pleasure and also to help universities and enthousiasts. Association bylaw protect members' intellectual property by forbidding any commercial use of the work done for the association.

The association works mostly on founders free time (we all work in embedded systems industry), which partly offsets the price of boards bought by members: 
- Initial costs were entirely founded by the founders, and are not matched in the boards selling price. 
- Tests, FPGA assembly and dispatching are made for no cost by volunteers. 
- Warranty and dead boards are not accounted for in the association until break-even. 

Those costs are not accounted for in boards selling price, mostly because the price would have been prohibitive and the project could not have started with such a high selling price. We do not want however to give all these for free to a 'for profit' project.

We have been quite surprised by the board success - and therefore believe that a company could have an interest in the design. Many alternatives could then be found then - even if it would be unlikely to occur in the short term: partnering with the association, separate (yet to create) licensing company...

==Hardware Questions==

===What does an Armadeus APF9328 board contain ?===
The heart of the APF9328 board is a i.MXL processor from Freescale (ex Motorola) with an ARM920T core running at 200MHz. It has the following integrated peripherals:
* LCD controller (TFT, CSTN, STN)
* USB 1.1 device
* 2 x SPI
* I2C
* 2 x Serial
* MMC/SD controller
* Serial bootstrap mode (removing the need of JTAG interface)
* a lot of General Purpose Input/Output, depending on the configured peripherals

Around this processor, the board is equipped with:
* 16MBytes of high speed SDRAM
* 8MBytes of NOR Flash
* 10/100Mbits Ethernet controller
* Xilinx Spartan3 FPGA (optional)
* an ADC and a DAC (optional)
* level converters for serial, USB and Ethernet
* 2 connectors for accessing main signals

Have a look at this link for more informations: [http://www.armadeus.com/downloads/apf9328/documentation/dataSheet_APF9328.pdf]

===What is the DevLight board ?===
APF9328 boards were designed to be as small as possible and ready to be embedded on any systems. So an APF9328 is not usable alone. You should see it much more like a module you can plug in everywhere.
To develop for APF9328 boards you can either develop your own "motherboard" and plug the APF9328 into it or use the one we develop for our needs.
Currently only the DevLight board is available. It contains:
* a serial connector
* an USB connector
* an Ethernet connector
* a prototype zone to test your developments
* a DC power regulator

For more informations look at here:
[http://www.armadeus.com/downloads/apf9328DevLight/documentation/dataSheet_APF9328_DevLight.pdf]

A DevFull board is currently in production and will contain:
* an AC97 + touchscreen chip
* 4 more serial ports
* a MMC connector
* ...

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

[[Image:FrenchFlag.png]][[Fr:FAQ | Cette page en Français]]

MemberList

2007-04-01T20:47:49Z

JeanBaptisteM:

==Here is the list of the members and their skills==

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

{|border=1 summary="Member list"
|----------------
| '''Name''' || '''Linux Apps'''|| '''Linux Drivers'''|| '''FPGA''' || '''Board Design''' || '''Projet/Domain'''
|----------------
|[[User:Salocin68|Nicolas Colombain]] || 1 || 1 || 1 || 2 || domotics
|----------------
|[[User:JulienB|Julien Boibessot]] || 2 || 2 || 0 || 1 || multimedia
|----------------
|[[User:JeanBaptisteM|Jean-Baptiste Mayer]] || 2 || 1 || 1 || 1 || robotics
|----------------
|}