AnsweredAssumed Answered

L4.1.15_2.1.0-ga_mfg_tools not finding board?

Question asked by colinhelliwell on Jan 23, 2018
Latest reply on Jan 27, 2018 by colinhelliwell

I'm trying to migrate from mfgtool2 on Windows to the Linux version. I'm using a custom board, with an IMX6Solo CPU, and I've been using the Windows version successfully, so I know my images etc are fine. 

I've used the cfg.ini and ucl2.xml files from Windows to set up the Linux tool, and I'm fairly sure all is correct with these - indeed an 'strace' on mfgtoolcli shows them being opened successfully.

 

The board is detected on USB - lsusb shows:

Bus 001 Device 007: ID 15a2:0061 Freescale Semiconductor, Inc.

with dmesg containing:

[1195478.199348] usb 1-2: new high-speed USB device number 7 using xhci_hcd
[1195478.328352] usb 1-2: New USB device found, idVendor=15a2, idProduct=0061
[1195478.328358] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[1195478.328362] usb 1-2: Product: SE Blank RIGEL
[1195478.328365] usb 1-2: Manufacturer: Freescale SemiConductor Inc
[1195478.352579] usbcore: registered new interface driver usbhid
[1195478.352583] usbhid: USB HID core driver
[1195478.358096] hid-generic 0003:15A2:0061.0001: hiddev0,hidraw0: USB HID v1.10 Device [Freescale SemiConductor Inc SE Blank RIGEL] on usb-0000:00:14.0-2/input0

 

 

The ucl2.xml file - in ./Profiles/myboard/OS Firmware-  has the LIST entry for 'LINUX-MMC', and a CFG section:

<CFG>
<STATE name="BootStrap" dev="MX6D" vid="15A2" pid="0061"/>
<STATE name="BootStrap" dev="MX6Q" vid="15A2" pid="0054"/>
<STATE name="BootStrap" dev="MX6UL" vid="15A2" pid="007D"/>
<STATE name="Updater" dev="MSC" vid="066F" pid="37FF"/>
</CFG>

 

However when I run mfgtoolcli (as sudo) - sudo ./mfgtoolcli -l "LINUX-MMC" -c "myboard" - there doesn't seem to be any comms with the board at all. The console shows:

  Your Options:
  Ready to flash.

(and it sits there like that). The log file contains:

DLL version: 2.3.4
Tue Jan 23 13:08:47 2018
Start new logging
ModuleID[2] LevelID[10]: address from XML 0x10500000

ModuleID[2] LevelID[10]: address from XML 0x10800000

ModuleID[2] LevelID[10]: address from XML 0x11180000

ModuleID[2] LevelID[10]: address from XML 0x11200000

ModuleID[2] LevelID[10]: address from XML 0x10600000

ModuleID[2] LevelID[10]: address from XML 0x10540000

ModuleID[2] LevelID[10]: address from XML 0x11100000

ModuleID[2] LevelID[10]: CMyExceptionHandler thread is running
ModuleID[2] LevelID[1]: new MxHidDeviceClass
ModuleID[2] LevelID[1]: new MxHidDeviceClass
ModuleID[2] LevelID[1]: new MxHidDeviceClass

 

Any thoughts on what's wrong, and/or how to debug further?

Thanks.

Outcomes