CE515 Advanced Processor Architecture and SoC Design - Revision history

Nico at 16:59, 6 October 2021

2021-10-06T16:59:06Z

← Older revision		Revision as of 16:59, 6 October 2021
Line 46:		Line 46:
	<syntaxhighlight lang="Makefile" line='line'>		<syntaxhighlight lang="Makefile" line='line'>
	CC=arm-none-eabi-gcc		CC=arm-none-eabi-gcc
	CFLAGS=-mcpu=cortex-a9 -mfpu=~~vfpv3~~ -mfloat-abi=hard -c -Wall -I./include		CFLAGS=-mcpu=cortex-a9 -mfpu=neon -mfloat-abi=hard -c -Wall -I./include
	LDFLAGS=-mcpu=cortex-a9 -mfpu=~~vfpv3~~ -mfloat-abi=hard -Wl,-build-id=none -specs=Xilinx.spec -Wl,-T -Wl,lscript.ld -Llib		LDFLAGS=-mcpu=cortex-a9 -mfpu=neon -mfloat-abi=hard -Wl,-build-id=none -specs=Xilinx.spec -Wl,-T -Wl,lscript.ld -Llib
	LIBS=-Wl,--start-group,-lxil,-lgcc,-lc,--end-group		LIBS=-Wl,--start-group,-lxil,-lgcc,-lc,--end-group

Line 73:		Line 73:
	arm-none-eabi-gcc -c -Wall -I./include -o main.o main.c		arm-none-eabi-gcc -c -Wall -I./include -o main.o main.c
	arm-none-eabi-gcc -c -Wall -I./include -o platform.o platform.c		arm-none-eabi-gcc -c -Wall -I./include -o platform.o platform.c
	arm-none-eabi-gcc -mcpu=cortex-a9 -mfpu=~~vfpv3~~ -mfloat-abi=hard -Wl,-build-id=none -specs=Xilinx.spec -Wl,-T -Wl,lscript.ld -Llib -o main.elf main.o platform.o -Wl,--start-group,-lxil,-lgcc,-lc,--end-group		arm-none-eabi-gcc -mcpu=cortex-a9 -mfpu=neon -mfloat-abi=hard -Wl,-build-id=none -specs=Xilinx.spec -Wl,-T -Wl,lscript.ld -Llib -o main.elf main.o platform.o -Wl,--start-group,-lxil,-lgcc,-lc,--end-group
	$		$
	</syntaxhighlight>		</syntaxhighlight>

Nico at 08:38, 6 October 2021

2021-10-06T08:38:40Z

← Older revision		Revision as of 08:38, 6 October 2021
Line 95:		Line 95:

	<syntaxhighlight lang="text">		<syntaxhighlight lang="text">
	connect -host ~~localhost~~ -port 3121		connect -host 127.0.0.1 -port 3121
	targets		targets
	targets 2		targets 2

Nico at 07:29, 6 October 2021

2021-10-06T07:29:58Z

← Older revision		Revision as of 07:29, 6 October 2021
Line 108:		Line 108:
	For the link settings Baud rate: 115200, 8 bits data, 1 bit stop, without parity check.		For the link settings Baud rate: 115200, 8 bits data, 1 bit stop, without parity check.

	* In <syntaxhighlight lang="text" inline>~~xmd~~</syntaxhighlight>, now type the following commands:		* In <syntaxhighlight lang="text" inline>xsct</syntaxhighlight>, now type the following commands:

	<syntaxhighlight lang="text">		<syntaxhighlight lang="text">
Line 119:		Line 119:
	* Validate the correct execution of the program.		* Validate the correct execution of the program.

	Before continuing with the next exercises, open 3 different terminals: the first one will be used to build the executable file (with ~~cs-~~make); the second one will be used to transfer the program on the board (with <syntaxhighlight lang="text" inline>~~xmd~~</syntaxhighlight>); the last one will be used to observe the results. Note that for the second terminal, a single <syntaxhighlight lang="text" inline>~~xmd~~</syntaxhighlight> session can be used to transfer multiple programs and that the start command will automatically detect if a new version of the program is available and transfer it on the board.		Before continuing with the next exercises, open 3 different terminals: the first one will be used to build the executable file (with make); the second one will be used to transfer the program on the board (with <syntaxhighlight lang="text" inline>xsct</syntaxhighlight>); the last one will be used to observe the results. Note that for the second terminal, a single <syntaxhighlight lang="text" inline>xsct</syntaxhighlight> session can be used to transfer multiple programs and that the start command will automatically detect if a new version of the program is available and transfer it on the board.

	== Timming ==		== Timming ==

