v1.6.2 - Burning bootloader unable to locate bootloader hex

Open
#658 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
55/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
arduino, c
Domain
tooling

Research direction

Start by checking the DxCore 1.6.2 board package configuration and bootloader file naming or path settings for AVR128DB48 with Optiboot on UART0. Compare them with v1.5.11 and reproduce the burn bootloader error using jtag2updi; done means the package locates the hex file and the bootloader burn succeeds.

Written by the indexing model from the issue text.

Description

Hello,

Just only downloaded a fresh copy of the Arduino 1.8.19 and also the Arduino IDE. Installed the latest v1.6.2 board package of DxCore and tried to burn bootloader of AVR128DB48 with Optiboot on UART0 PA0 & PA1 using jatg2updi but it can't locate the hex file. File is definitely there but there's some path wrongly set I believe. Works fine on v1.5.11.

Here's the error:
**OS error: file {bootloader.class}_ser0_extr.hex is not readable: No such file or directory**

Dominant language
C
Stars
239
Forks
64
PR merge metrics
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from SpenceKonde/DxCore

All issues in SpenceKonde/DxCore

Similar issues

More C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.