Lecture 1. Intro to Module and Tool-Chain

Size: px

Start display at page:

Download "Lecture 1. Intro to Module and Tool-Chain"

Harold Williamson
5 years ago
Views:

1 Lecture 1 Module Introduction, Semester Schedule, Feedback to Exercis, Introduction to, Information to Literature BTF Digital Electronics 2 Feb. 20, 2015 Bern University of Applied Sciences

2 Agenda Rev. ab24f70 1.2

3 Module Description Accordingly to the official module description : BTF4220-de.xml The following major topics are going to be covered in the course: Digital function blocks such as counters, multiplexers, comparators, adders, etc. VHDL syntax and design methods with VHDL Get practical experience during labor exercises Test-bench and simulation of VHDL designed circuits Rev. ab24f70 1.3

4 Module Documents Rev. ab24f70 1.4

5 Module Documents Rev. ab24f70 1.4

6 Module Elements lecture [2/w] exercises Advanced Electronics Digital laboratory [2/s] Analogue lecture [2/w] laboratory [2/s] exercises Rev. ab24f70 1.5

7 Module Grading Rev. ab24f70 1.6

8 Module Grading Advanced Electronics [BTF4220] Analogue Digital Exam [40%] Lab [10%] Exam [40%] Lab [10%] Rev. ab24f70 1.6

9 Module Grading Advanced Electronics [BTF4220] Analogue Digital Exam [40%] Lab [10%] Exam [40%] Lab [10%] A : 90 % B : 80 % C : 70 % D : 60 % E : 50 % FX : > 35 % F : 35 % Rev. ab24f70 1.6

10 Module Grading Advanced Electronics [BTF4220] Analogue Digital Exam [40%] Lab [10%] Exam [40%] Lab [10%] A : 90 % B : 80 % C : 70 % D : 60 % E : 50 % FX : > 35 % F : 35 % Rev. ab24f70 1.6

11 Module Grading Advanced Electronics [BTF4220] Analogue Digital Exam [40%] Lab [10%] Exam [40%] Lab [10%] A : 90 % B : 80 % C : 70 % D : 60 % E : 50 % FX : > 35 % F : 35 % The module grading is described more detailed by the document BTF4220 Berechnung der Modulnote/Calculation de la note final. Rev. ab24f70 1.6

12 Module Grading Advanced Electronics [BTF4220] Analogue Digital Exam [40%] Lab [10%] Exam [40%] Lab [10%] A : 90 % B : 80 % C : 70 % D : 60 % E : 50 % FX : > 35 % F : 35 % It is the students responsibility to get missed information, documents and to follow the course carefully. Rev. ab24f70 1.6

13 Module Schedule Date WoS WoY Description module introduction VHDL intro and design units programming paradigm combinational logic and test-bench hands-on combinational logic (parallel adder) theorie sequential logic easter holidays hands-on sequential logic (serial adder) VHDL operators and libraries data objects theorie FSM models hands-on FSM models Special project week basic digital circuits hands-on (calculator and/or others) exam exam feedback There is a special physics workshop (no course) Individual preparation is without lecturer on the Ascension day [Auffahrt] (WoS 14 WoY 22) Maybe individual hands-on lecture the Friday before Easter holidays Rev. ab24f70 1.7

14 Software used during the course OS We will work on Linux only (Ubuntu LTS or Debian stable). Get information to some Linux basics on our wiki CS There is a basic command overview on course website. (home work: install BFH Linux, Debian, or Ubuntu Get some initial experience to the described Linux commands) Rev. ab24f70 1.8

15 Software used during the course OS We will work on Linux only (Ubuntu LTS or Debian stable). Get information to some Linux basics on our wiki CS There is a basic command overview on course website. (home work: install BFH Linux, Debian, or Ubuntu Get some initial experience to the described Linux commands) Editor I recommend using Emacs as text editor. It is an open source and multi-platform software and very handy for VHDL too Alternatively use systems default GEdit syntax highlighting only. Rev. ab24f70 1.8

16 Software used during the course OS We will work on Linux only (Ubuntu LTS or Debian stable). Get information to some Linux basics on our wiki CS There is a basic command overview on course website. (home work: install BFH Linux, Debian, or Ubuntu Get some initial experience to the described Linux commands) Editor I recommend using Emacs as text editor. It is an open source and multi-platform software and very handy for VHDL too Alternatively use systems default GEdit syntax highlighting only. Make We will build our designs on command-line by using the build-system make vortraege/make_inhalt.en.html (home work : Read and do the examples given) Rev. ab24f70 1.8

