HI TI
How to open GPU watchdog in SDK8.6 and how to feed dog?
Thanks
This thread has been locked.
If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.
Hello,
I'm not aware of the GPU watchdog. Where did you get this information?
The GPU driver handles all of the communication with the GPU, so there is no need to worry about handling GPU internal modules. If you could elaborate on what your goal is I can guide you to the correct instructions.
Thanks,
Erick
HI,
Other core RTI watchdog on their own core and feed the dog, but GPU did not find the relevant information, how to open and feed the dog on the GPU?
Thanks
Hello,
I'm checking with our team, but I believe these are dedicated per core for safety diagnostic purposes. I'll need more information from them on how this is supposed to be used.
Thanks,
Erick
Hi,
Please take a look at the RTI implementations provided in the Software Diagnostics Library.
Software Diagnostics Library (SDL) — Software Diagnostics Library (SDL) - J721E User Guide
The example(s) / implementation provided in SDL can be referenced and the same logic re-used as needed for testing/implementing RTI15.
Regards,
kb
Hi,
The watchdog needs to be serviced, in relation to the GPU functionality. This can be done by S/W running on the A72 core, where the A72 S/W would "pet"/service the watchdog as result of an indication (callback, interrupt) from GPU.
For example if you have an application that is expecting 30 frames per second from the GPU, then upon receipt of each 'n' frames you could service the watchdog, which would prevent it from expiring. The DWWD window would need to be configured according to how many frame drops, or how many 'ms' the system is willing to wait before watchdog expires.
Regards,
kb
Hi,
Thank you very much for your answer. I have roughly understood the whole deployment process.
But some of the details are still unknown,
How to get frames from GPU, is there an API?
Or is there an example of deploying RTI15?
Thanks。
Hi,
Any periodic event can be used to trigger the service/pet of the watchdog, examples could be a standalone thread/process, that wakes up every 'n' ms, and services the watchdog. Another example could be a timer that triggers and interrupt every 'n' ms, and the handler of that interrupt services the watchdog.
In both of the above examples, as this watchdog is related to the GPU, the code would ideally check that the GPU is "alive". This could be a test frame, or checking of module states.
Ideally the services of RTI15 DWWD would be part of the data path, as described in example in earlier post, where the watchdog is serviced based on output from the GPU. However if the GPU data is not yet running, all that is required to test the RTI15 DWWD is as described above, and shown in the SDL for other instances of RTI DWWD.
Regards,
kb