7
31
Fork
You've already forked blackmagic
23

WIP: Support for JTAG-PDI based Atmel parts #1077

Draft
dragonmux wants to merge 42 commits from feature/avr into main
pull from: feature/avr
merge into: blackmagic-debug:main
blackmagic-debug:main
blackmagic-debug:fix/pre-bmp-v3-cross-file-cleanup
blackmagic-debug:feature/bmda-remote-comms
blackmagic-debug:ALTracer/feature/aarch64-ident
blackmagic-debug:feature/better-meson-optimisation-handling
blackmagic-debug:feature/am335x-support
blackmagic-debug:feature/esp32-c3-support
blackmagic-debug:feature/cortex-ar-software-breakpoints
blackmagic-debug:feature/unit-testing
blackmagic-debug:feature/windows-usb-serial-interface-naming
blackmagic-debug:fix/bmp-external-spi
blackmagic-debug:ALTracer/feature/bluepillplus-platform
blackmagic-debug:ALTracer/feature/at32f43x-unrdp
blackmagic-debug:feature/const-correctness
blackmagic-debug:ALTracer/feature/fault_handlers
blackmagic-debug:ALTracer/feature/hazard3-ice40-support
blackmagic-debug:fix/ci-cleanup
blackmagic-debug:ALTracer/fix/gdb-10-12-thread
blackmagic-debug:ALTracer/feature/blackpill-f4-adc
blackmagic-debug:ALTracer/fix/cortex-desc-allocfail-report
blackmagic-debug:ALTracer/feature/spi-perf
blackmagic-debug:ALTracer/feature/calibrate_swd
blackmagic-debug:ALTracer/feature/blank-check
blackmagic-debug:v2.0
blackmagic-debug:v1.9
blackmagic-debug:v1.10
blackmagic-debug:v1.8

This PR establishes support for several things related to the Atmel 8-bit AVR lineup:

  • It establishes support for handling AVR parts separately from the rest.
  • It establishes support for the JTAG-PDI protocol in BMPF.
  • It establishes target support for the ATXMega256A3U processor based atop of this JTAG-PDI support.
  • It establishes debug support for that same processor based on our documentation work for the PDI protocol w/ a focus on how debug works

It should be noted that the AVRs are pretty sensitive to how scan is completed which is why #978 had to land first, and the PDI controller is very sensitive to how data is clocked into the target. What the PDI controller does not care about is how fast we do so as JTAG on these parts is decoupled from CPU clock speed completely. You can run the PDI side of things at 10MHz on a processor running at 2 and nothing will hurt for that, except you getting a lot of PDI Delay Byte responses (which we make transparent to the target code for simplicity's sake).

This PR establishes support for several things related to the Atmel 8-bit AVR lineup: * It establishes support for handling AVR parts separately from the rest. * It establishes support for the JTAG-PDI protocol in BMPF. * It establishes target support for the ATXMega256A3U processor based atop of this JTAG-PDI support. * It establishes debug support for that same processor based on our [documentation work](https://dragonmux.github.io/tempest) for the PDI protocol w/ a focus on how debug works It should be noted that the AVRs are pretty sensitive to how scan is completed which is why #978 had to land first, and the PDI controller is very sensitive to how data is clocked into the target. What the PDI controller does not care about is how fast we do so as JTAG on these parts is decoupled from CPU clock speed completely. You can run the PDI side of things at 10MHz on a processor running at 2 and nothing will hurt for that, except you getting a lot of PDI Delay Byte responses (which we make transparent to the target code for simplicity's sake).
esden (Migrated from github.com) reviewed 2022年06月27日 03:12:05 +02:00
dragonmux force-pushed feature/avr from f992b37445 to c264478529
Some checks failed
ci/woodpecker/pr/build-firmware/8 Pipeline failed
ci/woodpecker/pr/build-firmware/4 Pipeline failed
ci/woodpecker/pr/build-firmware/2 Pipeline failed
ci/woodpecker/pr/build-firmware/1 Pipeline failed
ci/woodpecker/pr/build-firmware/6 Pipeline failed
ci/woodpecker/pr/build-firmware/5 Pipeline failed
ci/woodpecker/pr/build-firmware/3 Pipeline failed
ci/woodpecker/pr/build-firmware/7 Pipeline failed
ci/woodpecker/pr/build-firmware/16 Pipeline failed
ci/woodpecker/pr/build-firmware/14 Pipeline failed
ci/woodpecker/pr/build-firmware/15 Pipeline failed
ci/woodpecker/pr/build-firmware/13 Pipeline failed
ci/woodpecker/pr/build-firmware/11 Pipeline failed
ci/woodpecker/pr/build-firmware/10 Pipeline failed
ci/woodpecker/pr/build-firmware/12 Pipeline failed
ci/woodpecker/pr/build-firmware/9 Pipeline failed
ci/woodpecker/pr/build-linux/1 Pipeline failed
ci/woodpecker/pr/build-linux/2 Pipeline failed
ci/woodpecker/pr/build-firmware/18 Pipeline failed
ci/woodpecker/pr/build-firmware/20 Pipeline failed
ci/woodpecker/pr/build-windows Pipeline failed
ci/woodpecker/pr/build-firmware/17 Pipeline failed
ci/woodpecker/pr/build-firmware/19 Pipeline failed
2026年03月22日 16:06:45 +01:00
Compare
Some checks are pending
ci/woodpecker/pr/build-firmware/8 Pipeline failed
ci/woodpecker/pr/build-firmware/4 Pipeline failed
ci/woodpecker/pr/build-firmware/2 Pipeline failed
ci/woodpecker/pr/build-firmware/1 Pipeline failed
ci/woodpecker/pr/build-firmware/6 Pipeline failed
Required
Details
ci/woodpecker/pr/build-firmware/5 Pipeline failed
ci/woodpecker/pr/build-firmware/3 Pipeline failed
ci/woodpecker/pr/build-firmware/7 Pipeline failed
ci/woodpecker/pr/build-firmware/16 Pipeline failed
ci/woodpecker/pr/build-firmware/14 Pipeline failed
ci/woodpecker/pr/build-firmware/15 Pipeline failed
ci/woodpecker/pr/build-firmware/13 Pipeline failed
ci/woodpecker/pr/build-firmware/11 Pipeline failed
ci/woodpecker/pr/build-firmware/10 Pipeline failed
ci/woodpecker/pr/build-firmware/12 Pipeline failed
ci/woodpecker/pr/build-firmware/9 Pipeline failed
ci/woodpecker/pr/build-linux/1 Pipeline failed
Required
Details
ci/woodpecker/pr/build-linux/2 Pipeline failed
ci/woodpecker/pr/build-firmware/18 Pipeline failed
ci/woodpecker/pr/build-firmware/20 Pipeline failed
ci/woodpecker/pr/build-windows Pipeline failed
Required
Details
ci/woodpecker/pr/build-firmware/17 Pipeline failed
ci/woodpecker/pr/build-firmware/19 Pipeline failed
ci/woodpecker/pr/lint
Required
This pull request has changes conflicting with the target branch.
  • src/target/jtag_devs.c
View command line instructions

Manual merge helper

Use this merge commit message when completing the merge manually.

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin feature/avr:feature/avr
git switch feature/avr
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
2 participants
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!1077
Reference in a new issue
blackmagic-debug/blackmagic
No description provided.
Delete branch "feature/avr"

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?