Jump to content
  • 0

Cerebot MX7 board failures?


jfrenzel

Question

We have a lab full of Cerebot MX7 boards, some older than others, and this week two of them went belly up, with the programmer no longer able to read the Device ID. Both MPLAB IDE and IPE can connect to the debugger, but not the chip itself. So no programming and no erasing. (see attached screenshot)

First guess of course is ESD, but allegedly one board failed when the student was not connecting leads - simply downloading and running code.

This makes me wonder if there is something in the programming circuitry that may have failed, rather than the PIC32 itself.

Does anyone have any suggestions on an *easy* way to verify whether the appropriate signals are being generated to place the PIC32 into programming mode (or whether there are known failure mechanisms for these boards)?

Sadly, the PIC32 is backordered 52 weeks, so even if I wanted to try and replace the chip that isn't an option.

Thank you,

A (currently) Rather Unhappy User1594382595_microchipdeviceid.thumb.jpg.d80ee3622c46bd549c30b95458d17344.jpg

 

Link to comment
Share on other sites

0 answers to this question

Recommended Posts

There have been no answers to this question yet

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...