We have an iMX53-based platform that uses the DCD approach in U-Boot to perform device configuring both for the production and manufacturing versions of U-Boot and we have been successfully using the Freescale MFGTool (using the manufacturing version of U-Boot) to program the boards.
We have now changed to use the plugin approach to configure the device for both production and manufacturing versions of U-Boot. The production U-Boot works and the board boots correctly. However the MFGTool fails straightway when attempting to program the board using the new plugin-based U-boot approach.
Does anyone know of any issues relating to the use the MFGTool when using the iMX53 plugin approach?
Does the xml file differ between the DCD and plugin approaches - we use the same xml file for both. I've attached a copy of the xml file.
The MfgTool version is V1.6.2.055.
Thanks
Bruno
Here's the relevant error from the MfgTool log
Monday, December 04, 2017 12:52:13
1 - Panel A Start processing BT500-V4 <LIST/>.
Panel A Start <CMD/> type="boot" body="BootStrap" file="u-boot-mfg.bin" timeout="10" onError="" text=" Boot from mfg-mode U-Boot ".
1 - Panel A DoBoot() - Failed to load u-boot-mfg.bin to Recovery mode device. (err=6)
1 - Panel A Finished <CMD/> type="boot" body="BootStrap" file="u-boot-mfg.bin" timeout="10" onError="" text=" Boot from mfg-mode U-Boot " FAIL code=0x6.
Panel A: Reason is unknown,failed to run command: type="boot" body="BootStrap" file="u-boot-mfg.bin" timeout="10" onError="" text=" Boot from mfg-mode U-Boot " The handle is invalid.
2 - Panel A Finished processing BT500-V4 <LIST/> : FAIL code=6.
Panel A: Reason is unknown,Operation stopped by user. The process terminated unexpectedly.
what is the meaning of "plugin" approach?