Kess V2 Harware Rework - FREE SOLUTION!

[BubbaFet]

you can flash by whatever you want.

ISP, serial

OK, I have never replaced the NXP (never done a single write yet) on my clone - will the original NXP be able to be updated, or do I need to buy a new NXP first?

[carmageddon]

try to connect with jlink, if you connect with success at the cpu you can read-write without problem, if you cannot you need to change cpu

[BubbaFet]

Cheers, I'll get the solderingstation out then. Are the HW modifications strictly needed along the FW/SW updates? Or can I order the parts and the use it until I get the parts needed for the HW modifications

[toms4]

Cheers, I'll get the solderingstation out then. Are the HW modifications strictly needed along the FW/SW updates? Or can I order the parts and the use it until I get the parts needed for the HW modifications

You can update FW without HW modifications.

[BubbaFet]

It seems I could update via JTag. Now trying the net steps..

[BubbaFet]

Argh Bollocks.

Disabled the WIFI/Ethernet
Updated the FW
Updated the SD
Installed 2.08 - removed contents
Copied the contents of the 2.08 folder
Copied the update folder
Starting KSuite

Then BANG - "External Exception EEFFACE" :/

When plugging in the Kessv2 (USB->Computer) the red LED just blinks once every second - this cannot be normal?

[javyb]

Argh Bollocks.

Disabled the WIFI/Ethernet
Updated the FW
Updated the SD
Installed 2.08 - removed contents
Copied the contents of the 2.08 folder
Copied the update folder
Starting KSuite

Then BANG - EEFFace error. :/

When plugging in the Kessv2 (USB->Computer) the red LED just blinks once every second - this cannot be normal?

The firmware it gets stuck on when updating if u remove from folder the update will continue

[morgano]

Led blinking on connecting to usb is bad business.

[Dolcevita]

I've got some problem with understanding your post but if you meant what I think you did then you do not do an "initial" install just copy over.
I don't know if your reading inconsistencies are related to sw or hw but to make the software part sorted out is a tad bit easier so I'd start with that...

Try this:
- get rid of everything KSuite related from the PC/laptop
- install "original installer" from link
- THEN copy KSuite v2.8 folder from same link
- test...


ps. Have you seen my PM?


EDIT:
It even works on a Win 7 VM running on a Win 7 x64 Ultimate system

Thx mate for Sharing got few questions.
for what is KessV2_4.036_SDCARD_before_final_format.rar ? it?s insde HOWTO and other bits.rar .
If i follow step by step your how to above mentioned rar folder is useless or not?
Is there a Token limitation ? if yes how to reset?


knd regards

[BubbaFet]

Ok, I flashed the old firmware back to the Kess. Same issue - blinking LED and EEFFace error. Then I tried to keep the JTag connected and the JLink connected via USB to the computer - now it works. :/

Kess Suite did it's update and everything seems fine. The About tells me that I have 4.039 FW and 2.08 SW. If I disconnect the JTAG I get blinking LED again - reconnect it and everything is fine.

I do not have a car connected to the KESS - I wonder why it is not able to boot properly without the extra power from the JTAG?

..Next step, try it on the car.


EDIT: All protocols are greyed out - I can browse them, but I cannot connect using any of them. SDcard issues?

[BubbaFet]

OK, it seems the 4.39 Firmware posted earlier in this thread is CRP3 protected despite stated otherwise. That means no JTAG access anymore. However.. Judging by this pdf: http://www.nxp.com/documents/applica...te/AN10851.pdf

it should be possible to enter CRP2. This must be what the Kess Suite does when it updates. We "just" need to find out how to enter the CRP2 - then we can wipe and flash with a non-CRP3 firmware again. (4.024 is that CRP3?)

If there is an update folder in the KessSuite folder - then Kess Suite starts updating the firmware, but is it the NXP firmware it alters?

In the info dialog of KessSuite I have the following:

Device Type: M
FW version: 4.036
Serial Number: K666....
Customer Code:
Group Code:
Subscription Expiry Date:

[heteromies]

OK, it seems the 4.39 Firmware posted earlier in this thread is CRP3 protected despite stated otherwise. That means no JTAG access anymore. However.. Judging by this pdf: http://www.nxp.com/documents/applica...te/AN10851.pdf

it should be possible to enter CRP2. This must be what the Kess Suite does when it updates. We "just" need to find out how to enter the CRP2 - then we can wipe and flash with a non-CRP3 firmware again. (4.024 is that CRP3?)

If there is an update folder in the KessSuite folder - then Kess Suite starts updating the firmware, but is it the NXP firmware it alters?

In the info dialog of KessSuite I have the following:

Device Type: M
FW version: 4.036
Serial Number: K666....
Customer Code:
Group Code:
Subscription Expiry Date:

If fw is 4.036 you cannot use jlink anymore, MCU is locked CRP3. Try to play with files now... If doesnt work, need replace MCU and start over.

What i have hear, 4.026 is CRP2, and its older fw, so some OBD- protocols missing vs 4.036

[ecutuners]

With serial k6666666 and 4.036 it's time for new mcu

[BubbaFet]

I thought so. :/

[teerak2uk]

New nxp about ?20 on ebay or ?5 on aliexpress