Hello,

I do notice an issue where if I run my event markers code the first time after boot and running the xmutil loadapp prophesee-kv260-imx636   the detection works and pose is updated, however after stopping the application and re-starting I notice that detection and pose update no longer work, although the camera device is properly accessed and no error is reported via add_status_change_callback -> add_runtime_error_callback or any of the Camera device calls (from camera.h in openeb).

The only way I can restart the application to work again is to run the following:

xmutil unloadapp

xmutil loadapp prophesee-kv260-imx636  

Are there hooks in the accelerator that are not properly cleaned up after the event markers code is closed and the camera device stopped?

I would like to know how the event smart stream tracker and streamer from the zynq video drivers are accessed via the higher level openeb calls. I am guessing there is an issue in my custom code but I am using pretty much the same calls via the Camera class that the original event markers code uses.