C language with Proteus

gle=0000274d

how to implement c language in a proteus simulation

proteus labcenter elf to coff

Hi Shedeed,
You can read VDM51.pdf in Help folder of your proteus directory, it is explaint about "Proteus VSM and Keil Development Tools".


Siswanto

proteus +dwarf

Proteus loads the object module format produced by the compiler in order to extract addressing information, nesting levels, source info etc.

Supported formats include COFF, COD (limited support), UBROF8 (IAR), OMF51 ( Keil), ELF/DWARF (forthcoming in V6.8 ).

If your compiler can produce one of these formats then specify this file as the program property for the microcontroller on the schematic.

More information can be found here : h**p://www.labcenter.co.uk/products/compilers.htm

Iain.

proteus elf

Hi Iain,
I'm intersting with you pronouncement. I have ImageCraft compiler that can produce COFF file. I wanna simulate AVR with proteus. Could you please touch me how to load my COFF file to the proteus??
I have visite
h**p://www.labcenter.co.uk/products/compilers.htm
but the informations on it are minimum except about keil.



Thaks&Best regards
Siswanto

proteus omf51

You have to compile the source to a HEX file.

integrate keil proteus

pico said:

You have to compile the source to a HEX file.

Click to expand...

Hi Pico,
I have done successfully like as you mention above. But i need the better one, like as on keil I can do fully debugging like as single step, breakpoint, watch variable, change value of variable, and i can monitor every changing on proteus.

Does ImageCraft can do it?



Thanks
Siswanto

proteus variable watch

Let's say you have a simple program fred.c.
When you compile it you will get fred.cof and fred.hex.

fred.hex contains only binary information and so can be simulated but not debugged (no knowledge of C source, no link up between address and opcode, etc..).

fred.cof is a symbolic debug file and contains debugging information as well as source info. You can therefore specify fred.cof as the program property of the microcontroller (instead of fred.hex) and, not only will it simulate but when paused, you can access source window to step code in C or assembler, set breakpoints and so on.

Note that there are ambiguities with cof - different compilers use the segments for different purposes. While everything should work it is dependant on the compiler following standard protocol when implementing COF.

I believe Imagecraft are working on (or perhaps already have) ELF/DWARF options for debug output. That being the case I would recommend switching to this format when we release Proteus V6.8 (which includes an ELF/DWARF loader). The ELF/DWARF format is not only much 'cleaner' but also a far richer format and we intend to move towards ELF/DWARF and away from COF and COD in the future. This is very much in line with Atmel who I believe have gone ELF/DWARF in AVRStudio 4.

Hope this helps.
Iain.

proteus variable watch view

shedeed;
I saw some topic about using proteus with MPLAB. But I can't remember where it is. Please check the Labcenter's Website.

proteus .hex debug no source line

When i used *.cof file as property of microcontroller, the simulation works corectly but when I Pouse it, there is a message like as picture. what wrong??



Siswanto

How to integrated Keil and Proteus.?

I uses windows 98,

"failed to connect command socket to port localhost:8000.
GLE=0000274D"

settings in Debug tab are
Host IP : localhost
Port : 8000

Can you help me..?

Nothing is wrong with that picture - the simulation has simply paused at a point asynchronous to an instruction execution.

From the selector at the top of the picture you should be able to select a file corresponding to your source code. Once selected you can set breakpoints (F9), single step your code in C (F11 to step into, F10 to step over) or in assembly (CTRL+D for disassembly mode and then shortcuts as above).

All the options on shortcut keys are also available by right clicking on the source window for a context menu or from the debug menu.

Iain.