A header wizard

[mackrackit]

Here is another one to practice with
http://www.picbasic.co.uk/forum/showthread.php?t=10381
It has some problems the way it is written. Pointed out in the thread. I just never got around to fixing it.

It would be a good stand alone program, command line or GUI, to practice with.

[malc-c]

Here is another one to practice with
http://www.picbasic.co.uk/forum/showthread.php?t=10381
It has some problems the way it is written. Pointed out in the thread. I just never got around to fixing it.

It would be a good stand alone program, command line or GUI, to practice with.

Nice - just tested it with the latest version of my thermostat project -



Very useful app - thanks Dave

[ScaleRobotics]

The *.dev files come with MpLab IDE. I believe the only way to get Mpasm is to download the Mplab IDE. So, everyone that selects Mpasm should have one version or another of Mplab Ide, and the associated files. There are also some other usefull (depending on how complex you want to go) info. This area has pin # information: C:\Program Files\Microchip\MPLAB IDE\VDI\XML\PIC16 . Images could be "mapped" to show labels for pins, etc. Images are here: C:\Program Files\Microchip\MPLAB IDE\VDI\Images

I guess it is both good and bad to have it dependent on Microchip. If they end support, then your work needs to be re-worked. However, the updates being dependent on what mpasm has to work with seems like a good idea. You immediately see if the mplab ide version you have does not support your chip, does not require programmer intervention to add chips. But of course there are many ways to do it, all with advantages, and disadvantages.

Walter

[cncmachineguy]

Back when I played with VDI, I thought I had found a goldmine for pic setup. I was sad to discover they didn't support 16f818 or 16f676. I then figured out it just didn't support smaller chips. It seemed it was developed to help with larger more powerful stuff.

That said, its nice to know there is still support stuff shipping with mplab. I would be concerned how long that will continue. Like when the install won't fit on a CD anymore, what will they chop to squeeze in on.

As for general support of MPLAB, I can't imagine they would stop that. After all, thats what allows new customers to try their product out, and allows the seasoned vets to continue. Not to mention, all the third party folks who depend on it.

Now if the *.dev files are only required for VDI, then maybe they will cease at some point. But my vote is, for now, we take full advantage of what they offer.

[mackrackit]

I use this when I do ASM on Linux.
http://piklab.sourceforge.net/index.php
I do not see where it uses the *.dev files but it does use the *.inc files. Maybe MicroChip does not care? As long as we give credit where do.

I suppose when MicroChip quits supporting the files and/or does not like what we are doing it will be time to move on to another chip.

[mackrackit]

MicrChips EULA, Part of. What do you all think it really means?

(a) Subject to all of the terms of this Agreement, Company grants Licensee a personal, worldwide, non-exclusive, non-sublicensable, non-transferable limited license to use and modify the Software solely for use with Company products (“Company Products”).

Licensee may not modify, create derivatives or reverse engineer (by disassembly, decompilation, translation, or otherwise) Software and may not copy or reproduce all or any portion of Software, except to the extent that such activity is specifically allowed by this Agreement or expressly permitted by applicable law notwithstanding the foregoing limitations.

[cncmachineguy]

MicrChips EULA, Part of. What do you all think it really means?

Well I'm no lawyer to be sure. I am certain of one thing, it is vague enough to mean whatever their lawyers imagination needs it to mean.

Having said that, I take the first line to mean we are not allowed to use MPLAB to program any other uP's. The vagueness comes into play where the software or any data files may also be considered "company products". But we ARE using it to program THEIR products. AND we are not offering it for sale.

I don't believe we are doing any of the second statement unless we package copies of the inc's, dev's, ... with our wizard. So this brings me to the question of the web based app, can we have it look at the data on our local drive? That way we don't have to upload the files to the server, thus not violating the aggrement.

I agree with the post way back about the license, we need one, if for nothing else but to state the microchip files may not be copied.

Personally I am a wait and see kind of guy. As such, I don't believe we are infringing on the license. This may be one of those areas where they don't care, but if we push them to make a decision, they will decide we can't use them to avoid any further problems. We are after all, creating something to promote the sale of more PIC's. This wizard will in no way have a negitave impact on them or their product.

Now I suppose if someone wanted to, the wizards could be modified to work for other brands, but at that point the microchip files will be of no use to them.

Just my $.02.

[cncmachineguy]

I suppose when MicroChip quits supporting the files and/or does not like what we are doing it will be time to move on to another chip.

AMEN! I couldn't agree more!

[ScaleRobotics]

I use this when I do ASM on Linux.
http://piklab.sourceforge.net/index.php
I do not see where it uses the *.dev files but it does use the *.inc files. Maybe MicroChip does not care? As long as we give credit where do.

Hey Dave,
How do you get mpasm (or do you) on to linux? Are you using WINE?
I do not see the .inc files included here: http://packages.debian.org/lenny/i386/piklab/filelist Just wondering if you have the device files on your linux machine.

I did a little searching, and I could not find PBP setup instructions for Linux. (I hear a new Wiki calling your name......)

Anyway, I assume (in Microsoft environments) the .dev files are used in the SIM part of the IDE. But it looks like it is also used for some programmers, as it contains program voltages etc. It might be used for other features inside the IDE as well. I can't really see Microchip dropping the sim feature, so I think the Device files are pretty safe. The more info we can feed the wizard, the more we could make it do.

[prstein]

Hi All,

Added a version history in the zip file. Changes additions this time include:
-Added special handling for 16F676 and 16F630 PORTs and TRISs.
-Added a directory list box for use in selecting MPASM folder.
-Re-loads PIC combo box after changing MPASM folder in Settings window.
-Responds better to inaccurate folder settings.

cncmachineguy, couldn't do much about typing in the combo box this time around.

I could really use some direction on implementing the ADC setup. An example or two would be exceedingly helpful...

Best Regards,
Paul