Searching \ for '[PIC]: MPLAB &' 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=mplab
Search entire site for: 'MPLAB &'.

No exact or substring matches. trying for part
PICList Thread
'MPLAB & win 95'
1996\05\22@073323 by pic

flavicon
face
I have just been trying to get the MPLAB S/W to work on
windows95. Everything seems to install correctly, but when
I run it up and try selecting 'Project\New' nothing happens.
If I load up an asm file and select 'File\SaveAs' nothing
happens.

I have installed the same zip file on a machine running win311,
and the whole thing seems to work fine.

Anyone had these problems?

Suggestions?

Wayne G Boyd.

1996\05\22@092458 by Wireless Scientific

flavicon
face
At 12:27 PM 5/22/96, pic wrote:
>I have just been trying to get the MPLAB S/W to work on
>windows95. Everything seems to install correctly, but when
>I run it up and try selecting 'Project\New' nothing happens.
>If I load up an asm file and select 'File\SaveAs' nothing
>happens.

I had the same problem and found that running MPLAB from the start menu
item was the problem. I didn't have time to figure out the fix then but I
created a shortcut to the exe and now everything works fine.

1996\05\22@093256 by Norm Cramer

flavicon
face
Yes, I had the same problem.  It is due to an "outdated" .dll file.  I think
it was the bwcc.dll.  Win3.11 doesn't have it in the system directory so it
uses the one in the mplab directory.  Win95 has it (I think) in the system
directory and uses it from there.  I copied the file to the system directory
and now mplab works fine.  BTW I am at work now (the Win3.11 machine) so I
can't verify the file name of the DLL that I copied but I think it was the
bwcc.dll file.  Someone else may be able to verify the file name.

Good luck,

Norm

At 12:27 PM 5/22/96 PDT, you wrote:
{Quote hidden}

1996\05\22@120113 by Pete Brink

picon face
Wayne,

Norm is absolutely correct.  The file's name is BWCC.DLL.  MPLAB installs this
DLL to the same directory as MPLAB.  Apparently there is something Microsoft is
not telling us.  Windows and Windows 95 are supposed to look first in the same
directory as the executable for any required DLLs.  Apparently this is not
happening.  Either there is already an old version of BWCC.DLL loaded by another
program, or Windows actually looks in the \SYSTEM directory first for BWCC.DLL.

In any case, to solve the problem, copy the BWCC.DLL file from the MPLAB
directory to the \WINDOWS\SYSTEM directory and your problems should go away.

Pete Brink


______________________________ Reply Separator _________________________________
Subject: Re: MPLAB & win 95
Author:  Norm Cramer <spam_OUTcramerTakeThisOuTspamDSEG.TI.COM> at Internet_Exchange
Date:    5/22/96 8:30 AM


Yes, I had the same problem.  It is due to an "outdated" .dll file.  I think
it was the bwcc.dll.  Win3.11 doesn't have it in the system directory so it
uses the one in the mplab directory.  Win95 has it (I think) in the system
directory and uses it from there.  I copied the file to the system directory
and now mplab works fine.  BTW I am at work now (the Win3.11 machine) so I
can't verify the file name of the DLL that I copied but I think it was the
bwcc.dll file.  Someone else may be able to verify the file name.

Good luck,

Norm

At 12:27 PM 5/22/96 PDT, you wrote:
{Quote hidden}


'MPLab & programming'
1996\06\04@092548 by Harrison Cooper
flavicon
face
So, why didn't they include the various programmers, or at least
MPstart ?  I will admit its nice to edit and assemble within the same
window now, but I still have to min the window and jump into the DOS
window to run the programmer - unless I'm missing something here.
BTW, I have yet to see any crashes running it on 3 different machines
(all 486 jobs).

1996\06\04@095416 by Mike DeMetz

flavicon
face
> So, why didn't they include the various programmers, or at least
> MPstart ?  I will admit its nice to edit and assemble within the same
> window now, but I still have to min the window and jump into the DOS
> window to run the programmer - unless I'm missing something here.
> BTW, I have yet to see any crashes running it on 3 different machines
> (all 486 jobs).
>
Someone asked if they planned to support the PICSTART and they said
no.
**********************************************************
*Mike DeMetz                      SYSCON International   *
*.....mikedKILLspamspam@spam@syscon-intl.com            South Bend, IN USA     *
*aka 73165.1230spamKILLspamcompuserve.com    using Pegasus Mail     *
**********************************************************

1996\06\04@102726 by Jattie van der Linde

flavicon
face
Harrison Cooper wrote:
>
> So, why didn't they include the various programmers, or at least
> MPstart ?  I will admit its nice to edit and assemble within the same
> window now, but I still have to min the window and jump into the DOS
> window to run the programmer - unless I'm missing something here.
> BTW, I have yet to see any crashes running it on 3 different machines
> (all 486 jobs).

The Mpstart is included. Just run it from the Icon in the same
directory.

1996\06\04@131911 by fastfwd

face
flavicon
face
Mike DeMetz <.....PICLISTKILLspamspam.....MITVMA.MIT.EDU> wrote:

> > So, why didn't they include the various programmers, or at least
> > MPstart ?  I will admit its nice to edit and assemble within the
> > same window now, but I still have to min the window and jump into
> > the DOS window to run the programmer - unless I'm missing
> > something here. BTW, I have yet to see any crashes running it on 3
> > different machines (all 486 jobs).
>
> Someone asked if they planned to support the PICSTART and they said
> no.

Guys:

MPLAB supports the Picstart Plus now, and soon will support the PRO
MATE and PRO MATE II.

-Andy

Andrew Warren - EraseMEfastfwdspam_OUTspamTakeThisOuTix.netcom.com
Fast Forward Engineering, Vista, California
http://www.geocities.com/SiliconValley/2499

'MPLab & Picstart - where ?'
1996\06\04@151116 by Harrison Cooper

flavicon
face
Andrew Warren had indicated that Picstart is supported by MPLab.
OK, I still can't find the interface.  I am running ver 3.01.00.
Is it in a newer version (yet to be released ?)  Like I said, I
may be missing something.

1996\06\04@161402 by fastfwd

