I use the DEVKIT-MPC5744P REV-E.
MATLAB 2020A
S32DS_Power_Win32_v2.1
MBDToolbox_MPC57xx_3.2.0_20200414.mltbx
NXP_Support_Package_MPC57xx_20200414.mltbx
It can build and download successfully,But there is no response after downloading.
@petervlna when i build and download mbdt example code such as hello world, the DEVKIT-MPC5744P REV-E is no uart output.
The problem might be caused by the errata ERR050129 and is NOT something from the MBDT toolbox.
I get a elf file from your colleague and write it once using the S32DS for PA, then write again the RAppID bootloader and try again the MBDT generated code.try disabling the Core Cold LVD for the MPC57744P.
then i solve one DEVKIT-MPC5744P REV-E ,but the other one is still no uart output.
by the way, i bought two pieces of DEVKIT-MPC5744P REV-E.
Hello,
The problem might be caused by the errata ERR050129 and is NOT something from the MBDT toolbox.
Are are you observing reset on reset line (on oscilloscope)?
As errata explain:
When the internal regulator is used the VDD_LV_CORE may be up to 50 mV lower
than nominal value when device leave the reset. Together with lower value of VDD_LV_CORE the Cold Low voltage detector (LVD) can be triggered and generates Destructive reset.
when i build and download mbdt example code such as hello world, the DEVKIT-MPC5744P REV-E is no uart output.
I personally dont think this is errata related, as the Hello world is not running any high power consumption tasks (like CRC test for example).
Are you able to debug the device with JTAG debugger?
Best regards,
Peter
PS: If you are looking for direct support, you can always use NXP web tickets on our web site.
I have no JTAG debug, Is there any help file and link to share about JTAG debug
Hello,
Sure, simply connect you JTAG debugger (it must support MPC5744P device) to the J2 ONCE connector.
For example PEMicro, Lauterbach, PLS, GHS, iSystem, etc...
Best regards,
Peter
really poor experience,poor product,poor service。
Hello,
What I should imagine under "there is no response after downloading." ?
Is mirco without power? In reset? Is SW stuck? HW out of spec range?
Please elaborate the issue closely,
best regards,
Peter