DS-5 and DStream  set memory freescale i.MX6  error: ERROR(TAD11-NAL18)

The PC with 0xC....... makes me think that the target may have booted a Linux kernel which turned on the MMU (and not mapped any memory to 0x020E05A8).  Try looking at the SCTLR in CP15 to see if the M bit is on.  The reset command may be having no effect.  You could fake the reset yourself by clearing the M bit, the caching btis, setting the CPSR, etc. but that wouldn't reset the rest of the chip (memory controller, etc.).  Can you change the bootcmd variable in U-Boot to not boot the kernel?

The PC with 0xC....... makes me think that the target may have booted a Linux kernel which turned on the MMU (and not mapped any memory to 0x020E05A8).  Try looking at the SCTLR in CP15 to see if the M bit is on.  The reset command may be having no effect.  You could fake the reset yourself by clearing the M bit, the caching btis, setting the CPSR, etc. but that wouldn't reset the rest of the chip (memory controller, etc.).  Can you change the bootcmd variable in U-Boot to not boot the kernel?

1】The PC with 0xC....... is: The SoC will boot from the SD Card[contain the u-boot and linux kernel] before I click the debug in DS-5, to avoid it, I remove the SD card this time, the PC changed to 0x0000108C, and it seems success to write memory for some address(Line6~Line14), but failed after that:

Stopping running target Freescale - i.MX6 Solo (Generic) on USB:001870 on connection
Connected to running target Freescale - i.MX6 Solo (Generic) on USB:001870
Execution stopped at: S:0x0000108C
S:0x0000108C   BX       lr
source /v "/home/hexiongjun/SmartAuto/uboot-imx/cmimx6q.ds"
+mem set 0x020e05a8  32  0x00000028
+mem set 0x020e05b0  32  0x00000028
+mem set 0x020e0524  32  0x00000028
+mem set 0x020e051c  32  0x00000028
+mem set 0x020e0518  32  0x00000028
+mem set 0x020e050c  32  0x00000028
+mem set 0x020e05b8  32  0x00000028
+mem set 0x020e05c0  32  0x00000028
+mem set 0x020e05ac  32  0x00000028
+mem set 0x020e05b4  32  0x00000028
ERROR(TAD11-NAL20): 
# in /home/hexiongjun/SmartAuto/uboot-imx/cmimx6q.ds:12 while executing: mem set 0x020e05b4  32  0x00000028
! Failed to write 4 bytes to address S:0x020E05B4
! Verify error on memory operation.
ERROR(CMD656): The script /home/hexiongjun/SmartAuto/uboot-imx/cmimx6q.ds failed to complete due to an error during execution of the script
loadfile "/home/hexiongjun/SmartAuto/uboot-imx/u-boot"
ERROR(CMD16-TAD11-NAL22): 
! Failed to load "u-boot"
! Failed to write 179,688 bytes to address S:0x10000000
! General error on memory or register access.
Target Message: Could not determine target state

2】scatter file：

I think the u-boot ELF file should contain the entry point, so it's no necessary to add a scatter file.

1】 If your mem sets are to peripheral registers (e.g. memory controller) then they may not read back the same value that was written which is causing "Verify error on memory operation."

You can use a command like memory 0x020e0500 +0x100 nocache,noverify,nobp,nohbp (for some apropriate base address and size) to tell the debugger where the peripherals are.  See also ARM DS-5 Debugger Command Reference: memory

I suspect that the further loadfile error is probably a "cascade" error because the peripherals aren't all setup.

2】The scatter file (or linker script) is used to tell the linker how to build the image and what address to use for it.  It affects the image but doesn't directly tell the debugger anything.

I have tried the nocache,noverify,nobp,nohbp; and unlucky, it shows the same hint:

1. ERROR(TAD11-NAL20):  
2. # in /home/hexiongjun/SmartAuto/uboot-imx/cmimx6q.ds:12 while executing: mem set 0x020e05b4  32  0x00000028 
3. ! Failed to write 4 bytes to address S:0x020E05B4 
4. ! Verify error on memory operation. 

I give up for the moment.  Thank you.

I'm sorry to hear that.  It would be interesting (to me, anyway) to see the output of info memory immediately before the command that fails.