Are there debug pins in Matek H743 Slim V3?

Hardware Planes
1

Hello,

I am trying to debug a Matek H743 Slim V3 but I can not find anywhere the debug pins (SWDIO, SWCLK). Anyone knows if its possible to debug this board with a debugger somehow?

2

By the way, is it even possible to build the code with --debug --asserts for MatekH743?? I always get this error

[1154/1159] Linking build/MatekH743-bdshot/bin/arduplane
/usr/lib/gcc/arm-none-eabi/10.3.1/../../../arm-none-eabi/bin/ld:common.ld:202 cannot move location counter backwards (from 00000000081c0460 to 00000000081c0000)
collect2: error: ld returned 1 exit status

Waf: Leaving directory `/home/user/ardupilot-20240202/build/MatekH743-bdshot'
Build failed
 -> task in 'bin/arduplane' failed (exit status 1):
        {task 140251349950512: cxxprogram AP_Arming.cpp.51.o,AP_ExternalControl_Plane.cpp.51.o,ArduPlane.cpp.51.o,Attitude.cpp.51.o,GCS_Mavlink.cpp.51.o,GCS_Plane.cpp.51.o,Log.cpp.51.o,Parameters.cpp.51.o,Plane.cpp.51.o,RC_Channel.cpp.51.o,afs_plane.cpp.51.o,altitude.cpp.51.o,avoidance_adsb.cpp.51.o,commands.cpp.51.o,commands_logic.cpp.51.o,control_modes.cpp.51.o,ekf_check.cpp.51.o,events.cpp.51.o,failsafe.cpp.51.o,fence.cpp.51.o,is_flying.cpp.51.o,mode.cpp.51.o,mode_LoiterAltQLand.cpp.51.o,mode_acro.cpp.51.o,mode_auto.cpp.51.o,mode_autotune.cpp.51.o,mode_avoidADSB.cpp.51.o,mode_circle.cpp.51.o,mode_cruise.cpp.51.o,mode_fbwa.cpp.51.o,mode_fbwb.cpp.51.o,mode_guided.cpp.51.o,mode_loiter.cpp.51.o,mode_manual.cpp.51.o,mode_qacro.cpp.51.o,mode_qautotune.cpp.51.o,mode_qhover.cpp.51.o,mode_qland.cpp.51.o,mode_qloiter.cpp.51.o,mode_qrtl.cpp.51.o,mode_qstabilize.cpp.51.o,mode_rtl.cpp.51.o,mode_stabilize.cpp.51.o,mode_takeoff.cpp.51.o,mode_thermal.cpp.51.o,mode_training.cpp.51.o,motor_test.cpp.51.o,navigation.cpp.51.o,parachute.cpp.51.o,qautotune.cpp.51.o,quadplane.cpp.51.o,radio.cpp.51.o,reverse_thrust.cpp.51.o,sensors.cpp.51.o,servos.cpp.51.o,soaring.cpp.51.o,system.cpp.51.o,tailsitter.cpp.51.o,takeoff.cpp.51.o,tiltrotor.cpp.51.o,tuning.cpp.51.o -> arduplane}
 (run with -v to display more information)

I tried ./waf clean, ./waf distclean and even rm -rf build. The strange thing is that for Pixhawk4-bshot the build succeeds. Which got me thinking, perhaps not finding swd pins means that the project can not be configured for debugging?