there is nothing from t1040D4RDB's serial port output，why？

[ysli]

At the last normal time, I burned the device tree ，kernel ，and ramdisk img. The system prompted that the burned device tree file was incorrect and needed to be rewritten. After restarting, there was no output information on minicom or other serial debugging software, including u-boot information and some basic board letters before uboot. There's no interest left. What's the situation? The burning step is to follow the official documents. The burned documents are also the SDK packages downloaded from the official files.

在我最后一次正常的时候 烧录了 设备树 内核 跟文件系统，系统提示烧录的设备树文件有误，需要重新烧写，然后重启之后在minicom或是其他串口调试软件上就没有了任何输出信息，包括u-boot,以及uboot之前输出的一些板子基本信息都没有了，请问是什么情况？烧录步骤是按照官方所给的文档，烧录的文件也是官方上面下载的sdk包

[ufedor]

Where/how you obtained the images?

Please provide the images programming log.

To recover the board please download "QorIQ Linux SDK v2.0 PPC64E5500 IMAGE.iso" containing pre-built images using the following link:

Linux® SDK for QorIQ® Processors | NXP 

There are two options:

1) create bootable SD card, switch RCW source to SD card, boot U-Boot, download complete NOR Flash image using TFTP and program it by means of U-Boot.

SD card preparation in Linux:
   sudo dd if=u-boot-sdcard-2016.01+fslgit-r0.bin of=/dev/sdb bs=512 seek=8

   sudo dd if=fsl_fman_ucode_t1040_r1.1_106_4_18.bin of=/dev/sdb bs=512 seek=2080

Use the below u-boot commands to flash the image NOR flash Recovery image into NOR flash:
   => tftp 1000000 <NOR Flash Recovery image>
   => protect off all
   => erase all
   => cp.b 1000000 e8000000 $filesize

2) set RCW source to hard-coded option and use CodeWarrior to program the "QorIQ_SDK_V2.0_T1040D4RDB-64B_20160527_NOR_Flash.bin".