-
Notifications
You must be signed in to change notification settings - Fork 119
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Question about how to apply micro-ROS on FreeRTOS on teensy4.1 development board #1854
Comments
Just some background questions.
If you are a beginner to ROS2 and micro-ROS, you should use ubuntu instead of Windows. Although it is possible to run Jazzy on Windows, it is difficult for beginners. You can use docker to run ROS2. But you still need the knowledge of ubuntu linux. If you can install a ubuntu 24.04 pc or VM, you should be able to learn ROS2 and micro-ros better than on windows. If you only have windows, you should learn vscode+ros2+docker and platformio. If you are new to micro-ros, you should start with esp32 which is cheaper and easier than teensy4.1. The esp32 core runs freertos. You may follow the wiki, https://github.com/hippo5329/micro_ros_arduino_examples_platformio/wiki |
Thank you for your interest in my question.
In the past, I have experience using Teensy 4.1 as bare-metal using the micro-ros-arduino library and example code from Github. |
There is another rtos, chibios on arduino , https://github.com/greiman/ChRt And freertos, I am not sure if it works. |
It can build blink_task and publisher with micro-ros and freertos. But I didn't test on hardware. |
Issue template
Steps to reproduce the issue
I am trying to apply micro-ROS on FreeRTOS on the teensy4.1 development board.
So, can I use the static library micro_ros_arduino for the micro-ROS library like I used in the bare metal environment on the teensy4.1 development board?
Expected behavior
Actual behavior
Additional information
The operating system of the Arduino IDE is Windows 10.
The operating system of the MCUXpresso IDE is Windows 10.
The text was updated successfully, but these errors were encountered: