HEX file is not generated in "SEGGER Embedded Studio"

[takashina hiroki]

I have a question about "SEGGER Embedded Studio for ARM V4.12".

When "Build Solution" is executed, "Build failed" is displayed and an error occurs.
However, if you do "Bulid Solution" again, the error will not be displayed.
Even though the settings etc have not changed at all.
At that time, the HEX file has not been generated.
However, the MAP file is generated.

Please tell me the cause and measures.

[Øyvind]

Hello, takashina hiroki,

Are you able to reproduce the Build Failed error? Can you please provide a screenshot of the output of Segger Embedded Studio, where you change tasks to output: 

Even better, if you could copy all text in the output console and paste it here using "Insert Code". 

This should show us why your build failed. 

Kind regards,
Øyvind

[takashina hiroki]

Indicates a log that reproduces a Build Failed error.

****.hex 64-bit address 0x4b4fa300026000 out of range for Intel Hex file

Building ‘******’ from solution ‘******’ in configuration ‘Debug’
3> Compiling ‘main.c’
1> Linking ******.elf
1> C:/Program Files/SEGGER/SEGGER Embedded Studio for ARM 4.12/gcc/arm-none-eabi/bin/objcopy: ******.hex 64-bit address 0x4b4fa300026000 out of range for Intel Hex file
1> C:/Program Files/SEGGER/SEGGER Embedded Studio for ARM 4.12/gcc/arm-none-eabi/bin/objcopy:******.hex: bad value
Build failed

Please tell me how to solve the problem.

[AndreasF]

Hi.

I think the issue is related to a bug in GNU Arm Embedded Toolchain, can you please change version, either upgrade or downgrade.

Best regards,

Andreas

[takashina hiroki]

It confirmed, but my environment was "2018-q2-major".
This is different from "2018-q4-major" where the bug has been reported.
So I think this is not the cause, but what about?