Nico at 11:53, 5 October 2021

2021-10-05T11:53:10Z

← Older revision		Revision as of 11:53, 5 October 2021
Line 128:		Line 128:

	<syntaxhighlight lang="C" line='line'>		<syntaxhighlight lang="C" line='line'>
	#include ~~<xscutimer~~.h>		#include "xtime_l.h"
	</syntaxhighlight>		</syntaxhighlight>

Nico at 18:39, 4 October 2021

2021-10-04T18:39:50Z

← Older revision		Revision as of 18:39, 4 October 2021
Line 128:		Line 128:

	<syntaxhighlight lang="C" line='line'>		<syntaxhighlight lang="C" line='line'>
	#include <~~xtime_l~~.h>		#include <xscutimer.h>
	</syntaxhighlight>		</syntaxhighlight>

Line 159:		Line 159:
	* Observe the assembly routine generated by the compiler with the command:		* Observe the assembly routine generated by the compiler with the command:
	<syntaxhighlight lang="text">		<syntaxhighlight lang="text">
	$arm-~~xilinx~~-eabi-gcc -S neon.c -o neon.s		$arm-none-eabi-gcc -S neon.c -o neon.s
	</syntaxhighlight>		</syntaxhighlight>
	Locate the NEON instructions and compare them to the ones in <syntaxhighlight lang="text" inline>neon.c</syntaxhighlight>.		Locate the NEON instructions and compare them to the ones in <syntaxhighlight lang="text" inline>neon.c</syntaxhighlight>.

Nico at 16:54, 4 October 2021

2021-10-04T16:54:44Z

← Older revision		Revision as of 16:54, 4 October 2021
Line 71:		Line 71:
	<syntaxhighlight lang="text">		<syntaxhighlight lang="text">
	$ make		$ make
	arm-~~xilinx~~-eabi-gcc -c -Wall -I./include -o main.o main.c		arm-none-eabi-gcc -c -Wall -I./include -o main.o main.c
	arm-~~xilinx~~-eabi-gcc -Wl,-T -Wl,lscript.ld -~~L./lib~~ -o main.elf main.o platform.o -Wl,--start-group,-lxil,-lgcc,-lc,--end-group		arm-none-eabi-gcc -c -Wall -I./include -o platform.o platform.c
			arm-none-eabi-gcc -mcpu=cortex-a9 -mfpu=vfpv3 -mfloat-abi=hard -Wl,-build-id=none -specs=Xilinx.spec -Wl,-T -Wl,lscript.ld -Llib -o main.elf main.o platform.o -Wl,--start-group,-lxil,-lgcc,-lc,--end-group
	$		$
	</syntaxhighlight>		</syntaxhighlight>
Line 91:		Line 92:
	</syntaxhighlight>		</syntaxhighlight>

	* Type the following commands in xsct (one at a time):		* Type the following commands in <syntaxhighlight lang="text" inline>xsct</syntaxhighlight> (one at a time):

	<syntaxhighlight lang="text">		<syntaxhighlight lang="text">
