7
31
Fork
You've already forked blackmagic
23

New Target: AT32F45x #2249

Closed
opened 2026年05月06日 14:21:26 +02:00 by mTOTm · 0 comments
Contributor
Copy link

background

recently, I have been using the AT32F45x series chips and attempting to support them. Based on the current at32f43x.c file, if I added device identification. After a correct probe, it should work. However, in the end, I still decided to share my scan log. If a more professional person were to implement it, the result would probably be better than mine.I can assist in testing the code.

RM:https://www.arterytek.com/file/download/2624

bmda log (at32f456ce)

./build/blackmagic -t -v4
Black Magic Debug App v2.0.0-558-g85fcb0ef-dirty
 for Black Magic Probe, ST-Link v2 and v3, CMSIS-DAP, J-Link, FTDI (MPSSE) and WCH-Link
Using 1d50:6018 94728E77 Black Magic Debug
 Black Magic Probe v2.0.0-545-gba6f7fb9
Running in Test Mode
Target voltage: 3.3V
Speed set to 1.951MHz for SWD
Switching from JTAG to dormant
Switching from dormant to SWD
DP DPIDR 0x2ba01477 (v1 rev2) designer 0x43b partno 0xba
AP 0: IDR=24770011 CFG=00000000 BASE=e00ff000 CSW=e3000040 (AHB3-AP var1 rev2)
Halt via DHCSR(01030003): success after 4ms
ROM Table: BASE=0xe00ff000 SYSMEM=1, Manufacturer 43b Partno 4c4 (PIDR = 0x04000bb4c4)
0 0x0e000e000: Generic IP component - Cortex-M4 SCS (System Control Space) (PIDR = 0x04000bb00c DEVTYPE = 0x00 ARCHID = 0x0000)
-> cortexm_probe
CPUID 0x410fc241 (M4 var 0 rev 1)
cortexm_probe: Examining Part ID 0x04c4, AP Part ID: 0x04c4
Calling sam3x_probe
Calling lmi_probe
Calling apollo_3_probe
Invalid vendor ID read
Calling lpc546xx_probe
LPC546xx: Part ID 0x00000000
Calling lpc43xx_probe
Calling at32f40x_probe
at32f40x_probe: idcode = 700632d0, project_id = 16
Calling at32f43x_probe
at32f43x_probe: idcode = 700632d0, uid_byte = 16, debug_ser_id = 00001600 series = 70063000
Calling lpc40xx_probe
Calling kinetis_probe
Calling msp432e4_probe
msp432e4_probe: Device ID 0:0
Please report unknown device with Designer 0x43b Part ID 0x4c4
1 0x0e0001000: Generic IP component - Cortex-M3 DWT (Data Watchpoint and Trace) (PIDR = 0x04003bb002 DEVTYPE = 0x00 ARCHID = 0x0000)
2 0x0e0002000: Generic IP component - Cortex-M3 FBP (Flash Patch and Breakpoint) (PIDR = 0x04002bb003 DEVTYPE = 0x00 ARCHID = 0x0000)
3 0x0e0000000: Generic IP component - Cortex-M3 ITM (Instrumentation Trace Module) (PIDR = 0x04003bb001 DEVTYPE = 0x00 ARCHID = 0x0000)
4 0x0e0040000: Debug component - Cortex-M4 TPIU (Trace Port Interface Unit) (PIDR = 0x04000bb9a1 DEVTYPE = 0x11 ARCHID = 0x0000)
5 Entry 0xfff42002 -> Not present
ROM Table: END
Resuming target
*** 1 Unknown ARM Cortex-M Designer 0x43b Part ID 0x4c4 M4
Attaching to target..
Halting target
Target halted: Halt requested
Attach success
Detaching from target
## background recently, I have been using the AT32F45x series chips and attempting to support them. Based on the current at32f43x.c file, if I added device identification. After a correct probe, it should work. However, in the end, I still decided to share my scan log. If a more professional person were to implement it, the result would probably be better than mine.I can assist in testing the code. RM:https://www.arterytek.com/file/download/2624 ## bmda log (at32f456ce) ```bash ./build/blackmagic -t -v4 Black Magic Debug App v2.0.0-558-g85fcb0ef-dirty for Black Magic Probe, ST-Link v2 and v3, CMSIS-DAP, J-Link, FTDI (MPSSE) and WCH-Link Using 1d50:6018 94728E77 Black Magic Debug Black Magic Probe v2.0.0-545-gba6f7fb9 Running in Test Mode Target voltage: 3.3V Speed set to 1.951MHz for SWD Switching from JTAG to dormant Switching from dormant to SWD DP DPIDR 0x2ba01477 (v1 rev2) designer 0x43b partno 0xba AP 0: IDR=24770011 CFG=00000000 BASE=e00ff000 CSW=e3000040 (AHB3-AP var1 rev2) Halt via DHCSR(01030003): success after 4ms ROM Table: BASE=0xe00ff000 SYSMEM=1, Manufacturer 43b Partno 4c4 (PIDR = 0x04000bb4c4) 0 0x0e000e000: Generic IP component - Cortex-M4 SCS (System Control Space) (PIDR = 0x04000bb00c DEVTYPE = 0x00 ARCHID = 0x0000) -> cortexm_probe CPUID 0x410fc241 (M4 var 0 rev 1) cortexm_probe: Examining Part ID 0x04c4, AP Part ID: 0x04c4 Calling sam3x_probe Calling lmi_probe Calling apollo_3_probe Invalid vendor ID read Calling lpc546xx_probe LPC546xx: Part ID 0x00000000 Calling lpc43xx_probe Calling at32f40x_probe at32f40x_probe: idcode = 700632d0, project_id = 16 Calling at32f43x_probe at32f43x_probe: idcode = 700632d0, uid_byte = 16, debug_ser_id = 00001600 series = 70063000 Calling lpc40xx_probe Calling kinetis_probe Calling msp432e4_probe msp432e4_probe: Device ID 0:0 Please report unknown device with Designer 0x43b Part ID 0x4c4 1 0x0e0001000: Generic IP component - Cortex-M3 DWT (Data Watchpoint and Trace) (PIDR = 0x04003bb002 DEVTYPE = 0x00 ARCHID = 0x0000) 2 0x0e0002000: Generic IP component - Cortex-M3 FBP (Flash Patch and Breakpoint) (PIDR = 0x04002bb003 DEVTYPE = 0x00 ARCHID = 0x0000) 3 0x0e0000000: Generic IP component - Cortex-M3 ITM (Instrumentation Trace Module) (PIDR = 0x04003bb001 DEVTYPE = 0x00 ARCHID = 0x0000) 4 0x0e0040000: Debug component - Cortex-M4 TPIU (Trace Port Interface Unit) (PIDR = 0x04000bb9a1 DEVTYPE = 0x11 ARCHID = 0x0000) 5 Entry 0xfff42002 -> Not present ROM Table: END Resuming target *** 1 Unknown ARM Cortex-M Designer 0x43b Part ID 0x4c4 M4 Attaching to target.. Halting target Target halted: Halt requested Attach success Detaching from target ```
Sign in to join this conversation.
No Branch/Tag specified
main
fix/pre-bmp-v3-cross-file-cleanup
feature/bmda-remote-comms
ALTracer/feature/aarch64-ident
feature/better-meson-optimisation-handling
feature/am335x-support
feature/esp32-c3-support
feature/cortex-ar-software-breakpoints
feature/unit-testing
feature/windows-usb-serial-interface-naming
fix/bmp-external-spi
ALTracer/feature/bluepillplus-platform
ALTracer/feature/at32f43x-unrdp
feature/const-correctness
ALTracer/feature/fault_handlers
ALTracer/feature/hazard3-ice40-support
fix/ci-cleanup
ALTracer/fix/gdb-10-12-thread
ALTracer/feature/blackpill-f4-adc
ALTracer/fix/cortex-desc-allocfail-report
ALTracer/feature/spi-perf
ALTracer/feature/calibrate_swd
ALTracer/feature/blank-check
feature/avr
v2.0
v1.9
v1.10
v1.8
v2.1.0-rc1
v2.0.0
v2.0.0-rc2
v2.0.0-rc1
v1.9.3
v1.10.2
v1.10.1
v1.10.0
v1.10.0-rc1
v1.10.0-rc0
v1.9.2
v1.8.3
v1.9.1
v1.9.0
v1.9.0-rc1
v1.9.0-rc0
v1.8.2
v1.8.1
v1.8.0
v1.7.1
v1.7
v1.6.2-rc1
1.6.2-rc0
v1.6.1
v1.6
v1.6-rc1
v1.6-rc0
production_01
production_00
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#2249
Reference in a new issue
blackmagic-debug/blackmagic
No description provided.
Delete branch "%!s()"

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?