-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add feature to include FlashDevice device description #14
Conversation
Does #19 work for your use case? |
I found a few issues in your branch:
There are a couple of issues with
There is one quirky bit in the scripts that expect the Running
And with the dummy variable:
You can also reproduce with:
|
@theanh2020: I have looked at rebasing this PR. Some of this have been pulled into flash-algorithm but not in a released version. I will ask them when a release will happen. |
I just released |
359d28c
to
5a0506e
Compare
5a0506e
to
b2bfad7
Compare
Tested with target-gen, pyOCD's generate_blobs.py and DAPLink's generate_flash_algo.py. |
@mbrossard it would make more sense to ask for a review from someone with authority to merge, that particular github account has not contributed to this project (or any other project) and looks like a bot to me. |
That account somehow approved a previous version. So I thought the polite thing was to re-request a review. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, thanks for following up on this PR
The scripts from FlashAlgo rely on the
FlashDevice
struct (see https://www.keil.com/pack/doc/CMSIS/Pack/html/flashAlgorithm.html) and the existence of aPrgData
section.