Please provide the following info (check/uncheck the boxes after clicking “+ Create Topic”): Software Version
DRIVE OS Linux 5.2.0
DRIVE OS Linux 5.2.0 and DriveWorks 3.5
NVIDIA DRIVE™ Software 10.0 (Linux)
NVIDIA DRIVE™ Software 9.0 (Linux)
other DRIVE OS version
other
SDK Manager Version
1.6.0.8170
1.5.1.7815
1.5.0.7774
other
Host Machine Version
native Ubuntu 18.04
other
Hi All,
We would like to implement following operations pipe .
CSI → images/video → debayer → scale → rotate -->output in memory
a) What is best accelerator for this purpose ? Would VI or ISP do debayering ? If so - what are the relevant APIs - NvMedia ?
b) if the output in memory is to be consumed by GPU - we need to use NVStreams or DW ImageStreamer ? What is difference between the two ? Which one would be more optimal ?
We do not see all examples / samples on the pegasus systems shipped to us ? Could it be because it was not flashed with right version ? What can we do to get all official samples published for pegasus ?
Thanks VickNV.
More of a HW accelerator question(s). But I will be happy to post on the forum that you recommend. There are quite a few of them - just to avoid future confusion could you please tell me which forum should I post this to ? Please help with link ?
Thanks.
ISP does debyering and scaling, 2D does rotation.
Yes, NvMedia are the APIs. NvStreams libraries provide a way for sharing resources between libraries (e.g. NvMedia, CUDA, OpenGL). dwImageStreamer is for conversion between different dwImageType.
If it’s installed DRIVE OS Linux, please check your version with below command.
Thanks VickNV. If I understand you right - ISP will do debayering + scaling --(lets name this traffic as X)----> DDR memory then 2D reads from DDR memory --(lets name this traffic as Y)----> writes back rotated image - is that right ? If you notice X and Y is same data. Is there way to optimize traffic X and traffic Y by trapping them in system cache ? How big are system caches in Xavier and Orin (the tech specs do not give this info). Any cache management can help us in optimizing our large compute graphs where nodes are distributed over CPU, accelerators, and GPU.
Thanks VickNV. Which version of DriveOS does your Camera Sample application link refer to ? I could not infer from the doc. Our recent Xaviers (E550) do not seem to have this sample. Any idea what do we need to do to get right versions of the sample that you are referring to (this machine DOES NOT have SIPL sample code) ? This xavier machine that I am referring to shows -
I would like to work at 5.2.*. What would be good way to get the machine to state where we have all the official nvidia samples which matches version / compatibility with 5.2 ?