face
flavicon
face
Harrison Cooper <PICLISTspamspam_OUTMITVMA.MIT.EDU> wrote:

> Andrew Warren had indicated that Picstart is supported by MPLab.

   Wait a minute... I said the Picstart PLUS was supported, not the
   old Picstart 16s.

> OK, I still can't find the interface.  I am running ver 3.01.00. Is
> it in a newer version (yet to be released ?)  Like I said, I may be
> missing something.

   You are.

   In addition to the MPLAB software which you already have, you
   need to download a file called (I think) PSPLUS.ZIP.  This file
   contains the Picstart Plus "plug-in' for MPLAB.

   -Andy

Andrew Warren - @spam@fastfwdKILLspamspamix.netcom.com
Fast Forward Engineering, Vista, California
http://www.geocities.com/SiliconValley/2499

1996\06\05@040516 by mike

flavicon
picon face
In message  <KILLspam199606042013.NAA25026KILLspamspamdfw-ix6.ix.netcom.com> RemoveMEfastfwdTakeThisOuTspamix.netcom.com
writes:
> Harrison Cooper <spamBeGonePICLISTspamBeGonespamMITVMA.MIT.EDU> wrote:
>
> > Andrew Warren had indicated that Picstart is supported by MPLab.
>
>     Wait a minute... I said the Picstart PLUS was supported, not the
>     old Picstart 16s.
>
Is there a good reason why the "old" picstart 16s are not supported?
There is a lot of them out there.

What about the 3rd party programmers, are (m)any of them supported?


Mike Watson


'MPLAB & 16C62'
1996\10\04@112851 by Brian Aase
flavicon
face
A few weeks ago I developed a short program which I
intended to run on a 16C62.  But since I didn't have one
available at the time, I used a 16C64 instead and
everything turned out perfectly.

Now that I have finally acquired some 16C62 samples,
I modified the code by changing the List & Include
directives and deleting the init statements for Port D
and Port E (which were never used anyway).  Seems
like a simple excercise, no?

The problem is, MPLAB and Picstart+ don't seem to
program the 16C62 correctly.  Running Blank Check
after programming seems to indicate that the config & ID
bits were programmed, but the main program space was
not.  (When I run Blank Check on a 16C64, it DOES say
that program memory is not blank, as I would expect.)

Can anyone suggest what I might have missed here?

'MPLAB & PICMASTER Emulator'
1996\10\09@141624 by Mark Jurras

flavicon
face
How come when I assemble using BUILD ALL (CTRL F10) sometimes the HEX file
automatically updates the emulator memory and other times I have to do a
FILE-->IMPORT-->DOWNLOAD TO MEMORY to update the emulator???

It always works correctly when I start MPLAB and compile the first time.
After that it is a gamble. If I close MPLAB and restart same thing.

- -Mark

'MPLAB & PICSTART PLUS'
1996\10\17@025858 by tjaart

flavicon
face
I saw on the MNicrochip's web page that you shouldn't delete your old
version of MPLAB before installing 3.10.01 They've even kept the
previous version so you can install PICSTART PLUS and THEN upgrade to
MPLAB 3.10.01

--
Friendly Regards

Tjaart van der Walt
________________________________________________________________
R&D Engineer       | GSM vehicle tracking and datacomm solutions
WASP International | +27-(0)11-622-8686 | http://wasp.co.za

1996\10\17@130516 by Darrel Johansen

picon face
MPLAB v3.10.03 (the latest version on Microchip's web page and BBS) will
install MPLAB software, then look in your installing directory for the
older version of the PICSTART Plus driver, called MPPLUS.DLL and ask if
you want to install the new PICSTART Plus software.

If you have deleted your older files before installing, copy any file
into the directory where MPLAB will be installed and rename it
MPPLUS.DLL.  Then MPLAB v3.10.03 will see the file and let you install
PICSTART Plus software, too.

The new PICSTART Plus software offers no new features, but it must be
used with MPLAB v3.10.03.  New PICSTART Plus firmware, however, does add
support for some new processors.  New firmware does not have to be
installed unless you want to program these newer devices.  See the
README.PLS text file for more information.  You'll need a blank 17C44 to
upgrade the firmware.

Darrel Johansen
TakeThisOuTdarrel.johansenEraseMEspamspam_OUTmicrochip.com


'MPLAB & XORing'
1997\12\22@193719 by Philip Martin
flavicon
picon face
Taa for the replies to the MPLAB question. I also RTFM and found the way
to alter the INTCON bit to force the interrupt.

Next, Ohhh what a night:

Take this snipet-
       movf    rmax,w          ; load w with max time count
       xorwf   r1,f
       btfsc   _z              ; has the max time been reached

What I want to do is compare the value in rmax (value increasing each
interrupt) with a fixed value in r1, read in at the beginning of the
program from some BCD switches.

What I've realised is that the result of the XOR is then placed in r1,
overwriting the original data. My thinking now is to first transfer the
data from r1 to w and on to a temporary register and then test the
match. This would however mean doing this every pass (and in quite a few
locations).

Is this the best way of preserving the data in r1, or is there a better
way?

TIA,

--
Philip Martin   ----------------------------------------------------------------
Royal Quays             If at first you don't succeed, try again. Then quit:
North Shields.          no use being a damn fool about it !
                                                       W.C. Fields
email RemoveMEphilipspamTakeThisOuTphilmart.demon.co.uk

1997\12\22@201102 by Mark Thatcher

flavicon
face
part 0 1443 bytes
       movwf   rmax,w
       xorwf   r1,w            ; do the xor, but put result in W
       btfsc   _z

Mark

----------
From:   Philip Martin
Sent:   Tuesday, 23 December 1997 8:25
To:     PICLISTEraseMEspam.....MITVMA.MIT.EDU
Subject:        MPLAB & XORing

Taa for the replies to the MPLAB question. I also RTFM and found the way
to alter the INTCON bit to force the interrupt.

Next, Ohhh what a night:

Take this snipet-
       movf    rmax,w          ; load w with max time count
       xorwf   r1,f
       btfsc   _z              ; has the max time been reached

What I want to do is compare the value in rmax (value increasing each
interrupt) with a fixed value in r1, read in at the beginning of the
program from some BCD switches.

What I've realised is that the result of the XOR is then placed in r1,
overwriting the original data. My thinking now is to first transfer the
data from r1 to w and on to a temporary register and then test the
match. This would however mean doing this every pass (and in quite a few
locations).

Is this the best way of preserving the data in r1, or is there a better
way?

TIA,

--
Philip Martin   ----------------------------------------------------------------
Royal Quays             If at first you don't succeed, try again. Then quit:
North Shields.          no use being a damn fool about it !
                                                       W.C. Fields
email EraseMEphilipspamphilmart.demon.co.uk

1997\12\22@204046 by Harold Hallikainen

picon face
On Tue, 23 Dec 1997 00:25:09 +0000 Philip Martin
<RemoveMEphilipEraseMEspamEraseMEPHILMART.DEMON.CO.UK> writes:
{Quote hidden}

       How about just setting the destination of the XOR to w instead of
file?  this destroys w, but leaves your memory fine.

>        movf    rmax,w          ; load w with max time count
>        xorwf   r1,0           ; Set Z if equal, destroys W,
maintains r1
>        btfsc   _z              ; has the max time been reached
>


Harold

1997\12\22@210034 by Dmitry Kiryashov

flavicon
face
Harold Hallikainen wrote:

> >What I want to do is compare the value in rmax (value increasing each
> >interrupt) with a fixed value in r1, read in at the beginning of the
> >program from some BCD switches.
> >
>         How about just setting the destination of the XOR to w instead of
> file?  this destroys w, but leaves your memory fine.
>
> >        movf    rmax,w          ; load w with max time count
> >        xorwf   r1,0           ; Set Z if equal, destroys W, maintains r1
> >        btfsc   _z              ; has the max time been reached

This will not destroy W because easy to do the same XORWF again and
restore W ;)