17 Software used during the course VM As a vitalization environment use VirtualBox it is free and intuitive as well as multi-platform compatible if you do not want installing a bearmetal Linux. Rev. ab24f70 1.9

18 Software used during the course VM As a vitalization environment use VirtualBox it is free and intuitive as well as multi-platform compatible if you do not want installing a bearmetal Linux. VCS You will use Git to get the course code snippets as well as proposed solutions. (home work : Read the first chapters in online, opensource Git tutorial book) Rev. ab24f70 1.9

19 Software used during the course VM As a vitalization environment use VirtualBox it is free and intuitive as well as multi-platform compatible if you do not want installing a bearmetal Linux. VCS You will use Git to get the course code snippets as well as proposed solutions. (home work : Read the first chapters in online, opensource Git tutorial book) Git is more than a method distributing code snippets. We recommend using Git for your daily business in engineering where it comes to source code or other plain text resource management. Rev. ab24f70 1.9

20 What means VCS VCS : Version Control System Rev. ab24f

21 What means VCS VCS : Version Control System It records chances to a file or file-set over time Rev. ab24f

22 What means VCS VCS : Version Control System It records chances to a file or file-set over time Not only for source files also binary files can be controlled by a VCS e.g. as a web designer tracking images Rev. ab24f

23 What means VCS VCS : Version Control System It records chances to a file or file-set over time Not only for source files also binary files can be controlled by a VCS e.g. as a web designer tracking images Allows to revert to a previous state Rev. ab24f

24 What means VCS VCS : Version Control System It records chances to a file or file-set over time Not only for source files also binary files can be controlled by a VCS e.g. as a web designer tracking images Allows to revert to a previous state Shows who modified what when Rev. ab24f

25 What means VCS VCS : Version Control System It records chances to a file or file-set over time Not only for source files also binary files can be controlled by a VCS e.g. as a web designer tracking images Allows to revert to a previous state Shows who modified what when You can recover easily Rev. ab24f

26 What means VCS VCS : Version Control System It records chances to a file or file-set over time Not only for source files also binary files can be controlled by a VCS e.g. as a web designer tracking images Allows to revert to a previous state Shows who modified what when You can recover easily Very little overhead Rev. ab24f

27 Local Version Control Systems Copy files into an other directory - timestamped if user is clever Simplest method Very little control mechanism It is easy to forget proper working directory hence wrong file will be accidentally modified Rev. ab24f

Local Version Control Systems Copy files into an other directory - timestamped if user is clever Simplest method Very little control mechanism It is easy to forget proper working directory hence

28 Local Version Control Systems Copy files into an other directory - timestamped if user is clever Simplest method Very little control mechanism It is easy to forget proper working directory hence wrong file will be accidentally modified Programmers developed a simple database tracking mechanism to deal with the issues mentioned The VCS RCS was born that time and is still used nowadays RCS (Revision Control System) works on diff patch approach Img. ref.: Rev. ab24f

29 Centralized Version Control Systems Next issue was that people need to collaborate with developers on other systems. A sever based approach was needed (the server acts as a centralized source distributor and repository management unit) Drawbacks are single point of failure, nobody can collaborate without server, risky to loos everything Rev. ab24f

30 Centralized Version Control Systems Next issue was that people need to collaborate with developers on other systems. A sever based approach was needed (the server acts as a centralized source distributor and repository management unit) Therefore a Centralized Version Control System (CVCS) were developed CVC Systems, such as CVS, Perforce, and Subversion, have a single central place - server. Advantages are, everyone knows what everyone else is doing Administrators have fine-grained permission control Img. ref.: Drawbacks are single point of failure, nobody can collaborate without server, risky to loos everything Rev. ab24f

31 Distributed Version Control Systems Distributed Version Control Systems (DVCSs) stepped in DVC Systems, such as Git, Mercurial, Bazaar or Darcs, are nowadays standard The major difference is clients not only checkout a work-tree copy also they fully mirror the repository Rev. ab24f

Distributed Version Control Systems Distributed Version Control Systems (DVCSs) stepped in DVC Systems, such as Git, Mercurial, Bazaar or Darcs, are nowadays standard The major difference is clients

32 Distributed Version Control Systems Distributed Version Control Systems (DVCSs) stepped in DVC Systems, such as Git, Mercurial, Bazaar or Darcs, are nowadays standard The major difference is clients not only checkout a work-tree copy also they fully mirror the repository No longer reliable on an online available central server at anytime Off-site full backups of all the data Those system deal pretty well with several remote repository e.g. for libraries Several new smart workflows are possible Img. ref.: Rev. ab24f

com List of file based changes Information is keep as a

