ARMmbed / ARMmbed/DAPLink

hex files in release

Open
#638 0 comments 1 reaction 0 assignees View on GitHub
Dominant language
C
Stars
2.8k
Forks
1.1k
Avg merge
3d 12h
Merged PRs (30d)
1

Description

Hello world :-) I just encountered a situation where I need to put both Bootloader and Interface firmware into a bricked interface. Providing `hex` files with a release would make my life a lot easier because write address would be included right inside that `hex` file. I guess `hex` could also be used to flash Bootloader and Interface via UMS, right?

Contributor guide

Open the contributing guide

Research direction

Start by examining the release process and the Bootloader and Interface firmware artifacts. Determine how release images are produced and whether HEX files preserve the required write addresses for UMS flashing; done means both requested firmware images are available as usable HEX files in a release.

Written by the indexing model from the issue text.

Assessment

Tech stack
c
Domain
embedded-iot
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.