Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revision | |
en:iot-open:scriptingprogramming:remotedevelopment [2023/11/17 16:57] – pczekalski | en:iot-open:scriptingprogramming:remotedevelopment [2023/11/23 10:25] (current) – pczekalski |
---|
====== Remote development in Python ====== | ====== Remote development in Python ====== |
| {{:en:iot-open:czapka_b.png?50| General audience classification icon }}{{:en:iot-open:czapka_m.png?50| General audience classification icon }}{{:en:iot-open:czapka_e.png?50| General audience classification icon }}\\ |
As developers use PCs to author software, but it is executed in the microcontroller, using a terminal over a serial connection or secure shell (SSH) may not be convenient for larger projects. For this reason, many IDEs can perform remote development with code authored in the IDE on the PC but executed on the MCU. It requires a stable connection between the development host and the microcontroller and sometimes installation of the remote development host. One of the most flexible IDEs, able to act in virtually any scenario of remote development, is Visual Studio Code((https://code.visualstudio.com/docs/remote/remote-overview)). | As developers use PCs to author software, but it is executed in the microcontroller, using a terminal over a serial connection or secure shell (SSH) may not be convenient for larger projects. For this reason, many IDEs can perform remote development with code authored in the IDE on the PC but executed on the MCU. It requires a stable connection between the development host and the microcontroller and sometimes installation of the remote development host. One of the most flexible IDEs, able to act in virtually any scenario of remote development, is Visual Studio Code((https://code.visualstudio.com/docs/remote/remote-overview)). |
| |