Notice. New forum software under development. It's going to miss a few functions and look a bit ugly for a while, but I'm working on it full time now as the old forum was too unstable. Couple days, all good. If you notice any issues, please contact me.
Grogster Admin Group Joined: 31/12/2012 Location: New ZealandPosts: 9486
Posted: 11:09pm 20 Jul 2014
Copy link to clipboard
Print this post
I can't get MPLAB-X IPE to see the PICKit3 device at all.
When I plug in the PK3, POWER and ACTIVE leds light, STATUS stays off.
I'm trying to program a 250 with the VT100 terminal hex.
I've tried replugging the device, different ports, reboots - always the same "Connection failed." in red, when I try to talk to it.
Can anyone here offer any hints as to what I am doing wrong?
EDIT: OK, plugged it back in the 1st port I was using, and now IPE sees it there as a PICkit3, so we are making progress - it reports the PK3 firmware, and now the STATUS led is on.
Still can't talk to the PIC32 though - is now reporting "Failed to get device ID" in red. There is 3.2v on the chip where it should be, 5v USB power for the moment. One USB port powers the VT100 PCB, the other port feeds the PK3.
Also, ONLY works if I connect to the PK3 BEFORE I connect it to the VT100 terminal - I am sure I never had to do that when programming MicroMites. If I plug in the PK3 to the VT100, then IPE just refuses to talk to it again.Edited by Grogster 2014-07-22Smoke makes things work. When the smoke gets out, it stops!
Grogster Admin Group Joined: 31/12/2012 Location: New ZealandPosts: 9486
Posted: 11:26pm 20 Jul 2014
Copy link to clipboard
Print this post
OK, I just tried talking to a MicroMite, and I can establish a link fine, so it just does not want to talk to the 250 for some reason.
I am using a 10uF tant as per the schematic and PCB overlay. Are these not supposed to be about 47uF tants(10uF if ceramic) like the MicroMite chips?Smoke makes things work. When the smoke gets out, it stops!
Grogster Admin Group Joined: 31/12/2012 Location: New ZealandPosts: 9486
Posted: 11:45pm 20 Jul 2014
Copy link to clipboard
Print this post
OK, removed the BAUD jumpers, which I had installed for 38k4 by default, and then I was able to program the device - it obviously does not like certain things on it's I/O pins when programming, but now that I had the FW in there, I realised it was the old one, so tried to upgrade to 1.2 using the download and the procedure in the instructions, but when I put in a PID of 0xFA8D and click connect, the software just spits back that it can't find any device with that address.....
Instructions went fine until step 9 - as soon as I click CONNECT, it just says it ain't there to be had.
Smoke makes things work. When the smoke gets out, it stops!
BobD Guru Joined: 07/12/2011 Location: AustraliaPosts: 935
Posted: 11:59pm 20 Jul 2014
Copy link to clipboard
Print this post
Are you using a Pickit3 to load V1.2? That is not allowed. We just a big thread about that. The original goes in via a Pickit and that includes a bootloader. The updates must follow the procedure in the ZIP.
edit: Retract that, I have it wrong what you were doing. It must be the sauce I had with dinner. I can't see straight.Edited by BobD 2014-07-22
Grogster Admin Group Joined: 31/12/2012 Location: New ZealandPosts: 9486
Posted: 12:48am 21 Jul 2014
Copy link to clipboard
Print this post
NOTE TO ALL - Please see my other thread - this issue has been solved.Smoke makes things work. When the smoke gets out, it stops!
WhiteWizzard Guru Joined: 05/04/2013 Location: United KingdomPosts: 2927
Posted: 10:44am 21 Jul 2014
Copy link to clipboard
Print this post
You MUST remove Baud rate Jumper C when programming v1.0 ASCII Terminal Firmware. If not then you are grounding the PClk signal from the PicKit 3 and hence programming won't work.
Grogster Admin Group Joined: 31/12/2012 Location: New ZealandPosts: 9486
Posted: 01:30pm 21 Jul 2014
Copy link to clipboard
Print this post
Yes, that was also a mistake of mine - live and learn!
With the jumpers in place for 38k4, the PK3 would have nothing to do with the chip no matter what. Once I removed the jumpers, I WAS able to program in the 1.2 FW using PK3, but only then discovered that this was the wrong way to do it - I guess I have just got TOO used to programming MicroMite chips, where you just flash the virgin chip directly with the PK3, so just went along that road without really thinking much more about it.... Smoke makes things work. When the smoke gets out, it stops!
Justplayin Guru Joined: 31/01/2014 Location: United StatesPosts: 327
Posted: 01:57pm 21 Jul 2014
Copy link to clipboard
Print this post
I glanced over the schematics last Friday and thought to myself... I bet that jumper connected to the programmer line is going to cause problems. Congratulations... You are the first victim!
--CurtisI am not a Mad Scientist... It makes me happy inventing new ways to take over the world!!
Notice. New forum software under development. It's going to miss a few functions and look a bit ugly for a while, but I'm working on it full time now as the old forum was too unstable. Couple days, all good. If you notice any issues, please contact me.
Print this post
I glanced over the schematics last Friday and thought to myself... I bet that jumper connected to the programmer line is going to cause problems. Congratulations... You are the first victim!
