KESS V2 5.017 "EXTERNAL EXCEPION EEFFACE" Solution

Offer the possible reasons and solutions to KESS V2 5.017 error "EXTERNAL EXCEPION EEFFACE".

It is normal for the computer to detect as USB device:

I tried with v2.23, v2.25 and v2.47. All the same error.
I can't replace NXP, but I can try to replace SD card.

See how everyone has suggested how to solve this problem:
Advice 1. Plug it in and uninstall the 'usb device' from the device manager then unplug the device. Install drivers usbdevicedrv that comes with the correct version for your kess/Ktag. Once complete, plug in Kess and allow drivers to install and run ksuite (with internet disabled)

Advice 2. You need to create a new 5.017 SD Card Image by using the "ImageUSB-tool" program.
Remove SD-card from kess
Format SD-card  Fat32
Burn 5.017 img. file to SD-card using imageUSB-tool (everything you need is on MHH forum)
Put SD-card back in to kess.
Works perfect for mine kess!(same problem)

Finally, I discovered the problem.
My friend had ksuite 1.97 installed on his computer and started the software with internet connection.
Possibly this version has damaged something in NXP.
And found out this new AT89C51CC03U NXP:
https://www.obd2shop.co.uk/wholesale/ck-100-141300046-nxp-fix-chip-with-1024-tokens.html

For your information, I'd like to attach New 5.017 SD Card Image free download: 
1). How to do read an SD card for Kess 5.017 or create a new one?
128 MB XOR Key01-13.zip
https://mega.nz/#!kRxTwQxZ!Vw6g3ROBHr9w7aboGEe97UPIbv2ruVOvlLIZaH1HPDY
Zip Password = "kess5017"

Note: Only Kess 5.017 or 5.028, not for 3.099 etc.

2). How to create a new SD card?
Firstly, download WinHex and XorFiles v1.0 http://www.nirsoft.net/utils/xorfiles.html
Insert your Original SD-Card to Cardreader on PC.
Run WinHex, press F9 open Disk, read your SD-card.
Mark 208Bytes = 13 lines from 0x00000270 to 0x0000033F.

Copy 13 lines to a new file.
Open in WinHex my Keyfile “128 MB XOR Key01-13.img”
Search and replace line 1 in your Keyfile with all line1 lines in “128 MB XOR Key01-13.img”
Search and replace line 2 in your Keyfile with all line2 lines in “128 MB XOR Key01-13.img”
….............................
Search and replace line 13 in your Keyfile with all line13 lines in “128 MB XOR Key01-13.img”

Save your new 128 MB XOR Key01-13.img
run XorFiles v1.0
Filename 1: = your original SD-Imagefile
Filename 2: = your new createt “SD128 MB XOR Key01-13.img” (with your 13 lines ;-)
Destination: = any filename for your new uncryptet Imagefile

if you have decrypted the files, you can integrate the decrypted image file with "ImDisk Virtual Disk
Driver" as a virtual drive and save the files to the PC.
Link to ImDisk https://sourceforge.net/projects/imdisk-toolkit/
If you want to use any new SD-Card in your Kess 5017, use Winhex to fill the SD-card with 00.
put SD-card in Kess, power on Kess.
The 13-line KEY = 208 Bytes is x times on the SD.
From 0x000000D0 it is on some empty SD cards.
If you not found search any other line.
It is important that from line 0 always the 13 lines are
13, 26, 39, 52 ..... 4160 ..... 344032 etc.
that is, 0x0001040 is in decimal 4160,
13 rows = 208 bytes,
4160 divided by 208 = 20
Or 53FE0 = decimal 344032
344032 divided by 208 = 1654
that means if you think you have found the key you have to divide the address (decimal) by 208
without anything after a comma.
then the start same Procedure to create a new “SD128 MB XOR Key01-13.img” file with new SDCard
Key.
Format the new SD-card with FAT, copy Files to SD-ard and crypt it with “XorFiles v1.0”

