ArmadeusWiki - User contributions [en]

Armadeus 3

2022-06-30T12:12:18Z

FabienM: /* How-to obtain the Armadeus 3 */

This page will help you use the Armadeus 3.x 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.x 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 gitlab repository: https://gitlab.com/armadeus/armadeus-bsp/-/tags/release-3.4 or by download: https://gitlab.com/armadeus/armadeus-bsp/-/archive/release-3.4/armadeus-bsp-release-3.4.tar.gz

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@gitlab.com:armadeus/armadeus-bsp.git 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): Download tar.gz at https://gitlab.com/armadeus/armadeus-bsp/-/tags/release-2.x

==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 System configuration ---> 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 Filesystem images --> 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 Bootloaders --> 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 commands:
<pre class="host">
$ make linux-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 linux
$ 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 linux-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]]

Template:ArmadeusNews

2022-06-30T12:06:56Z

FabienM: Undo revision 15106 by FabienM (talk)

__NOTOC__

=====June 30th, 2022: Gitlab is now official repository for armadeus bsp =====
<noinclude>
Gitlab is now official repository for armadeus bsp : https://gitlab.com/armadeus/armadeus-bsp
</noinclude>

=====August 7th, 2018: New software release [[Releases#Release_7.0_.28latest_stable_one.29|Armadeus 7.0]]=====
<noinclude>
This new [[Releases#Release_7.0_.28latest_stable_one.29| release]] introduces the support for the new [[OPOS6UL]] & [[OPOS6UL_NANO]] SoM and concludes the move to Buildroot 2017.02.</noinclude>

=====August 11th, 2015: New software release [[Releases#Release_6.0_.28latest_stable_one.29|Armadeus 6.0]]=====
<noinclude>
This new [[Releases#Release_6.0_.28latest_stable_one.29| release]] introduces the support for the new [[APF6]] & [[APF6_SP]] Armadeus modules and concludes the move to Buildroot 2015.02 and U-Boot 2014.07+. It also consolidates the support for vanilla Linux kernels (3.19+).</noinclude>

=====June 17th, 2014: Bump to [[U-Boot-2014.04| U-Boot 2014.04]]=====
<noinclude>
All Armadeus boards moved to [[U-Boot-2014.04| U-Boot 2014.04]] on [[http://sourceforge.net/p/armadeus/code/ci/master/tree/ GIT]] </noinclude>

<noinclude>
=====December 25th 2013: New software release [[Releases#Release_5.3_.28latest_stable_one.29|Armadeus 5.3]]=====
This new [[Releases#Release_5.3_.28latest_stable_one.29| release]] concludes the move to Buildroot 2013.05 and U-Boot 2013.04. It also consolidates the support for vanilla Linux kernels (3.1x).</noinclude>

<noinclude>
=====June 11th 2013: Bump to Buildroot 2013.05 on GIT [[Current_Buildroot_status_in_Armadeus]]=====
Armadeus moved to Buildroot 2013.05 on GIT. Buildroot 2013.05 will apply after the BSP is fully rebuilt, so first backup your work in progress then do: git pull; git clean -dfx; make apfxx_defconfig; make </noinclude>

<noinclude>
=====October 12th 2012: New software release [[Releases#Release_5.2_.28latest_stable_one.29|Armadeus 5.2]]=====
This new [[Releases#Release_5.2_.28latest_stable_one.29| release]] enhances the supported features on the [[APF28]] board, fix a wireless issue on the PPS board and add few other improvements to the Armadeus software</noinclude>

<noinclude>
=====August 12th 2012: Armadeus 5.0 is released=====
Consolidated support for the [[APF28]] board, BR 2012.02, U-Boot 2012.04, misc. fixes.</noinclude>

<noinclude>
=====January 27th 2012: Armadeus 4.1 is released=====
This new release adds (very preliminary & experimental) support for the [[APF28]] board, BR 2011.05, better BR integration, Linux 3.0 for APF51 and industrial automation new packages.</noinclude>

<noinclude>
=====Some members of Armadeus Project team will attend booth n°71 at LSM 2011 in Strasbourg (11 to 14th July 2011)=====
</noinclude>

<noinclude>
=====July 9th 2011: Armadeus 4.0 is released=====
This new release adds support for the [[APF51]] board, BR 2010.11 and continue integration work (experimental) of Linux 2.6.38 for APF27/PPS & APF9328.</noinclude>

<noinclude>
=====May 1rst 2011: [[APF51]] SOM and [[APF51Dev]] docking board are available=====
These new powerfull boards are available on the Armadeus Systems Online Shop.</noinclude>

<noinclude>
=====March 3rd 2011: [[Release_3.4|Armadeus 3.4]] is released=====
This new release adds support for the [[APF27_PPS]] board, and continue integration work (experimental) of BR 2010.xx & Linux 2.6.38.</noinclude>

<noinclude>
=====July 30th 2010: [[Release_3.3|Armadeus 3.3]] is released=====
This new release adds better support for the [[Wireless_extension_board|APW]], WiFi, Bluetooth, GPS, Qt 4.5.3, BR 2010.05 & U-Boot 2010.03 (experimental), etc... </noinclude>

<noinclude>
=====January 15th 2010: [[Wireless_extension_board|APW]] board is available=====
The new [[Wireless_extension_board|APW]] board ("Wireless" extension for the APF27) is available on the Armadeus Systems Online Shop.</noinclude>

<noinclude>
=====December 1rst 2009: [[Release_3.2|Armadeus 3.2]] is released=====
This new release adds better support for the [[APF27]] & 7" screen, new packages (pygame, xenomai, etc...), svn to git migration, etc... </noinclude>

<noinclude>
=====July 8th 2009: [[Current_events#General_Assembly_.2F_LSM_2009 | General Assembly / LSM 2009 ]]=====
On Wednesday July 8th 2009, occurred the General Assembly in Nantes (France) </noinclude>

<noinclude>
=====June 29th 2009: [[Armadeus 3|Armadeus software 3.1]] is released, following the [[APF27Dev|APF27DevFull]] availability=====
The new Armadeus release 3.1 supports Linux kernel 2.6.29, GDB 6.7.1, APF27 FPGA download, HDMI Output of APF27DevFull and much more.
This release can be downloaded as a tarball package from [http://sourceforge.net/project/showfiles.php?group_id=122057 the usual place]</noinclude>

<noinclude>
=====February 26th 2009: [[Armadeus 3|Armadeus software 3.0]] is released, following the [[APF27]] availability=====
The new Armadeus release 3.0 supports the new Armadeus Systems APF27 board, linux kernel 2.6.27, GCC 4.2.1, U-Boot 1.3.4 and much more.
The software released can be downloaded as a tarball package from the usual place:
http://sourceforge.net/projects/armadeus</noinclude>

<noinclude>
=====December 6th 2008: [[Armadeus 3]] software available from subversion repository=====
The third generation of armadeus software is on the track. The documentation is available at [[Armadeus 3]]. For your convenience a copy of the wiki supporting previous version of Armadeus is available for offline browsing at [http://www.armadeus.com/assos_downloads/wiki/wiki_assoc_html_dump_03_12_2008.tar.gz Armadeus 2.x wiki]</noinclude>

<noinclude>
=====20 May 2008: DevFull boards are available=====
DevFull development boards are available and will be soon sold at discount price (for Armadeus Project members) on [http://www.store.armadeus.com/index.php?language=en armadeus systems online shop]</noinclude>

<noinclude>
=====17 Dec. 2007: Armadeus software version 2.2 released!=====
Armadeus release 2.2 adds many new drivers, fixes many bugs, supports the new linux kernel 2.6.23 and a recent version of buildroot.
Armadeus 2.2 can be downloaded as a tarball package from the usual place:
http://sourceforge.net/projects/armadeus

or directly from the Subversion server (SVN):
svn co https://armadeus.svn.sourceforge.net/svnroot/armadeus/tags/release-2.2 armadeus-2.2 </noinclude>

<noinclude>
=====15 Sept. 2007: APF9328 boards have been received & first DevFull prototypes are under test=====
Now all boards are available. DevFull is working well and will be available at the end of year.</noinclude>

<noinclude>
=====10 Jun. 2007: DevLight and LCD_Adapt received, but still waiting for APF9328 :-( !=====
DevLight and LCD_Adapter boards have been received but we are now waiting for new APF9328.

=====26 Mar. 2007: DevLight and LCD_Adapt ordered !=====
A new DevLight order has been placed! Expected delivey date: week 17/18

The LCD_Adapter boards have been ordered too. Expected delivery date: week 18/19</noinclude>

<noinclude>
=====22 Mar. 2007: DevLight boards are out-of-stock !=====
We have no more DevLight boards for the moment. New one have been ordered but will only be available mid-April</noinclude>
<noinclude>
=====09 Feb. 2007: Release v2.0 is out !=====
Software Release 2.0 is (at least ;-) ) available. To download it, go on Sourceforge... Now serious things can begin ! </noinclude>
<noinclude>
=====05 Nov. 2006: APF DevLight boards received=====
New members can now join us easily.</noinclude>
<noinclude>
=====15 Oct. 2006: APF DevLight boards quite ready=====
DevLight boards are in production and will be available end of October.</noinclude>
<noinclude>
=====12 Sept. 2006: APF DevLight boards ordered=====
Nico has placed an order today for 50 APF DevLight boards. They should arrive mid-october. They will allow more people to join this project soon.</noinclude>
<noinclude>
=====10 Sept. 2006: Wiki and Web sites are quite up now=====
250 years (and some months) after the birth of Wolfgang, a new genius has come to earth: the Armadeus project... ;-)
Wiki and web site (http://www.armadeus.com) begin to rock...</noinclude>

[[Template:ArmadeusNews|Show all News]]

Template:ArmadeusNews

2022-06-30T12:06:31Z

FabienM: /* June 30th, 2022: Gitlab is now official repository for armadeus bsp */

__NOTOC__

=====June 30th, 2022: Gitlab is now official repository for armadeus bsp =====

Gitlab is now official repository for armadeus bsp : https://gitlab.com/armadeus/armadeus-bsp

=====August 7th, 2018: New software release [[Releases#Release_7.0_.28latest_stable_one.29|Armadeus 7.0]]=====
<noinclude>
This new [[Releases#Release_7.0_.28latest_stable_one.29| release]] introduces the support for the new [[OPOS6UL]] & [[OPOS6UL_NANO]] SoM and concludes the move to Buildroot 2017.02.</noinclude>

=====August 11th, 2015: New software release [[Releases#Release_6.0_.28latest_stable_one.29|Armadeus 6.0]]=====
<noinclude>
This new [[Releases#Release_6.0_.28latest_stable_one.29| release]] introduces the support for the new [[APF6]] & [[APF6_SP]] Armadeus modules and concludes the move to Buildroot 2015.02 and U-Boot 2014.07+. It also consolidates the support for vanilla Linux kernels (3.19+).</noinclude>

=====June 17th, 2014: Bump to [[U-Boot-2014.04| U-Boot 2014.04]]=====
<noinclude>
All Armadeus boards moved to [[U-Boot-2014.04| U-Boot 2014.04]] on [[http://sourceforge.net/p/armadeus/code/ci/master/tree/ GIT]] </noinclude>

<noinclude>
=====December 25th 2013: New software release [[Releases#Release_5.3_.28latest_stable_one.29|Armadeus 5.3]]=====
This new [[Releases#Release_5.3_.28latest_stable_one.29| release]] concludes the move to Buildroot 2013.05 and U-Boot 2013.04. It also consolidates the support for vanilla Linux kernels (3.1x).</noinclude>

<noinclude>
=====June 11th 2013: Bump to Buildroot 2013.05 on GIT [[Current_Buildroot_status_in_Armadeus]]=====
Armadeus moved to Buildroot 2013.05 on GIT. Buildroot 2013.05 will apply after the BSP is fully rebuilt, so first backup your work in progress then do: git pull; git clean -dfx; make apfxx_defconfig; make </noinclude>

<noinclude>
=====October 12th 2012: New software release [[Releases#Release_5.2_.28latest_stable_one.29|Armadeus 5.2]]=====
This new [[Releases#Release_5.2_.28latest_stable_one.29| release]] enhances the supported features on the [[APF28]] board, fix a wireless issue on the PPS board and add few other improvements to the Armadeus software</noinclude>

<noinclude>
=====August 12th 2012: Armadeus 5.0 is released=====
Consolidated support for the [[APF28]] board, BR 2012.02, U-Boot 2012.04, misc. fixes.</noinclude>

<noinclude>
=====January 27th 2012: Armadeus 4.1 is released=====
This new release adds (very preliminary & experimental) support for the [[APF28]] board, BR 2011.05, better BR integration, Linux 3.0 for APF51 and industrial automation new packages.</noinclude>

<noinclude>
=====Some members of Armadeus Project team will attend booth n°71 at LSM 2011 in Strasbourg (11 to 14th July 2011)=====
</noinclude>

<noinclude>
=====July 9th 2011: Armadeus 4.0 is released=====
This new release adds support for the [[APF51]] board, BR 2010.11 and continue integration work (experimental) of Linux 2.6.38 for APF27/PPS & APF9328.</noinclude>

<noinclude>
=====May 1rst 2011: [[APF51]] SOM and [[APF51Dev]] docking board are available=====
These new powerfull boards are available on the Armadeus Systems Online Shop.</noinclude>

<noinclude>
=====March 3rd 2011: [[Release_3.4|Armadeus 3.4]] is released=====
This new release adds support for the [[APF27_PPS]] board, and continue integration work (experimental) of BR 2010.xx & Linux 2.6.38.</noinclude>

<noinclude>
=====July 30th 2010: [[Release_3.3|Armadeus 3.3]] is released=====
This new release adds better support for the [[Wireless_extension_board|APW]], WiFi, Bluetooth, GPS, Qt 4.5.3, BR 2010.05 & U-Boot 2010.03 (experimental), etc... </noinclude>

<noinclude>
=====January 15th 2010: [[Wireless_extension_board|APW]] board is available=====
The new [[Wireless_extension_board|APW]] board ("Wireless" extension for the APF27) is available on the Armadeus Systems Online Shop.</noinclude>

<noinclude>
=====December 1rst 2009: [[Release_3.2|Armadeus 3.2]] is released=====
This new release adds better support for the [[APF27]] & 7" screen, new packages (pygame, xenomai, etc...), svn to git migration, etc... </noinclude>

<noinclude>
=====July 8th 2009: [[Current_events#General_Assembly_.2F_LSM_2009 | General Assembly / LSM 2009 ]]=====
On Wednesday July 8th 2009, occurred the General Assembly in Nantes (France) </noinclude>

<noinclude>
=====June 29th 2009: [[Armadeus 3|Armadeus software 3.1]] is released, following the [[APF27Dev|APF27DevFull]] availability=====
The new Armadeus release 3.1 supports Linux kernel 2.6.29, GDB 6.7.1, APF27 FPGA download, HDMI Output of APF27DevFull and much more.
This release can be downloaded as a tarball package from [http://sourceforge.net/project/showfiles.php?group_id=122057 the usual place]</noinclude>

<noinclude>
=====February 26th 2009: [[Armadeus 3|Armadeus software 3.0]] is released, following the [[APF27]] availability=====
The new Armadeus release 3.0 supports the new Armadeus Systems APF27 board, linux kernel 2.6.27, GCC 4.2.1, U-Boot 1.3.4 and much more.
The software released can be downloaded as a tarball package from the usual place:
http://sourceforge.net/projects/armadeus</noinclude>

<noinclude>
=====December 6th 2008: [[Armadeus 3]] software available from subversion repository=====
The third generation of armadeus software is on the track. The documentation is available at [[Armadeus 3]]. For your convenience a copy of the wiki supporting previous version of Armadeus is available for offline browsing at [http://www.armadeus.com/assos_downloads/wiki/wiki_assoc_html_dump_03_12_2008.tar.gz Armadeus 2.x wiki]</noinclude>

<noinclude>
=====20 May 2008: DevFull boards are available=====
DevFull development boards are available and will be soon sold at discount price (for Armadeus Project members) on [http://www.store.armadeus.com/index.php?language=en armadeus systems online shop]</noinclude>

<noinclude>
=====17 Dec. 2007: Armadeus software version 2.2 released!=====
Armadeus release 2.2 adds many new drivers, fixes many bugs, supports the new linux kernel 2.6.23 and a recent version of buildroot.
Armadeus 2.2 can be downloaded as a tarball package from the usual place:
http://sourceforge.net/projects/armadeus

or directly from the Subversion server (SVN):
svn co https://armadeus.svn.sourceforge.net/svnroot/armadeus/tags/release-2.2 armadeus-2.2 </noinclude>

<noinclude>
=====15 Sept. 2007: APF9328 boards have been received & first DevFull prototypes are under test=====
Now all boards are available. DevFull is working well and will be available at the end of year.</noinclude>

<noinclude>
=====10 Jun. 2007: DevLight and LCD_Adapt received, but still waiting for APF9328 :-( !=====
DevLight and LCD_Adapter boards have been received but we are now waiting for new APF9328.

=====26 Mar. 2007: DevLight and LCD_Adapt ordered !=====
A new DevLight order has been placed! Expected delivey date: week 17/18

The LCD_Adapter boards have been ordered too. Expected delivery date: week 18/19</noinclude>

<noinclude>
=====22 Mar. 2007: DevLight boards are out-of-stock !=====
We have no more DevLight boards for the moment. New one have been ordered but will only be available mid-April</noinclude>
<noinclude>
=====09 Feb. 2007: Release v2.0 is out !=====
Software Release 2.0 is (at least ;-) ) available. To download it, go on Sourceforge... Now serious things can begin ! </noinclude>
<noinclude>
=====05 Nov. 2006: APF DevLight boards received=====
New members can now join us easily.</noinclude>
<noinclude>
=====15 Oct. 2006: APF DevLight boards quite ready=====
DevLight boards are in production and will be available end of October.</noinclude>
<noinclude>
=====12 Sept. 2006: APF DevLight boards ordered=====
Nico has placed an order today for 50 APF DevLight boards. They should arrive mid-october. They will allow more people to join this project soon.</noinclude>
<noinclude>
=====10 Sept. 2006: Wiki and Web sites are quite up now=====
250 years (and some months) after the birth of Wolfgang, a new genius has come to earth: the Armadeus project... ;-)
Wiki and web site (http://www.armadeus.com) begin to rock...</noinclude>

[[Template:ArmadeusNews|Show all News]]

2022-02-18T16:07:08Z

FabienM: /* Construction d'un container */

= Introduction =

Avec la pénurie de composants actuelle beaucoup d'entreprises sont contraintes de modifier leurs cartes électroniques de manière à supporter des variantes de leurs composants. Ce changement de composants impose souvent de retoucher le logiciel et de «remettre les mains dans le code» archivé depuis belle lurette.
Le temps du développement n'étant pas celui de la production, les projets sont souvent «figés» de longue date. Et les machines qui permettaient de compiler le matériel sont totalement obsolète quand le produit est en «full-prod».

Réinstaller les vieux logiciels qui ont permis de développer le produit se révèle souvent une gageur sur des systèmes actuels.

Heureusement pour Armadeus, tout le développement de ses cartes se fait sous Linux. Et nous avons aujourd'hui un outils formidable pour faire tourner de vieux logiciel sur des systèmes «à jour» : '''la virtualisation légère''', avec notamment le logiciel [https://fr.wikipedia.org/wiki/Docker_(logiciel) docker].

= Docker, la virtualisation légère =

Selon [https://fr.wikipedia.org/wiki/Docker_(logiciel) Wikipedia] Docker est «une plateforme permettant de lancer certaines applications dans des conteneurs logiciels. Docker étend le format de conteneur Linux standard, LXC, avec une API de haut niveau fournissant une solution pratique de virtualisation qui exécute les processus de façon isolée2.»

Dit simplement, Docker est une machine virtuelle qui émule le système d'exploitation et les librairies mais pas les instructions machine. Ce qui en fait une machine virtuelle très performante.

Docker est très intéressant pour faire tourner un programme dans un environnement logiciels contrôlé avec des versions figées. C'est par exemple le cas pour compiler un BSP en utilisant une vieille distribution linux.

= Compilation du BSP armadeus pour APF27 =

L'APF27 est typiquement la carte qui est encore actuellement en production chez armadeus mais dont le BSP n'est plus utilisable avec les outils actuels. À l'origine, le BSP de l'apf27 était compilé sur des version d'ubuntu datant des années 2010 !

Si l'on veut pouvoir reprendre son projet sans avoir à redémarrer un ordinateur de cette époque, voici comment faire avec docker.
L'exemple de cet article a été réalisé sur une distribution ubuntu version Ubuntu 20.04.3 LTS.

== Lancement de Docker ==

Docker est un «deamon» qu'il faut lancer en tâche de fond sur son système. Sur Ubuntu c'est systemd qui contrôle ça :
<source lang="sh">
$ sudo systemctl start docker
</source>

Une fois que docker tourne en tâche de fond, on peu lancer directement une console `bash` ubuntu version 12.04 avec la commande
<source lang="sh">
$ sudo docker run -it ubuntu:12.04 /bin/bash
root@1a5b88e1759c:/# cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=12.04
DISTRIB_CODENAME=precise
DISTRIB_DESCRIPTION="Ubuntu 12.04.5 LTS"
root@1a5b88e1759c:/#
</source>

Un container existe déjà sur les serveurs docker avec une version minimaliste. En tapant la commande ci-dessus, docker va simplement télécharger le container pour le lancer sur la machine.

Notre shell bash tourne bien dans une distribution ubuntu version 12.04. Pour visualiser les container actifs dans docker on lancera la commande suivant dans une autre console :
<source lang="sh">
$ sudo docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
1a5b88e1759c ubuntu:12.04 "/bin/bash" 2 minutes ago Up 2 minutes stoic_noether
</source>

Si l'on quitte la console avec `exit`, le container sera mis en inactif et il faudra le relancer pour pouvoir s'y ré-attacher :

<source>
root@1a5b88e1759c:/# exit
exit
$ sudo docker container start stoic_noether
stoic_noether
$ sudo docker attach stoic_noether
root@1a5b88e1759c:/# history
1 ls
2 top
3 cat /etc/lsb-release
4 exit
5 history
root@1a5b88e1759c:/#
</source>

Une fois que l'on se trouve dans la console on peut tenter de télécharger et compiler le bsp armadeus-7.0 par exemple :

<source lang="sh">
root@3264de07ca45:/# cd /opt/
root@3264de07ca45:/opt# mkdir bsp
root@3264de07ca45:/opt# cd bsp/
root@3264de07ca45:/opt/bsp# wget https://sourceforge.net/projects/armadeus/files/armadeus/armadeus-7.0/armadeus-7.0.tar.bz2/download
bash: wget: command not found
root@3264de07ca45:/opt/bsp# apt-get install wget
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to locate package wget
root@3264de07ca45:/opt/bsp# apt-get update
Ign http://archive.ubuntu.com precise Release.gpg
[...]
E: Some index files failed to download. They have been ignored, or old ones used instead.
root@3264de07ca45:/opt/bsp#
</source>

Ach! Très vite on se rend compte que la distribution fournie par docker est bien trop minimaliste pour que l'on puisse travailler avec. Nous allons donc devoir construire notre propre container qui partira de cette distribution pour la customiser.

== Construction d'un container ==

Pour construire son propre container, il faut créer un fichier de configuration avec le nom '''Dockerfile'''. Dans lequel on donnera le container de départ :
<source lang="INI">
#Simple commentaire d'entête
FROM ubuntu:12.04

# on ajoute les dépots apt encore accessible aujourd'hui

# Sources from https://gist.github.com/ivomts/4558134
RUN echo "deb http://old-releases.ubuntu.com/ubuntu/ precise main restricted" > /etc/apt/sources.list && \
echo "deb http://old-releases.ubuntu.com/ubuntu/ precise-updates main restricted" >> /etc/apt/sources.list && \
echo "deb-src http://old-releases.ubuntu.com/ubuntu/ precise main restricted" >> /etc/apt/sources.list && \
echo "deb http://old-releases.ubuntu.com/ubuntu/ precise-updates main restricted" >> /etc/apt/sources.list && \
echo "deb-src http://old-releases.ubuntu.com/ubuntu/ precise-updates main restricted" >> /etc/apt/sources.list
</source>

Et on construit le container en lui donnant un nom et une version :
<source lang="sh">
$ sudo docker build -t apf27bsp:0.1 .
Sending build context to Docker daemon 2.56kB
Step 1/2 : FROM ubuntu:12.04
---> 5b117edd0b76
Step 2/2 : RUN echo "deb http://old-releases.ubuntu.com/ubuntu/ precise main restricted" > /etc/apt/sources.list && echo "deb http://old-releases.ubuntu.com/ubuntu/ precise-updates main restricted" >> /etc/apt/sources.list && echo "deb-src http://old-releases.ubuntu.com/ubuntu/ precise main restricted" >> /etc/apt/sources.list && echo "deb http://old-releases.ubuntu.com/ubuntu/ precise-updates main restricted" >> /etc/apt/sources.list && echo "deb-src http://old-releases.ubuntu.com/ubuntu/ precise-updates main restricted" >> /etc/apt/sources.list
---> Running in 0b854be1e236
Removing intermediate container 0b854be1e236
---> 9c3cb7850267
Successfully built 9c3cb7850267
Successfully tagged apf27bsp:0.1
</source>

Le container ainsi construit peut être lancer avec la commande que l'on connaît bien maintenant :
<source>
$ sudo docker container run -it apf27bsp:0.1 /bin/bash
root@d6f2e3190f9b:/# apt-get update
Get:1 http://old-releases.ubuntu.com precise Release.gpg [198 B]
...
root@d6f2e3190f9b:/# apt-get install wget
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following extra packages will be installed:
libidn11
The following NEW packages will be installed:
libidn11 wget
0 upgraded, 2 newly installed, 0 to remove and 27 not upgraded.
Need to get 392 kB of archives.
After this operation, 970 kB of additional disk space will be used.
Do you want to continue [Y/n]? y
...
root@d6f2e3190f9b:/# cd /opt/
root@d6f2e3190f9b:/opt# ls
root@d6f2e3190f9b:/opt# mkdir bsp
root@d6f2e3190f9b:/opt# cd bsp/
root@d6f2e3190f9b:/opt/bsp# wget https://sourceforge.net/projects/armadeus/files/armadeus/armadeus-7.0/armadeus-7.0.tar.bz2/download --no-check-certificate
...
Saving to: `download'

100%[=========================================================================================================================================================================>] 6,572,959 1.87M/s in 3.8s

2022-02-18 15:58:54 (1.67 MB/s) - `download' saved [6572959/6572959]

root@d6f2e3190f9b:/opt/bsp# mv download armadeus-7.0.tar.bz2
root@d6f2e3190f9b:/opt/bsp# apt-get install bzip2
root@d6f2e3190f9b:/opt/bsp# tar jxf armadeus-7.0.tar.bz2
root@d6f2e3190f9b:/opt/bsp#
</source>

Très vite on se rend compte que nous avons beaucoup de logiciel à télécharger et installer. Le problème des container c'est que rien n'est enregistré, donc à chaque fois qu'on lance le containert avec la commande `run` tout est remis à zéro.

Il devient donc rapidement indispensable d'ajouter les commande de mise à jour des packages dans le `Dockerfile`. Et pour récupérer les fichiers que l'on compile avec le container il va être nécessaire de «monter» un répertoire de son ordinateur dans le container.

Ce montage se fait au lancement du container. Par exemple si nous souhaitons monter le répertoire de téléchargement des packets buildroot ainsi que le répertoire du bsp armadeus nous utiliserons la commande :

<source lang="sh">
sudo docker run --mount src=/downloads,target=/downloads,type=bind \
--mount src=/home/user/prj/armadeusbsp,target=/opt/bsp/,type=bind \
-it apf27bsp:1.0 /bin/bash
</source>

Nous mutualiserons ainsi le répertoires /downloads de notre machine et nous récupérerons les binaires générés à la compilation du bsp dans le container.

2022 02 18 Container docker pour vieux BSP

2022-02-18T15:52:53Z

FabienM: /* Lancement de Docker */

2022 02 18 Container docker pour vieux BSP

2022-02-18T15:45:31Z

FabienM: /* Lancement de Docker */

2022 02 18 Container docker pour vieux BSP

2022-02-18T15:26:35Z

FabienM: /* Lancement de Docker */

2022 02 18 Container docker pour vieux BSP

2022-02-18T15:26:01Z

FabienM: /* Compilation du BSP armadeus pour APF27 */

2022 02 18 Container docker pour vieux BSP

2022-02-18T15:06:40Z

FabienM: Created page with "= Introduction = Avec la pénurie de composants actuelle beaucoup d'entreprises sont contraintes de modifier leurs cartes électroniques de manière à supporter des variante..."

User:FabienM

2022-02-18T14:40:59Z

FabienM: /* Blog */

[[MemberList | << liste des membres]]

= Mes petites bidouilles avec l'armadeus =

* [[Une led qui clignote avec le spartan 3]]
* [[Petits trucs en vrac]]
* [[Led sensor]]
* [[vim | The best editor in the world]]

= Trucs =

== Python en environnement virtuel ==

Un pense bète pour installer la version voulue de python en environnement virtuel avec virtualenv:

=== virtualenv et autre tkinter ===

<pre>
apt-get install python-tk python3-tk tk-dev
apt-get install python-virtualenv
</pre>

=== Python 3.7.4 ===

<pre>
sudo apt-get install libffi-dev
wget https://www.python.org/ftp/python/3.7.4/Python-3.7.4.tar.xz
tar -Jxvf Python-3.7.4.tar.xz
cd Python-3.7.4
./configure --enable-shared
make
sudo make install
sudo ldconfig /usr/local/lib
</pre>

=== virtualenv ===

* Virtual env configuration:

<pre>
apt-get install python-virtualenv
mkdir virtenv
cd virtenv
virtualenv --python=/usr/local/bin/python3.7 envp37
</pre>

* enum bug fix:

<pre>
cd ~/virtenv/envp37/lib/python3.7
ln -s /usr/local/lib/python3.7/enum.py
</pre>

* Activation:
<pre>
source /home/armadeus/virtenv/envp37/bin/activate
</pre>

* Desactivation:
<pre>
deactivate
</pre>

= '''P'''eripheral '''O'''n '''D'''emand =

* [[Specification feedback]]

= Participation à la documentation ArmadeuS Project =

* [[How to make a VHDL design in Ubuntu/Debian]]
* [[How to simulate post synthesis and post place & route design with GHDL]]

* [[Using FPGA]]

* [[A simple design with Wishbone bus]]

* [[How to use kernel 2.6.38.x on APF27]]

== Trash ==
* [[APF27_FPGA-IMX_interface_description | Description of FPGA-IMX interface for APF27]]
* [[APF51_FPGA-IMX_interface_description | Description of FPGA-IMX interface for APF51]]
* [[FPGA | FPGA on APF introduction]]
* [[FPGA and led | Button and LED]]

== Projets ==

* Camera [[C38A]] with chip ov7620
* Camera omnivision [[VC21CC1]]
* [[Robotic]]
* [[Home monitoring energy | Compteur d'énergie électrique]]
* [[OOCP]] (Only One Cable Project)
* [[Use MySQL-client on apf9328]]
* [[Light-APF27Dev | Light-APF27Dev project ]]

= Liens utiles =

* Projets [http://sourceforge.net/projects/armadeus sourceforge]
* Site [http://www.armadeus.com/english/index.html entreprise]
* Les codes de retour d'erreurs : http://www.opengroup.org/onlinepubs/007908799/xsh/errno.h.html
* [[Buildroot_Packages]]
* [http://sebsauvage.net/files/20130426_cpp_quovadis2013cppontheweb-130425105424-phpapp01.pdf Un papier très intéressant] d'un développeur de jeux vidéo prônant l'utilisation du C++ ... pour le web. Notamment grâce à l'utilisation de [http://sebsauvage.net/files/20130426_cpp_multiplatformconthewebwithemscripten-130405172545-phpapp01.pdf emscripten] qui permet de compiler du C++ vers le javascript (HTML5).

= Somes usefull tricks =
== press a button ==
Here, function to «press enter to continue» on apf in different languages :

<source lang="bash">
setbit /proc/driver/gpio/portFmode 13 1 # set pin as gpio
setbit /proc/driver/gpio/portFdir 13 0 # set pin as input
setbit /proc/driver/gpio/portFirq 13 1 # irq on rising edge

/usr/bin/testsuite/testbutton /dev/gpio/PF13 3
</source>

With ''testbutton'' program comming from
''target/linux/modules/fpga/wishbone_example/wb_button''. Type «make» in this
directory to compile it.

== Logging with timestamps in seconds ==

<source lang="bash">
#!/bin/sh
while true
do
LIGHT=$(cat /sys/class/hwmon/hwmon0/device/in3_input)
TIME=$(date +%s)
echo $TIME", sec, "$LIGHT", mV," >> log;
sleep 2
done
</source>

== Press enter to continue ==
=== C ===

<source lang="C">
#include <stdio.h>

void pressEnterToContinue(void)
{
printf("Press enter to continue\n");
getc(stdin);//XXX
while( getc(stdin) != '\n') ;
}

</source>

=== C++ ===
<source lang="C">
#include <stdio.h> //XXX
#include <iostream>

void pressEnterToContinue(void)
{
cout << "Press enter to continue" << endl;
getc(stdin); //XXX
std::cin.ignore( std::numeric_limits <std::streamsize> ::max(), '\n' );
}

</source>

=== Python 2 ===

<source lang="python">

def pressEnterToContinue():
print "Press enter to continue"
raw_input()

</source>

=== Python 3 ===

<source lang="python">

def pressEnterToContinue():
print("Press enter to continue")
input()

</source>

= Kernel Driver =

* [[IIO kernel driver model]]
* [[UIO kernel driver model]]

= bac à sable =
[[Image:dessin.svg]]

* [[APF6_SP_DDR3_PINOUT]]
* [[APF6_SP The full howto]]

== Wavedrom ==

If [https://github.com/Martoni/mediawiki_wavedrom wavedrom plugin] is installed on this wiki, we can see a beautiful waves bellow :

<wavedrom>
{ signal: [
{ name: "clk", wave: "p......" },
{ name: "bus", wave: "x.34.5x", data: "head body tail" },
{ name: "wire", wave: "0.1..0." },
]}
</wavedrom>

= Blog =

* [[2022_02_18_Container_docker_pour_vieux_BSP]]

2021-09-07T15:14:38Z

FabienM: /* Chip Select */

[[Category: APF51]]
[[Category: FPGA]]
[[Category: Spartan6]]

== Introduction ==
This article describe the bus interface configuration to communicate between i.MX51 processor and Spartan6 FPGA. In i.MX51, the bus used to make communication with the FPGA is named '''WEIM''' for Wireless Extension Interface Module. All description of this bus can be found under the [http://cache.freescale.com/files/dsp/doc/ref_manual/MCIMX51RM.pdf?fpsp=1&WT_TYPE=Reference%20Manuals&WT_VENDOR=FREESCALE&WT_FILE_FORMAT=pdf&WT_ASSET=Documentation i.MX51 reference manual] in chapter 63 (page 3113).

== Simplified view ==

[[image:Imx51-spartan6.jpg|700px|center|thumb|'''figure 1''' - ''i.MX51-Spartan6 bus description'']]

Figure 1 is a simplified view of [[Datasheet#APF51 | APF51 schematics]] (page 15), signals are :

* '''BCLK''': i.MX51 burst clock used to clock the spartan6.
* '''DA'''[15:0] : Data/Address multiplexed bus.
* '''LBA''' : Noted '''ADV''' for ''AD''dress ''V''alid under the i.MX51 reference manual.
* EB0, EB1 : For Enable Byte, write signal for lower byte and upper byte on data bus.
* '''CS1''' : Chip Select 1.
* CS2 : Chip Select 2.
* OE : For Output Enable bit, read signal. (Motorola way of bus)
* '''RW''' : Read/Write signal. (Intel way of bus)
* DTACK : Data acknoledge, for asynchronous access.
* WAIT : Wait signal used for some burst access.
Not part of WEIM bus :
* CLK0 : An i.MX51 output clock (not used ).
* FPGA_INITB : used by default for interrupts (GPIO4_11).

Signals in '''bold''' are signals used in default configuration.

== Default configuration on CS1 ==
=== Clock ===

The clock used to clock the fpga is ''BCLK'' (IO_L29P_GCLK3_2 on Spartan6) and is configured to '''95 MHz'''.

=== Chip Select ===
By default the chip select 1 (CS1) is used for communication. The address domain corresponding to this chip select can be found in [https://www.nxp.com/docs/en/reference-manual/MCIMX51RM.pdf i.MX51 reference manual] in chapter 2 (Memory Map page 65).
{| border="1" cellpadding="5" cellspacing="0" align="center"
|- style="background:#efefef;" align="center"
! Start Address !! End Address !! Size !! Region

|- align="center"
| '''B800_0000''' || '''BFFF_FFFF''' || '''128M''' || '''CS1 (Flash) 128M'''

|- align="center"
| C000_0000 || C7FF_FFFF|| 128M|| CS2 (Flash) 128M

|}

It's possible to use the second chip select (CS2) to extend memory domain or to use different timing configuration with the same Address/Data bus signals.

The default bus configuration for the APF51 can be found in the file apf51.h in u-boot sources :
''buildroot/target/device/armadeus/apf51/apf51-u-boot-2010.03.h''

Especially these lines :
<source lang="c">
#define CONFIG_FPGA_GCR1_VALUE 0x019100bf
#define CONFIG_FPGA_GCR2_VALUE 0x00000000

#define CONFIG_FPGA_RCR1_VALUE 0x04000010
#define CONFIG_FPGA_RCR2_VALUE 0x00000000

#define CONFIG_FPGA_WCR1_VALUE 0x04000008
#define CONFIG_FPGA_WCR2_VALUE 0x00000000
</source>

{{Note| Do not forget to do :
<pre class="host">
$ make u-boot-dirclean
$ make
</pre>
To test your modification under the ''apf51-u-boot-2010.03.h'' file
}}

It is not necessary to modify apf51.h file and recompile U-Boot for WEIM timings test, register can be read/written ''via'' [http://www.denx.de/wiki/view/DULG/UBootCmdGroupMemory#Section_5.9.2.8. U-Boot] or [[FPGA_register | Linux]].
To access these register with U-Boot or Linux, use the address given under the reference manual in WEIM register descriptions (63.4.3 Register Descriptions).
{{Note| The 0xBASE value is given in chapter 2 "Memory Map" (page 65) : 0xBASE -> 0x83FD8000}}

Configuration register can be read/write with [[devmem]] tool:

<pre class="apf">
# echo "CS1GCR1"
# devmem 0x83fda018 32
0x019100BF
# echo "CS1GCR2"
# devmem 0x83fda01c 32
0x00000000
# echo "CS1RCR1"
# devmem 0x83fda020 32
0x04000010
# echo "CS1RCR2"
# devmem 0x83fda024 32
0x00000000
# echo "CS1WCR1"
# devmem 0x83fda028 32
0x04000008
# echo "CS1WCR2"
# devmem 0x83fda02C 32
0x00000000
# echo "WCR"
# devmem 0x83fda090 32
0x00000021
# echo "WIAR"
# devmem 0x83fda094 32
0x00000014

</pre>

==== Timings ====

Following chronograms represents WEIM read and write configured for APF51.

[[image:Imx51_sp6_write_timings.jpeg|700px|center|thumb|'''figure 2''' - ''WEIM Write timings'']]
[[image:Imx51_sp6_read_timings.jpeg|700px|center|thumb|'''figure 3''' - ''WEIM Read timings'']]

=== FPGA side ===

By default, the wishbone bus is used under the spartan6 fpga. Then a WEIM to Wishbone wrapper is used, this wrapper is available under [https://github.com/Martoni/pod_lib/tree/master/platforms/apf51 POD] default libraries in ''wrappers'' lib. The component is named ''imx51_wb16_wrapper''.

== The FPGA interrupt ==

By default under [https://github.com/Martoni/periphondemand POD] the pin '''FPGA_INITB''' (gpio4_11) is used for the interrupts manager ''irq_mngr''. For simple user application the gpio can be used with the [[GPIOlib]] interface, the gpio number will then be (4-1)x32+11 = '''107'''.

== Links ==

* [http://billauer.co.il/blog/2011/10/imx51-imx-weim-freescale-arm-bus/ Eli Billauer investigation].

IMX51-Spartan6 interface description

2021-09-07T14:45:51Z

FabienM: /* Chip Select */

[[Category: APF51]]
[[Category: FPGA]]
[[Category: Spartan6]]

== Introduction ==
This article describe the bus interface configuration to communicate between i.MX51 processor and Spartan6 FPGA. In i.MX51, the bus used to make communication with the FPGA is named '''WEIM''' for Wireless Extension Interface Module. All description of this bus can be found under the [http://cache.freescale.com/files/dsp/doc/ref_manual/MCIMX51RM.pdf?fpsp=1&WT_TYPE=Reference%20Manuals&WT_VENDOR=FREESCALE&WT_FILE_FORMAT=pdf&WT_ASSET=Documentation i.MX51 reference manual] in chapter 63 (page 3113).

== Simplified view ==

[[image:Imx51-spartan6.jpg|700px|center|thumb|'''figure 1''' - ''i.MX51-Spartan6 bus description'']]

Figure 1 is a simplified view of [[Datasheet#APF51 | APF51 schematics]] (page 15), signals are :

* '''BCLK''': i.MX51 burst clock used to clock the spartan6.
* '''DA'''[15:0] : Data/Address multiplexed bus.
* '''LBA''' : Noted '''ADV''' for ''AD''dress ''V''alid under the i.MX51 reference manual.
* EB0, EB1 : For Enable Byte, write signal for lower byte and upper byte on data bus.
* '''CS1''' : Chip Select 1.
* CS2 : Chip Select 2.
* OE : For Output Enable bit, read signal. (Motorola way of bus)
* '''RW''' : Read/Write signal. (Intel way of bus)
* DTACK : Data acknoledge, for asynchronous access.
* WAIT : Wait signal used for some burst access.
Not part of WEIM bus :
* CLK0 : An i.MX51 output clock (not used ).
* FPGA_INITB : used by default for interrupts (GPIO4_11).

Signals in '''bold''' are signals used in default configuration.

== Default configuration on CS1 ==
=== Clock ===

The clock used to clock the fpga is ''BCLK'' (IO_L29P_GCLK3_2 on Spartan6) and is configured to '''95 MHz'''.

=== Chip Select ===
By default the chip select 1 (CS1) is used for communication. The address domain corresponding to this chip select can be found in [https://www.nxp.com/docs/en/reference-manual/MCIMX51RM.pdf i.MX51 reference manual] in chapter 2 (Memory Map page 65).
{| border="1" cellpadding="5" cellspacing="0" align="center"
|- style="background:#efefef;" align="center"
! Start Address !! End Address !! Size !! Region

|- align="center"
| '''B800_0000''' || '''BFFF_FFFF''' || '''128M''' || '''CS1 (Flash) 128M'''

|- align="center"
| C000_0000 || C7FF_FFFF|| 128M|| CS2 (Flash) 128M

|}

It's possible to use the second chip select (CS2) to extend memory domain or to use different timing configuration with the same Address/Data bus signals.
The default bus configuration for the APF51 can be found in the file apf51.h in u-boot sources :
''buildroot/target/device/armadeus/apf51/apf51-u-boot-2010.03.h''

Especially these lines :
<source lang="c">
#define CONFIG_FPGA_GCR1_VALUE 0x019100bf
#define CONFIG_FPGA_GCR2_VALUE 0x00000000

#define CONFIG_FPGA_RCR1_VALUE 0x04000010
#define CONFIG_FPGA_RCR2_VALUE 0x00000000

#define CONFIG_FPGA_WCR1_VALUE 0x04000008
#define CONFIG_FPGA_WCR2_VALUE 0x00000000

</source>

{{Note| Do not forget to do :
<pre class="host">
$ make u-boot-dirclean
$ make
</pre>
To test your modification under the ''apf51-u-boot-2010.03.h'' file
}}

It is not necessary to modify apf51.h file and recompile U-Boot for WEIM timings test, register can be read/written ''via'' [http://www.denx.de/wiki/view/DULG/UBootCmdGroupMemory#Section_5.9.2.8. U-Boot] or [[FPGA_register | Linux]].
To access these register with U-Boot or Linux, use the address given under the reference manual in WEIM register descriptions (63.4.3 Register Descriptions).
{{Note| The 0xBASE value is given in chapter 2 "Memory Map" (page 65) : 0xBASE -> 0x83FD8000}}

==== Timings ====

Following chronograms represents WEIM read and write configured for APF51.

[[image:Imx51_sp6_write_timings.jpeg|700px|center|thumb|'''figure 2''' - ''WEIM Write timings'']]
[[image:Imx51_sp6_read_timings.jpeg|700px|center|thumb|'''figure 3''' - ''WEIM Read timings'']]

=== FPGA side ===

By default, the wishbone bus is used under the spartan6 fpga. Then a WEIM to Wishbone wrapper is used, this wrapper is available under [https://github.com/Martoni/pod_lib/tree/master/platforms/apf51 POD] default libraries in ''wrappers'' lib. The component is named ''imx51_wb16_wrapper''.

== The FPGA interrupt ==

By default under [https://github.com/Martoni/periphondemand POD] the pin '''FPGA_INITB''' (gpio4_11) is used for the interrupts manager ''irq_mngr''. For simple user application the gpio can be used with the [[GPIOlib]] interface, the gpio number will then be (4-1)x32+11 = '''107'''.

== Links ==

* [http://billauer.co.il/blog/2011/10/imx51-imx-weim-freescale-arm-bus/ Eli Billauer investigation].

Fpgaregs

2021-09-07T08:30:02Z

FabienM: Redirected page to FPGA registers access from Linux userspace

#REDIRECT[[FPGA_registers_access_from_Linux_userspace]]