Searching \ for '%MPLAB Prob%' in subject line. ()
Make payments with PayPal - it's fast, free and secure! Help us get a faster server
FAQ page: www.piclist.com/techref/microchip/languages.htm?key=mplab
Search entire site for: 'MPLAB Prob'.

_Sub string match.
PICList Thread
'MPLAB Prob'
1995\12\11@153317 by Ben Kwok-Yiu Li

picon face
Is anyone encountering a error about computing the toolbar size?

_____________________________________________________________________________
| spam_OUTbenliTakeThisOuTspamuclink2.berkeley.edu | .....benliKILLspamspam@spam@ocf.berkeley.edu | benlispamKILLspambdt.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\11@193431 by Andrew Warren

flavicon
face
Ben Kwok-Yiu Li <.....PICLISTKILLspamspam.....MITVMA.MIT.EDU> wrote:

> Is anyone encountering a error about computing the toolbar size?

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?

-Andy

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

1995\12\12@100311 by Christer Johansson

picon face
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: cjspamspam_OUTalgonet.se *
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
* Vi saljer Parallax, Inc. BASIC Stamp's produkter i Skandinavien *
   >> World Wide Web - http://www.algonet.se/~cj/catalog.html <<
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

1995\12\12@140951 by Pete.Brink

picon face
     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 <@spam@cjKILLspamspamALGONET.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: KILLspamcjKILLspamspamalgonet.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

picon face
    >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 <RemoveMEcjTakeThisOuTspamALGONET.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: spamBeGonecjspamBeGonespamalgonet.se *
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
* Vi saljer Parallax, Inc. BASIC Stamp's produkter i Skandinavien *
   >> World Wide Web - http://www.algonet.se/~cj/catalog.html <<
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

1995\12\12@150050 by Andrew Warren

flavicon
face
Christer Johansson <TakeThisOuTcjEraseMEspamspam_OUTALGONET.SE> wrote:

> Sorry to jump right in. Does MPLAB include a simulator in the
> Windows environment ?

Not yet, Christer... The simulator plug-in is expected to be
available by the second quarter of 1996.

-Andy

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


'MPC & MPLAB problems....'
1996\06\07@190607 by Carlos E Lopez-Reyna
flavicon
face
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

flavicon
face
From:    Carlos E Lopez-Reyna <clopezEraseMEspam.....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
EraseMEjperryspamnorfolk.infi.net

1996\06\10@113503 by Jim Kape

picon face
    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 <RemoveMEjperryEraseMEspamEraseMENORFOLK.INFI.NET> at Internet_Exchange
Date:    6/9/96 12:57 AM


From:    Carlos E Lopez-Reyna <RemoveMEclopezspam_OUTspamKILLspamENIAC.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
RemoveMEjperryTakeThisOuTspamspamnorfolk.infi.net


'Picstart Plus and MPLAB problems'
1996\10\10@233935 by Barry Bine
picon face
       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

flavicon
face
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.
EraseMEoptoengspamspamspamBeGonewhidbey.com
non-contact sensing and optoelectronics specialists

1996\10\11@071504 by Stefan Bormann

flavicon
face
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  RemoveMEs.bormannKILLspamspamtu-bs.de

FREMO: ourworld.compuserve.com/homepages/shipmill/inhalt.htm

1996\10\12@032110 by andreabelian

picon face
Barry Bine wrote:
{Quote hidden}

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.

flavicon
face
Andre Abelian wrote:
{Quote hidden}

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.


'MPLAB problems - cured'
1998\06\30@133542 by Russell McMahon
picon face
Pse ignore previous post.
Software uninstall and re-install produced a menu with "File" thereon and
'Import" on it but the "import" was greyed out. Exiting MPLAB and
re-starting produced desired result. Very Strange. (Ghost in the machine?)


'MPLAB problems....'
1998\10\06@145038 by Tobias
flavicon
face
Hello,

I have a PICstart plus programmer and running MPLAB for Windows/16 3.99.21,
After upgrading to WIN98 i now have big problems. MPLAB seems to "hang"
randomly (quite aften), and following message appear:

Please verify serial and power
connections and reset the programmer (0020,01,00,00)

There are nothing wrong with the connections, and resetting doesnt help much.

On my old 386 with win3.11 everything work great.

Anybody had similar problems, or know what could be the problem ????

Also:
I have firmware 1.20.00 on my PICstart plus programmer, how do I upgrade
the firmware ???

best regards,
tobias

1998\10\06@153936 by Piu Cheng

flavicon
face
  The same thing happens if you uses WINNT  which seems the
MPLAB doesn't support WIN98 and WINNT.

   Ivan

On Tue, 6 Oct 1998, Tobias wrote:

{Quote hidden}

1998\10\06@154603 by Quentin

flavicon
face
Hi
I can't help you with your problem but post a message to Microchip's web
board. MC's engineers seems to hang out there.

Also go to:
www.microchip.com/10/Tools/mTools/PICSTART/index.htm
To find out how to upgrade.

Quentin

1998\10\06@164150 by Bob Carter

flavicon
face
I was having similar problems using recent versions of MPLAB with Windows
3.1, but MPLAB v3.99.23 seemed to correct the problem. To upgrade your
firmware, look in the readme files that are installed with MPLAB. You can
buy windowed (17C44 I think) and program new firmware into it, then swap
with old chip. Microchip might even be dishing out firmware upgrades,
without all the hassle.

Thanks,
Bob Carter, design engineer

Wildlife Materials, Inc.
1031 Autumn Ridge Road
Carbondale, IL   62901

voice (618) 549-6330 (ext. 225)
fax   (618) 457-3340
email wolftechSTOPspamspamspam_OUTmidwest.net
www   http://www.wildlifematerials.com


'[pic]: MPLAB problems'
2000\08\13@210543 by Tom Messenger
flavicon
face
I'm having problems getting MPLAB working correctly. If anyone has an idea,
I would greatly appreciate hearing about it. Various things did not work
right in version 5 so I tried 5.11.02 and had the same results.  Here is
what the main problems show up as:

1.      a. Click on File, New
       b. New Project dialog box opens w/file extension set to .pjt
       c. Type a name: test.pjt
       d. box opens:
          New Project Error w/message:
          DialogBox failed.
          hInst=78be hFrameWnd=830
       e. Click OK, message closes, leaves a text box named Untitled1

2.      a. Click on Project, Install language tool
       b. box opens:
          Install Tool Error w/message:
          DialogBox() call failed.
          hInst=78be hFrameWnd=830

3.      a. Click on Options, Current modes...
       b. Nothing happens. I believe a dialog box should open showing current
settings.

4. I am running MPLAB version 5.0 on another machine; it works. On this
computer, it did the same things listed above. So I downloaded the latest
and greatest version MPLAB v5.11.02 and the results are the same.

5. Next, I checked which .dll files are required and I have them all.  Here
is what I found MPLAB wanting to have:

BC450RTL.DLL
BWCC.DLL
COMMDLG.DLL
DDEML.DLL
GDI.EXE
KRNL386.EXE
SHELL.DLL
SS16D25.DLL
STIMULUS.DLL
TAB16D20.DLL
TOOLHELP.DLL
USER.EXE
WIN87EM.DLL

I just assumed that maybe I was missing a .dll file; this doesnot look to
be the case unless I have the file located somewhere that MPLAB can't find it.

These are representative of some of the problems I'm having.

Any ideas?

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

2000\08\14@121856 by Quitt, Walter

flavicon
face
I had this exact same problem.  I uninstalled MPLAB and reinstalled it.
It did NOT help.  After much frustration I called Mchip.  The techies walked
me through some stuff and it did not help.  It seems something gets hosed.
The unistall does not remove the affected file or setting.  I ended up
reformatting
and starting over.  WHAT A PAIN!  I am up and running in MPLAB 5.11 now for
the last month or two.

GL, Walt

               {Original Message removed}

2000\08\14@123115 by Tim Hamel

picon face
In a message dated 8/14/00 9:19:44 AM Pacific Daylight Time,
KILLspamwquittspamBeGonespamMICROJOIN.COM writes:

> I had this exact same problem.  I uninstalled MPLAB and reinstalled it.
>  It did NOT help.  After much frustration I called Mchip.  The techies
walked
>  me through some stuff and it did not help.  It seems something gets hosed.
>  The unistall does not remove the affected file or setting.  I ended up
>  reformatting
>  and starting over.  WHAT A PAIN!  I am up and running in MPLAB 5.11 now for
>  the last month or two.
>
>  GL, Walt
<snip detailed explanation>

Maybe I can take a shot at this.  Of the files listed by the original poster,
commdlg/ctrl.dll are the important ones. User.exe, GDI.exe, etc aren't the
cause of this mess. Anyways, here's what you can try. If you're usin Win98,
navigate to your \windows\sysbckup folder and copy commdlg.dll to your
\windows\system folder; confirm replace. If that fails, try and extracting a
fresh copy of the DLL from your CD ( I can give you details via email).

Regards,

Tim Hamel

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

2000\08\14@161335 by Tom Messenger

flavicon
face
Per Tim Hamels suggestion, I copied commdlg.dll and ctrl.dll from the
\sysbckup folder into the \system folder and rebooted: no joy.  The problem
computer is at home and that was all the time I had at lunch; tonight I'll
look at trying to get fresh copies from my CD. And yes, Tim, it is '98.

In the meantime if anyone else has a suggestion, feel free to speak up!
Thanks!
Tom M.>

<snip detailed explanation>
{Quote hidden}

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

2000\08\14@172129 by Tim Hamel

picon face
Tom (and the original poster),

My apologies, I thought that would fix it seeing as how all the errors are
pointing to dialog boxes. I'm going to download the problematic MPLAB and see
if I can get this error and hopefully figure out a cure.

Regards,

Tim Hamel

In a message dated 8/14/00 1:14:03 PM Pacific Daylight Time,
EraseMEkristspamEraseMETHEGRID.NET writes:

> Per Tim Hamels suggestion, I copied commdlg.dll and ctrl.dll from the
>  \sysbckup folder into the \system folder and rebooted: no joy.  The problem
>  computer is at home and that was all the time I had at lunch; tonight I'll
>  look at trying to get fresh copies from my CD. And yes, Tim, it is '98.
>
>  In the meantime if anyone else has a suggestion, feel free to speak up!
>  Thanks!
>  Tom M.>

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

2000\08\14@180814 by Tim Hamel

picon face
I THINK I might have a solution! It appears bwcc.dll is "Borland Windows
Custom Control Library." I'm thinking that maybe you might have two copies
that are conflicting with eachother. I wasn't able to reproduce the problems
noticed by others, but a little investigation did find the error messages
embedded in mplab.exe.

If you're up to it, try this. Find copies of bwcc.dll in either in your
\windows or \windows\system directory and rename them. Then, make sure
bwcc.dll exists in your mplab directory and that it has a timestamp of August
7th, 2000, 8:07AM (Version 2.04). IF this works, I'll make sure to give
Microchip a jingle and update them on this problem.

Regards,

Tim Hamel

In a message dated 8/14/00 2:19:17 PM Pacific Daylight Time, TekPhobia writes:

> Tom (and the original poster),
>
>  My apologies, I thought that would fix it seeing as how all the errors are
> pointing to dialog boxes. I'm going to download the problematic MPLAB and
see
> if I can get this error and hopefully figure out a cure.
>
>  Regards,
>
>  Tim Hamel

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

