However, D4 is also the TX pin for Serial 2 on the Xenon.
The link above does mention " …[1] These pins are connected via jumper pads on the bottom. You can cut these jumper traces and rewire them to a different pin on the Mesh device if the need arises.".
Let us say I connect nINTERRUPT to D6 instead. Will this work? What changes are needed in the code?
While you can physically move the pin by cutting the jumper pads and adding jumper wires, there is no way to change which pins Device OS uses as the interrupt pin. So it won’t work.
At some time in the future the Ethernet pins might be reconfigurable in Device OS, but they are not reconfigurable at this time.
That should work. The SC16IS740/750/760 are basically the same chip but with more capabilities in the higher numbers. I’m pretty sure my library should work with the SC16IS750. And that’s a really good price for the breakout.
None of the Ethernet FeatherWing pins can be reconfigured because Device OS expects them to be on the pins they’re currently on. The ability to reconfigure the CS, reset, and INT pins will probably be added in a future release, but I don’t have a schedule for when that will happen.
I see. That completely prevents the use of Serial2 then on the Xenon. I was hoping that D5 can be reconfigured because it would have allowed the use of Serial2 on serial sensors that are only transmitting and do not need their RX connected …
If Serial 2 and the EthernetWing are not used at the same time, will it work? For example, turn the Ethernet off then on when needed …