Matrix user forums

I have a problem with the eeprom component, it wont compile. I get the following

Target folder: D:\Solar
Source name: D:\Solar\solar_controller8backup.fcfx
Title:
Description:
Device: PIC.18F.18F4550
Generated by: Flowcode v8.1.0.8
Date: Monday, December 03, 2018 12:31:35
Users: 1
Registered to: Roy Johnston
License key: **********
https://www.flowcode.co.uk
Launching the compiler...

Microchip MPLAB XC8 C Compiler (Free Mode) V1.45
Build date: Nov 15 2017
Part Support Version: 1.45
Copyright (C) 2017 Microchip Technology Inc.
License type: Node Configuration

Employing 18F4550 errata work-arounds:
* Corrupted fast interrupt shadow registers
.


Memory Summary:
ID Location space used 0h ( 0) of 8h bytes ( 0.0%)


You have compiled in FREE mode.


Compilation successful!

Launching the linker/assembler...

Launching the programmer...

Connecting...
PICkit 3 detected
Connecting to PICkit 3...

Firmware Suite Version...... 01.26.65
Firmware type......................PIC18F
.


PICkit 3 Connected.

Target Detected

Device ID Revision = 00000007
. .



Erasing ...
Erase device complete


Programming Device ...
EEData Memory

Programming failed

Failed to perform Program !!!

please see photo for proper fault report

Hello Roy,

That looks to be a PICkit related problem. I see your still using the old PK3CMD programming method.

I would advise you to move to the IPE programming method as hopefully it may simply solve the problem for you.
https://www.flowcode.co.uk/wiki/index.ph ... _.28NEW.29

Same problem,
this program was working before on ver 6 and 4.
as soon as I remove eeprom out of flowchart all is ok.

in actual fact it worked a few weeks ago on ver 8.
updates?

Hi Roy,

The error is that the PICkit is trying to program an EEPROM memory location and that programming is failing.

Select the EEPROM component on the panel and look at the component properties. Are you using the initial values field? If not then please remove all the values from there and they will no longer be programmed when downloading to the chip.

It could be the chip has developed a problem. On a 18F4550 you get approx 100,000 EEPROM write cycles. Have you written to the EEPROM in a loop as this can quickly eat through the write cycles?

Thank you
it was the pic