-
Notifications
You must be signed in to change notification settings - Fork 50
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
Olimex STM32 E407 FreeRTOS Broken: Build and PingPong App #84
Comments
I have followed the steps in the FreeRTOS tutorial and I have found no problem. Check my session. Could you provide steps for replicating? |
Sorry. I should have been more complete with my steps to reproduce. I watched your video and was worried something was wrong with my ROS2 install until I saw you use serial as the transport. The tutorial is serial..,but I am using Ethernet as the transport. I found the commit in Micro-XRCE-DDS-Client "Fix missing declarations of inet_to family for POSIX_NOPOLL (#272) which causes the following build error I will continue to debug the Agent issue I am seeing with Ethernet. |
I have been checking and:
Why is this not being included correctly? I'll continue checking |
Got it! I this that this PR can solve the problem: #85 Can you test this branch? |
I have tested. The build works and the client is able to connect and publish pings with the agent. I did not check pong. |
Issue template
Steps to reproduce the issue
Just run the FreeRTOS Ping-Pong first app Tutorial with Foxy as RTOS version
Expected behavior
Buld works, client can connect to agent and can send out pings
Actual behavior
Since last Friday 11/5 with previous install client create init options
// create init_options
RCCHECK(rclc_support_init(&support, 0, NULL, &allocator));
but agent would crash when initializing pingpong_node.
// create node
rcl_node_t node;
RCCHECK(rclc_node_init_default(&node, "pingpong_node", "", &support)); ,== crashed here.
Today following the tutorial fresh the build does not complete and issues the following error.
Additional information
Thank you
The text was updated successfully, but these errors were encountered: