1
\$\begingroup\$

I designed a simple USB to UART coverter using Microchip's MCP2200 microcontroller. worked nicely for a while, but while i was trying to Update configuration using supplied config utility... the application crashed during the cofiguration was beig updated..

Now whenever i connect it to the computer, it says USB device not recognized.(malfunctioned)..

So, my question is, Is there any way to reset default settings by hardware. as it is not recognized by the computer at all.

P.S. i did not changed the VID/PID so it is not a problem of driver.

\$\endgroup\$
3
  • \$\begingroup\$ I had the same problem, turns out it's only Windows that can't recognize it anymore. Still works like a charm under Linux Mint 17. \$\endgroup\$
    – user100054
    Commented Feb 11, 2016 at 11:22
  • \$\begingroup\$ Did you fix the configuration through Linux? \$\endgroup\$
    – Passerby
    Commented Feb 11, 2016 at 11:25
  • \$\begingroup\$ Did you find out why Windows won't recognize it anymore? Driver signing problem? \$\endgroup\$
    – Ariser
    Commented Feb 11, 2016 at 12:24

1 Answer 1

Reset to default
1
\$\begingroup\$

I think you're out of luck on this one. If the configuration memory was erased and the app crashed before the new values were written, it would explain why it's no longer enumerating - the firmware doesn't read valid config data and can't recover.

(Interesting side note: the MCP2200 is a relabelled PIC18F14K50 with pre-blown firmware inside it. You may be able to salvage it for other uses - the FOSS replacement for the MCP2200 firmware doesn't appear to be ready yet.)

\$\endgroup\$
4
  • \$\begingroup\$ MCP2200 is a relabelled PIC18F14K50 That's interesting... Does that mean i can copy firmware from other MCP2200 and upload to this corrupted one? \$\endgroup\$
    – Suraj Bhawal
    Commented May 1, 2015 at 15:49
  • \$\begingroup\$ Unfortunatly it doesnt seem like you can. According to the website the code is read protected. \$\endgroup\$
    – Mathieu L.
    Commented May 1, 2015 at 18:42
  • 1
    \$\begingroup\$ Perhaps you could read the 256-byte EEPROM section and write that to the bricked device? If you can do it without touching program memory it may work... \$\endgroup\$
    – Adam Lawrence
    Commented May 1, 2015 at 20:28
  • \$\begingroup\$ @AdamLawrence never mind. i ordered more of those chips.. but i will try to copy EEPROM data from working chip to bricked one once they arrive. \$\endgroup\$
    – Suraj Bhawal
    Commented May 2, 2015 at 16:54

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.