Share
This is a known issue and has been fixed as of v4.40 BusTools/1553-API.
Refer to the documentation included with the revision of API used to determine the correct API call to read firmware revisions.
This is a known issue and has been fixed as of v4.40 BusTools/1553-API.
Refer to the documentation included with the revision of API used to determine the correct API call to read firmware revisions.