Error codes and descriptions

[Blacky]

These error codes/descrtiptions were last updated Nov 25, 2007.

__________________________________________________ __________________________
$0000 Error code of 0 means no error.
__________________________________________________ __________________________

EFILive USB driver Error Code
__________________________________________________ __________________________

$0001 USB internal driver error (invalid handle)
$0002 USB device is not connected
$0003 USB device is not open
$0004 USB I/O error
$0005 USB insufficient resources
$0006 USB invalid parameter
$0007 USB invalid baud rate
$0008 USB device not open for erase
$0009 USB device not open for write
$000A USB write error
$000B USB eeprom read error
$000C USB eeprom write error
$000D USB eeprom erase error
$000E USB eeprom not present
$000F USB eeprom not programmed
$0010 USB invalid argument
$0011 USB device not supported
$0012 USB Unknown error

__________________________________________________ __________________________

EFILive_Hapi Error Codes
__________________________________________________ __________________________

$0020 EFILive USB driver DLL not loaded
$0021 EFILive USB driver DLL function not defined in loaded DLL
$0022 EFILive USB driver request timed out
$0023 File not found
$0024 EFILive_Hapi is not running
$0025 Can't get semaphore for control of EFILive_Hapi
$0026 Request was ignored - i.e. reply cmd<>send cmd
$0027 Device is not enabled
$0028 Device is currently being programmed
$0029 Device is NOT currently being programmed

__________________________________________________ __________________________

Boot Error Codes
__________________________________________________ __________________________

$0081 RAM failure
$0082 BOOT Block is not present or corrupt
$0083 BOOT Block is the wrong size
$0084 Boot block CRC is incorrect
$0085 Application firmware is not present or corrupt
$0086 Application Internal Flash CRC is incorrect
$0087 Application External Flash CRC is incorrect
$0088 Application Internal and External Flash CRC are incorrect
$0089 Application Internal firmware is the wrong size
$008A Application External firmware is the wrong size
$008B Attempted to erase or reflash non-existant flash memory
$008C License details have not been programmed yet
$008D Attempted to erase or reflash protected flash memory
$008E Attempt to overwrite firmware with an older version
$008F Hardware is not licensed

__________________________________________________ __________________________

Flash Memory Error Codes
__________________________________________________ __________________________

$00C1 Operating error
$00C2 Sequence error
$00C3 Protection error
$00C4 External flash erase error
$00C5 External flash write error

__________________________________________________ __________________________

USB Error Codes
__________________________________________________ __________________________

$0100 No USB connection
$0101 No data received
$0102 Transmit buffer is full
$0103 Received data message had no CRC data
$0104 Bad CRC on received data
$0105 Received data contained incorrect number of parameters
$0106 Received data contained parameters that were out of range
$0107 Received data message was too short
$0108 Received data message was too long
$0109 Received data message contained unknown command group
$010A Received data message contained unknown command action
$010B Device is locked by user PIN
$010C Device is busy (i.e. Black Box Logging or Reading/Flashing a tune)

__________________________________________________ __________________________

FAT32 Flash File System Error Codes
__________________________________________________ __________________________

$0180 F_NO_ERROR, (File system error: 0)
$0181 F_ERR_RESERVED_1, (File system error: 1)
$0182 F_ERR_NOTFORMATTED, (File system error: 2)
$0183 F_ERR_INVALIDDIR, (File system error: 3)
$0184 F_ERR_INVALIDNAME, (File system error: 4)
$0185 F_ERR_NOTFOUND, (File system error: 5)
$0186 F_ERR_DUPLICATED, (File system error: 6)
$0187 F_ERR_NOMOREENTRY, (File system error: 7)
$0188 F_ERR_NOTOPEN, (File system error: 8)
$0189 F_ERR_EOF, (File system error: 9)
$018A F_ERR_RESERVED_2, (File system error: 10)
$018B F_ERR_NOTUSEABLE, (File system error: 11)
$018C F_ERR_LOCKED, (File system error: 12)
$018D F_ERR_ACCESSDENIED, (File system error: 13)
$018E F_ERR_NOTEMPTY, (File system error: 14)
$018F F_ERR_INITFUNC, (File system error: 15)
$0190 F_ERR_CARDREMOVED, (File system error: 16)
$0191 F_ERR_ONDRIVE, (File system error: 17)
$0192 F_ERR_INVALIDSECTOR, (File system error: 18)
$0193 F_ERR_READ, (File system error: 19)
$0194 F_ERR_WRITE, (File system error: 20)
$0195 F_ERR_INVALIDMEDIA, (File system error: 21)
$0196 F_ERR_BUSY, (File system error: 22)
$0197 F_ERR_WRITEPROTECT, (File system error: 23)
$0198 F_ERR_INVFATTYPE, (File system error: 24)
$0199 F_ERR_MEDIATOOSMALL, (File system error: 25)
$019A F_ERR_MEDIATOOLARGE, (File system error: 26)
$019B F_ERR_NOTSUPPSECTORSIZE, (File system error: 27)
$019C F_ERR_ALLOCATION (File system error: 28)

