Сообщений в теме: 11

[jacopo99]

Hi, after days spent to search a guide to update my (BMW x1 xdrive E84 2010 CIC motion), I found your forum..
In particular I'm looking for these points:
-What types of cable I have to use? Inpa k+kan USB?
-I can use your software for upgrade my Europe Motion map (2012)
Thanks You in advance

[2real4u]

You'll need ICOM A+B, OPS or OPPS to update your CIC software. Don't do this over K+DCAN Cable.
The software you need to update CIC is called WinKFP, which is part of BMW Standard Tools.
The map is updated using USB stick. Since few on this forum speak English and all instructions posted here are in Russian, you may have better luck finding instructions on English-speaking forums.

[jacopo99]

Thanks for your help!
But if i only want to "crack" the FSC code to update ONLY the map, what cable i have to user?

[xooler]

Thanks for your help!
But if i only want to "crack" the FSC code to update ONLY the map, what cable i have to user?

 

You need post your vin here.

[jacopo99]

Here my VIN:
VN16396
Thanks for Your help!

[jacopo99]

Any good news?

[Илья]

Non ti serve nessun cavo, ti serve solo la chiavetta usb e il programma per caricare la mappa "gi? pronta"

[jacopo99]

Ho trovato realmente un italiano? Lol
Ma dopo aver scaricato la mappa da un qualsiasi torrente, poi non devo inserire il codice FSC che qualcuno deve generare? Che programma intendi per caricare la mappa?

[Илья]

Se l'hai scaricata dal torrent, ci doveva essere assieme il programma che ti spiega come modificare i file per avere un codice giusto. Diversamente contatta qualsiasi dei utenti "pro" che dietro a un pagamento ti possono fare il tutto loro

[jacopo99]

Non ho ancora scaricato nulla, ora cerco. Il programma ha un nome in generale?

[Илья]

Cerca fsc generator e come usarlo

[Exotic Hadron]

I recommend using a USB-to-Ethernet interface. When you get one of the compatible (as listed below), extracting the desired file is an easy doing:

 

1. Plug the USB-to-Ethernet adapter into the USB port mounted in the glove box.
2. Use the patch cable patch cord cable to connect the adapter to your PC.
3. Configure your adapter on the PC to have the network settings that match the subnet configured on CIC network adapter.

 

To configure adapter on your PC:
1. On Windows open Control Panel\Network and Internet\Network Connections.
2. Right-click the icon of your network adapter and select Properties.
2.1 [optional] If you have Windows 8/Windows 8.1/Windows 10 with installed Hyper-V feature, right-click on the vEthernet Hyper-V Virtual Ethernet Adapter and not on the physical adapter. This is because when Hyper-V option is installed, virtual adapter plays the role of your network adapter; physical adapter plays the role of a network switch.
3. In the Properties dialog box find the Internet Protocol Version 4 (TCP/IPv4) item and click Properties.
4. On the General tab for the IPv4 properties set the address from the range of the IP addresses bound to the network interface on CIC.

 

Possible IP addresses of CIC interface are:

 

 

10.250.89.2
160.48.199.99
169.254.199.99

 

For example, the interface of E84 is bound to 10.250.89.0/24. 

 

Provided that your CIC has IP address 10.250.89.2, do the following:
1. On the General tab for the IPv4 properties choose Use the following IP address and type any IP from the CIC subnet, e.g.: 10.250.89.3
2. We don't need the whole 24-bits of subnet mask, because we just need to connect 1 PC to CIC, 10.250.89.0/24 is just okay. In the Subnet mask type 255.255.255.0.
3. Leave the Default gateway field blank. Windwos will automatically detect the default gateway (which is by default 10.250.89.1).
4. Don't change anything else in this dialog box and click OK.
5. Click OK in the Properties dialog to apply changes to the network interface on your PC.
6. [optional] Right-click on the configured adapter and select Disable, then select Enable from the same context menu of the adapter. This will help you make double sure that changes applied to your adapter.
7. Open command line and ping the network adapter on CIC by running:

 

ping -n 10 10.250.89.3

 

What to do if none of the IP networks listed here work? That is when you specify 10.250.89.3 (160.48.199.100 or 169.254.199.100), ping doesn't give the response (desitnation host is unreachable).

 

You can guess the IP subnet address of the network interface on CIC by using WireShark.

 

To find out the subnet of the network interface on CIC:
1. Download and install the portable version of WireShark. Don't forget about the PCAP interface, which is typically bundled with WireShark. PCAP is necessary to sniff network traffic.
2. Start WireShark and select your network apapter (or, for Hyper-V configuration, select virtual adapter).
3. When WireShark is started, observe IP addresses in the Source and Destination columns. Most likely the ones more frequenlty showing in the Source column pertain to the network set on CIC.

 

How to select a working USB-to-Ethernet adapter

 

