0
\$\begingroup\$

Good day to all.

I'm not yet very experienced with MPLAB-X and don't know how to deal with the problem that I am currently having.

I'm developing with a project that uses the 16F1782.  I'm debugging with Real ICE which is connected to the appropriate emulation header - AC244064. This has a pic16f1789-me chip on board.

My code is written in assembler and I am using absolute mode - the appropriate check box is ticked on the project properties page.

I see two problems - hopefully related.

The first problem is that although the header appears to program correctly, the code never gets past the ColdBoot location in program memory.  Upon halting the emulator, I get the following message: "An Error occurred while running.  Failed to read emulation memory." (on two lines)

The other thing that I noticed is that in the Dashboard panel on the left side of the screen, Program Memory is shown as 641 words used (out of 2048 words).  However, Data memory is shown as 0 bytes used (out of 256 bytes). 

I'm not sure how to troubleshoot this.  Most likely an error on my part - I'm hoping that someone can give me guidance.

Many thanks!

dwayne

Additional information:

The last time I used MPLABX was while the computer was running WIndows 7. MPLABX version was 3.15.

The computer was upgraded to Windows 10 several months ago, just before the Microsoft free upgrade to Win 10 period expired.

I have just now downloaded and installed the most recent version of MPLABX - v3.50.

Same problem.

However, I have just noticed another anomaly: I'm getting errors during the assembly process:

Message[303] D:\DROPBOX\PIC\L598\L597A0BE.ASM 3255 : Program word too large. Truncated to core size. (DEFF)

This happens at the two lines where my config statements live as well as the very end of the code: just above the line that contains "END".

Not sure if this helps.

dwayne

More information: this is from the list file generated by the assembler. I've included all of the locations where the truncated word message appears.

Message[303]: Program word too large. Truncated to core size. (F9C4)

8007 39C4 00137 __config _CONFIG1, _FOSC_INTOSC & _WDTE_OFF & _PWRTE_ON & _MCLRE_ON & _BOREN_OFF

Message[303]: Program word too large. Truncated to core size. (DEFF)

8008 1EFF 00138 __config _CONFIG2, _WRT_OFF & _VCAPEN_OFF & _PLLEN_OFF & _STVREN_ON & _BORV_LO & _LPBOR_OFF & _LVP_O

And:

                  03254 

Message[303]: Program word too large. Truncated to core size. (F9C4)

Message[303]: Program word too large. Truncated to core size. (DEFF)

                  03255     END

MPASM 5.71 L597A0BE.ASM 12-22-2016 18:19:18 PAGE 65

Sorry for the poor code formatting - I have to learn how to do that properly here.

\$\endgroup\$
  • \$\begingroup\$ Which debugger are you using? What happens if you run your code in the simulator? \$\endgroup\$ – Bruce Abbott Dec 23 '16 at 0:57
  • \$\begingroup\$ I'm not certain what you mean when you ask "What debugger am I using?". I'm using the emulation debug header from Microchip - this header gives me debug capability similar to the old ICE2000 In Circuit Emulator. Code seemed to run as far as it could when I ran it in the simulator at home last night. I say "as far as it could" because the simulator doesn't appear to support Weak Pullups and I couldn't quickly go past the point where the input signals were always active because the simulator saw them as being LO. \$\endgroup\$ – Dwayne Reid Dec 23 '16 at 1:16
  • \$\begingroup\$ AC244064 connects to your PC via a debugger - PICkit 3, ICD 3, or REAL ICE. Which one are you using? \$\endgroup\$ – Bruce Abbott Dec 23 '16 at 1:32
  • \$\begingroup\$ Sorry - I'm using the Real ICE. \$\endgroup\$ – Dwayne Reid Dec 23 '16 at 1:32
  • \$\begingroup\$ "Program word too large. Truncated to core size. (DEFF)" Show us your code (just the initialization part will do). \$\endgroup\$ – Bruce Abbott Dec 23 '16 at 1:36

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.