1
00:00:02,740 --> 00:00:09,790
See simulation and RTL simulation work to debugging approaches we usually use during high level syntheses

2
00:00:09,790 --> 00:00:10,510
designed for.

3
00:00:11,050 --> 00:00:14,240
But how can we debug our design on the board at runtime?

4
00:00:14,830 --> 00:00:21,670
This section will explain how to use an integrated logic analyzer IP to perform this task.

5
00:00:27,310 --> 00:00:34,120
This section's main goal is to introduce the integrated logic analyzer LRIP in reverse order to monitor

6
00:00:34,120 --> 00:00:38,380
design signals at runtime while the circuit is running inside FPGA.

7
00:00:39,130 --> 00:00:46,690
To achieve this goal, we will attach an IP to our parallel to Sariel to parallel design explained previously

8
00:00:46,690 --> 00:00:50,080
in discourse and monitor its signals at runtime.

9
00:00:56,120 --> 00:00:58,290
These are the objectives of this section.

10
00:00:58,790 --> 00:01:07,430
Understanding the concept behind the LRIP customizer LRIP, using the Iola IP to monitor signals in

11
00:01:07,430 --> 00:01:08,540
unnaturalness design.

12
00:01:13,690 --> 00:01:20,110
This section consists of four lectures, this video as the first lecture clarifies the goal of this

13
00:01:20,110 --> 00:01:27,700
section and it's a structure, the next lecture defines the integrated logic analyzer IP and how to

14
00:01:27,700 --> 00:01:29,170
customize that environment.

15
00:01:30,040 --> 00:01:36,940
The third lecture explains how to instantiate annihilate in Rivaldo and connect that to a design and

16
00:01:36,940 --> 00:01:38,710
monitor the runtime signals.

17
00:01:39,790 --> 00:01:45,700
The last lecture, as usual, gives you a couple of exercises to master the techniques explained throughout

18
00:01:45,700 --> 00:01:46,300
this section.

19
00:01:49,640 --> 00:01:55,610
After finishing the section, you will be able to customize and isolate and connect that to a design

20
00:01:55,610 --> 00:02:00,710
in regards to monitor the runtime signals of a running design inside the bases.

21
00:02:00,710 --> 00:02:01,310
Three report.

22
00:02:04,850 --> 00:02:09,230
The next lecture will define the IP and explain how to customize the.

23
00:02:13,270 --> 00:02:19,390
These are our takeaway messages, monitoring the signals inside, and if PJ is a technique to debug

24
00:02:19,390 --> 00:02:21,220
our design at runtime.

25
00:02:24,300 --> 00:02:28,860
Mother provides us with an iron IP that enables runtime debugging.

26
00:02:33,030 --> 00:02:35,930
Now, the quiz question, what is the logic analyzable?