2000\08\14@182503 by Tom Messenger

flavicon
face
Thanks Tim. I'll check it out when I get home tonight.

Tom M.>

At 06:07 PM 8/14/00 EDT, you wrote:
{Quote hidden}

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

'[PIC]: MPLAB problems resolved'
2000\08\21@105425 by Tom Messenger

flavicon
face
Earlier, I asked for help getting MPLAB to function correctly on one of my
computers (all other software *appeared* to be working ok).

Yesterday, I bit the bullet and did a re-install of Win98: bingo! No
problem. MPLAB works fine now. Something somewhere was seriously bent.

My thanks to those who made helpful suggestions! As usual the piclist is
the place to go for solutions, even uncommented ones!

Tom M.>

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

2000\08\21@120059 by Thomas C. Sefranek

face picon face
Tom Messenger wrote:

> Earlier, I asked for help getting MPLAB to function correctly on one of my
> computers (all other software *appeared* to be working ok).
>
> Yesterday, I bit the bullet and did a re-install of Win98: bingo! No
> problem. MPLAB works fine now. Something somewhere was seriously bent.
>
> My thanks to those who made helpful suggestions! As usual the piclist is
> the place to go for solutions, even uncommented ones!
>
> Tom M.>

I have been seeing "Processor could not be halted..." a LOT now.
But if I reset and "run to here" again, it often works...

And it looks like the old ASYNC port problem is back in the latest version.
BTFSC  TXSTA, TRMT and it shows the bit SET but it still skips to the next
instruction.


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

--
 *
 |  __O    Thomas C. Sefranek  .....tcsspam_OUTspamcmcorp.com
 |_-\<,_   Amateur Radio Operator: WA1RHP
 (*)/ (*)  Bicycle mobile on 145.41, 448.625 MHz

ARRL Instructor, Technical Specialist, VE Contact.
hamradio.cmcorp.com/inventory/Inventory.html
http://www.harvardrepeater.org

--
http://www.piclist.com hint: To leave the PICList
TakeThisOuTpiclist-unsubscribe-request.....spamTakeThisOuTmitvma.mit.edu>

2000\08\21@131845 by Olin Lathrop

flavicon
face
> I have been seeing "Processor could not be halted..." a LOT now.
> But if I reset and "run to here" again, it often works...

I ran into that a few times where it didn't make sense either (ICE powered
up, target board powered up, etc).  It turned out that the connector where
the power supply cord plugs into the ICE 2000 isn't what it should be.  I
got rid of my problems by pushing it in REAL HARD.  I can sometimes even see
the lights on the front of the unit blink if the power cable isn't
absolutely in all the way.

> And it looks like the old ASYNC port problem is back in the latest
version.
> BTFSC  TXSTA, TRMT and it shows the bit SET but it still skips to the next
> instruction.

Keep in mind that the ICE often shows the true I/O state several cycles
late, although the bits are actually right inside the processor.


*****************************************************************
Olin Lathrop, embedded systems consultant in Devens Massachusetts
(978) 772-3129, TakeThisOuTolinKILLspamspamspamcognivis.com, http://www.cognivis.com

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

2000\08\21@161558 by Greg Maki

flavicon
face
"Thomas C. Sefranek" wrote:
{Quote hidden}

I just noticed today that in the Edit Project... dialog box where you
set the processor that it states that "Serial I/O is not simulated". I
wish I had noticed that a few days ago. It would have save me a lot of
time!

Greg Maki

--
http://www.piclist.com hint: To leave the PICList
RemoveMEpiclist-unsubscribe-requestspamspamBeGonemitvma.mit.edu>

2000\08\21@171328 by Thomas C. Sefranek

face picon face
Greg Maki wrote:

{Quote hidden}

I'm using the 18C452 and it does NOT say that!
(I do remember it for the 16 series...)
BUT... Thanks to you I found it's REAL limitation of 25 MHz.
Perhaps thats the problem.

I'll let you know.

>
>
> Greg Maki
>
> --
> http://www.piclist.com hint: To leave the PICList
> spamBeGonepiclist-unsubscribe-request@spam@spamspam_OUTmitvma.mit.edu

--
 *
 |  __O    Thomas C. Sefranek  TakeThisOuTtcsspamspamcmcorp.com
 |_-\<,_   Amateur Radio Operator: WA1RHP
 (*)/ (*)  Bicycle mobile on 145.41, 448.625 MHz

ARRL Instructor, Technical Specialist, VE Contact.
hamradio.cmcorp.com/inventory/Inventory.html
http://www.harvardrepeater.org

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


'[PIC]: MPLAB problem'
2001\01\14@181130 by Igor Pokorny
flavicon
face
Hello:

I have a problem when I open a project in MPLAB. Anytime when I do this I
get a message "Invalid processor detected in project or MPLAB ini file". It
happens in WIN98 as well in WIN2000. I tried to change version of the MPLAB
but the result is still the same.
Any suggestions?

Regards

Igor

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


2001\01\14@204139 by Tom Mariner

flavicon
face
Sometimes the .pjt file gets corrupted. Open it using some other editor
(notebook, etc.) and see if your "Processor=" line has something funny.

Tom

{Original Message removed}

2001\01\15@065749 by Alvaro Deibe Diaz

flavicon
face
I have the same problem. I've looked in the .pjt and in the .ini file, and
both have the same (apparently) wright line "Processor=...".  Don't know how
to solve this problem.

----- Mensaje original -----
De: Tom Mariner <RemoveMEtmarinerEraseMEspamspam_OUTOPTONLINE.NET>
Para: <@spam@PICLISTRemoveMEspamEraseMEMITVMA.MIT.EDU>
Enviado: lunes, 15 de enero de 2001 2:41
Asunto: Re: [PIC]: MPLAB problem


> Sometimes the .pjt file gets corrupted. Open it using some other editor
> (notebook, etc.) and see if your "Processor=" line has something funny.
>
> Tom
>
> {Original Message removed}

'[PIC]: mplab problems'
2001\01\24@075017 by John Walshe

flavicon
face
Hi guys,
   I tried searching the archive 'cos I'm sure it was discussed - but the
archive search engine is sick!
I'm trying to simulate a bit of code but the control of the windows is
constantly getting mixed up. If I try to single step in the code window the
program memory window does the single stepping. This is not a huge problem
when starting from a reset for the first time, but if I change to a modify
window,async input window etc and then return to the code window to
continue - the control reverts to the program memory eventhough the code
window is highlighted. At this stage nothing short of exiting MPLAB will fix
it.

I'm using MPLAB 5.02 on NT4 but I also have the problem on another PC with
win98.

Any ideas for/pointers to a fix?

John

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


2001\01\25@105530 by jamesnewton

face picon face
Not the one at
http://www.piclist.com/techref/postbot.asp
!

You just need to fill out the form and get your password PIN

---
James Newton (PICList Admin #3)
EraseMEjamesnewtonspam@spam@piclist.com 1-619-652-0593
PIC/PICList FAQ: http://www.piclist.com or .org

{Original Message removed}


'[PIC]:MPLAB problem. Please help!'
2001\03\28@124521 by Thomas N
picon face
Hello everyone,

Why do I have to make a port become an output port before I can modify its
content when I do the simulation?

When I simulate my code, and I want to modify a state of certain pin of a
port (to simulate an external input to the IC), I always have to make this
IO pin to be output first before I can make the change.  Is there a solution
for this?

Best regards.

Thomas




_________________________________________________________________________
Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com.

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


2001\03\28@133915 by Alan B. Pearce

face picon face
>Why do I have to make a port become an output port before I can modify its
>content when I do the simulation?

>When I simulate my code, and I want to modify a state of certain pin of a
>port (to simulate an external input to the IC), I always have to make this
>IO pin to be output first before I can make the change.  Is there a solution
>for this?

Look under the stimulus menu of MPLAB. You can set the state of an input port
there. It is also possible to set up a standard test file to do the stimulus for
you. Very useful if trying to simulate bit banging comms.

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


2001\03\28@141812 by Olin Lathrop

face picon face
> When I simulate my code, and I want to modify a state of certain pin of a
> port (to simulate an external input to the IC), I always have to make this
> IO pin to be output first before I can make the change.  Is there a
solution
> for this?

Check out the various simulator stimulus functions in the DEBUG menu.


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

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


2001\03\28@160703 by J.A.YOUNG

flavicon
face
Quoting Thomas N <spamBeGonethomasn101EraseMEspamHOTMAIL.COM>:

> Hello everyone,
>
> Why do I have to make a port become an output port before I can modify its
> content when I do the simulation?
>
> When I simulate my code, and I want to modify a state of certain pin of a
> port (to simulate an external input to the IC), I always have to make this
> IO pin to be output first before I can make the change.  Is there a solution
> for this?
>
By 'modifying the state', I'm presuming you're meaning put an input signal to a
pin. Assuming you've set the pin to INPUT (TRISB=1 sets pinRB0 to input, all
others to Output) in the code, you need to use Asynchronous Stimulus. Under the
Debug menu select Simulator Stimulus (or something similar) and another menu
will pop up with Asynchronous Stimulus. Click it, and the box will come up. By
using right click, you can then choose 'toggle' and assign a pin e.g.RB0, then
left-click during simulation to produce an input. The IO pin must be set up as
an _INPUT_ in the code for this to work.

Try looking at the MPLAB tutorial in the manual(if you have it).

John

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


2001\03\28@194322 by Thomas N

picon face
John,

Thank you!  It works now!
thomas


{Quote hidden}

_________________________________________________________________________
Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com.

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



'[PIC]: Strange MPLAB problem....windows wont come '
2002\08\12@090602 by Micro Eng
picon face
Here is a strange one I found this weekend....after the kids were playing on
the machine

I bring up a project...that has been working fine and now...I cannot edit
the project, ICD window wont come up, and build (F10) windows wont come up.
Basically, I have a fancy editor.  Oh, I can bring up the eeprom window,
breaks, listings...just anything to do with the project doesn't seem to want
to work.

I suppose I can reinstall the thing, but short of that...anyone else run
into this?  I can't recall the version, but im guessing its the same I have
on my work machine of 5.5

Comments?

_________________________________________________________________
Send and receive Hotmail on your mobile device: http://mobile.msn.com

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


2002\08\12@173354 by Jinx

face picon face
>
>a project...that has been working fine and now...I cannot edit

Anything to do with Options/Development Mode ?

My MPLAB occassionally drops into Editor Only mode, bless it

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


2002\08\12@180145 by Barry Gershenfeld

face picon face
>>a project...that has been working fine and now...I cannot edit
>
>Anything to do with Options/Development Mode ?
>
>My MPLAB occassionally drops into Editor Only mode, bless it

1st guess: Same as Jinx said.

2nd guess: Try to create a new project, as a reality check.

Barry

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


2002\08\15@142734 by Micro Eng

picon face
Tried all those tricks...because I've seen that before as well.
strange....


{Quote hidden}

_________________________________________________________________
Chat with friends online, try MSN Messenger: http://messenger.msn.com

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



'[PIC]:wisp628/mplab problem writing/verifying fuse'
2003\06\24@100128 by Stephen Evans
flavicon
face
i have a wisp628 programmer that i know works because i have been
successful writing sample hex files to it.

my problem seems to be with hex files generated by mplab. when i try to
load them with wisp.exe or xwisp.py i get what look like verification
errors on the fuses.

here is the error when using wisp.exe ...

