DIY Electronics Message Board
Register  |   |   |  Latest Topics
 
 
 


Reply
  Author   Comment   Page 1 of 2      1   2   Next
John Wood
Reply with quote  #1 
I had received the 150 a couple weeks ago but never really tried it out until now. Its using the P016 firmware and i'm using the correct MicroPro version. The program says that it is connected so I assume everything is working correctly. The problem is when I try to program the new firmware to a 16F648A chip. I thought I read that this would work, correct me if I'm wrong. Anyway, I line the chip up correcly on the zif socket and load the new hex file but when I try to program it first says that the chip isn't recognized so I continue and then continue to erase in order to program. But then I get ROM Programming Error at 0x0000. Good 0x28C9 Bad 0x000. Then I just tried programming a hex with eeprom data and I get the same end result except the Good hex value is different. I'm still kind of new at all this stuff so I'm not sure what I should do at this point. Any help would be appreciated.

Thanks,
John Wood
Bob Axtell
Reply with quote  #2 
Yes, you are doing the right thing, but are you setting the Chip select on F648A (correct device)?

Does the display say what the programmer actually is? If you click FILE>PROGRAMMER and select, say K149, does it tell you that no, you actually have a K150? What I am getting to is that MicroPro is a little vague about keeping you- the user- in the loop.

See, the first step is to make sure that the drivers for the FTDI USB ship are properly installed and running. because we do not use an enumeration message (for "Plug'N-Play" installation) it is more complex to verify that everything is online.

Then, we will go further.
Are you with me?

--Bob
John Wood
Reply with quote  #3 
Thanks for the reply. I made sure that the correct chip was selected and the got the same result. I also did what you suggested by changing the type of programmer in the program and see what happened and it said the connected board was the K150 and set that as the current programmer. So it seems like the board is being found correctly.

Thanks,
John Wood
Bob Axtell;
Reply with quote  #4 
OK, that means that the drivers are running properly, and that the drivers are able to communicate with the device.

The next is a series of tests designed to locate the hardware problem, because that is about he only thing left.

1. Make SURE no pins on the PIC Programmer Chip 'F628 or 'F628A are bent or curled.

2. Instead of installing chips into the socket, install pins or #22 guage wires, anc close the latch so that they stand up straight, on pin#1(VPP1) and pin#6(GND) of the DIP40. Set the chip select to PIC16F876. Press the big READ button (ignore the errors). Measure approx 13V with a good meter (A good meter is a Fluke) while it is reading.

3. Now install wires on pin#5(VPP2) and pin#6(GND) of the DIP40. Set the chip select to PIC16F648. Press the big READ button (ignore the errors). Measure approx 13V with a good meter while it is reading.

4. Install pins or #22 guage wires on pin#35(VCCP) and pin#6(GND) of the DIP40. Press the big READ button (ignore the errors). Measure approx 5V with a good meter while it is reading.

If step #2 failed, transistor TR2 has failed. If step#3 failed TR3 failed. If step#4 failed, TR1 failed. It is possible that the LS06 has failed, but unlikely. NOTE: theoretically, one could measure the transistor in circuit and verify it, but in fact the effect of other devices makes the measurement a poor test. All of those devices are the equiv of the standard workhorse PNP device PN2907/SOT23.

Lemme know..

--Bob



John Wood
Reply with quote  #5 
I ran the tests you had me do:

1. The programmer chip had no bent pins and was plugged in correctly.

2. I don't have a Fluke brand multimeter but its decent. I was able to measure 12.90 volts during the read.

3. I measured .22 volts during the read.

4. I wasn't sure if I was supposed to use the same chip selection from test 3 so I used it anyway. I measured 0 volts from the read.

So I'm not sure if test 4 was done correctly but it looks like test 3 failed. Where do I go from here?

Thanks,
John Wood
Bob Axtell;
Reply with quote  #6 
Then TR3 is defective. It will need to be replaced.

I can send you one and you can replace it, or you can send it to us and we can replace it.

--Bob
John Wood
Reply with quote  #7 
I replaced TR3 with what you provided me and when I do test #3 I get 12.9 volts so that works now. However, I am still get the same errors when I try to program.

I'm wondering if it has to do with TR1 because I never got test #4 to work as well. I wasn't sure which pic to use in the chip selection so I used the PIC16F648 from test #3. The result of that was 0 volts.

If that was the correct chip selection, should I replace TR1 with the other transister you provided me?

Thanks,
John Wood
Bob Axtell
Reply with quote  #8 
Yep!

--Bob
John Wood
Reply with quote  #9 
I replaced that transister and the programmer works like a charm now! It's weird that they both went bad. But thank you very much for your help.

John
Bob Axtell
Reply with quote  #10 
Glad to hear it, John!

--Bob
Francis
Reply with quote  #11 
Hi, I'm having the same problems John had except I'm using k128. Is the hardware test you mentioned also a valid way of testing k128?
Bob Axtell
Reply with quote  #12 
Its slightly different for the K128, it does NOT have transistor for the VCC (drives direct from the internal F628). There is only ONE transistor switch, for VPP.

But Micropro does not provide diagnostics. The transistor could be bad, but it also could be some other things wrong. We are dramatically improving this in our new application being developed for Protocol 19.

I don't get many K128s or K182's  in for warranty service. Feel free to send it in and I will rest, repair, and retuurn it in a flash. The address is published under the recent "Warranty Service" posting I made.

--Bob



hampton

Registered:
Posts: 3
Reply with quote  #13 
Hi, the same error occurred when programming the PIC18F4550. But when I try to programm the PIC12F675 and others it works! What can be the problem??
jhbe

Registered:
Posts: 45
Reply with quote  #14 

That would be because the 18F4550 is not supported. Yet. You'll have to wait for P019/MP2 or, if you're really keen/deperate, try one of the two "homegrown" programmers mentioned in this forum.

hampton

Registered:
Posts: 3
Reply with quote  #15 
I bought the PIC with the right firmware from Da-Logic! This firmware supports the 18F4550, so there shouldn't be a problem!
Previous Topic | Next Topic
Print
Reply

Quick Navigation:

Easily create a Forum Website with Website Toolbox.

Thank you for visiting.