Simulator

[Darrel Taylor]

If you have PBP 2.60A, then you can use .pbp files directly in Proteus.
Or you can use Proteus inside of MPLAB with more debugging options.

With previous version of PBP, you can only simulate the .HEX files.

[F1CHF]

OK darrel
you know everything !
and we got answer as soon as the enter key is done !
about this sentence
"Or you can use Proteus inside of MPLAB with more debugging options."
Mplab is too complicated for me ... may be I'm too old now "$3E" years old ! hi ...
best regards,
francois

just one question (off topic) what about Mélanie ?
She is still in the support group ?
I always appreciated her support way of life.

[F1CHF]

hello 23h35
I spent hours with the big BLINK application (bas and pbp under Pic Basic PRO 2.60A)
with ISIS version 7.7 SP2 without succes !
he didn't accept pbp extension
simulation is working (LED blinking), but I can't see any Basic line to put breakpoint and display my variable (compteur)
nb: I got this INFO message at start time ! (speaking about PROTON ???)

here is my big application :
' Example program from manual to blink an LED connected to PORTB.3 about once a second
compteur var byte

cont: High PORTB.3 ' Turn on LED connected to PORTB.3

Pause 500 ' Delay for .5 seconds

Low PORTB.3 ' Turn off LED connected to PORTB.3

Pause 500 ' Delay for .5 seconds
compteur = compteur + 1

Goto cont ' Go back to loop and blink LED forever
End

[Darrel Taylor]

Proteus assumes that anything with a .BAS extension is a PROTON program.
So use .PBP instead for PicBasic Pro programs.

Then you need to tell proteus how to compile a PicBasic Pro program... (Note: this assumes you have PBP 2.60A)

In ISIS, go to the Source > Define Code Generation Tools... menu and click the New button.
Point it to the c:\pbp\PBPMPLAB.BAT file. It will create a PBPMPLAB "tool".
Enter the following fields.

Source Extn: PBP
Obj. Extn: COF
Command Line: %1 -ampasmwin -oq -k#
List File Extn: LST
Then click OK



After drawing your circuit with a PIC chip in it ... Save it to a new folder first.
Then go to Source > Add/Remove Source files...
Under "Code Generation Tool", drop-down the box and select PBPMPLAB
Click the New button and either select the .PBP file, or give it a new name and it will create a new file.
AFTER giving it a Source Code Filename ... enter the PIC's part number in the Flags field -p12F683.
Then press OK.



To edit the source code, go to Source menu and select the file you specified previously at the bottom.
When you try to start the simulation, it will automatically compile the program if you have changed it.
Or you can select "Source > Build All" and it will compile it even if you haven't changed it.

If the compile succeeds, it will begin running the simulation.
If you selected "Build All" it will show the results of the compile process.

On Sunday I will try to make a video of the process.
Going Kart racing tomorrow at Unser's in Denver.
Need some sleep first. And some Advil after ... OK, several Advil.

[F1CHF]

5h30 AM it is not serious ! hi ..
Many thanks for your nice explanation, is it great !
I was obliged to modify the PBPMPLAB.BAT to point on the MPASMWIN (no problem at all)
I use MPASM version 5.2 (thanks for the explanation about Path installation)
http://melabs.com/support/mpasm.htm

Now the last error message I got is in the screen copy (Isis msg)
(looking for a BLINK.O file ???)

have a nice week end first

all the best
Francois

[mackrackit]

Using PBP 2.60A and MPASM v5.36 "O" files are generated. Maybe an MPASM upgrade will help?

[F1CHF]

Using PBP 2.60A and MPASM v5.36 "O" files are generated. Maybe an MPASM upgrade will help?

You can tell me that I am "outside my shoes"
I spent half an hour , but I am not able to locate where I can download
MPASM V5.36 !
thanks ...
francois

[mackrackit]

MPASM is part of MPLAB.
The latest version can be found here
http://www.microchip.com/stellent/id...&part=SW007002

[jellis00]

Proteus assumes that anything with a .BAS extension is a PROTON program.
So use .PBP instead for PicBasic Pro programs.

Then you need to tell proteus how to compile a PicBasic Pro program... (Note: this assumes you have PBP 2.60A)

In ISIS, go to the Source > Define Code Generation Tools... menu and click the New button.
Point it to the c:\pbp\PBPMPLAB.BAT file. It will create a PBPMPLAB "tool".
Enter the following fields.

