Multiple different programming errors occursLink to Multiple different programming errors occurs

ProblemLink to Problem

Programming fails systematically with errors at the same operation or at different operations each time. The log shows that these errors systematically occurs during a 'verify' step. This can be diagnosed through the following or similar messages in the programming log :

[ERROR] 13. 5. 2019 16:17:35: Error: Command 'verify:rootfs.ubi:8388608': Failed verification. First error at offset 0x01509000
or
[ERROR] 13. 5. 2019 16:08:18: Error: Command 'verify:zImage:2097152': Could not read pages at address 0x00219000 (applet returned success but did not return enough data)
or
[ERROR] 13. 5. 2019 16:17:35: Could not verify image 'XXXXX' at address 0x800000 : status=4294967295

This generally means that a write error occurred and the error is detected during the verification step. The write errors are generally due to a bad quality or damaged USB cable.

In the worst cases, errors can even occur at the very start of the programming :

[INFO] 26.11.2019 11:56:54.056 : Reading device information
[VERBOSE] 26.11.2019 11:56:55.734 : Opening serial port 'ttyACM0'
[VERBOSE] 26.11.2019 11:56:55.836 : Connection opened.
[ERROR] 26.11.2019 11:57:05.879 : /tmp/.mount_lorix-uLOmSU/resources/sam-ba/qml/SAMBA/Applet.qml:232: Error: Could not initialize applet (status: undefined)
or
[VERBOSE] 26.11.2019 11:57:17.226 : Opening serial port 'ttyACM0'
[ERROR] 26.11.2019 11:57:27.751 : Error: Could not switch monitor on port 'ttyACM0' to binary mode
or
[ERROR] 26.11.2019 11:58:08.518 : Could not erase region 0x0 to 0x40000 : status=255

This may be due to a malfunctioning USB port, a bad quality or damaged USB cable, a too long (>3m) USB cable or USB chain (multiple cable, USB hub).

Do not disable verification

If you disable the 'Verify' option for programming, the Programming Tool may report a successful programming but the gateway will most likely malfunction. Never disable the 'Verify' option until you know what you are doing.

SolutionLink to Solution

  • Change the USB cable.
  • Take a high quality, shorter USB cable.
  • Be sure the cable is not damaged.
  • Try another USB port.
  • Do not use a USB hub.