When comparing the MD5 checksums for downloaded packages and other installation media, there is no difference between v184.108.40.206a and the current v220.127.116.11b(3). I’m looking at the driveinstall.json.
I compared the MD5 md5sum v18.104.22.168a vs v22.214.171.124b, it is different. Please see below. Thanks.
Firstly, thanks for your response. In the release notes for v126.96.36.199b(3) the only difference since 188.8.131.52(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 184.108.40.206a), as it seems that they are the same.
In 220.127.116.11b there is a new file “dpx-patch-v2.0.0.run” while in 18.104.22.168a the similar file is “dpx-patch-v1.1.0.run” – these will have different checksums. Everything else is 100% the same. Thanks.