Examples illustrating application development on the REMCU Lib. These examples are designed to get you up and running with REMCU Lib in no time.
| Target | Jupyter notebook ex. | Python scripts ex. | Qt app ex. | C/C++ app ex. | Raspberry Pi board examples |
|---|---|---|---|---|---|
| stm32f4_discovery | C++(cling) & Python: ADC, DAC, DMA, GPIO, PWM |
Accelerometer & CAN bus sniffer | |||
| STM32F767X | C++(cling): ADC, DAC, DMA, GPIO, PWM | ||||
| STM32F103RCT6 | C++(cling) & Python: ADC, GPIO, PWM | ADC, GPIO | ADC, DAC, DMA, GPIO, CAN bus | C/C++ apps & Python scripts: ADC, GPIO, CAN bus - the prepared Raspbian image is available |
|
| STM32F103C8T6 Blue Pill board |
C++(cling) & Python: ADC, GPIO | ADC, GPIO | ADC, CAN Bus | C/C++ apps & Python scripts: ADC, GPIO, CAN bus - the prepared Raspbian image will be available |
|
| stm8l_discovery | C++(cling): ADC, DAC, DMA, GPIO, LCD screen | ||||
| STM32F030-51 | C++(cling) & Python: ADC, GPIO | Python scripts: ADC, GPIO - the prepared Raspbian image is available |
|||
| stm32f3_discovery | soon | Compas & Gyroscope | |||
| KIT_XMC_2GO_XMC1100 | WIP | soon | uart | ||
| LPC1768(NXP) | soon | soon: CAN bus sniffer | adc, dac, gpio | ||
| FRDM-K64F MK64FN1M0VLL12 MCU (Freescale/NXP) |
soon | soon: Accelerometer | gpio, mma8451 accelerometer I2C | ||
| EFM32TG(Silabs) | WIP | soon: LCD printer | gpio, lcd | ||
| SAMD20(Microchip) | soon | ssd1306, adc, dac, gpio | |||
| NRF51422 | adc |
(click here to view)
stm32f4_discovery/accell_graph demo:
stm32f4_discovery/CAN_BUS demo:
stm32f4_discovery/jupyter-notebook Python notebook demo:
STM32F767X/jupyter-notebook ADC, DAC, PWM demo:
STM32F103C8T6-Blue-Pill/Raspberry + Blue Pill CAN bus demo:
The REMCU Lib is a cross-platform library designed for remote access to internal peripherals of various MCU and SoC as if these peripherals were a part of your computer. The library gives access a user space program to all peripherals of the remote chip through the same API as peripheral drivers from Software Development Kit (SDK) provided by semiconductor chip vendors or third parties for MCU firmware development. Thereby a developer doesn’t need to learn new tools but can just reuse his firmware code and examples of the SDK in his code designed for personal or embedded computers. Firmware and protocol communication development are not required, because the REMCU Lib translates itself the local API function call on computer to the call of the same function of peripheral driver on the remote chip.
Let's have a look at the video below and see what opportunities and applications it provides.
REMCU Lib Docs: https://remotemcu.com/docs
Full details of the examples can be found in README.md file of the corresponding folders.
If you discover a problem with any of the samples published here that isn't already reported in Issues, open a New issue.
If you have a feature idea - please open a feature request.
If you have new sample development on the REMCU Lib - please opening a pull request or "Suggestion of examples" request.
We will be pleased to answer all your questions about the REMCU Lib project through the options/channels below:
StackOverflow. Tag your question with #remculib tag. We watch full list of questions and will answer ASAP. Make experience that you've got available for other users!
Contact us form
@Email
Twitter
Thanks in advance!