Hi,
After first trials with PBP I also checked ASM-file made by PBP and I was very puzzled. Then I found this old thread (asm and pbp), which explained these strange strings (list of macros).
BR,
-Gusse-
Hi,
After first trials with PBP I also checked ASM-file made by PBP and I was very puzzled. Then I found this old thread (asm and pbp), which explained these strange strings (list of macros).
BR,
-Gusse-
Thanks guys,
I know how the toolchain works, PBP compiles to ASM (sort of) and MPASM assembles that file creating a .hex file. I was hoping I somehow could get an ASM file containing only what will actually get assembled after all the assembler directives etc have been parsed/evaluated and the macros "called" have been replaced with the actual ASM code.
Oh well, the routines I'm trying to figure out here are fairly simple, like in the example I posted. Between the ASM, LST and MAC files I think and hope I can figure it out.
Darrels wonderful interrupt routines saves all the PBP system variables and in my case that just takes too much time. So, I'm trying to figure out what variables are being used by my routines so I can save those and only those.
Disassembling the hex file won't do me much good as I then have lost all variable names etc.
Thanks!
/Henrik.
That's not very imaginative. Add this to your PicBasic code and disassemble it:Disassembling the hex file won't do me much good as I then have lost all variable names etc.
and it will be easy to find in the assembler code, even if it is renamed.Code:@ nop @ nop @ nop Variable_Name = Variable_Name @ nop @ nop @ nop
Art.
Bookmarks