Same sketch -> different HEX than with IDE 1.8.19

Development Tools IDE 2.x
1

Same topic that just got closed without resolution:
Previous Topic

One would think someone on the development team would like to find out why there is a difference. It's quite easy to replicate by compiling an example Blink project.

Thanks

2

I do not have a clue as to what you are saying. There are many reasons the HEX file would be different. Did you use the same hardware? Did you use the same compiler? Was the source code exactly the same? Did you use a different IDE? Was the computer set for the same date and time? There are many more.

3

Sorry for the questions

  1. Are you running the IDEs on different PCs or on the same PC?
  2. Are you running a portable install of 1.x?
  3. Which versions of 1.x and 2.x are you using?
  4. Which board are you compiling for?
  5. Please enable verbose output during compilation in file / preferences for both IDEs. Next compile blink under both IDEs for the same board and post the output here using code tags.

Note:
I do not have access to a system with IDE 2.x so can't compile for that.

4

My inquiry was to the developers. The previous topic was clear but yes, same hardware, uP, board, etc.

I can even compile using Visual Studio with my Visual Micro extension and both the main and combined bootloader .hex files match using 1.8.19. Not so much for 2.3.2.

Finally, compile your own sketch under both IDE's. That way you can ensure your setup is identical. I've been there and done it and hence the question to the "developers".

5

This topic was automatically closed 180 days after the last reply. New replies are no longer allowed.