Hello,
It appears that my EEPROM edits are not written to the EP5 on download. So, I am trying to find out why.
I opened the EEPROM editor and selected the project hex file by mistake. I got an error about past grid or something and then an AV:
Access Violation at address 006F22CA in modulte mikroPascal Pro Pic.exe. Read of address 00000007
The edits were downloaded using 8.x but not now.
Any ideas?
Mark
Access Violation...
Re: Access Violation...
Did you check Use EEPROM in project check box in eeprom editor?Mark- wrote:Hello,
It appears that my EEPROM edits are not written to the EP5 on download. So, I am trying to find out why.
Do you have DATA(EEPROM) option under HEX File Options in picflash programmer checked?
I could not reproduce the AV error. Could you provide me with the hex file you were trying to load and the brief description of steps you took to import it.Mark- wrote: I opened the EEPROM editor and selected the project hex file by mistake. I got an error about past grid or something and then an AV:
Access Violation at address 006F22CA in modulte mikroPascal Pro Pic.exe. Read of address 00000007
The edits were downloaded using 8.x but not now.
Any ideas?
Mark
Send it to srdjan@mikroe.com along with the steps I should follow in order to reproduce the problem.Mark- wrote:Hello,
Yes. In my longer message I gave more details. The error is 100% reproduciable.
Yes. I still have the project hex file. Where do you want me to send it?
Mark
Hi,
Anyway, it is fixed now. It will be included in the release version of the compiler.
Thanks.
I have found the problem. In your .hex file you had a few empty lines at the end of the file and after 'end of file' intel hex line. In eeprom editor tool, we did not predict such situation.srdjan wrote:Send it to srdjan@mikroe.com along with the steps I should follow in order to reproduce the problem.Mark- wrote:Hello,
Yes. In my longer message I gave more details. The error is 100% reproduciable.
Yes. I still have the project hex file. Where do you want me to send it?
Mark
Anyway, it is fixed now. It will be included in the release version of the compiler.
Thanks.