Tom Collins

@robert-hh, in our case, MicroPython runs as a separate task, and the end-user doesn't have the ability to compile their own firmware. Use of .mpy files allows for source code...

Yes, it is possible to write and add those files for the STM32 platform. Take a look at https://github.com/digidotcom/xbee_ansic_library/blob/master/ports/README.md for instructions on how you can create them. If you're uncertain...

On any GitHub project, if you go to "Insights" and the "Network", you'll see who's making commits on their forks. Here's the [network](https://github.com/digidotcom/xbee_ansic_library/network) for this project.

I'm closing this out as we haven't received a pull request to integrate anyone's STM32 port.

The [gps_uart](../tree/master/samples/gps_uart) sample demonstrates communication with another device via the secondary serial port, which leaves the primary port for MicroPython debugging, or usage of API frames with a host processor.

As long as you don't call `xbee_dev_tick()` for the same device from two separate threads, or try to send to the same device from two threads, I think you might...

Did you write any test programs to validate this code, with coverage for multiple cases? If you've been using it extensively in your software and updated TLS code, it's probably...

I'm finally getting around to reviewing your PRs and merging them. Do you have any stats on the improvement you saw with the new code? Or was the change primarily...

And it needs to mention that the `mpy_cross` version matters. See this forum posting for details: https://www.digi.com/support/forum/70255/how-to-cross-compile-micropython-code-for-xbee3

Thanks for these improvements. I'm focused on some other issues at the moment, but hope to have time to review the code changes, do some testing, and then integrate them...