Arduino type libraries

[picster]

I find that documenting my variables and keeping track of them (with multiple modular includes) is one of the most challenging things. I usually create a modular include (sub) if it performs a task/function that I think I'll use again - and just comment it to death - but the idea of having a variable naming convention with a prefix indicating the INCLUDE NAME is a really good idea.

[Heckler]

Though I have never worked with an arduino board...

It occurs to me that one must realize (and you probably do) that the Arduino is based on a specific set of pinout functions. It is just a microcontroller on a very defined PCB with pin functions that are limited to what the PCB is set up for. ie. certain pins set for digital and certain other pins set for analog, etc.

So in order to use someone else's library you must use the same pins that they did (unless the library is written to allow you to choose different pins)

Whereas the group of contributors here are using a VERY WIDE RANGE of PIC microcontrollers. Not just one or two that would fit an arduino like model.

So I believe your best bet would be to use the search function to locate examples of code that will allow you to do what you want to do with your chosen PIC.

It seems to me that the only way to be able to use libraries or in PBP it would be "Include" files we would have to agree on a set of standard pin assignments and limit ourselves to just a few similar PIC's.

While I think your wish is valid and would be nice it is a bit unrealistic for such a broad range of microcontrollers that PBP works with.

That is obviously just my opinion and I would love to be wrong
dwight

[Dave]

I agree Dwight.....

[picster]

I try to use aliases typically, to designate pins. Provided that proposed "Code Libraries" use aliases as a rule of thumb (instead of specific pins), this would alleviate much of the "broad range" issue, would it not? Each user could then have their own specific alias definitions for assigning pins/ports. Data direction registers, Port and pin assignments, etc. would all be up to the user to define, so that the aliases within the "Library" are adapted to his/her PIC of choice. If requirements are documented within each Library, then users can ensure they allocate resources accordingly.

I realize that it's far from perfect, but in the interest of evolution toward standardized code snippets, doesn't it seem like something worth starting?

[Art]

Microchip’s libraries for any of their chips are written for development boards, so you can choose to agree on the hardware,
or take responsibility for hardware changes yourself. Some of the libraries go the DT way and are highly configurable.
Embedded platforms have always had them, at least since the early 90’s,
but people doing stuff with the controllers probably aren’t interested in the stock boards.

[pedja089]

There is arduino like board with microchip PIC
http://www.myamicus.co.uk