Source Extn: PBP
Obj. Extn: COF
Command Line: %1 -ampasmwin -oq -k#
List File Extn: LST
Then click OK

Attachment 4957

After drawing your circuit with a PIC chip in it ... Save it to a new folder first.
Then go to Source > Add/Remove Source files...
Under "Code Generation Tool", drop-down the box and select PBPMPLAB
Click the New button and either select the .PBP file, or give it a new name and it will create a new file.
AFTER giving it a Source Code Filename ... enter the PIC's part number in the Flags field -p12F683.
Then press OK.

Attachment 4958

To edit the source code, go to Source menu and select the file you specified previously at the bottom.
When you try to start the simulation, it will automatically compile the program if you have changed it.
Or you can select "Source > Build All" and it will compile it even if you haven't changed it.

If the compile succeeds, it will begin running the simulation.
If you selected "Build All" it will show the results of the compile process.

Darrel, I am trying to start using Proteus ISIS with simulator. Followed these instructions of yours and when I do a Build ALL I get the following error:
Processing ..\..\..\PBP26\Ellis_Codes\Temperature\0DisplayLM3 4temp.pbp...
PBPMPLAB ..\..\..\PBP26\Ellis_Codes\Temperature\0DisplayLM3 4temp.pbp -ampasmwin -oq -k# %1 -ampasmwin -oq -k#
\Microchip\MPASM was unexpected at this time.
ERROR: PBPMPLAB.BAT reported error code (255L).
Build FAILED with 1 error(s).

Looked at PBPMPLAB.BAT statements and can't figure out what error 255L is telling me. Can you advise??

[Darrel Taylor]

Normally, you get those kind of paths when you haven't saved the .DSN yet.

Each .dsn should be saved in it's own folder, and the source code should be in the same foler.

[jellis00]

Normally, you get those kind of paths when you haven't saved the .DSN yet.

Each .dsn should be saved in it's own folder, and the source code should be in the same foler.

Double checked that and .dsn file and source code are in the same folder. Still get same errors.
Maybe I should clarify, I am attempting to use Proteus Lite 6.7 to evaluate whether I want to buy VSM Startup Kit or not. I was under impression that I could simulate running my PBP v2.6A code on an 18F2620 model of CPU with Proteus Lite 6.7....not true?? I do notice that BUILD ALL is only option not grayed out...the Debug options are all grayed out, so maybe that means I can't simulate with Proteus Lite 6.7.

[Darrel Taylor]

It's been a few years since I had the Demo version.
So I installed it on another machine.

I do not see any example design files that use an 18F2620.
Which means you would have drawn a new schematic with an 18F2620.

The demo version does not allow you to save new designs, so I think your "Double checked that" may not have included the "save the file first" part.
But it won't let you simulate a new design either.

You can use any of the existing demo designs (without changing the design), and change the .hex file that it executes.
But most of them are 18F452's, and the designs are limited.

[jellis00]

Darrel, I have Proteus VSM SDK working now. However, when I run a simulation in the debug step mode I don't see variables listed in the Variables Window. In checking the VSM help files it says that most COF files from compilers will support the Variables Window. Does the PBP 2.6C compiler create a COF file that will let Proteus VSM show the variables in the program in the Variables Window??
John

[Darrel Taylor]

Yes, unfortunately the variables don't show when simulating directly in ISIS.

But if you run Proteus as a debugger in MPLAB 8 the watch window will show the variables.
MPLAB uses the same .cof file, so it's not currently known why they work in MPLAB and not ISIS.

Since you can have as many serial lcd's or virtual terminals as you want, it easier to just put a few statements in your program to spit out the variables at key points.
I don't really miss the variable window too much.

[AvionicsMaster1]

Boss says we might have some extra money and I'd like to order simulation software and an upgrade to PBP3.0.

Do you still recommend Proteus/ISIS when using PBP 3.0?

Thanks for your time.

[Darrel Taylor]

It's not very often that you won't see Proteus running on my computer.
It works great with PBP3.

I highly recommend getting the ARES (PCB layout) package with it.
I used to hate laying out PCB's, but it's almost enjoyable now.

Draw it, simulate it, lay it out, export gerbers, and order your proto's all in the same day.