RFC: Moving forward with the WiPy/CC3200 port
Posted: Thu Nov 03, 2016 12:07 am
Hello all WiPy/CC3200 users.
The WiPy 1.0 is no longer in production, but there are still many of these boards out there, and there is also the generic CC3200 LAUNCHXL board and possibly other boards created around the CC3200 chip. So I would like to see the CC3200 MCU supported for a little bit longer.
To continue to maintain the CC3200 port efficiently, it must track any changes that are made to the hardware API, the machine module in particular. Because the CC3200 does not have much memory or flash it's not feasible to make backwards compatible changes, so, moving forward, this port will start to introduce backwards-incompatible changes.
In order to help out those users who still want to use their older scripts with the older API the plan is the following: the release v1.8.6 will be the final release of the WiPy/CC3200 code that supports the original hardware API. After this release there will be backwards-incompatible changes to keep the port up-to-date with the other ports. The docs will evolve with the changes so users can still refer to the docs to see how to use the WiPy (and v1.8.6 docs will describe the older API). Since the API will match other ports it will be much easier to write scripts that are compatible, for example, with WiPy and ESP8266.
Please chime in here if you have any concerns with this plan, or ideas for how to manage this better.
Thanks!
The WiPy 1.0 is no longer in production, but there are still many of these boards out there, and there is also the generic CC3200 LAUNCHXL board and possibly other boards created around the CC3200 chip. So I would like to see the CC3200 MCU supported for a little bit longer.
To continue to maintain the CC3200 port efficiently, it must track any changes that are made to the hardware API, the machine module in particular. Because the CC3200 does not have much memory or flash it's not feasible to make backwards compatible changes, so, moving forward, this port will start to introduce backwards-incompatible changes.
In order to help out those users who still want to use their older scripts with the older API the plan is the following: the release v1.8.6 will be the final release of the WiPy/CC3200 code that supports the original hardware API. After this release there will be backwards-incompatible changes to keep the port up-to-date with the other ports. The docs will evolve with the changes so users can still refer to the docs to see how to use the WiPy (and v1.8.6 docs will describe the older API). Since the API will match other ports it will be much easier to write scripts that are compatible, for example, with WiPy and ESP8266.
Please chime in here if you have any concerns with this plan, or ideas for how to manage this better.
Thanks!