Searching \ for '[PIC] DevEnvironment choices.' 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=environ
Search entire site for: 'DevEnvironment choices.'.

Exact match. Not showing close matches.
PICList Thread
'[PIC] DevEnvironment choices.'
2005\09\18@222143 by Herman Aalderink

picon face

These tiny PIC-ers sure keep me busy .....
(going fishing instead sure is an attractive alternative ...)

Where do I go from here ?
-- learn the big MPLAB environment
-- continue to use only MPASMwin.
-- trying to follow/learn Olin's system (is Olin's an expanded MPLAB
system?)

I am a hardware-oriented hobby-builder.
I am familiar and comfortable with MPASM (my homebrew PIC-programmer is
working great).

Should I take the plunge and learn all the MPLAB stuff or just mind my
own MPASM business?
(expanding to a bigger development-setup seems to require an awful lot
of time)

I just came across this (it triggered the question) :
I am not yet familiar with the Linker so the Object part is lost on me.

  Assembly Code Templates (Object)              file: Object.zip   (for
use LINKER afaict)
  Assembly Code Templates (Absolute)           file: Code.zip     (for
use with MPASM)

>>>>>>>>>>>>> Inside Object.zip :   (f628tmpo.asm)
;   This file is a basic code template for object module code         *
;   generation on the PICmicro PIC16F628. This file contains the      *
;   basic code building blocks to build upon.  As a project minimum   *
;   the 16F628.lkr file will also be required for this file to        *
;   correctly build. The .lkr files are located in the MPLAB          *
;   directory.                                                        *
;                                                                     *
;   If interrupts are not used all code presented between the         *
;   code section "INT_VECTOR and code section "MAIN" can be removed.  *

>>>>>>>>>>>>>>> Inside Code.zip :    (f628temp.asm)
;   This file is a basic code template for assembly code generation   *
;   on the PICmicro PIC16F628. This file contains the basic code      *
;   building blocks to build upon.                                    *
;                                                                     *
;   If interrupts are not used all code presented between the ORG     *
;   0x004 directive and the label main can be removed.

Herman in PHL.

2005\09\18@224024 by Chen Xiao Fan

face
flavicon
face
IMHO, you should learn how to use relocatble code first by reading
Chapter 6 o "MPASM User's Guide with MPLINK and MPLIB" from Microchip
first. MPLAB (multiple assembly files in one project and using
relocatable) is not so difficult to use once you understand that.
Olin's environment is the next step. MPASMWIN can only handle
one assmebly file (I could be wrong here) but it is able to
handle relocatable code if only one assembly file is used.

Regards,
Xiaofan

{Original Message removed}

2005\09\19@064141 by Jan-Erik Soderholm

face picon face
Chen Xiao Fan wrote :

> MPASMWIN can only handle
> one assmebly file (I could be wrong here)...

No you aren't.
But that is no different from using MPLAB.

> but it is able to
> handle relocatable code if only one assembly file is used.

Of course. And use multiple source files if you want !
(You have to run MPASM(win) once for each file, of course...)

Then run MPLINK to link all .o files together, just as MPLAB does...

Anything MPLAB does, you can do yourself by calling the
different tools (MPASM, MPLIB, MPLINK) directly.

Jan-Erik.



2005\09\19@072409 by olin piclist

face picon face
Herman Aalderink wrote:
> -- trying to follow/learn Olin's system (is Olin's an expanded MPLAB
> system?)

My development environment at http://www.embedinc.com/pic uses the MPLAB
tool suite, so everything is free.  It runs the assembler, librarian, and
linker as stand alone tools.  MPLAB itself is not needed to build.  I use it
only for debugging.


*****************************************************************
Embed Inc, embedded system specialists in Littleton Massachusetts
(978) 742-9014, http://www.embedinc.com

2005\09\19@073147 by olin piclist

face picon face
Chen Xiao Fan wrote:
> MPASMWIN can only handle
> one assmebly file (I could be wrong here) but it is able to
> handle relocatable code if only one assembly file is used.

MPASMWIN is the assembler.  It assembles one source file at a time, whether
you run it stand alone or from within MPLAB.  For a multi-file project, you
run it once for each file and pass the resulting object files to the linker.
I go a step further and use the librarian to build a library of all but the
top level object files of a project.  That way the linker only takes those
that are referenced.

For example, you can have a module used only during debugging.  If all the
references to it are removed from the production code the linker won't
include the debug module even though it's still in the build.  I do that
sort of thing sometimes with assembler switches defined at the top of the
project include file.  DEBUG = 0 means production code, and other values
might cause additional debug code to be inserted.  In the code there would
be statements like:

 if debug
     movlw   13       ;pass the error code
     gcall   led_err  ;display it
   endif


*****************************************************************
Embed Inc, embedded system specialists in Littleton Massachusetts
(978) 742-9014, http://www.embedinc.com

2005\09\19@082035 by Xiaofan Chen

face picon face
Not true!

MPLAB is more than an IDE. It also has the simulator. Moreover, it can
communucate with ICD2 which you can not use outside MPLAB (LPLAB
is not fully working yet). Quite some toold integrated into MPLAB
do not have command line interface.

One thing I do not like about Olin's environment is that it is not integrated
into MPLAB. To be fair, Microchip does not release to the interface to
let third-party tools to be integated to MPLAB. Therefore it is not
Olin's fault. It is Microchip's fault. It would be good to have
Wisp628/EasyProg integrated to MPLAB IDE. Anyway, gputils has
a plug-in for MPLAB so maybe it is still possible to develop a
plug-in based on that.

Regards,
Xiaofan

On 9/19/05, Jan-Erik Soderholm <spam_OUTjan-erik.soderholmTakeThisOuTspamtelia.com> wrote:

> Anything MPLAB does, you can do yourself by calling the
> different tools (MPASM, MPLIB, MPLINK) directly.
>
> Jan-Erik.

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