F30POST
F30POST
2012-2015 BMW 3-Series and 4-Series Forum
BMW Garage BMW Meets Register Search Today's Posts Mark Forums Read
BMW 3-Series and 4-Series Forum (F30 / F32) | F30POST > Technical Forums > Navigation, iDrive, Audio, Video, Bluetooth, Phone, Cameras, Electronics > Fsc code Generator
Extreme Powerhouse
Post Reply
 
Thread Tools Search this Thread
      05-19-2016, 01:04 PM   #1123
zoomm
Registered
5
Rep
3
Posts

Drives: BMW F10
Join Date: May 2016
Location: Germany

iTrader: (0)

Hi!

Could someone pm info on how i can get access to fsc code generator?

Many thanks!

zoomm
Appreciate 1
      05-21-2016, 07:03 PM   #1124
lali
Registered
3
Rep
2
Posts

Drives: bmw F10 520d
Join Date: May 2016
Location: UK

iTrader: (0)

Quote:
Originally Posted by zoomm
Hi!

Could someone pm info on how i can get access to fsc code generator?

Many thanks!

zoomm
Hi. I managed to generate fsc code by using the software in link provided by DR HO on the first page of this thread. Only issue I had was that fsc file I got via esys wouldn't initially work with the fsc generator because it was not recognised as a base64 file. However, got it working after converting the file using base64 program I found via another link.
Appreciate 1
      05-24-2016, 02:18 PM   #1125
GARFIgo
New Member
15
Rep
16
Posts

Drives: X1-E84
Join Date: May 2016
Location: SPAIN

iTrader: (0)

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
      05-24-2016, 03:39 PM   #1126
zoomm
Registered
5
Rep
3
Posts

Drives: BMW F10
Join Date: May 2016
Location: Germany

iTrader: (0)

@ lali

Many thanks.

zoomm
Appreciate 1
      05-24-2016, 09:44 PM   #1127
realsgy
Private First Class
United_States
56
Rep
145
Posts

Drives: 2015 X5 35i
Join Date: Jun 2015
Location: Seattle, WA

iTrader: (0)

Quote:
Originally Posted by TePee View Post
Yes, it showed me some error. Unfortunately I don't remember anymore what exactly. But it was something with not accessible and 32-Bit.
You can run fsc exe on 64bit windows from a 32 bit command prompt (c:\windows\syswow64\cmd.exe)
Appreciate 1
      05-24-2016, 10:24 PM   #1128
realsgy
Private First Class
United_States
56
Rep
145
Posts

Drives: 2015 X5 35i
Join Date: Jun 2015
Location: Seattle, WA

iTrader: (0)

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
      05-25-2016, 02:12 PM   #1129
GARFIgo
New Member
15
Rep
16
Posts

Drives: X1-E84
Join Date: May 2016
Location: SPAIN

iTrader: (0)

Someone knows how solve “version after create () = 0x1D” error?
Appreciate 1
      05-25-2016, 05:48 PM   #1130
Exotic Hadron
X Eins in der Luft
12
Rep
81
Posts

Drives: X1
Join Date: Sep 2010
Location: Leningrad, Rußland

iTrader: (0)

Possible reason for 0xD1 returned by FSC decoder

Quote:
Originally Posted by pikcachu View Post
for some reason now one of the generators says:

"version after create() = 0xD1"
This was asked a long time ago, but since it is the most relevant GOOG result, and there doesn't seem to be an answer (except for 0x20h extra ASCII symbols) in here, I'd love to add another explanation.

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:
"version after create() = 0xD1"
Hope it helps other rookies like myself.
Appreciate 1
      05-25-2016, 07:25 PM   #1131
Exotic Hadron
X Eins in der Luft
12
Rep
81
Posts

Drives: X1
Join Date: Sep 2010
Location: Leningrad, Rußland

iTrader: (0)

How to properly prepare 1B file for using in FSC code generator to avoid 0xD1 errors

Quote:
Originally Posted by GARFIgo View Post
Someone knows how solve “version after create () = 0x1D” error?
The block of bytes that you must extract from the generalPersistencyData_DiagnosticSWTController file starts with the following sequence of bytes:

Quote:
01 01 00 1B
The generalPersistencyData_DiagnosticSWTController file can be found in /mnt/HBpersistence/normal/ on the QNX file system.

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:
3F 01 00 00
These are the four bytes that define how many bytes you must cut from the generalPersistencyData_DiagnosticSWTController file to prepare the correct 1B hexadecimal file for using with the FSC tool.

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:
3F 01 00 00
the proper order to compute the length will be:

Quote:
00 00 01 3F
or simply

Quote:
13F
Since the numbers are hexadecimal, the decimal value is 319 (because 13Fh = 319d). In other words, this means that to receive the correct 1B file, we must cut 319 bytes from the position 0x270 in the generalPersistencyData_DiagnosticSWTController file.

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:
42 01
sequence before, like in that case of MrPerfekt, reverting bytes will give you the number:

Quote:
01 42
or simply

Quote:
142
Converting 142 into the decimal system you find that you need to cut 322 bytes (because 142h = 322d)

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:
version after create() = 0xD1

Here is a short instruction on cutting the proper amount of bytes from the generalPersistencyData_DiagnosticSWTController file.
  1. Download a hex editor such as HxD (WinHEX is even more good but not necessary for such a simple operation).
  2. Press Ctrl+E to select a block of bytes.
  3. In the Start-offset edit box enter the start of the block (offset number): 270.
  4. In the Length edit box enter the size of block: 13F. The tool will automatically select the desired 319 bytes for you.
  5. Press Ctrl+C to copy the selected block.
  6. Now press Ctrl+N to create a new file and pasted the copied block into it by pressing Ctrl+V.
  7. Save the created hexadecimal file using the following naming template: XXNNNNN_001B0001.hex (here XXNNNNN are the last 7 symbols of your VIN number).
    If you can't remember your VIN, these figures are right there in the generalPersistencyData_DiagnosticSWTController file at the 0x2E offset.

You are all set.

Now use the command:

Quote:
fsc XXNNNNN_001B0001.hex APP_ID UPGRADE_INDEX
APP_ID is the hexadecimal number that defines the region of the map. For example, for Europe APP_ID = 0x28.

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
      05-26-2016, 01:13 AM   #1132
realsgy
Private First Class
United_States
56
Rep
145
Posts

Drives: 2015 X5 35i
Join Date: Jun 2015
Location: Seattle, WA

iTrader: (0)

Lightbulb

Quote:
Originally Posted by realsgy View Post
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!
Finally I found a different package that had nbt.exe in it. Using nbt.exe I was able to create a working code. 7 digit VIN can be passed in but it is optional.

Looks like contrary to Dr Ho's post, his package (and fsc.exe) does not work (anymore?) for NBT.
Appreciate 1
      05-30-2016, 10:42 AM   #1133
azikev
New Member
6
Rep
9
Posts

Drives: M135i
Join Date: Feb 2016
Location: FRANCE

iTrader: (0)

hello all,
Do you know where can i find the last Lookup file for update my map?
thx
Appreciate 1
      05-30-2016, 11:14 AM   #1134
CostinLogin
New Member
Romania
6
Rep
11
Posts

Drives: X3 F25 3.0d xDrive M-Pack
Join Date: Apr 2015
Location: Romania

iTrader: (0)

Quote:
Originally Posted by shawnsheridan View Post
0x28 = Europe PREMIUM
0x27 = 2016-2
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
      05-30-2016, 11:33 AM   #1135
shawnsheridan
General
shawnsheridan's Avatar
United_States
10340
Rep
40,310
Posts

Drives: 2018 Alpina B6 650ix GC
Join Date: Feb 2010
Location: Houston, TX

iTrader: (0)

Garage List
Quote:
Originally Posted by CostinLogin View Post
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
Read Post # 1003:

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
Appreciate 2
      05-30-2016, 01:10 PM   #1136
azikev
New Member
6
Rep
9
Posts

