So our generation is completed successfully now, and next step will be to first export and hardware,
including a big step.
And then we will be launching in SD, right?
So let us proceed by creating a new application project.
We'll just be naming this as TDCi.
OK?
And we'll be invoking an alcohol template.
Now, once we create an application project, we get an idea about what should be the recommended try
for the specific benefit, right?
So here if you consider digits zero, which we enable.
So the most recommended trigger for us is DCP said, I will go ahead to the Helloworld or see right
here now we need to do additional two things.
First one is the exact parameter date, which will give us an idea about what are the different values
we have for our target parameters.
And then the next one is the trial specific to the TDCi, right?
So we'll go ahead.
With adding to you, OK, and here, the driver for us is ditsy.
Yes, start right?
And one more driver file that will be adding is X parameters start, right?
This will give us and enough information required for configuring a variable as well as running.
Right now, we'll go ahead and try to analyze the API that we have for a driver right again.
This will be initialized by considering the scene.
To structure, one of them is instant structure, and another one is on fixed rate, so we'll go ahead
and try to add them both in.
Our main rate to convict structure should be pointed.
OK, so we'll just be naming this GTC config.
The next one is an instance such the that we have, right?
So we'll just be going ahead and will naming it as GTC.
OK, so let's proceed with creation of an initialize function, right?
So we'll just be naming this as GTC in it.
We will require see this variable that will be useful in verifying whether we are getting existing success
or not.
Right.
So the first API that we have that will look for the device, OK, in that and type people is look up
config.
So if we just go to a driver you haven't look upon right here, you just need to pass the device.
So did you see?
Can't think this should be worse to look up on fake, and then here we need to pass a device I.D. So
if you just go to the experimental dot and look for Etsy.
OK, so here we have it.
So here we have our device.
So we just copy this.
Rely on it here, right?
So this will return the DTC config structure, which will be utilizing to initialize our DDCA.
So to perform an initialization, the API that we have is CFD initialized.
So here we have this API, this basically written instead.
So we'll just be going ahead.
First thing it required is an instant structure, which we need less.
Then the config structure to UTC on fake.
OK, and finally then effectively be set.
So that could also be accessed from D.D.S. config so that this conflict can.
Then this operator and we have a visitors rate.
So this complete this step.
Now we will just be verifying whether the students return is existing sets and state so students should
be close to SSD success or it should be close to a single rate.
And if that is the case, we will just be mentioning in and its success rate and we'll just be mentioning
UTC net.
Fee, right?
This is going nowhere near where we are working with an intermediate that you could have, as discussed,
will also be performing a self-test, right?
So that will basically give us an idea where the heart rate is configured correctly.
Right.
So let me just go ahead and try to find out the API that we have for us at this rate.
Those ingredients that you do, we just need to pass an instill structure.
Right?
So we'll updating.
We will be updating the just value, OK, by the value that is written by our self dysfunction here
also.
We just need to pass an instance structure and then will again be performing a comparison.
But this time the message that we'll be sending is self test success rate down here.
We'll just be mentioning cell test fee, right?
So these are the kinds of things that we do to perform an initialization of benefit, right?
So we declare to structure, we utilize lookup config.
OK.
This will lead to the config structure for us.
And then utilizing that, we use CFG initialize API to initialize our benefit.
Right?
Then we are checking whether initialization is successful.
So once the initialization is successful, we are performing a set of this should work OK, and then
we could proceed for development of any.
So let me just go and try to see what code and programming SPG.
So when programming is successful, we'll just be collecting and to get dominance to come for, OK?
And then we'll be running our configuration on an FPGA.
OK, so right click released launch on Hideaway.
So now we'll just be calling after the platform, I didn't see any great.
And this a is not required, so we could just come and do so right, so let's just go ahead and just
relaunch in session.
And no, you could notice that D.C. and they did successful as well as circuit test is also successful.
So this complete step one now will proceed for writing an application, so our agenda will basically
be to generate a fixed fix.
OK?
Later on will be considering some of the examples, such as how we could provide utilizing PPC or utilizing
the DDC to create the fix and then triggering another verification, right?
So first, we'll just be proceeding for creating a fix.
So you have a fundamental idea of utilizing various functions, and then we could just modify this example
a bit so that you would understand the different scenarios where we could utilize that EDC, right?