View The Full Version : problem kess v2 fw 4.036
hi all, I have a kess 2.08 fw 4.036 by mistake I used the soft original or distraction, is connected to the internet and does not work now,when I try to start it tells me connection failed and I check the menu screen, car/bike/truck etc all in grey.
to be able to restart I tried to use the j-link, but it says that it does not support the processor now I have the doubt it may be that there is a different interface to program the micro, or there is a different procedure?
hello, if I am not mistaken the processor, after the update 4.036 is protected for both reading and writing, then no more upgradeable.... the solutions are 2: or change the micro and then resets, or get a new kess and the riaggiorni!!! ;)
is exactly as says rego88.
Yeah, I rego88 and ugoboss.
many thanks for the advice
hello, take a micro sd new, re-file, clean the inside, use the cfg file with the number and fw fix without changing anything, the facts in the tens.......
I have now shipped the interface for the repair,so as soon as I will arrive to me, I copy the contents of the sd card and in case of problems the rewrite on a new one so I should solve the problem.
I got it from the little version 2.13 kess
someone on the forum has the fw 4.036 you can find including the TF folder?
no I I bought already with that firmware
hello, take a micro sd new, re-file, clean the inside, use the cfg file with the number and fw fix without changing anything, the facts in the tens.......
the microsd you need the new max 8Gb then you need the data new sd easy that your damaged and for the rest, ask for info to those who have provided the tool.......
if I listen to, solve, the chip is not responding, crashes the micro sd card, get the new 8Gb and format it in fat32, then see how you can get to find a cfg that pertain to your tool
you pulled the files to be put in the micro sd card new? if you have new files to the copy the 4 folders in the micro and reconnect everything, if you have the protocols that gray do the reset and it should go
of confusion you're making a lot of in the first the micro sd card must be new in package, 2 data of the micro sd card must be new, 3 the file .cfg the file that you enable the protocols, if you have found the sw with the file running in the update including the cfg use that, and if normal resets the ftdi do recognize as a different device, 2 simple things you had to do, and if you still do experiments?
I know that you can throw away.
I the ones with the cars in grey are not able to retrieve them.
Only on a KTAG gave me L00000 as you and fw version 0, and it was the SD card corrupt
If you want to do further testing and I the file K10033818.cfg I have
hello to all
by a user on the forum I updated with the file K10033818.bin which according to him should be the 4.036. the problem is that in the info on their computers sees him still as a 3.099 then I think I've only changed the serial in the practice..
can you help me to do the update to fw 4.036?
I need the files for the update though..
thanks to all for the help
I have written what you need to do.
You have written actually the fw 4.036. The file name is correct.
But as long as you do not close the procedure with the update protocols keep hanging on that way.
You have to download and install on their computers to 2.08 GERMAN, modified
With that update, the protocols and active the cRp3 on the cpu
hello
thanks for your help!
could you help me a little more, perhaps leaving me the link?
I wanted to ask then the tokens are unlimited? can I rewrite the npx with the j-link after you have activated the crp3?
thanks!
Once activated, the CRP3 the jlink you can put in the drawer, the jtag-trust-chain is closed and it becomes impossible to connect to the NXP and then program it again.
Link if you can post I'm afraid.
Search on san ****** jlink update fw 4.036 something you find...
Powered by vBulletin® Version 4.2.2 Copyright © 2025 vBulletin Solutions, Inc. All rights reserved.