|Running Thread: ID=5068 Priority=0 Class= | |Address |Module |Unit |Class |Procedure/Method |Line | The Error is trapped for me by EurekaLog, and the error report gives the following call stack: Call Stack Information: I also have IDE Fix Pack 2009 2.9 installed. ![]() I have all the Delphi 2009 Updates installed right up to and including Update 4. Of course, if I was unable to SaveAll, then I lose all the edits I had made since last saving. Either way I am stuck and then the only thing I can do is use Windows Task Manager to shut down Delphi. If I am lucky I can sometimes do a File/SaveAll in Delphi, but sometimes I can't. This only happens occasionally, but after pressing OK, then my IDE and program both may freeze. While debugging my application with Delphi 2009, I sometimes get the following exception occurring: It seems that "External exception" isn't a Delphi's bug, I had this exception times ago and it was probably a problem with the motherboard, or with the hardware, because the program worked well at other machine. The splash screen to my applications do not appear now when I'm debugging but at least I don't get that EEFFACE error anymore. When I create and access the splash screen. So to overcome this issue, I now put if DebugHook = 0 then I tried various other ways to do splash screens but they always eventually resulted in getting an EEFFACE error when debugging. I could put a break point on the first line of the dpr file and found that it always seemed to occur when creating the splash screen to my applications. The same code never received that error message on Windows XP. I received this error regularly when I went to Windows Vista and 7. This is not an exact answer but may help you with overcoming the error by describing my experience with it. When the exception code is not a Delphi generated exception or a hardware related exception, Delphi simply maps it to EExternalException. If you can reproduce this with a test case, please report it in Qualit圜entral ( ).ĮEFFACE is the SEH exception code used by C++, which is "leaking" out to some Delphi code (in this case the IDE itself). ![]() The odd thing is that if it is, in fact, going through writeobj.c, something is certainly not quite right. Our customers feedback some problem about kess v2,we sovled it and have written below,if you have same problems,it will help you.This is clearly something happening in the Delphi evaluator (which is part of the compiler). Step 3: weld a connector on backside of interface.Īlso you can watch video in kess v2 master package to program the chip. Step 2. Prepare for a LINK J-LINK V8 ARM USB-JTAG Adapter Emulator. Step 1. Buy one LPC2478 chip to replace the original one for KESS V2 master. Note: the newest KESS V2 V2.06 is packed with J-link V8 programmer, no need buy additional one.ĭetails about j-link v8 solve Kess V2 master tokens limited problem: UOBDII.COM is available with J-link V8, cost about 20USD, user can buy at: Ģ.–or you have to weld a connector on backside of interface ,and plug the J-link programmer. ![]() Note: NPX is out of stock in some sites now, because the newest KESS V2 need not replace NPX, the NPX is preinstalled in the machine. Desolder the old NPX and change it with new.It cost 14-20USD, some users call this chip as CPU Repair Chip, available at. The interface is destroy/brokenġ.–Buy a new NPX chip with 60 tokens inside. I replaced chip and reset tokens, then get connection error “External exception EEFFACE” as following picture shows.ġ.If you connect to internet with this clone tool,or make online update.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |