Post by thread:[PICLIST] MPLAB

No exact or substring matches. trying for part
PICList Thread
'Microchip MPLAB PICMASTER Software'
1995\12\08@191254 by Darrel Johansen

MPLAB, the new Windows 3.1 IDE for the Microchip PICMASTER emulator is now available on the Microchip BBS. This software includes a windows version of MPASM, the Microchip universal assembler, integrated support for MPC, the ByteCraft C compiler, and a built in programmer's text editor and project manager. This software is in broad beta release to anyone who cares to download it from the BBS. It will be officially released soon, and eventually posted on Microchip's WEB site. Until then, all the software and full documentation in .PDF format (readable by Adobe Acrobat --also available on the BBS) can be downloaded. You may find benefits to using this software even if you do not have a PICMASTER emulator. Writing source code and assembling/compiling are highly integrated, letting you double click on lines in the error listing to return the offending lines in source code. If you are a PICMASTER user, we feel you'll like the new tools. If you don't have a PICMASTER but use MPASM or MPC, you'll probably benefit with MPLAB. Please check it out and give us comments on the BBS or here.

1995\12\09@003806 by Ben L Wirz

Does this mean anyone can get and use the ByteCraft C complier by downloading this or MPLAB will allow you to add the ByteCraft C complier to it. I'm sure the latter is true, I'm never that lucky. Ben, Ben Wirz Check out My Home Page for Great Deals on Bulk Buy Electronics (LMD 18200 H Bridge and PIC 16C84) spam_OUTblw2TakeThisOuTcec.wustl.edu http://cec.wustl.edu/~blw2/index.html On Fri, 8 Dec 1995, Darrel Johansen wrote: {Quote hidden}> MPLAB, the new Windows 3.1 IDE for the Microchip PICMASTER emulator is > now available on the Microchip BBS. > > This software includes a windows version of MPASM, the Microchip > universal assembler, integrated support for MPC, the ByteCraft C > compiler, and a built in programmer's text editor and project manager. > > This software is in broad beta release to anyone who cares to download > it from the BBS. It will be officially released soon, and eventually > posted on Microchip's WEB site. > > Until then, all the software and full documentation in .PDF format > (readable by Adobe Acrobat --also available on the BBS) can be > downloaded. > > You may find benefits to using this software even if you do not have a > PICMASTER emulator. Writing source code and assembling/compiling are > highly integrated, letting you double click on lines in the error > listing to return the offending lines in source code. > > If you are a PICMASTER user, we feel you'll like the new tools. If you > don't have a PICMASTER but use MPASM or MPC, you'll probably benefit > with MPLAB. Please check it out and give us comments on the BBS or > here. >

1995\12\09@142016 by Andrew Warren

Ben L Wirz <.....PICLISTKILLspam@spam@MITVMA.MIT.EDU> wrote: > Does this mean anyone can get and use the ByteCraft C complier by > downloading this or MPLAB will allow you to add the ByteCraft C > complier to it. I'm sure the latter is true, I'm never that lucky. You're correct, Ben; MP-C is not available for free. -Andy Andrew Warren - fastfwdKILLspamix.netcom.com Fast Forward Engineering, Vista, California http://www.geopages.com/SiliconValley/2499

'Programmer with MPLAB'
1995\12\10@002644 by Ben Kwok-Yiu Li

WOuld I be able to use Parallax or Advanced Transatlantic devices programmer with MPLAB? _____________________________________________________________________________ | .....benliKILLspam.....uclink2.berkeley.edu | EraseMEbenlispam_OUTTakeThisOuTocf.berkeley.edu | benlispam_OUTbdt.com ******| |---------------------------------------------------------------------------| |WEB Page under construction...coming soon to a WWW Server near you...******| |---------------------------------------------------------------------------| |"If we don't stop him now, Bill Gates will take over the entire galaxy, he | |already has Earth, and Mars." - Anonymous | |___________________________________________________________________________|

1995\12\10@143312 by Andrew Warren

Ben Kwok-Yiu Li <@spam@benliKILLspamuclink2.berkeley.edu> wrote: > WOuld I be able to use Parallax or Advanced Transatlantic devices > programmer with MPLAB? Ben: Sure, although if you already have a good text-editor and MPASM, MPLAB won't do much for you. -Andy Andrew Warren - KILLspamfastfwdKILLspamix.netcom.com Fast Forward Engineering, Vista, California http://www.geopages.com/SiliconValley/2499

'Re[2]: MPLAB Prob'
1995\12\12@140951 by Pete.Brink

At this point MPLAB does not include a simulator. However, we are working on a version of MPSIM that will function much the same as the emulator. If you are interested in MPLAB with the simulator, it is probably a good idea to download the MPLAB files from the Microchip BBS (including the help and the README.LAB!) and get familiar with the interface. It functions as an editor and project manager for PIC16/17 based products. Pete ______________________________ Reply Separator _________________________________ Subject: Re: MPLAB Prob Author: Christer Johansson <RemoveMEcjTakeThisOuTALGONET.SE> at Internet_Exchange Date: 12/12/95 4:00 PM Hi, >I'm not, Ben... Did you copy DEFAULT.TBR, MPLAB.INI, and MPC.PIF into >your WINDOWS directory, as directed in the README.LAB file? Sorry to jump right in. Does MPLAB include a simulator in the Windows environment ? /Christer -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- * High Tech Horizon - Christer Johansson - * email: spamBeGonecjspamBeGonealgonet.se * -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- * Vi saljer Parallax, Inc. BASIC Stamp's produkter i Skandinavien * >> World Wide Web - http://www.algonet.se/~cj/catalog.html << -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

1995\12\12@145628 by Darrel Johansen

>Sorry to jump right in. Does MPLAB include a simulator in the Windows >environment ? First and Last Word on MPLAB Simulator: This version of MPLAB does not include the simulator. The simulator is in development and should be ready in the spring of '96. Features will be the same as the DOS version of MPSIM, in terms of PIC processor support and stimuli. Time stamp will appear the the trace, and most other features will look exactly the same in MPLAB whether you are using the simulator or PICMASTER emulator (except the simulator runs a couple orders of magnitude slower). ______________________________ Reply Separator _________________________________ Subject: Re: MPLAB Prob Author: Christer Johansson <TakeThisOuTcjEraseMEspam_OUTALGONET.SE> at Internet_Exchange Date: 12/12/95 4:00 PM Hi, >I'm not, Ben... Did you copy DEFAULT.TBR, MPLAB.INI, and MPC.PIF into >your WINDOWS directory, as directed in the README.LAB file? Sorry to jump right in. Does MPLAB include a simulator in the Windows environment ? /Christer -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- * High Tech Horizon - Christer Johansson - * email: RemoveMEcjTakeThisOuTalgonet.se * -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- * Vi saljer Parallax, Inc. BASIC Stamp's produkter i Skandinavien * >> World Wide Web - http://www.algonet.se/~cj/catalog.html << -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

'Simulation on MPLAB'
1996\04\25@135736 by Russell Politzky

Does anyone know when the SIMULATION option will be available on MPLAB? MPLAB looks quite good so far. -- ------------------------------------- E-mail: politzkyEraseME.....icon.co.za Date: @date@ Time: @time@ Its better not to know than to know what aint so -------------------------------------

1996\04\25@161220 by Pete Brink

We intend to post the Beta version of the MPLAB-SIM (MPSIM for Windows) on our BBS under the name MPLAB299.EXE in the next day or two. If you are already using MPLAB with the PICMASTER emulator the transfer between the two should be basically transparent. To support the emulator with this version you will also need to download PICMASTR.EXE and install it after installing the new version of MPLAB. To get to our BBS call your local Compuserve number and type in MCHIPBBS. Pete Senior Software Engineer Microchip Technology Inc. EraseMEpete.brinkmicrochip.com ______________________________ Reply Separator _________________________________ Subject: Simulation on MPLAB Author: Russell Politzky <RemoveMEpolitzkyEraseMEEraseMEICON.CO.ZA> at Internet_Exchange Date: 4/25/96 7:52 PM Does anyone know when the SIMULATION option will be available on MPLAB? MPLAB looks quite good so far. -- ------------------------------------- E-mail: RemoveMEpolitzkyspam_OUTKILLspamicon.co.za Date: @date@ Time: @time@ Its better not to know than to know what aint so -------------------------------------

1996\04\25@165413 by Kim Cooper

Release is currently scheduled for May 15. Kim Cooper Microchip Technology ______________________________ Reply Separator _________________________________ Subject: Simulation on MPLAB Author: Russell Politzky <RemoveMEpolitzkyTakeThisOuTspamICON.CO.ZA> at Internet_Exchange Date: 4/25/96 7:52 PM Does anyone know when the SIMULATION option will be available on MPLAB? MPLAB looks quite good so far. -- ------------------------------------- E-mail: EraseMEpolitzkyspamspamBeGoneicon.co.za Date: @date@ Time: @time@ Its better not to know than to know what aint so -------------------------------------

1996\04\26@092645 by Norm Cramer

Pete, Could you let the list know when the software is posted to the BBS? Thanks, Norm At 01:00 PM 4/25/96 -0700, you wrote: > We intend to post the Beta version of the MPLAB-SIM (MPSIM for > Windows) on our BBS under the name MPLAB299.EXE in the next day or > two. > [snip] --------------------------------------------------------------------------- Norm Cramer Work: RemoveMEcramerKILLspamdseg.ti.com Texas Instruments Home: cramerSTOPspamspam_OUTiamerica.net Software Engineering Voice: 214-462-4923 Embedded Real Time Systems aka WD2AEM ---------------------------------------------------------------------------

1996\04\26@183713 by Pete Brink

The Beta version of MPLAB with the simulator is now available from the Microchip BBS. It is in the INT-REL library. To install this version of MPLAB you must download both MPLAB299.EXE and MPLAB299.W02. If you want to use the PICMASTER emulator as well, you must also download PICMASTR.EXE from the same library. Have fun simulating. Pete Pete Brink Senior Software Engineer Microchip Technology Inc. spamBeGonepete.brinkSTOPspamEraseMEmicrochip.com ______________________________ Reply Separator _________________________________ Subject: Re: Simulation on MPLAB Author: Norm Cramer <KILLspamcramerspamBeGoneDSEG.TI.COM> at Internet_Exchange Date: 4/26/96 8:24 AM Pete, Could you let the list know when the software is posted to the BBS? Thanks, Norm At 01:00 PM 4/25/96 -0700, you wrote: > We intend to post the Beta version of the MPLAB-SIM (MPSIM for > Windows) on our BBS under the name MPLAB299.EXE in the next day or > two. > [snip] --------------------------------------------------------------------------- Norm Cramer Work: EraseMEcramerEraseMEdseg.ti.com Texas Instruments Home: @spam@cramer@spam@spam_OUTiamerica.net Software Engineering Voice: 214-462-4923 Embedded Real Time Systems aka WD2AEM ---------------------------------------------------------------------------

'Has anyone downloaded MPLAB299?'
1996\04\30@181850 by Xaq

Has anyone had the chance to get MPLAB299 from microchip? If so how? Their BBS kicks me off after ten minutes, and that's just short of the amount of time I need to download the file. I am running 28.8kbps to my ppp account, and it is just not fast enough. I have sent a message to Pete Brink, at MicroChip, regarding this problem, and he said he would have to forward it to the BBS support manager. He said he would notify us when the problem is fixed, but I was wondering if any one has a faster connection and could download file and share it with the unfortunate few who don't have T3 lines running to our homes. (I am one of the unfortunate few) Thanks Zach

'SIMULATOR MPLAB299'
1996\05\01@100905 by Moshe Fish

Is it possible to put the beta version of mplab299.exe on the microchip website.It is much easier to get there Thanks ------------------------------------- Name :Moshe Fish E-mail :spamBeGonemfishKILLspamnetvision.net.il Date :05/01/96 Time :05:05:49

1996\05\01@110835 by Pete Brink

To the members of the PICLIST: We do not want to put the beta version on the Website, simply because it is just that, beta software. The Website is already full of other information, APP notes, etc. and we prefer to keep the development systems releases to production only. It only means a couple of weeks until the software is released and winds up on the Website. To Xaq in particular: I spoke with our BBS manager and he said there is nothing knocking you off our BBS after 10 minutes. The problem must be with your local Compuserve number. Sorry I cannot offer any other assistance. Pete Senior Software Engineer Microchip Technology Inc. .....pete.brinkspam_OUTmicrochip.com ______________________________ Reply Separator _________________________________ Subject: SIMULATOR MPLAB299 Author: Moshe Fish <TakeThisOuTmfish.....TakeThisOuTNETVISION.NET.IL> at Internet_Exchange Date: 5/1/96 5:05 AM Is it possible to put the beta version of mplab299.exe on the microchip website.It is much easier to get there Thanks ------------------------------------- Name :Moshe Fish E-mail :TakeThisOuTmfishKILLspamspamnetvision.net.il Date :05/01/96 Time :05:05:49

1996\05\01@121557 by Ed VanderPloeg

I downloaded the beta MPLAB299.EXE last night at 14.4kbaud, no sweat. And yes, the Compuserve number does have a timeout of some sort, I think the one I use is 30 or 45 minutes. Maybe they should change their motto to "To serve and disconnect". If you use the Zmodem protocol, then a clean 28.8Kbaud connection should download the file in under 10 minutes anyways... -Ed VanderPloeg ______________________________ Reply Separator _________________________________ Subject: Re: SIMULATOR MPLAB299 Author: pic microcontroller discussion list <.....PICLISTRemoveMEMITVMA.MIT.EDU> at InterNet Date: 5/1/96 8:15 AM To the members of the PICLIST: We do not want to put the beta version on the Website, simply because it is just that, beta software. The Website is already full of other information, APP notes, etc. and we prefer to keep the development systems releases to production only. It only means a couple of weeks until the software is released and winds up on the Website. To Xaq in particular: I spoke with our BBS manager and he said there is nothing knocking you off our BBS after 10 minutes. The problem must be with your local Compuserve number. Sorry I cannot offer any other assistance. Pete Senior Software Engineer Microchip Technology Inc. RemoveMEpete.brinkspamBeGonemicrochip.com ______________________________ Reply Separator _________________________________ Subject: SIMULATOR MPLAB299 Author: Moshe Fish <spamBeGonemfish@spam@spam_OUTNETVISION.NET.IL> at Internet_Exchange Date: 5/1/96 5:05 AM Is it possible to put the beta version of mplab299.exe on the microchip website.It is much easier to get there Thanks ------------------------------------- Name :Moshe Fish E-mail :TakeThisOuTmfishspamnetvision.net.il Date :05/01/96 Time :05:05:49

1996\05\01@123223 by cj

Dear Pete, >I spoke with our BBS manager and he said there is nothing knocking >you off our BBS after 10 minutes. The problem must be with your >local Compuserve number. Sorry I cannot offer any other >assistance. I experience the same - kicked out after 10 minutes and I also sent you an e-mail regarding this the same day the Beta was available... Must be something we are doing wrong ! What username and pass- word should be used ? I used anonymous and me e-mail address as password... Regards, /Christer -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- * High Tech Horizon - Christer Johansson - E-mail: cjEraseMEhth.com * -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- * Vi saljer Parallax, Inc. BASIC Stamp's produkter i Skandinavien * >> World Wide Web On-Line Catalog - http://www.hth.com << -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

1996\05\01@124708 by David Tait

Moshe Fish asked: > Is it possible to put the beta version of mplab299.exe on the microchip > website.It is much easier to get there Just to remind everyone that you can download files from the BBS by FTP. From the UK this is much faster than trying to get the same files from the Microchip WWW/FTP site hosted by ultranet.com. The beta release of MPLAB is here: ftp://mchipbbs.microchip.com/library/int-rel/mplab299.exe Though you can use anonymous FTP, the BBS FTP server needs a valid e-mail address (not just "user@" which is the style supplied by many WWW browsers). Note, this file is 1854123 bytes long! David -- RemoveMEdavid.taitEraseMEspam_OUTman.ac.uk

'Simulation on MPLAB'
1996\05\01@221152 by Karel Hladky

In article <@spam@1814d890RemoveMEEraseMEccmail.microchip.com>, Pete Brink <EraseMEPete.Brink@spam@MICROCHIP.COM> writes > The Beta version of MPLAB with the simulator is now available from > the Microchip BBS. It is in the INT-REL library. To install this > version of MPLAB you must download both MPLAB299.EXE and > MPLAB299.W02. If you want to use the PICMASTER emulator as well, > you must also download PICMASTR.EXE from the same library. Any chance of placing these also on your ftp server ? Karel -- ++++++++@spam@khladkyspam_OUT.....khdesign.demon.co.uk++Manchester M14 6BF England++++++++

'Re[2]: MPLAB & win 95'
1996\05\22@120113 by Pete Brink

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 <spamBeGonecramerEraseMEDSEG.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}>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. > >

'Initial MPLAB Comments'
1996\05\22@132941 by myke predko

Hi Folks, I just downloaded the latest version of MPLAB and tried it out. I really wanted it for the integrated Simulator, so my initial comments will pretty much be totally directed toward this. 1. MP-SIM does not run proplerly in the WIN-OS2 Session of OS/2 Warp. MPASMWIN and the Editor and other functions of MPLAB seem to work okay, but MP-SIM does not. I killed about an hour trying different options until I shut down OS/2 and booted Windows 3.11. 2. Is there any way to customize the register display? I'm asking this from two different perspectives. The first is just to display the Registers (RAM and otherwise) that you want, rather then them all and having to scroll through them. The second is to allow the user to specify one single format for the Register contents, rather than show every different (decimal, binary, and hex) type. I like to display the data differently depending on the Register. I may be weird, but I liked to create custom MPSIM.INI Files for each project I was working on; I found it made monitoring what was going on a lot easier. 3. The Processor Options (ie type) are not saved with the Project, is it possible (in the next upgrade) to include this as well. 4. What are the "PPLUS301.EXE" and "PMSTR300" files in the .zip file used for? I presume that "PPLUS301" is an upgrade for the PICStart Plus Package? 5. When will an updated manual be available? I do have the current manual, but I would like to see one with the updated features included. 6. Will there be a separate MP-SIM Manual made available? This would help avoid a lot of the problems I had initially. A tutorial (in "help", like the code assembly tutorial) would be nice as well. 7. Will there be a PICStart B and C Interface to MPLAB? Or, is there an interface for other Programmer Software? Now, having said all this, I have to say that I LOVE MPLAB! (So much so, I just ordered a PicStart Plus for pick up at the Seminar next week.) Features that I like: 1. In the editor, you actually use a mono-spaced font (my biggest complaint about "Write"-like editors for Windows that use a porportionally spaced font which looks crappy for code). 2. The executing code can be related to in the source (I hated MPSIM's single line interface). 3. Projects and only having to start one program from Windows. 4. Basic Register Contents on Bottom Line during Simulation Execution. (Including Processor Execution (Carry, Zero, Digit Carry) Flags.) I'm really pleased at how well everything goes together with this program. I have only tried it out on the "Tutor.asm" that it comes with and an assembler file that I created, but I am definitely moving to it from MPASM and MPSIM and the editor I was using. For the Microchip people: I'm really impressed with the level of support you give for your products. In my job, I work with other Micro-Controller manufacturers and the support and tools that you provide are defintely head and shoulders above them! Myke Myke "We're Starfleet officers, weird is part of the job." Capt. Catherine Janeway

1996\05\22@135836 by Mike DeMetz

> 4. What are the "PPLUS301.EXE" and "PMSTR300" files in the .zip file used > for? I presume that "PPLUS301" is an upgrade for the PICStart Plus Package? > > > 7. Will there be a PICStart B and C Interface to MPLAB? Or, is there an > interface for other Programmer Software? > > > Now, having said all this, I have to say that I LOVE MPLAB! (So much so, I > just ordered a PicStart Plus for pick up at the Seminar next week.) > What is the difference between Picstart Plus and Oicstart 16B,16B1 ********************************************************** *Mike DeMetz SYSCON International * *mikedspamBeGonesyscon-intl.com South Bend, IN USA * *aka RemoveME73165.1230@spam@spamBeGonecompuserve.com using Pegasus Mail * **********************************************************

1996\05\22@142927 by fastfwd

Mike DeMetz <.....PICLIST@spam@EraseMEMITVMA.MIT.EDU> wrote: > What is the difference between Picstart Plus and Picstart 16B,16B1 Mike: Picstart Plus will program ALL the PICs, from the very smallest 12-bit parts to the largest 16-bit parts. Also, Picstart Plus can only be operated from within the Windows-based MPLAB; there's no DOS software for it. -Andy Andrew Warren - .....fastfwdRemoveMEix.netcom.com Fast Forward Engineering, Vista, California http://www.geocities.com/SiliconValley/2499

1996\05\22@142935 by fastfwd

myke predko <.....PICLISTSTOPspam@spam@MITVMA.MIT.EDU> wrote: > 4. What are the "PPLUS301.EXE" and "PMSTR300" files in the .zip > file used for? I presume that "PPLUS301" is an upgrade for the > PICStart Plus Package? Myke: PPLUS301 adds PICStart Plus support to MPLAB; PMSTR300 adds PIC-Master support to it. Without those files, MPLAB only supports software simulation (and editing, project-management, etc.). -Andy Andrew Warren - fastfwdEraseME@spam@ix.netcom.com Fast Forward Engineering, Vista, California http://www.geocities.com/SiliconValley/2499

1996\05\22@151220 by Darrel Johansen

Myke, Thanks for the feedback. I'll try to answer some of your questions: 1. We have not tested on OS2. We know it runs on Win 3.1, 3.11, and '95. 2. Use the Watch windows to make customized register displays. Currently, we show the values of registers in all formats. Support for other data types will be added at some point in the future. 3. Processor Options should be saved. We'll look at that and make sure it gets fixed in a future release. 4. "PPLUS301.EXE" and "PMSTR300" are the .DLL files that support the new PICSTART Plus Universal Device Programmer, and the PICMASTER emulator in the new version of MPLAB. These need to be installed after MPLAB only if you have these development systems. 5. Updated manual should be on the Web and BBS soon (if not already) in .PDF format. New manuals are shipping with PICSTART Plus. 6. A separate MPSIM manual will not be available. What we've done is combined MPLAB IDE, Project, Editor, and Simulator into a single manual since that is the "core" common software now for all Microchip development systems. This manual is very similar to the on-line help of MPLAB, but fleshed out with more screen-shots. 7 Currently there are no plans to pull PICSTART 16B or 16C into the MPLAB IDE. We appreciate the comments and compliments , and are glad that you find the new products useful. Darrel Johansen ______________________________ Reply Separator _________________________________ Subject: Initial MPLAB Comments Author: myke predko <RemoveMEmykespamBeGonePASSPORT.CA> at Internet_Exchange Date: 5/22/96 1:29 PM Hi Folks, I just downloaded the latest version of MPLAB and tried it out. I really wanted it for the integrated Simulator, so my initial comments will pretty much be totally directed toward this. 1. MP-SIM does not run proplerly in the WIN-OS2 Session of OS/2 Warp. MPASMWIN and the Editor and other functions of MPLAB seem to work okay, but MP-SIM does not. I killed about an hour trying different options until I shut down OS/2 and booted Windows 3.11. 2. Is there any way to customize the register display? I'm asking this from two different perspectives. The first is just to display the Registers (RAM and otherwise) that you want, rather then them all and having to scroll through them. The second is to allow the user to specify one single format for the Register contents, rather than show every different (decimal, binary, and hex) type. I like to display the data differently depending on the Register. I may be weird, but I liked to create custom MPSIM.INI Files for each project I was working on; I found it made monitoring what was going on a lot easier. 3. The Processor Options (ie type) are not saved with the Project, is it possible (in the next upgrade) to include this as well. 4. What are the "PPLUS301.EXE" and "PMSTR300" files in the .zip file used for? I presume that "PPLUS301" is an upgrade for the PICStart Plus Package? 5. When will an updated manual be available? I do have the current manual, but I would like to see one with the updated features included. 6. Will there be a separate MP-SIM Manual made available? This would help avoid a lot of the problems I had initially. A tutorial (in "help", like the code assembly tutorial) would be nice as well. 7. Will there be a PICStart B and C Interface to MPLAB? Or, is there an interface for other Programmer Software? Now, having said all this, I have to say that I LOVE MPLAB! (So much so, I just ordered a PicStart Plus for pick up at the Seminar next week.) Features that I like: 1. In the editor, you actually use a mono-spaced font (my biggest complaint about "Write"-like editors for Windows that use a porportionally spaced font which looks crappy for code). 2. The executing code can be related to in the source (I hated MPSIM's single line interface). 3. Projects and only having to start one program from Windows. 4. Basic Register Contents on Bottom Line during Simulation Execution. (Including Processor Execution (Carry, Zero, Digit Carry) Flags.) I'm really pleased at how well everything goes together with this program. I have only tried it out on the "Tutor.asm" that it comes with and an assembler file that I created, but I am definitely moving to it from MPASM and MPSIM and the editor I was using. For the Microchip people: I'm really impressed with the level of support you give for your products. In my job, I work with other Micro-Controller manufacturers and the support and tools that you provide are defintely head and shoulders above them! Myke Myke "We're Starfleet officers, weird is part of the job." Capt. Catherine Janeway

1996\05\22@160704 by LEUNG LAUREN KWAN-KIT

Is PICSTART Plus available yet? I've ordered one in the 2nd first seminar this year, but still haven't got it yet... any words? - Lauren On Wed, 22 May 1996, Andrew Warren wrote: {Quote hidden}> Mike DeMetz <spamBeGonePICLISTKILLspam@spam@MITVMA.MIT.EDU> wrote: > > > What is the difference between Picstart Plus and Picstart 16B,16B1 > > Mike: > > Picstart Plus will program ALL the PICs, from the very smallest > 12-bit parts to the largest 16-bit parts. > > Also, Picstart Plus can only be operated from within the > Windows-based MPLAB; there's no DOS software for it. > > -Andy > > Andrew Warren - fastfwdspam_OUT@spam@ix.netcom.com > Fast Forward Engineering, Vista, California > http://www.geocities.com/SiliconValley/2499 >

1996\05\22@172115 by pic

Hi all, I have been experimenting with the new MPLAB software, and either it is full of bugs, it has problems with win95, or there is something wrong with my installation. First off I had the win95 problem with the bwcc.dll file. But I got that sorted out thanks to the advice of members of this list. Then I am faced with numerous GPF's and application errors, etc. I have hard reset the machine many times, but it seems to make no difference. The program runs fine for a while until I get it to go do something it has to think about, like going between animate and run modes, etc. The problems seem very intermittent but they are there all the same. Also, can anyone tell me why the highlight in the source code window sometimes runs one line ahead of where it should be in anamate mode? It would be nice to know if anyone else has experienced any of these problems? Wayne G Boyd.

1996\05\23@041734 by Wolfram Liebchen

myke predko wrote: > > Hi Folks, > > > 1. MP-SIM does not run proplerly in the WIN-OS2 Session of OS/2 Warp. > MPASMWIN and the Editor and other functions of MPLAB seem to work okay, but > MP-SIM does not. I killed about an hour trying different options until I > shut down OS/2 and booted Windows 3.11. > > > Now, having said all this, I have to say that I LOVE MPLAB! (So much so, I > just ordered a PicStart Plus for pick up at the Seminar next week.) Myke, I don't understand your problems with MPLAB and OS/2. I run MPLAB as a seamless Windows (enhanced 386) session in OS/2 Warp, and it works great (including simulator)! And that's true: MPLAB is a wonderful tool! Many thanks to Microchip. Wolfram -- +-----------------------------------------------+ ! Wolfram Liebchen, spamBeGoneliebchen@spam@ipserv.ffo.fgan.de ! ! Forschungsinstitut fuer Optik ! ! Schloss Kressbach ! ! D-72072 Tuebingen ! ! Tel: +49 (0)7071 / 709-158 ! ! Fax: +49 (0)7071 / 709-270 (G3 / G4) ! +-----------------------------------------------+

1996\05\23@085352 by Norm Cramer

At 10:16 PM 5/22/96 PDT, you wrote: >Hi all, > >I have been experimenting with the new MPLAB software, and either >it is full of bugs, it has problems with win95, or there is >something wrong with my installation. First off I had the >win95 problem with the bwcc.dll file. But I got that sorted >out thanks to the advice of members of this list. Then I am >faced with numerous GPF's and application errors, etc. I have >hard reset the machine many times, but it seems to make no difference. > I have been running it without any problems yet. I have only been doing testing to see if all my old stuff works in the new environment but havent seen the GPF yet. I may not have run it enough yet. I have not seen any of the other problems that you mention. There is an anoyance about the window though. I noticed that when the MPLAB window comes up, it covers the task bar. To get to the task bar, I have to minimize the window. I haven't played with it enough to see if I can work around this problem but if there isn't a workaround, this one needs to be fixed also. Anyone else see this one? > Also, can anyone tell me why the highlight in the source code >window sometimes runs one line ahead of where it should be in anamate >mode? I'll look for this one next time I run. I have found that for the testing level I am doing now, I don't like animate since it slows things down. For initial testing it looks like a key feature. Hope this helps, Norm

1996\05\23@090004 by Clyde Smith-Stubbs

Norm Cramer <RemoveMEcramerEraseMEKILLspamdseg.ti.com> wrote: > There is an anoyance about the window though. I noticed that when the MPLAB > window comes up, it covers the task bar. To get to the task bar, I have to > minimize the window. I haven't played with it enough to see if I can work Try *maximizing* the window. You'll find MPLAB then fills the screen area excluding the task bar. Why does it work this way? Who knows - Sicromoft logic, I guess. -- Clyde Smith-Stubbs | HI-TECH Software, | Voice: +61 7 3300 5011 spamBeGoneclydespam_OUTRemoveMEhitech.com.au | P.O. Box 103, Alderley, | Fax: +61 7 3300 5246 http://www.hitech.com.au | QLD, 4051, AUSTRALIA. | BBS: +61 7 3300 5235 ---------------------------------------------------------------------------- For info on the World's best C cross compilers for embedded systems, point your WWW browser at http://www.hitech.com.au, or email .....infoRemoveMEhitech.com.au

1996\05\23@091125 by myke predko

> >I don't understand your problems with MPLAB and OS/2. I run MPLAB as a >seamless Windows (enhanced 386) session in OS/2 Warp, and it works great >(including simulator)! > >And that's true: MPLAB is a wonderful tool! Many thanks to Microchip. > >Wolfram The problems was in the stepping and reset functions. The stepping commands seemed to jump to new addresses at random. The reset function wouldn't put in the correct initial address (started at 0x01 and 0x02 and never quite made 0x00) and the contents of the system registers never were the expected (as per the manual) values. This is on an IBM Thinkpad, running OS/2 Warp in the "WIN-OS2" Window. When I rebooted under DOS/Windows (using OS/2's "Boot Manager") and reloaded MPLAB, no problems. Myke Myke "We're Starfleet officers, weird is part of the job." Capt. Catherine Janeway

1996\05\23@092033 by Norm Cramer

At 10:59 PM 5/23/96 +1000, you wrote: >Try *maximizing* the window. You'll find MPLAB then fills the screen area >excluding the task bar. Why does it work this way? Who knows - Sicromoft >logic, I guess. > Thanks, I'll try it when I get home. Norm

1996\05\23@102929 by Darrel Johansen

> There is an anoyance about the window though. I noticed that when the MPLAB > window comes up, it covers the task bar. To get to the task bar, I have to > minimize the window. I haven't played with it enough to see if I can work > around this problem but if there isn't a workaround, this one needs to be > fixed also. Anyone else see this one? This is a general problem with Win 3.1 applications and Windows 95. There is a shareware program called "Shove It" which you can find on the Internet Win 95 Shareware Web sites which helps a little. Darrel.

1996\05\23@113048 by Andy David

part 0 762 bytes I've been using MPLAB as my development environment on my Win-95'd PC without any problems whatsoever (and isn't it just a vast improvement over the PICMaster environment?) - I think that MPLAB is a useful and solid IDE. I've just moved my code from a 10Mhz 16c73 to a 20Mhz '73 and had a few timing issues, so my only gripe is that the picmaster itself won't run at 20MHz. >There is an anoyance about the window though. I noticed that when the >MPLAB >window comes up, it covers the task bar. To get to the task bar, I have to >minimize the window. As for it hiding the taskbar, I have mine set to autohide, so it's not a problem. - Andy. Andy David AndyD@spam@Ultronics.co.uk Ultronics Division Ultra Hydraulics.

'More MPLAB comments and gripes!'
1996\05\28@112925 by Scott Newell

More MPLAB comments and bugs. 1. Where's my SSP shift register? The help file claims this pseudo-registe r is available for viewing in the special functions register. Don't see it there or in the watch window. 2. Problems with deselected windows always covering up the others. For instance, open up the Asynchronous Stimulus window. Then, open the help file. I can't seem to get the help file to cover the Asynch Stim window. 3. I get a 100:1 slowdown in execution speed when the Asynch Stim window is open. (4 instructions per second is pretty darn slow, and this is on a dx2-66!) 4. What's the official power-up value of BF in SSPSTAT? I can get the sim to give me 0 or 1. Power-on reset doesn't seem to affect the value, but my databook claims 0. Any thoughts? 5. A cool stepping function would be 'run until return'. That way, if you get into a long subroutine and see that things are going to work out you don't have to single step through a long routine (say, a floating point divide!). I guess I could scroll down and set a break, but I usually don't put labels at the end of routines. later, newell

'Changing pin values with MPLAB'
1996\05\28@143627 by Daniel Holt

How do you change the pin values in MPLAB durring a simulation. I am trying to simulate a matrix keypad which externally holds port B pins high. Of course the simulator doesn't know this (without a stimulation file). I have tried the 'modify' window with no luck. I can only change general purpose registers, but not the ports. Another gripe.... The help files where not included in my download. Is this normal? Thanks for any help. --- Daniel Holt DATA: EraseMEholtRemoveMESTOPspammail.sdsu.edu EMAIL RemoveMEholtKILLspamTakeThisOuTrohan.sdsu.edu FTP HomePage - http://rohan.sdsu.edu/home/holt VOICE: Home - (619) 670-3145 Office - (619) 594-4259 Pager - (619) 624-4964 Cell - (619) 987-0971 Voice Mail Local - 619-229-2244 Ext. 13145 Voice Mail Long Dist. 1800-680-2728 Ext. 13145 7pm-7am Please don't say you couldn't reach me.... :)

1996\05\28@150206 by Adrian Clinciu

Hi, You can use asynchronous, pin and clock stimulus, from "Debug/Simulator Stimulus" option on main menu. Adrian At 11:36 1996-05-28 -0700, Daniel Holt wrote: {Quote hidden}> >How do you change the pin values in MPLAB durring a simulation. I am trying >to simulate a matrix keypad which externally holds port B pins high. Of >course the simulator doesn't know this (without a stimulation file). I have >tried the 'modify' window with no luck. I can only change general purpose >registers, but not the ports. > >Another gripe.... The help files where not included in my download. Is >this normal? Thanks for any help. >--- >Daniel Holt >

1996\05\28@155230 by Darrel Johansen

Daniel Holt <spamBeGoneholt@spam@MAIL.SDSU.EDU> writes: >How do you change the pin values in MPLAB durring a simulation. I am >trying to simulate a matrix keypad which externally holds port B pins >high. Of course the simulator doesn't know this (without a >stimulation file). I have tried the 'modify' window with no luck. I >can only change general purpose registers, but not the ports. >Another gripe.... The help files where not included in my download. >Is this normal? Thanks for any help. The pin values will change as soon as you step or run the simulator. This is something that we want to address in an upcoming interim release, along with other things (the main one being the system crash after executing an Async Stimulus set to Pulse). That release should be posted early next week. The help files were separated from the executables for those who didn't want to download them for each release. This saves time, and most prefer it this way. Darrel Johansen

'Re[2]: MPLAB bug? HELP!!!'
1996\05\29@130845 by Darrel Johansen

Jim, This problem was reported in beta testing for MPLAB-SIM. The latest released version on the BBS (MPLAB 3.01) solves this problem. If you want to wait until next week, we'll be posting a new version of MPLAB-SIM which has some additional fixes and fine tunings. Darrel Johansen ______________________________ Reply Separator _________________________________ Subject: Re: MPLAB bug? HELP!!! Author: Newfound Electronics <RemoveMEnewfoundspam_OUTNE.COM.AU> at Internet_Exchange Date: 5/29/96 4:24 PM Hi all, I've been trying to use MPLAB and have ended up very confused! What is the real result of this operation? MOVLW 01 ADDWF PC,SAME RETLW 0AH RETLW 0Eh MPLAB insists on jumping to the first RETLW 0Ah. I reckon it's wrong and plug for the second RETLW 0Eh. A zero offset ends up in an infinite loop!!?? I'm sure I knew how this all worked but after using MPLAB, I am confused and have a king size headache! Am I bugged or is it MPLAB? Also, the RETLW instruction description "example" for all the PICs I checked appears to describe the table jump operation incorrectly. TABLE ADDWF PC RETLW K1 RETLW K2 " " RETLW Kn w = 0x07 should return K8 NOT k7, right? This is just to confuse me more I guess.... Jim

'Initial MPLAB + PICStart Plus Comments'
1996\05\31@094318 by myke predko

Hi Folks, I spent a couple of hours last night with the PICStart Plus with MPLAB and here are a few comments: 1. I got two General Protection Faults (GPFs) while running the program. Actually, they were both so bad the PC reset. I hadn't seem them with just running MPLAB. Once question on this, after the reboot, I found that the source code was at the last level (not the last *saved* level). Does the compile/build steps save the source? 2. The configuration fuses and Id locations weren't picked up from the program (__CONFIG and __IDLOCS, respectively). The documentation indicates that they should be loaded from the hex file. Not a big problem, just the first time I tried programming a device, I didn't notice that it was set for an "RC" oscillator and the watchdog timer was on. Not a big problem, just an annoyance. I ran PPLUS101.EXE from the Windows "Run" facility to install it. Other than these two problems, Programming runs seamlessly in the window. It should just be noted that the programmer has to be enabled and once this is done, no other functions of MPLAB can be used. Not a problem, just something to be aware of. Great Tools! Myke Myke "We're Starfleet officers, weird is part of the job." Capt. Catherine Janeway

'Current Version of MPLAB?'
1996\06\04@122821 by myke predko

Just checking the Microchip Web Site, I noticed that under development tools, MPLAB-IDE is noted at version 3.09.02. The current version that I am using is 3.01. Trying to download the file gave me an error saying the subdirectory doesn't exist. Did I happen in at the halfway point of a software upgrade? Could somebody please post on PICList when it is complete? Thanx, Myke Myke "We're Starfleet officers, weird is part of the job." Capt. Catherine Janeway

'Which MPLAB?'
1996\06\05@193137 by Pic User

Fellow PICers, I need help in straightening out this mess. I am trying to download MPLAB, this is what I have gone through: Do not have a modem. netscape to http://www.microchip.com works ok, but cannot get to software through it. using ftp: ftp.mchip.com/biz/mchip cannot connect at all using anonymous login, also tried ftp to mchip.com/biz/mchip, didn't work either. using netscape: ftp://ftp.mchip.com/biz/mchip/software/ works great, can get to software directory, then mplab directory resulting in: ftp://ftp.mchip.com/biz/mchip/software/mplab/ but they only have: mplab300.zip 2407 Kb Fri May 17 17:23:00 1996 very slow loading (500/sec). using ftp: Then tried the ftp site MCHIPBBS.MICROCHIP.COM using anonymous that Wolfram stated in the following message: "I don't have any problem with downloading. I did it during the last 20 minutes (MPLAB309.EXE and LBHP309.EXE). No problem. I logged on to the ftp site MCHIPBBS.MICROCHIP.COM with my registered user name and it worked very good." Worked great for me too, went to directory library/mplab and got files: labhp301.exe mplab301.exe pmstr300.exe pplus101.exe which are the same as what is in the zip file except for pplus101.exe. Downloaded much faster. ******** QUESTIONS ******** 1. What is difference between: netscape - ftp://ftp.mchip.com/biz/mchip/software/mplab/ ftp - MCHIPBBS.MICROCHIP.COM? Will they always be the same? 2. Where is MPLAB309.EXE? 3. What is difference between 309 and 301? 4. What is pplus101.exe? 5. What is a "registered user name"? Does that get me 309? 6. Exactly what files do I need for full MPLAB/WINDOWS capability? (Seminar is not until 27 June). Thanks a million. Steve ------------------------------------- E-mail: davidsonspamits.bldrdoc.gov Date: 04/20/94 Time: 10:00:38 This message was sent by Chameleon -------------------------------------

1996\06\06@091809 by Mike DeMetz

I ftp'd to ftp.futureone.com (their WEB site) and went to pub/download/mplab and got it. I am not seeing mplab309 in the mplab directory of mchipbbs.microchip.com wether I log in as anonymous or my registered name. ********************************************************** *Mike DeMetz SYSCON International * *spam_OUTmikedspam_OUTspam_OUTsyscon-intl.com South Bend, IN USA * *aka 73165.1230spam_OUTcompuserve.com using Pegasus Mail * **********************************************************

'Current Version of MPLAB?'
1996\06\06@095106 by Jattie van der Linde

myke predko wrote: > > Just checking the Microchip Web Site, I noticed that under development > tools, MPLAB-IDE is noted at version 3.09.02. The current version that I am > using is 3.01. > > Did I happen in at the halfway point of a software upgrade? Could > somebody please post on PICList when it is complete? > I've downloaded MPLAB and contrary to previous reports It does support Picstart. I'll attach it as mail to all personal requests.

1996\06\06@103427 by Mike DeMetz

.> I've downloaded MPLAB and contrary to previous reports It does support > Picstart. I'll attach it as mail to all personal requests. > Only Picstart Plus.

1996\06\07@021049 by Newfound Electronics

>.> I've downloaded MPLAB and contrary to previous reports It does support >> Picstart. I'll attach it as mail to all personal requests. >> >Only Picstart Plus. > Exactly! MPLAB supports only the PICSTART PLUS and mega dollar PROMATE programmers. The old picstart 16B and 16C have been generically renamed "PICSTART LITE" and are being sold off at a low cost. Microchip does not support them with MPLAB and has no plan to support them in the furture. However Microchip are open to some lobbying regarding their programmers. Jim

1996\06\07@093922 by Mike DeMetz

> The old picstart 16B and 16C have been generically renamed "PICSTART LITE" > and are being sold off at a low cost. Microchip does not support them with > MPLAB and has no plan to support them in the furture. However Microchip are > open to some lobbying regarding their programmers. > > Jim I'll join that lobby. Just upgraded my PICSTART 16B last fall. Any idea of the street price of the PLUS? ********************************************************** *Mike DeMetz SYSCON International * *RemoveMEmikedKILLspam@spam@syscon-intl.com South Bend, IN USA * *aka 73165.1230spamBeGone.....compuserve.com using Pegasus Mail * **********************************************************

'MPC & MPLAB problems....'
1996\06\07@190607 by Carlos E Lopez-Reyna

Does any body know how get MPLAB to show an absolute listing of an MPC (C compiler) file ? I have succesfully compile and generated *.lst files from within MPLAB but when time to debug comes the absolute listing option is dim. This doesn't happen with regular assambler files. Any help would be greatly appreciated. Carlos Lopez-Reyna

1996\06\09@005851 by John & Maria Perry

From: Carlos E Lopez-Reyna <KILLspamclopez.....ENIAC.SEAS.UPENN.EDU> > Does any body know how get MPLAB to show an absolute listing of > an MPC (C compiler) file ? I have succesfully compile and generated > .lst files from within MPLAB but when time to debug comes the > absolute listing option is dim. I had this same problem, and was about to send a desperate query to the list (I _HATE_ MPLAB's insistence on going to the source), when I realized that all I had to do was load the list file as a simple file. Behold, MPLAB even highlighted the correct instructions for me! Eventually, I even found out that I could get rid of those damn pop-ups into the original source by going to the WINDOW menu and killing the source window item. Now I'm doing fine with the absolute listing alone. Isn't there any way to make my preference permanent? john perry spam_OUTjperryKILLspamnorfolk.infi.net

'Which MPLAB?'
1996\06\10@055029 by Wolfram Liebchen

Pic User wrote: > > Fellow PICers, I need help in straightening out this mess. I am trying to > download MPLAB, this is what I have gone through: > > using ftp: > Then tried the ftp site MCHIPBBS.MICROCHIP.COM using anonymous > that Wolfram stated in the following message: > "I don't have any problem with downloading. > I did it during the last 20 minutes (MPLAB309.EXE and > LBHP309.EXE). No problem. I logged on to the ftp site > MCHIPBBS.MICROCHIP.COM with my registered user name and it > worked very good." > > 5. What is a "registered user name"? Does that get me 309? > > > Steve Steve, The files for version 3.09 are located in the INT-REL subdirectory of ftp://mchipbbs.microchip.com . What I mean with "registered user name" is: I first contacted Microchip's BBS via Compuserve (it's about the same as TELNET) and logged on as a new user, then received an account. Then you have a user name and a password and - I think - you have no restrictions in connect time. Maybe, you should try this. regards, Wolfram -- +-----------------------------------------------+ ! Wolfram Liebchen, RemoveMEliebchenRemoveMEEraseMEipserv.ffo.fgan.de ! ! Forschungsinstitut fuer Optik ! ! Schloss Kressbach ! ! D-72072 Tuebingen ! ! Tel: +49 (0)7071 / 709-158 ! ! Fax: +49 (0)7071 / 709-270 (G3 / G4) ! +-----------------------------------------------+

'Re[2]: MPC & MPLAB problems....'
1996\06\10@113503 by Jim Kape

John, Maria, and Carlos, I have a solution for you. In your first line of source code, place: #pragma option v This will tell the C Compiler to put enough information into the code description file for MPLAB to pull it out automatically. So instead of manually opening the absolute listing, you can pull it in via the window selection. This will also give you access to symbols, labels, etc. If you don't want it automatically pulling up the source, go to options->environment setup and turn off Track Source Code. This will allow the program memory or the absolute listing to be stepped, without worrying about the code. Hope that helps, Jim ______________________________ Reply Separator _________________________________ Subject: Re: MPC & MPLAB problems.... Author: John & Maria Perry <KILLspamjperryspamBeGoneNORFOLK.INFI.NET> at Internet_Exchange Date: 6/9/96 12:57 AM From: Carlos E Lopez-Reyna <clopezspamENIAC.SEAS.UPENN.EDU> > Does any body know how get MPLAB to show an absolute listing of > an MPC (C compiler) file ? I have succesfully compile and generated > .lst files from within MPLAB but when time to debug comes the > absolute listing option is dim. I had this same problem, and was about to send a desperate query to the list (I _HATE_ MPLAB's insistence on going to the source), when I realized that all I had to do was load the list file as a simple file. Behold, MPLAB even highlighted the correct instructions for me! Eventually, I even found out that I could get rid of those damn pop-ups into the original source by going to the WINDOW menu and killing the source window item. Now I'm doing fine with the absolute listing alone. Isn't there any way to make my preference permanent? john perry RemoveMEjperryspamBeGoneRemoveMEnorfolk.infi.net

'Future of MPLAB'
1996\06\12@082329 by Wolfram Liebchen

Hi, I saw someone of the list ask for long file names in MPLAB. Hm. I would be happy if MPLAB remains a 16-bit Windows application, so OS/2 users are not excluded from using this wonderful development system. It may also affect PowerMac users or users, that run any Windows-emulator on a different host. So, please Microchip, stay 16-bit and compatible! What are your suggestions? Wolfram -- +-----------------------------------------------+ ! Wolfram Liebchen, KILLspamliebchenspamBeGoneipserv.ffo.fgan.de ! ! Forschungsinstitut fuer Optik ! ! Schloss Kressbach ! ! D-72072 Tuebingen ! ! Tel: +49 (0)7071 / 709-158 ! ! Fax: +49 (0)7071 / 709-270 (G3 / G4) ! +-----------------------------------------------+

1996\06\12@090810 by John B C Walker

On Wed, 12 Jun 1996, Wolfram Liebchen wrote: > Hi, > > I saw someone of the list ask for long file names in MPLAB. > Hm. I would be happy if MPLAB remains a 16-bit Windows application, > so OS/2 users are not excluded from using this wonderful > development system. It may also affect PowerMac users or users, > that run any Windows-emulator on a different host. > So, please Microchip, stay 16-bit and compatible! > Is there any reason why there cannot be two versions of MPLAB, one for 16-bit and one for 32-bit. The extra facilities in Win95 make it difficult and frustrating to use existing 16-bit apps. What do you think? {Quote hidden}> What are your suggestions? > > Wolfram > > -- > > +-----------------------------------------------+ > ! Wolfram Liebchen, @spam@liebchenSTOPspam@spam@ipserv.ffo.fgan.de ! > ! Forschungsinstitut fuer Optik ! > ! Schloss Kressbach ! > ! D-72072 Tuebingen ! > ! Tel: +49 (0)7071 / 709-158 ! > ! Fax: +49 (0)7071 / 709-270 (G3 / G4) ! > +-----------------------------------------------+ > ----------------------------------------------------------------- Johnnie Walker MSc Digital Systems Engineering Heriot-Watt University email: ceejbcwspamBeGonespamBeGonecee.hw.ac.uk spamBeGoneceejbwpp.hw.ac.uk www: http://www.cee.hw.ac.uk/~ceejbcw tel: (0131) 343 2864 -----------------------------------------------------------------

1996\06\12@110626 by Wolfram Liebchen

John B C Walker wrote: > > > Is there any reason why there cannot be two versions of MPLAB, one for > 16-bit and one for 32-bit. The extra facilities in Win95 make it > difficult and frustrating to use existing 16-bit apps. > > What do you think? > Surely, you're right! I simply wanted to mention, that there might be people, who can't use a 32-bit version. To have two versions is the optimum. Wolfram +-----------------------------------------------+ ! Wolfram Liebchen, spam_OUTliebchenSTOPspamipserv.ffo.fgan.de ! ! Forschungsinstitut fuer Optik ! +-----------------------------------------------+

1996\06\12@221913 by Mark K Sullivan

'Is MPLAB only usefull when using a PIC Emulator?'
1996\06\18@140632 by NEIL GANDLER

From looking at the manual for MPLAB, it seems to only be usefull when using a compatable emulator. I was under the impression that MPLAB was an easier to use version of MPASM and MPSIM with am much better user interface, with a built in project manager. Am I wrong? I can't afford those $800 emulators, I am hoping the simulator can tackle my debugging needs. Neil Gandler

1996\06\18@223149 by Newfound Electronics

> From looking at the manual for MPLAB, it seems to only be usefull when >using a compatable emulator. I was under the impression that MPLAB >was an easier to use version of MPASM and MPSIM with am much better >user interface, with a built in project manager. Am I wrong? >I can't afford those $800 emulators, I am hoping the simulator can >tackle my debugging needs. > > Neil Gandler > Neil, MPLAB was first release a a front end for the emulators only, BUT a simulator version is now available. If you cannot find the simluator, chances are you have the earlier emulator version. Jump on the web or the BBS and and grab the latest version. Jim

1996\06\19@014521 by fastfwd

NEIL GANDLER <RemoveMEPICLISTspamMITVMA.MIT.EDU> wrote: > From looking at the manual for MPLAB, it seems to only be usefull > when using a compatable emulator. I was under the impression that > MPLAB was an easier to use version of MPASM and MPSIM with am much > better user interface, with a built in project manager. Am I wrong? Neil: No, you're correct... The simulator option (called MPLAB-SIM) was added to MPLAB only recently, so it's no real surprise that the manual doesn't mention it. -Andy Andrew Warren - TakeThisOuTfastfwdspamRemoveMEix.netcom.com Fast Forward Engineering, Vista, California http://www.geocities.com/SiliconValley/2499

1996\06\19@155957 by Bryan Hord

I'm having problems with MPLAB also. I've downloaded the latest and greatest (3.09) and tried to go through the tutorial. The first item is to create a new project. "Click on New Project, a dialog box appears," etc. Only a dialog box does not appear. I would dearly like to set up some simulations but I'm a bit stumped. At 01:56 PM 6/18/96 -0500, you wrote: > From looking at the manual for MPLAB, it seems to only be usefull when >using a compatable emulator. I was under the impression that MPLAB >was an easier to use version of MPASM and MPSIM with am much better >user interface, with a built in project manager. Am I wrong? >I can't afford those $800 emulators, I am hoping the simulator can >tackle my debugging needs. > > Neil Gandler > > KILLspambryanspamspam_OUTwllink.com

'Re[2]: MPLAB-SIM'
1996\06\24@102116 by Jim Kape

This is not necessarily true. You can step with the source code and have everything synchronized. If you have already compiled your code, you can highlight the source code and RESET, STEP, RUN, etc. without a problem. When you edit your code, however, it will offset the line number information that MPLAB saves from the compile. There are two solutions: 1) Re-compile. You can do this by clicking on the MAKE button on the toolbar, or by simply pressing F10. 2) Open the program memory window and step that. 3) - bonus solution - Open the absolute listing window and step that. To summarize, you can step source code, listing file, or disassembled memory contents. Whatever makes more sense to your debugging situation. Hope this helps. Jim ______________________________ Reply Separator _________________________________ Subject: Re: MPLAB-SIM Author: Clyde Smith-Stubbs <clydeRemoveMEHITECH.COM.AU> at Internet_Exchange Date: 6/24/96 10:28 PM Kalle Pihlajasaari <EraseMEkalleSTOPspamRemoveMEdevice.data.co.za> > > How is one intended to place ones comments so that the > single step stays synchronised with source file. There's an MPLAB bug^H^H^Hfeature - make sure you have the program window (NOT the source window) selected as the active window before stepping. Then it should update the source window ok. But if you have the source window active, it does not update it. Clyde -- Clyde Smith-Stubbs | HI-TECH Software, | Voice: +61 7 3300 5011 spam_OUTclydeRemoveMEEraseMEhitech.com.au | P.O. Box 103, Alderley, | Fax: +61 7 3300 5246 http://www.hitech.com.au | QLD, 4051, AUSTRALIA. | BBS: +61 7 3300 5235 ---------------------------------------------------------------------------- For info on the World's best C cross compilers for embedded systems, point your WWW browser at http://www.hitech.com.au, or email TakeThisOuTinfoRemoveME@spam@hitech.com.au

'17C42 in MPLAB'
1996\07\10@073414 by John B C Walker

Dear All, Thanks to Microchip, I replaced the BWCC.DLL file with the MPLAB one and everything works great. Problem: When I try to simulate the 17C42 in MPLAB, the DDRB,PORTA,PORTB etc registers never seem to show any changes. I'm sure my code is fine: movlb 0 ;select bank 0 clrf ddrb,1 ;all outputs clrf portb,1 ;clear port_b Is there a bug, or am I doing something wrong. Cheers. J.W. ----------------------------------------------------------------- Johnnie Walker MSc Digital Systems Engineering Heriot-Watt University email: EraseMEceejbcwRemoveMEcee.hw.ac.uk spamceejbw.....spampp.hw.ac.uk ceejbwspam_OUT@spam@torduff.hw.ac.uk www: http://www.cee.hw.ac.uk/~ceejbcw tel: (0131) 343 2864 -----------------------------------------------------------------

1996\07\10@223136 by Darrel Johansen

John B C Walker wrote: > > Problem: > > When I try to simulate the 17C42 in MPLAB, the DDRB,PORTA,PORTB etc > registers never seem to show any changes. I'm sure my code is fine: > > movlb 0 ;select bank 0 > clrf ddrb,1 ;all outputs > clrf portb,1 ;clear port_b > ------------------------ Some changes were made in version 3.09.03 having to do with the 17C42 ports. This particular problem had been previously reported and is now fixed. DJ.

'------- MPLAB ---------'
1996\07\11@084620 by ose G. Pineda A. ELECTRONICO

Hi: In which ftp I can find the last version of MPLAB ? Thank you -- | ~~ ~~ /^\ | Jose Pineda | ~~ /^\ / \ ~~ | Fax : +58 2 2426039 | /_ \/ _ \ ~~ | E-mail : .....jpinedaspam.....dino.conicit.ve | / # _ # _ # _ _ \ | Caracas, D.F. | / # # _ # # # # # _ \ | Venezuela |_/______#_#_#_#_#_#_#_#_#_____\_|

'------- MPLAB --------- -Reply'
1996\07\11@101905 by Mark Jurras

Goto http://www.microchip.com and follow the links. It will take you to http://www.futureone.com/... where you will finally find TWO files needed to download to get MPLAB. - -Mark >>> "Jose G. Pineda A. ELECTRONICO" <jpinedaKILLspamEraseMECONICIT.VE> 11 July 1996 8:45 am >>> Hi: In which ftp I can find the last version of MPLAB ? Thank you

1996\07\11@162029 by JUAN MANUEL MU�OZ

