Problem with PIC17C44

[radeonrelive]

Hello everyone

i have this problem when i want read the chip. Also when reprogram, but i find a new one, the information into the chip is not the same like the buffer.

any help can be accepted. thanks in advanced

[Dataman (Neil Parker)]

Hello radeonrelive,

Can you confirm that you have implimented the bypass capacitor as mention in the "Device info" section of our software related to thsi PIC device?

"
General Info:
In case of unreliable work of this device using universal adapter/module, please connect bypass capacitor (ceramic multilayer, that meet the EIA X7R or Z5U specification value 22nF-100nF) between GND(VSS) and VCC(VDD) pins of this device.
We provide a programming adapter DIL40/DIL40 ZIF AddCap with special soldering pads for better placing of some capacitors. The programming adapter package also contains 5 pieces of 100nF and 5 pieces of 100pF ceramic capacitors.
"

If the situation does not improve with the bypass capacitors applied, please let me know.

[radeonrelive]

Hello radeonrelive,

Can you confirm that you have implimented the bypass capacitor as mention in the "Device info" section of our software related to thsi PIC device?

"
General Info:
In case of unreliable work of this device using universal adapter/module, please connect bypass capacitor (ceramic multilayer, that meet the EIA X7R or Z5U specification value 22nF-100nF) between GND(VSS) and VCC(VDD) pins of this device.
We provide a programming adapter DIL40/DIL40 ZIF AddCap with special soldering pads for better placing of some capacitors. The programming adapter package also contains 5 pieces of 100nF and 5 pieces of 100pF ceramic capacitors.
"

If the situation does not improve with the bypass capacitors applied, please let me know.

hello Sr, yes, I'm putted a capacitor how like the description but don't working properly, I'm traying with 100nF like in the description 100pF, but i dont know what happens, this case don't have science. thanks for answering..

[Dataman (Neil Parker)]

Hello radeonrelive,

We have tested here with our sample of this chip and it works OK.

What version of the software are you running?
Does this happen with just one chip or many?
Can you provide a photo of the bypass capacitor placement for verification?
What is the result of the Selftest.. from the Porgrammer menu using the supplied 48pin diagnostic pod?

[radeonrelive]

im maked some proof with differents capacitors, but i guess the Vdd is to high.. i can provide some pictures for you..

selftest-ok

vdd-5.6v

soft version-3.95c

capacitors- 1nF - 100nF between pin 1 and 10

https://drive.google.com/drive/folders/ ... sp=sharing

[Dataman (Neil Parker)]

The placement of the bypass capacitor looks OK.

What is the result of a READ operation on this device? Can you perform this and then provide the full info-rich problem report using the standard method: Help > Create problem report. It is more useful than the screenshots and will give me the complete picture.

[radeonrelive]

Hi I have something...

[Dataman (Neil Parker)]

Hello,

We were not able to simulate such a problem with our samples. We tested all options for Verify, including +-10% VDD.
The problem source is local, it maybe the programmer itself.

Error - difference in data
0000FE08 FF7F FFFF
means something with the Config area.

If an identical error also appears in the case of setting the Verify once @ nominal VDD, it is most probably related to the DUT.

It might be also some HW error, but it is new programmer ... .

Basic operation for a new chip (if you are going to program it) is a Blank check.

[radeonrelive]

...when i want read the chip, i have this error...

[radeonrelive]

Hello,

We were not able to simulate such a problem with our samples. We tested all options for Verify, including +-10% VDD.
The problem source is local, it maybe the programmer itself.

Error - difference in data
0000FE08 FF7F FFFF
means something with the Config area.

If an identical error also appears in the case of setting the Verify once @ nominal VDD, it is most probably related to the DUT.

It might be also some HW error, but it is new programmer ... .

Basic operation for a new chip (if you are going to program it) is a Blank check.

hi Sr, yes this is the problem, when i put a new chip always i check the blank check, i have new chips and used for make a test. I'm traying everything and don't find the solution. Maybe the programmer don't working good...