A header wizard

[Ioannis]

4. ADC setup
5. Comparator setup
6. UASRT setup
7. I2C setup
8. SPI setup

But then think howmany flavors of controllers exist and how many combinations can be setup...

We need a wizard (of programming) to make the Header Wizard!

Ioannis

[cncmachineguy]

4. ADC setup
5. Comparator setup
6. UASRT setup
7. I2C setup
8. SPI setup

EXACTLY!!!

But then think howmany flavors of controllers exist and how many combinations can be setup...

Thats what I am thinking about

We need a wizard (of programming) to make the Header Wizard!

Ioannis

Seems to be a plenty of them around here

I think the power will be in the dat file. The "wizard" will load the dat for the selected device, and from there will know what options are available. In that way the wiz can determine what to display. Maybe a different page for each option.

maybe in rev 2 it can do some simple conflict checking to determine if trying to double assign functions.

I am not too familiar with the include files provided with mplab, but maybe these will work for the dat files?

[mackrackit]

I have 17 different flavors of PICs in inventory, several share the same data sheet and I only use maybe six of the flavors regularly.

For me a project like this would not be worth the time. If I were using a different chip every day then maybe it would be.

How many different chips do you plan on using?

[cncmachineguy]

well I really only have 4 different chips. The benefit for me is that I don't have to pour over the data sheet to find all the different setup options and make sure they are turned on or off. And I really don't do stuff with them often enough to retain a good working knowledge of them.

I guess it would be more useful for the programmer who doesn't work with it all the time.

Thank you for the input.

[mackrackit]

Well that is why forums like this are handy. There is almost always someone with an answer.

A very usefull tool that answers some of the questions is mister e PicMultiCalc.
It has a baud rate calculator, time calculator and some other stuff.

Then the config options can be found for each chip in the Pxxx.inc file in the MPASM directory.

But again. It is easier for us to answer questions than it is to make a large data base.

Hmmm. Might be good extra credit for a student...
Or a community supported data base.
Darn it. Now you got me thinking about how something like this could be put together.

[cncmachineguy]

Community supported database, that's the words I was looking for in my first post.

I posted this here in the "wish list" section, assuming the GUI part could be done by the pbp developers, so it would be an integrated part of mcs. Then "we" the community would build the database based on our needs.

I suppose an alternate solution would be, either a: if mcs supports plugins, we could develop it. Or b: just a stand alone app. I don't like that approace as much, cuz it won't feel intgreted.

[mackrackit]

The forum is a canned system from V Bullitin so we can not do anything tied directly to it.

But Lester has made free websites available to forum users so maybe we could play with something there.

I will do some poking around. Could be fun.