05-21-2016, 07:03 PM | #1124 | |
Registered
3
Rep 2
Posts |
Quote:
|
|
Appreciate
1
FlorinQCK-2.50 |
05-24-2016, 02:18 PM | #1125 |
New Member
15
Rep 16
Posts |
Hi!
Finally I managed to download 1B file with the ENET cable from my X1 E84 but I could not generate the GPS code because the “FSC Code Generator” gives me an error. “version after create () = 0x1D” I read a lot about this error but I have not be able to find a solution. Could someone help me? I need to connect and download the file again? o I have another solution? Best regards Last edited by GARFIgo; 05-25-2016 at 02:11 PM.. |
Appreciate
1
FlorinQCK-2.50 |
05-24-2016, 10:24 PM | #1128 |
Private First Class
56
Rep 145
Posts |
I am upgrading to NA NEXT 2016-2 on an F15. I am using fsc.exe from Dr Ho's post on the first page of the thread - tried other links but all contained a virus. I downloaded the DE file using E-Sys and run it through fsc.exe:
fsc.exe fsc_file_name 0xA8 0x27 > code.txt The code did not work. Went through quite a few posts on this thread and it is less and less clear how one is supposed to run fsc.exe. Here are my questions: Q1) does the file name of the DE file matter? The original E-SYS method instructions at the beginning of the thread tell you to save the DE file with a specific name (FXXXXXXX_000DE001.FSC where XXXXXX is last 7 VIN). fsc.exe does not seem to care about the file name (gives the same result regardless) and fsc.bat that the FSC generator app uses has a.hex as the file name. Q2) Do you need to add your VIN as the fourth parameter to fsc.exe? Some people seem to do it based on their posts. The resulting code will be different, so I guess only one method is correct. fsc.bat does not have it. Also, last 7 of VIN is in the DE file so passing it to fsc.exe looks redundant. Yet, the code will be different if I do. Q3) If you need to add the VIN, is it the last 8 characters or just the last 7? Could anyone please answer these questions? Thanks in advance! Last edited by realsgy; 05-25-2016 at 11:59 AM.. |
Appreciate
1
FlorinQCK-2.50 |
05-25-2016, 05:48 PM | #1130 | ||
X Eins in der Luft
12
Rep 81
Posts |
Possible reason for 0xD1 returned by FSC decoder
Quote:
The reason could be that the size of FSC/HEX file is incorrect. I've had this 0xD1 error when I've left an extra byte in edited generalPersistencyData_DiagnosticSWTController file. If you edit this file to extract the 1B sequence, please be attentive to four bytes that prepend the 01 01 00 1B ... sequence of generalPersistencyData_DiagnosticSWTController. These four bytes (if you read them in reversed order) provide the length of 1B file (the number of bytes you must cut starting from 01 01 00 1B ... sequence [typically at 0x270 offset]). The 1B length is typically 319 bytes, but it can be longer. If you cut out an incorrect number of bytes, FSC tool will return Quote:
|
||
Appreciate
1
FlorinQCK-2.50 |
05-25-2016, 07:25 PM | #1131 | ||||||||||
X Eins in der Luft
12
Rep 81
Posts |
How to properly prepare 1B file for using in FSC code generator to avoid 0xD1 errors
The block of bytes that you must extract from the generalPersistencyData_DiagnosticSWTController file starts with the following sequence of bytes:
Quote:
Alternatively, you may also use the debug data03 file, located in the /mnt/hbdebug/ folder. The 01 01 00 1B sequence starts at the 0x270 offset. However, there is a difference in how you compute the length of 1B sequence, depending on what file you have downloaded from the QNX computer via FTP service. The length of bytes that you must extract from generalPersistencyData_DiagnosticSWTController or data03 files is indicated by the bytes prepending the 01 01 00 1B sequence. In the generalPersistencyData_DiagnosticSWTController file the length is indicated by 4 bytes that go before the 01 01 00 1B sequence of bytes. For the data03 file the length of bytes to extract from the data03 file is indicated by 2 bytes that prepend the 01 01 00 1B sequence. For example, if you open the generalPersistencyData_DiagnosticSWTController in a Hex editor (such as HxD) and jump to the offset 0x270, you may find the following sequence of bytes that prepend the 01 01 00 1B sequence: Quote:
The CIC IVI infotainment system is based on the Renesas SH7785 (former Hitachi) processor. This processor is based on RISC architecture and supports both LE (LittleEndian) and BE (BigEndian) byte sequence. For the CIC implementation we have the LE architecture. That means we need to swap order of bytes to retrieve the correct order of bytes. For our sequence Quote:
Quote:
Quote:
This number of bytes, the length of the byte block that we need to extract, is an important thing. If you extract incorrect number of bytes, the resulting 1B file will produce incorrect convolutuion in the FSC tool and hence the D1 error. For example, if you see that in your generalPersistencyData_DiagnosticSWTController file you have different 4 bytes before the 01 01 00 1B, you must calculate the size based on this sequence in your file. Indeed, the guy from whom I learned this stuff (MrPerfekt), had to cut 322 bytes. Also, if you use the data03 file, please note that length must be calculated based on two bytes prepending the 01 01 00 1B sequence. For example, if you have: Quote:
Quote:
Quote:
If you cut 320 bytes where you had to cut 319, you will receive the 0xD1 error when using FSC tool for your HEX file: Quote:
Here is a short instruction on cutting the proper amount of bytes from the generalPersistencyData_DiagnosticSWTController file.
You are all set. Now use the command: Quote:
UPGRADE_INDEX is the hex number that defines edition of maps. Typically, upgrade index is increased in 1 byte increment from version to version. For example, the first edition for the current year (2016-1) has the index of 0x0B, the second edition (2016-2) is, hence, 0x0C. If you don't care specifying the 0x0D index in the future, when upgrading to 2017-1, you might want to set the index to 0xFF. Resulting bit mask will allow you to upgrade the maps in the future without having to specify the FSC code. |
||||||||||
Appreciate
1
FlorinQCK-2.50 |
05-26-2016, 01:13 AM | #1132 | |
Private First Class
56
Rep 145
Posts |
Quote:
Looks like contrary to Dr Ho's post, his package (and fsc.exe) does not work (anymore?) for NBT. |
|
Appreciate
1
FlorinQCK-2.50 |
05-30-2016, 11:14 AM | #1134 |
New Member
6
Rep 11
Posts |
Hi Shawn! Please tell me where in the map files do you find the code
0x28 which is for Europe PREMIUM? Because I try to generate FSC for Europe Next 2016-2. I understand that 0xFF is for life time but where do I find the other hex code ? Thank you for your time and answers |
Appreciate
1
FlorinQCK-2.50 |
05-30-2016, 11:33 AM | #1135 | |
General
10340
Rep 40,310
Posts
Drives: 2018 Alpina B6 650ix GC
Join Date: Feb 2010
Location: Houston, TX
|
Quote:
http://f30.bimmerpost.com/forums/sho...postcount=1003
__________________
2018 F06 Alpina B6 650ix GC; Space Grey; Vermillion Red Nappa Leather; Executive; B&O; Driving Assistant 2017 F15 X5 xDrive50i MSport; Glacier Silver Metallic; Black Dakota Leather; Executive; B&O; Driving Assistant; RSE |
|
06-01-2016, 12:47 PM | #1139 | |
General
10340
Rep 40,310
Posts
Drives: 2018 Alpina B6 650ix GC
Join Date: Feb 2010
Location: Houston, TX
|
Quote:
SXM can be bought cheap though. If you need source, PM me.
__________________
2018 F06 Alpina B6 650ix GC; Space Grey; Vermillion Red Nappa Leather; Executive; B&O; Driving Assistant 2017 F15 X5 xDrive50i MSport; Glacier Silver Metallic; Black Dakota Leather; Executive; B&O; Driving Assistant; RSE |
|
Appreciate
1
FlorinQCK-2.50 |
06-02-2016, 11:03 AM | #1140 |
Registered
8
Rep 4
Posts |
Is it correct lookup.xml file for ROAD MAP EUROPE WEST PREMIUM 2016-2 ?
<SgbmId id="NAVD_000004CE_255_002_061" SWID_FscShort="00280027" name="Road Map Europe West PREMIUM 2016-2" supplier="NTQ" sop="01.03.2014" version="10_09" MapOrderNumberBMW="" MapOrderNumberMINI="" MapOrderNumberRR="" successorMapOrderNumberBMW="" successorMapOrderNumberMINI="" successorMapOrderNumberRR=""> <EcuVariant CompatibilityIdentifier="HU_CIC-HB" Format="CIC" /> <SwUpdate SwUpdateEntry=""/> </SgbmId> |
Appreciate
1
FlorinQCK-2.50 |
06-02-2016, 11:08 AM | #1141 |
General
10340
Rep 40,310
Posts
Drives: 2018 Alpina B6 650ix GC
Join Date: Feb 2010
Location: Houston, TX
|
So long as you have "FscShort="00280027" name="Road Map Europe West PREMIUM 2016-2", the rest of it does not matter.
__________________
2018 F06 Alpina B6 650ix GC; Space Grey; Vermillion Red Nappa Leather; Executive; B&O; Driving Assistant 2017 F15 X5 xDrive50i MSport; Glacier Silver Metallic; Black Dakota Leather; Executive; B&O; Driving Assistant; RSE |
Appreciate
1
FlorinQCK-2.50 |
06-11-2016, 01:35 PM | #1143 |
Private First Class
28
Rep 109
Posts |
Is the party over? If not, could someone please PM me on the links to the generator and latest NA map for CIC HU ? THANKS!
Update: Found all necessary files although the lookup.html is outdated. Last edited by valley_nomad; 06-12-2016 at 06:08 PM.. |
Appreciate
1
FlorinQCK-2.50 |
06-12-2016, 05:36 PM | #1144 |
Private First Class
28
Rep 109
Posts |
So my understanding is, when editing lookup.html in this case, what really matters is "0088" which identifies Europe MOVE. Although "0027" identifies the targeted map version 2016-1, it can be actually replaced with FFFF for generating lifetime FSC -- i.e. targeting all future versions. The value (i.e. text string) for name doesn't really matter either. It is just for UI purpose when choosing the map. Please correct me if I am wrong.
|
Appreciate
1
FlorinQCK-2.50 |
Post Reply |
Bookmarks |
Thread Tools | Search this Thread |
|
|