Searching \ for '[PIC] Can't "Set PC at cursor" in MPLAB' in subject line. ()
Make payments with PayPal - it's fast, free and secure! Help us get a faster server
FAQ page: www.piclist.com/techref/microchip/languages.htm?key=mplab
Search entire site for: 'Can't "Set PC at cursor" in MPLAB'.

Exact match. Not showing close matches.
PICList Thread
'[PIC] Can't "Set PC at cursor" in MPLAB'
2005\05\06@072129 by Jinx

face picon face
Hi, I'm Larry. This is my brother Darryl, this is my other brother Darryl

A project has me stumped

I've been using MPLAB 6.40 for a very long time now and can't
figure this out. No other project has done it. This is a simple project,
with just one .asm file, no linker, nothing fancy. The build is successful.
Build Options are set just the way they are with oh so many other
projects. I simply can't see anything wrong with the way the project
has been formed or opened

Normally, when a project is built successfully, the Output window
goes to the back and the .asm text is in front with the green cursor
at the reset or program start org. Then it's possible to "Set PC at
cursor" by right-clicking with the editing cursor on the line you want
program flow to start from

In this project, bless it, grrrr, the green cursor is at reset in the
Program
Memory window, and can be moved around, but not never seen in the
.asm text window. Also, the Output window stays in front after the build

Tried all kinds of resets and even re-booted the PC in case the PS+
had gone funny, but no change

Any ideas ?

===============================================
If you aren't part of the solution, you're part of the precipitate

2005\05\06@084826 by olin_piclist

face picon face
Jinx wrote:
> In this project, bless it, grrrr, the green cursor is at reset in the
> Program
> Memory window, and can be moved around, but not never seen in the
> .asm text window. Also, the Output window stays in front after the build

I've occasionally seen something that may be the same symptom.  As best I
can tell, MPLAB looses association between source lines and program memory
addresses.  I had one case like that yesterday.  I know I had the right
source module open, but the RUN TO CURSOR menu entry, for example, was
grayed out.  I tried closing and reopening the file.  Eventually I got out
of MPLAB, rebuilt everything (although there had been no changes), got back
into MPLAB, and suddenly everything worked again on that same source file.
This has happened a few times before and I've never been able to figure out
the cause.


*****************************************************************
Embed Inc, embedded system specialists in Littleton Massachusetts
(978) 742-9014, http://www.embedinc.com

2005\05\06@091042 by Jinx

face picon face
> This has happened a few times before and I've never been able to
> figure out the cause

Well that's kind of encouraging. I've noticed the odd time when
something didn't work but it usually comes right. It's quite frustrating
as I'm full of ideas and busting to get ahead. The one thing that does
bother me is that previous versions of this file didn't exhibit this the
last time I used them in a project, but now they also have no text run
cursor. I moved the files over to another PC running MPLAB 7.0 and
the same thing happened - no cursor. I don't know what to think
(especially as the other versions of this file have not been edited at all).
Other recent F452 projects test OK, so there must be something
common to this particular file and its predecessors, but 4 hours
looking hasn't turned up anything. Maybe after a power-down it'll
all be ticketty in the morning

2005\05\06@100309 by Marcel Duchamp

picon face
Jinx wrote:
> Hi, I'm Larry. This is my brother Darryl, this is my other brother Darryl
>
> A project has me stumped
>
 > In this project, bless it, grrrr, the green cursor is at reset in the
> Program
> Memory window, and can be moved around, but not never seen in the
> .asm text window. Also, the Output window stays in front after the build
>
>
> Any ideas ?

Hi Larry, err, Darryl, er, uh, Jinx, what the hell

I have not had this happen since way back around Mplab 5.4 or early
6ish.  But the thing was then that the main project file (*.pjt?) would
get corrupted somehow and stuff would break.  Deleting the main project
file and creating a new one solved the problem back then.  So if nothing
else works, give that a try.
MD

2005\05\06@115644 by Alan B. Pearce

face picon face
>I've occasionally seen something that may be the same symptom.  As best I
>can tell, MPLAB looses association between source lines and program memory
>addresses.  I had one case like that yesterday.  I know I had the right
>source module open, but the RUN TO CURSOR menu entry, for example, was
>grayed out.  I tried closing and reopening the file.  Eventually I got out
>of MPLAB, rebuilt everything (although there had been no changes), got back
>into MPLAB, and suddenly everything worked again on that same source file.
>This has happened a few times before and I've never been able to figure out
>the cause.

I have seen similar too, and came to the conclusion that it thinks a given
window has the focus (even though the title bar is not highlighted), when it
doesn't. I have recovered the situation by working my way around all the
windows, and eventually you find the one that thinks it has the focus, and
then on selecting the one you actually want, the focus goes with you instead
of staying.

2005\05\06@124256 by Dave Turner

picon face
I've got MPLAB 6, and when using it with an ICD2, it very often gets
confused about which line the breakpoint is, which screwes up
debugging very badly.

On 5/6/05, Alan B. Pearce <spam_OUTA.B.PearceTakeThisOuTspamrl.ac.uk> wrote:
{Quote hidden}

> -

2005\05\06@184339 by Jinx

face picon face
> > Hi, I'm Larry. This is my brother Darryl, this is my other brother
Darryl

> Hi Larry, err, Darryl, er, uh, Jinx, what the hell

Larry, Darryl and Darryl  were three not-too-bright yokels from the
Bob Newhart Show. That's how dumb MPLAB had me feeling

> Deleting the main project file and creating a new one solved the
> problem back then.  So if nothing else works, give that a try

Well, nothing else worked - including what you suggested ;-(
already been there. It's very annoying and time-consuming

More... (looser matching)
- Last day of these posts
- In 2005 , 2006 only
- Today
- New search...