BMW CIC and, hello Harman Kardon, Audi MMI (and thus any VAG IVI device) seem to use the same embedded device. (When one is curious, both CIC and MMI interfaces are made by Harman Kardon. No surprise that both system have the same hardware, OS and hence unique interface settings.

 

Here are the network interface drivers integrated in BMW CIC and Audi MMI:

 

 

########## USB ETHERNET ADAPTORS

 

 #RTL8150 Chipset
 vendor=0x0bda,device=0x8150,type=ETH,driver=devn-rtl8150.so,args=speed=10 duplex=1,netif=5,netip=172.16.250.248,netmsk=255.255.0.0

 

 #Pegasus Chipset
 vendor=0x08dd,device=0x0986,type=ETH,driver=devn-pegasus.so,args=speed=10 duplex=1,netif=5,netip=172.16.250.248,netmsk=255.255.0.0

 

 #ASIX Chipset
 vendor=0x0b95,device=0x1720,type=ETH,driver=devn-asix.so,args=speed=10 duplex=1,netif=5,netip=172.16.250.248,netmsk=255.255.0.0
 vendor=0x0b95,device=0x7720,type=ETH,driver=devn-asix.so,args=speed=10 duplex=1,netif=5,netip=172.16.250.248,netmsk=255.255.0.0
 vendor=0x0846,device=0x1040,type=ETH,driver=devn-asix.so,args=speed=10 duplex=1,netif=5,netip=172.16.250.248,netmsk=255.255.0.0
 vendor=0x2001,device=0x3c05,type=ETH,driver=devn-asix.so,args=speed=10 duplex=1 phy_88772=0,netif=5,netip=172.16.250.248,netmsk=255.255.0.0

 

 #MCS7830
 vendor=0x9710,device=0x7830,type=ETH,driver=devn-mcs7830.so,args=speed=10 duplex=1,netif=5,netip=172.16.250.248,netmsk=255.255.0.0

 

By the way, on VW Tuareg they seem to have slightly different settings, but you get the clue:

 

##########     USB ETHERNET ADAPTORS

 

#RTL8150 Chipset
vendor=0x0bda,device=0x8150,type=ETH,driver=devn-rtl8150.so,args=speed=10 duplex=1,netif=5,netip=172.16.250.248,netmsk=255.255.0.0

 

#Pegasus Chipset
vendor=0x08dd,device=0x0986,type=ETH,driver=devn-pegasus.so,args=speed=10 duplex=1,netif=5,netip=172.16.250.248,netmsk=255.255.0.0

 

#ASIX Chipset
vendor=0x0b95,device=0x1720,type=ETH,driver=devn-asix.so,args=speed=10 duplex=1,netif=5,netip=172.16.250.248,netmsk=255.255.0.0
vendor=0x0b95,device=0x7720,type=ETH,driver=devn-asix.so,args=speed=10 duplex=1,netif=5,netip=172.16.250.248,netmsk=255.255.0.0
vendor=0x0846,device=0x1040,type=ETH,driver=devn-asix.so,args=speed=10 duplex=1,netif=5,netip=172.16.250.248,netmsk=255.255.0.0
vendor=0x2001,device=0x3c05,type=ETH,driver=devn-asix.so,args=speed=10 duplex=1 phy_88772=0,netif=5,netip=172.16.250.248,netmsk=255.255.0.0

 

#MCS7830
vendor=0x9710,device=0x7830,type=ETH,driver=devn-mcs7830.so,args=speed=10 duplex=1,netif=5,netip=172.16.250.248,netmsk=255.255.0.0

 

##########     PFS Devices  

 

vendor=0xffff,device=0xffff,type=PFS,driver=io-fs-media,args=ignore=0b951720 ignore=0b957720 debug=0

 

##########     USB SERIAL converters

 

#Prolifics USB Serial converter
vendor=0x067b,device=0x2303,type=SER,driver=devc-serusb_prolific,args=-b 57600 -F -S -v

 

#MULF cmd line below
#vendor=0x067b,device=0x2303,type=SER,driver=devc-serusb_prolific,args=-b 57600 -F -S -v -o disable=rx

 

##########     Mass Storage device

 

vendor=0x04e8,device=0x5041,type=MSD,driver=devb-umass
vendor=0xffff,device=0xffff,type=MSD,driver=devb-umass,cam=verbose retries=3:0:0:0,blk=normv noexec noatime cache=512k auto=none commit=high delwri=0 devdir=/dev/umass,dos=sfn=windows codepage=cp850 vollabel=ignore hidden=dot
#vendor=0xffff,device=0xffff,type=MSD,driver=devb-umass,cam=verbose timeout=4:0:0:0 retries=3:0:0:0,blk=verbose=5 ra=0 normv noexec cache=128k auto=none commit=high delwri=0 devdir=/dev/umass

 

##########     SDCard Storage device

 

vendor=0xffff,device=0xffff,type=SDCard,dos=sfn=windows exe=all codepage=cp850 noatime vollabel=ignore

 

##########     Devices Known Not to Work

 

Here are the sample devices that match the drivers integrated into CIC:

 

#RTL8150 Chipset

 

vendor=0x0bda,device=0x8150 ---> Linksys USB100M Rev. 1.0

 

#Pegasus Chipset

 

vendor=0x08dd,device=0x0986 ---> Billionton USB100

 

#ASIX Chipset

 

vendor=0x0b95,device=0x1720 ---> SMC2209USB

 

vendor=0x0846,device=0x1040 ---> Netgear

 

vendor=0x2001,device=0x3c05 ---> D-LINK DUB-E100 Rev. B1

 

#MCS7830

 

vendor=0x9710,device=0x7830 ---> Moschip

 

Other compatible analogs can be guessed by using this list of vendors and their devices that use network interface produced by ASIX Electronics Corp.

 

Personally, I used D-LINK DUB-E100 Rev. B1. If you refer to the referenced list, you'll find out that vendor with hex VendorID of 0x2001 is D-Link Corp. and device that has the 0x3c05 DeviceID is DUB-E100 Fast Ethernet Adapter(rev.B1)

 

 

vendor: 2001 ("D-Link Corp."), product: 3c05 ("DUB-E100 Fast Ethernet Adapter(rev.B1) [ASIX AX88772]")

 

Revision of the device is an important thing. Other revisions are reported to have another DeviceID.