More info in #668
if there is more than one BDM device attached, application file descriptors will be destroyed once mass1, mass2, mass3, etc will appear. Current workaround is ugly: wait 3 seconds, try dopen each mass until dopen fails, and only after that loop release application.
@KrahJohlito advised to call some enhanced callbacks once BDM driver is ready.
@rickgaiser advised to find an internal bug that is corrupting access to the mass0 once mass1 is attached.
More info in #668
if there is more than one BDM device attached, application file descriptors will be destroyed once mass1, mass2, mass3, etc will appear. Current workaround is ugly: wait 3 seconds, try dopen each mass until dopen fails, and only after that loop release application.
@KrahJohlito advised to call some enhanced callbacks once BDM driver is ready.
@rickgaiser advised to find an internal bug that is corrupting access to the mass0 once mass1 is attached.