Author Topic: ED programming fail: "Could not query PTG mode." - SOLVED!  (Read 3900 times)

Offline mmorlan62

  • Full Member
  • ***
  • Posts: 74
Hmm.

I built the ED board and encountered an error in the PICkit 3 program.  With the PICkit 3 hardware attached to the board and computer, I receive the following status messages:

  • Found 1 firmware suite. latest is version 01.38.51
  • Loaded device file with 679 devices
  • Found PICkit 3, SN: ...
  • Communications error: Could not query PTG mode.

I receive that error with or without the board power supplied from the wall wart.  The Device dropdown remains disabled and I can proceed no further.

I did a close inspection of the board and noted a solder bridge between pins 35 & 36 of the Ethernet chip.

I just bought the PICkit 3.

Thoughts?  Thanks for any help.

Michael
« Last Edit: March 29, 2012, by mmorlan62 »

Offline peteandvanessa

  • Sr. Member
  • ****
  • Posts: 492
Re: ED programming fail: "Could not query PTG mode."
« Reply #1 on: March 29, 2012, »
You are not allowed to view links. Register or Login

and here:

You are not allowed to view links. Register or Login
« Last Edit: March 29, 2012, by peteandvanessa »

sjb

  • Guest
Re: ED programming fail: "Could not query PTG mode."
« Reply #2 on: March 29, 2012, »
Is that the correct PIC device selected for the etherdongle?

Steve

Offline peteandvanessa

  • Sr. Member
  • ****
  • Posts: 492
Re: ED programming fail: "Could not query PTG mode."
« Reply #3 on: March 29, 2012, »
You are not allowed to view links. Register or Login
Is that the correct PIC device selected for the etherdongle?

Steve

I don't think it is the correct one, the correct one is PIC32MX795F512L (It's usually the last one on the drop down), but it may or may not appear until he's update the S/W for the PICKIT3
« Last Edit: March 29, 2012, by peteandvanessa »

Offline mmorlan62

  • Full Member
  • ***
  • Posts: 74
Re: ED programming fail: "Could not query PTG mode."
« Reply #4 on: March 29, 2012, »
SUCCESS!!

Mucho thankyou-o!  :-)

I followed the advice in the You are not allowed to view links. Register or Login thread about downloading a new operating system.

That fixed everything.

Thanks again,

Michael

Offline peteandvanessa

  • Sr. Member
  • ****
  • Posts: 492
Don't you love it when a plan comes together.

Glad it fixed it, now go and make your lights blink  :)

Offline mmorlan62

  • Full Member
  • ***
  • Posts: 74
On a separate note (and while I've got your attention)  :D

Is that solder bridge between pins 35 and 36 of the Ethernet chip an issue?  They are documented as grounds and don't appear to be connected to anything on the board.

M

Offline peteandvanessa

  • Sr. Member
  • ****
  • Posts: 492
You are not allowed to view links. Register or Login
On a separate note (and while I've got your attention)  :D

Is that solder bridge between pins 35 and 36 of the Ethernet chip an issue?  They are documented as grounds and don't appear to be connected to anything on the board.

M

Don't know for sure. I'll have to look at mine tonight when I get home.

Offline RJ

  • Administrator
  • Sr. Member
  • *****
  • Posts: 8519
You are not allowed to view links. Register or Login
On a separate note (and while I've got your attention)  :D

Is that solder bridge between pins 35 and 36 of the Ethernet chip an issue?  They are documented as grounds and don't appear to be connected to anything on the board.

M


No It is a trace between them and they all are like that.

No one should need to mess with the solder job on the smd chips on the second coop. If you are having issues do not assume it is a smd solder issue the chances are much much higher it is something else.

RJ
Innovation beats imitation - and it's more satisfying