Patrick Roncagliolo

@mjcarroll any update on this?

I started to compile against an old RTEMS toolchain of mine, since it was ready on my PC. rtems_toolchain.cmake ``` set(RTEMS_ROOT_PATH "/mnt/sdb/rtems") set(RTEMS_TOOLS_INSTALL_DIR "${RTEMS_ROOT_PATH}/5") set(RTEMS_TOOLS_BSP_LIB_DIR "${RTEMS_ROOT_PATH}/5/sparc-rtems5/lib") set(RTEMS_KERNEL_INSTALL_DIR "${RTEMS_ROOT_PATH}/5/sparc-rtems5/erc32") set(RTEMS_KERNEL_BSP_LIB_DIR "${RTEMS_ROOT_PATH}/5/sparc-rtems5/erc32/lib")...

A lot of warnings though. This one occurs at every package. ``` CMake Warning at /mnt/sdb/microros_ws/firmware/mcu_ws/install/share/rcutils/cmake/ament_cmake_export_libraries-extras.cmake:116 (message): Package 'rcutils' exports library 'dl' which couldn't be found ``` This annoying warning...

Is there a list of all the definitions in colcon.meta?

I discovered that no matter if in your custom toolchain you add a line such: ``` set(CMAKE_DL_LIBS "-lrtemscpu") # contains dlopen() family of symbols in RTEMS ``` the `rcutils` CMake...

Some updates: rtems-toolchain.cmake ``` set(RTEMS_ROOT_PATH "/mnt/sdb/rtems") set(RTEMS_TOOLS_INSTALL_DIR "${RTEMS_ROOT_PATH}/5") set(RTEMS_TOOLS_BSP_LIB_DIR "${RTEMS_ROOT_PATH}/5/arm-rtems5/lib") set(RTEMS_KERNEL_INSTALL_DIR "${RTEMS_ROOT_PATH}/5/arm-rtems5/beagleboneblack") set(RTEMS_KERNEL_BSP_LIB_DIR "${RTEMS_ROOT_PATH}/5/arm-rtems5/beagleboneblack/lib") set(ENV{PATH} "${RTEMS_TOOLS_INSTALL_DIR}/bin:$ENV{PATH}") set(RTEMS_TOOLS_BSP_INCLUDE_DIR "${RTEMS_ROOT_PATH}/5/arm-rtems5/include") set(RTEMS_KERNEL_BSP_INCLUDE_DIR "${RTEMS_KERNEL_BSP_LIB_DIR}/include") set(RTEMS_COMPILE_OPTIONS "-B${RTEMS_KERNEL_BSP_LIB_DIR} -B${RTEMS_TOOLS_BSP_LIB_DIR} -specs bsp_specs -qrtems -mcpu=cortex-a8") set(CMAKE_SYSTEM_NAME Generic) set(CMAKE_SYSTEM_PROCESSOR...

I opended some PRs to fix the warnings. Next step is waiting to retrieve my Beaglebone Black (which now I don't have with me, but it will be again sometime...

TODOs (suggestions welcomed): - [ ] build a sample application with micro-ros targeting RTEMS BeagleBone Black - [ ] deploy the application - [ ] get RTEMS boot correctly -...

I believe the basic setup could be a RTEMS application with 1 task and 1 micro-ROS publisher. Yes, I need to check if with my pre-existing setup I can already...

In parallel with making myself a new RTEMS environment (with the goal to execute some default tests in the emulator before starting to add micro-ROS in the mix), I'm reading...