Build blackmagic app to run on arm orangepi #2146

pistoletov1974 commented 2025年08月30日 14:59:25 +02:00 (Migrated from github.com)

Hi! I want to try running a debugging application on a single-board computer, but I get an error when I try to build it.

root@orangepipc:~/blackmagic# meson setup build -Dprobe=''
The Meson build system
Version: 0.53.2
Source dir: /root/blackmagic
Build dir: /root/blackmagic/build
Build type: native build
meson.build:196:3: ERROR: Expecting rparen got string.
 f'@bmf_base_name@_firmware',
 ^
For a block that started at 195,21
 bmf_elf = executable(
 ^

Does anyone have experience running an application on a device like this? This would be a great way to debug remote devices.

Hi! I want to try running a debugging application on a single-board computer, but I get an error when I try to build it. ``` root@orangepipc:~/blackmagic# meson setup build -Dprobe='' The Meson build system Version: 0.53.2 Source dir: /root/blackmagic Build dir: /root/blackmagic/build Build type: native build meson.build:196:3: ERROR: Expecting rparen got string. f'@bmf_base_name@_firmware', ^ For a block that started at 195,21 bmf_elf = executable( ^ ``` Does anyone have experience running an application on a device like this? This would be a great way to debug remote devices.

dragonmux commented 2025年08月30日 15:16:42 +02:00

For that setup, you want to build BMDA - drop the -Dprobe='' part. meson setup build w/ the gpiod dev libraries installed will get you a suitable binary to work with your SBC.

For that setup, you want to build BMDA - drop the `-Dprobe=''` part. `meson setup build` w/ the gpiod dev libraries installed will get you a suitable binary to work with your SBC.

pistoletov1974 commented 2025年08月31日 12:31:02 +02:00 (Migrated from github.com)

For that setup, you want to build BMDA - drop the -Dprobe='' part. meson setup build w/ the gpiod dev libraries installed will get you a suitable binary to work with your SBC.
I installed gpiod lib - apt install gpiod
and try to build BMDA without Dprobe option. Result is the same error.
May be problem in meson version?

root@orangepipc:~/blackmagic# meson setup build
The Meson build system
Version: 0.53.2
Source dir: /root/blackmagic
Build dir: /root/blackmagic/build
Build type: native build
meson.build:196:3: ERROR: Expecting rparen got string.
 f'@bmf_base_name@_firmware',
 ^
For a block that started at 195,21
 bmf_elf = executable(
 ^
A full log can be found at /root/blackmagic/build/meson-logs/meson-log.txt

> For that setup, you want to build BMDA - drop the `-Dprobe=''` part. `meson setup build` w/ the gpiod dev libraries installed will get you a suitable binary to work with your SBC. I installed gpiod lib - apt install gpiod and try to build BMDA without Dprobe option. Result is the same error. May be problem in meson version? ``` root@orangepipc:~/blackmagic# meson setup build The Meson build system Version: 0.53.2 Source dir: /root/blackmagic Build dir: /root/blackmagic/build Build type: native build meson.build:196:3: ERROR: Expecting rparen got string. f'@bmf_base_name@_firmware', ^ For a block that started at 195,21 bmf_elf = executable( ^ A full log can be found at /root/blackmagic/build/meson-logs/meson-log.txt ```

dragonmux commented 2025年08月31日 16:29:47 +02:00

Yeah, per the build guides and the meson.build in the root of the project, minimum Meson version is 0.63 - you'll need to get this from PyPI.

With regards gpiod, you'll need the -dev package too (libgpiod-dev) so the build system can find the development files to link against. This is just a quirk of Debian-based distros like Raspberian.

Yeah, per the build guides and the meson.build in the root of the project, minimum Meson version is 0.63 - you'll need to get this from PyPI. With regards gpiod, you'll need the `-dev` package too (`libgpiod-dev`) so the build system can find the development files to link against. This is just a quirk of Debian-based distros like Raspberian.

pistoletov1974 commented 2025年09月03日 16:26:49 +02:00 (Migrated from github.com)

Thank you! I was able to build the firmware and the app. I tried to connect to the AT32F437ZMT7, but it seems that the chip is not being detected correctly. Is it fully supported, or only certain versions?
UART work fine at 460800 speed-) minicom -b 460800 -D /dev/ttyBmpTarg

root@orangepipc:~/blackmagic/build# ./blackmagic -t
Black Magic Debug App v2.0.0-95-g1e3bcd8a
 for Black Magic Probe, ST-Link v2 and v3, CMSIS-DAP, J-Link, FTDI (MPSSE) and WCH-Link
Using 1d50:6018 306C33683235 Black Magic Debug
 Black Magic Probe (BlackPill-F401CC) v2.0.0-95-g1e3bcd8a-dirty
Running in Test Mode
Target voltage: Unknown
Speed set to 7.000MHz for SWD
Switching from JTAG to dormant
Switching out of dormant state into 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 22ms
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)
Invalid vendor ID read
LPC546xx: Part ID 0x00000000
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 0x0e0041000: 0x00000000 <- does not match preamble (0xb105000d)
ROM Table: END
*** 1 AT32F435 M4
RAM Start: 0x20000000 length = 0x10000
RAM Start: 0x20010000 length = 0x50000
Flash Start: 0x08000000 length = 0x200000 blocksize 0x1000
Flash Start: 0x08200000 length = 0x1f0000 blocksize 0x1000

Thank you! I was able to build the firmware and the app. I tried to connect to the AT32F437ZMT7, but it seems that the chip is not being detected correctly. Is it fully supported, or only certain versions? UART work fine at 460800 speed-) minicom -b 460800 -D /dev/ttyBmpTarg ``` root@orangepipc:~/blackmagic/build# ./blackmagic -t Black Magic Debug App v2.0.0-95-g1e3bcd8a for Black Magic Probe, ST-Link v2 and v3, CMSIS-DAP, J-Link, FTDI (MPSSE) and WCH-Link Using 1d50:6018 306C33683235 Black Magic Debug Black Magic Probe (BlackPill-F401CC) v2.0.0-95-g1e3bcd8a-dirty Running in Test Mode Target voltage: Unknown Speed set to 7.000MHz for SWD Switching from JTAG to dormant Switching out of dormant state into 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 22ms 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) Invalid vendor ID read LPC546xx: Part ID 0x00000000 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 0x0e0041000: 0x00000000 <- does not match preamble (0xb105000d) ROM Table: END *** 1 AT32F435 M4 RAM Start: 0x20000000 length = 0x10000 RAM Start: 0x20010000 length = 0x50000 Flash Start: 0x08000000 length = 0x200000 blocksize 0x1000 Flash Start: 0x08200000 length = 0x1f0000 blocksize 0x1000 ```

dragonmux commented 2025年09月08日 03:40:34 +02:00

Sorry for not getting back to you sooner! Having had a check of the AT32F4 parts and how the support works - looks like there's no real way to tell the F435 and F437 apart and they work the same for all intents and purposes to BMD. Same Flash, same controller, just different names and peripherals. So this is working exactly as it should, and your part is fully supported.

Sorry for not getting back to you sooner! Having had a check of the AT32F4 parts and how the support works - looks like there's no real way to tell the F435 and F437 apart and they work the same for all intents and purposes to BMD. Same Flash, same controller, just different names and peripherals. So this is working exactly as it should, and your part is fully supported.