User Tools

Site Tools


drafts:updater-error-codes

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
drafts:updater-error-codes [2019-09-17 08:29]
evandromr
drafts:updater-error-codes [2019-09-20 11:05] (current)
evandromr
Line 1: Line 1:
-==== Error codes ====+==== 9.4 Error codes ====
  
 In spite of our painstaking efforts, sometimes errors occur. But don't worry, it is always possible to recover your product. ​ In spite of our painstaking efforts, sometimes errors occur. But don't worry, it is always possible to recover your product. ​
Line 25: Line 25:
 | D92             | Updating failed, erasing firmware failed. The product might be unusable. Try again and check the product settings once updated. | | D92             | Updating failed, erasing firmware failed. The product might be unusable. Try again and check the product settings once updated. |
 | D93             | Error starting firmware after updating. Power cycle (off/on) your product and if that does not help\\ try updating again, and check the product settings once updated. | | D93             | Error starting firmware after updating. Power cycle (off/on) your product and if that does not help\\ try updating again, and check the product settings once updated. |
-| D94             ​| ​Could not start updating, error reading ​configuration. | +| D94             ​| ​Product updated successfullybut an error occurred ​reading ​the previous settings. Check the product settings. | 
-| D95             | Product updated successfully,​ but an error occurred restoring the settings. Check the product settings. |+| D95             | Product updated successfully,​ but an error occurred restoring the previous ​settings. Check the product settings. |
 | D96             | Updating failed due to version mismatch. Power cycle (off/on) your product and if that does not help try\\ updating again, and check the product settings once updated. | | D96             | Updating failed due to version mismatch. Power cycle (off/on) your product and if that does not help try\\ updating again, and check the product settings once updated. |
 | D97             | Dup executable too old. | | D97             | Dup executable too old. |
Line 55: Line 55:
 | B102 | An internal error occurred (Not allowed). Please send a service report to Victron Energy. | | B102 | An internal error occurred (Not allowed). Please send a service report to Victron Energy. |
  
-** XUP files **+** VE.Bus Products ** 
 + 
 +^Error ^Description^ 
 +|V2  | No product detected. Please check all the cable connections and try again.| 
 +|V3  | An unexpected timeout was triggered. Please check all the cable connections and try again.| 
 +|V4  | Incomplete vff file. Nonce missing. Please make sure you selected a valid update file and try again.| 
 +|V5  | Incomplete vff file. EEPROM lines missing. Please make sure you selected a valid update file and try again.| 
 +|V6  | The vff file contains more eeprom data than supported. Please make sure you selected a valid update file and try again.| 
 +|V7  | The calibration map in the file exceeds the device calibration map. Please make sure you selected a valid update file and try again.| 
 +|V8  | Device calibration data size bigger than expected. Please make sure you selected a valid update file and try again.| 
 +|V9  | Bootloader did not respond to bootloader setup. Please check all the cable connections and try again.| 
 +|V10 | Bootloader response to version request failed.| 
 +|V11 | Incompatible bootblock. Function version invalid.| 
 +|V12 | Incompatible bootblock. Version invalid.| 
 +|V13 | Bootloader did not start after bootblock update.| 
 +|V14 | Incompatible bootblock type.| 
 +|V15 | No or unexpected response to target id query.| 
 +|V16 | No or unexpected response to eeprom read action.| 
 +|V17 | No or unexpected response to calibration map query.| 
 +|V18 | The supplied firmware contains new unsupported calibration values. \\ The updater does not know how to handle them.| 
 +|V19 | No response received to eeprom write command. Please check all the cable connections and try again.| 
 +|V20 | Invalid response received to eeprom write command. Please check all the cable connections and try again.| 
 +|V21 | No response received to code write command. Please check all the cable connections and try again.| 
 +|V22 | Invalid response received to code write command.| 
 +|V23 | The MK2/MK3 did not respond. Please check all the cable connections and try again.| 
 +|V24 | The connected product does not match the specified model in the file. \\ Please make sure you selected a valid update file and try again.| 
 +|V25 | The hardware revision specific eeprom defaults data is corrupt. \\ Please make sure you selected a valid update file and try again.| 
 +|V26 | Updates can not be performed with a VEBUS BMS connected.| 
 +|V27 | Updates can not be performed with a DMC connected.| 
 +|V40 | Failed to start Update. could not allocate memory. Malloc error.| 
 +|V50 | Failed to start Update. File open error. Please check the file location and access permissions.\\ Make sure you selected a valid update file and try again.| 
 +|V51 | Failed to start Update. File write error. Please check file location and access permissions.\\ Make sure you selected a valid update file and try again.| 
 +|V52 | Failed to start Update. File read error. Please check file location and access permissions.\\ Make sure you selected a valid update file and try again.| 
 +|V53 | Failed to start Update. File checksum error. File corrupted or not a valid VFF file.\\ Please make sure you selected a valid update file and try again.| 
 +|V54 | Failed to start Update. File has an incompatible version number.\\ Please make sure you selected a valid update file and try again.| 
 +|V55 | Failed to start Update. File section not found. File corrupted or not a valid VFF file.\\ Please make sure you selected a valid update file and try again.| 
 +|V56 | Failed to start Update. Format error. File corrupted or not a valid VFF file.\\ Please make sure you selected a valid update file and try again.| 
 + 
 +** All other products (XUP update ​files)**
 ^Error ^Description^ ^Error ^Description^
 |X3 |Invalid updater state. Please try again.| |X3 |Invalid updater state. Please try again.|
