Searching \ for '[PIC]: Help with MPLAB funkiness, please...' 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: 'Help with MPLAB funkiness, please...'.

Exact match. Not showing close matches.
PICList Thread
'[PIC]: Help with MPLAB funkiness, please...'
2000\11\23@105453 by o-8859-1?Q?K=FCbek_Tony?=

flavicon
face
Hi,
Have a very odd problem with MPLAB, have coded a fairly
large project for the 18x series in relocatable modules.
As I'm waiting for the h/w to arrive I decided to do some
test within MPLAB using the simulator. However a very odd thing
happens.
After reset, then stepping the program it BEGINS at the first *called*
routine ( i.e it does not start at 0x0000 as it should ).
However looking at the clock/counter is clearly shows that x no. of
cycles already has been executed. Then I took a look at the program
memory
window instead and there I somehow can step from reset vector.

Very strange inded, continuing to step through the program it, most of
the time,
NEVER steps inside called code modules ( where i can see my code ), it
does this
however for maybe 2-3 modules ( out of 20 ). But, again, using the
program memory
window I can see that the code is correct and ececuted BUT I CANNOT STEP
IN THE CODE MODULES <phew>..very anoying.

For example in the main module ( the main loop ) I can step in the
subroutines
but not in the mainloop ?? after the return from a subroutine the
'cursor' just
stays at the 'return' line when single stepping ( but as said before,
looking
at the memory window I can see the instructions beeing executed after
the return ).

ANYONE ?... why this ?...please...

/Tony







Tony Kübek, Flintab AB            
²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²
E-mail: spam_OUTtony.kubekTakeThisOuTspamflintab.com
²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²

--
http://www.piclist.com hint: PICList Posts must start with ONE topic:
[PIC]:,[SX]:,[AVR]: ->uP ONLY! [EE]:,[OT]: ->Other [BUY]:,[AD]: ->Ads


2000\11\23@150357 by Olin Lathrop

face picon face
>>
After reset, then stepping the program it BEGINS at the first *called*
routine ( i.e it does not start at 0x0000 as it should ).
However looking at the clock/counter is clearly shows that x no. of
cycles already has been executed. Then I took a look at the program
memory
window instead and there I somehow can step from reset vector.
<<

MPLAB sometimes has problems stepping in the source code window, especially
when macros are being used.  I keep the program memory and source code open
all the time, and step only in the program memory window.  It tracks
correctly most of the time in the source window except when in a macro.  If
execution jumps to a different source module, you sometimes have to manually
point it to the new module.


*****************************************************************
Olin Lathrop, embedded systems consultant in Devens Massachusetts
(978) 772-3129, .....olinKILLspamspam@spam@embedinc.com, http://www.embedinc.com

--
http://www.piclist.com hint: PICList Posts must start with ONE topic:
[PIC]:,[SX]:,[AVR]: ->uP ONLY! [EE]:,[OT]: ->Other [BUY]:,[AD]: ->Ads


2000\11\23@165726 by Morgan Olsson

picon face
I usually have the *.lst file open at side of the asm file I am debugging, and macro expansion on, so in th elist file I can see every step and also comments etc whenever it is executing instructions not visible in the asm file.

An option to "singlestep" and highlight macro calls like instructions would be very appreciated, Microchip!

/Morgan


>MPLAB sometimes has problems stepping in the source code window, especially
>when macros are being used.  I keep the program memory and source code open
>all the time, and step only in the program memory window.  It tracks
>correctly most of the time in the source window except when in a macro.  If
>execution jumps to a different source module, you sometimes have to manually
>point it to the new module.

--
http://www.piclist.com hint: PICList Posts must start with ONE topic:
[PIC]:,[SX]:,[AVR]: ->uP ONLY! [EE]:,[OT]: ->Other [BUY]:,[AD]: ->Ads


2000\11\24@024827 by Bob Ammerman

picon face
> MPLAB sometimes has problems stepping in the source code window,
especially
> when macros are being used.  I keep the program memory and source code
open
> all the time, and step only in the program memory window.  It tracks
> correctly most of the time in the source window except when in a macro.
If
> execution jumps to a different source module, you sometimes have to
manually
> point it to the new module.
>

I find MPLAB tracks well in the "Absolute Listing" window.

Bob Ammerman
RAm Systems
(contract development of high performance, high function, low-level
software)

--
http://www.piclist.com hint: The list server can filter out subtopics
(like ads or off topics) for you. See http://www.piclist.com/#topics


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