|
Title: ECU reports that security access is not granted Post by: jimmcgee5 on July 06, 2012, 11:56:17 AM Hi Guys , just used this great software for the first time ;D, and running into problems reading the ECU
06/Jul/2012 07:27:43.453: LOG: Set timing parameters to defaults. 06/Jul/2012 07:27:43.484: LOG: Sent message with service ID TesterPresent 06/Jul/2012 07:27:43.484: LOG: Changed diagnostic session type to: ProgrammingSession 06/Jul/2012 07:27:43.484: LOG: ECU requesting specific baud rate: 124800 06/Jul/2012 07:27:43.484: USER: Successfully started diagnostic session. 06/Jul/2012 07:27:43.484: USER: Negotiating communication timings. 06/Jul/2012 07:27:43.484: LOG: Reading current communication timings. 06/Jul/2012 07:27:45.484: LOG: Message received no replies. 06/Jul/2012 07:27:45.484: LOG: Resending message. Send attempts: 2 06/Jul/2012 07:27:45.500: LOG: Sent message with service ID TesterPresent 06/Jul/2012 07:27:45.546: LOG: Received message with service ID: TesterPresentPositiveReponse 06/Jul/2012 07:27:45.609: LOG: Sent message with service ID AccessTimingParameters 06/Jul/2012 07:27:45.656: LOG: Received message with service ID: AccessTimingParametersPositiveResponse 06/Jul/2012 07:27:45.656: LOG: Set timing parameters to new values. 06/Jul/2012 07:27:45.656: LOG: Reading communication timing limits. 06/Jul/2012 07:27:45.718: LOG: Sent message with service ID AccessTimingParameters 06/Jul/2012 07:27:45.765: LOG: Received message with service ID: AccessTimingParametersPositiveResponse 06/Jul/2012 07:27:45.765: LOG: Requesting communication at timing limits. 06/Jul/2012 07:27:45.781: LOG: Sent message with service ID AccessTimingParameters 06/Jul/2012 07:27:45.828: LOG: Received message with service ID: AccessTimingParametersPositiveResponse 06/Jul/2012 07:27:45.828: USER: Successfully changed to new communication timings. 06/Jul/2012 07:27:45.828: USER: Requesting security access. 06/Jul/2012 07:27:45.843: LOG: Sent message with service ID SecurityAccess 06/Jul/2012 07:27:45.859: LOG: Received message with service ID: SecurityAccessPositiveResponse 06/Jul/2012 07:27:45.859: USER: Security access granted. 06/Jul/2012 07:27:45.859: USER: Validating flash memory starts at 0x00800000 and ends at 0x00900000. 06/Jul/2012 07:27:45.937: LOG: Sent message with service ID RequestUpload 06/Jul/2012 07:27:45.968: LOG: Received message with service ID: NegativeResponse 06/Jul/2012 07:27:45.968: LOG: Received negative response for service ID: RequestUpload, with response code: SecurityAccessDenied_SecurityAccessRequested 06/Jul/2012 07:27:45.968: USER: Validation failed, ECU reports that security access is not granted. 06/Jul/2012 07:27:45.968: USER: Memory layout validation failed. 06/Jul/2012 07:27:48.453: LOG: Sent message with service ID TesterPresent 06/Jul/2012 07:27:48.468: LOG: Received message with service ID: TesterPresentPositiveReponse 06/Jul/2012 07:27:50.015: LOG: User Prompt - Title: Unable to validate memory layout Message: Unable to validate memory layout. Do you want to continue reading flash memory without validating the memory layout? Result: OK 06/Jul/2012 07:27:50.015: USER: Starting to read data block. 06/Jul/2012 07:27:50.015: USER: Requesting upload from ECU for address range 0x00800000 to 0x0080FFFF. 06/Jul/2012 07:27:50.046: LOG: Sent message with service ID RequestUpload 06/Jul/2012 07:27:50.062: LOG: Received message with service ID: NegativeResponse 06/Jul/2012 07:27:50.062: LOG: Received negative response for service ID: RequestUpload, with response code: SecurityAccessDenied_SecurityAccessRequested 06/Jul/2012 07:27:50.109: USER: Request upload from ECU failed, ECU reports security access has not been granted. 06/Jul/2012 07:27:50.109: USER: Reading ECU flash memory failed. Trying to force ECU to recognize read operation is complete. 06/Jul/2012 07:27:50.171: LOG: Validating flashed data checksum for address range 0x00900000 to 0x00900001. 06/Jul/2012 07:27:50.187: LOG: Sent message with service ID StartRoutineByLocalIdentifier 06/Jul/2012 07:27:50.218: LOG: Received message with service ID: StartRoutineByLocalIdentifierPositiveResponse 06/Jul/2012 07:27:50.234: LOG: Sent message with service ID RequestRoutineResultsByLocalIdentifier 06/Jul/2012 07:27:50.265: LOG: Received message with service ID: NegativeResponse 06/Jul/2012 07:27:50.265: LOG: Received negative response for service ID: RequestRoutineResultsByLocalIdentifier, with response code: BlockTransferDataChecksumError 06/Jul/2012 07:27:50.265: LOG: Checksum is incorrect. 06/Jul/2012 07:27:50.265: USER: Finished forcing ECU to recognize that failed read operation is complete. 06/Jul/2012 07:27:50.265: USER: Reading ECU flash memory failed. 06/Jul/2012 07:27:52.750: LOG: Sent message with service ID TesterPresent 06/Jul/2012 07:27:52.781: LOG: Received message with service ID: TesterPresentPositiveReponse 06/Jul/2012 07:27:55.265: LOG: Sent message with service ID TesterPresent 06/Jul/2012 07:27:55.296: LOG: Received message with service ID: TesterPresentPositiveReponse 06/Jul/2012 07:27:56.468: LOG: User Prompt - Title: Reading ECU Flash Memory Complete Message: Reading ECU flash memory failed. Result: OK 06/Jul/2012 07:27:56.468: USER: 100% complete. 06/Jul/2012 07:27:56.500: USER: Restoring Windows sleep mode. 06/Jul/2012 07:27:57.781: LOG: Sent message with service ID TesterPresent 06/Jul/2012 07:27:57.796: LOG: Received message with service ID: TesterPresentPositiveReponse 06/Jul/2012 07:28:00.296: LOG: Sent message with service ID TesterPresent 06/Jul/2012 07:28:00.328: LOG: Received message with service ID: TesterPresentPositiveReponse 06/Jul/2012 07:28:00.718: USER: Disconnecting... 06/Jul/2012 07:28:00.781: LOG: Sent message with service ID StopCommunication 06/Jul/2012 07:28:00.796: LOG: Received message with service ID: StopCommunicationPositiveResponse 06/Jul/2012 07:28:00.796: USER: Disconnected 06/Jul/2012 07:28:00.875: LOG: Closing FTDI device. 06/Jul/2012 07:28:00.890: LOG: Send receive thread now terminated. 06/Jul/2012 07:41:15.312: LOG: Opening NefMoto VW Audi ME7 Flasher Logger 1.9.3.2 06/Jul/2012 07:41:15.453: LOG: Cannot load license file, file does not exist: C:\Documents and Settings\Administrator\Application Data\Nefarious Motorsports\NefMoto VW Audi ME7 Flasher Logger\ImportedLicenses.License.dat 06/Jul/2012 07:41:15.500: LOG: Opened NefMoto VW Audi ME7 Flasher Logger 1.9.3.2 any one point me in the right direction ??? Title: Re: ECU reports that security access is not granted Post by: jimmcgee5 on July 18, 2012, 03:08:19 PM :-\ anyone help me :-*
is it this by any chance?? Cannot load license file, file does not exist: C:\Documents and Settings\Administrator\Application Data\Nefarious Motorsports\NefMoto VW Audi ME7 Flasher Logger\ImportedLicenses.License.dat Title: Re: ECU reports that security access is not granted Post by: gsxeclipsepsi on August 05, 2012, 06:38:17 PM Im having a issue too. I have flashed my car a month ago on the older realease at that time. I was able to connect and save and flash a file. I was also able to use APR immo program and it read and write my codes.
I than again connect a few days ago and checked and cleared CEL. After that I installed new realease 1.9.3.2 or w.e. and now I am having problems. At first it would only connect while ignition was off but got error like stated about security. Then it would only connect if you had ignition on and while trying to connect turn ignition off it would connect but not flash. Now its will do the last thing I said and not connect at all. VCDS lite will not work now. I will provide a log in a few mintues when I try something new. I was thinking my cable is bad. I am using a blue with sliver cable Ebay cable and I borrowed my friends ross tech usb-II or w.e. and vCDS workes fine and neffmoto comes up as a cable but can't be used. So I'm not sure if the ebay cable is fauilty. thanks Title: Re: ECU reports that security access is not granted Post by: gsxeclipsepsi on August 07, 2012, 06:42:28 PM Validated FTDI device is in dumb mode.
Disconnected Connecting... Starting slow init connection. Connecting to address 0x01. Slow init failed. Disconnected Connecting... Starting slow init connection. Connecting to address 0x01. Slow init succeeded. Switching to KWP1281 session. Failed to read KWP1281 connect info. Connecting to address 0x01. Slow init succeeded. KWP1281 connect info: 8D0907551L 2.7l V6/5VT G 0001 Title: Re: ECU reports that security access is not granted Post by: jimmcgee5 on August 10, 2012, 07:45:48 AM ;D ;D I fixed it !! ;D ;D, when I do the fast init , it connects at 124800, but before I ask it to read , change it down to 9600 and it connects and reads ;D, happy days !!
now all I need is a laptop with a battery that will last more than 10 minutes lol, so I can create an original file . woohoo Title: Re: ECU reports that security access is not granted Post by: gsxeclipsepsi on August 10, 2012, 08:10:57 PM 10/Aug/2012 10:26:03.893: USER: Disconnected
10/Aug/2012 10:26:04.050: LOG: Closing FTDI device. 10/Aug/2012 10:26:04.064: LOG: Send receive thread now terminated. 10/Aug/2012 10:26:08.817: LOG: Setting Address: 0x01 KeyByte1: 0x6B KeyByte2: 0x0F 10/Aug/2012 10:26:08.827: USER: Switching to KWP2000 session. 10/Aug/2012 10:26:08.976: LOG: Opened FTDI device. 10/Aug/2012 10:26:08.986: LOG: FTDI device info - Description: USB <-> Serial Serial Number: Device Type: FT_DEVICE_BM ID: 0x4036001 Device Flags: 0x0 10/Aug/2012 10:26:08.996: LOG: FTDI ChipID DLL is loaded, checking chip ID... 10/Aug/2012 10:26:09.005: LOG: Unable to read FTDI device chip ID 10/Aug/2012 10:26:09.060: USER: Validated FTDI device is in dumb mode. 10/Aug/2012 10:26:09.133: LOG: Starting send receive thread. 10/Aug/2012 10:26:09.143: LOG: Send receive thread now started. 10/Aug/2012 10:26:09.160: USER: Disconnected 10/Aug/2012 10:26:09.198: LOG: Setting communication timings to defaults. 10/Aug/2012 10:26:09.211: USER: Connecting... 10/Aug/2012 10:26:09.272: LOG: Setting communication timings to defaults. 10/Aug/2012 10:26:09.338: USER: Starting fast init connection. 10/Aug/2012 10:26:09.356: USER: Connecting to address 0x01. 10/Aug/2012 10:26:12.182: USER: Fast init sent, sending start communication request. 10/Aug/2012 10:26:12.199: LOG: Read incorrect echo from ECU while sending message bytes. Matched first 1 of 6 bytes. 10/Aug/2012 10:26:12.245: LOG: Expected: 81 01 F1 81 F4 10/Aug/2012 10:26:12.259: LOG: Read: 00 00 81 01 F1 81 10/Aug/2012 10:26:12.272: LOG: Was ignoring first 1 bytes of the echo. 10/Aug/2012 10:26:12.285: LOG: Clearing remaining expected echo bytes. 10/Aug/2012 10:26:15.303: LOG: Double checking receive buffer for embedded messages before flushing receive buffer due to P1 ECU response inter byte time out. 10/Aug/2012 10:26:15.314: LOG: Discarding first 1 bytes from the receive buffer because a message starts there. 10/Aug/2012 10:26:15.333: LOG: Ignoring received message not addressed to tester with address 01. Message service ID was StartCommunication 10/Aug/2012 10:26:15.349: LOG: Received message with service ID: StartCommunicationPositiveResponse 10/Aug/2012 10:26:15.363: LOG: Setting Address: 0x01 KeyByte1: 0x6F KeyByte2: 0x0F 10/Aug/2012 10:26:15.376: USER: Switching to KWP2000 session. 10/Aug/2012 10:26:15.390: USER: Connected 10/Aug/2012 10:26:15.567: LOG: Sent message with service ID TesterPresent 10/Aug/2012 10:26:17.570: LOG: Message received no replies. 10/Aug/2012 10:26:17.589: LOG: Resending message. Send attempts: 2 10/Aug/2012 10:26:17.622: LOG: Sent message with service ID TesterPresent 10/Aug/2012 10:26:19.625: LOG: Message received no replies. 10/Aug/2012 10:26:19.641: LOG: Resending message. Send attempts: 3 10/Aug/2012 10:26:19.673: LOG: Sent message with service ID TesterPresent 10/Aug/2012 10:26:21.674: LOG: Message received no replies. 10/Aug/2012 10:26:21.710: LOG: Failed to send message 3 times, message send failed. 10/Aug/2012 10:26:21.726: USER: Disconnecting because no response was received for the Tester Present message. 10/Aug/2012 10:26:21.803: LOG: User Prompt - Title: Confirm Full Write ECU Flash Memory Message: If you are ready to write, confirm the following things: 1) You have loaded a valid file and memory layout for the ECU. 2) The engine is not running. 3) Battery voltage is at least 12 volts. 4) It is OK the ECU adaptation channels will be reset to defaults 5) Flashing process can run uninterrupted until complete. 6) You agree to release Nefarious Motorsports Inc from all liability. Note: Some non-standard flash memory chips may prevent writing the flash memory. Click OK to confirm, otherwise Cancel. Result: OK 10/Aug/2012 10:26:21.854: USER: Disconnected 10/Aug/2012 10:26:21.869: USER: Disabling Windows sleep mode. 10/Aug/2012 10:26:21.886: USER: Writing ECU flash memory. 10/Aug/2012 10:26:21.918: USER: Writing ECU flash memory failed. 10/Aug/2012 10:26:21.935: USER: 100% complete. 10/Aug/2012 10:26:22.082: LOG: Closing FTDI device. 10/Aug/2012 10:26:22.097: LOG: Send receive thread now terminated. 10/Aug/2012 10:26:26.768: LOG: User Prompt - Title: Writing ECU Flash Memory Complete Message: Writing ECU flash memory failed. Result: OK 10/Aug/2012 10:26:26.777: USER: Restoring Windows sleep mode. 10/Aug/2012 10:26:31.044: LOG: Setting Address: 0x01 KeyByte1: 0x6B KeyByte2: 0x0F |