Hi,
We have MIMXRT1051CVL5B on our design.
the MCU SNVS and 3.3V rails are in the required range, the clocks are ok, but we can't see a device connected (on the SW or device manager) while we connect the USB host to J16 connector or the NXP debugger to J3 connector.
I have attached our design. Can you please review and let us know what can be the problem?
已解决! 转到解答。
Hi @sapirbuz ,
You mentioned the MCU doesn't wake up, do you mean you use the low power mode, or just your customer board can't work? In fact not the low power issues?
If it is the low power wake up issue, do you also test it on the NXP MIMXRT1050-EVKB, whether that works ok or not? Just make sure your software have no issues.
You mentioned: but we can't see a device connected (on the SW or device manager)
Which device? please give me more information about this point, I am a little lost about it.
Best Regards,
Kerry
Hi,
Our board can't work. We connect the USB host or the SWD NXP debugger and nothing happens.
When we connect our board with the NXP to the host, the NXP MCU Boot Utility doesn't recognize the flash, but when we connect the EVKB with the same flash, it is recognized automatically, and we see device connected on the device manager.
Hi @sapirbuz ,
Your board enter the SDP mode failed. Do you set your board in the serial download mode?
Can you use the debugger enter the debug mode in RAM?
You can check the SRC status register at first.
Best Regards,
Kerry
Do you set your board in the serial download mode?- Yes
Can you use the debugger enter the debug mode in RAM? no, the debugger isn't recognized as well as the USB.
We noticed that the 3.3V-SNVS and the 3.3V to the other NXP pins raised together.
the 3.3V to the other NXP pins is high before the PMIC_ON_REQ pin is high
Hi @sapirbuz ,
Please check two points:
1. POR sequence
DCDC_PSWITCH is delayed more than 1ms to switch the internal DCDC on, this is the must.
2. Do you have JLINK, you can use the JLINK to check with SWD, whether you can find the M7 core or not?
If the M7 core is not detected, it means your hardware have issues.
Best Regards,
Kerry
Hi @sapirbuz
1. DCDC_PSWITCH is delayed 8ms to switch the internal DCDC on.
=>Kerry: it's enough!
2. We have SWD debugger, should it work the same as JLINK?
=>Kerry: SWD is the interface, the JLINK connect interface is SWD, so you can try to use the JLINK connect to the RT board SWD interface, then use the JLINK commander to test it, something like this:
JLINK commander can find in the JLINK driver.
Hi,
Thank you!
I found the problem in the design: the VDD_USB_CAP is shortened to VDD_SOC_IN.
Can I know if anything may be damaged if the VDD_USB_CAP pin will be float (and not connected to capacitor)
Hi @sapirbuz ,
Thanks for your information.
1. JLINK connection result
That is not correct, you need to check the SWD connection between your board the JLINK, seems connection have issues.
If you still have issues, you can share me your connection photo!
2. the USB issues
I don't think your chip is damaged, please remove the VDD_SOC_IN from VDD_USB_CAP.
VDD_USB_CAP should like this:
After the modification, can you find the USB or not in the serial download mode?
Any updated information, kindly let me know.
Best Regards,
kerry
Hi @sapirbuz ,
For testing, I think, you need to remove the VDD_SOC_IN from VDD_USB_CAP at first, then try it if you can't add the capacitor. the capacitor is a must if you design the product, but for the simple testing, you can leave it as float at first.
Wish it helps you!
Best Regards,
Kerry
Hi,
We succeed in connecting the debugger using the MCUXpresso IDE.
The USB is still not recognized.
What can we do to debug the problem using the MCUXpresso IDE?
Should we program something before the USB is recognized? or should it be recognized automatically on a "clean" MCU?
BDY, the detection failed using the Jlink commander
Hi,
When we connect our board with the NXP to the host, the NXP MCU Boot Utility doesn't recognize the flash and nothing happens.
But when we connect the EVKB with the same flash, it is recognized automaticall.