WBR Dmitry.
PS.
       movfw   A
       addwf   B,w
       xorwf   C,w
       skpnz
       ...             ;probably GOTO or CALL command

       xorwf   C,w     ;restore A+B in W
       ...

1997\12\23@113315 by Justin Crooks

flavicon
face
How about:
       movf    rmax,W
       xorwf   r1,F
       skpz
       .set flag...
       xorwf   r1,F

Xor a register twice with same W and, voila, the original data is back.

       I don't see any reason to xor though...
       Why not just:

       movf    rmax,w
       subwf   r1,W
       skpnz

       ???

----------
{Quote hidden}

----------------------------------------------------------------
> Royal Quays             If at first you don't succeed, try again. Then
quit:
> North Shields.          no use being a damn fool about it !
>                                                         W.C. Fields
> email EraseMEphilipspamspamspamBeGonephilmart.demon.co.uk

1997\12\23@195334 by Philip Martin

flavicon
picon face
In article <RemoveME19971223163252822.AAA2047KILLspamspamCOD-CAP-2.WYOMING.COM>, Justin
Crooks <jcrooksSTOPspamspamspam_OUTWYOMING.COM> writes
>How about:
>        movf    rmax,W
>        xorwf   r1,F
>        skpz
>        .set flag...
>        xorwf   r1,F
>
>Xor a register twice with same W and, voila, the original data is back.
>
>        I don't see any reason to xor though...
>        Why not just:
>
>        movf    rmax,w
>        subwf   r1,W
>        skpnz
>
>        ???
Errr, cos i didn't think of doing it that way.

BTW, is there any difference in code efficiency by doing it by
subtraction rather than xor?

--
Philip Martin   ----------------------------------------------------------------
Royal Quays             If at first you don't succeed, try again. Then quit:
North Shields.          no use being a damn fool about it !
                                                       W.C. Fields
email spamBeGonephilipSTOPspamspamEraseMEphilmart.demon.co.uk

1997\12\24@112507 by Justin Crooks

flavicon
face
Essentially the only difference is the "leftovers" in W, and you save an
instruction.  If you don't need the XOR result, subwf is simpler.  It can
also be used as a greater than/less than check (the C flag in the status
register).

----------
{Quote hidden}

----------------------------------------------------------------
> Royal Quays             If at first you don't succeed, try again. Then
quit:
> North Shields.          no use being a damn fool about it !
>                                                         W.C. Fields
> email .....philipspam_OUTspamphilmart.demon.co.uk


'Generating sequential serial-numbers using MPLAB &'
1999\06\30@100612 by Caisson
flavicon
face
Hello all,

 I've got a problem.  I'm creating program for a couple (100+) of devices.
Those devices will be working in a cluster.  A PC will be used to
communicate with them.   But ...  I have to adress all those devices
one-by-one.   That means they will need unique adresses.

That's not really a problem,  cause I can : Set an ID-value, assemble the
program, burn a controller, change the ID-value, assemble the program, burn
the next controller, and-so-on.

If that's how it must be done, that's the way I'll do it.  But when there
is another way (like using an Auto-increment counter), I sure would like to
know :-)

So, if someone knows how to make my life easier, please let me know.

Greetz,
 Rudy Wieser

1999\06\30@172042 by Mark Willis

flavicon
face
Caisson wrote:
> <snipped>
> If that's how it must be done, that's the way I'll do it.  But when there
> is another way (like using an Auto-increment counter), I sure would like to
> know :-)
>
> So, if someone knows how to make my life easier, please let me know.
>
> Greetz,
>   Rudy Wieser

 Alternate methods that come to me just now:

 Each PIC could have a 24C01 attached, drop the ID value in the C01 &
read it in on startup.

 A PISO shift register set could load a bunch of jumpers/dip
switches/broken PCB traces, at startup time.

 A Dallas I-Button could load the I-Button's serial number in at
startup.  (I still wish PICs had a serial number, some times.)

 Cheapest is probably the most labor intensive, which you've mentioned.

 Mark


'Generating sequential serial-numbers using MPLAB &'
1999\07\01@093453 by Adam Davis
flavicon
face
(Note:  I haven't been receiving my own posts from the piclist, though I assume
they're getting through, since I've had a reply from two or three...  Is this
problem typical to the list and being resolved, or is it just me?)

Anyway...

Once you assemble the program, identify the bytes in the hex file which change
when you change the ID.  Then set up a small program (could be basic, C,
whatever.  You might even use grep to search and replace it) and put it in a
batch file which automates the entire thing for you.