Line 101: Line 139:
 |X45 |Update Error. Vreg Ack error: Invalid instance. Please check the connection and try again.| |X45 |Update Error. Vreg Ack error: Invalid instance. Please check the connection and try again.|
 |X46 |Update Error. Vreg Ack error. Please check the connection and try again.| |X46 |Update Error. Vreg Ack error. Please check the connection and try again.|
- 
-** VE.Bus Products ** 
- 
-^Error ^Description^ 
-|V2  | No product detected. Please check all the cable connections and try again.| 
-|V3  | An unexpected timeout was triggered. Please check all the cable connections and try again.| 
-|V4  | Incomplete vff file. Nonce missing. Please make sure you selected a valid update file and try again.| 
-|V5  | Incomplete vff file. EEPROM lines missing. Please make sure you selected a valid update file and try again.| 
-|V6  | The vff file contains more eeprom data than supported. Please make sure you selected a valid update file and try again.| 
-|V7  | The calibration map in the file exceeds the device calibration map. Please make sure you selected a valid update file and try again.| 
-|V8  | Device calibration data size bigger than expected. Please make sure you selected a valid update file and try again.| 
-|V9  | Bootloader did not respond to bootloader setup. Please check all the cable connections and try again.| 
-|V10 | Bootloader response to version request failed.| 
-|V11 | Incompatible bootblock. Function version invalid.| 
-|V12 | Incompatible bootblock. Version invalid.| 
-|V13 | Bootloader did not start after bootblock update.| 
-|V14 | Incompatible bootblock type.| 
-|V15 | No or unexpected response to target id query.| 
-|V16 | No or unexpected response to eeprom read action.| 
-|V17 | No or unexpected response to calibration map query.| 
-|V18 | The supplied firmware contains new unsupported calibration values. \\ The updater does not know how to handle them.| 
-|V19 | No response received to eeprom write command. Please check all the cable connections and try again.| 
-|V20 | Invalid response received to eeprom write command. Please check all the cable connections and try again.| 
-|V21 | No response received to code write command. Please check all the cable connections and try again.| 
-|V22 | Invalid response received to code write command.| 
-|V23 | The MK2/MK3 did not respond. Please check all the cable connections and try again.| 
-|V24 | The connected product does not match the specified model in the file. \\ Please make sure you selected a valid update file and try again.| 
-|V25 | The hardware revision specific eeprom defaults data is corrupt. \\ Please make sure you selected a valid update file and try again.| 
-|V26 | Updates can not be performed with a VEBUS BMS connected.| 
-|V27 | Updates can not be performed with a DMC connected.| 
-|V40 | Failed to start Update. could not allocate memory. Malloc error.| 
-|V50 | Failed to start Update. File open error. Please check the file location and access permissions.\\ Make sure you selected a valid update file and try again.| 
-|V51 | Failed to start Update. File write error. Please check file location and access permissions.\\ Make sure you selected a valid update file and try again.| 
-|V52 | Failed to start Update. File read error. Please check file location and access permissions.\\ Make sure you selected a valid update file and try again.| 
-|V53 | Failed to start Update. File checksum error. File corrupted or not a valid VFF file.\\ Please make sure you selected a valid update file and try again.| 
-|V54 | Failed to start Update. File has an incompatible version number.\\ Please make sure you selected a valid update file and try again.| 
-|V55 | Failed to start Update. File section not found. File corrupted or not a valid VFF file.\\ Please make sure you selected a valid update file and try again.| 
-|V56 | Failed to start Update. Format error. File corrupted or not a valid VFF file.\\ Please make sure you selected a valid update file and try again.| ​         ​ 
drafts/updater-error-codes.1568701797.txt.gz · Last modified: 2019-09-17 08:29 by evandromr