why the HEX file compiled by Eclipse is different from compiled by keil ?

RE: why the HEX file compiled by Eclipse is different from compiled by keil ?

Alex — Fri, 08 Jan 2016 03:58:07 GMT

yes ,my board is 51422 XXAC

RE: why the HEX file compiled by Eclipse is different from compiled by keil ?

RK — Fri, 08 Jan 2016 03:42:19 GMT

What. Revision. Chip. Do. You. Have. On. Your. Test. Board?

RE: why the HEX file compiled by Eclipse is different from compiled by keil ?

Alex — Fri, 08 Jan 2016 03:39:14 GMT

thx for ur response ,i try to use debug mode to find the problem ,but it show up something (i post in above question ),how to solve it?

RE: why the HEX file compiled by Eclipse is different from compiled by keil ?

RK — Fri, 08 Jan 2016 03:34:30 GMT

you haven't answered the main basic question here which is what chip revision do you ACTUALLY have on the board. if it's not an XXAC, don't use the XXAC linker file, use the XXAA or XXAB one.

RE: why the HEX file compiled by Eclipse is different from compiled by keil ?

RK — Thu, 07 Jan 2016 12:46:32 GMT

if those two hex files have the SP in the right place, the lefthand one has the stack pointer at 0x20008000 and the right-hand one at 0x20000808. The lefthand one is consistent with the normal gcc 51422_xxac.ld file which bungs the stack at the end, so I'm guessing that's the gcc one.

So if the chip variant it's running on isn't an XXAC, that's quite possibly the issue.

RE: why the HEX file compiled by Eclipse is different from compiled by keil ?

awneil — Thu, 07 Jan 2016 12:32:32 GMT

Examining the Memory Map file should show if the code placement is wrong.

Do you have the map for the Keil build?

RE: why the HEX file compiled by Eclipse is different from compiled by keil ?

RK — Thu, 07 Jan 2016 12:17:25 GMT

Random guess - you're using the linker file for the XXAC version chip but actually have an XXAA or XXAB chip so it crashes on launch.

And yes 'really', two compilers will produce radically different code from the same source. Two versions of gcc will produce different code from the same source, one version of gcc will produce two totally different binary files if even one option was changed.

RE: why the HEX file compiled by Eclipse is different from compiled by keil ?

awneil — Thu, 07 Jan 2016 12:14:20 GMT

I asked about Warnings - not errors

RE: why the HEX file compiled by Eclipse is different from compiled by keil ?

Alex — Thu, 07 Jan 2016 12:07:22 GMT

there is no error after i built,it just like what i post above

RE: why the HEX file compiled by Eclipse is different from compiled by keil ?

awneil — Thu, 07 Jan 2016 11:47:03 GMT

Do you receive any warnings in either of the builds?

Again, you need to debug the code to see where it's failing.

RE: why the HEX file compiled by Eclipse is different from compiled by keil ?

Alex — Thu, 07 Jan 2016 11:31:52 GMT

really? if problem is not in hex file ,it may in where at the above step? have u find that i miss or make mistake anything? if there is ,PLZ tell me .thx!

RE: why the HEX file compiled by Eclipse is different from compiled by keil ?

awneil — Thu, 07 Jan 2016 10:57:30 GMT

You should not expect the hex files from different compilers to be identical.

Different compilers will produce different results; this is natural - it is not a problem as such.

If one works and the other doesn't, you are going to have to do some debugging to find where the problem is occurring...