Hi!
  I'm using an Adafruit Metro M0 Express, and the file <project>.with_bootloader.hex generated is just wrong. The first part is the project in normal Intel .hex format, but it looks like the end of the file is the bootloader in binary format. Of course, the result is a bad file.

  It's not a big problem for me, I can manually combine my bootloader with the good <project>.hex and use that instead, but is it a bug with Visual Micro?

Martin

Attached: The zipped BlinkWithoutDelay.with_bootloader.hex and the bootloader in both .bin and .hex.

Hi!

Tim@Visual Micro wrote on Oct 1^st, 2018 at 4:22pm:

The boards.txt does have a bootloader.file= section pointing to a binary file:

bin 

What I did to create the bootloader .hex file?
I have a J-Link EDU mini connected to the board. I used AS7 Tools>Device programming> Fuses/Memories.

1. I cleared bootloader protection fuses, 
2. erased the entire flash chip, 
3. re-uploaded the .bin file and 
4. restored bootloader protection fuses. 
5. Then, I read back the flash in .hex format.

I might have edited the file to keep only the bootloader lines and delete those from memory 0x2000 and above.

Now, the .bin files (with .elf and .uf2) are provided with the Adafruit SAMD board package from the Arduino Manager.

https://adafruit.github.io/arduino-board-index/package_adafruit_index.json 

There is a dependency on the Arduino SAMD package, install it first.

If you need more detail, just ask!
Thanks,
Martin
Edit: I may have misunderstood the question, clarification below:
The <project>.with_bootloader.hex file is auto-generated when I select to Build>Build Solution or Build Project in AS7.

Tim@Visual Micro wrote on Oct 1^st, 2018 at 5:20pm:

  I am not sure about what you mean by that, the bad .hex file is a (crude) cat between the compiled project in Intel .hex format (that is good, but without Intel .hex file end marker) with the unprocessed, raw binary bootloader code from the .bin file (not in Intel .hex format, BAD!). Since the .hex file is NOT ENTIRELY in Intel .hex format, it is unusable and rejected by the flash programmer.

It looks like something expects the binary bootloader to be in .hex format. I don't know if Visual micro is at fault or if Adafruit mistakenly feeds a binary instead of a .hex, but in the end, the file in the Release or Debug folder is messed up because some code expects .hex but does not check. Maybe a bug in AS7?

Tim@Visual Micro wrote on Oct 1^st, 2018 at 5:20pm:


  Yes, the board has a Burn bootloader option in the Arduino IDE.

Anyway, this bug not a show stopper for me whatever who or what causes it. Visual Micro's upload mechanism works well. 

Thanks!
Martin

Even better: Don't erase the bootloader and use the normal mechanism!

But yeah, I changed the setting to erase the program only instead of Erase chip... I found the bug while trying all sorts of ways to get the Debug to work previously. 

  Since, I learned how to erase, reload and protect my bootloader, and some ways to debug my project. I am still struggling at times, I started this whole adventure in Arduino programming in July! I had no knowledge in C/C++ programming then!

Now if I could figure this: (not in this thread!)

:(.bss.radioArgvList+0x0): multiple definition of radioArgvList
ores\arduino\Print.h:62: first defined here
: error: ld returned 1 exit status 

Martin