<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: iMX6DL has problem when using mfgtools in i.MX Processors</title>
    <link>https://community.nxp.com/t5/i-MX-Processors/iMX6DL-has-problem-when-using-mfgtools/m-p/734536#M114337</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Liu&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;could you clarify meaning:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- " after I updated the parameters to the uboot DCD header, it still can't work."&lt;/P&gt;&lt;P&gt;- 'My colleague helped to test uploading to DDR using a software named "imx_usb_loader-master",&lt;/P&gt;&lt;P&gt;we found the data verification was failed. "&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;any logs, detailed description of steps.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best regards&lt;BR /&gt;igor&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 12 Feb 2018 05:25:08 GMT</pubDate>
    <dc:creator>igorpadykov</dc:creator>
    <dc:date>2018-02-12T05:25:08Z</dc:date>
    <item>
      <title>iMX6DL has problem when using mfgtools</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/iMX6DL-has-problem-when-using-mfgtools/m-p/734532#M114333</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi community&lt;/P&gt;&lt;P&gt;I developed a board with the reference of&amp;nbsp;SPF-27417_C5(Board:&amp;nbsp;MCIMX6DL-SDP), It seems everything is OK, except the Serial download mode &amp;nbsp;with mfgtools(Using L4.9.11_1.0.0.0-ga_mfg-tools). It always stopped at "Jumping to OS image". &amp;nbsp;And I can't get anything from serial port. It looks like the uboot is not running.&lt;/P&gt;&lt;P&gt;By the way, I swapped the LDM and UDM of two DDR3 chips(D16-D31, D48-D63), but I can run the uboot and Linux from SD card, and also can copy the image to eMMC from SD card, and run them. maybe this mistake is not the reason why mfg_tools can't download imges.&lt;/P&gt;&lt;P&gt;Can anybody tell me how shall I do to get the mfg_tools work？&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks a lot.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Here is the log from mfg_tools:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;DLL version: 2.7.0&lt;BR /&gt;Friday, February 09, 2018 14:51:48 Start new logging&lt;BR /&gt;ModuleID[2] LevelID[10]: CMyExceptionHandler thread is running&lt;BR /&gt;ModuleID[2] LevelID[1]: new MxHidDeviceClass&lt;BR /&gt;ModuleID[2] LevelID[1]: new MxHidDeviceClass&lt;BR /&gt;ModuleID[2] LevelID[1]: new MxHidDeviceClass&lt;BR /&gt;ModuleID[2] LevelID[1]: new MxHidDeviceClass&lt;BR /&gt;ModuleID[2] LevelID[1]: new MxHidDeviceClass&lt;BR /&gt;ModuleID[2] LevelID[1]: new MxHidDeviceClass&lt;BR /&gt;ModuleID[2] LevelID[1]: new MxHidDeviceClass&lt;BR /&gt;ModuleID[2] LevelID[1]: new MxHidDeviceClass&lt;BR /&gt;ModuleID[2] LevelID[1]: new MxHidDeviceClass&lt;BR /&gt;ModuleID[2] LevelID[10]: Device Manager thread is running&lt;BR /&gt;ModuleID[2] LevelID[1]: Can't set m_hStopEvent before it initialized or it already stop&lt;/P&gt;&lt;P&gt;ModuleID[2] LevelID[10]: DeviceManager::DevChangeWnd::OnDeviceChange() - DEVICE_ARRIVAL_EVT(\\?\USB#VID_15A2&amp;amp;PID_0061#6&amp;amp;35c31b9d&amp;amp;0&amp;amp;3#{a5dcbf10-6530-11d2-901f-00c04fb951ed})&lt;BR /&gt;ModuleID[2] LevelID[10]: DeviceManager::DevChangeWnd::OnDeviceChange() - end&lt;BR /&gt;ModuleID[2] LevelID[10]: DeviceManager::OnMsgDeviceEvent() - DEVICE_ARRIVAL_EVT(\\?\USB#VID_15A2&amp;amp;PID_0061#6&amp;amp;35c31b9d&amp;amp;0&amp;amp;3#{a5dcbf10-6530-11d2-901f-00c04fb951ed})&lt;BR /&gt;ModuleID[2] LevelID[10]: DeviceClass::FindDeviceByUsbPath--DeviceListType_Current, _devices.size: 0&lt;BR /&gt;ModuleID[2] LevelID[1]: DeviceClass::FindDeviceByUsbPath() - DeviceListType_New--index: 0&lt;BR /&gt;ModuleID[2] LevelID[1]: DeviceClass::FindDeviceByUsbPath() - DeviceListType_New--devPath: \\?\hid#vid_046d&amp;amp;pid_c05a#7&amp;amp;2ca4ada0&amp;amp;0&amp;amp;0000#{4d1e55b2-f16f-11cf-88cb-001111000030}&lt;BR /&gt;ModuleID[2] LevelID[1]: DeviceClass::FindDeviceByUsbPath() - DeviceListType_New--index: 1&lt;BR /&gt;ModuleID[2] LevelID[1]: DeviceClass::FindDeviceByUsbPath() - DeviceListType_New--devPath: \\?\hid#vid_15a2&amp;amp;pid_0061#7&amp;amp;351c8d35&amp;amp;0&amp;amp;0000#{4d1e55b2-f16f-11cf-88cb-001111000030}&lt;BR /&gt;ModuleID[2] LevelID[10]: new MxHidDevice[00B5D050]&lt;BR /&gt;ModuleID[2] LevelID[10]: DeviceClass::FindDeviceByUsbPath--DeviceListType_New, devInstPathToFind: USB\VID_15A2&amp;amp;PID_0061\6&amp;amp;35C31B9D&amp;amp;0&amp;amp;3, _deviceInstanceID: USB\VID_15A2&amp;amp;PID_0061\6&amp;amp;35C31B9D&amp;amp;0&amp;amp;3&lt;BR /&gt;ModuleID[2] LevelID[10]: DeviceClass::FindDeviceByUsbPath--DeviceListType_New, Find the device, Port: 3&lt;BR /&gt;ModuleID[2] LevelID[10]: DeviceClass::AddUsbDevice() successful USB#VID_15A2&amp;amp;PID_0061#6&amp;amp;35C31B9D&amp;amp;0&amp;amp;3#{A5DCBF10-6530-11D2-901F-00C04FB951ED} add to current list, retrycount: 0&lt;BR /&gt;ModuleID[2] LevelID[10]: DeviceManager::OnMsgDeviceEvent() - DEVICE_ARRIVAL_EVT,[MxHidDeviceClass] vid_15a2&amp;amp;pid_0061, Hub:4-Port:3&lt;BR /&gt;ModuleID[2] LevelID[10]: DeviceManager::OnMsgDeviceEvent() - DEVICE_ARRIVAL_EVT, Notify&lt;BR /&gt;ModuleID[2] LevelID[10]: CmdOpreation[0]--OnDeviceChangeNotify, Volume Arrive/Remove or Device Arrive/Remove&lt;BR /&gt;ModuleID[2] LevelID[10]: CmdOpreation[0]--OnDeviceChangeNotify, m_p_usb_port is not NULL, so only refresh&lt;BR /&gt;ModuleID[2] LevelID[10]: CmdOpreation[0]--OnDeviceChangeNotify, Volume/Device Arrive&lt;BR /&gt;ModuleID[2] LevelID[1]: CmdOpreation[0]--set m_hDeviceArriveEvent.&lt;BR /&gt;ModuleID[2] LevelID[10]: CmdOpreation[0]--WaitforEvents device arrive1&lt;BR /&gt;ModuleID[2] LevelID[10]: CmdOperation[0] device chagned and reset to state 0&lt;BR /&gt;ModuleID[2] LevelID[10]: CmdOperation[0], skip current command, so SetEvent(hDevCanDeleteEvent)&lt;BR /&gt;ModuleID[2] LevelID[10]: ExecuteCommand--Boot[WndIndex:0], File is G:\Development board\MFGTools\L4.9.11_1.0.0-ga_mfg-tools\mfgtools-without-rootfs\mfgtools\Profiles\Linux\OS Firmware\firmware\u-boot-imx6dlsabresd_sd.imx&lt;BR /&gt;ModuleID[2] LevelID[10]: CmdOperation[0], skip current command, so SetEvent(hDevCanDeleteEvent)&lt;BR /&gt;ModuleID[2] LevelID[10]: CmdOperation[0], skip current command, so SetEvent(hDevCanDeleteEvent)&lt;BR /&gt;ModuleID[2] LevelID[10]: CmdOperation[0], skip current command, so SetEvent(hDevCanDeleteEvent)&lt;BR /&gt;ModuleID[2] LevelID[10]: CmdOperation[0], skip current command, so SetEvent(hDevCanDeleteEvent)&lt;BR /&gt;ModuleID[2] LevelID[10]: CmdOperation[0], skip current command, so SetEvent(hDevCanDeleteEvent)&lt;BR /&gt;ModuleID[2] LevelID[10]: CmdOperation[0], skip current command, so SetEvent(hDevCanDeleteEvent)&lt;BR /&gt;ModuleID[2] LevelID[10]: CmdOperation[0], skip current command, so SetEvent(hDevCanDeleteEvent)&lt;BR /&gt;ModuleID[2] LevelID[10]: ExecuteCommand--Load[WndIndex:0], File is G:\Development board\MFGTools\L4.9.11_1.0.0-ga_mfg-tools\mfgtools-without-rootfs\mfgtools\Profiles\Linux\OS Firmware\firmware\zImage, address is 0x12000000&lt;BR /&gt;ModuleID[2] LevelID[10]: PortMgrDlg(0)--Command Load excute successfully, retry count: 0&lt;BR /&gt;ModuleID[2] LevelID[10]: CmdOperation[0], skip current command, so SetEvent(hDevCanDeleteEvent)&lt;BR /&gt;ModuleID[2] LevelID[10]: CmdOperation[0], skip current command, so SetEvent(hDevCanDeleteEvent)&lt;BR /&gt;ModuleID[2] LevelID[10]: ExecuteCommand--Load[WndIndex:0], File is G:\Development board\MFGTools\L4.9.11_1.0.0-ga_mfg-tools\mfgtools-without-rootfs\mfgtools\Profiles\Linux\OS Firmware\firmware\fsl-image-mfgtool-initramfs-imx_mfgtools.cpio.gz.u-boot, address is 0x12C00000&lt;BR /&gt;ModuleID[2] LevelID[10]: PortMgrDlg(0)--Command Load excute successfully, retry count: 0&lt;BR /&gt;ModuleID[2] LevelID[10]: CmdOperation[0], skip current command, so SetEvent(hDevCanDeleteEvent)&lt;BR /&gt;ModuleID[2] LevelID[10]: CmdOperation[0], skip current command, so SetEvent(hDevCanDeleteEvent)&lt;BR /&gt;ModuleID[2] LevelID[10]: CmdOperation[0], skip current command, so SetEvent(hDevCanDeleteEvent)&lt;BR /&gt;ModuleID[2] LevelID[10]: ExecuteCommand--Load[WndIndex:0], File is G:\Development board\MFGTools\L4.9.11_1.0.0-ga_mfg-tools\mfgtools-without-rootfs\mfgtools\Profiles\Linux\OS Firmware\firmware\zImage-imx6dl-sabresd.dtb, address is 0x18000000&lt;BR /&gt;ModuleID[2] LevelID[10]: PortMgrDlg(0)--Command Load excute successfully, retry count: 0&lt;BR /&gt;ModuleID[2] LevelID[10]: CmdOperation[0], skip current command, so SetEvent(hDevCanDeleteEvent)&lt;BR /&gt;ModuleID[2] LevelID[10]: CmdOperation[0], skip current command, so SetEvent(hDevCanDeleteEvent)&lt;BR /&gt;ModuleID[2] LevelID[10]: CmdOperation[0], skip current command, so SetEvent(hDevCanDeleteEvent)&lt;BR /&gt;ModuleID[2] LevelID[10]: CmdOperation[0], skip current command, so SetEvent(hDevCanDeleteEvent)&lt;BR /&gt;ModuleID[2] LevelID[10]: CmdOperation[0], skip current command, so SetEvent(hDevCanDeleteEvent)&lt;BR /&gt;ModuleID[2] LevelID[10]: CmdOperation[0], skip current command, so SetEvent(hDevCanDeleteEvent)&lt;BR /&gt;ModuleID[2] LevelID[10]: CmdOperation[0], skip current command, so SetEvent(hDevCanDeleteEvent)&lt;BR /&gt;ModuleID[2] LevelID[10]: ExecuteCommand--Jump[WndIndex:0]&lt;BR /&gt;ModuleID[2] LevelID[10]: *********MxHidDevice[00B5D050] Jump to Ramkernel successfully!**********&lt;BR /&gt;ModuleID[2] LevelID[10]: CmdOperation[0], current state command has been finished and the last command is successful, so SetEvent(hDevCanDeleteEvent)&lt;BR /&gt;ModuleID[2] LevelID[10]: DeviceManager::DevChangeWnd::OnDeviceChange() - DEVICE_REMOVAL_EVT(\\?\USB#VID_15A2&amp;amp;PID_0061#6&amp;amp;35c31b9d&amp;amp;0&amp;amp;3#{a5dcbf10-6530-11d2-901f-00c04fb951ed})&lt;BR /&gt;ModuleID[2] LevelID[10]: DeviceManager::DevChangeWnd::OnDeviceChange() - end&lt;BR /&gt;ModuleID[2] LevelID[10]: DeviceManager::OnMsgDeviceEvent() - DEVICE_REMOVAL_EVT(\\?\USB#VID_15A2&amp;amp;PID_0061#6&amp;amp;35c31b9d&amp;amp;0&amp;amp;3#{a5dcbf10-6530-11d2-901f-00c04fb951ed})&lt;BR /&gt;ModuleID[2] LevelID[10]: DeviceClass::FindDeviceByUsbPath--DeviceListType_Current, _devices.size: 1&lt;BR /&gt;ModuleID[2] LevelID[10]: DeviceClass::FindDeviceByUsbPath--DeviceListType_Current, devInstPathToFind: USB\VID_15A2&amp;amp;PID_0061\6&amp;amp;35C31B9D&amp;amp;0&amp;amp;3, _deviceInstanceID: USB\VID_15A2&amp;amp;PID_0061\6&amp;amp;35C31B9D&amp;amp;0&amp;amp;3&lt;BR /&gt;ModuleID[2] LevelID[10]: DeviceClass::FindDeviceByUsbPath--DeviceListType_Current, Find the device&lt;BR /&gt;ModuleID[2] LevelID[10]: DeviceManager::OnMsgDeviceEvent() - DEVICE_REMOVAL_EVT,[MxHidDeviceClass] vid_15a2&amp;amp;pid_0061, Hub:4-Port:3&lt;BR /&gt;ModuleID[2] LevelID[10]: DeviceManager::OnMsgDeviceEvent() - DEVICE_REMOVAL_EVT, Notify&lt;BR /&gt;ModuleID[2] LevelID[10]: CmdOpreation[0]--OnDeviceChangeNotify, Volume Arrive/Remove or Device Arrive/Remove&lt;BR /&gt;ModuleID[2] LevelID[10]: CmdOpreation[0]--OnDeviceChangeNotify, m_p_usb_port is not NULL, so only refresh&lt;BR /&gt;ModuleID[2] LevelID[10]: CmdOpreation[0]--OnDeviceChangeNotify, Volume/Device Remove&lt;BR /&gt;ModuleID[2] LevelID[1]: CmdOpreation[0]--set m_hDeviceRemoveEvent.&lt;BR /&gt;ModuleID[2] LevelID[10]: CmdOpreation[0]--WaitforEvents device remove1&lt;BR /&gt;ModuleID[2] LevelID[10]: DeviceManager::OnMsgDeviceEvent()-DEVICE_REMOVAL_EVT, hDevCanDeleteEvent has been set&lt;BR /&gt;ModuleID[2] LevelID[10]: delete MxHidDevice[00B5D050]&lt;BR /&gt;ModuleID[2] LevelID[10]: DeviceManager::DevChangeWnd::OnDeviceChange() - DEVICE_ARRIVAL_EVT(\\?\USB#VID_15A2&amp;amp;PID_0061#6&amp;amp;35c31b9d&amp;amp;0&amp;amp;3#{a5dcbf10-6530-11d2-901f-00c04fb951ed})&lt;BR /&gt;ModuleID[2] LevelID[10]: DeviceManager::DevChangeWnd::OnDeviceChange() - end&lt;BR /&gt;ModuleID[2] LevelID[10]: DeviceManager::OnMsgDeviceEvent() - DEVICE_ARRIVAL_EVT(\\?\USB#VID_15A2&amp;amp;PID_0061#6&amp;amp;35c31b9d&amp;amp;0&amp;amp;3#{a5dcbf10-6530-11d2-901f-00c04fb951ed})&lt;BR /&gt;ModuleID[2] LevelID[10]: DeviceClass::FindDeviceByUsbPath--DeviceListType_Current, _devices.size: 0&lt;BR /&gt;ModuleID[2] LevelID[1]: DeviceClass::FindDeviceByUsbPath() - DeviceListType_New--index: 0&lt;BR /&gt;ModuleID[2] LevelID[1]: DeviceClass::FindDeviceByUsbPath() - DeviceListType_New--devPath: \\?\hid#vid_046d&amp;amp;pid_c05a#7&amp;amp;2ca4ada0&amp;amp;0&amp;amp;0000#{4d1e55b2-f16f-11cf-88cb-001111000030}&lt;BR /&gt;ModuleID[2] LevelID[1]: DeviceClass::FindDeviceByUsbPath() - DeviceListType_New--index: 1&lt;BR /&gt;ModuleID[2] LevelID[1]: DeviceClass::FindDeviceByUsbPath() - DeviceListType_New--devPath: \\?\hid#vid_15a2&amp;amp;pid_0061#7&amp;amp;351c8d35&amp;amp;0&amp;amp;0000#{4d1e55b2-f16f-11cf-88cb-001111000030}&lt;BR /&gt;ModuleID[2] LevelID[10]: new MxHidDevice[00B603F0]&lt;BR /&gt;ModuleID[2] LevelID[10]: DeviceClass::FindDeviceByUsbPath--DeviceListType_New, devInstPathToFind: USB\VID_15A2&amp;amp;PID_0061\6&amp;amp;35C31B9D&amp;amp;0&amp;amp;3, _deviceInstanceID: USB\VID_15A2&amp;amp;PID_0061\6&amp;amp;35C31B9D&amp;amp;0&amp;amp;3&lt;BR /&gt;ModuleID[2] LevelID[10]: DeviceClass::FindDeviceByUsbPath--DeviceListType_New, Find the device, Port: 3&lt;BR /&gt;ModuleID[2] LevelID[10]: DeviceClass::AddUsbDevice() successful USB#VID_15A2&amp;amp;PID_0061#6&amp;amp;35C31B9D&amp;amp;0&amp;amp;3#{A5DCBF10-6530-11D2-901F-00C04FB951ED} add to current list, retrycount: 0&lt;BR /&gt;ModuleID[2] LevelID[10]: DeviceManager::OnMsgDeviceEvent() - DEVICE_ARRIVAL_EVT,[MxHidDeviceClass] vid_15a2&amp;amp;pid_0061, Hub:4-Port:3&lt;BR /&gt;ModuleID[2] LevelID[10]: DeviceManager::OnMsgDeviceEvent() - DEVICE_ARRIVAL_EVT, Notify&lt;BR /&gt;ModuleID[2] LevelID[10]: CmdOpreation[0]--OnDeviceChangeNotify, Volume Arrive/Remove or Device Arrive/Remove&lt;BR /&gt;ModuleID[2] LevelID[10]: CmdOpreation[0]--OnDeviceChangeNotify, m_p_usb_port is not NULL, so only refresh&lt;BR /&gt;ModuleID[2] LevelID[10]: CmdOpreation[0]--OnDeviceChangeNotify, Volume/Device Arrive&lt;BR /&gt;ModuleID[2] LevelID[1]: CmdOpreation[0]--set m_hDeviceArriveEvent.&lt;BR /&gt;ModuleID[2] LevelID[10]: CmdOpreation[0]--WaitforEvents device arrive1&lt;BR /&gt;ModuleID[2] LevelID[10]: CmdOperation[0] device chagned and reset to state 0&lt;BR /&gt;ModuleID[2] LevelID[10]: CmdOperation[0], skip current command, so SetEvent(hDevCanDeleteEvent)&lt;BR /&gt;ModuleID[2] LevelID[10]: ExecuteCommand--Boot[WndIndex:0], File is G:\Development board\MFGTools\L4.9.11_1.0.0-ga_mfg-tools\mfgtools-without-rootfs\mfgtools\Profiles\Linux\OS Firmware\firmware\u-boot-imx6dlsabresd_sd.imx&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 09 Feb 2018 11:35:44 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/iMX6DL-has-problem-when-using-mfgtools/m-p/734532#M114333</guid>
      <dc:creator>liujin</dc:creator>
      <dc:date>2018-02-09T11:35:44Z</dc:date>
    </item>
    <item>
      <title>Re: iMX6DL has problem when using mfgtools</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/iMX6DL-has-problem-when-using-mfgtools/m-p/734533#M114334</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Liu&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;for new board mfg tools firmware (files in ..OS Firmware/firmware folder)&lt;/P&gt;&lt;P&gt;should be replaced with new ones, generated using&lt;/P&gt;&lt;P&gt;sect.6.2 Manufacturing Tool, MFGTool attached Yocto Gude&lt;/P&gt;&lt;P&gt;after performing ddr test&lt;/P&gt;&lt;P&gt;&lt;A href="https://community.nxp.com/docs/DOC-105652"&gt;i.MX6/7 DDR Stress Test Tool V2.80&lt;/A&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;and changing uboot dcd header (file ../mx6sabresd/mx6q_4x_mt41j128.cfg)&lt;/P&gt;&lt;P&gt;with new calibration settings found from ddr test.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best regards&lt;BR /&gt;igor&lt;BR /&gt;-----------------------------------------------------------------------------------------------------------------------&lt;BR /&gt;Note: If this post answers your question, please click the Correct Answer button. Thank you!&lt;BR /&gt;-----------------------------------------------------------------------------------------------------------------------&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 09 Feb 2018 23:37:07 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/iMX6DL-has-problem-when-using-mfgtools/m-p/734533#M114334</guid>
      <dc:creator>igorpadykov</dc:creator>
      <dc:date>2018-02-09T23:37:07Z</dc:date>
    </item>
    <item>
      <title>Re: iMX6DL has problem when using mfgtools</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/iMX6DL-has-problem-when-using-mfgtools/m-p/734534#M114335</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Igor,&lt;/P&gt;&lt;P&gt;Thanks for your reply.&lt;/P&gt;&lt;P&gt;I have already done the DDR stress test and get the parameters. We can run the uboot and kernal with the DDR parameters.&lt;/P&gt;&lt;P&gt;But, after I updated the parameters to the uboot DCD header, it still can't work.&amp;nbsp;&lt;/P&gt;&lt;P&gt;To confirm the problem, I bought another board &amp;nbsp;referred to &lt;SPAN style="color: #51626f; background-color: #ffffff;"&gt;SPF-27417_C5,&lt;/SPAN&gt;&amp;nbsp;designed by &amp;nbsp;third party. My uboot can work on that board using mfgtools.&amp;nbsp;&lt;/P&gt;&lt;P&gt;My colleague helped to test uploading to DDR using a software named "imx_usb_loader-master", we found the data verification was failed.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Now I am confused. Is the problem coming from the hardware? Anything I need to test?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 10 Feb 2018 06:07:14 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/iMX6DL-has-problem-when-using-mfgtools/m-p/734534#M114335</guid>
      <dc:creator>liujin</dc:creator>
      <dc:date>2018-02-10T06:07:14Z</dc:date>
    </item>
    <item>
      <title>Re: iMX6DL has problem when using mfgtools</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/iMX6DL-has-problem-when-using-mfgtools/m-p/734535#M114336</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P style="color: #51626f; background-color: #ffffff; border: 0px; font-size: 14px;"&gt;Hi Igor,&lt;/P&gt;&lt;P style="color: #51626f; background-color: #ffffff; border: 0px; font-size: 14px;"&gt;Thanks for your reply.&lt;/P&gt;&lt;P style="color: #51626f; background-color: #ffffff; border: 0px; font-size: 14px;"&gt;I have already done the DDR stress test and get the parameters. We can run the uboot and kernal with the DDR parameters.&lt;/P&gt;&lt;P style="color: #51626f; background-color: #ffffff; border: 0px; font-size: 14px;"&gt;But, after I updated the parameters to the uboot DCD header, it still can't work.&amp;nbsp;&lt;/P&gt;&lt;P style="color: #51626f; background-color: #ffffff; border: 0px; font-size: 14px;"&gt;To confirm the problem, I bought another board &amp;nbsp;referred to &lt;SPAN style="color: #51626f; background-color: #ffffff; border: 0px; font-weight: inherit; font-size: 14px;"&gt;SPF-27417_C5,&lt;/SPAN&gt;&amp;nbsp;designed by &amp;nbsp;third party. My uboot can work on that board using mfgtools.&amp;nbsp;&lt;/P&gt;&lt;P style="color: #51626f; background-color: #ffffff; border: 0px; font-size: 14px;"&gt;My colleague helped to test uploading to DDR using a software named "imx_usb_loader-master", we found the data verification was failed.&amp;nbsp;&lt;/P&gt;&lt;P style="color: #51626f; background-color: #ffffff; border: 0px; font-size: 14px;"&gt;Now I am confused. Is the problem coming from the hardware? Anything I need to test?&lt;/P&gt;&lt;P style="color: #51626f; background-color: #ffffff; border: 0px; font-size: 14px;"&gt;And shall I need to configure the eFuses？&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 11 Feb 2018 13:21:29 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/iMX6DL-has-problem-when-using-mfgtools/m-p/734535#M114336</guid>
      <dc:creator>liujin</dc:creator>
      <dc:date>2018-02-11T13:21:29Z</dc:date>
    </item>
    <item>
      <title>Re: iMX6DL has problem when using mfgtools</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/iMX6DL-has-problem-when-using-mfgtools/m-p/734536#M114337</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Liu&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;could you clarify meaning:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- " after I updated the parameters to the uboot DCD header, it still can't work."&lt;/P&gt;&lt;P&gt;- 'My colleague helped to test uploading to DDR using a software named "imx_usb_loader-master",&lt;/P&gt;&lt;P&gt;we found the data verification was failed. "&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;any logs, detailed description of steps.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best regards&lt;BR /&gt;igor&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 12 Feb 2018 05:25:08 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/iMX6DL-has-problem-when-using-mfgtools/m-p/734536#M114337</guid>
      <dc:creator>igorpadykov</dc:creator>
      <dc:date>2018-02-12T05:25:08Z</dc:date>
    </item>
  </channel>
</rss>