--------------------------------------------------------------------------------------
C:\Program Files\XWisp>wisp go volser.hex
wisptool 4.11
hardware Wisp628 1.07
target auto-detect ... target is a 16f877 rev 05
patch
end patch
program fuses a=0000 d=FFFF
22:38:37.23 (02317230) fatal: send [w] 01110111 expected [w] 01110111
received [
?] 00111111 : check the connection to the target and retry
--------------------------------------------------------------------------------------

and here is the error when using xwisp.py ...

---------------------------------------------------------------------------------------
C:\PROGRA~1\XWisp>xwisp.py go volser.hex
XWisp 1.06, command line mode
>>> COM1
hardware: Wisp628 1.07 (fast)
target: 16f877, revision 05
write Fuses 2007Traceback (most recent call last):
 File "C:\PROGRA~1\XWisp\xwisp.py", line 2730, in ?
   XWisp_Main()
 File "C:\PROGRA~1\XWisp\xwisp.py", line 2727, in XWisp_Main
   Wisp_Line().Interpret()
 File "C:\PROGRA~1\XWisp\xwisp.py", line 2347, in Interpret
   self.Execute( Command )
 File "C:\PROGRA~1\XWisp\xwisp.py", line 2329, in Execute
   exec( 'self.CMD_' + Command.upper() + '()' )
 File "<string>", line 1, in ?
 File "C:\PROGRA~1\XWisp\xwisp.py", line 1826, in CMD_GO
   self.Bus_Target.Write_Verify( self.Patched_Image())
 File "C:\PROGRA~1\XWisp\xwisp.py", line 1685, in Write_Verify
   self.Write( Image, [ Region ] )
 File "C:\PROGRA~1\XWisp\xwisp.py", line 1647, in Write
   self.Put( Address, Image.Get( Address ))
 File "C:\PROGRA~1\XWisp\xwisp.py", line 1562, in Put
   self.Bus.Send_Expect(( '%04X' % Data ) + 'w' )
 File "C:\PROGRA~1\XWisp\xwisp.py", line 821, in Send_Expect
   raise self.WBus_Protocol_Error, \
__main__.WBus_Protocol_Error: send='000Ew' received='000E?'
-----------------------------------------------------------------------------------------

any help/ideas would be really appreciated

btw, the hex file loads just fine using my ICD.

thanks,

steve

--
http://www.piclist.com#nomail Going offline? Don't AutoReply us!
email spamBeGonelistservKILLspamspam@spam@mitvma.mit.edu with SET PICList DIGEST in the body

2003\06\24@101508 by

flavicon
face
There is a problem when wisp tries to set config bits that
are "unsetable" and always read back as "0" (or "1", can't
remember) and will mess up the verify. Note though that
the config bits are set correctly (if specified correctly
in your code, of course). I had this problem with a 18f252
and solved it by ANDing (or ORing) the _CONFIG setting with
a value that forced the unsetable bits to the default value
when read back, so the verify passed.

If you check the manual page 142, it says about the
"unimplemeted" bits, that they are "read as "1"".
These bits has to be set to "1" in MPLAB also, if not
the verify in wisp will fail.

Wouter has talked about "learning" the wisp software
which bits are "unimplemented", so his software could
take carer of this...

I don't think that this would be different in the 16f
series from the 18f series, since it's a wisp issue.

The ICD might very well "know" about this...

Jan-Erik.

{Original Message removed}

2003\06\25@110047 by Stephen Evans

flavicon
face
thanks to all for your help on this.

i changed my config settings such that only those bits that i needed were turned on which fixed my problem (so there was a problem in my code in that some config bits were incorrectly set).

btw, John Nall, the new version of xwisp.py did not solve the problem.

thanks again,

steve








Jan-erik Söderholm (QAC) <Jan-erik.Soderholmspam_OUTspam@spam@PAC.ERICSSON.SE>
Sent by: pic microcontroller discussion list <spamBeGonePICLIST@spam@spamMITVMA.MIT.EDU>
06/24/2003 10:14 AM
Please respond to pic microcontroller discussion list

        To:     RemoveMEPICLISTEraseMEspamKILLspamMITVMA.MIT.EDU
       cc:         Subject:        Re: [PIC]:wisp628/mplab problem writing/verifying fuses


There is a problem when wisp tries to set config bits that
are "unsetable" and always read back as "0" (or "1", can't
remember) and will mess up the verify. Note though that
the config bits are set correctly (if specified correctly
in your code, of course). I had this problem with a 18f252
and solved it by ANDing (or ORing) the _CONFIG setting with
a value that forced the unsetable bits to the default value
when read back, so the verify passed.

If you check the manual page 142, it says about the
"unimplemeted" bits, that they are "read as "1"".
These bits has to be set to "1" in MPLAB also, if not
the verify in wisp will fail.

Wouter has talked about "learning" the wisp software
which bits are "unimplemented", so his software could
take carer of this...

I don't think that this would be different in the 16f
series from the 18f series, since it's a wisp issue.

The ICD might very well "know" about this...

Jan-Erik.

{Original Message removed}

2003\06\25@110505 by

flavicon
face
What "new" version ?
Jan-Erik.


Stephen Evans wrote :

> btw, John Nall, the new version of xwisp.py did not solve the problem.

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

2003\06\25@124920 by John Nall

flavicon
face
At 05:03 PM 6/25/2003 +0200, Jan-Erik wrote:

> >What "new" version ?
> >Jan-Erik.
>
>
> >Stephen Evans wrote :
>
> > btw, John Nall, the new version of xwisp.py did not solve the problem.

