PK2 debug exec in wrong place.

Status
Not open for further replies.
P

Pommie

Well-Known Member
Most Helpful Member
I am trying to debug a 12F509 with PK2 and it appears that MPLAB is trying to place the debug executive at location 0x600. The 12F509 only has memory up to 0x3ff. I've posted on Microchip about this but as it's weekend I thought I would see if anyone here can help.

This is the output window,

edit, forget it, it looks like this device needs additional circuitry before you can debug.

Mike.
 
Last edited:
Hay Pommie, Nice catch.Perhaps it would covered only in next version update.
How are you other wise? Finger fully restored and perhaps we can forget about that accident.

Ps: Can you set the device to base line and select the device, there after see the mplab limitations as displayed there please?
 
Last edited:
Hi Sarma,

Yes, my finger is fully restored.

I hadn't tried debugging one of the little pics before and didn't realize that an additional header was required. I'm currently debugging the 12f509 code on a 16F886 as that was the smallest chip I had that has full PK2 debug (the 16f88 only has partial support). The hardest bit is making sure I don't exceed the 2 address stack.

I hope all is well with you and your family.

Mike.
 
Status
Not open for further replies.

Similar threads

P
XC8 warning - what is wrong?
Replies
7
Views
3K
tumbleweed
T
P
Is MCC (code Configurator) wrong?
Replies
5
Views
746
Ian Rogers
B
  • Question
Temperature controlled fan using PIC16F877a (in assembly language)
Replies
6
Views
1K
Dan Soze
D
T
  • Question
Time Interval In STM32
Replies
2
Views
1K
tepalia02
T
K
  • Question
Role of OSI Model in IoT Projects
Replies
6
Views
3K
rjenkinsgb
Menu
Log in
Register
Cookies are required to use this site. You must accept them to continue using the site. Learn more…