__________________________________________________ __________________________

File Transfer Link Error Codes (follows UNIX errno.h)
__________________________________________________ __________________________

$0200 Can't open file (Errno: 0)
$0201 Permission denied (Errno: 1)
$0202 Does not exist (Errno: 2)
$0207 Is too big (Errno: 7)
$0210 File system is busy (Errno: 16)
$0211 Already exists (Errno: 17)
$0214 Is not a directory (Errno: 20)
$0215 Is a directory (Errno: 21)
$021C No space (Errno: 28)
$0222 Range error (Errno: 34)

__________________________________________________ __________________________

OBD Error Codes
__________________________________________________ __________________________

$0280 Unsupported protocol (i.e. no vehicle detected)
$0281 No data received
$0282 No such node
$0283 No such PID
$0284 Unknown PCI (Protocol Control Information)
$0285 Incorrect sequence ID
$0286 CAN, VPW or ALDL handler is busy
$0287 Dynamic packets are full
$0288 Response from controller not supported by EFILive
$0289 PID selection is full

__________________________________________________ __________________________

Controller Error Codes - generated by vehicle's controller
__________________________________________________ __________________________

$0311 Mode Not Supported ($11)
$0312 Sub Function Not Supported or Invalid Format ($12)
$0322 Conditions Not Correct or Request Sequence Error ($22)
$0323 Routine Not Complete ($23)
$0331 Request Out of Range ($31)
$0378 Request Correctly Received, Response Pending ($78)
$0381 Scheduler Full ($81)
$03E3 Device Control Limits Exceeded ($E3)

__________________________________________________ __________________________

SD Card Error Codes
__________________________________________________ __________________________

$0401 Unknown SD card error
$0402 SD card not present
$0403 SD card not initialized
$0404 SD card busy
$0405 SD card is write protected
$0406 Error writing to SD card
$0407 Error reading from SD card
$0408 SD card took too long to respond
$0409 Incorrect SD card command parameter
$040A Invalid SD card sector address
$040B SD card erase sequence error
$040C SD card CRC incorrect
$040D Invalid SD card command
$040E SD card erase reset failed
$040F SD card is still initializing
$0410 SD card took too long to read data
$0411 SD card took too long to ack write request
$0412 SD card took too long to write data
$0413 SD card init loop 0 timeout
$0414 SD card init loop 1 timeout
$0415 Unrecoverable read error
$0416 Unrecoverable write error

[XLR8NSS]

I went out to try logging my truck. I selected E38 Auto and then tried logging. After hitting "F1 Record data" it came up "creating log file". Then it showed error $0205. I don't see it listed here.

The truck is a '07 GMC 2500HD 6.0L 6L90E with OS 12618277

[Blacky]

I went out to try logging my truck. I selected E38 Auto and then tried logging. After hitting "F1 Record data" it came up "creating log file". Then it showed error $0205. I don't see it listed here.

The truck is a '07 GMC 2500HD 6.0L 6L90E with OS 12618277
Error $205 is incorrect, it should be $185 "File not Found". I will fix it.

You will get that error if FlashScan can't find the \EFILive\V7\Scan folder.
That could happen if you formatted your SD Card using a PC and did not add in that folder.

Actually, it makes sense to have FlashScan automatically create the folders it needs if they do not exist. I will do that as well.

Regards
Paul

[oztracktuning]

