Dear NXP,
I connected the board with the attached circuit diagram to the i.MX8M plus board and performed a Serial Download, but as shown in the captured image, only the screen appears and the process does not proceed further.
I would like to inquire about how to resolve this.
Thank you.
Best Regards,
Inho Jeon
Dear yipingwang,
The NXP EVK (8MPLUS-BB) works fine, but the board with the circuit I designed (the attached circuit diagram) operates for a while as shown in the screenshot and then stops. Please review the attached circuit diagram to ensure it is properly designed.
Thank you.
Best Regards,
Inho Jeon
Please download the latest UUU from https://github.com/nxp-imx/mfgtools/releases
Then use the following command to program images.
unzstd
uuu -b emmc_all
If it still fails, please try the following command.
uuu.exe -b emmc imx-boot-imx8mpevk-sd.bin-flash_evk
The schematic looks same as the NXP EVK base board. The only difference is JTAG_MOD was pulled high. Please remove R216 to have a try.
Dear yipigwang,
The OS image upload still fails even after removing R216.
Please review the circuit diagram again.
Thank you.
Would you please execute the following commands and capture the UUU log to me again?
unzstd
uuu -b emmc_all
Attached a capture image file.
On your Linux host PC, please execute the following commands first.
$ unzstd imx-image-core- imx8mpevk*.rootfs.wic.zst
Then execute the following UUU command.
uuu -b emmc_all imx-boot-imx8mpevk-sd.bin-flash_evk imx-image-core- imx8mpevk*.rootfs.wic
I have several questions on this issue as shown below. Please help to clarify them.
- Did the same CPU board work well on the NXP base board, but failed on the custom one?
- Could the same CPU board pass DDR stress test with the custom base board?
- Is there any log printed from the debug console during the Serial download process?
Here is the answer:
- Did the same CPU board work well on the NXP base board, but failed on the custom one? => YES.
- Could the same CPU board pass DDR stress test with the custom base board? => YES.
- Is there any log printed from the debug console during the Serial download process? => No
It did not work even after applying the method you suggested.
Please suggest another method.
Thank you.
Since SD2 IF is under NVCC_SD2 power domain, R129 - 134 and R137 should be connected to NVCC_SD2 instead of VSD_3V3. Please just remove all these resistors.
It seems that the uboot could be loaded to DRAM successfully, but it did not run at all. Please check how J13 was connected to J18 and check if UART2 IF had been connected well as debug console for A53.
Even after removing all the resistors marked in yellow (R129~134 and R137) on the SD circuit diagram, it still does not work.
Additionally, no output is displayed at all when the debug console is connected.
Please review this part again.
Since the u-boot could be downloaded into DRAM by uuu, the USB connection should be fine. No other h/w would affect the u-boot to run. u-boot log is helpful to analyze the root cause. Please check if PC host could identify 4 COM ports as shown below and make sure the 3rd COM port had been used as debug console for A53 so that u-boot log could be printed correctly.
I Attached a U-boot log file.
Unknown image format!
Run fastboot ...
USB init failed: -22
u-boot=>
Seem usb has issue, please check if there is typec in your board, if haven't, please disable it. You can refer to this patch
1. dts
@@ -444,14 +445,6 @@
ports {
#address-cells = <1>;
#size-cells = <0>;
-
- port@0 {
- reg = <0>;
- - typec1_dr_sw: endpoint { - remote-endpoint = <&usb1_drd_sw>; - }
;
- };
2. xxx_evk.c
struct tcpc_port *port_ptr;
debug("%s %d\n", _func_, dev_seq(dev));
-
+#ifdef CONFIG_USB_TCPC
if (dev_seq(dev) == 0)
port_ptr = &port;
else
return USB_INIT_HOST;
-
+#else
+ return USB_INIT_DEVICE;
+#endif
3. defconfig
-CONFIG_USB_TCPC=y