qemu-discuss
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

QEMU baremetal TCP sockets


From: Benjamin
Subject: QEMU baremetal TCP sockets
Date: Wed, 27 May 2020 13:51:23 -0600

I am attempting to run the FreeRTOS+TCP demo found here (release 10.1.1):
https://github.com/FreeRTOS/FreeRTOS-Kernel/tree/d6c89bb3a078bd51a830d30a22919a952bdc424c/FreeRTOS-Plus/Demo/FreeRTOS_Plus_TCP_Minimal_Windows_Simulator

The code is written for the Windows Simulator, but I am attempting to target the Xilinx Zynq, emulated by QEMU of course.  The host is Ubuntu 16.04.
Network Interface port:
https://github.com/FreeRTOS/FreeRTOS-Kernel/tree/d6c89bb3a078bd51a830d30a22919a952bdc424c/FreeRTOS-Plus/Source/FreeRTOS-Plus-TCP/portable/NetworkInterface/Zynq

One of the obvious modifications to the demo is changing the way messages are printed, and removing calls to the Windows "Sleep" function.  I am using ARM semihosting to view the print statements.

Besides these changes, what changes will I need to make to the command line call?  The demo creates a TCP echo server and client.  If these are tied together, then no traffic should need to go to the host.  Is there anything special I would need to do to get this to work?

Since this is technically a baremetal application, CLI options like `-nic user,hostfwd=tcp::5022-:22` give the warning "qemu-system-arm: warning: nic cadence_gem.1 has no peer".
(Found https://stackoverflow.com/questions/46041082/how-to-replace-qemu-system-redir-command-argument).

If I ever did want to send traffic between the host and guest (like having a ncat echo server, instead of in FreeRTOS), how would I go about doing that?

Thank you

--
Benjamin

reply via email to

[Prev in Thread] Current Thread [Next in Thread]