After injecting the drivecode "CMD_InjectCustomDriveCode()" the next action is "CheckDriveState(true)"... while checking the drive state, "dwIntVec" is equal to 0xDDDDDDDD thats where it hangs... you're crashing the drive, DDDD is dummy data returned on timeout. in CMD...

We were having an issue where once the flashloader has been transferred into the MN102 memory, the program would check a specific part of the memory and it would not return properly.

where exactly did it hang?