part 0 701 bytes Suerte.. Juan Manuel Mu–oz ea7dae.ampr.org 44.133.11.13 Email: EraseMEjmmc@spam@@spam@arrakis.es ---------- De: Jose G. Pineda A. ELECTRONICO[SMTP:@spam@jpinedaspamKILLspamCONICIT.VE] Enviado: jueves 11 de julio de 1996 12:45 Para: Multiple recipients of list PICLIST Asunto: ------- MPLAB --------- Hi: In which ftp I can find the last version of MPLAB ? Thank you -- | ~~ ~~ /^\ | Jose Pineda | ~~ /^\ / \ ~~ | Fax : +58 2 2426039 | /_ \/ _ \ ~~ | E-mail : spamBeGonejpinedaRemoveMEEraseMEdino.conicit.ve | / # _ # _ # _ _ \ | Caracas, D.F. | / # # _ # # # # # _ \ | Venezuela |_/______#_#_#_#_#_#_#_#_#_____\_|

'Re[2]: MPLAB stimulus file format'
1996\07\24@115622 by Darrel Johansen

Andy, Thanks for posting the information on the simulator stimulus. When MPSIM was brought under MPLAB, however, there were a few changes. I've noted these on your reply below for everyone's information. Darrel ______________________________ Reply Separator _________________________________ Subject: Re: MPLAB stimulus file format Author: Andrew Warren <RemoveMEfastfwdKILLspamRemoveMEIX.NETCOM.COM> at Internet_Exchange Date: 7/23/96 11:32 PM >Rusu Dan Victor <TakeThisOuTPICLISTMITVMA.MIT.EDU> wrote: > Where can I find the stimulus file format for MPLAB? >First, make sure that you are using the latest version of the >simulator (version 5.20)... Actually, the latest version of the simulator on the web site and BBS is MPLAB 3.09.03. Since the simulator has been brought under MPLAB, the DOS version is "frozen." New parts and fixes will only be occurring in MPLAB-SIM. MPLAB-SIM has a number of other advantages, as well, of course --the main one being the MPLAB IDE. >Regular, periodic clock signals can be simulated by using the "CK" >command... This feature is under the Debug>Simulator Stimulus>Clock Stimulus menu. Now you can enter clock stimuli in this dialog list. As an additionaly bonus, we've added the "invert" switch, which lets you define a clock stimulus that starts out on the low part of the cycle. You can define up to 12 clocks. {Quote hidden}>If you need to simulate waveforms that are not this regular, you can >do so using a "stimulus file". Stimulus files are simple ASCII text >files that look like this: >STEP RB7 RC0 RA2 >1 0 0 0 >5 1 0 0 >20 1 0 1 >21 0 0 0 >The headings in the first line are important: The first one must >be "STEP", and the remaining ones show which pins are to be >stimulated. >In each of the following lines, the first number is the "step count" >(more on this later) and the other numbers are the values to be placed >on the pins. There is no limit to the length of a stimulus file, nor >to the number of pins that it can stimulate. >The "step count" defaults to the instruction step. That is, the >above stimulus file will execute the first line when the first >instruction is executed, the second line when the 5th instruction is >executed, the third line when the 20th instruction is executed, etc. >Since some instructions (GOTO, CALL, etc.) take two cycles rather than >one, this may lead to unexpected results, since the simulator is using >instruction counts rather than absolute time. >To remedy this, Microchip has added the "IP" command. It sets the >bahavior of stimulus files thusly: >"IP" displays the current mode. >"IP step" sets the mode to "count steps". >"IP time" sets the mode to "count time". >"step" and "time" are literal strings... To set the >mode to "time", the command is actually "IP time". >Note that, even if you use the "IP" command to set the mode to >"time", the first column heading in your stimulus file must still >be "STEP". >After creating the stimulus file, you load your source code into MPSIM >as usual, then load the stimulus file using "ST filename". This feature is called Debug>Simulator Stimulus>Pin Stimulus in MPLAB. We found very few people using the STEP mode, so this feature is now always in the TIME mode, counting cycles as matched by MPLAB's stopwatch. Few people actually care to inject a value at the 240'th instruction, and usually want to inject a value every 10 ms; or after 45, then 60, then 17E microseconds; or whatever. Using the clock frequency, calculate the number of PIC16/17 cycles that would be required for that time, and enter that as the value in the first column. The header must say "STEP," for compatibility with older MPSIM fiiles. You can also put comments in files. Here is a section of a file to test the 16C620 comparators. Note the use of "!" to separate comments: ! 16C62x Comparator Stimulus file ! The calculated outputs represent the state of the comparator outputs ! _after_ the step executes. ! CM<2:0> 000 100 011 101 111 110 001 001 ! Ref Ref CIS0 CIS1 ! reset |2 Com |2 Com |1 Ind |Off |2 Com |3 In/2|3 In/2 ! AN0 AN3 AN1 AN2 C1 C2 C1 C2 C1 C2 C1 C2 C1 C2 C1 C2 C1 C2 C1 C2 STEP RA0 RA3 RA1 RA2 ! RA3 RA4 0 0 0 0 0 4 0 0 0 0 14 0 0 1 1 ! 0 0 0 0 1 0 0 0 0 0 1 0 1 0 1 0 16 0 1 1 1 ! 0 0 1 0 1 0 0 0 0 0 1 0 1 0 1 0 18 0 1 1 0 ! 0 0 1 0 1 0 0 0 0 0 1 0 1 0 0 0 22 0 1 1 0 ! 0 0 1 0 1 0 0 0 0 0 1 0 1 0 0 0 In addition to these, there is also the Debug>Simulator Stimulus>Register Stimulus, which is similar to the Pin Stimulus,but it injects a *value* into a register at a specied program counter location. The values are read sequentially from a file, where the values are just and ASCII list like: 20 26 2F 30 ... The purpose of this stimulus is to mimic something like an A/D register, although you can use it to inject values into any writable register. If you specify the address of the start of your A/D handler as the program counter address for the Register Stimulus, each time that address is executed a value from the list will be injected into the specified register. After MPLAB-SIM gets the last value from this list, it will wrap and get the first value, repeating the list endlessly. >Hope this helps... >-Andy >Andrew Warren - spamBeGonefastfwdKILLspamTakeThisOuTix.netcom.com >Fast Forward Engineering, Vista,California >http://www.geocities.com/SiliconValley/249 This information is in the MPLAB User's Guide, which is available for download from the WWW site or Microchip's BBS in a .PDF format. Darrel Johansen Microchip Technology, Inc.

'16C74 in MPLAB'
1996\08\07@082643 by John B C Walker

Dear All, I've got code running under MPLAB for a PIC16C74. The code uses the btfss and btfsc instructions. But MPLAB doesn't seem to handle these correctly, it treats the instruction as true all the time, and never skips the following instruction even if false. A code snippet: ..... btfss flg,1 ;test flag goto test_zero btfsc porta,1 ;test A14 = 0 bsf flg,1 ;set flag if A14 = 1 goto ALE_check1 test_zero: btfss porta,1 ;test A14 = 1 goto finish ;end if A14 = 0 ..... In this section, the simulator just skips through to the end, even though the flg register is all zeros Any ideas? Cheers. J.W. ----------------------------------------------------------------- Johnnie Walker MSc Digital Systems Engineering Heriot-Watt University email: EraseMEceejbcw.....KILLspamcee.hw.ac.uk spamceejbwpp.hw.ac.uk ceejbwSTOPspamtorduff.hw.ac.uk www: http://www.cee.hw.ac.uk/~ceejbcw tel: (0131) 343 2864 -----------------------------------------------------------------

'Faster assembly in MPLAB V3.09'
1996\08\22@081817 by Dennis Frost

Hi people, This may interest those of you who use MPLAB ver 3.09 and are as impatient as I am. When you compile a file the windows MPASMWIN program is started. It assembles the file and then there is this stupid wait at the end to allow you to see the displayed results (Red bar, Green bar). If you rather get MPLAB to run the dos version of the assembler, then although not as glamorous, the assembly is much faster. I tried it on the code I am busy with now and it took 11 seconds using MPASMWIN and only 5 seconds using MPASM (Dos). Five seconds saved is not a lot but assemble 300 times and you've saved 25 minutes. Anyway I just hate slow things. :-( To use the dos assembler do the following: Go to Project: Add/Modify Complier... In the command line box type MPASM Press OK Go to Project: Make Setup click the Custom Working directory & then enter the path where you copy of mpasm.exe can be found e.g. c:\pic\mplab Press OK Now when you 'Make Project' a dos window will open and the assembly will begin. You will see nothing in the dos window and it will close once the assembly is finnished. All I have to do now is figure out how to stop the empty dos window from displaying. Does anyone know how to do this? Cheers Dennis ____________________________________________________ FROST - Electronic Design, Manufacture & Consulting. Dennis Frost Tel: +27 331 965125 Cel: +83 2275216 Email: dennis.frostSTOPspamKILLspampixie.co.za Pietermaritzburg, South Africa ____________________________________________________

1996\08\22@090804 by Dennis Frost

Hi people, This may interest those of you who use MPLAB ver 3.09 and are as impatient as I am. When you compile a file the windows MPASMWIN program is started. It assembles the file and then there is this stupid wait at the end to allow you to see the displayed results (Red bar, Green bar). If you rather get MPLAB to run the dos version of the assembler, then although not as glamorous, the assembly is much faster. I tried it on the code I am busy with now and it took 11 seconds using MPASMWIN and only 5 seconds using MPASM (Dos). Five seconds saved is not a lot but assemble 300 times and you've saved 25 minutes. Anyway I just hate slow things. :-( To use the dos assembler do the following: Go to Project: Add/Modify Complier... In the command line box type MPASM Press OK Go to Project: Make Setup click the Custom Working directory & then enter the path where you copy of mpasm.exe can be found e.g. c:\pic\mplab Press OK Now when you 'Make Project' a dos window will open and the assembly will begin. You will see nothing in the dos window and it will close once the assembly is finnished. All I have to do now is figure out how to stop the empty dos window from displaying. Does anyone know how to do this? Cheers Dennis ____________________________________________________ FROST - Electronic Design, Manufacture & Consulting. Dennis Frost Tel: +27 331 965125 Cel: +83 2275216 Email: @spam@dennis.frost.....spampixie.co.za Pietermaritzburg, South Africa ____________________________________________________

1996\08\22@111616 by Kalle Pihlajasaari

Hi, > All I have to do now is figure out how to stop the empty dos window from > displaying. > Does anyone know how to do this? Not having tried you might get away with making a PIF file and setting the run minimised option on if this is possible. Cheers -- Kalle Pihlajasaari spamkalle..........data.co.za Interface Products Box 15775, Doornfontein, 2028, South Africa +27 (11) 402-7750 Fax: +27 (11) 402-7751

1996\08\22@112219 by Pete Brink

As an added nore to Dennis' message. The install program for MPLAB should already have a setup for MPASM for DOS. Typing in MPASM into the edit box is not necessary. All you have to do is select the Assembler radio button, and then choose MPASM from the combo box in the upper left corner of the dialog. Pete Pete Brink Senior Software Engineer Microchip Technology Inc. Pete.Brink.....microchip.com ______________________________ Reply Separator _________________________________ Subject: Faster assembly in MPLAB V3.09 Author: Dennis Frost <KILLspamdennis.frostspam_OUTPIXIE.CO.ZA> at Internet_Exchange Date: 8/22/96 2:15 PM Hi people, This may interest those of you who use MPLAB ver 3.09 and are as impatient as I am. When you compile a file the windows MPASMWIN program is started. It assembles the file and then there is this stupid wait at the end to allow you to see the displayed results (Red bar, Green bar). If you rather get MPLAB to run the dos version of the assembler, then although not as glamorous, the assembly is much faster. I tried it on the code I am busy with now and it took 11 seconds using MPASMWIN and only 5 seconds using MPASM (Dos). Five seconds saved is not a lot but assemble 300 times and you've saved 25 minutes. Anyway I just hate slow things. :-( To use the dos assembler do the following: Go to Project: Add/Modify Complier... In the command line box type MPASM Press OK Go to Project: Make Setup click the Custom Working directory & then enter the path where you copy of mpasm.exe can be found e.g. c:\pic\mplab Press OK Now when you 'Make Project' a dos window will open and the assembly will begin. You will see nothing in the dos window and it will close once the assembly is finnished. All I have to do now is figure out how to stop the empty dos window from displaying. Does anyone know how to do this? Cheers Dennis ____________________________________________________ FROST - Electronic Design, Manufacture & Consulting. Dennis Frost Tel: +27 331 965125 Cel: +83 2275216 Email: spam_OUTdennis.frostTakeThisOuTpixie.co.za Pietermaritzburg, South Africa ____________________________________________________

'newbie MPLAB questions'
1996\09\12@194205 by Dwayne Reid

I looked at MPLAB when it was first released several months ago, but didn't then have the time to learn its way of doing things. Now I am about to start a new project and it seems like a good opportunity to look at it again. I do have several questions. I downloaded version 3.09.10 and loaded it over top of the old version that I had before. I created a new project with the same name as an existing .ASM file and then made that .ASM file a part of the project. First question: when selecting files to become part of a project, there is an option button labelled "copy". Why? I assume I would just continue to use the same directory that I do all of my DOS based development from. Is there a benefit to creating a seperate project directory for each project? I should mention that I do most of my code writing on my office machine and a seperate machine in the lab has the PICMASTER hardware installed. I do keep seperate directories on the lab machine for each project (mostly to keep the config and trace files seperate). Is there any way to persuade MPLAB to use a different editor? If possible, I would like to continue to use my DOS based editor (QEdit from Semware). If not, is there any way to configure the existing MPLAB editor to allow entering of text anywhere on the screen as opposed to only within existing lines (virtual whitespace). Upon exiting MPLAB, I find a LARGE (2.09 Mb) file in my MPLAB directory called SMTR001.DAT containing nothing but nulls - what and why is that file? I am sure that I will have many more questions in the days to follow. Thanks to all for any answers and suggestions. Dwayne

'UART simulation with mplab'
1996\09\21@204915 by Pablo

Hi, I have a little problem here. I'm just playing with a very simple code for send data thru de SCI in asynchronous mode of the 16c74. I've done all the pertinent initialization then I wrote a word on the TXREG, then I scan the TXIF on the PIR1 register. The fact is that the txif never goes up after the first transmition.. What I'm doing wrong??? Regards, Pablo Mochcovsky

'Problems with MPLAB 3.10 and PICStart Plus 1.20'
1996\09\30@232821 by myke predko

Hi Folks, Has anybody else successfully loaded the latest (at least on the Web Page) versions of MPLAB and PICStart Plus? I had a number of problems loading MPLAB 3.10 and PSP 1.20 - the first time, I could no longer use Trumpet Winsock and could no longer get on the web. Now, I do have it working, but I get the message the first time I enable the programmer: "An updated version of PICSTART Plus firmware is available,...". When I look at the "Readme" file, I see that I have to get a new 17C44 to load the firmware on. Does anybody have any comments on this? Next, once I "Okay" past this message, I get "Open projects must be rebuilt to properly coordinate device informatoin with PICSTART Plus". What does this mean? Inside the code, I identify the PIC although, MPLAB doesn't seem to remember the device being used in the PICStart Plus Window. As well, the Configuration fuses don't seem to be updated (although in the docs, it indicates that they should be). Has anybody else seen this, or are working with the software yet? Myke Do you ever feel like an XT Clone caught in the Pentium Pro Zone?

'Problems with MPLAB 3.10 and PICStart Plus 1.20'
1996\10\01@085659 by Philip Restuccia

> Hi Folks, > > Has anybody else successfully loaded the latest (at least on the Web Page) > versions of MPLAB and PICStart Plus? I loaded it on my Toshiba Satellite 105CS last night, but didn't have enough time left to play with it. > > I had a number of problems loading MPLAB 3.10 and PSP 1.20 - the first time, > I could no longer use Trumpet Winsock and could no longer get on the web. Hmmm. When I ran it, I noticed that my Desktop Glidepoint started acting *very* erratic. Stayed that way, too, after I exited MPLAB. Had to reboot the laptop to get back even operation of the Glidepoint. (Note: I have the Glidepoint on the PS/2 port, NOT the serial port). Would anyone else have any insight as to why this would have happened? Philip Restuccia .....philip.restuccia.....RemoveMEperi.com

1996\10\03@171151 by myke predko

Hi Kim, Thanx for the reply, I haven't spoken to you in a while. > > The "An updated version..." message is a warning that newer firmware > exists and that not all of the devices will be supported by the > firmware version you are running. For example, the PIC12C508 is not > supported by firmware version 1.01. If you are using firmware version > 1.01, you will not be allowed to select the PIC12C508. I understand this and I'm looking at getting a 17C44 to put in it's place. This is turning out to be surprisingly difficult. I have contacted our rep here in Toronto and they're getting a couple for me. > > The "Open projects must be..." message is a warning that device > information is reinitialized when PICSTART Plus is enabled. If you > had a project open when you enabled PICSTART Plus, you must either > rebuild the project or import the hex file. In the future, PICSTART > Plus will be better coordinated with the simulator and emulator > memory. I'm not really sure what this means. Right now, I am building the project then enabling PICSTART Plus, burning the part and everything works fine. Except that I have to manually set the configuration bits. > > PICSTART Plus must be enabled to update the configuration bits. Then > they updated properly by reading a device, building a project, or > importing a hex file. As I said above, I have to manually set the Configuration Bits on the PICSTART Plus enabled window. Not a big deal, but a bit of a pain (especially when you've just put in your last mod to you code, you *think* everything will work and then the PIC doesn't enable the right oscillator and it just sits there)... > > Hope this helps! Thanx for the reply, I guess my biggest problem was that when I loaded in MPLAB 3.10 the first time, I lost the use of my serial port and modem. I still don't understand why, because when I uninstalled MPLAB and then reloaded it, everything worked fine! To be totally fair, it could also be my PC which is really on it's last legs. myke > > Kim Cooper Do you ever feel like an XT Clone caught in the Pentium Pro Zone?

'current MPLAB version?'
1996\10\10@034227 by liebchen

Hi all, I am a little confused about the current version of MPLAB. Some of you seem to use version 3.10 . But I only see version 3.09.10 on the Microchip WWW site. Their ftp-site (mchipbbs.microchip.com) has an even older version of MPLAB. Where could I get the current version? Thanks. regards Wolfram +------------------------------------------------+ ! Wolfram Liebchen, Forschungsinstitut fŸr Optik ! ! spam_OUTliebchenTakeThisOuTEraseMEffo.fgan.de ! +------------------------------------------------+

1996\10\10@102613 by Darrel Johansen

All, The current released version is still 3.01. Some advance releases (noted by a second decimal point) have been posted. Most recently we posted 3.10.02. Currently we do not have an advance release on either the BBS or web page, but we should be posting the full released version, 3.11, in the next few days. I'll post a note here when the new software is available. Darrel Johansen ______________________________ Reply Separator _________________________________ Subject: current MPLAB version? Author: Wolfram Liebchen <EraseMEliebchenspamBeGoneKILLspamFFO.FGAN.DE> at Internet_Exchange Date: 10/10/96 9:43 AM Hi all, I am a little confused about the current version of MPLAB. Some of you seem to use version 3.10 . But I only see version 3.09.10 on the Microchip WWW site. Their ftp-site (mchipbbs.microchip.com) has an even older version of MPLAB. Where could I get the current version? Thanks. regards Wolfram +------------------------------------------------+ ! Wolfram Liebchen, Forschungsinstitut fŸr Optik ! ! RemoveMEliebchenspamBeGonespamffo.fgan.de ! +------------------------------------------------+

'Picstart Plus and MPLAB problems'
1996\10\10@233935 by Barry Bine

I recently acquired a Picstart Plus development system and have been having mucho problems getting it to work properly. At first I thought Mchip's software was full of bugs, until I learned that most people aren't having any problems. I am at a loss and hoping that someone on the list has had similar problems and fixed them. The symptoms: All I have to do is insert a blank 16C74 and perform the "BLANK CHECK ALL" operation. Sometimes the software reports that the device is blank, other times it reports that it is not. In the latter case, the yellow "ACTIVE" LED on the programmer does not light. The whole thing is very flakey. I have tried different COMM drivers (including the original one that came with Win 3.1) with little success. Programming and verify operations are also sporadic. On the surface, it looks like a communcations problem, but I think it is something else. MPLAB and the assembler are also giving me problems. To put it simply, these programs crash with such regularity that I cannot possibly do any development with them. I have tried two versions of the tool set: 3.01 and 3.09.10 with similar results. Now, since everybody out there seems to be happy with MPLAB and Picstart Plus, I can only suspect that my problems have something to do with my system configuration. Perhaps there is some outdated .DLL or something, but how can I tell? There are many possibilities and I can't think where to begin. If anybody out there in PIC-land has some insights into my problem, I would definitely appreciate hearing from you. Thanks in advance, - Barry Bine P.S. This is my system configuration (if it'll help): PCI/VLB combo motherboard with SIS chipset, Award BIOS, and EIDE I/O. Cyrix 5x86 120 CPU and 20 MB RAM. Number Nine "Motion 771" VLB vid card set to 1024X768 X 15-bit. Sigma Designs Winwave multimedia controller (SB & MPU 401 compatible w/ SCSI CD-ROM). DFI handy scanner. 8-bit Arcnet NIC, "Little Big Lan" network software. Logitech mouse. Windows 3.1 and DOS 6.0. ... that's all the relevent info I can think of. These are my .DLL's- In the WINDOWS directory: MORICONS DLL 118864 03-10-92 3:10a PBRUSH DLL 6766 03-10-92 3:10a RECORDER DLL 10414 03-10-92 3:10a MCIOLE DLL 12288 03-03-94 12:00a VYIOSVC2 DLL 9856 12-15-93 9:48a VMP_MM DLL 18912 12-03-93 2:32p MPEG320 DLL 110096 02-09-94 3:39p MPEG160 DLL 108560 02-09-94 3:39p MSND_MP2 DLL 54288 10-27-93 2:14p MSND_WAV DLL 13840 10-27-93 11:37a LOOKCHIP DLL 10256 02-10-93 12:00p DUNZIP DLL 35328 09-23-94 4:28p FX_METER DLL 6688 07-07-95 12:00p CTL3D DLL 20976 09-15-93 12:00a FX_GRAY DLL 76800 08-04-95 1:26p FWINSDLL DLL 120464 10-30-95 3:34p VER DLL 9008 03-23-92 3:10a AMIENV DLL 11208 02-04-93 7:06p In the WINDOWS/SYSTEM directory: LZEXPAND DLL 9936 03-10-92 3:10a VER DLL 9008 03-10-92 3:10a COMMDLG DLL 89248 03-10-92 3:10a DDEML DLL 36864 03-10-92 3:10a MMSYSTEM DLL 61648 03-10-92 3:10a OLESVR DLL 24064 03-10-92 3:10a SHELL DLL 41600 03-10-92 3:10a WIN87EM DLL 12800 03-10-92 3:10a OLECLI DLL 83456 03-10-92 3:10a TOOLHELP DLL 14128 12-28-94 12:00a WBTRCALL DLL 51392 12-10-93 3:00a FINSTALL DLL 200368 03-10-92 3:10a SETUPKIT DLL 7008 04-28-93 12:00a WINSOCK DLL 145152 11-03-94 2:57p MSAJT200 DLL 995056 11-18-94 12:00a BWCC DLL 164928 02-28-95 11:14a CTL3D DLL 26000 09-16-94 2:00p AAPLAY DLL 137232 06-15-93 9:58a AAVGA DLL 13840 06-15-93 9:58a DISPDIB DLL 7168 11-19-93 12:00a MSVIDEO DLL 121936 03-17-95 12:00a ACMCMPRS DLL 12800 11-19-93 12:00a AVICAP DLL 72704 09-02-94 12:00a AVIFILE DLL 96944 03-03-94 12:00a INTUPROF DLL 20208 01-11-96 12:00a MFCOLEUI DLL 146976 01-13-95 2:10p OLE2CONV DLL 57328 11-18-94 12:00a OLE2DISP DLL 164832 11-18-94 12:00a OLE2NLS DLL 150976 11-18-94 12:00a OLE2PROX DLL 51712 11-18-94 12:00a TYPELIB DLL 177216 11-18-94 12:00a MSACM DLL 49616 11-19-93 12:00a IR21_R DLL 77664 11-19-93 12:00a IR30 DLL 151552 03-27-95 12:00a PCDXBMP DLL 28016 07-19-93 12:00a PCDXEPS DLL 39244 07-19-93 12:00a PCDXPCX DLL 30776 07-19-93 12:00a PCDXTIF DLL 43444 07-19-93 12:00a PCDLIB DLL 84448 07-19-93 12:00a STORAGE DLL 157696 11-18-94 12:00a IR21 DLL 77664 11-19-93 12:00a IR32 DLL 151552 03-27-95 12:00a IYVU9 DLL 50016 09-21-94 12:00a DCIMAN DLL 7840 09-02-94 12:00a VBRUN300 DLL 398416 05-12-93 12:00a DMCOLOR DLL 18480 03-10-92 3:10a D2HTOOLS DLL 44464 07-07-95 2:12a WINGDE DLL 188960 08-24-94 12:00a WING DLL 92208 09-21-94 12:00a WING32 DLL 12800 09-21-94 12:00a CTVWCN DLL 2432 11-25-94 12:00a MVAPI2 DLL 12288 03-22-93 12:00a MVBMP2 DLL 138864 03-22-93 12:00a MVBRKR2 DLL 19968 03-22-93 12:00a MVFS2 DLL 52224 03-22-93 12:00a MVFTSUI2 DLL 160768 09-22-93 12:00a MVMCI2 DLL 93184 03-22-93 12:00a MVSRCH2 DLL 53760 03-22-93 12:00a MVTITLE2 DLL 24576 03-22-93 12:00a QCONNECT DLL 100192 01-11-96 12:00a WELCOME DLL 10535 01-18-95 12:00a UNIDRV DLL 128432 12-31-93 3:11a WINDAPI DLL 70208 04-14-93 2:59p FTENGINE DLL 43520 09-16-94 2:00p FTUI DLL 68096 09-16-94 2:00p MVAPI DLL 5120 09-16-94 2:00p CCAPI200 DLL 46400 09-16-94 2:00p CUECARD2 DLL 2944 09-16-94 2:00p QRYINTL DLL 35391 09-16-94 2:00p WINRFS DLL 14509 09-16-94 2:00p TECHNOTE DLL 14080 09-16-94 2:00p MFC250 DLL 320880 03-02-95 12:42a MFCN250 DLL 11072 01-13-95 2:10p MFC250D DLL 1910248 03-02-95 12:41a MFCN250D DLL 428268 01-13-95 2:10p MFCD250 DLL 51920 03-01-95 3:32a MFCD250D DLL 535992 03-01-95 3:30a MFCO250 DLL 125344 01-13-95 2:10p MFCO250D DLL 986756 01-13-95 2:10p COMPOBJ DLL 108544 11-18-94 12:00a MSCPXLT DLL 10304 07-12-94 12:00a MSJETERR DLL 11232 11-18-94 12:00a MSJETINT DLL 15936 11-18-94 12:00a ODBC DLL 56240 12-07-94 12:00a ODBCCURS DLL 88896 12-07-94 12:00a ODBCINST DLL 92576 12-07-94 12:00a ODBCJT16 DLL 246928 11-18-94 12:00a ODBCTL16 DLL 64080 11-18-94 12:00a ODDBSE16 DLL 4080 11-18-94 12:00a ODFOX16 DLL 4096 11-18-94 12:00a OLE2 DLL 302592 11-18-94 12:00a VBAJET DLL 1984 11-18-94 12:00a VBAR2 DLL 298880 11-18-94 12:00a XBS200 DLL 296832 11-18-94 12:00a CTL3DV2 DLL 26992 08-15-95 12:00a MVBK13W DLL 14512 11-29-95 12:00a MVCL13W DLL 119584 11-29-95 12:00a MVFS13W DLL 46112 11-29-95 12:00a MVMG13W DLL 46400 11-29-95 12:00a MVSR13W DLL 45232 11-29-95 12:00a MVTL13W DLL 40992 11-29-95 12:00a QBA DLL 23056 01-11-96 12:00a OWL252 DLL 484704 08-29-95 4:52a BIDS45 DLL 60758 08-29-95 4:52a BC450RTL DLL 220672 08-29-95 4:52a

1996\10\10@235431 by optoeng

