ArmadeusWiki - User contributions [en]

User:JulienC

2009-03-08T16:16:42Z

JulienC: /* Change Ethernet MAC address */ Link to more complete page

Ethernet MAC address

2009-03-04T09:24:43Z

JulienC: Ethernet MAC address details and how to change it on APF9328

If, for any reasons, you want to change your board Ethernet MAC address, here is the procedure.

== Introduction ==
Every network card has a [[wikipedia:MAC address|MAC address]] to identify itself on the network. The MAC address first three octets are known as the [[wikipedia:Organizationally Unique Identifier|Organizationally Unique Identifier]]. Armadeus OUI is 00:1E:AC [http://www.coffer.com/mac_find/?string=Armadeus]

=== Hardware ===
Armadeus APF9328 board has a separate MAC controller, the DM9000 chip from Davicom [http://www.davicom.com.tw/userfile/24247/DM9000-DS-F03-041906_1.pdf]. The [http://www.armadeus.com/_downloads/apf9328/hardware/apf_schema.pdf APF schematic], page 10, shows the implementation of the chip with an EEPROM chip to store its parameters, including MAC address.

=== U-boot ===
[[BootLoader|U-boot]] has a parameter containing the Ethernet address. This parameter is independent from the hardware address. The parameter is '''ethaddr'''.
<pre class="apf">
BIOS> printenv ethaddr
00:1E:AC:XX:XX:XX
</pre>
XX:XX:XX being the board specific address.

== Change MAC address ==

It can happen that the MAC address is wrong (e.g.: 00:00:0E:00:00:00 in my case), empty or that you want to change it.

=== Empty MAC address ===
If the board MAC address is empty, the procedure is simplified.

In U-boot, simply set the correct value in the parameter '''ethaddr''', ping any address and save the environment.
<pre class="apf">
BIOS> setenv ethaddr 00:1e:ac:XX:XX:XX
BIOS> ping 1
MAC: 00:1e:ac:XX:XX:XX
operating at 100M full duplex mode
[Ctrl-C]
Abort
ping failed; host 1 is not alive
BIOS> saveenv
</pre>
FIXME: The above message are made-up, don't know if reprogramming message is displayed or not...
=== Wrong MAC address ===
If the MAC address is already set but wrong, changing the U-boot parameter ethaddr will not automatically reprogram the EEPROM. It is necessary to indicate to U-boot to reprogram the EEPROM.

This is made possible by a specific patch to U-boot by Armadeus for the DM9000 chip [http://armadeus.svn.sourceforge.net/viewvc/armadeus/trunk/buildroot/target/u-boot/u-boot-1.3.4-111-apf9328-DM9000.patch?revision=1009&view=markup] line 68 and following. Thanks to this patch, setting the ethaddr parameter to ff:ff:ff:ff:ff:ff and ping any IP will provoke the MAC address reprogramming. Then simply set ethaddr parameter again to the correct MAC address and ping any IP address, as shown below.
<pre class="apf">
BIOS> setenv ethaddr ff:ff:ff:ff:ff:ff
BIOS> ping 1
Warning: MAC addresses reprogramming..
MAC: ff:ff:ff:ff:ff:ff
operating at 100M full duplex mode
[Ctrl-C]
Abort
ping failed; host 1 is not alive
BIOS> setenv ethaddr 00:1e:ac:XX:XX:XX
BIOS> ping 1
Warning: MAC addresses reprogramming..
MAC: 00:1e:ac:XX:XX:XX
operating at 100M full duplex mode
[Ctrl-C]
Abort
ping failed; host 1 is not alive
BIOS>
</pre>

== Check your MAC address in Linux ==
Linux kernel and U-boot do not use the same source to get the board MAC address. As mentioned before, U-boot trusts its parameter ethaddr. Instead, Linux kernel, which uses the DM9000 driver, reads the MAC address from the EEPROM. During Linux boot, the driver prints the MAC address.
<pre class="apf">
[...]
dm9000 Ethernet Driver, V1.31
eth0: dm9000e at c1854000,c1856002 IRQ 110 MAC: 00:1e:ac:xx:xx:xx (eeprom)
[...]
</pre>

When logged on Linux, the tool '''ifconfig''' also displays information about the Ethernet MAC address.
<pre class="apf">
# ifconfig eth0
eth0 Link encap:Ethernet HWaddr 00:1E:AC:XX:XX:XX
inet addr:192.168.0.10 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: fe80::21e:acxx:xxxx:xx/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:468 (468.0 B)
Interrupt:110 Base address:0x4000
</pre>
The field HWaddr corresponds to the MAC address read by dm9000 driver and used during communication.

User:JulienC

2009-03-03T22:01:40Z

JulienC: /* Change Ethernet MAC address */

My name is Julien and I am a French engineer in embedded systems. My interests are in FPGA programming and embedded Linux. I will try to share my experiments on this wiki.

I am new in the FPGA world. I will try to learn and share as much as I can.

== Blinking LED ==
'''Goal''': Make a LED blink.

I used the [[Une_led_qui_clignote_avec_le_spartan_3|LED blinking page]] VHDL code to generate the FPGA binary file with Xilinx ISE. (more details are needed on this wiki to generate .bit files)

On the hardware side, I connected the 2 FPGA pins L28P and L28N to a [[wikipedia:breadboard|breadboard]] with wires. Those 2 pins are accessible on the DevLight bottom, as mentioned on the [http://www.armadeus.com/_downloads/apf9328DevLight/documentation/dataSheet_APF9328_DevLight_V2.pdf datasheet], page 9. Those 2 pin-holes are too small to solder [http://www.selectronic.fr/article.asp?article_ref_entier=90.0425-9999 "conventional" pins], so my set-up is quite unstable. I need to make it more robust.

On the software side, I don't want (yet) to flash my board with a new software, so I am using the default one provided (Linux kernel 2.6.27.2). Moreover I want to load the FPGA from Linux (and not [[InstallTargetSoftware#FPGA_firmware_installation|from U-boot]]).
I set-up a [[MultiMediaCard|microSD card]] to transfer my files. to load the FPGA binary file, in addition to the .bit file, I needed the [[FPGA_loader|fpgaloader]] driver script which seems not to be by default on the board.

After booting the board, I use the following commands:
<pre class="apf">
# mount -t ext2 /dev/mmcblk0p2 /mnt/mmc
# cd /mnt/mmc/root/
# ls
Clk_div_led.bit fpgaloader.sh
# sh fpgaloader.sh
fpgaloader module v0.0.6 successfully loaded !
# dd if=Clk_div_led.bit of=/dev/fpga/fpgaloader
255+1 records in
255+1 records out
</pre>

And it blinks!

== Change Ethernet MAC address ==
(TO BE detailed)
http://armadeus.svn.sourceforge.net/viewvc/armadeus/trunk/buildroot/target/u-boot/u-boot-1.3.4-111-apf9328-DM9000.patch?revision=1009&view=markup line 68+

U-boot:
<pre class="apf">
BIOS> setenv ethaddr ff:ff:ff:ff:ff:ff
BIOS> ping 1
Warning: MAC addresses reprogramming..
MAC: ff:ff:ff:ff:ff:ff
operating at 100M full duplex mode

Abort
ping failed; host 1 is not alive
BIOS> setenv ethaddr 00:1e:ac:XX:XX:XX
BIOS> ping 1
Warning: MAC addresses reprogramming..
MAC: 00:1e:ac:XX:XX:XX
operating at 100M full duplex mode

Abort
ping failed; host 1 is not alive
BIOS>
</pre>

Linux boot:
<pre class="apf">
[...]
dm9000 Ethernet Driver, V1.31
eth0: dm9000e at c1854000,c1856002 IRQ 110 MAC: 00:1e:ac:xx:xx:xx (eeprom)
[...]
</pre>
<pre class="apf">
# ifconfig
eth0 Link encap:Ethernet HWaddr 00:1E:AC:XX:XX:XX
inet addr:192.168.0.10 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: fe80::21e:acxx:xxxx:xx/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:468 (468.0 B)
Interrupt:110 Base address:0x4000
</pre>

== Notes ==
Booting from SD card: (links, not tried yet)
* http://wiki.openmoko.org/wiki/Booting_from_SD
* http://docwiki.gumstix.org/U-Boot#The_MMC_card

User:JulienC

2009-03-02T15:29:09Z

JulienC: Follow WritingRules

User:JulienC

2009-03-01T20:58:30Z

JulienC: wikipedia links enabled (Thanks!)

User:JulienC

2009-03-01T00:15:13Z

JulienC: Booting from SD card (links to investigate)

User:JulienC

2009-02-28T22:12:09Z

JulienC: My first FPGA blinking LED !

MMC/SD

2009-02-28T16:56:42Z

JulienC: /* microSD/TransFlash: */ EMTEC 2 Gbyte (ext2)

How-To connect an MMC/SD adapter/connector to your APF9328

For instructions on how to use MMC/SD on Linux, see [[MultiMediaCard]] page. 
'''SDCard, MiniSD, and Transflash/MicroSD are all the same devices but in different package shapes and are all pin compatible.''' 
On Armadeus boards, MMC are controlled in 1 bit MMC mode and SD/MiniSD/MicroSD in 4 bits SD mode.
We don't use MMC/SD in slow & error prone SPI mode.

== Adapter board (for DevLight 1.0 or your custom board) ==
We have designed a small adapter board with a push-pull MMC/SD connector on it.
You need to connect the signals listed in the table below to the corresponding one on your DevLight board.
The WP and CD_SW signals are optional and must be connected to free i.MXL GPIOs, if used.

[[Image:MMC_Adapt.jpg|thumb|center|Top view, connector on the left]]

Signals name (Top view with MMC connector on the right):[[Image:MMC_Adapt_pinout.jpg|thumb|Left|]]
{| border="1" cellpadding="5" cellspacing="0" summary="Signal connections"
|- style="background:#efefef;"
!'''Adapter Pin''' || '''Desc''' || '''Adapter Pin''' || '''Desc'''
|----------------
|1 (square) || +3.3V || 2 || SD_DAT2
|----------------
|3 || SD_CMD || 4 || SD_DAT3
|----------------
|5 || SD_CLK || 6 || SD_DAT0
|----------------
|7 || WP (option) || 8 || SD_DAT1
|----------------
|9 || CD_SW (option) || 10 || GND
|----------------
|}

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

'''If you don't want to buy such an adapter or don't have a MMC slot (and are a hacker ;-) ), you can still try this link:'''
* http://www.hackaday.com/2006/09/12/floppy-connector-mmc-card-slot/

== On a DevFull board, there is already a MMC/SD connector ==

== On a DevLight 2.0 board, there is already a microSD connector ==

== Supported Cards ==
Here is a list of the current cards which were tested. Speeds are rounded to the nearest multiple of 5: 
===MMC===
{| border="1" cellpadding="5" cellspacing="0" summary="MMC"
|- style="background:#efefef;"
!'''Model''' || '''Status''' || '''Speed in kB/sec (read/write)''' || '''Comments'''
|----------------
|'''Hama 256 Mbytes''' || style="background:#00ff00;" |working || 895 / 455 || Ext2
|----------------
|}

===MMC+===

{| border="1" cellpadding="5" cellspacing="0" summary="MMC+"
|- style="background:#efefef;"
!'''Model''' || '''Status''' || '''Speed in kB/sec (read/write)''' || '''Comments'''
|----------------
|'''Kingston 256 Mbytes''' || style="background:#00ff00;" |working || NA ||
|----------------
|}

===SD:===

{| border="1" cellpadding="5" cellspacing="0" summary="MMC+"
|- style="background:#efefef;"
!'''Model''' || '''Status''' || '''Speed in kB/sec (read/write)''' || '''Comments'''
|----------------
|'''Kingston 512 Mbytes''' || style="background:#00ff00;" |working || 3275 / 155 || Ext2
|----------------
|'''Kingston 256 Mbytes''' || style="background:#00ff00;" |working || NA ||
|----------------
|'''Dane-Elec 2 Gbytes''' || style="background:#ff0000;" |KO || NA || OK in 1bit mode. doesn't work : Card recognized but partition table not found in 4bits mode
|----------------
|'''Transcend 2 Gbytes (x150)''' || style="background:#00ff00;" |working || NA ||
|----------------
|'''Sandisk 512 Mbytes''' || style="background:#00ff00;" |working || NA || formating failure may happen sometimes. Workaround: retry
|----------------
|'''Panasonic 16 Mbytes''' || style="background:#00ff00;" |working || NA || Ext2
|----------------
|}

===MiniSD:===
{| border="1" cellpadding="5" cellspacing="0" summary="MiniSDs"
|- style="background:#efefef;"
!'''Model''' || '''Status''' || '''Speed in kB/sec (read/write)''' || '''Comments'''
|----------------
|'''Corsair 1Gbytes''' || style="background:#00ff00;" |working || 3330 / 365 || VFAT
|----------------
|'''Sandisk 1Gbytes''' || style="background:#00ff00;" |working || 3300 / 295 || Ext2
|----------------
|'''Sandisk 512Mbytes''' || style="background:#00ff00;" |working || 2750 / 215 || VFAT
|----------------
|'''Transcend 512Mbytes''' || style="background:#ff0000;" | not recognized || NA ||
|----------------
|'''Extreme Memory 512Mbytes''' || style="background:#ff0000;" |not recognized || NA ||
|----------------
|'''Dane-Elec 1Gbytes''' || style="background:#ff0000;" |doesn't work || NA || Card recognized but partition table not found
|----------------
|}

===microSD/TransFlash:===
{| border="1" cellpadding="5" cellspacing="0" summary="MicroSDs"
|- style="background:#efefef;"
!'''Model''' || '''Status''' || colspan="2" | '''Speed in kB/sec (read/write)''' APF9328 | APF27 || '''Comments'''
|----------------
|'''Sandisk 512 Mbytes''' || style="background:#00ff00;" |working || 3330 / 320 || NT / NT || VFAT
|----------------
|'''Dane-Elec 1 Gbyte''' || style="background:#00ff00;" |working || 3415 / 130 || NT / NT || VFAT
|----------------
|'''Sandisk 1 Gbyte''' || style="background:#00ff00;" |working || 3355 / 130 || NT / NT || VFAT
|----------------
|'''Kingston 1 Gbyte''' || style="background:#00ff00;" |working || 3355 / 130 || NT / NT || VFAT
|----------------
|'''Kingston 2 Gbyte''' || style="background:#00ff00;" |working || 3355 / 130 || NT / NT || VFAT
|----------------
|'''EMTEC 2 Gbyte''' || style="background:#00ff00;" |working || 3232 / 1548 || NT / NT || EXT2
|----------------
|'''Kingston 4 Gbyte''' || style="background:#00ff00;" |working || 3355 / 130 || NT / NT || VFAT
|----------------
|'''Transcend 4 Gbyte SDHC Class 6''' || style="background:#00ff00;" |working || 3379 / 2668 || NT / NT || VFAT
|----------------
|}

===Test method===
Use test script (''mmc_perf.sh'') located in ''armadeus/target/test/mmc/''. Copy it on your target and launch it:
# mmc_perf.sh speed

== Links ==
* [[MultiMediaCard|How to use MMC/SD/microSD on Linux]]
* [http://elm-chan.org/docs/mmc/mmc_e.html How to use MMC/SD]

 
{{LanguageBar|MMC/SD|MMC/SD|MMC/SD}}

[[Category:Hardware]]
[[Category:MassStorage]]

FPGA registers access from Linux userspace

2009-02-15T21:55:02Z

JulienC: /* the mmap problem */ spelling

[[Category:FPGA]]

= fpgaregs =

== compile ==
To access FPGA registers a tool named ''fpgaregs'' is available under ''target/linux/module/fpga/dev_tools/'' directory. To compile it for apf9328, use the command above :

<source lang="bash">
arm-linux-gcc -mcpu=arm920t fpgaregs.c -o fpgaregs
</source>

== use ==

fpgaregs can be used to read and write 16 or 32 bits registers.

'''read 16 bits'''
<source lang="bash">
fpgaregs w <address>
</source>

Where <address> is an address relative to fpga mapping in hexadecimal value.

'''write 16 bits'''
<source lang="bash">
fpgaregs w <address> <value>
</source>

Where <value> is hexadecimal value to write.

'''read 32 bits'''
<source lang="bash">
fpgaregs l <address>
</source>

'''write 32 bits'''
<source lang="bash">
fpgaregs l <address> <value>
</source>

= the mmap problem =

First of all, you need to get a file descriptor for ''/dev/mem'' using the ''open()'' function
<source lang="c">
ffpga=open("/dev/mem",O_RDWR|O_SYNC);
</source>
Now you have a valid file descriptor to access your FPGA.

The O_SYNC option is recommended to avoid Linux to cache the content of /dev/mem and delay any modification done in this file.

To access fpga register, fpgaregs use the ''mmap()'' system call :

<source lang="c">
ptr_fpga = mmap (0, 8192, PROT_READ|PROT_WRITE, MAP_SHARED, ffpga, FPGA_ADDRESS);
</source>

Thanks to this function, fpga registers are accessible directly on memory with pointer ptr_fpga. To read and write in 16bits or in 32 bits we will cast the pointer value in ''unsigned short'' or ''unsigned int'' :

'''16bits'''
''write''
<source lang="c">
*(unsigned short*)(ptr_fpga+(address)) = (unsigned short)value;
</source>
''read''
<source lang="c">
value = *(unsigned short*)(ptr_fpga+(address));
</source>

'''32 bits'''
''write''
<source lang="c">
*(unsigned int*)(ptr_fpga+(address)) = (unsigned short)value;
</source>

''read''
<source lang="c">
value = *(unsigned int*)(ptr_fpga+(address));
</source>

== The problem ==

By default, if the specific ''arm920t'' target is not specified, ''arm-linux-gcc'' will try to generate compatible read/write for all ARM9 model when it access register in 16bits. Indeed it seems that not all ARM9 have 16bits read/write capabilities (''ldrh'' asm instruction).

As the interface between i.MXL and FPGA on APF9328 has no 8bits read/write capabilities, each 8 bits access is recognized by the FPGA as a 16bits access. So on each 16bits access of the i.MXL, FPGA will process two 16bits access instead of 1. That is a problem when accessing a FIFO for example.

To avoid this painful problem don't forget the ''-mcpu=arm920t'' option when compiling ''fpgaregs'' for APF9328.

==Links==
* http://sources.redhat.com/ml/crossgcc/2005-08/msg00120.html : Explanation of the problem.