Arun Pradhan

I have 20 years of experience in, uh, digital signal processing and embedded Software design, and I've experienced in various platforms, Uh, DSP, a risk score. I work in the domain of, uh, cable electronics, telecommunications, Automotive, defense and security. I work in the area of audio, acoustic speech, Competition, image processing, also in physical layer signal processing. I use language programming language c, c plus plus, MATLAB, sometimes Python. I love to design embedded systems, uh, to implement real time signal processing algorithms and integration into the framework to enable the applications.

The impact of this video on the system is a critical or noncritical, uh, for the performance of systems? Uh, performance I mean, here, functional performance and system performance, like, latency, and, you know, throughput and, uh, power efficiency? So What is that? Yeah, man. I cannot do this. Is it? No. I don't know.

Uh

Well, architecture should be scalable in terms of you know, It has to be, uh, first, implement the very basic functionalities of the computations, uh, that maps to the hardware architecture. I mean, the data path, uh, especially the instruction in top 226. Uh, so that in any kind of note code of computation, those are well optimized using the processor's instruction set. And then using those Low level functions, which has already been optimized in the 26, will be called or will be used to develop the, APIs and creative flow. Conditional code or control code does not need not to be optimized, but So we will design to handle the flow for that. You know? All the error Reporting and everything are taken care. And finally, these are, uh, these all these blocks will be integrated in terms of APIs to create a pipeline. And those sets of APIs have been provided, uh

Well, in a bit of software development, as I said, it Covers of, uh, interior, uh, functional timelines in terms of user stories And, uh, it's easiest to do this in terms of task, hence of task. And, uh, the task status would be reported in terms of, Completed or input. This are done. And this would be log attached to your 3 tasks. For test and debugging. And, Those who did peer reviewed by, uh, the team members. So, uh, every Task need to need to have short term score to have, uh, you know, continuously Lee evolving, uh, status, and it should be reviewed in Standard meeting, the status, and the failure of the blockage. So this would be some continuous flow of, uh, improving so that it should cover up all the subtask tasks, and he just wish to complete the whole, uh, uh, AS stories and the whole functional pipelines.

Here, the red lines would be fast, Uh, put before the right, and then right.

I don't understand this code snippet when it tries to do. Is this or What does it mean? I am not familiar with this kind of syntax at

Well, That's our tasks that we know, uh, reviewed, uh, because the functional terms as a peer review, This design review, code review, uh, and those would be the test design should be, uh, come from the other functional type of functional team to, for bot testing and the function of the functional, uh, features of other team. And those would be reviewed cost reviewed by other teams. 1 team developed a, Uh, features. Uh, other teams would view that, and test designs would come, uh, from the other team, And test report should be viewed by then. So this is one aspect I can see. And Yeah. I think this is one of the things I need to to develop it, uh, across Amazon teams. This would be continuously checked in and, you know, using the repo and should be Uh, thoroughly, you know, tested by the test plan, which is reviewed by the other team. And, uh, hardware also, you know, hardware, uh, first software to develop, we'll test it. A deviate level, then, um, subsystem level and system level. As you know, the as for the test plan, and then, uh, I need to put on the hardware before putting hardware. The complexity of the software need to be estimated in the simulator or whatever the profiling strategies so that it can fit into the existing memory footprint and cycles. It was a hardware. And, uh, the drivers and And I also be tested first, and then, uh, the processing code, and that's scheduling, uh, based on the articles news. Uh, so there will be some Systematic testing of the software, which is why we integrate in the hardware. So, Yeah. Uh, it's earlier with the approach. It will be taken care

Well, we can, uh, imply, uh, we can we can the binaries, uh, of embedded from where it need to be compressed using some HVD. And, uh, while putting out the need to be decompressed, error check, like, quality check, SCS, you know, uh, with before after it completes this. And then it, uh, add it to be bring it to the memory of the device