33 Git concept Img. ref.: Img. ref.: List of file based changes Information is keep as a set of files Set of snapshots of a mini filesystem No changes means no snapshot of that part Rev. ab24f

34 Git concept Local operations : Most operations in Git only need local resources and files to operate. Due to local file operation, Git commands don t suffer from network latency. If you browse history Git doesn t need a server connection. An other advantage is the offline-tracking capability Rev. ab24f

35 Git concept Local operations : Most operations in Git only need local resources and files to operate. Due to local file operation, Git commands don t suffer from network latency. If you browse history Git doesn t need a server connection. An other advantage is the offline-tracking capability Data integrity : Git is using SHA-1 hash numbers for integrity check. Every file will be check-summed before stored. Hence no modification can be made without letting Git know of the change. Rev. ab24f

36 Git concept Local operations : Most operations in Git only need local resources and files to operate. Due to local file operation, Git commands don t suffer from network latency. If you browse history Git doesn t need a server connection. An other advantage is the offline-tracking capability Data integrity : Git is using SHA-1 hash numbers for integrity check. Every file will be check-summed before stored. Hence no modification can be made without letting Git know of the change. Three states : Git has three stages where files can reside in. Committed, modified and staged. Rev. ab24f

37 The three stages of Git Img. ref.: Rev. ab24f

38 The three stages of Git Img. ref.: Committed : The data is safely stored in your local database Rev. ab24f

39 The three stages of Git Img. ref.: Committed : The data is safely stored in your local database Modified : There are changes on files not committed to the database yet Rev. ab24f

The three stages of Git Img. ref.: http://git-scm.

40 The three stages of Git Img. ref.: Committed : The data is safely stored in your local database Modified : There are changes on files not committed to the database yet Staged : There are modified file in its current version marked to go into the next commit snapshot Rev. ab24f

41 Don t miss the chance It was quite a bit of information and there is a big chance to get lost. So, don t waste your time...learn Git! Official Git book Git wiki on kernel.org Take a tour Learn Git visually http: //marklodato.github.io/visual-git-guide/index-en.html Rev. ab24f

42 Processor vs ASIC Rev. ab24f

43 Universal Structure Rev. ab24f

44 AND in a LUT Rev. ab24f

45 SPLD SPLD : (Simple Programmable Logic Device) Rev. ab24f

46 Unprogrammed PLD Rev. ab24f

47 Programmed PLD irreversible universal structure OR array Rev. ab24f

48 FPGA Structure Rev. ab24f

49 CLB Element Rev. ab24f

50 IO Block Rev. ab24f

51 Block RAM Rev. ab24f

52 DSP Element Rev. ab24f

53 DSP Element Rev. ab24f

54 FPGA vs uc Summary An FPGA provides several configurable slices (LUTs, Mux, FFs), Block RAM elements, clock and signal routing resource etc. Rev. ab24f

55 FPGA vs uc Summary An FPGA provides several configurable slices (LUTs, Mux, FFs), Block RAM elements, clock and signal routing resource etc. Based on the macro elements we are able to realize any kind of function Rev. ab24f

56 FPGA vs uc Summary An FPGA provides several configurable slices (LUTs, Mux, FFs), Block RAM elements, clock and signal routing resource etc. Based on the macro elements we are able to realize any kind of function Due to the options we have. An FPGA is like a canvas. VHDL helps describing the function modle. The tool-chain realizes our system based on our description Rev. ab24f

57 FPGA vs uc Summary An FPGA provides several configurable slices (LUTs, Mux, FFs), Block RAM elements, clock and signal routing resource etc. Based on the macro elements we are able to realize any kind of function Due to the options we have. An FPGA is like a canvas. VHDL helps describing the function modle. The tool-chain realizes our system based on our description A uc is a static hardware (unchangeable) hence we program it by using the static and available resources. Rev. ab24f

58 FPGA vs uc Summary An FPGA provides several configurable slices (LUTs, Mux, FFs), Block RAM elements, clock and signal routing resource etc. Based on the macro elements we are able to realize any kind of function Due to the options we have. An FPGA is like a canvas. VHDL helps describing the function modle. The tool-chain realizes our system based on our description A uc is a static hardware (unchangeable) hence we program it by using the static and available resources. Pros Cons flexible well skilled designer FPGA fast solution longer time to marked chap compared to ASIC short time to market bad performance uc low unit cost less flexible Rev. ab24f

Computer Science Design I Version Control with Git

Computer Science Design I Version Control with Git Department of Electrical Engineering & Computer Science Information Technology & Telecommunications Research Center The University of Kansas annguyen@ittc.ku.edu