bootloader gets destroyed every time

[1inguini]

I can upload sketch, but once I do that the arduino stops getting detected by the computer.
I can fix it by burning arduino bootloader to it (arduino-ide seems to work fine), but if I upload sketch again the same thing happens.
My arduino is a clone of SparkFun pro micro.

[per1234]

Which version of arduino-cli are you using?

Please provide the arduino-cli commands you are using to compile and upload.

[1inguini]

command: probably ➤ arduino-cli upload -p /dev/ttyACM0 --fqbn SparkFun:avr:promicro Arduino/FirstSketch/ accrding to my fish's history.

version: arduino-cli version 0.3.4-alpha.preview

[cmaglie]

Is the Arduino IDE uploading without the issue?
If yes please:

1. please provide the verbose output of the Arduino IDE
2. provide the verbose output of the arduino-cli
   so we can compare them.

If you can test also the latest version of the cli (0.5.0) it would be great.

[bjanders]

I have the same issue, also with a SparkFun pro micro clone. I used a self compiled arduino-cli, commit 550179e

[ubidefeo]

@bjanders when you compile for a target board you also build a version of the firmware with included bootloader.
This is the one you should burn (upload) onto the board.

essentially it becomes a two part operation in which you compile choosing to --export-binaries,
thus creating a local build folder inside your sketch, and then upload with --input-file and passing the build/SparkFun.avr.micro/MySketch.ino.with_bootloader.hex

unfortunately I seem to have found an issue with this particular file in my case, which might be related to an old problem we had with CLI assembling the bootloader binary with the newly created hex.

@cmaglie and I are going to investigate asap

here's a recap of my actions for a sketch named BlinkMe.
I'm inside the BlinkMe folder

arduino-cli compile --export-binaries -b arduino:avr:micro -v
arduino-cli upload -b arduino:avr:micro -v -P arduinoisp --input-file build/arduino.avr.micro/BlinkMe.ino.with_bootloader.hex