reload driver after recovery for d457 #14143
Conversation
| subprocess.run( cmd ) | ||
| recovered = True | ||
|
|
||
| if 'jetson' in test.context: |
There was a problem hiding this comment.
Are you sure we want it here?
This is after the command
There was a problem hiding this comment.
I think this is correct.
We usually need to modprobe d4xx after the recovery device has been burnt with bundle fw.
No need to do it before, since the device has already been found (as recovery device).
Do we want to add this command also in case the device has not been found at all (and jetson is in context)?
I think it can only help.
There was a problem hiding this comment.
But bundle FW is signed FW.
We do it every night and never had to reload the driver.
Issues started with unsigned FW flow
Right?
There was a problem hiding this comment.
But every night, the device is not identified as recovery device.
So the update is triggerred below (see line 244)
3 participants
No description provided.