start
Modify file
Prompt for new chip
program chip
Goto start

I hope this helps, and good luck!

-Adam

Caisson wrote:
{Quote hidden}

1999\07\01@095400 by Octavio Nogueira

flavicon
face
> Caisson wrote:
> > <snipped>
> > If that's how it must be done, that's the way I'll do it.  But when
there
> > is another way (like using an Auto-increment counter), I sure would like
to
> > know :-)
> >
> > So, if someone knows how to make my life easier, please let me know.
> >

I don't know about PicStart Plus but you can generate the serial
number with ProPic 2 programmer, you can specify the start address,
the size and the increment of the serial number.

                         /"\
Friendly Regards          \ /
                          X  ASCII RIBBON CAMPAIGN
Octavio Nogueira          / \ AGAINST HTML MAIL
===================================================
TakeThisOuTnogueira.....spamTakeThisOuTpropic2.com                  ICQ# 19841898
>From the creator of ProPic, ProPic 2 now much better
New ProPic 2  homepage:      http://www.propic2.com
PIC Programmer for Windows with down to earth price
===================================================

1999\07\01@180453 by Eric Oliver

flavicon
face
On Thursday, July 01, 1999 8:48 AM, Adam Davis [SMTP:TakeThisOuTadavisKILLspamspamspamBALADYNE.COM]
wrote:
> (Note:  I haven't been receiving my own posts from the piclist, though I
assume
> they're getting through, since I've had a reply from two or three...  Is
this
> problem typical to the list and being resolved, or is it just me?)

Although there was talk of changing this, I think the PICLIST defaults to
not copying you with your own message. There is a way to change it ... I
think the instructions are included in the original sign-on message you
should have received.  Tjaart has a PICLIST FAQ I think .. unfortuantely I
can't find the link .. Tjaart ?

Eric

1999\07\02@063522 by Caisson

flavicon
face
> Van: Adam Davis <.....adavisspamRemoveMEBALADYNE.COM>
> Aan: RemoveMEPICLISTspamspamBeGoneMITVMA.MIT.EDU
> Onderwerp: Re: Generating sequential serial-numbers using MPLAB &
Picstart+-An Auto-increment counter ?
> Datum: donderdag 1 juli 1999 15:47

Hello Adam,

> (Note:  I haven't been receiving my own posts from the piclist, though I
assume
> they're getting through, since I've had a reply from two or three...  Is
this
> problem typical to the list and being resolved, or is it just me?)

This is no problem, it's just the (old) default.  You can ask the server to
send you a copy of your own messages (as will be de new default).  How ?
I'm not sure anymore, but you can ask the server to send you a list of
commands. The way to do it is described in your "Hello, nice you joined"
message.

> Anyway...
>
> Once you assemble the program, identify the bytes in the hex file which
change
> when you change the ID.  Then set up a small program (could be basic, C,
> whatever.  You might even use grep to search and replace it) and put it
in a
> batch file which automates the entire thing for you.

