Expansion Board pin numbers vs LoPy pin numbers

Reply to Expansion Board pin numbers vs LoPy pin numbers on Fri, 11 Nov 2016 16:56:35 GMT

Jakko — Fri, 11 Nov 2016 16:56:35 GMT

Let me ask a naïve question, for which there is probably a very straightforward answer:

Why is the pin numbering on the expansion board (beginning with 'G') completely different from the pin numbering on the LoPy (beginning with 'P')? The expansion board numbers also are not mentioned on the newly published Pin-Out overview.
What am I missing?

Thanks,

Jakko

Reply to Expansion Board pin numbers vs LoPy pin numbers on Fri, 11 Nov 2016 17:08:16 GMT

Xykon — Fri, 11 Nov 2016 17:08:16 GMT

I'm assuming it was done to provide backwards compatibility for the WiPy1 expansion board.

Reply to Expansion Board pin numbers vs LoPy pin numbers on Fri, 11 Nov 2016 17:30:13 GMT

Jakko — Fri, 11 Nov 2016 17:30:13 GMT

Thanks Xykon, that makes sense.

Is it then correct that both Pin('Px', ......) and Pin('Gx', .......) with x being the pin number, will be recognized by micropython?

Reply to Expansion Board pin numbers vs LoPy pin numbers on Fri, 11 Nov 2016 17:34:32 GMT

Xykon — Fri, 11 Nov 2016 17:34:32 GMT

@Jakko Yes

from machine import Pin
p_out=Pin('G23',mode=Pin.OUT)
p_out.id()
'P2'

Reply to Expansion Board pin numbers vs LoPy pin numbers on Sun, 13 Nov 2016 16:12:20 GMT

LoneTech — Sun, 13 Nov 2016 16:12:20 GMT

Yes, the G numbers are to match the WiPy 1 (version 2 uses ESP32 like the LoPy), and the WiPy 1 in turn got their order from the GPIO pin order on the CC3200 processor it uses. LoPy's support for the G numbering is fairly explicitly to keep the expansion board the same, as the P names are all under machine.Pin.module and the G names are under machine.Pin.exp_board. By the way, those locations hold preexisting instances of all the pins, so can be used to access the few that currently crash (like G3/P16). That's one bug I plan to chase down after source release.