When comparing the MD5 checksums for downloaded packages and other installation media, there is no difference between v5.0.5.0a and the current v5.0.5.0b(3). I’m looking at the driveinstall.json.
Dear benjamin-b,
I compared the MD5 md5sum v5.0.5.0a vs v5.0.5.0b, it is different. Please see below. Thanks.
cee1d514cf7aeea9242b2be141a6caed DriveInstall_5.0.5.0aL_SDK_b19.run
4ddc2a8927691a3dcef99882f117c8e9 DriveInstall_5.0.5.0bL_SDK_b3.run
Hi Steve,
Firstly, thanks for your response. In the release notes for v5.0.5.0b(3) the only difference since 5.0.5.0(a) is “Coverage for Maxim Max96799 GMSL aggregator revision update on some DRIVE PX 2 AutoChauffeur boards”. As the boards in question are partially controlled by the aurix controller, this would likely require an update to the aurix firmware and/or the files that are used to flash it. However, the foundations sdk that provides them is the same (again, see driveinstall.json), and so is the zip where they’re found in the install dir (DriveSDK/drive-t186ref-foundation/utils/scripts/DPX2-P2379-EB-V4.02.02_release.zip). I’m wondering how the appropriate changes in the codebase/SDK/extra tools have happened in this specific release (i.e., since 5.0.5.0a), as it seems that they are the same.
B
Dear benjamin-b,
In 5.0.5.0b there is a new file “dpx-patch-v2.0.0.run” while in 5.0.5.0a the similar file is “dpx-patch-v1.1.0.run” – these will have different checksums. Everything else is 100% the same. Thanks.