Yeah. So, we have today information session, let's call it. It's not really a training, it's not hands-on on something. But it tells you about our tool, not so much about our tool itself, we don't need so much to promote the tool, we are market leader with our tools. It is really that you have the benefit from the information that I can provide to you. So, we were invited to tell you about especially tracing. It will be a little bit that I talk also about the basics of using a debugger because the trace itself that we will use cannot be used without a debug system. Now, you need a data connection to set up the systems the right way, so that you can trace. Okay. So, I have everything here on the table that I want to show you. Okay. So, we have basically two parts. Okay. We have two parts, one is our debug system. It is a universal box which has firmware running on it later. For sure, you have a graphical user interface, regular executable, but it works also with Linux and even with macOS. Here comes a specific part, that is the connection to a JTAG port. JTAG is for debugging. So, when you connect this, then this tool becomes specific. In this case, it becomes specific to debug ARM Cores. But they can be combined. So, when we started to support ARM Coes, it was like almost 20 years ago. I'm seven and things like this. Careful, nowadays when we have the seven, its ARMv7, version seven, so it's Cortex. So, this can't connect to such JTAG port. We will see it has basically five signals and that's enough for debugging. When we hear debugging, it's always that you have like taking pictures. You move forward to a situation, maybe it was break point or was single-stepping and then you check the system, and it's like a snapshot only. What we will see most of the time tonight is that you can trace in real time, and so the timing, the performance is correct and that means that you can find even if there is something like a race condition or something. The second part that we connect to the debug system, why are special bars here, is our trace module. So, this trace module is also universal and it becomes also specific with the adapter that we have. So, this adapter has rear and front, two connectors, each one can take 16-bit ETM trace. Usually, we use just one. Some customers have 32, that is the rare case. So, to control this unit and also to setup the target the right way, we need to have them both together. Then it looks a little bit bigger, and it has two connections. But maybe you have a target and you know the target strictly, some are small by energy consumption, by frequency, many reasons to built them small. So, we try to have small connectors. If you watch carefully here, then we have a PCB and we have a smaller PCB logo sandwich on top. You can see also some pages here. There's a different target, but it's the same way to do it. I think when I go over here, you don't see that. Okay. Anyway, do we have like a laser? There you go. Okay. So, yeah. I think the voice is enough, you don't see to see my body on the video all the time. So here, that is our tool and you see that's the full tool with debugger part and trace part debugger cable here, JTAG and here is what we call pre-processor and that is available in different ways. So, this specific part for ETM tracing can be for a serial ETM, or it can be for a parallel ETM. Then, we have a connector, because there's only one connector, I see that, that is a serial ETM. This port that I brought is really good port. Meanwhile, a few years old. That's an OMAP 4430. So, it has SOC that has several cores inside. Not only ARM, there's also DSP. It's a port from TI's or it's TIDSP inside. So, we will connect to this port, and usually this port has no trace connector. So, what we did was this port here, you can see that here on our screen also. This port has the JTAG connector and TI. Typically, it has 14 pins. Five JTAG typical signals TI, TDO, and we will see them on the next slide, I think. Then, we have here on this port an LCD port. LCDs and GPIO. GPIO can be multiplexed. So, we will switch it and use the trace capability to trace signals of this OMAP here from this connector. Here, we have the rear JTAG connector, 14 pin. Here's the LCD connector. Well, it's no longer LCD, it's now trace and brings out here breakout to the matching connectors for tracing. Okay. So, let's see. First, I connect. The tool was USB. Then the power of the tool comes from here. Then, I connect here, this pre-processor with little flex cable to the port. Then, we can connect power to the target's. Should be everything. Okay. Well, if I'm checking this so carefully, it's really easy to do. But I have other boards with me. So, I have here also called Odroid. So, that's ARMv8. At the very end, we could have a look also for that. Okay. So, that is the connection that we have and this is how it is finally connected to tool. But this one here is a differet kind of adapter. It's a CombiProbe. So, we have a different connector in use. What I use is a Mictor 38. This a little adapter. If you buy audio cable, it will be for ARM, it has 20 pins which doesn't match to the foreign pin connector. So, we have adapter and then we have TI-14 here. That is not a pixel error here on the screen, that is real. That white spot is a lock. So, it's locked, so you cannot put it the wrong way on adapter. Okay. That's regarding the board. Then, these are the different pre-processors. So, that's really the one that I have. I use just 16 bit, not 32. This one is a newer generation, has some TAG connector instead with 60 pin. What they have in common? They have flex cables here. They have, here you see it, the Golden part. Our breath. I think it's really gold. That is a ground plane. That is for signal integrity and also for ground connection. So, that is really the advantage of this connector to this, and it has 16 pins on almost the same size, and it's for higher frequencies up to 12th gigabit per second. Sorry, that is this one. But it's even only 40 pins. Because that our differential lines, so there are always two lines for one lane of serial trace port. Okay. So, that is how it looks like on our Mictor-38 connector. You see, it's a mix of debug signals. I mark them green and the trace signals. So, you see our connector was Mictor-38, has trace data zero, one, two, three, up to seven and on the other side, we have eight to 15. Trace clock is here and voltage reference for the traces there. Same with JTAG. So, voltage reference and then the essential JTAG signals are here. You might know them already, maybe not. So, test, the T is always test. You see the T is almost everywhere. Later we'll tap also test access port and so on. So, test data in, test that out and so on and so on. Also, this is a slideshow which is nice to see and follow tonight. But if you need more information I have on the last pages typically links for other files and also Dave has files available. So, you can put them on your server or you can get them from our server.
