objcopy: regression when converting binary to ihex

[Chris Reed]

The GNU Arm Embedded 8-2018-q4-major release for Windows introduces a regression in arm-none-eabi-objcopy. The problem appears when converting a binary file to Intel hex. (Even though the format is called "Intel" hex, it is widely used in Arm embedded systems.)

The attached binary demonstrates the problem.

This is the command line, using the attached file, and the error reported by objcopy:
--
$ arm-none-eabi-objcopy -v -I binary -O ihex -B arm \
   max32630fthr.bin test.hex
copy from `max32630fthr.bin' [binary] to `test.hex' [ihex]
arm-none-eabi-objcopy: test.hex 64-bit address 0x4b4fa300000000 out of range for Intel Hex file
arm-none-eabi-objcopy: test.hex: bad value
--

The problem does not happen on Mac or Linux, and it does not happen with 7-2018-q2-update on Windows.

Here is what the output should look like:
--
copy from `max32630fthr.bin' [binary] to `test.hex' [ihex]
--

[Liviu Ionescu (ilg)]

please see: https://bugs.launchpad.net/gcc-arm-embedded/+bug/1810274

[Liviu Ionescu (ilg)]

This bug, plus many other, were already fixed in the latest release of GNU MCU Eclipse ARM Embedded GCC. Some required small patches, for other updating to more recent GNU commits was enough.

It would be good if ARM would consider an update release to fix these problems.

Since then you can use the GME distribution.

[Edwin Hoeks (ehoeks)]

Hopefully Arm will update it's official toolchain to. Keeping this bug present does not look good on them.

[Chris Reed (creedflit)]

Thanks, Liviu! As usual, you're ahead of the game. :)

And sorry I didn't see 1810274, I did search existing bugs but somehow missed it.

[Chris Reed (creedflit)]

Marking as duplicate of 1810274.

[Liviu Ionescu (ilg)]

Thank you, Chris. I'm glad if my projects can be of any help.