7
32
Fork
You've already forked blackmagic
23

Make adaption to different STM32 boards easier #12

Merged
UweBonnes merged 43 commits from master into master 2013年02月18日 09:49:35 +01:00
UweBonnes commented 2013年02月03日 16:20:32 +01:00 (Migrated from github.com)
Copy link

Hello,

as my comment on the sourceforge blackmagic mailing list went unnoticed for two weeks, here a pull request as base for discussion. Again my target is to make porting of blackmagic to different(STM32) boards easier with as few code duplication as possible. In fact, I have blackmagic now running on

There are some patches of general interest in the pull request, like option byte handling for F3, use of the STM32 CRC unit etc. I implemented when need for that feature was seen.

Please tell how to proceed

  • Do you need the patches of general interest as separate pull request?
  • Any chance for inclusion? What needs to be done for that?

Thanks

Hello, as my comment on the sourceforge blackmagic mailing list went unnoticed for two weeks, here a pull request as base for discussion. Again my target is to make porting of blackmagic to different(STM32) boards easier with as few code duplication as possible. In fact, I have blackmagic now running on - the F103 of discovery boards - the F407 on the F4 discovery board - two other local STM boards To get access to the JTAG chains of the F103 on the discovery to reprogramm as black magic debug probe, find some hints on http://embdev.net/articles/STM_Discovery_as_Black_Magic_Probe For the USPS_F407, find eagle schematic on https://github.com/UweBonnes/wiki_fuer_alex/tree/master/layout There are some patches of general interest in the pull request, like option byte handling for F3, use of the STM32 CRC unit etc. I implemented when need for that feature was seen. Please tell how to proceed - Do you need the patches of general interest as separate pull request? - Any chance for inclusion? What needs to be done for that? Thanks
Sign in to join this conversation.
No reviewers
Labels
Clear labels
BMD App
Black Magic Debug App (aka. PC hosted) (not firmware)
BMP Firmware
Black Magic Probe Firmware (not PC hosted software)
Bug
Confirmed bug
Build system
Build system
Can't reproduce
Maintainers can't reproduce this problem
CI
Continuous Integration System
Contribution wanted
User contributions welcome
Documentation
Project documentation
Draft
Work in progress draft
Duplicate
This issue or pull request already exists
Enhancement
General project improvement
Feedback wanted
Requires additional submitter feedback
Foreign Host Board
Non Native hardware to runing Black Magic firmware on
GDB
Issue/PR related to GDB
Good first issue
Good for newcommers
HwIssue Mitigation
Solving or mitigating a Hardware issue in Software
Information Needed
Maintainers need more information
NativeHardware
Official Black Magic Debug Hardware
New Host Board
New hardware to run Black Magic firmware on
New Target
New debug target
Off Topic
Something that does not involve the project in any way
Potential Bug
A potential, unconfirmed or very special circumstance bug
Regression
Bug caused by a regression
User Interest Needed
More user interest required before consideration
User Testing Needed
Looking for user testing reports
Won't fix
Outside of the project scope or works as intended
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
blackmagic-debug/blackmagic!12
Reference in a new issue
blackmagic-debug/blackmagic
No description provided.
Delete branch "master"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?