Im getting $0182 when i try to do the step 5
"Click and drag ALL files from the Config folder to the [Config Files] tab page.
Hint: hold down the Ctrl key on the PC keyboard to select multiple files and then drag all highlighted files to the [Config Files] tab page

Im using Vista.

[SV8346]

gday steve, make sure the sd card is formatted in the BB using EFILIVE Hapi. If you format it in a card reader plug into the computer it wont put the required folders onto the card, i had this problem at first as well.

[Lennart]

I keep getting error $0414, is that $4014 in your list?

[Blacky]

I keep getting error $0414, is that $4014 in your list?
Yes, that's my fat fingers making typing mistakes. I'll fix the error numbers.

$0414 means FlashScan cannot get the SD card to finish its initialization sequence.
Is it a 2Gb or 4Gb card? Large cards can sometimes take a *long* time to initialize.

Regards
Paul

[Lennart]

Yes, that's my fat fingers making typing mistakes. I'll fix the error numbers.

$0414 means FlashScan cannot get the SD card to finish its initialization sequence.
Is it a 2Gb or 4Gb card? Large cards can sometimes take a *long* time to initialize.

Regards
Paul

It is a 256MB MMC card!
See this thread: http://forum.efilive.com/showthread.php?t=7658

[abkimble]

How about error $0483

[Blacky]

How about error $0483

That error can happen if you are using old *.pmm files with the latest version of the software.

Look at the very end of the document: Start->All Programs->EFILive->V8->Documents->EFILive Error Messages.
It explains what the error is and how to fix it.

Here's what it says:

$0483 *.pmm file has incorrect CRC

The *.pmm file that was copied to FlashScan or AutoCal when setting up Black Box Logging is corrupt or is not a true *.pmm file.

Re-install (or repair-install) the EFILive V8 software, then use the BBL [Program] option with the “Force update of PMM files” option checked.

Regards
Paul

[abkimble]

That error can happen if you are using old *.pmm files with the latest version of the software.

Look at the very end of the document: Start->All Programs->EFILive->V8->Documents->EFILive Error Messages.
It explains what the error is and how to fix it.

Here's what it says:

$0483 *.pmm file has incorrect CRC

The *.pmm file that was copied to FlashScan or AutoCal when setting up Black Box Logging is corrupt or is not a true *.pmm file.

Re-install (or repair-install) the EFILive V8 software, then use the BBL [Program] option with the “Force update of PMM files” option checked.

Regards
Paul

Ok thank you. I had to have messed this up. I had used bbl just a few hours ago.

Thanks again Paul

[Sparky8370]

I've just downloaded and installed v7.5.6.99 and v8.12.75
Now I am trying to update my boot block and firmware from BB2.06.02 (oct 16 2008) and FW 2.06.12 (jun 09 2009)
I open efi explorer, go to F12, select C:\Program Files\EFILive\V8\Firmware\FSProgV2_06_16.efw, click the boot block button, and then hit program. I get error $0023 file not found.
I re-downloaded v8.1.2.75 and installed it again (but did not remove anything first) and it still isn't working.
I have noticed in efi explorer on the file tree, or whatever you call it, on the left if you go to EFI Live>V8>firmware it has FSProgV2_06_16.efw as well as previous versions, but if you select EFI Live>V8>firmware>boot block it only has FSBootV2_06_02.efw

Don't know if that has anything to do with it, but it appears that the file is where it is supposed to be, but I am getting that $0023 error

[Sparky8370]

Nevermind, I thought I was supposed to be updating the boot block and the firmware. I just went back and re-read and didn't find that I was supposed to be updating the boot block. Unless I didn't look in the right place.

A little note though, when I just updated the FW I got a pop up message that said something like V2 not responding, please make sure Boot Block version 2.05.xx or higher installed. There was a box that said rebooting.... but another box popped up behind it that said firmware upgrade successful. I wasn't able to close the rebooting box until I moved it and closed the FW upgrade successful box that was behind it.

[joecar]

Did you get it all sorted out...?

[Sparky8370]

Yup I am all set. I re-read everything because I thought there was a new boot block, but apparently not. It was difficult trying to find where I thought I may have seen a new boot block as being part of these last updates because I was linked from thread to thread to get to it.