Actions
Forum Thread Details
  • State Not Answered
  • Replies 3 replies
  • Subscribers 401 subscribers
  • Views 460 views
  • Users 0 members are here
Related

Arduino equilivent - Chipkit uno32 - Dead on arrival?

Former Member

Hey

I know this isnt an Arduino, but it uses a version of the Arduino IDE and is very similar

Recently I aquired a chipkit uno32, however when it arrived it had a red D printed on the chip ( http://i.imgur.com/2WNPo.jpg )

Not being deterred, I attempted to get it working through usual manners

I installed their arduino IDE ( https://github.com/chipKIT32/chipKIT32-MAX/downloads ), and attempted to install the drivers,

However it did not Automatically detect the drivers from the install, when I directed it at the location of it

In the end I chose the driver manually and would get a "Device cannot start" error from device manager

The device is broke, and i'm not doing something stupid, Right?

Parents
  • 0

    Hi,

     

    When I first powered up my UNO32, the USB port could not find the device.  However, I followed thier installation guide and found the USB COM line that the HW was attached to and that solved the problem.

     

    When you plug the UNO32 into your computer, does it recognize that you have attached new hardware?

    I found the Digitec site quite helpful and the software has worked fine for me. 

     

    Are you using Windows?

    See if you can find your hardware using the windows hardware installation wizard.

     

    Without knowing more details about your set up, I can only suggest that you re-install everything and try it again.

     

    DAB

  • 0 in reply to DAB

    Yeah I'm on Windows 7 - 64 bit

     

    When I first plugged it in, it found it but failed to automatically install the drivers, but that I thought was expected.

     

    I then went into device manager and tried to install drivers by showing it the location of the correct drivers, but it did not find them - So I then picked the correct one manually and told it to use it. Could you check what your drivers name is for me? Just so I know I didnt choose the wrong one, although i did try the three that were in the drivers folder.

     

    I'll try reinstalling it all now -

     

    And somehow amazingly uninstalling the driver and plugging it back in worked - Which is a giant surprise as I was fiddling around with the drivers quite a lot when I first got it.

    Not quite sure why it randomly it didnt work, and now does. But the red D on the chip probably made me give up faster than I would've normally.

     

    However I encountered another problem, googled it and foudn documentation on the problem.

    http://www.chipkit.cc/wiki/index.php?title=Avrdude:_verification_error;_content_mismatch

    Which may be why it had the red D, sadly i do not have the equipment to flash the bootloader myself currently. Time to RMA

    Thanks a lot for your help!

Reply
  • 0 in reply to DAB

    Yeah I'm on Windows 7 - 64 bit

     

    When I first plugged it in, it found it but failed to automatically install the drivers, but that I thought was expected.

     

    I then went into device manager and tried to install drivers by showing it the location of the correct drivers, but it did not find them - So I then picked the correct one manually and told it to use it. Could you check what your drivers name is for me? Just so I know I didnt choose the wrong one, although i did try the three that were in the drivers folder.

     

    I'll try reinstalling it all now -

     

    And somehow amazingly uninstalling the driver and plugging it back in worked - Which is a giant surprise as I was fiddling around with the drivers quite a lot when I first got it.

    Not quite sure why it randomly it didnt work, and now does. But the red D on the chip probably made me give up faster than I would've normally.

     

    However I encountered another problem, googled it and foudn documentation on the problem.

    http://www.chipkit.cc/wiki/index.php?title=Avrdude:_verification_error;_content_mismatch

    Which may be why it had the red D, sadly i do not have the equipment to flash the bootloader myself currently. Time to RMA

    Thanks a lot for your help!

Children