Looking at pic basic pro symbol values in mplab 8.15a simulator

[Bruce]

Have you tried opening the watch window, and selecting your variables?

It works fine for me. Never tried mouseover, but I definitely can watch variables change
when I have the watch window open. And they change as the PBP program runs. It doesn't
need to be stopped before they update.

[ukemigrant]

Hey Bruce, sadly yes that's the window that I add the variables to but it always says 'value not found'. Do you have the Symbols tab in the workspace window populated with variables, functions etc? That's the other tab in the window that lists all the source code in the project.

Thanks again.

Have you tried opening the watch window, and selecting your variables?

It works fine for me. Never tried mouseover, but I definitely can watch variables change
when I have the watch window open. And they change as the PBP program runs. It doesn't
need to be stopped before they update.

[Charles_Leo]

The variables you declared in the PBP program should appear in the watch window Add Symbol dropdown, but an underscore "_" will be appended in front of the name. ("myvar" shows as "_myvar".) The exception to this are BIT-variables, which will not show by name.

In the build options for the source file, make sure that "Use MPASM Assembler" and "Source-level Debug" are checked.

You will need to specify the type of variable by right-clicking in the watch window after you add the variable. All variables are displayed as bytes by default.

[ScaleRobotics]

Looks like you can go to File, then Import, then selected the file.cod file, and then you can select your variables. Very nice Bruce, I did not know that either.

<img>http://www.picbasic.co.uk/forum/attachment.php?attachmentid=3393</img>

[ukemigrant]

Excellent thanks Charles_Leo, scalerobotics and Bruce.

I look forward to trying that when I get home tonight and tracking down the relevant part of the documentation that I might have missed.

I also look forward to contributing to the forum when I get up to speed.

Cheers.

[ukemigrant]

I thought I posted a final reply - I got this working ok - the _ variables were in the symbol list. Sadly the bit variables are not there, which I find a bit strange.

Thanks again for the help.

[Charles_Leo]

PBP BIT variables in MPLAB:

Bit variables in PBP are created as aliases to individual bits within a byte variable created to hold them. MPLAB won't display the bit aliases, but it will display the byte container variable. The problem is, you don't know the name of the container variable or the placement of the specific bits without digging into the .ASM file.

One solution is to create your own container variable and bit aliases. This won't make the bit names show in MPLAB, but it will allow you to show the container variable. You'll know which bits are which, because you defined their locations in the first place. There's no performance penalty using this method, because it's exactly what PBP would do if you declared bit variables. There are, in fact, advantages... like the ability to initialize multiple bit variables with a single command.

<code>
mybits VAR BYTE

bitflag0 VAR mybits.0
bitflag1 VAR mybits.1
bitflag2 VAR mybits.2
</code>

Now the variable "_mybits" will be available in the MPLAB watch window, and you'll know how the individual bits in the variable relate to your program.

[ukemigrant]

Excellent Charles! I fully intend to use this technique.

Nice one.

PBP BIT variables in MPLAB:

Bit variables in PBP are created as aliases to individual bits within a byte variable created to hold them. MPLAB won't display the bit aliases, but it will display the byte container variable. The problem is, you don't know the name of the container variable or the placement of the specific bits without digging into the .ASM file.

One solution is to create your own container variable and bit aliases. This won't make the bit names show in MPLAB, but it will allow you to show the container variable. You'll know which bits are which, because you defined their locations in the first place. There's no performance penalty using this method, because it's exactly what PBP would do if you declared bit variables. There are, in fact, advantages... like the ability to initialize multiple bit variables with a single command.

<code>
mybits VAR BYTE

bitflag0 VAR mybits.0
bitflag1 VAR mybits.1
bitflag2 VAR mybits.2
</code>

Now the variable "_mybits" will be available in the MPLAB watch window, and you'll know how the individual bits in the variable relate to your program.