Just wondering if anyone has come across anything like this before, I seem to have bricked an Apalis iMX6Q module permanently by loading an experimental u-boot.
I understand that my bootloader may have a problem that causes the module not to start but what is strange is that it appears some permanent damage/misconfiguration has occurred. I have tried both the freescale MfgTool2 GUI tool and the sb_loader command line tool with similar results. Both start fine in recovery mode and find the HID device, start and then fail as soon as they try to load the stock apalis bootloader into ram (see log and screen shots). If I just replace the iMX module only and both methods work fine.
What could have happened?, it almost seems like the DDR has remembered some corrupt setting… is this possible?..
Extract from MfgTool.log…
ModuleID LevelID: MxHidDevice::Read() Error reading from device 0x48f. ModuleID LevelID: Failed to read HAB type from ROM!!! ModuleID LevelID: Failed to initialize memory! ModuleID LevelID: PortMgrDlg(0)--MxHidDevice--Command Boot excute failed
Debug from sb_loader…
C:\sb_loader.v1.2>sb_loader -f u-boot.imx Found USB#VID_15A2&PID_0054#6&121F0AE7&0&4. Reg 0x20e05a8 is initialized. Reg 0x20e05b0 is initialized. Reg 0x20e0524 is initialized. . . . . . . . . . . . Reg 0x20e059c is initialized. Reg 0x20e05a0 is initialized. Reg 0x20e0750 is initialized. Failed to initialize memory! Failed to run plugin u-boot.imx to the device.*