Post by thread:MPLAB bugs

I would like to suggest that my respected fellow PIClisters post the bugs (real MPLAB bugs, not undocumented features in your own PIC software) and features that irritate them about MPLAB. I will compile a 'Best of' and mail it to Microchip's people. After some degree of bitching, moaning and groaning, it seems that they are looking at some of the stuff that drove me nuts (too late for me now - I'm too far around the bend!). I understand that a new version of MPLAB (3.13.00) will be released soon. (How soon? - I don't know). Perhaps we can worm in a couple of extras before it hits our desktops (like a 'buffer watch', or changeable icons on the toolbar). Come on - it will be far more interesting to discuss possible features for MPLAB than the usual PDF-versus-Excell, My-operating-system-is-better- than-your-Operating-system, Hey-where-is-the-PIClist, Where-can-I-get-a- programmer-for-under-50-cents. -- 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 | spam_OUTtjaartTakeThisOuTwasp.co.za | |______________________________________________________________|

>I would like to suggest that my respected fellow PIClisters post >the bugs (real MPLAB bugs, not undocumented features in your own >PIC software) and features that irritate them about MPLAB. I will >compile a 'Best of' and mail it to Microchip's people. Great suggestion Tjaart. I have a few things I would like to see: How about getting PICStart Plus to pick up and setup defaults based on: 1. The Device. 2. The Options in the __CONFIG Statement? As well, I'm still getting the message telling me to rebuild my application to the latest level when I enable PSP (I'm running 3.10, so this shouldn't be an issue). Can somebody tell me how to get rid of this message? In terms of features: 1. How about a graphical display of the I/O (with the Stimulus File I/O)? Included with this would be: 1.1 Displaying the graphical display either by Step Count or absolute time. 1.2 Allowing Break Points to be put in at various points of the Waveform. 1.3 Being able to Zoom In and Out on the Time Base (down to individual clocks so you can see when I/O is happening). 1.4 Being able to edit the Stimulus file from this Graphical Display. 1.4.1 What would really turn me on is the ability to cut and paste Sections of the Stimulus (and even being able to take from other files). 1.5 This should probably work with the PICMaster (to see what actually happened and how the PIC responded. I would be willing to pay for this feature. This would cut down my stimulus development and code debug by a huge amount. 2. Being able to create Stimulus points based on Time points, rather than Steps. (I'm tired of converting time to steps, by taking the reciprocal of the frequency, dividing by four - let the PC do it). 3. Speed up the Stimulus Execution. 4. Get MPLAB (and in particular PSP) to run more reliably under Windows 95. 5. Give the user the option of seeing how a Macro executes in the Simulator (as it does now) or just treating the Macro as a black box. I find that I loose the thread of the program if I have a large Macro and MPLAB bleeps off to the Macro definition. The whole point of using Macros is to simplify code by using pre-defined operations. myke Today, the commercial sector is advancing computer and communication technology at a breakneck pace. In 1992, optical fiber was being installed within the continental U.S. at rates approaching the speed of sound (if computed as total miles of fiber divided by the number of seconds in the year). Aviation Week and Space Technology, October 28, 1996

Hello ! I am a newbie on the PICLIST. I am trying to check a programa I have written for 16C57 using MPLAB rel 3.12 - downloaded from Microchip FTP site - under WIN95. I am experiencing GPF fault on trying to load a STI file. But I have had success in some of the fist attemps, so I wonder if I have changed something in the program setup wich caused the problem. BTW, is there any trick to SAVE in the project also the ASYNC stimulus assignment ? And WHY microchip Made not-resizeable the WATCH clock and it is impossible put it on the foreground? With a 800X600 screen it is really crowded... Thanks for the replies ( if any .. ) :-)) And best wishes for a Merry Xmas Bruno ====================== Bruno Rodeghiero I3 RGH ( how many are the Hams on the list ?) maito:.....brurodegKILLspam@spam@mbox.vol.it