If it's any consolation, I've been extremely unhappy with PSP and with Microchip's support of it. However, it sounds like we are having different problems at the moment. Basically, my PSP doesn't like most of the COM ports I've tried. It only connects to 1 of my 3 computers. Unfortunately, that's the one computer I've set up for my kids, so it's a hassle to use it. Microchip admitted that there are some bugs, and they said someone is working on it, but I haven't heard anything from them now for 3 weeks. I suspect that when I get it going with the COM ports on my preferred computers, I will encounter additional problems such as those you mention. In the meantime, I've put that particular project on the back burner. -- Paul Mathews, consulting engineer AEngineering Co. @spam@optoengspamwhidbey.com non-contact sensing and optoelectronics specialists

1996\10\11@071504 by Stefan Bormann

On Thu, 10 Oct 1996, Barry Bine wrote: > All I have to do is insert a blank 16C74 and perform the "BLANK > CHECK ALL" operation. Sometimes the software reports that the device is > blank, other times it reports that it is not. In the latter case, the > yellow "ACTIVE" LED on the programmer does not light. The whole thing is > very flakey. I have tried different COMM drivers (including the original > one that came with Win 3.1) with little success. Programming and verify > operations are also sporadic. On the surface, it looks like a communcations > problem, but I think it is something else. I have the similar problems with a 16C73 and Picstart Plus and MPLAB. It seems there is no problem with the 16C84 for me. I figured out, that I can rely on the first think, Picstart does after a complete reset of computer and programmer. This is not a solution but a work-around, until these bugs are fixed. BTW: I am working on a system that is quite different to yours, I believe, the problem is just a bug in the Picstart firmware or MPLAB. I hope, somebody posts a message here, when the bugs are fixed! -- Stefan Bormann TakeThisOuTs.bormannKILLspam@spam@tu-bs.de FREMO: ourworld.compuserve.com/homepages/shipmill/inhalt.htm

'New MPLAB Interim Release Available'
1996\10\11@233919 by Darrel Johansen

New MPLAB interim release files v.3.10.03 are now available on the Microchip BBS and on the Microchip web page (http://www.microchip.com). This version fixes the problem that sometimes shows as a KRNL386.EXE error, and will detect older running versions of the file BWCC.DLL that some have had problems with.

'Picstart Plus and MPLAB problems'
1996\10\12@032110 by andreabelian

Barry Bine wrote: {Quote hidden}> > I recently acquired a Picstart Plus development system and have been > having mucho problems getting it to work properly. At first I thought > Mchip's software was full of bugs, until I learned that most people aren't > having any problems. I am at a loss and hoping that someone on the list has > had similar problems and fixed them. > > The symptoms: > > All I have to do is insert a blank 16C74 and perform the "BLANK > CHECK ALL" operation. Sometimes the software reports that the device is > blank, other times it reports that it is not. In the latter case, the > yellow "ACTIVE" LED on the programmer does not light. The whole thing is > very flakey. I have tried different COMM drivers (including the original > one that came with Win 3.1) with little success. Programming and verify > operations are also sporadic. On the surface, it looks like a communcations > problem, but I think it is something else. > > MPLAB and the assembler are also giving me problems. To put it > simply, these programs crash with such regularity that I cannot possibly do > any development with them. > > I have tried two versions of the tool set: 3.01 and 3.09.10 with > similar results. > > Now, since everybody out there seems to be happy with MPLAB and > Picstart Plus, I can only suspect that my problems have something to do with > my system configuration. Perhaps there is some outdated .DLL or something, > but how can I tell? There are many possibilities and I can't think where to > begin. If anybody out there in PIC-land has some insights into my problem, > I would definitely appreciate hearing from you. Thanks in advance, > > - Barry Bine > > P.S. This is my system configuration (if it'll help): > PCI/VLB combo motherboard with SIS chipset, > Award BIOS, and EIDE I/O. > Cyrix 5x86 120 CPU and 20 MB RAM. > Number Nine "Motion 771" VLB vid card > set to 1024X768 X 15-bit. > Sigma Designs Winwave multimedia controller > (SB & MPU 401 compatible w/ SCSI CD-ROM). > DFI handy scanner. > 8-bit Arcnet NIC, "Little Big Lan" network > software. > Logitech mouse. > Windows 3.1 and DOS 6.0. > ... that's all the relevent info I can think of. > > These are my .DLL's- > > In the WINDOWS directory: > > MORICONS DLL 118864 03-10-92 3:10a > PBRUSH DLL 6766 03-10-92 3:10a > RECORDER DLL 10414 03-10-92 3:10a > MCIOLE DLL 12288 03-03-94 12:00a > VYIOSVC2 DLL 9856 12-15-93 9:48a > VMP_MM DLL 18912 12-03-93 2:32p > MPEG320 DLL 110096 02-09-94 3:39p > MPEG160 DLL 108560 02-09-94 3:39p > MSND_MP2 DLL 54288 10-27-93 2:14p > MSND_WAV DLL 13840 10-27-93 11:37a > LOOKCHIP DLL 10256 02-10-93 12:00p > DUNZIP DLL 35328 09-23-94 4:28p > FX_METER DLL 6688 07-07-95 12:00p > CTL3D DLL 20976 09-15-93 12:00a > FX_GRAY DLL 76800 08-04-95 1:26p > FWINSDLL DLL 120464 10-30-95 3:34p > VER DLL 9008 03-23-92 3:10a > AMIENV DLL 11208 02-04-93 7:06p > > In the WINDOWS/SYSTEM directory: > > LZEXPAND DLL 9936 03-10-92 3:10a > VER DLL 9008 03-10-92 3:10a > COMMDLG DLL 89248 03-10-92 3:10a > DDEML DLL 36864 03-10-92 3:10a > MMSYSTEM DLL 61648 03-10-92 3:10a > OLESVR DLL 24064 03-10-92 3:10a > SHELL DLL 41600 03-10-92 3:10a > WIN87EM DLL 12800 03-10-92 3:10a > OLECLI DLL 83456 03-10-92 3:10a > TOOLHELP DLL 14128 12-28-94 12:00a > WBTRCALL DLL 51392 12-10-93 3:00a > FINSTALL DLL 200368 03-10-92 3:10a > SETUPKIT DLL 7008 04-28-93 12:00a > WINSOCK DLL 145152 11-03-94 2:57p > MSAJT200 DLL 995056 11-18-94 12:00a > BWCC DLL 164928 02-28-95 11:14a > CTL3D DLL 26000 09-16-94 2:00p > AAPLAY DLL 137232 06-15-93 9:58a > AAVGA DLL 13840 06-15-93 9:58a > DISPDIB DLL 7168 11-19-93 12:00a > MSVIDEO DLL 121936 03-17-95 12:00a > ACMCMPRS DLL 12800 11-19-93 12:00a > AVICAP DLL 72704 09-02-94 12:00a > AVIFILE DLL 96944 03-03-94 12:00a > INTUPROF DLL 20208 01-11-96 12:00a > MFCOLEUI DLL 146976 01-13-95 2:10p > OLE2CONV DLL 57328 11-18-94 12:00a > OLE2DISP DLL 164832 11-18-94 12:00a > OLE2NLS DLL 150976 11-18-94 12:00a > OLE2PROX DLL 51712 11-18-94 12:00a > TYPELIB DLL 177216 11-18-94 12:00a > MSACM DLL 49616 11-19-93 12:00a > IR21_R DLL 77664 11-19-93 12:00a > IR30 DLL 151552 03-27-95 12:00a > PCDXBMP DLL 28016 07-19-93 12:00a > PCDXEPS DLL 39244 07-19-93 12:00a > PCDXPCX DLL 30776 07-19-93 12:00a > PCDXTIF DLL 43444 07-19-93 12:00a > PCDLIB DLL 84448 07-19-93 12:00a > STORAGE DLL 157696 11-18-94 12:00a > IR21 DLL 77664 11-19-93 12:00a > IR32 DLL 151552 03-27-95 12:00a > IYVU9 DLL 50016 09-21-94 12:00a > DCIMAN DLL 7840 09-02-94 12:00a > VBRUN300 DLL 398416 05-12-93 12:00a > DMCOLOR DLL 18480 03-10-92 3:10a > D2HTOOLS DLL 44464 07-07-95 2:12a > WINGDE DLL 188960 08-24-94 12:00a > WING DLL 92208 09-21-94 12:00a > WING32 DLL 12800 09-21-94 12:00a > CTVWCN DLL 2432 11-25-94 12:00a > MVAPI2 DLL 12288 03-22-93 12:00a > MVBMP2 DLL 138864 03-22-93 12:00a > MVBRKR2 DLL 19968 03-22-93 12:00a > MVFS2 DLL 52224 03-22-93 12:00a > MVFTSUI2 DLL 160768 09-22-93 12:00a > MVMCI2 DLL 93184 03-22-93 12:00a > MVSRCH2 DLL 53760 03-22-93 12:00a > MVTITLE2 DLL 24576 03-22-93 12:00a > QCONNECT DLL 100192 01-11-96 12:00a > WELCOME DLL 10535 01-18-95 12:00a > UNIDRV DLL 128432 12-31-93 3:11a > WINDAPI DLL 70208 04-14-93 2:59p > FTENGINE DLL 43520 09-16-94 2:00p > FTUI DLL 68096 09-16-94 2:00p > MVAPI DLL 5120 09-16-94 2:00p > CCAPI200 DLL 46400 09-16-94 2:00p > CUECARD2 DLL 2944 09-16-94 2:00p > QRYINTL DLL 35391 09-16-94 2:00p > WINRFS DLL 14509 09-16-94 2:00p > TECHNOTE DLL 14080 09-16-94 2:00p > MFC250 DLL 320880 03-02-95 12:42a > MFCN250 DLL 11072 01-13-95 2:10p > MFC250D DLL 1910248 03-02-95 12:41a > MFCN250D DLL 428268 01-13-95 2:10p > MFCD250 DLL 51920 03-01-95 3:32a > MFCD250D DLL 535992 03-01-95 3:30a > MFCO250 DLL 125344 01-13-95 2:10p > MFCO250D DLL 986756 01-13-95 2:10p > COMPOBJ DLL 108544 11-18-94 12:00a > MSCPXLT DLL 10304 07-12-94 12:00a > MSJETERR DLL 11232 11-18-94 12:00a > MSJETINT DLL 15936 11-18-94 12:00a > ODBC DLL 56240 12-07-94 12:00a > ODBCCURS DLL 88896 12-07-94 12:00a > ODBCINST DLL 92576 12-07-94 12:00a > ODBCJT16 DLL 246928 11-18-94 12:00a > ODBCTL16 DLL 64080 11-18-94 12:00a > ODDBSE16 DLL 4080 11-18-94 12:00a > ODFOX16 DLL 4096 11-18-94 12:00a > OLE2 DLL 302592 11-18-94 12:00a > VBAJET DLL 1984 11-18-94 12:00a > VBAR2 DLL 298880 11-18-94 12:00a > XBS200 DLL 296832 11-18-94 12:00a > CTL3DV2 DLL 26992 08-15-95 12:00a > MVBK13W DLL 14512 11-29-95 12:00a > MVCL13W DLL 119584 11-29-95 12:00a > MVFS13W DLL 46112 11-29-95 12:00a > MVMG13W DLL 46400 11-29-95 12:00a > MVSR13W DLL 45232 11-29-95 12:00a > MVTL13W DLL 40992 11-29-95 12:00a > QBA DLL 23056 01-11-96 12:00a > OWL252 DLL 484704 08-29-95 4:52a > BIDS45 DLL 60758 08-29-95 4:52a > BC450RTL DLL 220672 08-29-95 4:52a Same kind of problem hapned with me. If you have norton utility run it will search your hard disk. if there is problem will tel you. then optimize your hard disk. then run memmaker. then chek your IRQ's. by remove any extra boards like sound card "temperery" this way 100% you can find the problem. After all this stil did not work ok delete MPLAB directory then reinstall. should be ok.

1996\10\16@171323 by Cynetics Corp.

Andre Abelian wrote: {Quote hidden}> > Barry Bine wrote: > > > > I recently acquired a Picstart Plus development system and have been > > having mucho problems getting it to work properly. At first I thought > > Mchip's software was full of bugs, until I learned that most people aren't > > having any problems. I am at a loss and hoping that someone on the list has > > had similar problems and fixed them. > > > > The symptoms: > > > > All I have to do is insert a blank 16C74 and perform the "BLANK > > CHECK ALL" operation. Sometimes the software reports that the device is > > blank, other times it reports that it is not. In the latter case, the > > yellow "ACTIVE" LED on the programmer does not light. The whole thing is > > very flakey. I have tried different COMM drivers (including the original > > one that came with Win 3.1) with little success. Programming and verify > > operations are also sporadic. On the surface, it looks like a communcations > > problem, but I think it is something else. > > > > MPLAB and the assembler are also giving me problems. To put it > > simply, these programs crash with such regularity that I cannot possibly do > > any development with them. > > > > I have tried two versions of the tool set: 3.01 and 3.09.10 with > > similar results. > > > > Now, since everybody out there seems to be happy with MPLAB and > > Picstart Plus, I can only suspect that my problems have something to do with > > my system configuration. Perhaps there is some outdated .DLL or something, > > but how can I tell? There are many possibilities and I can't think where to > > begin. If anybody out there in PIC-land has some insights into my problem, > > I would definitely appreciate hearing from you. Thanks in advance, > > > > - Barry Bine > > > > P.S. This is my system configuration (if it'll help): > > PCI/VLB combo motherboard with SIS chipset, > > Award BIOS, and EIDE I/O. > > Cyrix 5x86 120 CPU and 20 MB RAM. > > Number Nine "Motion 771" VLB vid card > > set to 1024X768 X 15-bit. > > Sigma Designs Winwave multimedia controller > > (SB & MPU 401 compatible w/ SCSI CD-ROM). > > DFI handy scanner. > > 8-bit Arcnet NIC, "Little Big Lan" network > > software. > > Logitech mouse. > > Windows 3.1 and DOS 6.0. > > ... that's all the relevent info I can think of. > > > > These are my .DLL's- > > > > In the WINDOWS directory: > > > > MORICONS DLL 118864 03-10-92 3:10a > > PBRUSH DLL 6766 03-10-92 3:10a > > RECORDER DLL 10414 03-10-92 3:10a > > MCIOLE DLL 12288 03-03-94 12:00a > > VYIOSVC2 DLL 9856 12-15-93 9:48a > > VMP_MM DLL 18912 12-03-93 2:32p > > MPEG320 DLL 110096 02-09-94 3:39p > > MPEG160 DLL 108560 02-09-94 3:39p > > MSND_MP2 DLL 54288 10-27-93 2:14p > > MSND_WAV DLL 13840 10-27-93 11:37a > > LOOKCHIP DLL 10256 02-10-93 12:00p > > DUNZIP DLL 35328 09-23-94 4:28p > > FX_METER DLL 6688 07-07-95 12:00p > > CTL3D DLL 20976 09-15-93 12:00a > > FX_GRAY DLL 76800 08-04-95 1:26p > > FWINSDLL DLL 120464 10-30-95 3:34p > > VER DLL 9008 03-23-92 3:10a > > AMIENV DLL 11208 02-04-93 7:06p > > > > In the WINDOWS/SYSTEM directory: > > > > LZEXPAND DLL 9936 03-10-92 3:10a > > VER DLL 9008 03-10-92 3:10a > > COMMDLG DLL 89248 03-10-92 3:10a > > DDEML DLL 36864 03-10-92 3:10a > > MMSYSTEM DLL 61648 03-10-92 3:10a > > OLESVR DLL 24064 03-10-92 3:10a > > SHELL DLL 41600 03-10-92 3:10a > > WIN87EM DLL 12800 03-10-92 3:10a > > OLECLI DLL 83456 03-10-92 3:10a > > TOOLHELP DLL 14128 12-28-94 12:00a > > WBTRCALL DLL 51392 12-10-93 3:00a > > FINSTALL DLL 200368 03-10-92 3:10a > > SETUPKIT DLL 7008 04-28-93 12:00a > > WINSOCK DLL 145152 11-03-94 2:57p > > MSAJT200 DLL 995056 11-18-94 12:00a > > BWCC DLL 164928 02-28-95 11:14a > > CTL3D DLL 26000 09-16-94 2:00p > > AAPLAY DLL 137232 06-15-93 9:58a > > AAVGA DLL 13840 06-15-93 9:58a > > DISPDIB DLL 7168 11-19-93 12:00a > > MSVIDEO DLL 121936 03-17-95 12:00a > > ACMCMPRS DLL 12800 11-19-93 12:00a > > AVICAP DLL 72704 09-02-94 12:00a > > AVIFILE DLL 96944 03-03-94 12:00a > > INTUPROF DLL 20208 01-11-96 12:00a > > MFCOLEUI DLL 146976 01-13-95 2:10p > > OLE2CONV DLL 57328 11-18-94 12:00a > > OLE2DISP DLL 164832 11-18-94 12:00a > > OLE2NLS DLL 150976 11-18-94 12:00a > > OLE2PROX DLL 51712 11-18-94 12:00a > > TYPELIB DLL 177216 11-18-94 12:00a > > MSACM DLL 49616 11-19-93 12:00a > > IR21_R DLL 77664 11-19-93 12:00a > > IR30 DLL 151552 03-27-95 12:00a > > PCDXBMP DLL 28016 07-19-93 12:00a > > PCDXEPS DLL 39244 07-19-93 12:00a > > PCDXPCX DLL 30776 07-19-93 12:00a > > PCDXTIF DLL 43444 07-19-93 12:00a > > PCDLIB DLL 84448 07-19-93 12:00a > > STORAGE DLL 157696 11-18-94 12:00a > > IR21 DLL 77664 11-19-93 12:00a > > IR32 DLL 151552 03-27-95 12:00a > > IYVU9 DLL 50016 09-21-94 12:00a > > DCIMAN DLL 7840 09-02-94 12:00a > > VBRUN300 DLL 398416 05-12-93 12:00a > > DMCOLOR DLL 18480 03-10-92 3:10a > > D2HTOOLS DLL 44464 07-07-95 2:12a > > WINGDE DLL 188960 08-24-94 12:00a > > WING DLL 92208 09-21-94 12:00a > > WING32 DLL 12800 09-21-94 12:00a > > CTVWCN DLL 2432 11-25-94 12:00a > > MVAPI2 DLL 12288 03-22-93 12:00a > > MVBMP2 DLL 138864 03-22-93 12:00a > > MVBRKR2 DLL 19968 03-22-93 12:00a > > MVFS2 DLL 52224 03-22-93 12:00a > > MVFTSUI2 DLL 160768 09-22-93 12:00a > > MVMCI2 DLL 93184 03-22-93 12:00a > > MVSRCH2 DLL 53760 03-22-93 12:00a > > MVTITLE2 DLL 24576 03-22-93 12:00a > > QCONNECT DLL 100192 01-11-96 12:00a > > WELCOME DLL 10535 01-18-95 12:00a > > UNIDRV DLL 128432 12-31-93 3:11a > > WINDAPI DLL 70208 04-14-93 2:59p > > FTENGINE DLL 43520 09-16-94 2:00p > > FTUI DLL 68096 09-16-94 2:00p > > MVAPI DLL 5120 09-16-94 2:00p > > CCAPI200 DLL 46400 09-16-94 2:00p > > CUECARD2 DLL 2944 09-16-94 2:00p > > QRYINTL DLL 35391 09-16-94 2:00p > > WINRFS DLL 14509 09-16-94 2:00p > > TECHNOTE DLL 14080 09-16-94 2:00p > > MFC250 DLL 320880 03-02-95 12:42a > > MFCN250 DLL 11072 01-13-95 2:10p > > MFC250D DLL 1910248 03-02-95 12:41a > > MFCN250D DLL 428268 01-13-95 2:10p > > MFCD250 DLL 51920 03-01-95 3:32a > > MFCD250D DLL 535992 03-01-95 3:30a > > MFCO250 DLL 125344 01-13-95 2:10p > > MFCO250D DLL 986756 01-13-95 2:10p > > COMPOBJ DLL 108544 11-18-94 12:00a > > MSCPXLT DLL 10304 07-12-94 12:00a > > MSJETERR DLL 11232 11-18-94 12:00a > > MSJETINT DLL 15936 11-18-94 12:00a > > ODBC DLL 56240 12-07-94 12:00a > > ODBCCURS DLL 88896 12-07-94 12:00a > > ODBCINST DLL 92576 12-07-94 12:00a > > ODBCJT16 DLL 246928 11-18-94 12:00a > > ODBCTL16 DLL 64080 11-18-94 12:00a > > ODDBSE16 DLL 4080 11-18-94 12:00a > > ODFOX16 DLL 4096 11-18-94 12:00a > > OLE2 DLL 302592 11-18-94 12:00a > > VBAJET DLL 1984 11-18-94 12:00a > > VBAR2 DLL 298880 11-18-94 12:00a > > XBS200 DLL 296832 11-18-94 12:00a > > CTL3DV2 DLL 26992 08-15-95 12:00a > > MVBK13W DLL 14512 11-29-95 12:00a > > MVCL13W DLL 119584 11-29-95 12:00a > > MVFS13W DLL 46112 11-29-95 12:00a > > MVMG13W DLL 46400 11-29-95 12:00a > > MVSR13W DLL 45232 11-29-95 12:00a > > MVTL13W DLL 40992 11-29-95 12:00a > > QBA DLL 23056 01-11-96 12:00a > > OWL252 DLL 484704 08-29-95 4:52a > > BIDS45 DLL 60758 08-29-95 4:52a > > BC450RTL DLL 220672 08-29-95 4:52a > Same kind of problem hapned with me. > If you have norton utility run it will search your hard disk. > if there is problem will tel you. > then optimize your hard disk. > then run memmaker. > then chek your IRQ's. > by remove any extra boards like sound card "temperery" this way 100% > you can find the problem. After all this stil did not work ok > delete MPLAB directory then reinstall. should be ok. I'd had a lot of trouble after I upgraded MPLAB. I called the Tech Support hotline at 1-800-437-2767 and found out that I had to delete an old BWCC.DLL file. Then I had to copy the newest one to both the windows directory and the windows\system directory. I think MPLAB 3.10 is available now.

'Advice on initial install of MPLAB, MPLAB-C, & PIC'
1996\10\18@142754 by dfr

Hi gang. I've just received the PICSTART+ and MPLAB-C kits, and having noticed many comments on compatibility problems between these modules here, I'd like to ask a few questions, if I may. I'm running WIN95 and have disks for MPLAB V3.09.03 and V3.01, MPLAB-C V1.10, & PICSTART+ V1.01. Should I upgrade to later verions of the above before installing? I'm assuming that MPLAB V3.09.03 is later than V3.01. Does MPLAB include the simulator, or do I need to download MPSIM? Any comments, caveats, etc? -- Regards, Dana Frank Raymond

1996\10\18@201250 by Darrel Johansen

>Subject: Advice on initial install of MPLAB, MPLAB-C, & PICSTART+ >Author: Dana Raymond <.....dfrRemoveMEICOM.CA> at Internet_Exchange >Date: 10/18/96 2:28 PM > > >Hi gang. > >I've just received the PICSTART+ and MPLAB-C kits, and having noticed >many comments on compatibility problems between these modules here, >I'd like to ask a few questions, if I may. > >I'm running WIN95 and have disks for MPLAB V3.09.03 and V3.01, >MPLAB-C V1.10, & PICSTART+ V1.01. > >Should I upgrade to later verions of the above before installing? I'm >assuming that MPLAB V3.09.03 is later than V3.01. > >Does MPLAB include the simulator, or do I need to download MPSIM? > >Any comments, caveats, etc? ______________________________ Reply Separator _________________________________ Dana, You don't need to install the older software first. I'd recommend getting the latest software off the web page or BBS. v3.09.03 is better than v3.01, but 3.10.04 has some improvements. Since version 3.00 of MPLAB, MPLAB-SIM is a standard component of MPLAB, along with MPASM. Darrel

1996\10\20@194841 by dfr

Darrel Johansen wrote: > You don't need to install the older software first. I'd recommend getting the > latest software off the web page or BBS. v3.09.03 is better than v3.01, but > 3.10.04 has some improvements. Thanks for your advice Darrel. I loaded MPLAB V3.10.04 (downloaded from the web site), installed it, and then installed MPLAB-C V1.10. The platform is a pentium running WIN95. I have a couple of questions remaining... 1) How do I get the MPLAB directory added to the PATH in WIN95? I added the "include=" and "lib=" to autoexec.bat, but the path is always just "c:\windows;c:\windows\command" no matter what I put in the autoexec.bat file. The installation failed to do either even though it did mention modifying the environment. My harddrive is double-spaced by WIN95. 2) What in heaven is RTM.EXE? MPLAB seems to load it before (or 'for') MPLAB-C during a compile, but it sits there for many seconds (some times tens of seconds) doing who-knows-what! When MPLAB-C is done a message talking about "Microsoft Popup" or something or other is displayed in MPLAB-C's window. Why? I'm running windows, not dos! BTW the mouse is frozen while RTM is thinking! I have 48MB of RAM on the motherboard, could it have something to do with memory management? BTW the progam BWCCFIX.EXE in the MPLAB directory is a good tool to hunt out and delete competing copies of BWCC.DLL. I don't know if that has been mentioned... I found it experimentally. So far so good. PICSTART+ seems to be operating correctly with a 16C84. Thanks for those who have provided assistance on this matter. Much appreciated! -- Regards, Dana Frank Raymond

'DDE and mplab'
1996\10\22@043552 by Joe McCauley

Hi, Can someone please give me a step by step account of how to use dde to get data from mplab into excel. I tried following the sequence in the mplab manual but got no where. Excel seems to want to start mplab and initially did so altough I could'nt get any data from it, but now for some reason excel ,on trying to open mplab, says that it can't start mplab as one of it's components is missing. I'm using Excel 5 and mplab 3.10.03 and win95. Thanks Joe

1996\10\23@084736 by Andrew David