Back when I was having a similar problem, Wouter and I had a little
interchange off line, which resulted in him sending me a modified copy of
xwisp.py which he felt would solve the problem.  Since I was using your
(Jan-Erik) version of __CONFIG, my problem already had been solved and I
have not yet tested the newer version of xwisp.  So I forwarded it to Steve
hoping it might help him.  Apparently it did not. :-(

(I keep suggesting that people buy things from Wouter, in the hope that his
company will become large and that he can hire an efficient young lady
whose job will be to keep everything on his website up to date with the
latest and greatest. :-)

John

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

2003\06\26@163735 by Wouter van Ooijen

face picon face
> my problem seems to be with hex files generated by mplab.
> when i try to
> load them with wisp.exe or xwisp.py i get what look like verification
> errors on the fuses.

I lost track of which people I sent the fix for this problem, if not yet
to you email me off-list.

Wouter van Ooijen

-- -------------------------------------------
Van Ooijen Technische Informatica: http://www.voti.nl
consultancy, development, PICmicro products

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

2003\06\26@165013 by

flavicon
face
Any special reason not to update the on-line copy ?
Desn't it work for everyone ?
Jan-Erik.

-----Original Message-----
From: Wouter van Ooijen [wouterspam@spam@VOTI.NL]
Sent: den 26 juni 2003 22:37
To: EraseMEPICLISTRemoveMEspamSTOPspamMITVMA.MIT.EDU
Subject: Re: [PIC]:wisp628/mplab problem writing/verifying fuses


> my problem seems to be with hex files generated by mplab.
> when i try to
> load them with wisp.exe or xwisp.py i get what look like verification
> errors on the fuses.

I lost track of which people I sent the fix for this problem, if not yet
to you email me off-list.

Wouter van Ooijen

-- -------------------------------------------
Van Ooijen Technische Informatica: http://www.voti.nl
consultancy, development, PICmicro products

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

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


'[PIC] PIC18F2520 and MPLAB problem'
2006\11\26@232332 by David
flavicon
face
I have recently purchased a bunch of PIC18LF2520 micros as a replacement
for PIC18LF252 that are currently being used in my applications.

I am having trouble getting the code to run correctly. The program has a
bit-bashed serial routine that sends data just after powerup. I can get
the code running when I am in Debug mode with ICD2 but when I switch to
Programmer, the device no longer transmits data out the allocated pin.

The oscillator appears to be running ok on the micro and MCLR is high.
I am using MPLAB v7.5, Hi Tech C compiler V9.5 PL2 and ICD2 debugger.

Having spent a long time on the phone with the local Microchip field
tech, I am no further ahead.

Has anyone had a similar issue and know how to resolve it. Could there
be a bug in MPLAB V7.5 that is not allocating the config bits correctly ?


Thanks

Regards

David

2006\11\27@044005 by peter green

flavicon
face

> I am having trouble getting the code to run correctly. The program has a
> bit-bashed serial routine that sends data just after powerup. I can get
> the code running when I am in Debug mode with ICD2 but when I switch to
> Programmer, the device no longer transmits data out the allocated pin.
have you already been through all the obvious stuff like watchdog timer, lvp etc

also consider power supply decoupling, the ICD2 debug connector seems to have sufficiant capactiance on the target power supply rail to sometimes make a cuircuit with inadequate decoupling work.



'[pic]: mplab problem'
2011\07\20@175056 by Andre Abelian
picon face
Hi all,

I am having problem with mplab 8.7 on 3 different pc exact same problem.
watch window is open. any time I click on watch window then I click on main
window top portion of mplab like about 6 inches from the top turns gray and as soon
as I minimize and maximize it goes back to normal. any idea?
thanks

A

2011\07\20@180247 by jim

flavicon
face


Andre,

It sounds like the MPLAB download file may have gotten corrupted
somehow while being downloaded.   Try reinstalling a newly downloaded version to see if it persists.  If
it does, try reloading the  video driver associated with MPLAB.   Also, make sure you have enough
main memory in the PC's,  expecially if they share main memory.  
Regards,

Jim

> ---{Original Message removed}

2011\07\20@182256 by Andre Abelian

picon face
Jim,

for sure its not download issue and all 3 pc's I have 8 gig ram and video cards are 512 mb.
I tried reinstll no change.

AA



________________________________
From: "RemoveMEjimKILLspamspamTakeThisOuTjpes.com" <spamBeGonejimspam@spam@jpes.com>
To: Microcontroller discussion list - Public. <RemoveMEpiclistspam_OUTspammit.edu>
Sent: Wed, July 20, 2011 3:02:44 PM
Subject: RE: [pic]: mplab problem



Andre,

It sounds like the MPLAB download file may have gotten corrupted
somehow while being downloaded.  Try reinstalling a newly downloaded version to see if it persists.  If
it does, try reloading the video driver associated with MPLAB.   Also, make sure you have enough
main memory in the PC's, expecially if they share main memory.  
Regards,

Jim

> ---{Original Message removed}

2011\07\20@184043 by Isaac Marino Bavaresco

flavicon
face
Em 20/7/2011 19:22, Andre Abelian escreveu:
> Jim,
>
> for sure its not download issue and all 3 pc's I have 8 gig ram and video cards
> are 512 mb.
> I tried reinstll no change.
>
> AA


Certainly the installer checks the integrity of the installation files.
It shouldn't be a corrupted file, the installer would not even install
the software.

Maybe you are using a very uncommon video board or it may be a bug in
the board's driver.


Isaac



{Quote hidden}

>> ---{Original Message removed}

2011\07\20@215710 by Andre Abelian

picon face
Isaac,

at work I have 1 year old HP workstation with good spec. at home I have macpro desktop
with good spec.
AA



________________________________
From: Isaac Marino Bavaresco <RemoveMEisaacbavarescoKILLspamspam@spam@yahoo.com.br>
To: Microcontroller discussion list - Public. <piclistspamBeGonespam.....mit.edu>
Sent: Wed, July 20, 2011 3:40:45 PM
Subject: Re: [pic]: mplab problem

Em 20/7/2011 19:22, Andre Abelian escreveu:
> Jim,
>
> for sure its not download issue and all 3 pc's I have 8 gig ram and video cards
>
> are 512 mb.
> I tried reinstll no change.
>
> AA


Certainly the installer checks the integrity of the installation files.
It shouldn't be a corrupted file, the installer would not even install
the software.

Maybe you are using a very uncommon video board or it may be a bug in
the board's driver.


Isaac



{Quote hidden}

>> ---{Original Message removed}

2011\07\21@044916 by alan.b.pearce

face picon face
> Hi all,
>
> I am having problem with mplab 8.7 on 3 different pc exact same problem.
> watch window is open. any time I click on watch window then I click on main
> window top portion of mplab like about 6 inches from the top turns gray and as
> soon
> as I minimize and maximize it goes back to normal. any idea?
>
> thanks
>
> AA

Which 8.7 version???

8.70 had problems.

8.73 had problems, and was temporarily withdrawn.

The current download is 8.73a., which is supposed to have the problems fixed.


-- Scanned by iCritical.

2011\07\21@110356 by Andre Abelian

picon face
I tried using virtual machine xp 32bit  it worked fine. Only it does on  win7 64 bit.
I can tell mplab is million times better then before. microchip is great they do fantastic job.




________________________________
From: "KILLspamalan.b.pearcespamspamBeGonestfc.ac.uk" <alan.b.pearcespamspamstfc.ac.uk>
To: RemoveMEpiclistspamBeGonespamRemoveMEmit.edu
Sent: Thu, July 21, 2011 1:46:56 AM
Subject: RE: [pic]: mplab problem

{Quote hidden}

Which 8.7 version???

8.70 had problems.

8.73 had problems, and was temporarily withdrawn.

The current download is 8.73a., which is supposed to have the problems fixed.



-- Scanned by iCritical.

2011\07\21@212938 by Xiaofan Chen

face picon face
On Thu, Jul 21, 2011 at 11:03 PM, Andre Abelian <KILLspamabelian.andrespamBeGonespamyahoo.com> wrote:
> I tried using virtual machine xp 32bit  it worked fine. Only it does on  win7 64
> bit.
> I can tell mplab is million times better then before. microchip is great they do
> fantastic job.

Microchip MPLAB 8.x is near their end of life and the future is MPLAB X.

It seems that IDEs become too complicated that many MCU or
MCU Compiler companies start to move to established IDE like
Eclipse (many, like ARM and MIPS, TI, Freescale, etc), Netbean
(Microchip MPLAB X) and Visual Studio Shell (Atmel Studio 5).

Of course some leading independent compiler vendors like GreenHills,
IAR and Keil are still using their own IDE.


-- Xiaofan


'[PIC] MPLAB problem'
2012\11\27@150915 by Steve Smith
flavicon
face
Guys....

I have a problem.... I have just started with 24F's in ASM30 and have run
into a stubborn issue. I have a simple piece of code that kicks a text
display into life.
The main code operates from the reset to the first call to a subroutine that
is in an included file. At this point the simulator goes back to the __reset
line in the main source code instead of switching to the included file. If I
have the code in line in the main file it simulates properly. It does this
with both MPLAB Sim and ICD3.
When ICD3 is the target the program runs on the device properly it also
displays as expected in the disassembly listing.

This was never a problem with and 8 bit device and I cant drive 'C' yet and
there is very sparse web recourses on ASM30 at all...

Thanks in advance

Steve


Main code segment


       .equ        __p24FJ256GB210.inc,        1
;        .include        "p24FJ256GB210.inc"
; INCLUDE FILES
       .global                __reset                                ; reset vector
       .global                __T2Interrupt                ; Timer ISR entry

       .global                delay

       .section __CONFIG_REG.sec, code
       .global __CONFIG_REG
       __CONFIG_REG: .pword POSCMOD_NONE & IOL1WAY_ON & OSCIOFNC_OFF &
FCKSM_CSECMD & FNOSC_FRCPLL & PLL96MHZ_ON & PLLDIV_DIV2 & IESO_ON

.DATA           ; Switch to DATA RAM segment:
       Flag_0:  .space  2       ; Reserve two bytes (one 16-bit word) in a
DATA RAM space for FLAGS bits
; Bit assignments in Flag_0:
       Tick   = 0             ; Bit 0 in Flag_0 is named Tick

..extern                Start_TXT
..extern                TXT_Cmd
..extern                TXT_Dta


; Start of executable code:

__reset:
       
       bra                Init

..include        "interrupt.s"                ; int handlers
       
       Init:

       mov     #__SP_init,W15                ; Initialise stack pointer and stack
limit register,
       mov     #__SPLIM_init,W0        ; __SP_init and __SPLIM_init values
are defined at compile/link time.
       mov     W0,SPLIM                        ;
       nop        
                                               
;        bset        T2CON,#TCS                        ; int/2 and on and /8
       bset        T2CON,#TCKPS0
       bset        T2CON,#TON
       bset        IPC0,#T2IP0                        ; timer 1 lowest priority
       bset        IEC0,#T2IE                        ; enable int        





       call                Start_TXT                ; THIS IS THE CALL THAT GOES
WRONG
       nop
       mov.b                #'F',W0
       call                TXT_Dta                ;        .....and then
..include        "TextDisplay.inc"                ; this is currently at the
bottom of code but it fails in the same way where ever it gets put !!!


TextDisplay.inc


..global                Start_TXT
..global                TXT_Cmd
..global                TXT_Dta
..extern                delay
;-------------LCD Port setup with standard text
module-----------------------
Start_TXT:
       mov                #0b1111101111111011,W0
       mov                W0,TRISD                        ; RS,E outputs
       nop
       bclr                PORTD,#0x02                        ; E low
       clr                PORTE

       mov                #0xFF00,W0                        ; E0-7        mov                W0,TRISE                        ; make outputs
       mov.b                #0x38,W0                        ; 8 bit
       call                TXT_Cmd

There is more here

2012\11\27@191119 by Joe Mickley

picon face
Saw something like this in a dsPIC30 running MPLAB and SIM.  The MPLAB environment doesn't want to switch to the include file for debugging. I simply wrote it off as a limit of MPLAB SIM and started pasting in the contents of the include and not ever using includes for
anything but register definitions.

You might want to go thru Microchip tech support to see if they have any suggestions. (NOT FORUMS, just the Tech support).  There
may be some setup stuff in MPLAB that fixes that.  ASM30 has some odd stuff (compared to the 16F/18F environment) and that may
be in the list of "odd"

MPLAB doesn't handle exceptions very well and there may be one generated when the program tries to step into the include.  I had
a math error and it took me forever to get the math error interrupt trap to catch it.  MPLAB would simply go back to __reset.  It
turns out that the default handler for any rupt not explicitly decalred is __reset (Dug that out of the linker script) at least for the dsPIC30

{Original Message removed}

2012\11\27@192018 by Tamas Rudnai

face picon face
You should analyse the disassembly code to tell what is going on --
however, i think you should use individual modules and linker scripts
instead of .include-ing separated ASM files.

Tamas



On 27 November 2012 12:09, Steve Smith <@spam@xygaxSTOPspamspam@spam@blueyonder.co.uk> wrote:

{Quote hidden}

>

2012\11\28@005032 by Perry Curling-Hope

picon face
Something simple I've found which may be related (16F stuff)

MPLAB does not like branching to assembler directives of any kind.

For instance, a call to  banksel  0  is a no no, whilst a call to bcf
STATUS,  RP0 (presumably the same thing) works just fine?


On Wed, Nov 28, 2012 at 2:20 AM, Tamas Rudnai <tamas.rudnaispamBeGonespamspamBeGonegmail.com>wrote:

{Quote hidden}

> > --

2012\11\28@011454 by Tamas Rudnai

face picon face
On 27 November 2012 21:50, Perry Curling-Hope <spam_OUTperry741STOPspamspamgmail.com> wrote:

> For instance, a call to  banksel  0  is a no no, whilst a call to bcf
>  STATUS,  RP0 (presumably the same thing) works just fine?
>

It is a bit off topic, but you should use banksel with the label, so for
example:

 banksel myRegister
 movwf   myRegister

Banksel is an internal macro of mpasm, and it will make sure the bank
selection will be always correct, regardless of where your register is
located. That means it makes your code more portable (with less work you
can compile your code to another PIC), and modifiable (later on you place
your register somewhere else, and your code will still be correct). Also it
makes possible to use modules and linker scripts where you do not even know
where your resources will be located on the final linked binary.

Tamas



{Quote hidden}

>

2012\11\28@022433 by Perry Curling-Hope

picon face
Hi Tamas,

With Steve's indulgence for  being off topic, I just tried out something
again which better shows what I am referring to,

Example 1

;Some stuff
call   Tamas
;
;
Tamas   banksel  myRegister
;
;rest of routine



Example 2

;Some stuff
;call   Tamas
;
;
Tamas    nop
              banksel  myRegister
;
;rest of routine


Example 1 does not compile, and reports that 'Tamas' is both an illegal and
previously undefined label

Example 2 compiles fine and runs as expected.

It is no longer a problem, I just avoid calling directly to some internal
macros






On Wed, Nov 28, 2012 at 8:14 AM, Tamas Rudnai <KILLspamtamas.rudnaispamspamspam_OUTgmail.com>wrote:

{Quote hidden}

> >

2012\11\28@041608 by Isaac Marino Bavaresco

flavicon
face
The problem is not branching to a assembler directive, but the presence
of the label *AND* the directive on the same line.
Just put an <enter> after the label and put the directive alone on the
next line. There is no need for the NOP at all:

Tamas:
                       banksel myRegister


Note: Use colon after the labels, it becomes more readable.


Best regards,

Isaac



Em 28/11/2012 05:24, Perry Curling-Hope escreveu:
{Quote hidden}

>

2012\11\28@042633 by alan.b.pearce

face picon face
> It is a bit off topic, but you should use banksel with the label, so for
> example:
>
>   banksel myRegister
>   movwf   myRegister
>
> Banksel is an internal macro of mpasm, and it will make sure the bank selection will
> be always correct, regardless of where your register is located

There are no banks in PIC24/30/33 chips, so this macro probably isn't supported.

Also ASM30 is so different to the ASM for base and midrange chips that you would never port it directly anyway.
-- Scanned by iCritical.

2012\11\28@052441 by Perry Curling-Hope

picon face
part 1 1486 bytes content-type:text/plain; charset="iso-8859-1" (decoded quoted-printable)

Isaac,

Always wondered about this...thanks[?]

I've had instances where source with branches to directives has compiled
OK, but has produced unexpected runtime results.
Merely moving the directives somewhere else without actually changing their
envisaged result has fixed the problem.

Also, I've had instances where compiled source has executed exactly as
expected under MPLAB SIM, but not on the live running target.
This has occurred with logic (once using SUBWF and branching depending on
the  Z or C bits) not timing critical operations such as  Dallas 'OneWire
Bus' communications  and suchlike.

MPLAB rocks, but it seems to have a few odd quirks of it's own....nothing
that cannot be overcome with some creative diddling about.

On Wed, Nov 28, 2012 at 1:23 AM, <.....alan.b.pearcespamspam.....stfc.ac.uk> wrote:

{Quote hidden}

> -

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