micro-ROS / micro-ROS/micro_ros_setup
I have been trying to implement the micro-ros in the i.MX93 (it has an m33 core mcu).
- Lenguaje dominante
- Shell
- Estrellas
- 509
- Forks
- 183
- Merge medio
- 22 h 26 min
- PR fusionados (30 d)
- 7
Descripción
I have been trying to implement the micro-ros in the i.MX93 (it has an m33 core mcu).
What's already done:
1. Created a static library and linked to the mcuxpresso ide.
2. Implemented a custom transport function.
3. The setup has connected with the micro-ros agent, node and topic published.
But...
The rclc_executor_spin_some() is not working, i have tried multiple ways to invoke this but still can't figure out. My assumption reagarding the issue is that the time i am providing to the clock_gettime().
I have debugged the time functions of the mcu and getting the ticks values properly. But still the executor() is not working.
When the rcl_publish() is manually invoked the data is publishing to the topic.
How can i debug this issue. Will there be any issue with the static library that i have made first? if that's the case will this much steps work with the current setup?
How should i feed the time to the clock_gettime() ? if this ticks converted to sec and nsec not enough?
I have attached the files with this post, ROS Experts please help me.
Thank you.
[uros_transport.c](https://github.com/user-attachments/files/24434909/uros_transport.c)
[hello_world.c](https://github.com/user-attachments/files/24434911/hello_world.c)
[timer.c](https://github.com/user-attachments/files/24434912/timer.c)
_Originally posted by @Anandhu-Sudha in https://github.com/micro-ROS/micro_ros_setup/discussions/802_
Guía de contribución
Línea de trabajo
Comience con los archivos adjuntos uros_transport.c, hello_world.c y timer.c, siguiendo la llamada a rclc_executor_spin_some() y los valores de clock_gettime() en el núcleo M33 del i.MX93. Compare la ruta del executor con la ruta de rcl_publish() que funciona manualmente. Se considera completado cuando se haya identificado la causa de que el executor no funcione y se haya documentado si el origen del reloj o la configuración de la biblioteca estática es responsable.
Escrito por el modelo de indexación a partir del texto del issue.
Evaluación
- Stack tecnológico
- c
- Área
- embedded-iot, robotics
- Tipo de issue
- Error
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Estado de actividad
- Estancado
- Claridad
- Necesita aclaración
- Aptitud para principiantes
- 20/100