does not create subscriber/publisher

keeps repeating same thing
hreya@shreya:~/microros_ws$ ros2 run micro_ros_agent micro_ros_agent serial --dev /dev/ttyACM0
[1723271821.205933] info | TermiosAgentLinux.cpp | init | running... | fd: 3
[1723271821.206102] info | Root.cpp | set_verbose_level | logger setup | verbose_level: 4
[1723271821.210384] info | Root.cpp | create_client | create | client_key: 0x45402441, session_id: 0x81
[1723271821.210409] info | SessionManager.hpp | establish_session | session established | client_key: 0x45402441, address: 0
[1723271821.210453] info | SessionManager.hpp | establish_session | session re-established | client_key: 0x45402441, address: 0
[1723271821.221491] info | SessionManager.hpp | establish_session | session re-established | client_key: 0x45402441, address: 0
[1723271821.221521] info | SessionManager.hpp | establish_session | session re-established | client_key: 0x45402441, address: 0
[1723271821.221528] info | SessionManager.hpp | establish_session | session re-established | client_key: 0x45402441, address: 0
[1723271821.221534] info | SessionManager.hpp | establish_session | session re-established | client_key: 0x45402441, address: 0
[1723271821.232733] info | SessionManager.hpp | establish_session | session re-established | client_key: 0x45402441, address: 0
[1723271821.232781] info | SessionManager.hpp | establish_session | session re-established | client_key: 0x45402441, address: 0
[1723271821.232795] info | SessionManager.hpp | establish_session | session re-established | client_key: 0x45402441, address: 0
[1723271821.232807] info | SessionManager.hpp | establish_session | session re-established | client_key: 0x45402441, address: 0
[1723271821.243884] info | SessionManager.hpp | establish_session | session re-established | client_key: 0x45402441, address: 0
[1723271821.243928] info | SessionManager.hpp | establish_session | session re-established | client_key: 0x45402441, address: 0
[1723271821.243941] info | SessionManager.hpp | establish_session | session re-established | client_key: 0x45402441, address: 0
[1723271821.243953] info | SessionManager.hpp | establish_session | session re-established | client_key: 0x45402441, address: 0
[1723271821.254833] info | SessionManager.hpp | establish_session | session re-established | client_key: 0x45402441, address: 0
[1723271821.254880] info | SessionManager.hpp | establish_session | session re-established | client_key: 0x45402441, address: 0
[1723271821.254893] info | SessionManager.hpp | establish_session | session re-established | client_key: 0x45402441, address: 0
[1723271821.254905] info | SessionManager.hpp | establish_session | session re-established | client_key: 0x45402441, address: 0
[1723271821.265959] info | SessionManager.hpp | establish_session | session re-established | client_key: 0x45402441, address: 0
[1723271821.266006] info | SessionManager.hpp | establish_session | session re-established | client_key: 0x45402441, address: 0
[1723271821.266019] info | SessionManager.hpp | establish_session | session re-established | client_ke

Start with the reported micro-ROS Agent serial command and its repeated session re-established output, then compare the STM32CubeMX project setup with the expected subscriber and publisher creation flow. Reproduce the issue with /dev/ttyACM0 and determine what prevents creation; done means the subscriber and publisher are created without the repeated session loop.

Written by the indexing model from the issue text.