Run As -> Launch Hardware (Single Application Debug (GDB))  Error:
Error while launching program:
Memory write error at 0x100000. MMU section translation fault

The reason is that the JP4 interface is mistakenly connected to SD, but it can be connected to JTAG and the Program Device can be successfully connected.

Read More:

• Memory write error at 0x100000. MMU section translation fault [How to Solve]
• [Solved] ZYNQ download program error: Memory write error at 0x100000. APB
• VITIS Error: memory wirte error at 0x0 [How to Solve]
• [Solved] Linux Install Xilinx_SDK but Failed to Login Error: Authentication error: Xilinx
• [Solved] MDK Compile Error: error:No section matches selector – no section to be FIRST/LAST
• [Solved] Message from debugger: debug-server is x86_64 binary running in translation, attached failed.
• [Solved] ZYNQ Programs Error: memory write error at 0x100000.APB AP transaction error,DAP status f0000021
• [Solved] docker Commands Execute Error: Segmentation fault
• Vitis-AI Generate a Quantitative Model: NotImplementedError
• Node Memory Overflow: FATAL ERROR: Reached heap limit Allocation failed – JavaScript heap out of memory
• How to Fix Error Launching Installer WIN10
• Error while Launching activity [How to Solve]
• [Solved] RuntimeError: CUDA error: out of memory
• [Solved] Android Studio Error: error while launching activity
• How to Solve “parcel segmentation fault” Error in Linux
• Android 10 SurfaceView Crash: signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x4
• [Solved] paddle:FatalError: `Segmentation fault` is detected by the operating system.
• [Solved] Could not identify launch activity: Default Activity not found Error while Launching activity
• [Solved] C++ reason ncnn model error: Segmentation fault (core dumped)
• [Solved] Vscode debug error launch: Program “path” does not exist