06-20-2021, 10:01 PM | #1 |
New Member
22
Rep 7
Posts |
Missing btld_00001a90...
I'm attempting to upgrade a few different ecus that are apparently too old to do gts/cs coding on, but esys keeps complaining "SVT <"ist"> could not be read. [C064] Bootloader btld_00001a90-060_000_001 not found in BaseVariantMapper [782]"
I have checked several different versions of psdzdata full, and none have that file. Anyone know what to do about this? Thanks, Mike |
06-21-2021, 07:35 AM | #3 |
New Member
22
Rep 7
Posts |
|
Appreciate
0
|
06-21-2021, 08:23 AM | #4 | |
BimmerPost Supporting Vendor
1780
Rep 3,052
Posts |
Quote:
__________________
Apple CarPlay Fullscreen for NBTEVO / ENTRYNAV2 / Anti-Dazzle F/G
CS FLASH G8X /GTS FLASH F8X / F8X Ultimate PACK / NBTEVO iDrive 6 FLASH iDrive Firmware Update + CarPlay Fullscreen -> Video Process Visit BIMMER-REMOTE.com - 10% OFF with BIMMERPOST_10 promocode info@bimmer-remote.com or PM |
|
Appreciate
0
|
02-13-2022, 06:15 PM | #7 |
Registered
3
Rep 3
Posts |
This is because you are running bootmod3 CustomROM. CustomROM has it's own bootloader with version 00001a90, which is not exist in PsdZData.
For fixing this issue, you need to do next: Open folder psdzdata -> mapping - in blmap.xml file add <entry key="00001a90" byteorder="MSB">DME2</entry> - in cvnpos.xml file add <entry key="BTLD-00001A90">1</entry> This will resolve your error. |
03-27-2022, 07:08 PM | #8 | |
Private
40
Rep 95
Posts |
Quote:
__________________
Current: 2020 X3M, 2022 911 GT3
Past: 2020 M2 Competition,2018 X3 M40i,2017 X3,2016 VW ,Golf R,2015 BMW M3,2010 VW GTI,2008 911 GT3,2005 VW GTI,2002 VW GTI 337 Last edited by Doublej; 03-27-2022 at 07:17 PM.. |
|
Appreciate
0
|
03-27-2022, 07:10 PM | #9 |
Private
40
Rep 95
Posts |
how did you 'go around' the issue?
__________________
Current: 2020 X3M, 2022 911 GT3
Past: 2020 M2 Competition,2018 X3 M40i,2017 X3,2016 VW ,Golf R,2015 BMW M3,2010 VW GTI,2008 911 GT3,2005 VW GTI,2002 VW GTI 337 |
Appreciate
0
|
03-28-2022, 05:30 AM | #10 |
BimmerPost Supporting Vendor
1780
Rep 3,052
Posts |
But it's not the issue at all...
__________________
Apple CarPlay Fullscreen for NBTEVO / ENTRYNAV2 / Anti-Dazzle F/G
CS FLASH G8X /GTS FLASH F8X / F8X Ultimate PACK / NBTEVO iDrive 6 FLASH iDrive Firmware Update + CarPlay Fullscreen -> Video Process Visit BIMMER-REMOTE.com - 10% OFF with BIMMERPOST_10 promocode info@bimmer-remote.com or PM |
Appreciate
0
|
04-05-2022, 04:47 AM | #11 |
Registered
3
Rep 3
Posts |
|
Appreciate
0
|
04-09-2022, 06:03 AM | #12 | |
New Member
0
Rep 10
Posts |
Quote:
|
|
Appreciate
0
|
01-22-2023, 05:43 AM | #13 |
New Member
2
Rep 14
Posts |
I am getting
Bootloader btld_00002b41-007_000_000 not found in BaseVariantMapper [782] and Base variant not determinable. Check diagnostic address. [G175] while FSC read |
Appreciate
0
|
03-15-2023, 10:44 PM | #14 |
Private First Class
54
Rep 123
Posts |
Remove bootmod3 customROM
I'd like to add to this thread, as there is absolutely no info on what to do in this situation. You can flash other modules by making the changes posted above. However, you can't touch your DME
If you are in this predicament and you want to flash a tuned DME (remove tune, revert to stock), but you find your DME bootloader has been replaced with a custom version: e-sys with not allow you to flash the DME without some changes. I had a car that had Bootmod3 installed on the DME. As a result, the TAL process failed when trying to flash the stock bootloader to the DME. The error is that e-sys is unable to validate the existing bootloader version (BTLD_00001A90_060_000_001 , which is bootmod3's custom bootloader), and cancels the whole process. The error says there are no entries for 00001A90 in the "ActivationKeyFile" I had never heard of this file(s) until now. No matter what you do, e-sys will insist on existing bootloader verification for DMEs. You can't force the flash by traditional methods that work on other modules. I don't have access to the previous owner, and I am not a bootmod3 customer. I just wanted the car stock again There is a way around this verification: This guide assumes you are familiar with e-sys. Don't do any of this if you don't understand what you are doing, seriously. Go learn e-sys first. You can't just copy and paste what I have here. Entry values will vary car-to-car. You will need to make these adjustments as required for whatever DME you are working on. I am not responsible for your mistakes with e-sys. I always connect via gateway URL. VCM and MSM update disabled. First, calculate an SVT target as normal, you'll need it to reference the correct target BTLD version. You can also get your current "custom" BTLD version this way, you will be using that value below. You need to add entries to two files that are used to authorize bootloaders by esys: 1. C:\Data\psdzdata\security\sec_auth_l3.xml In this XML file, use text editor to duplicate the AuthenticationKey entry from the target btld version. In my case, it was for BTLD-00001A83. Duplicate this entry, and modify it as follows to fit the bootmod3 customROM btld version currently installed on your DME. The actual long string for keyData doesn't matter, just copy it from the prior entry. </AuthenticationKey> -<AuthenticationKey plain="false"> <BL_ID>btld-00001A90-00.00.00</BL_ID> <keyData signatureScheme="BMWSigVerify" digestAlg="md5" type="21">76079F1FC3E7D4.......LONG STRING HERE</keyData> </AuthenticationKey> 2. C:\Data\psdzdata\security\sec_ncdkeys.xml Do the same for NCodSigKey entries. Again, the actual keyData string can be copied from an existing entry. I duplicated the entry for btld-00001a83, and adjusted it as follows: </NCodSigKey> <NCodSigKey plain="false" testKey="false"> <BL_ID>btld-00001A90-00.00.00</BL_ID> <keyData type="21" digestAlg="md5" signatureScheme="BMWSigVerify">AC7C51151162F.......LONG STRING HERE</keyData> If you want to avoid the base variant mapping error(s), you will also want to add the following two entries: 1. C:\Data\psdzdata\mapping\blmap.xml Again, add an entry by duplicating the most recent appropriate entry for your specific DME, and adjust it to suit. In this case I only needed to change the key= value <entry smac="false" eeComponent="DME-MEVD172G" byteorder="MSB" key="00001a90">DME2</entry 2. C:\Data\psdzdata\mapping\cvnpos.xml Same thing for this entry. Duplicate most recent, adjust it for your application. My entry looked like this: <entry key="BTLD-00001A90">1</entry> At this point, open esys and save an SVT_ist. Open the SVT_ist in the SVT editor, expand dme2-12 folder, expand StandardSVK, expand CAFD, BTLD, and both SWFLs. Edit the patch versions to be Patchversion=000. Do this for all four(CAFD, BTLD, and SWFLs). Save this modified SVT as SVT_ist_mod. Use this modified svt ist, along with a standard svt target file to create a TAL as normal. You should be able to program the DME entirely in one shot at this point. Hope this helps somebody someday. |
Appreciate
0
|
Post Reply |
Bookmarks |
|
|