Hi guys , When both usb cables are plugged in to the Edison board , I see that MERRIFIELD driver pops up and down in the device manager, and am unable to figure out why. Also the drive of Edison doesn't appear in My Computer. Any help would be appreciated!!...
I had simular problem my self.
Is the Edison installed the right way?
Sometimes Arduino drivers make the edison not visible.
Have you tryed using a new computer with nothing else then Intel Edison drivers and XDK software installed?
https://software.intel.com/iot/hardware/edison/downloads IoT - Intel® Edison Board Download | Intel® Software
Re-install Driver software
.....Perform this if you need to re-install the Edison chip......
Re-install Flash Tool Lite in Advanced mode and select all installations.
Download the 3.0 Yocto files and unzip it.
After you have installed all above and unziped the Yocto files open the Flash Tool Lite and select the Yocto file directory and find the flash file. Follow the instructions on Flash tool lite to install.
This will only work if the drivers are installed the right way and the Edison does not have any power then you connect the usb to it.
If the Edison gets installed the right way you are now ready to perform new setup of the edison.
https://software.intel.com/en-us/get-started-edison-windows-step1 IoT - Step 1: Assemble Board | Intel® Software
In order to avoid seeing the Edison as a Merrifield device so that the OTG is recognized as Edison you need to run the flashall script. You can see instructions to run the flashall here /docs/DOC-25154 https://communities.intel.com/docs/DOC-25154 .
After you see the Edison properly recognized you can install the XDK following https://software.intel.com/en-us/getting-started-with-the-intel-xdk-iot-edition https://software.intel.com/en-us/getting-started-with-the-intel-xdk-iot-edition
Take a look at this thread /thread/60643 https://communities.intel.com/thread/60643 , it describes the same issue you have. There are several suggestions like using a different dfu_util.exe, using different cables and disabling driver signatures.
Try these approaches and let us know your results for each of these methods.