Right, that's what I thought of too.  But because of the fact that the
PICSTART+ only works with MPLAB, I would be forced to : Program a chip,
call the routine that modifies my HEX-file, reload the project (making sure
the last version of the HEX-file will be used when programming the next
chip), and start programming again.  It's allmost the same bore as manually
changing the Source-file, assemble it, and program a chip ... :-(  Ah well,
To bad that there is no counter available for this purpose.

Greetz,
 Rudy Wieser

1999\07\02@080721 by Peter van Hoof

picon face
<x-flowed>This may not be that easy not only will the byte change, the checksum
calculated from this byte changes as well!

It will require some knowledge about the hexfile and some programming

Peter spamBeGonepvh@spam@spamspam_OUTvertonet.com



{Quote hidden}

_______________________________________________________________
Get Free Email and Do More On The Web. Visit http://www.msn.com

</x-flowed>

1999\07\02@104730 by Adam Davis

flavicon
face
Yes, this list defaults to not sending you your own messages.  I should have
checked with the list server before sending that message.

For those needing to change this, send the following in the body of a message:

set piclist rep

to: @spam@LISTSERVRemoveMEspamEraseMEMITVMA.MIT.EDU

It will send you confirmation email, to which you reply 'ok' as you did when you
signed up for the list.

Thanks to everyone who helped!

-Adam

Eric Oliver wrote:
{Quote hidden}


'[PIC]: MPLAB & ICD & Code protection bug'
2000\07\17@023718 by Robert Rolf
picon face
I'm still doing battle with ICD and my 16F876's.
I managed to get one to erase, but not the other.
I -think- the permutation that worked was to NOT have 'Erase before
program' set, but ALL other sections had to be on, and the full
address range (0-1fff) had to be specified. Has anyone here ever
reused a 'code protected' 16F8xx device with ICD? My one success doesn't
count and at the moment I can't afford the time to debug the ICD
to see if I can undo CP again. I'm already 4 days late on delivery of
a 'patch' because of this.

Someone mentioned that the ICD firmware -will- do a uncodeprotect,
but I'd like to see the disassembly to know the EXACT
conditions that are required to trigger this command.

What REALLY bugs me, is that the ICD 'erase' command ALWAYS
reports 'PASS', even though the device IS NOT IN FACT ERASED!!
It doesn't matter what section is 'erased', it is always 'passed'
and of course, WRONG!. What's the point of the 'erase' button
if it doesn't work as expected?

And the config register reads back as all zeros once CP is on.

Nothing quite as frustrating as having tools that don't 'quite'
work.

Robert

--
http://www.piclist.com hint: PICList Posts must start with ONE topic:
[PIC]: PIC only [EE]: engineering [OT]: off topic [AD]: advertisements


'[PIC]: MPLAB & PICstart pokin EEPROM locations?'
2001\01\17@185847 by Hardware Engineering
picon face
ok...still working on getting the EEPROM writes/reads to work (either hangs or
just does not work...)?

Is it possible to poke values to the EEPROM locations using MPLAB and
PICstart?

that way...at least I can test the read function if I know the values in the
EEPROM

____________________________________________________________________
Get free email and a permanent address at http://www.netaddress.com/?N=1

--
http://www.piclist.com hint: PICList Posts must start with ONE topic:
[PIC]:,[SX]:,[AVR]: ->uP ONLY! [EE]:,[OT]: ->Other [BUY]:,[AD]: ->Ads


2001\01\17@192924 by Mark Samuels

flavicon
face
in MPLAB, you can use the Window > Modify menu to fill specified EEPROM
locations with data.
Then, once you enable the Picstart Plus, instead of hitting the program
button in the programmer window, select the
Picstart Plus > Program/Verify menu, which will allow you to deselect
everything except the EEPROM locations to be programmed.

If you want to have initial values loaded into the EEPROM on a device each
time you program a new part with code,
check the programming specification data sheet for the particular device
you're using...
the EEPROM initial values can be written as data in your assembly code,
starting at a particular memory address.
For example, the 16F873,874,876,877 start EEPROM memory at location 0x2100.
Once this data is in your code, you can program the EEPROM at the same time
you program the device with your code.


At 04:59 PM 1/17/01 -0700, you wrote:
{Quote hidden}

-------------------------------------------
Mark Samuels
ARMA Design
Tel:(858) 549-2531
Fax:(858) 549-2594
Email: @spam@markspam_OUTspam.....armanet.com
Web: http://www.armanet.com



The information contained in this electronic message is private and may
contain privileged, confidential or inside information.  Any distribution,
copying or forwarding or use of this communication by anyone other than the
intended recipient(s) is strictly prohibited and may be unlawful.

--
http://www.piclist.com hint: PICList Posts must start with ONE topic:
[PIC]:,[SX]:,[AVR]: ->uP ONLY! [EE]:,[OT]: ->Other [BUY]:,[AD]: ->Ads


2001\01\17@203243 by Drew Vassallo

picon face
>in MPLAB, you can use the Window > Modify menu to fill specified EEPROM
>locations with data.
>Then, once you enable the Picstart Plus, instead of hitting the program
>button in the programmer window, select the
>Picstart Plus > Program/Verify menu, which will allow you to deselect
>everything except the EEPROM locations to be programmed.

You can also go to Window->EEPROM Memory to display the contents of the
EEPROM.  It dynamically updates during program operation  so you can see
what's happening.  Also, you should open a watch window for EECON1 and
EECON2 along with EEDATA and EEADR.

>At 04:59 PM 1/17/01 -0700, you wrote:
>>ok...still working on getting the EEPROM writes/reads to work (either
>>hangs or
>>just does not work...)?

STILL??  Start from scratch.  Something may be wrong fundamentally that
you're not catching because you're bleary-eyed from re-re-re-reading the
routine.  Use the datasheets and our code snippets to build a new routine.
Believe me, this works.

--Andrew
_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com

--
http://www.piclist.com hint: PICList Posts must start with ONE topic:
[PIC]:,[SX]:,[AVR]: ->uP ONLY! [EE]:,[OT]: ->Other [BUY]:,[AD]: ->Ads



'[PIC]: MPLAB & MPLINK Build Scripts'
2001\08\24@112713 by Ross Russell
picon face
Does anybody run MPLAB & MPLINK builds from
a DOS .bat file?  I need to automate my build
process, and can't seem to get past the console
that needs a keystroke to move from one .asm
file to the next.

Thanks,
hooch

_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp

--
http://www.piclist.com hint: To leave the PICList
spamBeGonepiclist-unsubscribe-requestEraseMEspammitvma.mit.edu


2001\08\24@150806 by Olin Lathrop

face picon face
> Does anybody run MPLAB & MPLINK builds from
> a DOS .bat file?  I need to automate my build
> process, and can't seem to get past the console
> that needs a keystroke to move from one .asm
> file to the next.

I run MPASMWIN, the librarian, and the linker, from scripts and automated
build tools all the time.  They work fine from BAT files on 32 bit Windows
systems, but I have never tried the DOS executables.  Why not run the
Windows executables from BAT files on Windows?


********************************************************************
Olin Lathrop, embedded systems consultant in Littleton Massachusetts
(978) 742-9014, olinspamBeGonespamembedinc.com, http://www.embedinc.com

--
http://www.piclist.com hint: To leave the PICList
RemoveMEpiclist-unsubscribe-request@spam@spamspamBeGonemitvma.mit.edu


2001\08\25@062913 by Peter L. Peres

picon face
> batch

Try to use MPASM instead. This works from C/L. There are some utilities
that simulate a keypress. Work under DOS don't know about Windows keyboard
buffers and such.

Peter

--
http://www.piclist.com hint: PICList Posts must start with ONE topic:
[PIC]:,[SX]:,[AVR]: ->uP ONLY! [EE]:,[OT]: ->Other [BUY]:,[AD]: ->Ads



'[PICLIST] [PIC] - MPLAB & Win2000 ECP Services'
2001\10\24@123728 by Andy David
flavicon
face
Guys,

I'm having a problem with a new PC running Windows 2000.

I use a FlexBDM JTAG cable to develop for (ahem!) a Mot. HC12. It's a
parallel port jtag interface, and it's been working fine on my PC.

After installing MPLAB this morning with the MPLAB-ICE option ticked, my
flex refused to work.

I tried reinstalling flex and it's NT driver, but that didn't fix the
problem so I reverted to a previous Ghost image and flex worked again. Up
until this point I hadn't considered that the MPLAB installation had caused
the problem -- the flex failure occurred immediately after installing an
Intellimouse driver -- so I duly installed MPLAB (again, with the MPLAB-ICE
option ticked), Flex then stopped working again, absolutely identical to the
first time.

The error reported by flex is that it is unable to program clock synch due
to comms failure. The last message in the event log before the flex failure
event message is a message from the mplabice service that it has
reconfigured my ECP port -- as this is the same port that flex uses, this
looks like the cause of the error. I cannot, however, find a way of fixing
the error.

I'd like to fix this without reverting again to the Ghost image if possible.
Any suggestions? (yeah, yeah, don't use Win 2k, I know...)




Regards,

- Andy.
---------------------------------------------
Andrew David, Software Manager, Ultronics Ltd
http://www.Ultronics.com


_____________________________________________________________________
This message has been checked for all known viruses by Star Internet
delivered through the MessageLabs Virus Scanning Service. For further
information visit http://www.star.net.uk/stats.asp or alternatively call
Star Internet for details on the Virus Scanning Service.

--
http://www.piclist.com hint: PICList Posts must start with ONE topic:
[PIC]:,[SX]:,[AVR]: ->uP ONLY! [EE]:,[OT]: ->Other [BUY]:,[AD]: ->Ads


2001\10\24@133406 by Gerhard Fiedler

flavicon
face
At 17:25 10/24/2001 +0100, Andy David wrote:
>The error reported by flex is that it is unable to program clock synch due
>to comms failure. The last message in the event log before the flex failure
>event message is a message from the mplabice service that it has
>reconfigured my ECP port -- as this is the same port that flex uses, this
>looks like the cause of the error. I cannot, however, find a way of fixing
>the error.
>
>I'd like to fix this without reverting again to the Ghost image if possible.
>Any suggestions?

I don't know what flex or MPLAB-ICE need from this port, but usually you
can set the properties manually either in the Device Manager or in the BIOS.

If you can't figure it out at all, and if you don't need the parallel port
for MPLAB (don't know their ICE), you can try to go back to your image and
install MPLAB as a user without admin priviledges. This should prevent
MPLAB from modifying any system settings.

Another helpful tool is Inctrl (version 5) from PCMagazine. It lets you
track all the modifications an application does during install. You then
know what has been done and should be able to undo whatever is a problem
for flex.

>(yeah, yeah, don't use Win 2k, I know...)

For me the best Windows ever... :)

ge

--
http://www.piclist.com hint: PICList Posts must start with ONE topic:
[PIC]:,[SX]:,[AVR]: ->uP ONLY! [EE]:,[OT]: ->Other [BUY]:,[AD]: ->Ads


2001\10\24@215111 by Bob Ammerman

picon face
Set the MPLABICE service to start manually.

Bob Ammerman
RAm System

----- Original Message -----
From: "Andy David" <.....akdavid@spam@spamEraseMEULTRONICS.CO.UK>
To: <.....PICLISTRemoveMEspamMITVMA.MIT.EDU>
Sent: Wednesday, October 24, 2001 9:25 AM
Subject: [PIC] - MPLAB & Win2000 ECP Services


{Quote hidden}

caused
> the problem -- the flex failure occurred immediately after installing an
> Intellimouse driver -- so I duly installed MPLAB (again, with the
MPLAB-ICE
> option ticked), Flex then stopped working again, absolutely identical to
the
> first time.
>
> The error reported by flex is that it is unable to program clock synch due
> to comms failure. The last message in the event log before the flex
failure
> event message is a message from the mplabice service that it has
> reconfigured my ECP port -- as this is the same port that flex uses, this
> looks like the cause of the error. I cannot, however, find a way of fixing
> the error.
>
> I'd like to fix this without reverting again to the Ghost image if
possible.
{Quote hidden}

--
http://www.piclist.com hint: PICList Posts must start with ONE topic:
[PIC]:,[SX]:,[AVR]: ->uP ONLY! [EE]:,[OT]: ->Other [BUY]:,[AD]: ->Ads


2001\10\25@085409 by Andy David

flavicon
face
Ned, Bob & Gerhard,

thanks for the suggestions, guys. I don't have the option of adding a second
serial port (I use a laptop) and I can't find the mplabice service -- I've
looked under Start->Control_Panel->Admin_Tools->Services and I can't find
mplabice service listed.

Think I'll go back to my image...


Regards,

- Andy.
---------------------------------------------
Andrew David, Software Manager, Ultronics Ltd
http://www.Ultronics.com



_____________________________________________________________________
This message has been checked for all known viruses by Star Internet
delivered through the MessageLabs Virus Scanning Service. For further
information visit http://www.star.net.uk/stats.asp or alternatively call
Star Internet for details on the Virus Scanning Service.

--
http://www.piclist.com hint: The list server can filter out subtopics
(like ads or off topics) for you. See http://www.piclist.com/#topics


2001\10\25@115043 by Gerhard Fiedler

flavicon
face
At 13:39 10/25/2001 +0100, Andy David wrote:
>I don't have the option of adding a second
>serial port (I use a laptop)

Unluckily I can't help you with the MPLAB service -- I don't use the ICE my
self. But I use USB serial ports with my notebook for quite some time
(almost) without problems.

ge

--
http://www.piclist.com hint: The list server can filter out subtopics
(like ads or off topics) for you. See http://www.piclist.com/#topics


2001\10\25@121137 by Andy David

flavicon
face
I found the problem this afternoon -- bad parallel cable. It surprised me,
I'd tried it on 2 other laptops, both worked perfectly so I didn't suspect
the hardware. Still, live & learn.

Thanks,



- Andy.
---------------------------------------------
Andrew David, Software Manager, Ultronics Ltd
http://www.Ultronics.com



_____________________________________________________________________
This message has been checked for all known viruses by Star Internet
delivered through the MessageLabs Virus Scanning Service. For further
information visit http://www.star.net.uk/stats.asp or alternatively call
Star Internet for details on the Virus Scanning Service.

--
http://www.piclist.com hint: The list server can filter out subtopics
(like ads or off topics) for you. See http://www.piclist.com/#topics



'[PIC]: MPLAB & LINUX'
2001\12\10@124021 by Mike Blakey
flavicon
face
Does anyone know if there are plans to port/run MPLAB on LINUX.



********************************************************************
This email and any attachments are confidential to the intended
recipient and may also be privileged. If you are not the intended
recipient please delete it from your system and notify the sender.
You should not copy it or use it for any purpose nor disclose or
distribute its contents to any other person.
********************************************************************

--
http://www.piclist.com hint: The PICList is archived three different
ways.  See http://www.piclist.com/#archives for details.


2001\12\10@152644 by Harold M Hallikainen

picon face
Will it run under WINE?

Harold

On Mon, 10 Dec 2001 17:03:10 +0000 Mike Blakey
<.....mike.blakeySTOPspamspam@spam@BAESYSTEMS.COM> writes:
> Does anyone know if there are plans to port/run MPLAB on LINUX.
>
>

FCC Rules Online at http://hallikainen.com/FccRules
Lighting control for theatre and television at http://www.dovesystems.com

________________________________________________________________
GET INTERNET ACCESS FROM JUNO!
Juno offers FREE or PREMIUM Internet access for less!
Join Juno today!  For your FREE software, visit:
dl.http://www.juno.com/get/web/.

--
http://www.piclist.com hint: The PICList is archived three different
ways.  See http://www.piclist.com/#archives for details.


2001\12\10@160706 by Jeff DeMaagd

flavicon
face
At 05:03 PM 12/10/01 +0000, you wrote:
>Does anyone know if there are plans to port/run MPLAB on LINUX.

Heck, they are so far behind they haven't even released a Win32 MPLAB!

As the other poster suggested, try WINE and let us know how it works.  I
think you could also check what the gnupic group has so far.

Jeff

--
http://www.piclist.com hint: The PICList is archived three different
ways.  See http://www.piclist.com/#archives for details.


2001\12\10@161310 by jay

flavicon
face
On Mon, 2001-12-10 at 15:03, Jeff DeMaagd wrote:
> At 05:03 PM 12/10/01 +0000, you wrote:
> >Does anyone know if there are plans to port/run MPLAB on LINUX.
>
> Heck, they are so far behind they haven't even released a Win32 MPLAB!
>
> As the other poster suggested, try WINE and let us know how it works.  I
> think you could also check what the gnupic group has so far.
>
> Jeff
I've had success running Forest Electronic Developments PIC-C under
WINE.  I was amazed it actually worked pretty good!
Jason Mielke
jmielkeEraseMEspam@spam@linuxforbroadcasters.com
http://www.linuxforbroadcasters.com

--
http://www.piclist.com hint: The PICList is archived three different
ways.  See http://www.piclist.com/#archives for details.


2001\12\10@162554 by Wesley Moore

flavicon
picon face
MPLAB runs under Linux using the WINE windows emulator. I did not test all
features but it will compile PIC code successfully. I have a screen shot of it
in action at:
http://yallara.cs.rmit.edu.au/~wmoore/images/linux/winemplab.png

Wesley

On Mon, Dec 10, 2001 at 05:03:10PM +0000, Mike Blakey wrote:
> Does anyone know if there are plans to port/run MPLAB on LINUX.
>
--
Wesley Moore      http://yallara.cs.rmit.edu.au/~wmoore/
RMIT - BEng (Comp Sys Eng)/BApp.Sc. (Comp Sci)  3rd Year

--
http://www.piclist.com hint: The PICList is archived three different
ways.  See http://www.piclist.com/#archives for details.



'MPLAB & 12C509'
2003\01\07@190535 by David Duffy
flavicon
face
MPLAB 6 doesn't seem to support the 12C509 so I tried
to use MPLAB 5.5 instead but it is unstable with the new
PicStart+ firmware. I keep getting comms errors,etc.
A look on the Microchip site hasn't turned up anything yet
so does anyone have any idea's on this? I could re-burn
the older firmware back into the PicStart+ but that's a lot
of juggling as I only have one JW 17C42 to do it with along
with the original OTP that it came with.
David...
___________________________________________
David Duffy        Audio Visual Devices P/L
U8, 9-11 Trade St, Cleveland 4163 Australia
Ph: +61 7 38210362   Fax: +61 7 38210281
New Web: http://www.audiovisualdevices.com.au
___________________________________________

--
http://www.piclist.com hint: PICList Posts must start with ONE topic:
[PIC]:,[SX]:,[AVR]: ->uP ONLY! [EE]:,[OT]: ->Other [BUY]:,[AD]: ->Ads

2003\01\07@193027 by Spehro Pefhany

picon face
At 10:08 AM 1/8/03 +1000, you wrote:
>MPLAB 6 doesn't seem to support the 12C509 so I tried
>to use MPLAB 5.5 instead but it is unstable with the new
>PicStart+ firmware. I keep getting comms errors,etc.
>A look on the Microchip site hasn't turned up anything yet
>so does anyone have any idea's on this? I could re-burn
>the older firmware back into the PicStart+ but that's a lot
>of juggling as I only have one JW 17C42 to do it with along
>with the original OTP that it came with.

I've seen nothing of the kind using both MPLAB 5.70.40 and
MPLAB 6.10.0.0 with firmware Version 3.10.0. Rock-solid,
on the older parts.

Best regards,

Spehro Pefhany --"it's the network..."            "The Journey is the reward"
RemoveMEspeffspamspamBeGoneinterlog.com             Info for manufacturers: http://www.trexon.com
Embedded software/hardware/analog  Info for designers:  http://www.speff.com

--
http://www.piclist.com hint: PICList Posts must start with ONE topic:
[PIC]:,[SX]:,[AVR]: ->uP ONLY! [EE]:,[OT]: ->Other [BUY]:,[AD]: ->Ads

2003\01\08@114510 by Mike Mansheim

flavicon
face
David Duffy wrote:
> PicStart+ firmware. I keep getting comms errors,etc.

I had communication problems that were fixed by changing two serial port
settings (win98 setup):
- "hardware" flow control
- in the advanced section, make sure the "Use FIFO..." box is NOT checked

--
http://www.piclist.com hint: The list server can filter out subtopics
(like ads or off topics) for you. See http://www.piclist.com/#topics

2003\01\09@171446 by David Duffy

flavicon
face
MPLAB 6 doesn't seem to support the 12C509 so I tried
to use MPLAB 5.5 instead but it is unstable with the new
PicStart+ firmware. I keep getting comms errors,etc.
A look on the Microchip site hasn't turned up anything yet
so does anyone have any idea's on this? I could re-burn
the older firmware back into the PicStart+ but that's a lot
of juggling as I only have one JW 17C42 to do it with along
with the original OTP that it came with.
David...
___________________________________________
David Duffy        Audio Visual Devices P/L
U8, 9-11 Trade St, Cleveland 4163 Australia
Ph: +61 7 38210362   Fax: +61 7 38210281
New Web: http://www.audiovisualdevices.com.au
___________________________________________

--
http://www.piclist.com hint: The PICList is archived three different
ways.  See http://www.piclist.com/#archives for details.


'[PIC:] MPLAB & PICCLite question'
2003\11\10@193253 by 1zlx0fc02
picon face
Sorry if this is a repeat post. I got some bounce messages from the list server and I
don't think my post survived.

Hi:

I'd like to be able to call C code from asm and vice versa.

I got an asm file from PICCLite to check the calling convention and compiled it to an
object file in PICCLite. I changed the .obj extension to .o for MPLINK.

MPLINK reported that it was not a valid COFF format so I used one of PICCLite's
tools to convert the .obj to a COFF file and MPLINK reported that it couldn't read the
header.

Does anyone know how to get these two development systems to play nice? I see
other posts regarding PICCLite so maybe someone has played with this and can
help. I'd appreciate it much.

Thanks in advance,
Miike

--
http://www.piclist.com hint: The PICList is archived three different
ways.  See http://www.piclist.com/#archives for details.


'[PIC] MPLAB & ICD1'
2005\04\30@174212 by Robert Rolf
picon face
Olin Lathrop wrote:
> Robert Rolf wrote:
>
>>They obsoleted the ICD1 for no apparent reason.
>
> You mean other than it's obsolete?

There is no good reason to abandon products when the ONLY
requirement to keep them useful is a firmware update.

>>They dynamically change the firmware in the ICD2 when chosen chip
>>family or mode (debug/program) is changed, so there is no reason why
>>they couldn't do the same thing for the ICD1 if they really needed to.
>
> There may well be a good reason.  The ICD1 is very old.  It's quite
> possible, even likely, that it doesn't have a flash part inside.

The earliest version's didn't. The newer versions did.
16F876 instead of a '73.

MPLAB 5.x supported an 'update firmware' command. Trivial to
burn the new code into a new flash chip and upgrade your old ICD1.
Eventually they came out with a firmware version that allowed
16F87xA parts to be programmed as non A parts. They could have
also upgraded MPLAB to support the new algorithms for the newer
parts.

>  If I
> remember right, it's at least as old as the Picstart+ which used a 17C44
> inside.

It did. Took me all of 5 minutes to upgrade to the flashable version.

>>How many thousands of ICD1's were obsoleted when MPLAB 6 came out?
>  
> None, because nobody took away MPLAB 5.  The old versions of MPLAB and the
> ICD1 continue to do everything they previously did.

True. But they could ALSO have fully supported the newer -A series chips
with the ICD1 since the only significant change was the
programming algorithm. MPLAB 6 & 7 COULD have continued to support
ICD1 if they had wanted to. I doubt that the command stream is
that different from the ICD2.

I'll say it again. ICSP is ICSP. 4 wires banged appropriately.
It's not THAT hard to update the ICD1 firmware/software to make it
REMAIN useful with the newest chips. The ICD2 clones out there
show that the hardware is substatially the same except for the
USB<->serial convertor and the switchable circuit power mode.

>  Microchip made a
> decision that the ICD1 wasn't up to the task of handling the newer chips,

On what basis do you make this claim? ICSP is ICSP....
The ICD1 is a nice little programmer and COULD have had a much longer
life if Microchip had wanted it to.

> and USB capability was long overdue anyway.

And which is implemented with a USB to serial chip internally
so there is no great speed advantage.

As I understand it, ICD1 was not designed/ manufactured by Microchip.
The ICD2 is, and occupies 3 times the desk area. Politics over engineering,
as usual.

>>Unfortunately their simulator does NOT emulate serial ports
> It was my understanding it did, although I haven't tried to use that feature
> yet.

It does NOT support interrupts, which is an issue for my particular
projects.

> I only use MPLAB for debugging.  While it's got its share of annoyances, it
> is constantly improving and is a very effective tool for getting the job
> done.  I particularly like how the simulator, the ICD2, the ICE2000 and the
> ICE4000 have the same debugging interface despite the vastly different
> underlying structure.

I also like the newer MPLAB interface. I am just pissed off that they
needlessly obsoleted the ICD1. I HATE premeditated waste, particularly
when it is so easy to avoid.

Robert

2005\04\30@190047 by John J. McDonough

flavicon
face
----- Original Message -----
From: "Robert Rolf" <spamBeGoneRobert.RolfKILLspamspam@spam@ualberta.ca>
Subject: Re: [PIC] MPLAB & ICD1


> There is no good reason to abandon products when the ONLY
> requirement to keep them useful is a firmware update.

I'm sure Microchip made a decision based on business realities.  At some
point, you make the decision that the cost of maintaining support exceeds
the business losses caused by disaffected customers.  Support for any
product inside a company as large as Microchip isn't cheap.  I'm sure that a
firmware upgrade must cost tens of thousands, if not hundreds of thousands,
of dollars.  Continuing the baggage in future versions of MPLAB will cost
even more.

This is always the case, and will always be the case.  I'm pretty annoyed
that the old version of PageMaker that I have loved so long no longer works
very well with the latest versions of Windows.  The new product is not only
expensive, but not the same product.  It is big, complicated and cumbersome.
Oh well, that's just the way it is.

The time will come for ICD2, ICE2000, ICE4000, and on and on.  When we buy a
piece of hardware that is dependent on some manufacturer's software, or when
we buy software that is dependent on some other piece of software, we have
to expect this.  We need to make our best estimate of the useful life based
on the entire environment, and then recognize that we may not see the
business drivers the same way as the supplier.

And that's how it is ...

--McD


2005\04\30@204529 by Jinx

face picon face
> I'm sure Microchip made a decision based on business realities.  At some
> point, you make the decision that the cost of maintaining support exceeds
> the business losses caused by disaffected customers

<snip>

> This is always the case, and will always be the case.  I'm pretty annoyed
> that the old version of PageMaker that I have loved so long no longer

<snip>

> The time will come for ICD2, ICE2000, ICE4000, and on and on.

<snip>

> And that's how it is ...

Well, that's how the big picture is. On an individual basis there's often
no need to abandon a working product. It's why I keep a Win95/98
PC so I can contiuue using older, proven, versions of s/w and h/w
(for exarmpit my perfectly good scanner hasn't got XP drivers) that
I'm well-used to. Specifically wrt to Microchip, of course I also have
XP/MPLAB7 for latest release devices

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