Thanks.

http://blog.obd2shop.co.uk/how-to-solve-kess-v2-5-017-external-excepion-eefface/

How to update fgtech firmware from 0386 to 0475?

Guys if I understand correctly fgtech 0386 or 0475 is the firmware of the micro.e you can do update or change the pcb ???
0386 is ok on SW china,0475 is ok on sw eu....

Reply:
v48 is 100% not possible to use with fw from v53...this is reality because the hw is totally different...if you want to reprogram lpc you can (if you know how on v48) but the functionality from v53 are not available on hw v48

To agree the above option:
Yes, update the firmware to 0475.
fgtech 0475 is more clean and stable, in combination with a rework pcb (Armageddon΄s list, few pages back)!!

Question: Is possible to use 90% of v53 functionality, just jtag not possible because obviously hw is missing.
Answer: But full working OBD, and BDM updated support to v53 is possible.

Question: ok then pcb changes from v48 to v53 / 54. anyone has a picture of 2 pcb ??

Answer: Maybe you don' t understand,
about pcb:
we change the bad components of china v54 pcb with better quality (components).
v48 is different pcb and it can' t be same with v54...
0475 is the firmware-software and cooperates flawlessly with v54 pcb.
photo v54

Question: now I read that it should be done hw rework and downgrade to sw v53.

Answer: v48 it's no longer on the market. only v54.
"simply" rework the components of v54 pcb (hw) and update the firmware from 0386 to 0475 if needed, because sοme sellers (obd2shop.co.uk) have already the fgtech 0475.
of course we need and good luck with these china copies...

Here is the FGTech 0475 PCB (sold at obd2shop.co.uk): 

If you are interested in it, here you can go:
https://www.obd2shop.co.uk/wholesale/euro-0475-version-v54-fgtech-galletto-2-master.html

Thanks.

FGTech Galletto 0475 win7 win10 works with no problem

Users feedback FGTech 0475 works on XP, 7 32/64 bit, win10 no problem.

1. My FGTech works now under Win10
Story went like this:
11th April, 2019 update:
I cannot write the firmware to the LPC2119.
I have erased first, but writ not possible. In Philips flash utility: "cannot communicate with testboard"
in Fash Magic this message: "Operation Failed. (programming - failed to send data to the device)"
or this message: "unable to communicate. (transmit/receive)".
I use Win XP 32bit, but on Win10 64bit i have the same write problem

12th April, 2019 update:
I'm confused ... i have erased the LPC MCU, writing is not possible ... but the FGTech still works (as 0386) ! After ERASE! Is this normal?
PS: i can still read the security too (it is 2 or 3)

13th April, 2019 update:
Just small feedback. I have now successful write the FGTech 0475 firmware.
I have buy new LPC MCU and replace it. Then was possible to write it. Just for info for another mates with the same writing problem.
My FGTech works now under Win10.

2. FGTech Galletto 0475 on Win xp and win7 32bit no problem:
The FGTech Galletto 0475 with 0475 and soft v54, works without problem in a desktop with win 7 32bit.

V54 FGTech 0475 Galletto 2 Master install on Win7 32bit: 



3. FGTech Galletto 0475 win7 64bit: get Crash report
Solution 1:
use fix tool. if not work again, maybe it is microsoft visual issues...
Here is free download link of fix tool:
https://mega.nz/#!cJABgQbD!SlEUD1vM91ovCGuCrHzAT6891t7OKgdkydhDFnB1iCs
No password

Solution 2:
Tried with fw 0386 FGTech Galletto and aes soft, it works in win7 64bit.
(one user's advice, does not represent the author's point of view ) :

The difference between 0386 and 0475:
0386 = june 2012, 0475 = december 2012

Thanks!

http://blog.obd2shop.co.uk/fgtech-galletto-0475-win7-win10-works-with-no-problem/