Examples of common failure error messages in the log

Cannot find ..\blhost\win\blhost.exe

The failure reports for missing blhost.exe in the folder blhost\win. The tool searches for blhost.exe in the bin\tools\blhost\win folder. Make sure it is available in the correct folder.

Parent topic:Examples of common failure error messages in the log

No response received for the ping command

{
   "command" : "flash-erase-all-unsecure",
   "response" : [],
   "status" : {
      "description" : "10000 (0x2710) kStatus_UnknownCommand",
      "value" : 10000
   }
}

There could be several reasons for such error. Here are some troubleshooting steps:

See the reference manual for the device to ensure that the device is supported by the MCU bootloader.
Check whether the device is powered up.
The device may boot off the image on the flash and not the MCU bootloader image from the ROM or flash. Erase the flash memory and try again to enable the device to boot into the MCU bootloader mode.
Direct boot feature can be enabled. Erase the flash and try again to boot into the MCU bootloader.

Parent topic:Examples of common failure error messages in the log

UnknownCommand

{
   "command" : "flash-erase-all-unsecure",
   "response" : [],
   "status" : {
      "description" : "10000 (0x2710) kStatus_UnknownCommand",
      "value" : 10000
   }
}

The blhost.exe can execute all MCU bootloader commands. However, the command itself may not be supported by the target MCU bootloader device. See the ROM Bootloader/Flashloader chapter of the device reference manual to check whether the command is supported.

Parent topic:Examples of common failure error messages in the log

Command disallowed when security is enabled

{
   "command" : "flash-erase-all",
   "response" : [],
   "status" : {
      "description" : "10001 (0x2711) Command disallowed when security is enable
d.",
      "value" : 10001
   }
}

The device is in a secure state and cannot be programmed. To program a secured device, add the unlock command to the ucl2.xml file.

Parent topic:Examples of common failure error messages in the log

MemoryRangeInvalid

{
   "command" : "write-memory",
   "response" : [],
   "status" : {
      "description" : "10200 (0x27D8) kStatusMemoryRangeInvalid",
      "value" : 10200
   }
}

The memory range may be in the reserved region used by the bootloader. See the device reference manual for the available memory region to program the flash and fix the address range for the command accordingly.

Parent topic:Examples of common failure error messages in the log

FlashCommandFailure

{
   "command" : "write-memory",
   "response" : [],
   "status" : {
      "description" : "105 (0x69) kStatus_FlashCommandFailure",
      "value" : 105
   }
}

The possible cause for the failure may be the flash region not being erased before writing to it. A flash-erase-region command must be called before writing to it.

Parent topic:Examples of common failure error messages in the log

Parent topic:Troubleshooting guide