E

  • Error code 0x81
    1.1 Error code 0x81 Is returned by many routines which were accessing UART (for read or write) and UART port was unexpectedly closed by the Host ...
  • Error code 0x82
    1.2. Error code 0x82 Returned by routines which expect a different input parameter. Most often is returned by the h/w scripts (*.has) processing block in case ...
  • Error code 0x83
    1.3. Error code 0x83 Returned by firmware in case there was an attempt to use some specific function like read/write target memory by 8- 16- 32- ...
  • Error code 0x60
    1.5. Error code 0x60 Returned by the JTAG shifter block when timeout happens. This is possible when RTCK mode is active and firmware waits for RTCK ...
  • ERROR(0x42): Communication is not established. Terminating.
    1.7. Error code 0x42 Returned by the box’s firmware in case there was nothing detected on the JTAG chain.    Solution: Hold power key on target device during connection ...
  • ERROR: Wrong response code from the RIFF Box: 0x44
    1.9. Error code 0x44 Returned by the box’s firmware if attempted target HALT operation failed.   Solution: Check target device connection. In case You're trying to access device based ...
  • Error code 0x45
    1.10. Error code 0x45 Returned by box’s firmware when attempt to read ARM9 ICE Breaker register failed. This happens when target unexpectedly loses power or connection ...
  • Error code 0x46
    1.11. Error code 0x46 Returned by box’s firmware when attempt to write ARM9 ICE Breaker register failed. See error code 0x45 for symptoms. ...
  • Error code 0x47
    1.12. Error code 0x47 Returned by box’s firmware as status whether target is currently running or halted. Current code means target is running. ...
  • Error code 0x48
    1.13. Error code 0x48 Returned by box’s firmware when attempt to start target running (to exit from debug/halted state) failed. Could happen when user clicks Run ...
  • Error code 0x49
    1.14 Error code 0x49 Returned by box’s firmware when some timeout happens during JTAG communication between box and target. Can happen due to erroneous connection, spontaneous ...
  • Error codes 0x54, 0x55
    1.16. Error codes 0x54, 0x55 May be returned by box during firmware update stage. These errors are severe and can happen due to box’s h/w malfunction ...
  • ERROR: DCC Loader has reported Error Code = 0x22
    2.1. Error code 0x22 Returned by the DCC Loader in case received packet of data failed to pass CRC32 checksum check. May happen due to spontaneous ...
  • Error code 0x23
    2.2. Error code 0x23 Returned by the DCC Loader when supplied parameter to requested command is wrong – for example during read operation supplied read length ...
  • Error code 0x2D
    2.5. Error code 0x2D Returned by the DCC Loader when it fails to erase or program flash memory due to active write protection. Shall not happen ...
  • Error code 0x2E
    2.6. Error code 0x2E Returned by the DCC Loader when it fails to erase flash memory’s logical block and cannot determine the reason of such error.   Solution: Ask ...
  • Error code 0x2F
    2.7. Error code 0x2F Returned by the DCC Loader when it fails to wait till specific write protection unlock procedure on some memory chips is signaled ...
  • Error code 0x30
    2.7. Error code 0x30 Returned by the DCC Loader when it fails to perform specific write protection unlock procedure on some memory chips when it is ...
  • Error code 0x31
    2.7. Error code 0x31 Returned by the DCC Loader when it fails to program part of flash memory due to unrecognized (by the DCC Loader) reasons. ...
  • Error code 0x2A
    2.7. Error code 0x2A Returned by the DCC Loader when it attempts to program part of flash memory and fails waiting for selected flash memory controller ...
  • Error code 0x2B
    2.7. Error code 0x2B Returned by the DCC Loader when it attempted to erase block of flash memory and fails waiting for selected flash memory controller ...
  • Error code 0x27
    2.7. Error code 0x27 Returned by the DCC Loader when it fails waiting for selected flash memory controller to assert ready status. Explanation: May happen if target is ...
  • ERROR: Read Failed with Error Code: 0x28
    2.7. Error code 0x28 Returned by the DCC Loader when it fails reading part of flash memory. Explanation: May happen if target is currently in some unrecoverable h/w ...
  • Error code 0x3C
    2.7. Error code 0x3C Returned by the DCC Loader when it detects in some targets an active write protection – thus erase/program operations will not be ...
  • Error code 0x3D
    2.7. Error code 0x3D Returned by the DCC Loader in case its internal memory buffer cannot satisfy current needs. Explanation: Can happen when DCC Loader has limited amount ...
  • Error: Wrong DCC Data Checksum
    2. Wrong DCC Data Checksum  Happens when DCC Loader which is being executed by target is too slow to respond through the DCC channel. Since RIFF ...
  • ERROR: Read/Write memory failed during H/W Init
    ERROR: Read/Write memory failed during H/W Init This error can happen due to few reasons: NRST or GND pins not connected properly Wrong model selected Hardware failure Solution: Connect NRST and ...
  • ERROR: Main data file size is less than requested to flash to main
    ERROR: Main data file size is less than requested to flash to main   Happens when "Autofullflash size" is used and file selected in main field is ...
  • ERROR: Set I/O Voltage failed. Real reading is "value"
    ERROR: Set I/O Voltage to"value" failed. Real reading is "value".   Can happen due to following reasons: Connection with device is wrong Target device has developed hardware  malfunction RIFF Box ...
  • ERROR: No response from the RIFF Box.
    ERROR: No response from the RIFF Box.   Can happen due to numerous of reasons. Mostly it's caused by wrongly configured RTCK/TCK sampling value, or badly connected ...
  • ERROR: The RTCK Signal does not respond.
    ERROR: The RTCK Signal does not respond.   Can happen due to numerous of reasons: RTCK  not connected RTCK signal doesn't exist for current target device Target device is wrongly ...
  • ERROR: RAM memory selftest failed.
    ERROR: RAM memory selftest failed.   This error can be caused by numerous reasons. In most cases, it's due to bad connection (unstable NRST signal line), or ...
  • ERROR: DCC Loader has reported Error Code = 0x3E (0x007FFF 0x010000)
    ERROR: DCC Loader has reported Error Code = 0x3E (0x007FFF <> 0x010000)  This is returned by DCC loader in case that eMMC internal controller fails to ...
  • ERROR: Timeout while waiting for DCC Loader response.
    ERROR: Timeout while waiting for DCC Loader response.   Returned by DCC loader, usually during write operations. There is number of reasons which can cause this error:  RTCK/TCK ...
  • ERROR: Failed due to multiple communication errors.
    ERROR: Failed due to multiple communication errors.  This error is returned in case that connection between box and target device is unstable. - Badly connected/soldered - Bad ribbon ...
  • ERROR: DCC Loader has reported Error Code = 0x35
    This is returned by DCC loader in case that eMMC internal controller fails to write specific block. Usually it means that eMMC chip has failed, ...
  • ERROR: Failed to unpack received data. Terminating.
    Returned by JTAG Manager in case when it's impossible to decrypt received data from DCC loader.Restarting JTAG Manager usually helps, otherwise it's caused by hardware ...