VirtualPins

Hi!

I have and enhancement proposal to do small changes in the wiring_digital file and pins_arduino pin mapping, fully preserving compatibility, virtualizing the pins concept and do media (SPI,I2C, etc..) abstraction.
With minimal impact on existing function performance. The existing checks can work on an extended pin map and only adding an if, comparing pin number with a constant to existing functions (digital read/write).

In case of mapping to a virtual pin then the "content" is sent over an SPI or I2C (according to the map).

with this changes, libraries like LiquidCristal wouldn't have to be rewritten to control the same LCD's wired over SPI or I2C.

There are a LOT of advantages beside the mentioned one, but just for that I thinks it worth the effort considering the minimal impact it has.

I've done the implementation and some tests, available here for testing/appreciation:

https://github.com/neu-rah/VirtualPins

but I wish to put it here for discussion first and to get some advice on how should I proceed.

1. do a pull request with the changes to the arduino environment.
2. implement an alternative core and board that use virtual pins by duplicating some of the existing boards and pointing them to the alternative core.

waiting for feedback.

thanks.

_P.S. this was once done (in bad timing, to and older IDE) but now I'm available again and ported it to 1.8.3_

Inizia esaminando il file wiring_digital e la mappatura dei pin pins_arduino, quindi confronta il comportamento proposto con l’implementazione e i test nel repository VirtualPins collegato. La proposta è completa quando le API dei pin esistenti rimangono compatibili, le mappature virtuali possono trasportare contenuti tramite SPI o I2C e viene dimostrato che l’impatto sulle prestazioni è minimo.

Scritto dal modello di indicizzazione a partire dal testo della issue.