micro-ROS / micro-ROS/micro_ros_setup

Error cloning repository during create_firmware_ws.sh

Open
#692 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Shell
Stars
509
Forks
183
Avg merge
22h 26m
Merged PRs (30d)
7

Description

  • Hardware description: esp32 or olimex-stm32-e407
  • RTOS: FreeRTOS
  • Installation type: -
  • Version or commit hash: humble
  • Im working on Ubuntu 22.04 with ROS2 Humble.
Steps to reproduce the issue

I followed the "First micro-ROS Application on FreeRTOS" tutorial until $ ros2 run micro_ros_setup create_firmware_ws.sh freertos olimex-stm32-e407

where i face this error:
$ ros2 run micro_ros_setup create_firmware_ws.sh freertos olimex-stm32-e407
Creating firmware for freertos platform olimex-stm32-e407
/usr/bin/vcs:6: DeprecationWarning: pkg_resources is deprecated as an API. See https://setuptools.pypa.io/en/latest/pkg_resources.html
from pkg_resources import load_entry_point
.......
=== ./ament/ament_cmake (git) ===
Cloning in '.'...
=== ./ament/ament_index (git) ===
Cloning in '.'...
=== ./ament/ament_lint (git) ===
Cloning in '.'...
=== ./ament/ament_package (git) ===
Cloning in '.'...
=== ./ament/googletest (git) ===
Cloning in '.'...
=== ./ament/uncrustify_vendor (git) ===
Cloning in '.'...
=== ./ros2/ament_cmake_ros (git) ===
Cloning in '.'...
/usr/bin/vcs:6: DeprecationWarning: pkg_resources is deprecated as an API. See https://setuptools.pypa.io/en/latest/pkg_resources.html
from pkg_resources import load_entry_point
List of repositories is empty
#All required rosdeps installed successfully
/usr/bin/vcs:6: DeprecationWarning: pkg_resources is deprecated as an API. See https://setuptools.pypa.io/en/latest/pkg_resources.html
from pkg_resources import load_entry_point
..............
=== ./ros2/common_interfaces (git) ===
Cloning in '.'...
=== ./ros2/example_interfaces (git) ===
Cloning in '.'...
=== ./ros2/libyaml_vendor (git) ===
Cloning in '.'...
=== ./ros2/rcl (git) ===
Cloning in '.'...
=== ./ros2/rcl_interfaces (git) ===
Cloning in '.'...
=== ./ros2/rcl_logging (git) ===
Cloning in '.'...
=== ./ros2/rcpputils (git) ===
Cloning in '.'...
=== ./ros2/rmw (git) ===
Cloning in '.'...
=== ./ros2/rmw_implementation (git) ===
Cloning in '.'...
=== ./ros2/rosidl (git) ===
Cloning in '.'...
=== ./ros2/rosidl_dds (git) ===
Cloning in '.'...
=== ./ros2/rosidl_defaults (git) ===
Cloning in '.'...
=== ./ros2/test_interface_files (git) ===
Cloning in '.'...
=== ./ros2/unique_identifier_msgs (git) ===
Cloning in '.'...
/usr/bin/vcs:6: DeprecationWarning: pkg_resources is deprecated as an API. See https://setuptools.pypa.io/en/latest/pkg_resources.html
from pkg_resources import load_entry_point
.........E.
=== ./eProsima/Micro-CDR (git) ===
Cloning in '.'...
=== ./eProsima/Micro-XRCE-DDS-Client (git) ===
Cloning in '.'...
=== ./uros/micro_ros_msgs (git) ===
Cloning in '.'...
=== ./uros/micro_ros_utilities (git) ===
Cloning in '.'...
=== ./uros/rcl (git) ===
Cloning in '.'...
=== ./uros/rclc (git) ===
Cloning in '.'...
=== ./uros/rcutils (git) ===
Cloning in '.'...
=== ./uros/rmw_microxrcedds (git) ===
Cloning in '.'...
=== ./uros/rosidl_typesupport (git) ===
Cloning in '.'...
=== ./uros/rosidl_typesupport_microxrcedds (git) ===
Cloning in '.'...
=== ./uros/tracetools (git) ===
Could not determine ref type of version: remote:
remote: ========================================================================
remote:
remote: ERROR: The namespace you were looking for could not be found.

remote:
remote: ========================================================================
remote:
fatal: Could not read from remote repository.

Please make sure you have the correct access permissions
and that the repository exists.
[ros2run]: Process exited with failure 1
[ros2run]: Process exited with failure 1

Additional information

Same error doing: $ ros2 run micro_ros_setup create_firmware_ws.sh freertos esp32

Seems could not find tracetools package, dont know why...

Thanks in advance!

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with create_firmware_ws.sh and reproduce the command for both olimex-stm32-e407 and esp32. Inspect how the firmware workspace selects the uros/tracetools repository and its version, then verify that the configured remote exists and cloning completes without the shown ref or permission error.

Written by the indexing model from the issue text.

Assessment

Tech stack
git, shell
Domain
build-system, embedded-iot
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.