part 0 1031 bytes I tried to do this, got nowhere in about an hour. Recently, though, my project manager has been very generous and bought me an Icepic and a Rice16... and the Icepic software (version 1.5.38 available on Microchip's web site) contains a sample excel spreadsheet for controlling the Icepic - maybe this contains some answers...? I've not really used the Icepic or the Rice16 in anger yet, so I can't really comment on which is better. I will say that there's nothing intrinsically wrong with either, both seem to be perfectly capable professional development tools. A Picmaster with MPLAB is the best I've used, though, no question. - Andy. ************************************************************* Andrew David Senior Project Engineer - Software Ultronics Division KILLspamAndyTakeThisOuTUltronics.co.uk Ultra Hydraulics Ltd. Anson Business Park Cheltenham Road East Staverton Glos. GL2 9QN Tel.: (01452) 858376 (Direct) Ultronics Fax.: (01452) 858377 *************************************************************

'Re[2]: MPLAB and Picstart Plus compatibility.'
1996\10\23@094356 by myke predko

>Return-Path: <TakeThisOuTNorm.LeMieuxspam_OUTmicrochip.com> >Date: Tue, 22 Oct 1996 12:36:24 -0700 >From: RemoveMENorm.LeMieuxspamSTOPspamMicrochip.COM (Norm LeMieux) >Subject: Re[2]: MPLAB and Picstart Plus compatibility. >To: myke predko <.....mykeEraseMEPASSPORT.CA> >Content-Description: cc:Mail note part >X-UIDL: 6bf645e8ca26d8dafda258288876005c > > I assume you mean BWCC.DLL... > > Sorry about that. Yes, I did mean "BWCC.DLL", not "DWCC.DLL" when I was talking about installing the latest versions of MPLAB. Hopefully nobody went looking for DWCC.DLL... Myke Avoiding precedents does not mean nothing should ever be done. It only means that nothing should ever be done for the first time - Sir Humphrey Appleby K.C.B.

'Attn: MPLAB Users: New MPLAB Release'
1996\10\24@193405 by Darrel Johansen

MPLAB Users: As promised, here is an announcement for the new MPLAB software, v.3.12. You can download this from: http://www.microchip2.com/softupdt.htm or from the Microchip BBS. This software also includes new PICSTART Plus drivers and new PICSTART Plus firmware (you will need a blank 25 Mhz 17C44). You do *not* need to upgrade the firmware unless you want to use some of the new devices on PICSTART Plus. See the README.PLS file for more info. Darrel Johansen Microchip Technology, Inc. spamBeGonedarrel.johansenRemoveMEmicrochip.com

1996\10\25@043504 by liebchen

Darrel Johansen wrote: > > MPLAB Users: > > As promised, here is an announcement for the new MPLAB software, v.3.12. > You can download this from: > > http://www.microchip2.com/softupdt.htm Hi Darrel, what is the difference between v.3.10.4 and v.3.12 ? Does it make sense to download? TIA Wolfram -- +------------------------------------------------+ ! Wolfram Liebchen, Forschungsinstitut fŸr Optik ! ! .....liebchenEraseMEffo.fgan.de ! +------------------------------------------------+

'Error Message in MPLAB'
1996\10\25@091443 by myke predko

Hiya, Last night, I (finally) got in some 17C44s and upgraded the firmware to 1.20.00 on my PICStart Plus. This got rid of the message saying that there is a higher level of PSP Firmware available, but did not get rid of the message: "Open Projects must be rebuilt to properly coordinate device information with PICSTART Plus." What exactly does this mean? I rebuilt ("Build All" under "Projects") the code and even created a new project after installing the new Firmware, but there's no difference. Can anybody help me out here? Thanx, myke Avoiding precedents does not mean nothing should ever be done. It only means that nothing should ever be done for the first time - Sir Humphrey Appleby K.C.B.

'Attn: MPLAB Users: New MPLAB Release'
1996\10\26@003059 by Darrel Johansen

Liebchen Wolfram wrote: {Quote hidden}> > Darrel Johansen wrote: > > > > MPLAB Users: > > > > As promised, here is an announcement for the new MPLAB software, v.3.12. > > You can download this from: > > > > http://www.microchip2.com/softupdt.htm > > Hi Darrel, > > what is the difference between v.3.10.4 and v.3.12 ? > Does it make sense to download? > TIA > > Wolfram > > -- > > +------------------------------------------------+ > ! Wolfram Liebchen, Forschungsinstitut fŸr Optik ! > ! spamliebchenspam_OUT@spam@ffo.fgan.de ! > +------------------------------------------------+ Wolfram and all, The only difference between 3.10.4 and 3.12 is that we omitted the software driver for the 16C715 simulator. If you are not using that device, and you have already downloaded v3.10.4, don't bother with v3.12.

'PROBLEMS WITH MPLAB!'
1996\10\29@142721 by Graversen, Soeren

I have had big problems with my MPLAB. When I tried to open a NEW PROJECT (and many other menu-points) nothing happened.... As far as I see the problem only occurs if PROTEL for Windows is installed on the system. There is a duplicate of a file called: BWCC.DLL The first file is in the MPLAB directory The second is in the WINDOWS directory. Solution: --------- Rename \windows\bwcc.dll --> bwcc.old Copy \MPLAB\bwcc.dll --> \windows\bwcc.dl Please send a mail if any of you have some other experiences/problems running MPLAB. See you around.... Sxren Graversen Denmark Mail: spamgraver@spam@STOPspampost1.tele.dk

1996\10\30@065749 by Philippe TECHER

On Mon, 28 Oct 1996 20:01:44, Graversen Soeren wrote >There is a duplicate of a file called: BWCC.DLL > >The first file is in the MPLAB directory >The second is in the WINDOWS directory. Don't worry, if you want to keep the 2 BWCC.DLL files, just copy the BWCC.DLL for MPLAB into your MPLAB directory (where the EXE file is). By default, a EXE file try to load the DLL wich are in its own directory, if it cannot found the DLL then it try to find it in WINDOWS directory. With this technique, you will keep the 2 versions of BWCC.DLL without any problem. Be carrefull, because if the "Windows" version is loaded by another program, the second version will not be loaded by MPLAB. Anyway, its seems better to keep only the last version of BWCC.DLL, functionnality are exactly same between a version and one other: BWCC functions are: to display Dialog box with Borland style, display message box with Borland style and use also some special Borland control in dialog box. Regards, Philippe <spamBeGoneP.TECHERspamBeGone@spam@icare.fr>.

1996\10\30@125452 by vador Eduardo Tropea (SET)

Sxren wrote: >I have had big problems with my MPLAB. >When I tried to open a NEW PROJECT (and many other menu-points) nothing >happened.... >As far as I see the problem only occurs if PROTEL for Windows is >installed on the system. >There is a duplicate of a file called: BWCC.DLL >The first file is in the MPLAB directory >The second is in the WINDOWS directory. >Solution: >--------- >Rename \windows\bwcc.dll --> bwcc.old >Copy \MPLAB\bwcc.dll --> \windows\bwcc.dl >Please send a mail if any of you have some other experiences/problems >running MPLAB. >See you around.... That's a fault of the programmers of MPLAB, they must ensure that are referencing to your copy of BWCC. And the other faulty people are the Borland designers who made incompatible one lib with the other. SET ******************************************************************************** Salvador Eduardo Tropea (SET) - RemoveMEsalvadorRemoveMERemoveMEinti.edu.ar Work: INTI (National Institute of Industrial Technology) Sector: ICE (Electronic Control & Instrumentation) Post (Home): Curapaligue 2124 - Caseros (1678)- Buenos Aires - Argentina

'Weird MPLAB Simulator Problem'
1996\10\31@155156 by myke predko

Hi Folks, I would appreciate it if Kim Cooper or one of the other Microchip Engineers could look at this problem. I've just spent a frustrating two hours trying to figure out a problem with the MPLAB Simulator. The problem came down to 10 commented out lines in a stimulus file. When I originally created the file, I had commented out the data (for use later) like this: !12345 1 ! Some Comments explaining the Serial Stream !12346 0 !12347 1 Each time I would load this stimulus file, the data changes wouldn't show up and when I tried to leave MPLAB, I would get a GPF error. Other Stimulus Files would load and run fine. When I finally guessed that this was the problem (unfortunately, I complicated it by using DOS E/Edit to create the file and I searched through looking for bad characters), I changed these lines to: ! 12345 1 ! Some Comments explaining the Serial Stream ! 12346 0 ! 12347 1 With the blank after the exclamation, everything worked fine. What was weird about the whole thing was that occasionally, Windows would get trashed as well. Is this documented somewhere or was I just unlucky? Myke Avoiding precedents does not mean nothing should ever be done. It only means that nothing should ever be done for the first time - Sir Humphrey Appleby K.C.B.

'Re[2]: MPLAB crashes Windows 3.1'
1996\11\05@115318 by Darrel Johansen

Roland Andrag wrote: >I am experiencing more or less the same problem - Double click on >icon (hourglass), hard disk starts running, icons disappear. Only >my system does not freeze - I get a General protection fault. Im am >not quite sure what version of MPLAB I have - I downloaded it from >the web site about 1 or two months ago. I have since erased the >installation, all copies of BCCWIN.DLL (or whatever), and >reinstalled it, with the same results. Installation goes fine, no >problems reported. _________________________________________________________________________ ______________________________ Reply Separator _________________________________ Roland, As I asked Ian in his orginal post, download the latest version of MPLAB (v.3.12). There is a known problem with some of the interim released versions that could produce problems like you and he described. It may be that the transfer protocol was not correct, and the .EXE file that he downloaded was corrupted and will not install. We know of no other system problems that would cause general protection faults on start up. If you are still having problems with v.3.12, let us know. Darrel. darrel.johansenKILLspamspammicrochip.com

'Interrupts (17C44) in MPLAB-SIM?'
1996\11\08@070203 by liebchen

Hi all, I have a working program for a 17C44. It uses some interrupt driven routines for sending and receiving characters through serial line and for timers. Although the program runs in real silicon, the simulator doesn't create any interrupts?!? The version of MPLAB is 3.10.??. Is there a known bug in the simulator for 17C44 or do I myself have a bug? Would version 3.12 help? I would appreciate your help! regards Wolfram -- +------------------------------------------------+ ! Wolfram Liebchen, Forschungsinstitut fŸr Optik ! ! spam_OUTliebchen@spam@ffo.fgan.de ! +------------------------------------------------+

'Interupts in MPSIM running under MPLAB'
1996\11\08@161226 by Joe Dowlen

Does anyone know how to generate an interupt in MPSIM while running under MPLAB? Thanks, TakeThisOuTJoe_Dowlenspam_OUTEGGINC.COM

1996\11\11@090750 by liebchen

Joe Dowlen wrote: > > Does anyone know how to generate an interupt in MPSIM while running > under MPLAB? > > Thanks, > > KILLspamJoe_Dowlen.....TakeThisOuTEGGINC.COM Ah, you seem to have the same problem as I do! My program - running with interrupts in real silicon (17C44) - doesn't produce any interrupts while running under MPLAB-Simulator! Can Microchip comment this feature? regards Wolfram -- +------------------------------------------------+ ! Wolfram Liebchen, Forschungsinstitut fŸr Optik ! ! TakeThisOuTliebchenEraseMERemoveMEffo.fgan.de ! +------------------------------------------------+

1996\11\11@095645 by Mike Riendeau

>Joe Dowlen wrote: >> >> Does anyone know how to generate an interupt in MPSIM while running >> under MPLAB? >> >> Thanks, >> >> spam_OUTJoe_DowlenRemoveME.....EGGINC.COM >Ah, you seem to have the same problem as I do! >My program - running with interrupts in real silicon (17C44) - doesn't >produce any interrupts while running under MPLAB-Simulator! >Can Microchip comment this feature? >regards Wolfram >-- I have had some success by halting the program, modifying the appropriate registers, and setting the appropriate interrupt bit(s) using the Special registers window. When you restart the program, the interrupt(s) will occur. I hope this helps. Mike R.

1996\11\11@103153 by Darrel Johansen

Joe, Wolfram, You are correct. The 17C4x family interrupts, as well as some of the 17C4x timers are not functioning correcly in v3.12 of MPLAB-SIM. We'll try to get these fixed as soon as we can and get an interim version posted on the BBS and web site. We apologize for this inconvenience. Perhaps you could go back to an earlier version until we can get this posted. Darrel Johansen spamdarrel.johansenKILLspamKILLspammicrochip.com ______________________________ Reply Separator _________________________________ Subject: Re: Interupts in MPSIM running under MPLAB Author: Liebchen Wolfram <spamliebchenspam_OUTFFO.FGAN.DE> at Internet_Exchange Date: 11/11/96 3:08 PM Joe Dowlen wrote: > > Does anyone know how to generate an interupt in MPSIM while running > under MPLAB? > > Thanks, > > STOPspamJoe_Dowlenspam_OUTspamBeGoneEGGINC.COM Ah, you seem to have the same problem as I do! My program - running with interrupts in real silicon (17C44) - doesn't produce any interrupts while running under MPLAB-Simulator! Can Microchip comment this feature? regards Wolfram -- +------------------------------------------------+ ! Wolfram Liebchen, Forschungsinstitut fŸr Optik ! ! spam_OUTliebchenspamBeGoneffo.fgan.de ! +------------------------------------------------+

'MPLAB + MPLABC'
1996\11\12@024439 by tjaart

Can anyone tell me when Microchip plans to upgrade it's watch windows in MPLAB to include bitflags, long variables, and arrays (like buffers)? Does anyone know when MPLAB C will have stronger bit handling? -- Friendly Regards Tjaart van der Walt ______________________________________________________________ | Another sun-deprived R&D Engineer slaving away in a dungeon | |WASP International GSM vehicle tracking and datacomm solutions| | +27-(0)11-622-8686 | http://wasp.co.za | |______________________________________________________________|

'Help with MPLAB'
1996\11\14@052336 by Maurice De Jersey

Help! My computer I was using MPLAB on crashed* while I was using MPLAB. The result of which I cannot trace a program at source level now when using the simulator, everything else seems fine. Whenever I do a RESET and single step MPLAB brings up the Program Memory Window for single stepping etc. The option in the "Environment Setup" (Ctrl+F7) for tracking source code is checked. Has anyone else had and overcome this problem? Anyone know of a setting to re-enable source level tracing, changing an INI file setting...? Any help would be much appreciated. TIA Maurice *Actually the laptop battery went flat!

1996\11\14@062838 by efoc

Maurice De Jersey wrote: {Quote hidden}> > Help! > > My computer I was using MPLAB on crashed* while I was using MPLAB. The > result of which > I cannot trace a program at source level now when using the simulator, > everything else seems > fine. Whenever I do a RESET and single step MPLAB brings up the Program > Memory Window > for single stepping etc. The option in the "Environment Setup" (Ctrl+F7) > for tracking source > code is checked. > > Has anyone else had and overcome this problem? Anyone know of a setting to > re-enable source > level tracing, changing an INI file setting...? > > Any help would be much appreciated. > > TIA > Maurice > > *Actually the laptop battery went flat! I had this too a few times..... wot I did was to close down the window with the source in it and re-open it again with the FILE->VIEW off the main menu... after this all seemed well. The other think to do is to re-build the project under adeferent name from the project->new menu option Peter ...... -- ================================== = New Ideas come from those who = = didn't know it wasn't possible = ==================================

'How to link multiple files with MPLAB/MPASM?'
1996\11\14@100300 by BLEGER

Hi folks, I'm new to the PIC family of s/w tools, and I'm wondering how to link multiple files. MPLAB Help doesn't say much about the linking process. Here's what I'm trying to do: I have a Project in MPLAB with 3 asm files. I need the first file to originate (org) at 0000h. That's easy. But now I need the next two files to link so that memory is utilized contiguously. Thanks in advance for your assistance. -Brian Leger EraseMEblegerKILLspamharris.com

1996\11\14@125653 by Bob Fehrenbach

BLEGER <EraseMEBLEGERRemoveMEMAILB.HARRIS.COM> wrote: > Hi folks, > > I'm new to the PIC family of s/w tools, and I'm wondering how to link > multiple files. MPLAB Help doesn't say much about the linking > process. Here's what I'm trying to do: I have a Project in MPLAB with > 3 asm files. I need the first file to originate (org) at 0000h. That's > easy. But now I need the next two files to link so that memory is > utilized contiguously. > > Thanks in advance for your assistance. > > -Brian Leger > .....blegerspam_OUTharris.com > ORG the first file at 0. At the bottom of that file add 'include' statements for each of the other two files. The linker for MPASM is not yet available. -- Bob Fehrenbach Wauwatosa, WI @spam@bfehrenbEraseMEspamexecpc.com

1996\11\14@153710 by Craig Knotts

Currently, your only option is to use "#include" files to link the other two files to the original. At this time there is no link facility available for PIC products (as far as I know). ______________________________ Reply Separator _________________________________ Subject: How to link multiple files with MPLAB/MPASM? Author: BLEGERTakeThisOuTKILLspamMAILB.HARRIS.COM at internet Date: 11/14/96 12:35 AM Hi folks, I'm new to the PIC family of s/w tools, and I'm wondering how to link multiple files. MPLAB Help doesn't say much about the linking process. Here's what I'm trying to do: I have a Project in MPLAB with 3 asm files. I need the first file to originate (org) at 0000h. That's easy. But now I need the next two files to link so that memory is utilized contiguously. Thanks in advance for your assistance. -Brian Leger RemoveMEblegerTakeThisOuTharris.com

1996\11\14@190341 by Ed VanderPloeg

Yup, the only currently available method is the "include" control directive, unless someone on the list has made their own thing. Note that it's not "#include" like in C, but just plain old "include" like this: include "filename.inc" ;some header file (macros, etc) org h'0000' ;place for the first file to go include "filename.asm" ;some chunk of code include "filenam2.asm" ;some more code, located in memory immediately after filename.asm And also note that the include's can go anywhere in the file, before or after or in between code, it doesn't matter. Just remember to check your *.lst file for where all the code ended up (like across page boundries, etc.). -Ed V. ______________________________ Reply Separator _________________________________ Subject: Re: How to link multiple files with MPLAB/MPASM? Author: pic microcontroller discussion list <@spam@PICLISTSTOPspamMITVMA.MIT.EDU> at InterNet2 Date: 11/14/96 2:32 PM Currently, your only option is to use "#include" files to link the other two files to the original. At this time there is no link facility available for PIC products (as far as I know). ______________________________ Reply Separator _________________________________ Subject: How to link multiple files with MPLAB/MPASM? Author: TakeThisOuTBLEGERTakeThisOuTRemoveMEMAILB.HARRIS.COM at internet Date: 11/14/96 12:35 AM Hi folks, I'm new to the PIC family of s/w tools, and I'm wondering how to link multiple files. MPLAB Help doesn't say much about the linking process. Here's what I'm trying to do: I have a Project in MPLAB with 3 asm files. I need the first file to originate (org) at 0000h. That's easy. But now I need the next two files to link so that memory is utilized contiguously. Thanks in advance for your assistance. -Brian Leger spam_OUTblegerspam.....harris.com

1996\11\15@035036 by efoc

BLEGER wrote: > > Hi folks, > > I'm new to the PIC family of s/w tools, and I'm wondering how to link > multiple files. MPLAB Help doesn't say much about the linking > process. Here's what I'm trying to do: I have a Project in MPLAB with > 3 asm files. I need the first file to originate (org) at 0000h. That's > easy. But now I need the next two files to link so that memory is > utilized contiguously. > > Thanks in advance for your assistance. > > -Brian Leger > bleger.....@spam@harris.com how about #including them Peter -- ================================== = New Ideas come from those who = = didn't know it wasn't possible = ==================================

'Can't get MPLAB SIM register stimulus file to read'
1996\11\22@101400 by BLEGER

Hello, I filled in the "Register Stimulus" dialog box (file name, PC addr for when xfer is to occur, and the register to be written.) I single stepped through my code while viewing a watch window and saw none of the stimulus file coming in to the register. Always zero. I double checked my file & path. Made a loop for many reads but still see nothing but zero in my register. Using RCREG as the register. Also tried WREG as the register. Bank is set to zero. What am I missing? Brian

1996\11\24@003347 by Wynn Rostek

At 10:10 AM 11/22/96 -0500, you wrote: > Hello, > > I filled in the "Register Stimulus" dialog box (file name, PC addr for > when xfer is to occur, and the register to be written.) > I single stepped through my code while viewing a watch window and saw > none of the stimulus file coming in to the register. Always zero. I > double checked my file & path. Made a loop for many reads but still > see nothing but zero in my register. Using RCREG as the register. Also > tried WREG as the register. Bank is set to zero. What am I missing? > > > Brian > Brian, I'm missing it too. I've tried and tried to get values into PORTA. Nary a peep. Maybe some kind soul that knows how it works can pass along a few hints????? TIA Wynn Rostek spamBeGoneWB4ZUYspam_OUTamsat.org

'Help with MPLAB simulating 17C42A'
1996\12\05@005725 by Callum Jamieson

Hi, I have a problem simulating the 17C42A processor with MPLAB. The symptoms are as follows: I am unable to get timer1, timer2 or timer3 to function correctly. I have Timer0 working fine and was able to generate interrupts from it. I am unable to see tmr1, tmr2 or tmr3l or tmr3h increment in the simulator either during animate mode, or by halting the simulation. I also tried generating interrupts off these timers and was unable to generate interrupts. While I am fairly new to the PIC family I have had experience with other micro-controllers and emulators. Any help either in pointing out a stupid mistake or confirming a bug in the simulator would be appreciated. Here is the test fragment of code I have been using: processor 17C42a #include "p17c42a.inc" org 0 ; Here at power on reset. Goto Reset org 8h ; Here for external interrupt on RA0 Retfie org 10h ; Here for TMR0 overflow interrupt Retfie org 18h ; Here for external interrupt on T0CKI Retfie org 20h ; Here for peripherals PEIF Nop Retfie Reset ;Here at power on reset. ; Test code starts here Movlb 2 Movlw h'80' Movwf PR1 Movwf PR2 Movwf PR3L Movwf PR3H Movlb 3 ;Setup timer 1, 2, 3 to increment from internal clock. Movlw b'00000000' Movwf TCON1 ;Set timer 1, 2 and 3 run flags. Movlw b'00000111' Movwf TCON2 Main Nop Goto Main end I would expect by running this program using the animate mode or halting simulation I would be able to see the timers clocking. This is certainly the behaviour I have with timer0. Thank you, Callum. ----------------------------------- Callum Jamieson ADInstruments P.O Box 6320, Dunedin, New Zealand Ph (03) 477 4646 Fax (03) 477 4346 -----------------------------------

1996\12\05@034345 by Wolfram Liebchen

At 19:03 05.12.96 +0000, Callum wrote: >Hi, > >I have a problem simulating the 17C42A processor with MPLAB. > >The symptoms are as follows: > >I am unable to get timer1, timer2 or timer3 to function correctly. >I have Timer0 working fine and was able to generate interrupts from >it. Callum, there is a bug in the simulator software for PIC17C4x since some MPLAB releases, that prevents timers from working correctly. I already told Microchip the problem, and they sent me a fixed version of MPLAB-SIM for 17Cxx in private e-mail (for MPLAB-version 3.12). I will send you this package in private eMail (I hope Microchip won't blame me for that!). regards Wolfram +-----------------------------------------------------+ | Wolfram Liebchen | | Forschungsinstitut fŸr Optik, TŸbingen, Deutschland | | EraseMEliebchen.....ffo.fgan.de | +-----------------------------------------------------+

1996\12\05@100250 by Darrel Johansen

Wolfram Liebchen <spamliebchenKILLspam@spam@FFO.FGAN.DE> writes: >there is a bug in the simulator software for PIC17C4x since some >MPLAB releases, that prevents timers from working correctly. >I already told Microchip the problem, and they sent me a fixed >version of MPLAB-SIM for 17Cxx in private e-mail (for MPLAB-version >3.12). I will send you this package in private eMail (I hope >Microchip won't blame me for that!). Wolfram, We have no problems with the distribution of the MPLAB-SIM 17C4xx updates. People should note that these are what we call "dot" releases, software fixes that are not as robustly tested as our full release. Unfortunately the timers were not re-tested after some minor changes in the last release, so this bug slipped out. If anybody else would needs advnace copies this software, I'd be glad to privately mail the software. We'll post it on the 'net and BBS next week. Note that you *must* have MPLAB v3.12 to use these drivers. Darrel Johansen Microchip Technology, Inc. darrel.johansenspamTakeThisOuTmicrochip.com ______________________________ Reply Separator _________________________________ Subject: Re: Help with MPLAB simulating 17C42A Author: Wolfram Liebchen <RemoveMEliebchenRemoveMEFFO.FGAN.DE> at Internet_Exchange Date: 12/5/96 9:45 AM At 19:03 05.12.96 +0000, Callum wrote: >Hi, > >I have a problem simulating the 17C42A processor with MPLAB. > >The symptoms are as follows: > >I am unable to get timer1, timer2 or timer3 to function correctly. >I have Timer0 working fine and was able to generate interrupts from >it. Callum, there is a bug in the simulator software for PIC17C4x since some MPLAB releases, that prevents timers from working correctly. I already told Microchip the problem, and they sent me a fixed version of MPLAB-SIM for 17Cxx in private e-mail (for MPLAB-version 3.12). I will send you this package in private eMail (I hope Microchip won't blame me for that!). regards Wolfram +-----------------------------------------------------+ | Wolfram Liebchen | | Forschungsinstitut fŸr Optik, TŸbingen, Deutschland | | TakeThisOuTliebchen@spam@@spam@ffo.fgan.de | +-----------------------------------------------------+

'Re[2]: MPLAB question: How to stimulate pin with s'
1996\12\12@093323 by Darrel Johansen

Dmitry Kiryashov writes: >So Step parameter mean points of time when RC7 parameter take next value, for >example above at start moment (time=1) RC7=0 , at time=5 RC7=1 , at time=7 >RC7=0 ,i.e. parameter Step means absolute value when pin take next value ? >Or maybe parameter Step mean relative value - i.e after start pin RC7=0 during >step=1 , RC7=1 during step=5 and so on ... >WBW Dmitry. >P.S. If someone have detailed documentation about internal format of stimulus >file please attach me it with reply letter . An update to MPLAB-SIM was posted on the Microchip BBS and should be on the web page as well (http://www.microchip.com). The file called README.LAB in this update has an expanded section on the stimulus files for the simulator and should answer all your questions. This update is a fix for the timers in the 17c4x family which were not functioning in the last release.

'networked MPLAB ?'
1997\01\23@072523 by all (Stephen Birchall)

has anyone been able to install MPLAB into a network environment ? is there a network version available ? thanx in advance for any info Steve

1997\01\23@075436 by eter J. (GEA, 068974 )

Steve, Perhaps you can create a WINDOWS\SYSTEM directory on your network drive prior to installation. This worked for my network configuration, but I don't know the details of yours.....yet. -Pete {Quote hidden}>---------- >From: Stephen Birchall (Stephen Birchall)[SMTP:TakeThisOuTN.S.BirchallspamLBORO.AC.UK] >Sent: Thursday, January 23, 1997 7:21AM >To: Multiple recipients of list PICLIST >Subject: networked MPLAB ? > >has anyone been able to install MPLAB into a network environment ? > >is there a network version available ? > >thanx in advance for any info > >Steve >

'Long Variables in MPC or MPLABC'
1997\02\03@090021 by tjaart

Hi All! Here's my problem : I want to copy a 'long' variable to into two useable bytes (high and low). MPLABC and MPD doesn't allow access to the byte at the higher address, so I am forced to do it in assembly. The problem, however comes in when the variable moves into another bank, so I have to re-check the validity of all the assembly sections after compilation. Yuck. Is there an easier way? -- Friendly Regards Tjaart van der Walt ______________________________________________________________ | Another sun-deprived R&D Engineer slaving away in a dungeon | | WASP International | | GSM and GPS value-added applications | |+27-(0)11-622-8686 | http://wasp.co.za | KILLspamtjaartKILLspamspamBeGonewasp.co.za | |______________________________________________________________|

1997\02\03@153933 by Andrew Warren

Tjaart van der Walt <spamBeGonetjaartKILLspamwasp.co.za> wrote: > I want to copy a 'long' variable to into two useable bytes (high and > low). MPLABC and MPD [sic] doesn't allow access to the byte at the higher > address, so I am forced to do it in assembly. The problem, however > comes in when the variable moves into another bank, so I have to > re-check the validity of all the assembly sections after > compilation. Yuck. > > Is there an easier way? Tjaart: Yeah, there is. You can even arrange things so that each BIT in a long (16-bit) variable is accessible. First, to make the code easy to read, do a couple of typedefs: typedef unsigned char byte; typedef unsigned long word; Next, define two structures... One is a pair of bytes; the other is a pair of what MPC calls "bits" (newer versions of MPC may make the "bits" thing unnecessary). struct both_bytes { byte hi; byte lo; }; struct bits_16 { bits hibits; bits lobits; }; Finally, set up unions of the various structures. The first one allows access to a long variable either as a 16-bit or an 8-bit value; the second one adds access to each of the 16 bits, too. union w_and_b { word w; struct both_bytes b; }; union all_three { word w; struct both_bytes b; struct bits_16 b16; }; Ok... When you allocate space for your variables, do it like this: union w_and_b two_way; // "two_way" can be accessed as // either a 16-bit word or two // individual bytes. union all_three three_way; // "three_way" can be accessed as a // 16-bit word, two individual // bytes, or 16 individual bits. To use the variables, do this: two_way.w = 65000; // To access two_way as a 16-bit // word, append ".w". if (two_way.b.hi) {}; // To access two_way's high byte, // append ".b.hi". two_way.b.lo &= 0xF0; // To access two_way's low byte, // append ".b.lo". // three_way works the same as above, but adds the following: three_way.b16.lobits.4 = 1; // To access a bit in three_way's // low byte, append // ".b16.lobits.x", where "x" is // the bit number [0-7]. if (three_way.b16.hibits.7) // To access a bit in three_way's { }; // low byte, append // ".b16.hibits.x", where "x" is // the bit number [0-7]. Of course, you may want to change the names of the structures and unions. The bit-access union (used for "three_way" in the above examples) is kinda clunky... I expect that newer versions of MPC/MPLABC will provide better built-in bit access, so the multi-level structures that I've shown won't be necessary. -Andy === Andrew Warren - fastfwd@spam@KILLspamix.netcom.com === === Fast Forward Engineering - Vista, California === === === === Did the information in this post help you? Consider === === contributing to the PICLIST Fund. Details are at: === === http://www.geocities.com/SiliconValley/2499/fund.html ===

'Can't get MPLAB SIM pin stimulus'
1997\02\11@102421 by Alberto Rodella

Hello, I'm trying to use the MPLAB simulator. I filled the file for pin stimulus. I single stepper through my code while viewing the watch window and I saw none of stimulus file coming in to the port. Is there someone that can suggest me what I'm missing? Any help will be appreciated.

1997\02\12@033531 by Marc Schmaeche

>Hello, >I'm trying to use the MPLAB simulator. >I filled the file for pin stimulus. I single stepper through my code while >viewing the watch window and I saw none of stimulus file coming in to the >port. Is there someone that can suggest me what I'm missing? >Any help will be appreciated. I've made similar experience that MPLAB might fail (without any error message) if there are any unexpected characters in the stimulus file. Also make sure that there are no blank lines contained in the stimulus file not even at the end of file. Regards, Marc Schmaeche ZAM-AZN Am Weichselgarten 7 91058 Erlangen (Germany) E-mail: EraseMEmsRemoveME@spam@zam.nf.fh-nuernberg.de (Ger/Eng/Spa welcome)

'more and more MPLAB-C bugs'
1997\02\13@023259 by Marc Schmaeche

Hi PIC fans, I'm also suffering from several MPLAB-C bugs! But is there a better solution than MPLAB-C available, that is a R E L E A S E D C-compiler with sufficient - code-efficiency, - mixing C and ASM, - HLL-debugging support? >Tjaart van der Walt wrote: >The official Microchip line I received was : >"We don't want to release untested software to paying customers." It's hard to believe that the actual version of MPLAB-C V1.10 is thoroughly tested! >The reality is, however, that all the MPLABC users are also paying for >time spent wondering what the heck is going wrong in their PIC code, Just another MPLAB-C bug: compact but wrong code!!! 037C 2003 CALL 0003h temp_var = 6 + GetValueFromRom() - temp_var; 037D 3E06 ADDLW 06h 037E 02BD SUBWF 3D >and some of us (hint, hint) are MORE than willing to test beta versions. Yes, I also would like to test a new beta! Regards, Marc Schmaeche ZAM-AZN Am Weichselgarten 7 91058 Erlangen (Germany) E-mail: RemoveMEmsspamEraseMEzam.nf.fh-nuernberg.de (Ger/Eng/Spa welcome)

'new release of MPLAB-C ???'
1997\02\13@023453 by Marc Schmaeche

>Matthew wrote: > I started with V1.10 of MPLAB and have upgraded to V1.40 or something >like that I cannot remember. That seemed to take care of most of my >problems with the W register. You can get the newest version at >http://www.microchip.com Isn't this release V1.40 a limited version? Regards, Marc Schmaeche ZAM-AZN Am Weichselgarten 7 91058 Erlangen (Germany) E-mail: STOPspamms.....zam.nf.fh-nuernberg.de (Ger/Eng/Spa welcome)

'undocumented option for MPLAB-C'
1997\02\13@045356 by Marc Schmaeche

Dear Tjaart, >> Hi PIC fans, >> >> I'm also suffering from several MPLAB-C bugs! But is there a better solution >> than MPLAB-C available, that is a R E L E A S E D C-compiler with >> sufficient >> - code-efficiency, >> - mixing C and ASM, >> - HLL-debugging support? > >Try this : >Sit down and pour yourself a stiff one. >Import your list file into a word proc package. Do a word count on bsf >3.5, and bcf 3.5 >I get up to 20% of my precious code space littered with RAM switching. >SIS! YUCK! I've had the same problem and I got a hint from microchip. If you (almost) only need bank0 try: #pragma option j7 This suppresses all the unnecessary bsf 3.5, and bcf 3.5! But .... You then have to take care of the Bits RP0, RP1 by yourself (for accessing TRIS-Registers and so on)! Nevertheless it's a nice workaround; but using the option j7 the compiler seems to get stuck sometimes. Regards, Marc Schmaeche ZAM-AZN Am Weichselgarten 7 91058 Erlangen (Germany) E-mail: spamBeGonemsRemoveMERemoveMEzam.nf.fh-nuernberg.de (Ger/Eng/Spa welcome)

'Any forum for C code for MPLAB_C?'
1997\02\18@232142 by jmillien

Gentlemen: I need to make the transition from assembly to C. I am using the MPLAB-C. Is there any place where I can get help on how to implement simple programs in C. I usually start by writing code to toggle output ports, implement timer interrupts. Should any one, using the MPLAB-C, have some thing that could get me started, I would deeply appreciated it. Thanks JeanM. ...True Knowledge knows no bounderies...

'The MPLABC upgrade -> reportback'
1997\03\06@030307 by tjaart

Hiya fellow MPLABC users! I have at long last succeeded in 'upgrading' MPLABC with the patch offered by Microchip. The only difference I could see, was that ver 1.21 (the 'new' version) gives mysterious syntax errors that have to be disabled with the /s- switch. There is *absolutely* no difference in code inefficiency between 1.1 and 1.21 I did a word count on BSF 05.3 and BCF 05.3 in the List file for a 16C74 and discovered a whopping 761 ocurrences in the used 4073 bytes of ROM space. That means 18% of the code space is taken up by *mostly* unnecessary RAM page switching. Geez - will MPLABC users get a 18% discount on PIC parts ? I think not! HEY MICROCHIP! YOOOHOOOO!!! -- Friendly Regards Tjaart van der Walt @spam@tjaartspamBeGonewasp.co.za _____________________________________________________________ | Another sun-deprived R&D Engineer slaving away in a dungeon | | WASP International http://wasp.co.za | | GSM and GPS value-added applications | | Voice : +27-(0)11-622-8686 | Fax : +27-(0)11-622-8686 | |_____________________________________________________________|

'undocumented option for MPLAB-C (V1.10)'
1997\03\06@073442 by Marc Schmaeche

Dear Tjaart, I've had the same trouble with the the unnecessary bsf 3.5, and bcf 3.5 and I got a hint from microchip (which works at least on MPLAB-C V1.10). Just try: #pragma option j7 This suppresses all the unnecessary bsf 3.5, and bcf 3.5. But .... You then have to take care of the Bits RP0, RP1 by yourself (for accessing TRIS-Registers and so on)! That's fine if you just (almost) use bank 0. So if you're using different ram banks it will become a little bit tricky, because you've to take care of all the bank-switching (that is setting & clearing Bit RP0 by yourself). But I suppose it's worth the effort if you need to save ROM. Nevertheless it's a nice workaround; but using the option j7 the compiler seems to get stuck sometimes. Best regards, Marc Schmaeche ZAM-AZN Am Weichselgarten 7 91058 Erlangen (Germany) E-mail: spam_OUTmsspamzam.nf.fh-nuernberg.de (Ger/Eng/Spa welcome)

'The MPLABC upgrade -> reportback'
1997\03\06@135651 by Andrew Warren

Tjaart van der Walt <spamtjaartspamspamwasp.co.za> wrote: > I have at long last succeeded in 'upgrading' MPLABC with the patch > offered by Microchip. The only difference I could see, was that ver > 1.21 (the 'new' version) gives mysterious syntax errors that have to > be disabled with the /s- switch. There is *absolutely* no difference > in code inefficiency between 1.1 and 1.21 Correct. As far as I know, the only difference between the two is that 1.21 includes a text-file that shows workarounds for all the known bugs. -Andy === Andrew Warren - spamBeGonefastfwdKILLspamKILLspamix.netcom.com === Fast Forward Engineering, Vista, California === http://www.geocities.com/SiliconValley/2499

'This blasted MPLAB software'
1997\03\12@140544 by Frank A. Vostenbosch

Hi, I've been trying to use this MPLAB thing with a 12C508/JW (the UV erasable one) and can't get it to program the "MOVLW 0x30" into location 0x1ff. My program has an org 0x1ff movlw 0x30 at the end, and even when I specify programming calibration memory it still comes out as XORLW 0xFF. Also, when I try to use __idlocs this enters data at addresses 0x1ff, 0x200, 0x201 and 0x202 which obviously can't be right (although I don't know where they should go). This is using MPLAB 3.12 which internally uses MPASM(WIN) 01.40. Any help? Frank ------------------------------------------------------------------------ Frank A. Vorstenbosch Phone: +44-181-941 7899 Electronics & Software Engineer Mobile: +44-976-430 569 Eidos Technologies Ltd., Hampton, Middx Fax: +44-181-941 7895

1997\03\12@154357 by Todd Peterson

At 05:18 PM 3/12/97 +0000, you wrote: >Hi, > >I've been trying to use this MPLAB thing with a 12C508/JW (the UV erasable >one) and can't get it to program the "MOVLW 0x30" into location 0x1ff. >My program has an > org 0x1ff > movlw 0x30 >at the end, and even when I specify programming calibration memory it >still comes out as XORLW 0xFF. Yes, it took me about a week of investigating to get to the bottom of this one. Check the back list of the PICLIST for more details. It turns out, as verified by Microchip, that there is a flaw in MPLAB. You must switch to 'editor only' mode or else that location won't program. I am hopeful that this bug will be fixed; the man at Microchip that I spoke with said he would turn it over to the programmers. Let me know if you need any more assistance; all works fine for me when you remember to switch to 'Editor Only'. -Todd .--------------------------------------------------------------. / .-. E-Lab Digital Engineering, Inc. .-. \ | / \ Embedded Control & Integrated Circuit Solutions / \ | | \_. | | / | |\ | /| http://www.netins.net/showcase/elab |\ | /| | `---' | | `---' | | |Inquire about our EDE700 Serial LCD Screen Driver!| | | | (712) 944-5344 FAX:(712) 944-5501 | | | |--------------------------------------------------| | \ / \_____/ `---'

'Beta Release of MPLAB v3.20'
1997\03\14@191655 by Darrel Johansen

MPLAB v3.20 beta release is available on the WWW (should be posted by the end of the day) and Microchip BBS site (now, in the INT-REL directory). This version is numbered v3.12.14 until official release. MPLAB has these new features: £ PRO MATE device programmer support £ New parts support: £ PIC12C671/672 - MPASM £ PIC16C642/662 - MPASM, MPLAB-SIM, PICMASTER, PICSTART Plus, PRO MATE £ PIC16C66/67/76/77 - MPASM, MPLAB-SIM, PICMASTER, PICSTART Plus, PRO MATE £ PIC17C752/756 - MPASM, MPLAB-SIM, PICSTART Plus, PRO MATE £ PIC16C715 - PICMASTER (PIC16C715 support already exists in other tools) £ Improvements to PICSTART Plus user interface £ Retention of previous tool bar customizations £ 16-bit and 1-bit watch windows £ Stimulus file disable £ Improved Help files £ Many fixes for reported problems MPLAB v3.12.14 fixes the following reported problems with previous versions: - Various data problems using the PICSTART Plus with MPLAB-SIM and PICMASTER emulator. Data was not always updated or presented correctly. - All memory is cleared when changing processors or before importing the object code from a new project. MPLAB v3.12.14 still has the following known problems: - Processor configuration bits set in source code do not change the corresponding emulator/simulator processor mode. - No warnings are issued when loading hex files that are out of range or contain data with more bits than supported by current processor. We would request constructive feedback about this latest version. We rate problems according to these categories: £ 1. System crash £ 2. Serious problem, --no easy work around £ 3. Problem, --work-around available £ 4. Design request --"it would be nice" £ 5. Can't duplicate --document, so we don't forget about it FYI, we have no known level 1's or 2's, a few 3's (those listed above), and we've got a lot of #4's. If we had all the time in the world, we would like to address them (or even debate the ones that are contradictory with other requests). We're more interested in what you need to get your jobs done. If you can't use MPLAB to easily and quickly simulate, emulate, or program your Microchip PIC devices, please let us know immediately. Private post directly (but depending upon the number of messages, don't expect an immediate response). Faster responses are possible on the Microchip BBS.

1997\03\15@102843 by Darrel Johansen

1997\03\16@234227 by tjaart

Darrel Johansen wrote: > > > MPLAB v3.20 beta release is available on the WWW (should be posted by > the end of the day) and Microchip BBS site (now, in the INT-REL > directory). This version is numbered v3.12.14 until official release. > > Hooooooooooooooorrrrrrrrrraaaaaaaaaayyyyyyyy!!!!!!!!!!! Not only is there an update, but someone at Microchip is actually accepting responsibility for MPLAB. Man! What a way to start on a Monday morning! This is going to be a fine week indeed. -- Friendly Regards Tjaart van der Walt TakeThisOuTtjaartspamwasp.co.za _____________________________________________________________ | Another sun-deprived R&D Engineer slaving away in a dungeon | | WASP International http://wasp.co.za | | GSM and GPS value-added applications | | Voice : +27-(0)11-622-8686 | Fax : +27-(0)11-622-8686 | |_____________________________________________________________|

1997\03\17@053235 by Wolfram Liebchen

At 08:22 15.03.97 -0700, you wrote: > We would request constructive feedback about this latest version. We > rate problems according to these categories: > £ 1. System crash > £ 2. Serious problem, --no easy work around > £ 3. Problem, --work-around available > £ 4. Design request --"it would be nice" > £ 5. Can't duplicate --document, so we don't forget about it > > Private post directly (but depending upon the number of messages, > don't expect an immediate response). Faster responses are possible on > the Microchip BBS. Darrel, there is another problem of kind 3: When using international keyboards (the ones with an ALT-GR key on the right side), you cannot acces the characters, that need the ALT-GR key. On a German keyboard, this covers the characters "[ ] { } \ ~ |". The workaround is, to use the charmap-applet via clipboard. Somewhat annoying. I think, software recognises the ALT-GR as CTRL + ALT. Regards, Wolfram +-----------------------------------------------------+ | Wolfram Liebchen | | Forschungsinstitut fŸr Optik, TŸbingen, Deutschland | | spamBeGoneliebchenffo.fgan.de | +-----------------------------------------------------+

1997\03\24@051236 by Bruno Rodeghiero

At 17.17 14/03/97 -0700, Darrel Johansen wrote: > FYI, we have no known level 1's or 2's, a few 3's (those listed > above), and we've got a lot of #4's. If we had all the time in the > world, we would like to address them (or even debate the ones that are > contradictory with other requests). We're more interested in what you > need to get your jobs done. If you can't use MPLAB to easily and > quickly simulate, emulate, or program your Microchip PIC devices, > please let us know immediately. Hello! I am using the new release on WIN95 + 486/100 32Meg.. There are a pair of annoyances I hoped fixed in the new release (and weren't): 1) SAVING THE ASYNC STIMULUS SETTINGS WITH THE PROJECT !!!!!!!!!!!!!!!!!!!!!!!! 2) Use smaller keys in async window( more space on the screen..) 3) Being able to put that damned window in the background or minimize it !!! An icon on the toolbar could recall easily with SHOW/NoSHOW function : 4) The same for the StopWatch ! The screen is already crowded with a lot of things, why the window must be so large with target frequency always visible? normally that is a fixed value on a project, elapsed time and cycle count is enough... The use of a Key on the toolbar only to ENABLE the window (function WindowStopWatch) is USELESS if it can only ENABLE and NOT HIDE IT. I suggest an ON/OFF function. And the window should remember WHERE to pop-up, as the watch windows and the Async stimulus... 5) Of course it's difficult, but I am homesick of JRN file on MPSIM... it was easy to resume the work from the same point we stopped in the last debugging session... I'm using MPLAB on 800x600 screen, I think I will buy soon a greater Monitor or new glasses.. Thanks.. ================================ Bruno Rodeghiero i3RGH Bassano del Grappa (VI) ITALY E-Mail: EraseMEbrurodegEraseMEtin.it ================================

1997\03\24@100225 by Robert Zeff

part 0 712 bytes Thanks, \\\|/// \\ ~ ~ // ( @ @ ) --------------oOOo-(_)-oOOo--------------- | | | Robert Zeff | | Nikola Engineering | | 209-577-4268 x101 | | spamBeGonerzeffspam_OUT.....nikola.com | | Free Spice for Windows NT / Win95: | | WWW: http://Nikola.com | | | ----------------------Oooo.--------------- .oooO ( ) ( ) ) / \ ( (_/ \_)

'Beta Release of MPLAB v3.20 - BUG ?'
1997\03\26@051837 by Bruno Rodeghiero

Hello! I think new MPLAB beta release corrupts the CFG file of the project. I have the project files in E:\MPLAB\PROJECTS\TX32. While I use the 3.12 version it works OK. This is the TX32.CFG File with 3.12: ------- [Windows] 10=0020 516 8 806 208 9 0 9=0002 E:\mplab\projects\tx32\Bank3.wat 508 151 815 357 9 0 8=0001 -123 333 500 479 9 0 7=0002 e:\mplab\projects\tx32\Bank0_0.wat -2 3 258 153 9 0 6=0002 E:\mplab\projects\tx32\Bank2.wat 503 318 763 488 9 0 5=0000 E:\mplab\projects\tx32\tx32.asm 12 130 635 276 2 4 4=0002 E:\mplab\projects\tx32\Bank1_0.wat 256 2 519 169 9 0 3=0002 E:\mplab\projects\tx32\Bank1_1.wat 255 172 518 323 9 0 2=0000 E:\mplab\projects\tx32\auto_pg.inc 549 423 876 501 9 0 1=0002 E:\mplab\projects\tx32\Bank0_1.wat -1 153 259 340 9 0 0=0200 547 356 821 434 9 4 Stopwatch=557 271 783 422 9 0 ------- If I use new Beta-version and I save the project as soon as I start, I get the following TX32.CFG: [Windows] 10=0020 516 8 806 208 9 0 9=0002 e:\mplab\projects\tx32\e:\mplab.wat 508 151 815 357 9 0 8=0001 -123 333 500 479 9 0 7=0002 e:\mplab\projects\tx32\e:\mplab.wat -2 3 258 153 9 0 6=0002 e:\mplab\projects\tx32\e:\mplab.wat 503 318 763 488 9 0 5=0000 e:\mplab\projects\tx32\tx32.asm 12 130 635 276 2 4 4=0002 e:\mplab\projects\tx32\e:\mplab.wat 256 2 519 169 9 0 3=0002 e:\mplab\projects\tx32\e:\mplab.wat 255 172 518 323 9 0 2=0000 e:\mplab\projects\tx32\auto_pg.inc 549 423 876 501 9 0 1=0002 e:\mplab\projects\tx32\e:\mplab.wat -1 153 259 340 9 0 0=0200 547 356 821 434 9 4 Stopwatch=557 271 783 422 9 0 ------- As you can see, the watch windows have a truncated name, and there is the disk name in the path !!! So if I reload the project I dont't see the watch windows, only the ASM and the INC files, whose name is correct.. Best regards... ================================ Bruno Rodeghiero i3RGH Bassano del Grappa (VI) ITALY E-Mail: spambrurodegtin.it ================================

'Help - 16C84 1K memory -> MPLab bug?'
1997\04\03@030752 by Rob Santello

Myke, >I noticed this to with the latest version of MPLAB (3.12.14). According to >MPLAB, the 16C84 only seems to have 512 Instructions. Exactly what I'm seeing here, thanks for the confirmation, I was going nuts trying to figure out what I was doing wrong. Wasted hours! I even thought there might be a problem with MPLab so I checked their web site and found a new release 3.22.00. This did not fix the problem. I even tried to compile and run as a 16F84, same error. Man, I hate it when this happens! At least I don't have to kick myself ... yet. So, Microchip ... what's up? --rob-- {Quote hidden}>The other problems I noticed were: > >1. Sometimes on pulling up a project, the right side of the Stopwatch is >cut off (to the edge of the window beside it - even if it doesn't show up >(see the next problem)). > >2. Sometimes on bringing up a project, if a custom watch window has been >created for it, the watch window didn't come up. > >I didn't report these problems earlier because I am only running 3.12.14 on >a laptop running Windows 3.11 (that I'm having some hard drive problems) >and I wasn't sure the problems were in MPLAB, or in the laptop. >>>Ok, this should be an easy one for you guys. I'm sure it's something >>>simple (stupid) I'm over looking. Why is it that MPLab will not program >>>the C84 beyond 512 bytes? My program compiles fine but when I simulate it, >>>as soon as it hits step 0x01FF it jumps back to step 0. There is 1K of >>>memory space right? What am I missing?

1997\04\03@181459 by Darrel Johansen

Rob Santello writes: >>I noticed this to with the latest version of MPLAB (3.12.14). According to >>MPLAB, the 16C84 only seems to have 512 Instructions. >Exactly what I'm seeing here, thanks for the confirmation, I was going >nuts trying to figure out what I was doing wrong. Wasted hours! I even >thought there might be a problem with MPLab so I checked their web site >and found a new release 3.22.00. This did not fix the problem. I even >tried to compile and run as a 16F84, same error. >So, Microchip ... what's up? The latest version of MPLAB-SIM for the 16C84 is really for the 16C83, hence it has only 512 words of program memory. We are going to post an update. In the meantime, we suggest selecting the 16F84. This can be used to simulate the 16C84 until the fix is available. If you are programming 16C84 devices with the PRO MATE or PICSTART Plus, switch to "Editor Only" mode and then use the 16C84 as selected on the programmer dialog. Switch back to the 'F84 to simulate. We posted this info yesterday, but I'm not sure that it got through to the PICLIST. Darrel Johansen

'Missing ROM for 16C84 in MPLAB 3.22.00'
1997\04\22@015212 by Brent Miller

I have been working on a 16C84 project using the latest MPLAB, version 3.22.00. I have not had any success using addresses beyond 1FF in the simulator. The ROM window only lists addresses 0-1FF, and any GOTO to labels beyond 1FF wraps to the 0-1FF range. Simulating the same code in an older version (3.09.10) works fine. Has anyone else seen this problem? What am I doing wrong? TIA. Brent Miller

1997\04\22@020910 by Andrew Warren

Brent Miller <RemoveMEPICLISTKILLspamKILLspamMITVMA.MIT.EDU> wrote: > I have been working on a 16C84 project using the latest MPLAB, > version 3.22.00. I have not had any success using addresses > beyond 1FF in the simulator. The ROM window only lists addresses > 0-1FF, and any GOTO to labels beyond 1FF wraps to the 0-1FF range. > > Simulating the same code in an older version (3.09.10) works fine. > Has anyone else seen this problem? What am I doing wrong? Brent: You're doing nothing wrong; it's a bug in version 3.22. Microchip knows about it and is working on (or has already completed) a fix. -Andy === Andrew Warren - EraseMEfastfwdspamBeGonespamix.netcom.com === Fast Forward Engineering, Vista, California === http://www.geocities.com/SiliconValley/2499

1997\04\22@101337 by Darrel Johansen

Andrew Warren wrote: > > Brent Miller <KILLspamPICLISTMITVMA.MIT.EDU> wrote: > > > I have been working on a 16C84 project using the latest MPLAB, > > version 3.22.00. I have not had any success using addresses > > beyond 1FF in the simulator. The ROM window only lists addresses > > 0-1FF, and any GOTO to labels beyond 1FF wraps to the 0-1FF range. > > > > Simulating the same code in an older version (3.09.10) works fine. > > Has anyone else seen this problem? What am I doing wrong? > > Brent: > > You're doing nothing wrong; it's a bug in version 3.22. Microchip > knows about it and is working on (or has already completed) a fix. > .. In the mean time, select the 16F84 for development. Differences are very minor, and won't affect simulation of the part. Darrel

'Known bug in MPLAB 3.22 ?'
1997\04\23@102011 by Bruno Rodeghiero

Hello dear PicListers, I'm working with a project involving a PIC16C57 using MPLAB simulator (NO EMULATOR, here). :-((( Perhaps I got a BUG, I dont'know if it' already a known one.. When I put (or I forget I had put ) a breakpoint - with the mouse right-button or with the Breakpoint Setting Window - in a Subroutine, if I use STEP OVER key in the main - trying to jump over the subroutine - the program will _not_ stop at the breakpoint, and, when the program returns to the main program, in the STACK window I still see the subroutine address.( call OxZZ ). Furthermore, the values in the register are those active at the Breakpoint, not those at the RETLW ..... I think MPLAB-SIM uses the breakpoint as a "Return" code.. If the sub address does'nt pop out from the SIMULATOR stack, next time I will use - in my program - a double CALL I will get a STACK OVERFLOW error. I was lucky, because I didn't yet realized that the STEPPED-OVER subroutine doesn' behave as the STEPPED-IN until I went hunting for that misterious error.. Perhaps this problem could be happening only simulating a PIC16C57 ? I developed also a very simple Test program ( only some NOP and a couple of CALL ) and I got the same result so it is not in my code. In my analysis, there are two conflicting command to MPLAB (STEP_OVER and BREAK ) but I think that it shouldn't happen , simply the Break should be executed anyway and the STEP_OVER used as a RUN_TO_BREAKPOINT command... Any comment from some PIC guru would be appreciated.. even to say that it's my fault. TIA ================================ Bruno Rodeghiero i3RGH Bassano del Grappa (VI) ITALY brurodegspam_OUTspamtin.it ================================

'Bug In MPLAB 3.22 ?'
1997\05\04@133150 by Bruno Rodeghiero

>Date: Tue, 29 Apr 1997 10:52:06 -0700 >From: darrel.johansenspam@spam@Microchip.COM (Darrel Johansen) >Subject: Re: Bug In MPLAB 3.22 ? > > Bruno, > Yes, you've found a bug. We'll put it on the schedule to fix it. > Thanks, > > Darrel > >______________________________ Reply Separator _________________________________ {Quote hidden}>Subject: Bug In MPLAB 3.22 ? >Author: Bruno Rodeghiero <spamBeGonebrurodeg.....tin.it> at Internet_Exchange >Date: 4/28/97 11:01 PM > > >****** Copy of the message sent to the PICLIST ******* ><snip> > >Perhaps I got a BUG, I dont'know if it' already a known one.. > >When I put (or I forget I had put ) a breakpoint - with the mouse >right-button or with the Breakpoint Setting Window - in a Subroutine, >if I use STEP OVER key in the main - trying to jump over the subroutine >- the program will _not_ stop at the breakpoint, and, when the program >returns to the main program, in the STACK window I still see the >subroutine address.( call OxZZ ). > >Furthermore, the values in the register are those active at the >Breakpoint, not those at the RETLW ..... I think MPLAB-SIM uses the >breakpoint as a "Return" code.. > >If the sub address does'nt pop out from the SIMULATOR stack, next time >I will use - in my program - a double CALL I will get a STACK OVERFLOW error. > >I was lucky, because I didn't yet realized that the STEPPED-OVER >subroutine doesn' behave as the STEPPED-IN until I went hunting for >that misterious error.. > >Perhaps this problem could be happening only simulating a PIC16C57 ? > >I developed also a very simple Test program ( only some NOP and a >couple of CALL ) and I got the same result so it is not in my code. > >In my analysis, there are two conflicting command to MPLAB (STEP_OVER >and BREAK ) but I think that it shouldn't happen , simply the Break >should be executed anyway and the STEP_OVER used as a RUN_TO_BREAKPOINT >command... > ><snip> > >Dear Darrel >I had no answer to this message, but I think that IT IS A BUG.. AND >VERY ANNOYING, TOO. > ------------- Copy of Private message for the PICLIST.. Have fun. ================================ Bruno Rodeghiero i3RGH Bassano del Grappa (VI) ITALY .....brurodeg@spam@tin.it ================================

'stack overflow error in MpLab'
1997\05\05@041114 by FrankT

For those guys who followed my story on the interrupt problems I had, here's the next chapter. After a few mails to the piclist and some great help I came up with the next piece of code. void __INT(void) { if(PIR1.SSPIF) { PIR1.SSPIF = FALSE; // Clear I2C interrupt flag INTCON.GIE = FALSE; // Global interrupt enabled save_context; I2C_InterruptServiceRoutine(); // decode I2C message Transmit or receive restore_context; INTCON.GIE = TRUE; // Global interrupt enabled } else if(PIR1.CCP1IF) { PIR1.CCP1IF = FALSE; // Clear compare interrupt flag INTCON.GIE = FALSE; // Global interrupt disabled save_context; if (DBS_LaserMode == LAS_MAIN_ON_STATE) // switch of/on pulse generation { LaserFreqOut = ~LaserFreqOut; // PULSE GENERATION } restore_context; INTCON.GIE = TRUE; // Global interrupt enabled } else if(INTCON.T0IF) { INTCON.T0IF = FALSE; INTCON.GIE = FALSE; // Global interrupt disabled save_context; TMR_InterruptServiceRoutine(); // SYSTEM TIMER restore_context; INTCON.GIE = TRUE; // Global interrupt enabled } return; } The problem now is that I receive a Stack overflow error from Mplab when the timer is generating very fast interrupts, generating pulses from 2kHz works fine. Once I increase the value the Stack overflow error is displayed Frank Temmerman __________________________________________________________________ One fool can ask more questions than all the scientists in teh world can answer __________________________________________________________________

1997\05\05@044508 by tjaart

FrankT wrote: > > For those guys who followed my story on the interrupt problems I had, > here's the next chapter. > After a few mails to the piclist and some great help I came up with the > next piece of code. > > void __INT(void) > { > if(PIR1.SSPIF) > { > PIR1.SSPIF = FALSE; // Clear I2C interrupt flag You must save the context (W, Status, and a wealth of other mysterious MPLABC variables) first. Here you are going to run into trouble. The include files for the various parts in MPLABC do not all contain context saving code. You cannot (probably cannot) do this yourself because you don't know how the compiler uses these variables. I ran into this problem with the '74. The support I received from Microchip stank. I mailed every Mchip guy from my distributor to every FAE I could find, but have still not received ANY constructive feedback after 8 months. What I did receive was a whole lot of rethoric about Mchip policy to not update their software products too often. They claim the customers would rather sit with malfunctioning software than download updates all the time. Geez, don't you just hate PR? I received a working header file from a guy (not connected to Mchip) on this list, but had to promise him I wouldn't mail it to the list or mention his name. I will respect that. What I can suggest, is that you mail a request for a header file with a working version of the context saving for your PIC to this list. I'm sure the Good Samaritan who helped me will also help you. If you still don't get help, I will mail him a request on your behalf. For any prospecting MPLABC buyers out there, I have this piece of advice : ***************************************************************************** *** Don't buy MPLABC until Microchip has the competency to offer support *** ***************************************************************************** This may take until next millenium by the looks of it. :( -- Friendly Regards Tjaart van der Walt @spam@tjaartwasp.co.za _____________________________________________________________ | Another sun-deprived R&D Engineer slaving away in a dungeon | | WASP International http://wasp.co.za | | GSM and GPS value-added applications | | Voice : +27-(0)11-622-8686 | Fax : +27-(0)11-622-8973 | |_____________________________________________________________|

1997\05\05@074928 by Andrew Warren

FrankT <PICLISTRemoveMEMITVMA.MIT.EDU> wrote: {Quote hidden}> void __INT(void) > { > if(PIR1.SSPIF) > { > PIR1.SSPIF = FALSE; > interrupt flag INTCON.GIE = FALSE; > save_context; > I2C_InterruptServiceRoutine(); > restore_context; > INTCON.GIE = TRUE; > } > else if(PIR1.CCP1IF) > { > .... etc. .... > } > return; > } > > The problem now is that I receive a Stack overflow error from Mplab > when the timer is generating very fast interrupts, generating pulses > from 2kHz works fine. Once I increase the value the Stack overflow > error is displayed Frank: You need to do a few things here... First, the "save_context code must be THE VERY FIRST thing you do, right at the start of the __INT() functionm, and the "restore_context"code must be the very LAST thing you do, just before the "return". You didn't mention hether you were using MPC, MPLAB-C, or some other compiler; some compilers will automatically generate the save/restore code for you if they know that you're writing an interrupt-service routine (and they'll also ensure that the "return" is properly compiled to a "RETFIE" instruction, not a "RETURN"). Second, there's no need for the "INTCON.GIE = FALSE" instructions; the GIE bit is cleared automatically by the PIC's interrupt hardware. Third, you MUST NOT set the GIE bit to TRUE within your interrupt routine; that's what's causing your stack overflow errors. The "RETFIE" at the end of your routine will automatically set the GIE bit true when it returns to your main code. Other than those three things, your code is fine. -Andy === Andrew Warren - spamfastfwdix.netcom.com === Fast Forward Engineering, Vista, California === http://www.geocities.com/SiliconValley/2499

1997\05\06@122547 by Vishram sarurkar

On Mon, 5 May 1997, FrankT wrote: > __________________________________________________________________ > One fool can ask more questions than all the scientists in teh world can > answer > __________________________________________________________________ > Wow !!!! if he can ask so many questions then, i must say he's a genius not a fool !!! regards... vishram. +------------------------------------------+ | Vishram A. Sarurkar | | ^^^^^^^^^^^^^^^^^^^^^ | | another hobbyist turned researcher | | slogging @ Indian Institute of Science | | ----------- | | e-mail:vishspam_OUTTakeThisOuTisu.iisc.ernet.in. | | Phone:+91 (080) 3092487. | +------------------------------------------+

'HOT KEYS IN MPLAB!'
1997\06\11@061940 by -8859-2?Q?Sylwester_=A3azar?=

I discover that after using find option (shortcut- F3), I can use F4. This open a list of all recently used words. I can do it manually of course, but I thing it's faster to press F3&F4. Maybe someone else, knows any shortcuts ?! There is many tricks in programs, we can use to improve our work and to love even MPLAB . Lets find it all! Sylwester £azar electronics engineer spam_OUTzsee@spam@RemoveMEids.poznan.pl POLAND

'Can an MPLAB MACRO do this?'
1997\07\01@204300 by Andrew Kalman

Hi All. I'm wondering if it's possible to define a macro in MPLAB to do the following with its arguments: "call" the macro as: _mymacro REGISTER, BIT and have it expand to, say bcf my_REGISTER_name, BIT I would expect to be able to do something like _mymacro macro arg1, arg2 bcf my_&arg1&_name, arg2 endm where the "&" is interpreted as a string concatenator, but MPLAB doesn't seem to support this. Am I missing something obvious here? Thanks, ___________________________________________ | Andrew E. Kalman, Ph.D. spamaekspamnetcom.com | | standard disclaimers apply | |___________________________________________|

'HEX representation in MPLAB (Re: PICLIST Digest - '
1997\07\13@175417 by paulb

Ian Bennett wrote: > Is there any way I can confgure the assembler to accept hex data as $?? > instead of H'??' or 0x??, both of which seem to me to be somewhat awkward. Hear Hear! Unless one feels a desparate need for compatibility with an Intel product (and one should be asking really serious quentions if so; it seems that Microchip didn't REALLY feel the need), commonsense indicates that one of the first things in writing an assembler would be to opt for the Motorola (Pascal, most FORTH) format. Regards, Paul B.

'Using TDE and MPLAB'
1997\07\14@123751 by jhobbs

I use the TDE with Pro Mate II all the time. You need to make a .bat file like this. My TDE folder is in Program Files c:\progra files\tde file name: cvasm16a.bat contents: @echo off cvasm16.exe %1 /s The /s will strip off the usless stuff. I then use a shortcut in c:\windows\sendto CVASM The shortcut Cmd line: c:\progra~1\tde\cvasm16a.bat Working: c:\progra~1\tde Run: Minimized Check Close on exit. Now when you are done with your TDE program, open your folder where your .obj resides. Highlight it, right mouse click and Send To, choose CVASM. It's fast and easy. If you are running the new MPLAB 3.22.02 you will new to select File and Import to load your code. Hope this helps. Take care -Jim @spam@Jhobbsspam_OUTquiknet.com

'debug using MPLAB ?'
1997\07\31@212720 by Ravindra Divekar

Hi friends! I tried using MPLAB to develop my software. I managed to Create a new project, add .asm files to the project and assemble it without errors. However I am unable to debug my project. When I go to the Debug menu, none of the choices are active (such as run,animate etc.). am i missing something here ? do i need to setup the environment in a different way, or is it justa keypress away ? --ravindra

'debug using MPLAB ?'
1997\08\01@004935 by Mike Keitz

On Thu, 31 Jul 1997 18:17:59 -0700 Ravindra Divekar <.....ravindra.....HAL.COM> writes: >Hi friends! > >I tried using MPLAB to develop my software. >I managed to Create a new project, >add .asm files to the project and assemble it >without errors. The project can contain only one .asm file. To "link" in other asm files use include directives in the main asm file. The assembler does not use a seperate linking stage, the entire project must be assembled all at once. Much of the facilities for more than 1 file, "make" as opposed to "build all", etc. are just for show now. The assembler is not advanced enough to use them. To assemble, use "Build All". If there are no errors, this will load the object code into the program memory window ready to program or simulate. >However I am unable to debug my project. >When I go to the Debug menu, none of the choices >are active (such as run,animate etc.). Open the Options:Development Mode dialog and check "MPLAB-SIM Simulator" rather than "Editor Only".

1997\08\01@103331 by Martin R. Green

I had the exact same problem last night. I discovered that even though I had told MPLAB to create the project in Simulator mode, it had actually created it in Editor Only mode. Go to Options->Development Mode and select MPLAB-SIM Simulator. MPLAB will close your current project, but when you reopen it, all the debug stuff will work. CIAO - Martin R. Green spamelimarKILLspambigfoot.com ---------- From: Ravindra Divekar[SMTP:RemoveMEravindraRemoveMEHAL.COM] Sent: Thursday, July 31, 1997 9:17 PM To: KILLspamPICLIST.....KILLspamMITVMA.MIT.EDU Subject: debug using MPLAB ? Hi friends! I tried using MPLAB to develop my software. I managed to Create a new project, add .asm files to the project and assemble it without errors. However I am unable to debug my project. When I go to the Debug menu, none of the choices are active (such as run,animate etc.). am i missing something here ? do i need to setup the environment in a different way, or is it justa keypress away ? --ravindra

1997\08\01@111502 by Tom Mariner

On Friday, August 01, 1997 12:51 AM, pic microcontroller discussion list On Behalf Of Mike Keitz wrote: {Quote hidden}> On Thu, 31 Jul 1997 18:17:59 -0700 Ravindra Divekar <ravindraspam_OUTspam_OUTHAL.COM> > writes: > >Hi friends! > > > >I tried using MPLAB to develop my software. > >I managed to Create a new project, > >add .asm files to the project and assemble it > >without errors. > > The project can contain only one .asm file. To "link" in other asm files > use include directives in the main asm file. The assembler does not use > a seperate linking stage, the entire project must be assembled all at > once. Much of the facilities for more than 1 file, "make" as opposed to > "build all", etc. are just for show now. The assembler is not advanced > enough to use them. > > To assemble, use "Build All". If there are no errors, this will load the > object code into the program memory window ready to program or simulate. > > >However I am unable to debug my project. > >When I go to the Debug menu, none of the choices > >are active (such as run,animate etc.). > > Open the Options:Development Mode dialog and check "MPLAB-SIM Simulator" > rather than "Editor Only". > Also make certain that the correct microcontroller model is selected. If it isn't, you can edit, but not much else. Tom

'What use is 32 bits ? [Was MPLAB Win CE]'
1997\08\02@140254 by Mike

At 10:02 AM 8/2/97 +0200, you wrote: >> What makes you think 32 bit apps are more efficient ? >> >> Windows 95 is 95% 16 bit drivers and libraries most of which is ported >> >> over from win 3.11. >> >> there is a lot of propoganda and hype Win NT comes close to be a 32 >> bit app >> but even that uses 16 bit dlls ! >> >> rdgs >> >> mike > >So is there a TRUE 32-bit OS out there? Does it matter ? Why FORCE one instruction per 32 bits when you can get TWO or more ? WHY do you NEED an 8 bit character to occupying 32 bits - when its more efficient for it to occupy a byte or at most a 16 bit word ? >What will Win97 be? (If ever it surfaces from the rumours!) Not important - Actually it will be Win98 and WILL have lots of 16 bit instructions in it (even though the buss might fetch 2 or 4 of them at a time). Why slow down a machine forcing it to use 32 bit instructions ? Did you know that 8 bit micros have faster IO than any 486 or Pentium in a windows type GUI - apart from operating system overhead - most comms is 8 bits - so the value of a wider word size is a overdoing it, a bit;) Rgds Mike Perth, Western Australia Some say there is no magic but, all things begin with thought then it becomes academic, then some poor slob works out a practical way to implement all that theory, this is called Engineering - for most people another form of magic. Massen

1997\08\02@154438 by Scott Newell

>>So is there a TRUE 32-bit OS out there? > >Does it matter ? I don't really care if 95 is a *true* 32-bit OS or not. But there are some things I like about it. (And some I don't...) I like not having to worry about memory models and whether I'm going to wrap around a 64k segment and how big my pointers are and whether it's a near call or a far call. I also like that the 32 bit address space gives you room for neat tricks like memory mapped files. >Why FORCE one instruction per 32 bits when you can get TWO or more ? It's not the simple. Not every x86 protected mode instruction is 32 bits wide. Not every instruction on the 8086 was 16 bits wide, either. It's my understanding that a 32 bit OS has a 32 bit address space, and that the size of the opcodes is irrelevant. later, newell

'MPLAB on Libretto (was Re: MPLAB with HP Palmtop w'
1997\08\02@200838 by Eric Smith

Darrel Johansen <KILLspamdarrelj@spam@PRIMENET.COM> asks: > I wonder if anyone out there has tried MPLAB with the Toshiba Libretto? > It's only now becoming available outside of Japan, but it runs Win 95, > not CE. It should run MPLAB, I would think. Yes, I've been running it on a Libretto since March. Of course, mine is the Japanese model rather than the US model, but AFAIK the only difference is the keyboard, so it should work fine on the US model as well. Although the US keyboard has slightly wider keys, it was done at the expense of the dedicated Insert, Delete, Home, End, Page Up, and Page Down keys. I actually prefer the Japanese keyboard. My portable embedded systems development kit now consists of: Toshiba Libretto, 32M, 1.6G IBM hard drive (about the size of a VHS tape) TechTools Clearview Mathias Microchip PICSTART Plus HP LogicDart - handheld three channel logic analyzer with DVM And soon to be added: Xeltek SuperPro III/L - device programmer to use for stuff other than PICs All this stuff fits in a medium sized bag that fits under the seat in front of me on a plane, and still leaves room for my feet! Although the Libretto doesn't have an integral CD-ROM drive, so I can't use the Microchip CD-ROM on the road, I copied the PDF files I use the most over to the hard drive. I do have a Panasonic portable 10X CD-ROM drive, but I don't actually carry it around. I do travel with PCMCIA modem and ethernet cards though. Cheers, Eric In case anyone wants more information on any of the mentioned products, here are some URLs. I am not affiliated with any of these companies. Libretto: www.toshiba.com/tais/csd/products/portable/libretto/overview/index.htm Mathias http://www.tech-tools.com/mathias.htm PICSTART Plus www.microchip2.com/products/devtools/prog/picstrpl.htm LogicDart www.tmo.hp.com/tmo/ordering/LogicDart/index.cgi SuperPro III/L http://www.xeltek.com/sp3lbroch.html

'32 vs. 16 bit O/S code [Was: MPLAB with HP Palmtop'
1997\08\03@034251 by Clyde Smith-Stubbs

There is an awful lot of misinformation being spread on this thread. The 16 vs. 32 bit distinction on Intel x86 processors is as follows: 80x86 processors up to the '286 are 16 bit only - they have 16 bit wide accumulators and index registers, and a limit of 64K per addressable segment. The 386 and higher processors have split personalities; they are effectively two processors in one. The distinction comes about only when running in protected mode, and is made by distinguishing two types of segments - 16 bit segments operate just like a 286, 32 bit segments operate like a quite different processor; in 32 bit segments the available register set is different (all 32 bit not 16 bit) and the set of addressing modes is *totally* different (note; it is possible to have 32 bit instructions in a 16 big segment or vice versa, by use of override prefixes). In a 32 bit O/S like NT or Linux, the operating system code runs in 32 bit segments, and uses "flat" model code, where a linear 32 bit address space is used. In a 16 bit O/S like Win3.1, the O/S code mostly runs in 16 bit segments, using segmented addressing. Win95 is a hybrid; some 32 bit code, quite a lot of 16 bit code. When it comes to applications under Windows, there is not only the distinction between 16 and 32 bit code, but also the distinction between the Win16 API and the Win32 API. While the Win32 API is superficially a superset of Win16, there are major extensions, and fundamental differences that, amongst other things, make it possible for Win32 programs to be pre-emptively task-switched, whereas Win16 programs in the same virtual machine can only be co-operatively task switched. Win95 and WinNT both support both the Win16 and Win32 API, but only Win32 applications task switch cleanly (all Win16 apps in NT are treated together as one Win32 task, and within that task the Win16 apps do not pre-emptively task switch - though it is possible to have additional Win16 (aka Windows On Windows or WOW) virtual machines running, but it's very memory hungry). Win On Sun, Aug 03, 1997 at 02:52:27AM -0400, Mike wrote: > > Sorry - no such thing as a true 32 bit operating system - what is the > collective definition of a 16 or 32 bit operating system ANYWAY ??? A 32 bit O/S is one that runs natively on a 32 bit processor. NT fits this definition. Win3.1 does not, Win95 might do. > It may not load a 16bit dll 'app' BUT I would be willing to bet it is > riddled with 16 bit code since its more efficient to selectively use > 16 bit instructions when its just a complete waste of resources to try Wrong! On an x86 processor in 32 bit mode, 16 bit addressing (i.e. using a 16 bit index register or even loading a 16 bit register) is very inefficient, due to the prefix byte required to force 16 bit addressing. In this mode, 32 bit addressing is much more efficient. And 32 bit mode is more efficient than 16 bit mode since the flat model eliminates the very costly segment register loads required by the 16 bit segmented model used in 16 bit mode. Any memory intensive 32 bit code will run much faster than 16 bit code that has to address more than 64K memory. Cheers, Clyde -- Clyde Smith-Stubbs |HI-TECH Software, |Email: @spam@clydeRemoveMEhtsoft.com Ph: +61 7 3354 2411|P.O. Box 103, Alderley,|WWW: http://www.htsoft.com/ Fax: +61 7 3354 2422|QLD, 4051, AUSTRALIA. |PGP: finger clyde@spam@EraseMEhtsoft.com --------------------------------------------------------------------------- ANSI C for the PIC! Now shipping! See http://www.htsoft.com for more info.

1997\08\03@040326 by Mike

At 05:41 PM 8/3/97 +1000, you wrote: Hi Clyde, Thanks for clarifying the preliminaries re apps etc {Quote hidden}>> It may not load a 16bit dll 'app' BUT I would be willing to bet it is >> riddled with 16 bit code since its more efficient to selectively use >> 16 bit instructions when its just a complete waste of resources to try > >Wrong! On an x86 processor in 32 bit mode, 16 bit addressing (i.e. using >a 16 bit index register or even loading a 16 bit register) is very >inefficient, due to the prefix byte required to force 16 bit addressing. In >this mode, 32 bit addressing is much more efficient. And 32 bit mode is >more efficient than 16 bit mode since the flat model eliminates the >very costly segment register loads required by the 16 bit segmented model >used in 16 bit mode. Any memory intensive 32 bit code will run much faster >than 16 bit code that has to address more than 64K memory. mmm - I'm not so sure. I remember seeing this sort of debate some time ago when Win95 first came out at that time I was shown code snippets in 'true' 32 bit mode and 'hybrid' which had about 70% in NON 32 bit mode, I think the data structures being operated on were around the 64K sixe, since that involved a peculiarity of the processor. I seem to recall that the 'true' 32 bit code was slower and occupied more space than 'selectively' preparing the appropriate segment registers, doing the required operations in NON 32 bit mode, then cleaning up the various segment registers at the end - OVERALL the 16 bit code was faster and about 20% smaller. There was apparantly no way the task could be put into 32 bit only mode AND have it run faster or be smaller. The task had a lot to do with 'real world' data processing and preparing output for display. I'll try and dig this up, but it was about 15 months ago... So - would you suggest that in NT (ignore 16 bit ported app/dlls) every single instruction operates on the 32 bit model and there are no 16 bit instructions or other instructions which are less than a 32 bit 'lump', frankly I can't see how you could write an OS which ONLY had 32 bit instructions on the 486/Pentium processor - there must be some 8/16 bit instruction - at least in terms of word size - is there a 32bit IO space as well as memory address space - and would you want that ? Rgds Mike

1997\08\03@050636 by Clyde Smith-Stubbs

On Sun, Aug 03, 1997 at 04:03:26AM -0400, Mike wrote: > At 05:41 PM 8/3/97 +1000, you wrote: > I seem to recall that the 'true' 32 bit code was slower and occupied more > space than 'selectively' preparing the appropriate segment registers, doing 32 bit code tends to be smaller (because of better addressing modes) - if you avoid doing any segment register loads, 16 bit code could execute as fast as 32 - it's unlikely to be faster except in very exceptional circumstances. In practice, any 16 bit Windows application will use segment register loads, which really kills performance (each segment register load actually loads several hidden registers from the segment table). > can't see how you could write an OS which ONLY had 32 bit instructions on > the 486/Pentium processor - there must be some 8/16 bit instruction - at Of course. The 8 bit addressing is still available in 32 bit mode, and has no performance penalty, but trying to use 16 bit index registers is costly, and offers no benefit (since the 386 and up have 32 bit data buses anyway). > least in terms of word size - is there a 32bit IO space as well as memory Again, of course the address space is 32 bit - the external data bus requires that. But there's no problem accessing data 8 bits at a time, it's just you get a 32 bit address put out (though the external hardware may see less than 32 bits). -- Clyde Smith-Stubbs |HI-TECH Software, |Email: spam_OUTclydespam_OUTRemoveMEhtsoft.com Ph: +61 7 3354 2411|P.O. Box 103, Alderley,|WWW: http://www.htsoft.com/ Fax: +61 7 3354 2422|QLD, 4051, AUSTRALIA. |PGP: finger RemoveMEclyde.....htsoft.com --------------------------------------------------------------------------- ANSI C for the PIC! Now shipping! See http://www.htsoft.com for more info.

1997\08\03@112135 by Griffith Wm. Kadnier

Hi Mike, 1) As one of the original WinNT Kernel-Team developers @ MS from 1991-1993, and then as a Kernel-Team developer, porting 32 bit elements of NT to Windows95, for that group, I can tell you absolutely that WinNT uses NO 16 bit code in it's 32 bit-OS data paths. Almost 100% of the base OS is C/C++ (except elements of the HAL, where some assembler is used), and is/has been compiled using MS's 32 bit compilers. The upper-edge WOW, and DOS VDM routines are the only part of NT that even KNOW about 16 bit code, and these elements can be looked at as add-ons, for backwards compatibility. I think that scenario suffices for a definition of a 32 bit operating system :} See my book "Windows NT4, The Complete Reference"-Osborne McGraw-Hill ISBN 0-07-882181-9, for a sysadmin-level discussion of NT's 32 bit architecture, vis-a-vis the Kernel, GDI, drivers, etc. Windows 95, on the other hand, has many 16 bit elements, cooperating (hopefully) with it's 32 bit layers. (I don't think 95% is anywhere near correct though)--The Win95 User/Kernel is probably less than 20-30% dependent upon 16 bit code, and ALL ancillary VxD's are 32 bit. Some of the OS routines thunk down to a base-16 bit routine, and that, among other issuses, is where you take a hit. 2) That said, it must also be noted that comments in prior msg's linked to this thread, about 8/16 bit quantities or accesses being ineffeciently handled by a 32 bit-wide instruction stream, are equally fallacious. It does NOT take 32 bits to store an 8 bit memory or port quantity. The instruction may be 32 (or more) bits wide, and memory addresses will be 32 bits, but a byte is still a byte in 32 bit land, and memory access can be done with equal effeciency on 32 bit intel processors that contain instructions to read, write, and do I/O on byte, word, double-word, and quad-word basis, given that the electronic architectures are equal. Also, a data structure gets only the space that is allocated for it by a compiler or at the asm level. A 4 gb address space is NOT automaticlly given to ANY process, and certainly not to an arbitrary data structure within a process; that is the responsibility of the OS memory management that is in charge; the part of the underlying software that is actually handling memory and process allocation on behalf of an upper-level process. 3) The memory space of the Pentium family is 4 gb. The I/O space of the Pentium family is 64k. Memory is actually organized in 64 bit chunks, with byte-sized sub-unit addressing. I/O is organized as sequences of 32 bit quantities, accessable as byte sub units. It is up to the computer maker to organize these base schemes in terms of access to 64, 32, 16, or 8 bit I/O or memory planes. 4) Clyde is also right in his assertion that 16 bit code is *usually* less effecient on a 32 bit CPU. Selector loads, and indexing are always less effecient than flat model. BUT, the responsibility to use 32 bit instructions and address space for the most efficient data movement is ++always++ put squarely upon the programmer and/or the compiler used. I know of a lot of very SLOWWW code being produced by programmers that don't know/care how their compiler works. (How about passing whole C++ objects...not pointers, around on the stack??....Do you want to see what repeated setup/teardown of a 512K deep stack does to the operation of a process???) This kind of stuff would only be worse in a 16 bit environment. Applications (and OS code) always rise to the level of the incompetecy of their creators! I'd love to get down to Australia sometime. I hear it's the land to be in for us Liberatarians-at-heart. gwk Algorithmics Inc. ---------- > From: Mike <spamerazmus@spam@WANTREE.COM.AU> > To: PICLISTTakeThisOuTMITVMA.MIT.EDU > Subject: Re: 32 vs. 16 bit O/S code [Was: MPLAB with HP Palmtop windows CE] {Quote hidden}> Date: Sunday, August 03, 1997 1:03 AM > > At 05:41 PM 8/3/97 +1000, you wrote: > > Hi Clyde, > Thanks for clarifying the preliminaries re apps etc > > >> It may not load a 16bit dll 'app' BUT I would be willing to bet it is > >> riddled with 16 bit code since its more efficient to selectively use > >> 16 bit instructions when its just a complete waste of resources to try > > > >Wrong! On an x86 processor in 32 bit mode, 16 bit addressing (i.e. using > >a 16 bit index register or even loading a 16 bit register) is very > >inefficient, due to the prefix byte required to force 16 bit addressing. In > >this mode, 32 bit addressing is much more efficient. And 32 bit mode is > >more efficient than 16 bit mode since the flat model eliminates the > >very costly segment register loads required by the 16 bit segmented model > >used in 16 bit mode. Any memory intensive 32 bit code will run much faster > >than 16 bit code that has to address more than 64K memory. > > mmm - I'm not so sure. I remember seeing this sort of debate some time ago > when Win95 first came out at that time I was shown code snippets in > 'true' 32 bit mode and 'hybrid' which had about 70% in NON 32 bit mode, > I think the data structures being operated on were around the 64K sixe, > since that involved a peculiarity of the processor. > > I seem to recall that the 'true' 32 bit code was slower and occupied more > space than 'selectively' preparing the appropriate segment registers, doing > the required operations in NON 32 bit mode, then cleaning up the various > segment registers at the end - OVERALL the 16 bit code was faster and about > 20% smaller. There was apparantly no way the task could be put into > 32 bit only mode AND have it run faster or be smaller. The task had a lot > to do with 'real world' data processing and preparing output for display. > I'll try and dig this up, but it was about 15 months ago... > > So - would you suggest that in NT (ignore 16 bit ported app/dlls) every single > instruction operates on the 32 bit model and there are no 16 bit instructions > or other instructions which are less than a 32 bit 'lump', frankly I > can't see how you could write an OS which ONLY had 32 bit instructions on > the 486/Pentium processor - there must be some 8/16 bit instruction - at > least in terms of word size - is there a 32bit IO space as well as memory > address space - and would you want that ? > > Rgds > > Mike

'Windows 32 bits (was re MPLAB on Windows CE)'
1997\08\04@212624 by John Payson

The following question isn't really PIC related, but it seems to come up now and again; perhaps it should go into a FAQ someplace? > At 05:47 PM 8/2/97 -0700, you wrote: > >WinNT IS a true 32 bit OS. It just provides 16 bit dlls for running legacy > >apps ala Win 3.1. > > Sorry - no such thing as a true 32 bit operating system - what is the > collective definition of a 16 or 32 bit operating system ANYWAY ??? In this context, the term "32-bit [operating system] refers to the mode in which the 80x86 chip is run. While it's possible to use both 16- and 32-bit instructions from within any mode, there are nonetheless two issues to be considered: [1] If an application passes a pointer to an OS call, what is the meaning of the pointer? Under Win16, a pointer contained a segment and an offset; arithmetic on pointers beyond 64K wouldn't work. Under WIn32, a pointer contains a 32-bit virtual address and arrays up to 4GB (theoretical upper limit) in size may be handled with having to be subdivided into 64K chunks. [2] What is the instruction-level default mode? On the 80386 and higher, the processor can run in two [broadly speaking] modes: (a) Instructions whose operand is "word" sized should operate on the 16-bit registers AX, BX, CX, etc.; memory addresses should be of the form (Address + [BX | BP] + [SI | DI]). (b) Instructions whose operand is "word" sized should operate on the 32-bit registers EAX, EBX, ECX, etc.; memory addresses should be of the form (Address + [reg32] + [{1|2|4|8}*{reg32}). If the machine is in mode "b", executing an instruction from set "a" will require one or more override-prefix bytes; similarly, if it's in mode "a", an instruction from mode "b" will require override prefix(es). > >If all you run is 32 bit applications, WinNT never even tries to load or > >intercept any 16 bit code. > > It may not load a 16bit dll 'app' BUT I would be willing to bet it is > riddled with 16 bit code since its more efficient to selectively use > 16 bit instructions when its just a complete waste of resources to try > and FORCE a 4 gigabyte address space on each and every data structure ? Actually, code size will often be smaller if a Win32 application consistently uses 32-bit data types than if it mixes 32-bit and 16-bit types (because 16-bit ops require extra prefixes). While routines that store large amounts of data in memory may benefit from using 16-bit types (thereby saving 2 bytes per item) non-array variables should often be 32 bits to avoid extra prefix bytes.

1997\08\04@214725 by Griffith Wm. Kadnier

Hi John, Yes, as you correctly point out and expand on my thoughts, is the fact that I was referring to NT OS code that does not use segment:offset semantics, working fully in flat model (your "b" scenario). gwk Algorithmics Inc. ---------- > From: John Payson <.....supercatTakeThisOuTMCS.COM> > To: EraseMEPICLISTKILLspamMITVMA.MIT.EDU > Subject: Windows 32 bits (was re MPLAB on Windows CE) > Date: Monday, August 04, 1997 1:17 PM > > The following question isn't really PIC related, but it seems to come up > now and again; perhaps it should go into a FAQ someplace? > > > At 05:47 PM 8/2/97 -0700, you wrote: > > >WinNT IS a true 32 bit OS. It just provides 16 bit dlls for running legacy > > >apps ala Win 3.1. > > > > Sorry - no such thing as a true 32 bit operating system - what is the > > collective definition of a 16 or 32 bit operating system ANYWAY ??? > > In this context, the term "32-bit [operating system] refers to the mode in > which the 80x86 chip is run. While it's possible to use both 16- and > 32-bit instructions from within any mode, there are nonetheless two > issues to be considered: > > [1] If an application passes a pointer to an OS call, what is the meaning > of the pointer? Under Win16, a pointer contained a segment and an offset; {Quote hidden}> arithmetic on pointers beyond 64K wouldn't work. Under WIn32, a pointer > contains a 32-bit virtual address and arrays up to 4GB (theoretical upper > limit) in size may be handled with having to be subdivided into 64K > chunks. > > [2] What is the instruction-level default mode? On the 80386 and higher, > the processor can run in two [broadly speaking] modes: > > (a) Instructions whose operand is "word" sized should operate on the > 16-bit registers AX, BX, CX, etc.; memory addresses should be of the form > (Address + [BX | BP] + [SI | DI]). > > (b) Instructions whose operand is "word" sized should operate on the > 32-bit registers EAX, EBX, ECX, etc.; memory addresses should be of the > form (Address + [reg32] + [{1|2|4|8}*{reg32}). > > If the machine is in mode "b", executing an instruction from set "a" will > require one or more override-prefix bytes; similarly, if it's in mode "a", > an instruction from mode "b" will require override prefix(es). > > > >If all you run is 32 bit applications, WinNT never even tries to load or {Quote hidden}> > >intercept any 16 bit code. > > > > It may not load a 16bit dll 'app' BUT I would be willing to bet it is > > riddled with 16 bit code since its more efficient to selectively use > > 16 bit instructions when its just a complete waste of resources to try > > and FORCE a 4 gigabyte address space on each and every data structure ? > > Actually, code size will often be smaller if a Win32 application > consistently uses 32-bit data types than if it mixes 32-bit and 16-bit > types (because 16-bit ops require extra prefixes). While routines that > store large amounts of data in memory may benefit from using 16-bit types > (thereby saving 2 bytes per item) non-array variables should often be 32 > bits to avoid extra prefix bytes.

1997\08\05@064409 by nvdw

> > It may not load a 16bit dll 'app' BUT I would be willing to bet it is > > riddled with 16 bit code since its more efficient to selectively use > > 16 bit instructions when its just a complete waste of resources to try > > and FORCE a 4 gigabyte address space on each and every data structure ? Win95 yes....Thats why it is faster and less RAM hungry, and less stable. NT no.... Try running around in both with SoftIce.... Nic.

'TRICE with MPLAB 3.22.02'
1997\08\09@174811 by and

Hi I'm Sam, Recently I bought PIC in a box from Farnell which consist of MPLAB IDE & PICStart Plus & other stuff. But I feel I need an emulator. Has anyone tried TRICE from Lennard Research with MPLAB IDE and just how true is TRICE compared to any other bond out chip based ICE? Thank u, Sam MSE - MASRONICS Survey Electronics, Malaysia. samsmanEraseMEpc.jaring.my EraseMEsamsmanspamBeGonetm.net.my

'Parallax to MPlab'
1997\08\13@184230 by David Bramham

Hi all, I have a copy of RCV2LCD.SRC for Parallax PIC Application.I would like t o convert it to an MPlab ASM file .However,I have problems converting such statements as 'csne'and 'cjb'. Does anybody have either a this program in ASM file format or a list of conversions between the 2 codes. Many thanks David

1997\08\13@195119 by Martin R. Green

I am doing some similar conversions for a C Compiler I am converting that used to produce a source file for an 8051 style assembler for PIC's. The bad news is that there are no direct conversions for the conditional jump instructions you are looking at. The good news is all can be simulated on a PIC, but will require at least two, and sometimes quite a few PIC instructions. This isn't as bad as it seems since the 8051 is not a RISC device, so the number of clock cycles used for a jump is comparable to the 8051 equivalent, it is just a lot cleaner to look at the 8051 versions than the PIC versions. If you want to keep the clean look in you ASM files, I suggest you write macros that convert the old compare instructions into a sequence of PIC ones that do the same thing. Oh, one other caveat, many of the PIC equivalents will mess up one or other of the arguments (W or a register file). The csxx instruction are basically "compare and skip if true" instructions. They can be simulated simply for stuff like "csnz file": movf file,1 btfsc STATUS, ZERO skipee ; this is the instruction that will be skipped. Of course STATUS and ZERO are defines for your target device. A cjxx instruction like "cjz file, target" can be written as: movf file,1 btfsc STATUS, ZERO goto target ; this instruction will be skipped if file is NOT zero. These were simple, but it gets messier when you need to use the carry flag and the zero flag for comparisons like greater than or below. In these cases your code will have a few btfsx instructions and maybe a few local labels (or relative goto's) too. This is not intended to explain the whole process (I don't have time for that), but hopefully it will put you on the right path. HTH - Martin R. Green TakeThisOuTelimarTakeThisOuTbigfoot.com BTW - another gotcha is that other uC's allow direct file to file comparisons, while with PIC's you must move one register file into W and perform the comparison from there. It makes thing messier but it can be done. ---------- From: David Bramham[SMTP:d.bramhamspam_OUTQUT.EDU.AU] Sent: Wednesday, August 13, 1997 6:33 PM To: spamPICLIST@spam@mitvma.mit.edu Subject: Parallax to MPlab Hi all, I have a copy of RCV2LCD.SRC for Parallax PIC Application.I would like to convert it to an MPlab ASM file .However,I have problems converting such statements as 'csne'and 'cjb'. Does anybody have either a this program in ASM file format or a list of conversions between the 2 codes. Many thanks David

1997\08\14@025029 by wterreb

David Bramham <spam_OUTd.bramhamTakeThisOuTKILLspamQUT.EDU.AU> wrote: > Hi all, > I have a copy of RCV2LCD.SRC for Parallax PIC > Application.I would like to > convert it to an MPlab ASM file .However,I have problems > converting such statements as 'csne'and 'cjb'. Does > anybody have either a this program in ASM file format or > a list of conversions between the 2 codes. David I also wanted to convert for Parallax to Microchip recently and was franticly searching for a suitable converter program. The all of a sudden it struck me..... You can do the entire translation with MLPAB! It works beautifully. This is what you do... You import the Parallax OBJ file in to memory (under File menu). The Parallax OBJ file is also INHX8M (Intel Hex 8-bit Merged format) format, so MPLAB has no problem importing it. Then you display the program memory window (under Window menu). This will give you the assembler together with line numbers and addresses. Select and copy this to a text file and you have your assembler. You'll have to manually edit it a bit to change the calls and goto's to labels again, but at least you will have a 100% correctly translated file. :) Hope this helps. Rgds Werner -- Werner Terreblanche users.iafrica.com/w/we/wernerte/index.htm RemoveMEwterreb@spam@spamplessey.co.za (work) OR RemoveMEwernerteRemoveMETakeThisOuTiafrica.com (home) Plessey SA, PO Box 30451,Tokai 7966, Cape Town, South Africa or at home : Suite 251, PostNet X5061, Stellenbosch, 7599 Tel +27 21 7102251 Fax +27 21 7102886 Home +27 21 8872196 ------------------------------------------------------------

'Help with MPLAB simulator'
1997\08\14@104429 by arl Wainwright

Just a short request to anybody who is using or has used the simulator. I am having trouble simulating the SPI on the 16C64A within the simulator. I know its possible because it says in the MPLAB manual. Except I am having a few problems starting SPI putting values into the Shift register through a stimulus file! If anybody has any idea about this I would be very grateful Carl Wainwright -- Carl Wainwright, Design Engineer Tel +44 (0) 1635 584000 Controlware Ltd. Fax +44 (0) 1635 548098 Newbury, U.K. E-mail cwainwrightTakeThisOuT@spam@cware-dev.demon.co.uk

'Is it just me being stupid,or do I blame MPLAB?'
1997\09\01@032411 by wterreb

My Picstart Plus programmer running under MPLAB is really starting to make me doubt my knowledge of computers. I seem to spend more time getting the programmer to run than actually doing development work on it. Its latest phenomena is to refuse to work on COM1 or COM2, but only on COM4. The only problem is that I have only COM1 and COM2 on my computer. Every time I try to set the thing up for one of these two comm ports it gives me a message "Could not open comm port" and then "Picstart Plus not found on COM4". I suspect that it must be something to do with my Win95 configuration, but 4 hours of fiddling which included re-installing MPLAB and Win95 could not solve the problem. I knew my comm ports were still working because I had no problems getting my mouse and modem to work on them. It was just my Picstart Plus programmer that refused to work on them. Out of desperation I eventually configured my COM2 as COM4 and "voila!", MPLAB was happy with that. But why would it not work on COM2 is boyond my comprehension. Has anybody else ever had a similiar problem or is it just me? The Microchip documentation does not mention this problem at all. When I was originally selected a programmer, I decided upon the Picstart Plus because I thought that the fact that it was a Microchip product would mean that all the usual bugs associated with cheap programmers would be eliminated. Now I'm not so sure anymore whether that is really the case. If I would buy another programmer again I would much rather buy one from one of third party suppliers present on this list. Rgds Werner

'?'s on MPLAB version 3.3.'
1997\09\29@130557 by Kirby W. Cartwright

part 0 632 bytes content-type:text/x-vcard; charset=us-ascii; name="vcard.vcf" (decoded 7bit) The new version of MPLAB advertises that it supports MPLINK and the new MPASM for Windows that produces relocatable code. I downloaded it and tried it but it still only allows one file in a project. Also, I couldn't find any settings for linking or producing relocatable code. What gives? Kirby Cartwright Content-Type: text/x-vcard; charset=us-ascii; name="vcard.vcf" Content-Transfer-Encoding: 7bit Content-Description: Card for Kirby Cartwright Content-Disposition: attachment; filename="vcard.vcf" Attachment converted: wonderland:vcard.vcf 1 (TEXT/CSOm) (00007B43)

1997\09\29@155303 by Darrel Johansen

Kirby, You need to download the preliminary documentation for the new MPASM v2.00 and MPLINK and MPLIB. That's on the web page (or should be by now --it was also part of the previous package, the pre-release of MPASM v2.00). It's also on the BBS. MPLAB is lagging behind a little, so the projects still have the same limitations. We'll get to that and integrate everything into MPLAB as time allows. For now, you can use batch or make facilities to set up the assembler for relocatable objects. Set the "Add/Modify Compiler" of MPLAB to a new compiler that is the name of your make or batch file (it will only take 8 characters, including the extension, so call it something like MAKE.MAK or RELO.BAT). Add the main file as the file for the project and you'll be able to see all the files in the Project Window and debug with MPLAB as usual. The final manual should be ready for publication soon, and we'll put a PDF version on the web just as soon as it's ready. Darrel Johansen ______________________________ Reply Separator _________________________________ Subject: ?'s on MPLAB version 3.3. Author: pic microcontroller discussion list <PICLISTTakeThisOuTspamBeGoneMITVMA.MIT.EDU> at Internet_Exchange Date: 9/29/97 1:04 PM PIClisters: The new version of MPLAB advertises that it supports MPLINK and the new MPASM for Windows that produces relocatable code. I downloaded it and tried it but it still only allows one file in a project. Also, I couldn't find any settings for linking or producing relocatable code. What gives? Kirby Cartwright

'ICEPIC support in MPLAB'
1997\10\01@141430 by Christof

ICEPIC is running under MPAB Ver 3.30!! Well Done!! My initial tests ran OK and even the ICEPIC diagnostics is supported under >Verify Emulator (although a little bit patched). The Add-In file is now available on the RFSolutions Page. Installation is fairly straightforward (see below). Regards, Christof On 26 Sep 97 at 14:30, Darrel Johansen wrote: {Quote hidden}> MPLAB v3.30 will be posted to the Microchip web site today. The > software will be at: > > http://www.microchip2.com/mplab.htm > > This version also supports the ICEPIC emulator from R.F. Solutions. > You must first install MPLAB v3.30, then install the latest ICEPIC > software. Except for the configuration of the serial port for ICEPIC, > operation is almost exactly the same as for PICMASTER. Some features, > such as the trace buffer and support for the 17Cxx family, are not > available with ICEPIC and these menu items are greyed out. > >

'PORT problem MPLAB'
1997\10\04@221745 by Anthony Buckwell

Hi There PIC16c77 Im trying to send data to PORTD but it keeps sending to TRISE, In MPLAB sample "inc = p16c77.inc" DATA equ PORTD DATA_Tris equ TRISD DATA_CNLT equ TRISE ; in program bcf STATUS, RP0 bcf STATUS, RP1 movlw 0x38 movwf DATA (in MPLAB it keeps sending to TRISE) ??? thanks Anthony thanks Anthony Buckwell \\\\\\\\\\\\\\\\\\\\\\\\\\\\//////////////////////////// Anthony Buckwell School Of Microelectronics, Faculty Of Engineering Griffth University-Nathan, Brisbane, QLD 4111 AUSTRALIA Ph: +61 7 3875 5061 Ph: 0419 783 109 Fax: +61 7 3875 3854 ////////////////////////////\\\\\\\\\\\\\\\\\\\\\\\\\\\\

1997\10\06@142015 by Tjabo Kloppenburg

hi Anthony, > DATA equ PORTD > DATA_Tris equ TRISD > DATA_CNLT equ TRISE I don't know the 16c77, but perhaps MPLAB doesn't like "_", or it uses only the first 4 characters in recognizing labels. I suggest using different labels: DATA equ PORTD TrisDATA equ TRISD CNLTDATAT equ TRISE hope it helps, -- tk. : Tjabo Kloppenburg : Student der Technischen Datenverarbeitung : http://www.rs.uni-siegen.de/studenten/tjabo : Picproject: click 'projekt' button on first page (german)

'PIC-Master / MPLAB-ICE and Windows NT'
1997\10\16@055248 by Andrew Warren

I wrote: If, like me, you think that NT-compatibility should be an absolute REQUIREMENT for any new development tools from Microchip, call your local Microchip rep or FAE and tell him so... Maybe if they hear it often enough, they'll actually do something about it. then Marc Schmaeche wrote: I would recommend you (and everybody else who wants to work with NT) asking Microchip again and again for NT support. Maybe we will then receive NT support in this millenium. and Tjaart van der Walt replied: I suppose If one was really tired of the quagmire of support, one could start mailing one's complaints directly to [list of Microchip upper management deleted]. Dudes: Microchip's informal user surveys have allegedly indicated that hardly any of us are using (or have plans to switch to) Windows NT. I think they could use more-accurate information than they've gotten from those informal surveys, so... If you own or plan to acquire a PIC-Master or the new MPLAB-ICE emulator within the next year, and either run Windows NT now or plan to upgrade to it within the next year, please send a PRIVATE email to me at: spamfastfwdTakeThisOuTix.netcom.com with the word "survey" in the subject line and the word "yes" in the message body. Just to be fair, if you own or plan to buy an emulator and intend to run it under Windows 3.x or Windows 95 rather than Windows NT, send me a PRIVATE email with the word "survey" in the subject line and the word "no" in the message body. After a week or so, I'll tabulate the results and send them to the appropriate people at Microchip. There are over 1200 subscribers to the PICLIST, and I would REALLY like to see responses from at least ten percent of you so we can have some confidence in the survey results... So please take just a minute to respond. Remember: "Survey" in the message SUBJECT, and "yes" or "no" in the message BODY. The survey results will be tabulated by an automated process, so if you want to say something more than simply "yes" or "no", send it in a separate message. Thanks. -Andy P.S. PLEASE remember to send those messages in PRIVATE email directly to me at: .....fastfwdspamBeGoneix.netcom.com Responses sent to the list will be ignored. === Andrew Warren - .....fastfwdTakeThisOuTEraseMEix.netcom.com === Fast Forward Engineering - Vista, California === http://www.geocities.com/SiliconValley/2499

1997\10\16@082128 by Mike Smith

<<Dudes: Microchip's informal user surveys have allegedly indicated that hardly any of us are using (or have plans to switch to) Windows NT. I think they could use more-accurate information than they've gotten from those informal surveys, so... If you own or plan to acquire a PIC-Master or the new MPLAB-ICE emulator within the next year, and either run Windows NT now or plan to upgrade to it within the next year, please send a PRIVATE email to me at:>> Clarification - is the MPLAB-ICE the same unit as the ICEPIC made by RF Solutions? MikeS <RemoveMEmikesmith_ozspamKILLspamrelaymail.net>

1997\10\16@091137 by Clyde Smith-Stubbs

On Thu, Oct 16, 1997 at 09:51:59PM +0930, Mike Smith wrote: > Clarification - is the MPLAB-ICE the same unit as the ICEPIC made by RF No, it's not. It's the PICMaster, made by Microchip. It has a bus card interface. -- Clyde Smith-Stubbs | HI-TECH Software Email: STOPspamclydeEraseMEhtsoft.com | Phone Fax WWW: http://www.htsoft.com/ | USA: (408) 490 2885 (408) 490 2885 PGP: finger clydespamBeGonehtsoft.com | AUS: +61 7 3354 2411 +61 7 3354 2422 --------------------------------------------------------------------------- ANSI C for the PIC! Now shipping! See http://www.htsoft.com for more info.

1997\10\16@091601 by Clyde Smith-Stubbs

On Thu, Oct 16, 1997 at 11:10:54PM +1000, I wrote: > On Thu, Oct 16, 1997 at 09:51:59PM +0930, Mike Smith wrote: > > > Clarification - is the MPLAB-ICE the same unit as the ICEPIC made by RF > > No, it's not. It's the PICMaster, made by Microchip. It has a bus > card interface. But I am probably talking through my hat. I didn't read Mike's message carefully enough, and in fact I don't know the answer to his question. Sorry.

1997\10\16@100803 by Andy Kunz

>Just to be fair, if you own or plan to buy an emulator and intend to >run it under Windows 3.x or Windows 95 rather than Windows NT, send >me a PRIVATE email with the word "survey" in the subject line and >the word "no" in the message body. ALL mfg's need to smarten up about this issue, not just Microchip and Parallax. MS plans to discontinue Win 9x support (and DOS I/O compatibility) soon after the next version comes out. After that, all Win cores will be based upon NT. That means no parallel port comms, unless you have a device driver to support it. It means NT-style serial comms. It means 32-bit apps. That is their plan for both HOME & OFFICE versions of the OS's. If you are smart, move to NT asap, and keep another machine around to run DOS-like stuff on. The future is coming. Finally! Andy ================================================================== Andy Kunz - Montana Design - 409 S 6th St - Phillipsburg, NJ 08865 Hardware & Software for Industry & R/C Hobbies "Go fast, turn right, and keep the wet side down!" ==================================================================

1997\10\16@155224 by Andrew Warren

Mike Smith <mikesmith_oz@spam@relaymail.net> wrote: > Clarification - is the MPLAB-ICE the same unit as the ICEPIC made by > RF Solutions? Mike: No; MPLAB-ICE is a new emulator with all the features of the PIC-Master and more. Microchip expects to introduce it by the middle of '98. -Andy === Andrew Warren - spam_OUTfastfwdspamix.netcom.com === Fast Forward Engineering - Vista, California === http://www.geocities.com/SiliconValley/2499

'Bit watches in MPLAB'
1997\10\17@022712 by tjaart

Does anyone know if it is possible to display a bit flag in a watch window *WITHOUT* the byte it belongs to. For instance, if you have a byte Flag1, and want to display bit 4 in the watch window, you have to enter Flag1:4 . This is not as easy to keep track of as, say BigErrorFlag. I have noticed that you cannot define a bit and then use that definition in the watch window. Is there a better way? -- Friendly Regards Tjaart van der Walt tjaartspam_OUTRemoveMEwasp.co.za _____________________________________________________________ | WASP International http://www.wasp.co.za/~tjaart/index.html | | R&D Engineer : GSM peripheral services development | | Vehicle tracking | Telemetry systems | GSM data transfer | | Voice : +27-(0)11-622-8686 | Fax : +27-(0)11-622-8973 | | WGS-84 : 26010.52'S 28006.19'E | |_____________________________________________________________|

'Bug with STATUS as destination in MPLAB-SIM 6.30 ('
1997\11\05@191324 by Dmitry Kiryashov

Hello All. I found bug in MPLAB-SIM v6.30 . In case when i use STATUS register as destination in MOVWF STATUS command the IRP and RP1 bits stay unchanged. But in real PIC16Cxx chip result of this operation change IRP and RP1 bits . WBR Dmitry .

'Using MPLAB'
1997\11\06@004235 by Dave Celsnak

Ok- I'm using a PICBASIC Compiler. It makes a source file (assembly language, w/ statements asking for include files), and it makes a HEX file. From what I am gathering, I can import the hex file to MPLAB. Correct? And my hex file should already have everything needed to be emulated (simulated?) ????? and the next step is (Help?) -Dave Celsnak College is a place to learn how much you don't know.

'icepic and mplab'
1997\11\06@163433 by XYGAX

I have recently obtained ICEPIC to speed development and its advertised as interfacing with MPLAB. HOW do you do this there is not software support on ICEPIC do you need a later version of mplab (3.12) Please help Steve.....

1997\11\06@165638 by Andrew Warren

XYGAX <spamPICLISTspamBeGoneMITVMA.MIT.EDU> wrote: > I have recently obtained ICEPIC to speed development and its > advertised as interfacing with MPLAB. > > HOW do you do this there is not software support on ICEPIC do you > need a later version of mplab (3.12) Steve: Yes, you need a later version... MPLAB versions 3.30 and above support the ICEPIC. The newest version of MPLAB is always available on Microchip's web site: http://www.microchip.com -Andy === Andrew Warren - spamfastfwdRemoveMEix.netcom.com === Fast Forward Engineering - Vista, California === http://www.geocities.com/SiliconValley/2499

1997\11\07@001258 by Rob Bristow

Visit the Rf Solutions site. http://www.rfsolutions.co.uk/ More specifically go to page http://www.rfsolutions.co.uk/PICTools/ICEPIC/software/mplabver.html You need to download the file from this page as a plug-in to get ICEPIC to run under MPLAB Goodluck Martin McArthur ---------- From: Andrew Warren[SMTP:KILLspamfastfwdspam_OUTspam_OUTIX.NETCOM.COM] Sent: Thursday, November 06, 1997 11:54 PM To: PICLISTspam_OUTTakeThisOuTMITVMA.MIT.EDU Subject: Re: icepic and mplab XYGAX <spamBeGonePICLISTspamspamBeGoneMITVMA.MIT.EDU> wrote: > I have recently obtained ICEPIC to speed development and its > advertised as interfacing with MPLAB. > > HOW do you do this there is not software support on ICEPIC do you > need a later version of mplab (3.12) Steve: Yes, you need a later version... MPLAB versions 3.30 and above support the ICEPIC. The newest version of MPLAB is always available on Microchip's web site: http://www.microchip.com -Andy === Andrew Warren - @spam@fastfwdspamspam_OUTix.netcom.com === Fast Forward Engineering - Vista, California === http://www.geocities.com/SiliconValley/2499

1997\11\07@102519 by Stephen H Alsop

Get MPLAB 3.31 and the icepic 1.10.00 (not Mplab version 3.30 as 3.30 has a program download problem with icepic). The system works well and is to be recommended Regards Stephen H Alsop email: KILLspamsteveKILLspams.ssystems.easynet.co.uk S&S Systems Ltd www: http://easyweb.easynet.co.uk/~s.ssystems ---------- : From: XYGAX <KILLspamXYGAXspamspamAOL.COM> : To: PICLISTKILLspam.....MITVMA.MIT.EDU : Subject: icepic and mplab : Date: 06 November 1997 21:23 : : I have recently obtained ICEPIC to speed development and its advertised as : interfacing with MPLAB. : : HOW do you do this there is not software support on ICEPIC do you need a later : version of mplab (3.12) : : Please help : : Steve.....

'Looking for EEPROM library for MPLAB-C'
1997\11\10@130338 by Eric van Es

Hiya guys I'm _desperately_ looking for the correct(ed) ee14.h and ee14.lib files for MPLAB-C. Apparently the ones that came with my MPLAB have errors. I'm not a C man, so I don't even have an idea of where to start looking for the errors. Cheers! -- Eric van Es | Cape Town, South Africa vanesspamBeGoneilink.nis.za | http://www.nis.za/~vanes LOOKING FOR TEMPORARY / HOLIDAY ACCOMODATION? http://www.nis.za/~vanes/accom.htm

1997\11\10@134327 by WF AUTOMA��O

Eric van Es wrote: > > Hiya guys > > I'm _desperately_ looking for the correct(ed) ee14.h and > ee14.lib files for MPLAB-C. Apparently the ones that came with > my MPLAB have errors. I'm not a C man, so I don't even have an > idea of where to start looking for the errors. > > Cheers! > -- > Eric van Es | Cape Town, South Africa > vanesspam_OUTilink.nis.za | http://www.nis.za/~vanes > LOOKING FOR TEMPORARY / HOLIDAY ACCOMODATION? > http://www.nis.za/~vanes/accom.htm I have used this library with success! Miguel.

'Prog to generate I2C stimulus files for MPLAB?'
1997\12\19@163758 by Joe McCauley

Hi, Does anyone know of a program which will run under MSDOS or Windows which will genetate stimulus files for the mplab simulator. I need to generate some I2C to test the I2C module on a 16C74. Unfortunatly I dont have a 16c74 pod for my Picmaster. Ideally what I am looking for would take in a hex string representing the I2C data and ACK bits sent from a master to the PIC, and generate the stim file. Any ideas gratefully recieved. Joe

1997\12\19@163758 by Joe McCauley

1997\12\19@170118 by Walter Markiw

At 21:21 19/12/97 +0000, you wrote: >Hi, > >Does anyone know of a program which will run under MSDOS or Windows which >will genetate stimulus files for the mplab simulator. I need to generate >some I2C to test the I2C module on a 16C74. Unfortunatly I dont have a >16c74 pod for my Picmaster. Ideally what I am looking for would take in a >hex string representing the I2C data and ACK bits sent from a master to the >PIC, and generate the stim file. > >Any ideas gratefully recieved. > >Joe > > Hi,Joe I read in the mplab manual that it doesm't support ssp simulation in IC2 mode. Cheers,Walter

'HELP! MPLAB: How to add pin to the display?'
1998\01\13@165812 by Nigel Broad

I have just started using MPLAB version 3.12. Can anyone advise how to view the logic value on an output pin, ie what is the equivalent to the DOS MPSIM command AD RA0 ? -- Nigel Broad

'Linking and MPLAB (newbie question)'
1998\01\22@100312 by Charles Bennett

part 0 574 bytes content-type:text/x-vcard; charset=x-user-defined; name="vcard.vcf" (decoded 7bit) I can add the files and even get the /o addition to create object files, but the linker never seems to get invoked. The online "help" doesn't mentions linking but never shows how. MPLAB is the latest version from microchip. Thanks Chuck Content-Type: text/x-vcard; charset=x-user-defined; name="vcard.vcf" Content-Transfer-Encoding: 7bit Content-Description: Card for Charles Bennett Content-Disposition: attachment; filename="vcard.vcf" Attachment converted: wonderland:vcard.vcf (TEXT/CSOm) (00010F05)

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