Line 102:		Line 103:
	</syntaxhighlight>		</syntaxhighlight>

	The function <syntaxhighlight lang="text" inline>ps7_init()</syntaxhighlight> permits to activate the clock, the memory controller, and the peripherals (UART).		The function <syntaxhighlight lang="text" inline>ps7_init()</syntaxhighlight> permits to activate the clock, the memory controller, and the peripherals (UART). This function have to be called before writing to the memory.

	* In another terminal, observe the [https://en.wikipedia.org/wiki/Serial_port serial port] with a terminal (e.g. <syntaxhighlight lang="text" inline>putty</syntaxhighlight> in Windows).		* In another terminal, observe the [https://en.wikipedia.org/wiki/Serial_port serial port] with a terminal (e.g. <syntaxhighlight lang="text" inline>putty</syntaxhighlight> in Windows).

Nico at 16:37, 4 October 2021

2021-10-04T16:37:04Z

← Older revision		Revision as of 16:37, 4 October 2021
Line 22:		Line 22:
	#include <stdio.h>		#include <stdio.h>
	#include "platform.h"		#include "platform.h"
			#include "xil_printf.h"


	int main()		int main()
	{		{
	init_platform();		init_platform();

	~~printf~~("Hello ~~world~~");		print("Hello World\n\r");

	return 0;		cleanup_platform();
			return 0;
	}		}
	</syntaxhighlight>		</syntaxhighlight>
Line 42:		Line 45:

	<syntaxhighlight lang="Makefile" line='line'>		<syntaxhighlight lang="Makefile" line='line'>
	CC=arm-~~xilinx~~-eabi-gcc		CC=arm-none-eabi-gcc
	CFLAGS=-c -Wall -I./include		CFLAGS=-mcpu=cortex-a9 -mfpu=vfpv3 -mfloat-abi=hard -c -Wall -I./include
	LDFLAGS=-Wl,-T -Wl,lscript.ld -~~L./lib~~		LDFLAGS=-mcpu=cortex-a9 -mfpu=vfpv3 -mfloat-abi=hard -Wl,-build-id=none -specs=Xilinx.spec -Wl,-T -Wl,lscript.ld -Llib
	LIBS=-Wl,--start-group,-lxil,-lgcc,-lc,--end-group		LIBS=-Wl,--start-group,-lxil,-lgcc,-lc,--end-group

	all: main.elf		all: main.elf


	main.o: main.c		main.o: main.c

Nico at 16:28, 4 October 2021

2021-10-04T16:28:33Z

← Older revision		Revision as of 16:28, 4 October 2021
Line 65:		Line 65:
	The four first lines are simple variables. The rest of the file is composed of 4 rules. The first line of each rule defines the name of the target and its associated dependencies. For each rule, <syntaxhighlight lang="text" inline>make</syntaxhighlight> checks the modification date of the dependencies compared to the one of the target. If one of the dependencies has been modified after the target, <syntaxhighlight lang="text" inline>make</syntaxhighlight> run the command(s) located after the first line (and which have to begin by tab).		The four first lines are simple variables. The rest of the file is composed of 4 rules. The first line of each rule defines the name of the target and its associated dependencies. For each rule, <syntaxhighlight lang="text" inline>make</syntaxhighlight> checks the modification date of the dependencies compared to the one of the target. If one of the dependencies has been modified after the target, <syntaxhighlight lang="text" inline>make</syntaxhighlight> run the command(s) located after the first line (and which have to begin by tab).

	* To build the project invoke <syntaxhighlight lang="text" inline>~~cs-~~make</syntaxhighlight> at the prompt. You should observe the following output:		* To build the project invoke <syntaxhighlight lang="text" inline>make</syntaxhighlight> at the prompt. You should observe the following output:

	<syntaxhighlight lang="text">		<syntaxhighlight lang="text">
	$ ~~cs-~~make		$ make
	arm-xilinx-eabi-gcc -c -Wall -I./include -o main.o main.c		arm-xilinx-eabi-gcc -c -Wall -I./include -o main.o main.c
	arm-xilinx-eabi-gcc -Wl,-T -Wl,lscript.ld -L./lib -o main.elf main.o platform.o -Wl,--start-group,-lxil,-lgcc,-lc,--end-group		arm-xilinx-eabi-gcc -Wl,-T -Wl,lscript.ld -L./lib -o main.elf main.o platform.o -Wl,--start-group,-lxil,-lgcc,-lc,--end-group
Line 83:		Line 83:
	Finally, switch on the SW4 switch (LD11 diode should be on).		Finally, switch on the SW4 switch (LD11 diode should be on).

	* Start the <syntaxhighlight lang="text" inline>~~xmd~~</syntaxhighlight> software in a terminal:		* Start the <syntaxhighlight lang="text" inline>xsct</syntaxhighlight> software in a terminal:

	<syntaxhighlight lang="text">		<syntaxhighlight lang="text">
	$ ~~xmd~~		$ xsct
	</syntaxhighlight>		</syntaxhighlight>

	* Type the following commands in ~~xmd~~:		* Type the following commands in xsct (one at a time):

	<syntaxhighlight lang="text">		<syntaxhighlight lang="text">
	connect ~~arm hw~~		connect -host localhost -port 3121
			targets
			targets 2
	source ps7_init.tcl		source ps7_init.tcl
	ps7_init		ps7_init
Line 106:		Line 108:

	<syntaxhighlight lang="text">		<syntaxhighlight lang="text">
	~~start~~		con
	stop		stop
	</syntaxhighlight>		</syntaxhighlight>

Nico at 13:59, 4 October 2021

2021-10-04T13:59:45Z

← Older revision		Revision as of 13:59, 4 October 2021
Line 37:		Line 37:
	* Open a terminal (<syntaxhighlight inline lang="text">cmd.exe</syntaxhighlight>) and go to your project location (using <syntaxhighlight lang="text" inline>cd</syntaxhighlight>).		* Open a terminal (<syntaxhighlight inline lang="text">cmd.exe</syntaxhighlight>) and go to your project location (using <syntaxhighlight lang="text" inline>cd</syntaxhighlight>).

	* Execute the following script: <syntaxhighlight lang="text" inline>C:\Xilinx\~~Vivado~~\~~2016~~.4\settings64.bat</syntaxhighlight>. This script modifies the PATH evironment variable and allows to call the Xilinx tools directly form the command line.		* Execute the following script: <syntaxhighlight lang="text" inline>C:\Xilinx\Vitis\2019.2\settings64.bat</syntaxhighlight>. This script modifies the PATH evironment variable and allows to call the Xilinx tools directly form the command line.

	* Build process is fully automatized using [https://en.wikipedia.org/wiki/Make_(software) <syntaxhighlight lang="text" inline>make</syntaxhighlight>]. Open the <syntaxhighlight lang="text" inline>Makefile</syntaxhighlight> in your editor:		* Build process is fully automatized using [https://en.wikipedia.org/wiki/Make_(software) <syntaxhighlight lang="text" inline>make</syntaxhighlight>]. Open the <syntaxhighlight lang="text" inline>Makefile</syntaxhighlight> in your editor:

Nico at 09:34, 10 June 2021

2021-06-10T09:34:29Z

← Older revision		Revision as of 09:34, 10 June 2021
Line 1:		Line 1:
	This course is separated into 2 parts. The first one deals will SoC design and programming and is supervised by David Hély. The second one is focused on the SIMD extension present inside ARM architecture. The goal of this lab is implement and develop algorithms (functions) optimized for the NEON extension included in the architecture ARMv7-A et ARMv7-R. Slides of the course can be found [https://nicolas-barbot.ovh/wiki/pool/neon_en.pdf here]. This course requires the basic knowledge of a micro-controller architecture and classical C programming. Processing will run over a Zynq 7000 SoC which contain an ARM Cortex A9 MP Core. Performance of the NEON engine will be compared to the performance of classical implementation (C function executed on the ARM core).		This course is separated into 2 parts. The first one deals will SoC design and programming and is supervised by David Hély. The second one is focused on the SIMD extension present inside ARM architecture. The goal of this lab is implement and develop algorithms (functions) optimized for the NEON extension included in the architecture ARMv7-A et ARMv7-R. Slides of the course can be found [https://nicolas-barbot.ovh/wiki/pool/neon_en.pdf here]. This course requires the basic knowledge of a micro-controller architecture and classical C programming. Processing will run over a [https://www.xilinx.com/ Xilinx] [https://www.xilinx.com/products/silicon-devices/soc/zynq-7000.html Zynq 7000] SoC which contain an ARM Cortex A9 MP Core. Performance of the NEON engine will be compared to the performance of classical implementation (C function executed on the ARM core).

	== Introduction ==		== Introduction ==
Line 210:		Line 210:

	The objective of this part is to start a Linux distribution on the Zybo development board and to evaluate the performance of our edge detection application on a bitmap image. Several distribution are available to run over Zynq 7000 SoC. Some of them provide a file system only in the RAM. Some others can use the file system from an external flash memory (SD card).		The objective of this part is to start a Linux distribution on the Zybo development board and to evaluate the performance of our edge detection application on a bitmap image. Several distribution are available to run over Zynq 7000 SoC. Some of them provide a file system only in the RAM. Some others can use the file system from an external flash memory (SD card).
	Linaro distribution is a Ubuntu based distribution and provide the same tools than a desktop distribution (graphical user interface). Before doing the following operations, check that the Zybo board is switch off. Also, this exercise can be realize with a Raspberry Pi 2 or 3 ([https://nicolas-barbot.ovh/wiki/pool/rpi.zip <syntaxhighlight lang="text" inline>rpi.zip</syntaxhighlight>]).		Linaro distribution is a Ubuntu based distribution and provide the same tools than a desktop distribution (graphical user interface). Before doing the following operations, check that the Zybo board is switch off. Also, this exercise can be realize with a [https://en.wikipedia.org/wiki/Raspberry_Pi Raspberry] Pi 2 or 3 ([https://nicolas-barbot.ovh/wiki/pool/rpi.zip <syntaxhighlight lang="text" inline>rpi.zip</syntaxhighlight>]).

	* Insert the SD card in the slot located under the board.		* Insert the SD card in the slot located under the board.