Has a definitive solution to this issue been found? I bought an mbed about a month ago, it worked fine and I was able to download some basic blinky programs to it for testing, I know it worked because I tried several demo programs, but I was busy at that time and put the mbed away. Yesterday I took it out of the box again but this time I'm completely stuck.
I can only get Windows to recognize the mbed if I hold down the reset button and plug in. If I format it and the flash memory is blank, Windows sees it fine, I can see MBED.HTM and can drag and drop files, but once I reset or let go the reset button, the program starts to run, and the mbed drive disappears. If I plug the mbed in when there's a program in memory, the program starts to execute, but Windows either does absolutely nothing, or gives me a USB device error 43.
It's not the USB cable as I've tried every single USB cable I have, and I have a LOT. The mbed itself is fine since it works on my Windows server box and my home Macbook (using any cable, I tested). It doesn't work on my Thinkpad X61, and it doesn't work on my colleague's Thinkpad T61. Both notebooks are Windows 7 Pro SP1. Could it a be notebook USB thing or some software conflict? Both Thinkpads are work computers and have a lot of applications installed. (I'm a Windows sysadmin and my colleague is tech support.) The server is a test server and only has Windows and SQL 2008 R2 installed, and the Macbook is my home computer and runs Windows 7 Ultimate SP1 and only has basic apps.
I've tried uninstalling the mbed mass storage driver and all USB related programs and drivers. Tried plugging in the mbed when logged in as the administrator user. Tried changing autoplay/autorun options. Also already tried everything the deadmbed page suggested.
Technically my mbed still works, as I can hold down the reset button, and I can drag and drop files to it with the button held down. Will try installing a new copy of Windows on a blank drive later on and see if it's Windows or my notebook...
Sorry for the long (and first!) post, but I've been trying different things for more than 15 hours and I really want to get things going.
Has a definitive solution to this issue been found? I bought an mbed about a month ago, it worked fine and I was able to download some basic blinky programs to it for testing, I know it worked because I tried several demo programs, but I was busy at that time and put the mbed away. Yesterday I took it out of the box again but this time I'm completely stuck.
I can only get Windows to recognize the mbed if I hold down the reset button and plug in. If I format it and the flash memory is blank, Windows sees it fine, I can see MBED.HTM and can drag and drop files, but once I reset or let go the reset button, the program starts to run, and the mbed drive disappears. If I plug the mbed in when there's a program in memory, the program starts to execute, but Windows either does absolutely nothing, or gives me a USB device error 43.
It's not the USB cable as I've tried every single USB cable I have, and I have a LOT. The mbed itself is fine since it works on my Windows server box and my home Macbook (using any cable, I tested). It doesn't work on my Thinkpad X61, and it doesn't work on my colleague's Thinkpad T61. Both notebooks are Windows 7 Pro SP1. Could it a be notebook USB thing or some software conflict? Both Thinkpads are work computers and have a lot of applications installed. (I'm a Windows sysadmin and my colleague is tech support.) The server is a test server and only has Windows and SQL 2008 R2 installed, and the Macbook is my home computer and runs Windows 7 Ultimate SP1 and only has basic apps.
I've tried uninstalling the mbed mass storage driver and all USB related programs and drivers. Tried plugging in the mbed when logged in as the administrator user. Tried changing autoplay/autorun options. Also already tried everything the deadmbed page suggested.
Technically my mbed still works, as I can hold down the reset button, and I can drag and drop files to it with the button held down. Will try installing a new copy of Windows on a blank drive later on and see if it's Windows or my notebook...
Sorry for the long (and first!) post, but I've been trying different things for more than 15 hours and I really want to get things going.