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
• When using postman assertion, the global variables set in the tests of the pit will take effect only after the interface is executed
• [Solved] Keil5 burn STM32F chip Error: error: Flash download failed – “cortex-m4″“
• [Solved] Failed to allocate graph: MYRIAD device is not opened.
• [Solved] STM32F4 MDK5 Software Simulate Error: error 65: no ‘read‘ permission
• [Solved] docker Commands Execute Error: Segmentation fault
• [Solved] RuntimeError: CUDA error: out of memory
• [Solved] Vscode debug error launch: Program “path” does not exist
• Appium Top 10 Common Error [How to Solve]
• [Solved] Android Studio Run Error: Error while executing: am start -n
• How to Solve Android Arouter Frame Autowired Error
• [Solved] Cordova Android Compile Error: Execution failed for task ‘:packageDebug‘
• [Solved] INSTALL_FAILED_DEXOPT (DEX optimization verification failed)
• unhandled system error, NCCL version 2.7.8 [How to Solve]
• C++ Compile Error: error: invalid conversion from ‘void*‘ to ‘char*‘ [-fpermissive]
• [ERROR_BUNDLE_PATH_OR_FILE] & Error while Deploying HAP
• [Go] Solve the empty interface interface{} cannot use (type []string) as type []interface {}
• [Solved] kettle Error: GC overhead limit exceeded
• [Solved] Android Error: E/EGL_adreno: tid 3927: eglSurfaceAttrib(1334): error 0x3009 (EGL_BAD_MATCH)