Drives: M135i
Join Date: Feb 2016
Location: FRANCE

iTrader: (0)

hello shawn,
Do you know where can i find the last Lookup file for update my map to europe next 2016-2?
thx
Appreciate 1
      05-30-2016, 01:22 PM   #1137
shawnsheridan
General
shawnsheridan's Avatar
United_States
10340
Rep
40,310
Posts

Drives: 2018 Alpina B6 650ix GC
Join Date: Feb 2010
Location: Houston, TX

iTrader: (0)

Garage List
Quote:
Originally Posted by azikev View Post
hello shawn,
Do you know where can i find the last Lookup file for update my map to europe next 2016-2?
thx
Clone existing entry, change to FSCShort to 00A90027 and Name to Europe NEXT 2016-2.
Appreciate 1
      06-01-2016, 12:44 PM   #1138
TrickyT
Private
TrickyT's Avatar
12
Rep
86
Posts

Drives: 2015 Alpine White 328i xDrive
Join Date: Feb 2016
Location: USA

iTrader: (0)

2 Questions, I'm only 6 pages in but...
1) has anyone done this for upgrading from SXM ready to get SXM?
2) Is the process the same as what I've already read in the first 6 pages from 2014 or has it changed/updated?
Appreciate 1
      06-01-2016, 12:47 PM   #1139
shawnsheridan
General
shawnsheridan's Avatar
United_States
10340
Rep
40,310
Posts

Drives: 2018 Alpina B6 650ix GC
Join Date: Feb 2010
Location: Houston, TX

iTrader: (0)

Garage List
Quote:
Originally Posted by TrickyT View Post
2 Questions, I'm only 6 pages in but...
1) has anyone done this for upgrading from SXM ready to get SXM?
2) Is the process the same as what I've already read in the first 6 pages from 2014 or has it changed/updated?
No, not possible. Only a Map FSC Code can be generated, as it is FSC Short. All other FSC Codes are FSC Long, and must be issued by BMW AG, and signed with their Private Encryption Key.

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
      06-02-2016, 11:03 AM   #1140
Slamon
Registered
Slamon's Avatar
Germany
8
Rep
4
Posts

Drives: G20
Join Date: Jun 2015
Location: D

iTrader: (0)

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
      06-02-2016, 11:08 AM   #1141
shawnsheridan
General
shawnsheridan's Avatar
United_States
10340
Rep
40,310
Posts

Drives: 2018 Alpina B6 650ix GC
Join Date: Feb 2010
Location: Houston, TX

iTrader: (0)

Garage List
Quote:
Originally Posted by Slamon View Post
Is it correct lookup.xml file for ROAD MAP EUROPE WEST PREMIUM 2016-2 ?
...
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
      06-02-2016, 11:28 AM   #1142
Slamon
Registered
Slamon's Avatar
Germany
8
Rep
4
Posts

Drives: G20
Join Date: Jun 2015
Location: D

iTrader: (0)

Thanks
Appreciate 1
      06-11-2016, 01:35 PM   #1143
valley_nomad
Private First Class
28
Rep
109
Posts

Drives: 2013 F30 328i
Join Date: May 2012
Location: Silicon Valley

iTrader: (0)

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
      06-12-2016, 05:36 PM   #1144
valley_nomad
Private First Class
28
Rep
109
Posts

Drives: 2013 F30 328i
Join Date: May 2012
Location: Silicon Valley

iTrader: (0)

Quote:
Originally Posted by shawnsheridan View Post
It is quote simple. Clone Europe MOVE the 2016-1 Lookup.xml entry, and edit the following:

SWID_FscShort="00880027"
name="Road Map Europe MOVE 2016-2"

None of the other values matter.
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
Post Reply

Bookmarks

Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off



All times are GMT -5. The time now is 12:06 AM.




f30post
Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2024, vBulletin Solutions Inc.
1Addicts.com, BIMMERPOST.com, E90Post.com, F30Post.com, M3Post.com, ZPost.com, 5Post.com, 6Post.com, 7Post.com, XBimmers.com logo and trademark are properties of BIMMERPOST