ArmadeusWiki - User contributions [en]

Bugs

2006-09-19T11:32:12Z

217.128.254.186:

==This is a list of known bugs and others problems reported==

===If project is compiled twice then jffs2 generation of rootfs can fail===
'''workaround:''' do the compilation in a new shell.

===Ma carte ne marche pas===
Nico a du oublier de souder un composant, désolé ;-)

FAQ

2006-09-19T11:31:50Z

217.128.254.186:

==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 wolrd will run open source software, life will be better ;-)

===What is the legal status of the project ?===
The Armadeus Project is a french association (loi 1901) held in Mulhouse, France (68). We accept members from everywhere.
Board production is done by a privatly held company.

===How do I become a member ?===
You have to buy an Armadeus board. With this board you will receive userid and password to participate to this Wiki and project activities. Everyone is welcome.

===How do I get an Armadeus board ?===
Order it on http://www.armadeus.com.

===How do I get help ?===
First take a look at the whole Wiki. If you can't find help contact us directly. 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.

==Hardware Questions==

==Software Questions==

LCD

2006-09-19T11:31:27Z

217.128.254.186:

On this page, you will find all the informations needed to use LCD on Armadeus.

== Hardware interface ==

Two possibilities:
* LCD can be used with i.MX LCD controller -> direct connection to i.MX LCD pins (ex: [[MotLCD]] )
* LCD has a built-in controller with a parallel interface -> usage of i.MX LCD pins as GPIOs and emulation of a PC parallel port to reuse existing software
* ?? Should we support serial interface ?.

== Supported LCD / Software API ==
=== Which LCD controller are we going to support (for parallel port/GPIO interface) ===

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 informations, not very customizable for user GUI

Lcdproc ??
(Not tested)

Other idea ??

[[Category:Hardware]]

Trash Fr:MMC/SD

2006-09-19T11:30:55Z

217.128.254.186:

Comment connecter une MMC/SD à l'APF9328.<br>
Pour utiliser la MMC sous Linux, consultez la page [[MultiMediaCard]].

=== Carte d'adaptation ===
Vous devez connecter les signaux listés dans le tableau ci-dessous à votre carte APF9328DevLight.
Les signaux WP et CD_SW sont optionnels et doivent être connectés à des IOs libres si besoin.

Vu de dessus:
{|border=1 summary="Correspondance des signaux"
|----------------
|'''Adapter Pin''' || '''Desc''' || '''Adapter Pin''' || '''Desc'''
|----------------
|1 || +3.3V || 2 || SD_DAT2
|----------------
|3 || SD_CMD || 4 || SD_DAT3
|----------------
|5 || SD_CLK || 6 || SD_DAT0
|----------------
|7 || WP || 8 || SD_DAT1
|----------------
|9 || CD_SW || 10 || GND
|----------------
|}

Remarques:
* Pin 1 (pad rectangulaire)
* WP: Protection en écriture
* CD_SW: Interrupteur de détection carte

MMC/SD

2006-09-19T11:30:31Z

217.128.254.186:

How-To connect an MMC/SD to the APF9328

For instructions to use MMC on Linux, see [[MultiMediaCard]] page.

=== Adapter board ===
You need to connect the signals listed in the table below to the APF9328DevLight board.
The WP and CD_SW signals are optional and must be connected to free IOs if used.

Top view:
{|border=1 summary="Signal corresponding."
|----------------
|'''Adapter Pin''' || '''Desc''' || '''Adapter Pin''' || '''Desc'''
|----------------
|1 || +3.3V || 2 || SD_DAT2
|----------------
|3 || SD_CMD || 4 || SD_DAT3
|----------------
|5 || SD_CLK || 6 || SD_DAT0
|----------------
|7 || WP || 8 || SD_DAT1
|----------------
|9 || CD_SW || 10 || GND
|----------------
|}

Remarks:
* Pin 1 (rectangular pad)
* WP: write protect
* CD_SW: Card Detect switch

[[Fr:MMC/SD|Page en français]]
[[Category:Hardware]]

PS/2

2006-09-19T11:30:05Z

217.128.254.186:

==Instructions to connect a PS/2 keyboard to your Armadeus board==

===Introduction===

Your Armadeus board allows you to connect it a PC keyboard, by using the power of the Spartan3 FPGA (if present on your board).

===Hardware connection===

Connection of the PS/2 connector to the FPGA:
[[http://artemys25.free.fr/armadeus/images/PS2_Schema.png PS2_Schema.png]]
[[http://artemys25.free.fr/armadeus/images/PS2_FPGA.gif PS2_FPGA.gif]]

===Firmware installation===

Firmware for PS/2 is avaiblable in your SVN repository: software/firmware/PS2/ps2_top.bin.<br>
Copy it to your TFTP directory and follow the procedure here: [[InstallTargetSoftware#FPGA_firmware_installation|Firmware installation]]

===Memory Map===

The core uses the following register map:
{|border=1
|----------------
|Address|| Name || Description
|----------------
|0x12000000 || Status register ||The following bits are used: 0x2 => empty, 0x8=>full, the other bits can be ignored (not used or for debug purposes)
|----------------
|0x12000002 || Data read register ||The keyboard scancodes can be read from this register. After each access, the next byte from the fifo appears here
|----------------
|0x12000004 || Test register || (has nothing to do with the PS2 interface, just for fun) The lower 8 bit behave like a normal RAM
|----------------
|0x12000006 || Test register || (has nothing to do with the PS2 interface, just for fun) The lower 8 bit behave like a normal RAM
|----------------
|0x12000008 || Test register || (has nothing to do with the PS2 interface, just for fun) The value is always 0x1234, write is ignored
|}

===BUGS===

Status register start with value 0x000A -> Fifo Full + Fifo Empty normal ??

===Links===

* http://www.barcodeman.com/altek/mule/scandoc.php
* http://www.rennes.supelec.fr/ren/fi/elec/docs/mouse_ps2/souris_ps2.htm
* http://www.computer-engineering.org/ps2protocol/

[[Category:Hardware]]

Hardware

2006-09-19T11:29:48Z

217.128.254.186:

Hardware Add-Ons (Page bricolage :-))

* IRReceiver
* [[LCD]]: How to connect LCD (graphic & text) to your board
* [[PS/2]]: How to connect PS/2 devices to your board
* [[MMC/SD]]: How to connect MMC/SD devices to your board
* Step motor controler
* TV Output
* Compact Flash slot

Hardware

2006-09-19T11:29:23Z

217.128.254.186:

Hardware Add-Ons (Page bricolage :-))

* IRReceiver
* [[LCD]]: How to connect LCD (graphic & text) to your board
* [[PS2]]: How to connect PS/2 devices to your board
* [[MMC/SD]]: How to connect MMC/SD devices to your board
* Step motor controler
* TV Output
* Compact Flash slot

LCD4linux

2006-09-19T11:28:31Z

217.128.254.186:

On this page, you will find all the informations needed to compile, install & use LCD4linux on Armadeus board.

== Compilation & installation ==

Manually:
Go in software/target/package/lcd4linux directory and update your local SVN repository:
svn update
Then, compile the beast:
make lcd4linux
This will install 2 files in your /local/export/: lcd4linux executable and lcd4linux.conf
Launch your target, mount NFS and copy lcd4linux in /usr/bin of you target and lcd4linux.conf in /etc
Change acces rights for lcd4linux.conf:
# chmod 600 /etc/lcd4linux.conf

Automatically:
in buidlroot do a:
make menuconfig
and in package selection, choose LCD4Linux.
Relaunch buildroot compilation and install generated rootfs on your target.

== Usage ==

* LCD4linux needs GPIO & // port emulation drivers to be loaded first. So, please refer to [[GPIO Driver]] page (you need to have gpio.ko & ppdev.ko modules loaded).
Be sure to have a /dev/parport/0 node. (automatically created when your run loadgpio.sh script)
* a configuration file (/etc/lcd4linux) is also needed to configure layout and widget, so if you want to change these parameters, this is the place to look at
* LCD4linux is then easily launched:
# /usr/bin/lcd4linux
It automatically daemonizes itself.

== Links ==

http://ssl.bulix.org/projects/lcd4linux/

MotLCD

2006-09-19T11:28:08Z

217.128.254.186:

Tips to connect the Mot LCD to the APM dev Board

== LCD Adapt schematics ==
The schematics of the LCD adapt board have been placed under SVN and can be found here:
svn://ericjarrige.homelinux.org/armadeus/trunk/hardware/LCD_ADAPT_MOT/schema.pdf

== Connections ==
Just connect signals with same names together, excepted for the following ones:

{|border=1 summary="Signal corresponding."
|----------------
|'''LCD Adapt board''' || '''APM dev board'''
|----------------
|TB_RL || GND
|----------------
|CM || GND
|----------------
|MCLK || LSCLK
|----------------
|OE || OE_ACD
|----------------
|HSYNC || LP_HSYNC
|----------------
|VSYNC || FLM_VSYNC
|----------------
|SD || CONTRAST with 1k pullup to 3.3V
|----------------
|And due to an error on first print of the adapter board, connect:
|----------------
|B4 || B4
|----------------
|B3 || B0
|----------------
|B2 || B1
|----------------
|B1 || B2
|----------------
|B0 || B3
|}

As the fine pitch connector of the LCD is symetrical, take care when connecting the LCD to the Adapt board !!.
The LCD must be placed over the DC/DC converter (not mounted):
[[http://artemys25.free.fr/armadeus/images/dsc01081.jpg MotoLCD.jpg]] (!! don't forget to isolate the back of the LCD, with some rubber for ex. !!)
The Berg connector is reference to P2 and the dine pitch is P1 in the schematics.

The DC/DC converter is not yet tested so you will need a ~12V supply for the LCD backlight.... this is why you have a separate cable on the LCD adapt. This 12V supply can be the same as the one used for the APM dev board.

Hardware

2006-09-19T11:27:38Z

217.128.254.186:

Applications

2006-09-19T11:26:52Z

217.128.254.186:

On this page, we will try to summarize all the applications your Armadeus board can be usefull for.

{| cellspacing=5 cellpadding=5 border=1 width=100%
{{IconLink|Entertainment|Entertainment|game.png|Develop the next gaming platform or the best MP3 player ever}}
{{IconLink|Robotic|Robotic|robot.png|Give your robots, the brain they deserve}}
|-
{{IconLink|Domotic|Domotic|domotic.png|Control everything in your house, from a web browser}}
{{IconLink|Electronic|Electronic|hard.png|Create usefull electronic devt devices like oscilloscops or data acquisition}}
|-
{{IconLink|Environment|Environment|faq.png|Save the world by building your own intelligent & green power sources}}
{{IconLink|Medical|Medical|medic.png|Develop medical devices for every day life}}
|}

Linux Debug

2006-09-19T11:25:57Z

217.128.254.186:

** Tips to do debug under linux **

===Introduction===

On this page, you will find usefull informations for debugging Armadeus under Linux

===Testing Linux kernel===

You can test a linux kernel you've generated without to have to reflash your board and destroy your currently working image.
Indeed Linux kernel images can be loaded and started from RAM:
BIOS> tftpboot 0x08800000 linux-kernel-2.6.16-arm.bin
BIOS> bootm 0x08800000

===imxregs===

This tool allows you to access iMX registers from linux userspace/console. This way you debug your driver or access iMX hardware functionnalities
directly from Linux console.

First, you have to go in software/target/linux/debug/imxregs/ directory and build the tool:
$ make clean
$ make
$ cp imxregs /your/nfs/shared/dir/

To use it, you must clear PAR 1&2 registers (register access rights) before launching Linux kernel, so in U-Boot type:
BIOS> mw.l 0x00200008 0
BIOS> mw.l 0x00210008 0

Then in linux, launch it like that:
# imxregs REGISTER_NAME (give it the register name as printed in iMX Ref Manual or just the begining of the name)
or
# imxregs (to dump all supported registers)

====Examples:====
Show OCR1 registers of each GPIO Port:
# imxregs OCR1

===TBDL===

===Links===
http://www.armadeus.com

Qt/Embedded

2006-09-19T11:25:38Z

217.128.254.186:

Instructions to install and use QtEmbedded & Opie for Armadeus

== Introduction ==

This page will summarize the process to build, install and use QtEmbedded & Opie. Qtopia may be supported in a second phase.
You will also find instructions to setup a Host development environment for simulating applications before deploying them on the target.

== Installation ==
Update your armadeus SVN snapshot:
# cd armadeus/
# svn update
be sure to get Qt patch in software/patches
Activate Qt in buildrot
# make menuconfig
go in Toolchain options and be sure to activate c++ compiler generation
go in Package Selection for the target --> and select Qt/Embedded GPL package
- select Qvfb if you want to have a host simulation environment
- select Opie if you want to have a full PDA distribution for your board (not functionnal yet)
then save your config and launch compiling:
# make

after compilation ends, reflash rootfs or copy libraries on your target
Copy software/buildroot/package/qte_gpl/set_qt_env.sh script to your Armadeus filessytem in /etc. Edit this file to change QTDIR if not appropriate.
to be functionnal, you should copy fonts/ directory of your "build_arm_nofpu/qt_gpl/qt_2.3.10/lib/fonts" with the fonts you want to use

I'm currently preparing stuff to make these steps automatics...
Don't forget to read build_arm_nofpu/qt_gpl/qt_2.3.10/lib/doc/html/install-qws.html for more informations and feel free to update this page !!

only Qt is working yet, opie is coming soon.
In progress... ask Juju if you want to test buildroot Makefile

== Usage ==

by default Qt is installed in /usr/lib/ directory of your target rootfs
before launching Qt on the target, you should set following env variables to the right value: QTDIR, LD_LIBRARY_PATH, etc...
You can do it automatically by sourcing the /etc/set_qt_env.sh script if you have modified it during installation.
# . /etc/set_qt_env.sh

Test the beast:
Compile hello example (!! tricky) and copy it to your rootfs
Launch it:
# /usr/bin/hello -qws

== Qvfb ==

Qvfb (Qt Virtual Framebuffer) is a framebuffer emulator for your host/devt system.
With it you can simulate your target and run your Qt/E programs on your PC before deploying them to your Armadeus board.
To use it:
- copy software/buildroot/package/qte_gpl/set_qt_env.sh script to yur home directory and edit it to have the right QTDIR path (for example: software/buildroot/build_arm_nofpu/qt_gpl/qt-2.3.10-x86/ )
- source it:
# source /home/julien/set_qt_env.sh
- go in software/buildroot/build_arm_nofpu/qt_gpl/qt-2.3.10-x86/ and launch Qvfb:
# qvfb -width 240 -height 320 &
- then go in examples and launch the program you want to test
# cd examples/hello/
# make
# ./hello -qws
Working examples with current configuration (Opie) are: buttongroups, cursor, customlayout, drawlines, forever, layout, life, lineedits, listbox, listcombobox, menu, popup, rot13, tetris, tictac

Cool ! no ? ;-)

== Qtopia ==

! Not tested/supported yet !
Go here: [[http://www.trolltech.com/forms/unsupportedeval.html]] and ask for a free licence

== Work in progress / to do list ==

* Customisation of src/tools/config-qpe.h to have a custom Qt/E library well designed for Armadeus usage (currently we are using Opie's config
* Creating support for a new device for compilation customization, cf qt-2.3.10/doc/html/install-qws.html (currenlty arm examples are not compiling automatically)

== Links ==

* http://www.trolltech.com

Development

2006-09-19T11:25:02Z

217.128.254.186:

On this page you will find usefull informations to develop software for your Armadeus board

* [[Cross Compiler|C/C++ Cross Compiler]] installation
* [[Qt/Embedded]] & Co
* [[Linux Debug]]: Tips to debug under Linux
* [[Drivers|Linux drivers development]]
* [[Perl|Perl development]]
* [[Python|Python development]]
* [[FPGA|FPGA firmware development]]

DAC

2006-09-19T11:23:04Z

217.128.254.186:

The DAC '''max5821L''' can be controlled from the user space by using the setDAC function

The Linux kernel configuration must enable the necessary I2C drivers (modules):

* -> I2C support
* -> I2C support -> I2C device interface
* -> I2C support -> I2C Hardware Bus support -> I2C bus on i.MX

You must enable the '''max5821ctrl''' package into your buildroot configuration:<br>
Board support Options->Board support for the Armadeus development boards->armadeus packages

If you are using modules instead linux drivers,
you can check if the modules are loaded with:
# lsmod
i2c_imx 4008 0
i2c_dev 5024 0
i2c_core 11472 2 i2c_imx,i2c_dev

to set the DAC use the '''setDAC''' command:
# setDAC

##Usage: setDAC OUTPUT [VALUE]
power down or set DAC output with value 0 - 1023

OUTPUT is A , B or AB (both)
VALUE must be 0 - 1023

If no VALUE is given, then the output is powered down
##

Do not forget to connect a voltage reference for the DAC

MultiMediaCard

2006-09-19T11:22:40Z

217.128.254.186:

Instructions to use the MultiMediaCard (MMC/SD) on your Armadeus board

==Introduction==

You can use standard MMC/SD cards with your Armadeus board, if you have the corresponding connector attached to your devt board.
See [[MMC/SD]] page to know how to connect the hardware part.

==Installation==

when you build your kernel image, then modify your configuration:
[user@toto]$ make xconfig
in Device Drivers->MMC/SD Card support->iMX Support
In FileSystems, don't forgt to add support for the filesystem on the MMC and if you activate FAT/VFAT, don't forget to activate Native Language Support (NLS)
otherwise you'll get errors like:
Unable to load NLS charset cp437
FAT: codepage cp437 not found

Save your configuration and then rebuild your kernel image:
[user@toto]$ make
now you should have following drivers in your kernel source tree:
drivers/mmc/
Copy '''mmc_core.ko''', '''imxmmc.ko''' & '''mmc_block.ko''' to your target root filessytem in '''/lib/modules/''' or reflash the generated rootfs.

If not already existing then create MMC block devices:
# mknod /dev/mmca b 254 0
# mknod /dev/mmca1 b 254 1
If not already existing then create the mount point (/mnt/mmc):
# mkdir -p /mnt/mmc

==Usage==

First, load the core controller driver on your board:
# insmod /lib/modules/mmc_core.ko
and then the iMX MMC Host driver:
# insmod /lib/modules/imxmmc.ko
To access the MMC as a block device, load this module too:
# insmod /lib/modules/mmc_block.ko
Then just mount the MMC, for example (FAT32 formatted card):
# mount -t vfat /dev/mmca1 /mnt/mmc
You can then access the MMC's files from /mnt/mmc directory

==TBDL==

==Links==

* http://www.linux-usb.org/gadget/

USB Gadget

2006-09-19T11:22:19Z

217.128.254.186:

Instructions to use the USB port of your Armadeus board to communicate with your PC

==Introduction==

You can connect your Armadeus board to a PC using its USB port and it can be enumerated as many USB devices (depending on the type of communication way you want to use):
* serial device
* net device
* mass storage device

==Installation==

when you build your kernel image, then modify your configuration:
[user@toto]$ make xconfig
in Device Drivers->USB support->USB Gadget Support, choose Support for USB Gadgets and activate all USB Gadget Drivers
Save your configuration and then rebuild your kernel image:
[user@toto]$ make
now you should have following drivers in your kernel source tree:
'''drivers/usb/gadget/gadgetfs.ko''' For test
'''drivers/usb/gadget/g_ether.ko''' Ethernet emulation on USB
'''drivers/usb/gadget/g_file_storage.ko''' Mass storage
'''drivers/usb/gadget/g_serial.ko''' Serial emulation on USB
'''drivers/usb/gadget/g_zero.ko''' For test
'''drivers/usb/gadget/imx_udc.ko''' i.MX USB device Core Controller

Copy imx_udc.ko, g_file_storage.ko & g_serial.ko to your target root filessytem in /lib/modules/

==Usage==

First, load the core controller driver on your board:
# insmod /lib/modules/imx_udc.ko

===To emulate a mass storage device:===
* create or get a "backing storage file", for example: [[http://artemys25.free.fr/armadeus/binaires/backing_file.gz]]
* copy this file (uncompressed) in the '''/tmp''' directory of your rootfs (see NetworkConfig if necessary)
* load g_file_storage module:
# insmod /lib/modules/g_file_storage.ko file=/tmp/backing_file
* connect target's USB cable to your PC and,
On Linux:
* as root, launch dmesg and find the /dev/sdaX device assigned to your board
* then mount the device and enjoy file sharing:
[root@toto]# mount /dev/sda1 /mnt/tmp
[root@toto]# cd /mnt/tmp
[root@toto]# showimage /mnt/tmp/test.jpg

===To emulate a serial port:===
# mknod /dev/ttygserial c 127 0 (only needed the first time you want to use it, if not already existing)
# insmod /lib/modules/g_serial.ko

==TBDL==

==Links==

* http://www.linux-usb.org/gadget/
* http://www.linux-usb.org/gadget/file_storage.html

Serial Transfer

2006-09-19T11:21:51Z

217.128.254.186:

Instructions to use the serial port of your Armadeus board to communicate with your PC

==Introduction==

When you only have a serial port to connect to your devt PC, then you can use Zmodem protocol to send/receive files to/from your Armadeus board

==Installation==

when you build your root filessytem with buildroot, then modify your configuration:
[user@toto]$ make menuconfig
to add lrzsz package and then rebuild your rootfs
[user@toto]$ make
Check that lrz and lsz executable are present in your rootfs and if not copy them to there:
[user@toto]$ cp ./build_arm_nofpu/lrzsz-0.12.20/src/lsz ./build_arm_nofpu/root/usr/bin/
end then rebuild your rootfs
[user@toto]$ make

==Usage==

You must use minicom as serial terminal and not kermit sorry ! :-(
After having booted your Armadeus system, launch lrz for receiving and lsz to send files:

Host --> Target
# cd /whereToPutTheFile/
# lrz -bZ
then in minicom Ctrl+A then s and choose zmodem protocol and the file to send
Wait a little and your file will be copied to your board rootfs ! ;-)

Target --> Host
# lsz -b --zmodem filename

==TBDL==

==Links==

* http://www.ohse.de/uwe/software/lrzsz.html

Network File System configuration

2006-09-19T11:21:31Z

217.128.254.186:

==Introduction==

On this page, you will find usefull informations to configure your Host or Target network

==Host NFS server==

On Linux (&Mac?) NFS is part of your distribution so you normally don't need to install it.
The only thing you have to do is to configure the directory you want others access from the network.
For that you have to modify the /etc/exports file (for example):
# Directory for Armadeus:
/local/export 192.168.0.0/255.255.0.0(ro,no_root_squash,sync)
(In that case your Host will authorize all client from the subnet 192.168.*.* to access /local/export in read only mode)

Then restart your NFS server:
# /sbin/service nfs restart

Next time you boot, you can check your NFS server status with:
# /sbin/service nfs status
and if not started then:
# /sbin/service nfs start

==On your Armadeus target:==

- create a mount point (for example):
# mkdir -p /mnt/host
- mount it (for example):
# mount -t nfs 192.168.0.2:/local/export /mnt/host
192.168.0.2 is your Host IP address and /local/export the name of your Host directory you want to mount.

==Troubleshooting:==

1] If nfsd and mountd daemon are not running on your Host, then you will get a message like:
# mount: RPC: Program not registered
In that case, restart the NFS service on your Host (see above)
2] To successfully mount a NFS drive, portmap daemon should be running on your target, if not system will hang during some minutes when you launch the mount !!
To check if portmap is running, look at the running processes:
# ps faux
If portmap is not listed, then launch it manually:
# /etc/init.d/S14portmap

==TFTP Server under Windows:==

For those who want to transfer some files from Windows (kernel image / root fs), a small and FREE tftp server is available here:
http://tftpd32.jounin.net/

==Links==

* http://www.denx.de/wiki/view/DULG/SystemSetup#Section_4.8.

[[Fr:Configuration Réseau|Page en français]]

GPIO Driver

2006-09-19T11:21:05Z

217.128.254.186:

On this page, you will find all the informations needed to use the Armadeus GPIO driver.

== Module compilation & installation==
The first thing you have to do is to compile the driver. The only way to do that actually is to compile it as a module:
# cd driver_directory
Be sure to have ARMADEUS_KERNEL_DIR environment variable defined. If not:
# export ARMADEUS_KERNEL_DIR=/local/julien/Armadeus/Armadeus_SVN_test/armadeus/software/buildroot/build_arm_nofpu/linux-2.6.12/ (for example)
Compile it:
# make ARCH=arm CROSS_COMPILE=/local/julien/Armadeus/Armadeus_SVN_test/armadeus/software/buildroot/build_arm_nofpu/staging_dir/bin/arm-linux-

When compiled, you will obtain 3 modules:
* gpio.ko: this is the main driver. It should be loaded first and will allow you to easily control gpio pin from user space.
* ppdev.ko: this is an extension driver to add PPDEV emulation. This way you will be able to emulate a standard parallel port on one GPIO port (and then for example connect a LCD)
* loadfpga.ko: this is an extension driver to add the possibility to load the fpga on APF boards from linux userspace -> fpga reprogrammation after linux boot.

Then, you have to:
* copy these modules on your rootfs in /lib/modules/to_be_defined/
* copy loadgpio.sh script on your rootfs in /etc/
After that you can launch:
# sh /etc/loadgpio.sh
or look inside this script if you want to manually enter the module parameters
# insmod /lib/modules/2.6.10-imx/drivers/gpio.ko portB_init=0,0,0x00FFFF00,0,0,0,0,0,0x0FF00000,0,0,0,0,0,0,0x0FF00000
gpio .ko module parameters are values for PORTA, PORTB, PORTC, PORTD configuration registers in following order:
DDIR, OCR1, OCR2, ICONFA1, ICONFA2, ICONFB1, ICONFB2, DR, GIUS, SSR, ICR1, ICR2, IMR, GPR, SWR, PUEN,

== Driver usage ==
GPIO driver is usable through 2 interfaces:
* use /proc/drivers/gpio/portXdir to read (cat) or write (echo) pin direction
* use /proc/drivers/gpio/portX to read (cat) or write (echo) pin status

Examples:
See which IO-Pins of PortD are configured as inputs, and which are outputs ('1' = output, '0' = input):
# cat /proc/driver/gpio/portDdir##

Configure the IO-Pins 30, 28, 23, 22 and 21 of PortB as outputs, all others are inputs:
# echo 01010000111000000000000000000000 >/proc/driver/gpio/portBdir

Read the status of the IOs of PortB:
# cat /proc/driver/gpio/portB

Set bits 30, 28 and 23 of PortB to '1', all other outputs to '0':
# echo 01010000100000000000000000000000 > /proc/driver/gpio/portB

== Links ==
* http://soekris.hejl.de/
* http://people.redhat.com/twaugh/parport/html/ppdev.html

Framebuffer

2006-09-19T11:20:30Z

217.128.254.186:

== Armadeus Framebuffer documentation page ! ==

Here is the procedure to have a working framebuffer on the board (beware
it's tricky for the moment !!, but it's for people who can't wait ;-))

* comment lines number 427 & 438 in linux/drivers/video/imxfb.c (PD11,PD12 config)
* merge attached scb9328.c file with linux/arc/arm/mach-imx/scb9328.c

configure the linux kernel for Framebuffer support:
<pre>
make menuconfig
</pre>
* in "Char Devices" menu, activate ''"Virtual Terminal"'' and ''"Support for virtual terminal on console"''
* in "Graphic support" activate "Support for Framebuffer", "Motorola iMX
LCD support" "Console display driver support ->Frame buffer console
support" (deactivate VGA stuff & add some fonts), then choose 224 colour
boot logo

recompile the kernel, now to have console on serial port, you will have
to add "console=ttySMX0,115200n8" to your boot parameters

load image on your board and enjoy (you should see linux logo on screen
at startup)!

If you have devfs activated, framebuffer device can be accessed with /dev/fb/0. Otherwise, you will neede to create the device node with
<pre>
mknod c 29 0
</pre>

You can activate some test tools from the armadeus build process:
<pre>
make menuconfig -> packages -> fbset
</pre>

You have several test tools on yahoo groups to play a little with the framebuffer.

[[Category:Documentation]]

BootStrap

2006-09-19T11:19:54Z

217.128.254.186:

==Instructions to use the Armadeus Bootstrap utility==

===Introduction===

Bootstrap utility is a Perl piece of code that allows you to interactivly communicate with the iMX processor while in bootstrap mode.
To enter bootstrap mode, you have to put bootstrap jumper and restart your Armadeus board.

===Launch===

Go inside the boostrap folder and launch
sh runBootstrap.sh if you're on Linux or
runBootstrap.bat if you're on Window$

Boostrap tool will then try to synchronize with iMX:
<pre>
Initializing serial port to 19200 bps
Re-synchronizing...
Please reset your board in bootstrap mode !
Please reset your board in bootstrap mode !
Please reset your board in bootstrap mode !
Please reset your board in bootstrap mode !
</pre>
When you see that message reset your board.

if nothing happens, verify your bootstrp jumper is put and try to reset your board.
At last check you serial port device is the right one.

===Usage===

Fisrt thing to do when entering bootstrap is initializing your SDRAM controller if you want to use it:
<pre>
initSDRAM 32
</pre>

Then you can for example flash u-boot with:
<pre>
loadFLASHbin u-boot.bin 10000000
</pre>

To have a list of all the functionnalities, try:
<pre>
help
</pre>

===Links===

http://www.armadeus.com

BootLoader

2006-09-19T11:18:50Z

217.128.254.186:

==Introduction==

This page describe the U-Boot installation/usage in the Armadeus context.

==Build U-Boot==
Build process is now part of the Armadeus package.
The process is automated in the global build process (see Install Armadeus software),
So the following information is only usefull for a manual build process:

* Download Das U-Boot source code archive from: http://sourceforge.net/project/showfiles.php?group_id=65938
* Uncompress it:
tar jxvf u-boot-1.1.3.tar.bz2
* Download Armadeus patches corresponding to your u-boot & gcc version from: http://fr.groups.yahoo.com/group/armadeus/files/Patches/ and copy it to the u-boot directory.
* Go inside the u-boot directory and apply the patches:
patch -p1 < u-boot1.1.3-apm9328-2.1.patch
patch -p1 < u-boot1.1-gcc3.4.patch (if necessary)

If you have a 8 or 16MB apm9328 board, edit the include/configs/apm9328.h.
look for a #define SDRAM_xxxMBIT
change it to a:

* #define SDRAM_64MBIT /* for 8MB */
* #define SDRAM_128MBIT /* for 16MB */
* #define SDRAM_256MBIT /* for 32MB */

Then build u-boot:
make apm9328_config
make
this produce a u-boot.bin and a u-boot.brec file:
* '''u-boot.bin''' is a binary image file and can be downloaded with the u-boot loadb command (or tftpboot, nfs,...)
* '''u-boot-brec''' is a boostrap record file compatible with the freescale bootloader. Use the kermit transmit command.

==Install or restore from scratch==

If your Armadeus board doesn't boot anymore (flash content erased or dammaged), you will have to use the bootstrap mode of the i.MX.
Use the jumper to boot the integrated freescale bootstrap.
check your host .kermrc file and add the following line:
set transmit linefeed on
Then connect to the apm9328:
kermit
c
Synchronize baudrate with the 'A' key until you receive the character ':' then press return to validate the synchronization.
Go back to command mode:
<CTRL><ALT GR>\
c
Then transmit the u-boot.brec file:
transmit armadeus_path/software/buildroot/u-boot.brec
This process can take a couple of minutes.
U-boot is now running in RAM. make a new connection to check you have prompt:
BIOS>
You can burn u-boot in flash memory. see Update u-boot hereafter.
Then remove the jumper to use u-boot at the next power-up.

For faster restoring you can use [[BootStrap]] utility too.

==Update U-Boot==

There are two steps to update u-boot:
*1] Load the new u-boot code in RAM
You can use the following commands to download U-boot.
With ethernet and a tftpboot server:
tftpboot 08000000 /tftpboot_path_to_buildroot/u-boot.bin
With ethernet and a nfs server:
nfs 08000000 host_ip_addr:/nfs_path_to_buildroot/u-boot.bin
With the kermit and a serial line
loadb
<CTRL><ALT GR>\
c
send path_to_buildroot/u_boot.bin
c

*2] Transfer code from RAM to Flash memory
There is a simple u-boot command/script to do that:
run flash_uboot

==Modify your environment variables==

There is a set of variables you can customize to your needs.
The commande '''printenv''' show you most of them and their current state.
Use the command '''setenv''' to change one of these variable.
For instance:
setenv ipaddr 192.168.0.3
Use the command '''saveenv''' to save the state of your environment variables in flash memory.

==Customize the flash memory organization==

==Booting Linux==

The Install Armadeus software on target provide some information to install linux on Armadeus board

==Customize Linux boot mode==

==Typical Kermit (.kermrc) config file==
<pre>
set line /dev/ttyS0
set speed 115200
set carrier-watch off
set handshake none
set flow-control none
robust
set file type bin
set file name lit
set rec pack 1000
set send pack 1000
set window 5
set transmit linefeed on
</pre>

==Links==
* http://www.denx.de/wiki/DULG/Manual

Linux start screenshot

2006-09-19T11:17:31Z

217.128.254.186:

==Screenshot showing the serial text console during boot:==

U-Boot 1.1.3 (Jan 8 2006 - 16:00:26) apm9328 patch 2.2

U-Boot code: 0BF80000 -> 0BFA2264 BSS: -> 0BFA7014
RAM Configuration:
Bank #0: 08000000 32 MB
Flash: 16 MB
In: serial
Out: serial
Err: serial
BIOS> boot
""##"" Booting image at 100a0000 ...
Image Name: Linux-2.6.12
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 1028824 Bytes = 1004.7 kB
Load Address: 08008000
Entry Point: 08008000
Verifying Checksum ... OK
OK

Starting kernel ...

Uncompressing Linux.................................................................... done, booting the kernel.
Linux version 2.6.12 (eric@supin) (gcc version 3.4.3) #2 Fri Jan 27 21:14:03 CET 2006
CPU: ARM920Tid(wb) [41129200] revision 0 (ARMv4T)
CPU0: D VIVT write-back cache
CPU0: I cache: 16384 bytes, associativity 64, 32 byte lines, 8 sets
CPU0: D cache: 16384 bytes, associativity 64, 32 byte lines, 8 sets
Machine: Synertronixx scb9328
Memory policy: ECC disabled, Data cache writeback
Built 1 zonelists
Kernel command line: console=ttySMX0,115200n8 mtdparts=scb9328_flash:256k(U-boot)ro,128k(U-boot_env),256k(firmware),1m(kernel),6m(root),-(fs) root=/dev/mtdblock4 rootfstype=jffs2 ip=192.168.000.2:192.168.000.1:192.168.000.1:255.255.255.0:apm9328dev::off
PID hash table entries: 256 (order: 8, 4096 bytes)
Console: colour dummy device 80x30
Dentry cache hash table entries: 8192 (order: 3, 32768 bytes)
Inode-cache hash table entries: 4096 (order: 2, 16384 bytes)
Memory: 32MB = 32MB total
Memory: 30208KB available (1884K code, 214K data, 96K init)
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
NET: Registered protocol family 16
JFFS2 version 2.2. (C) 2001-2003 Red Hat, Inc.
Initializing Cryptographic API
i.MX Framebuffer driver
Console: switching to colour frame buffer device 30x40
apf9328_lcd_power: 1
Serial: IMX driver
ttySMX0 at MMIO 0xe0006000 (irq = 30) is a IMX
ttySMX1 at MMIO 0xe0007000 (irq = 24) is a IMX
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered
RAMDISK driver initialized: 1 RAM disks of 4096K size 1024 blocksize
dm9000 Ethernet Driver
eth0: dm9000 at edc3fffc,edc40000 IRQ 110 MAC: 00:0e:32:00:00:01
Probing scb9328_flash at physical address 0x10000000 (16-bit buswidth)
scb9328_flash: Found 1 x16 devices at 0x0 in 16-bit bank
Intel/Sharp Extended Query Table at 0x0031
Using buffer write method
cfi_cmdset_0001: Erase suspend on write enabled
6 cmdlinepart partitions found on MTD device scb9328_flash
Creating 6 MTD partitions on "scb9328_flash":
0x00000000-0x00040000 : "U-boot"
0x00040000-0x00060000 : "U-boot_env"
0x00060000-0x000a0000 : "firmware"
0x000a0000-0x001a0000 : "kernel"
0x001a0000-0x007a0000 : "root"
0x007a0000-0x01000000 : "fs"
mice: PS/2 mouse device common for all mice
NET: Registered protocol family 2
IP: routing cache hash table of 512 buckets, 4Kbytes
TCP established hash table entries: 2048 (order: 2, 16384 bytes)
TCP bind hash table entries: 2048 (order: 1, 8192 bytes)
TCP: Hash tables configured (established 2048 bind 2048)
NET: Registered protocol family 1
NET: Registered protocol family 17
eth0: link down
IP-Config: Complete:
device=eth0, addr=192.168.000.2, mask=255.255.255.0, gw=192.168.100.1,
host=apm9328dev, domain=, nis-domain=(none),
bootserver=192.168.200.1, rootserver=192.168.200.1, rootpath=
VFS: Mounted root (jffs2 filesystem).
Freeing init memory: 96K
Starting portmap daemon: portmap.
eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
Initializing random number generator... done.
Starting network...
Starting sshd: OK

Welcome to the Armadeus project.

armadeus login: root

""BusyBox"" v1.01 (2006.01.27-18:50+0000) Built-in shell (ash)
Enter 'help' for a list of built-in commands.

#