2012-04-07 16:50:57 +02:00
|
|
|
#
|
|
|
|
|
# For a description of the syntax of this configuration file,
|
2015-06-28 16:08:57 +02:00
|
|
|
# see the file kconfig-language.txt in the NuttX tools repository.
|
2012-04-07 16:50:57 +02:00
|
|
|
#
|
2012-04-05 19:44:04 +02:00
|
|
|
|
2012-04-11 04:04:59 +02:00
|
|
|
if ARCH_SIM
|
2012-09-09 17:43:18 +02:00
|
|
|
comment "Simulation Configuration Options"
|
|
|
|
|
|
2014-08-23 02:21:32 +02:00
|
|
|
choice
|
|
|
|
|
prompt "Host CPU Type"
|
|
|
|
|
default HOST_X86_64
|
|
|
|
|
|
|
|
|
|
config HOST_X86_64
|
|
|
|
|
bool "x86_64"
|
2019-09-28 18:46:12 +02:00
|
|
|
select ARCH_HAVE_STACKCHECK
|
2020-05-31 20:41:11 +02:00
|
|
|
select LIBC_ARCH_ELF_64BIT if LIBC_ARCH_ELF && !SIM_M32
|
2023-01-13 11:32:10 +01:00
|
|
|
select ARCH_HAVE_MATH_H
|
2014-08-23 02:21:32 +02:00
|
|
|
|
|
|
|
|
config HOST_X86
|
|
|
|
|
bool "x86"
|
2019-09-28 18:46:12 +02:00
|
|
|
select ARCH_HAVE_STACKCHECK
|
2014-08-23 02:21:32 +02:00
|
|
|
|
2017-08-26 19:38:44 +02:00
|
|
|
config HOST_ARM
|
2019-09-28 18:46:12 +02:00
|
|
|
bool "arm"
|
|
|
|
|
select ARCH_HAVE_STACKCHECK
|
2017-08-26 19:38:44 +02:00
|
|
|
|
2022-02-02 23:36:23 +01:00
|
|
|
config HOST_ARM64
|
|
|
|
|
bool "arm64"
|
|
|
|
|
select ARCH_HAVE_STACKCHECK
|
|
|
|
|
|
2014-08-23 02:21:32 +02:00
|
|
|
endchoice # Host CPU Type
|
|
|
|
|
|
2019-08-08 00:05:00 +02:00
|
|
|
config ARCH_CHIP
|
|
|
|
|
string
|
2020-02-10 05:57:25 +01:00
|
|
|
default "sim"
|
2019-08-08 00:05:00 +02:00
|
|
|
|
2014-10-03 16:23:57 +02:00
|
|
|
config SIM_M32
|
|
|
|
|
bool "Build 32-bit simulation on 64-bit machine"
|
|
|
|
|
default n
|
|
|
|
|
depends on HOST_X86_64
|
|
|
|
|
---help---
|
|
|
|
|
Simulation context switching is based on logic like setjmp and longjmp. This
|
|
|
|
|
context switching is only available for 32-bit targets. On 64-bit machines,
|
|
|
|
|
this context switching will fail.
|
|
|
|
|
|
|
|
|
|
The workaround on 64-bit machines for now is to build for a 32-bit target on the
|
|
|
|
|
64-bit machine. The workaround for this issue has been included in NuttX 6.15 and
|
2020-02-23 09:50:23 +01:00
|
|
|
beyond. For those versions, you must add SIM_M32=y to the .config file in
|
2014-10-03 16:23:57 +02:00
|
|
|
order to enable building a 32-bit image on a 64-bit platform.
|
|
|
|
|
|
2015-09-24 17:08:52 +02:00
|
|
|
config SIM_CYGWIN_DECORATED
|
|
|
|
|
bool "Decorated Cygwin names"
|
|
|
|
|
default n
|
|
|
|
|
depends on WINDOWS_CYGWIN
|
|
|
|
|
---help---
|
2017-01-01 22:34:23 +01:00
|
|
|
Older versions of Cygwin tools decorated C symbol names by adding an
|
2015-09-24 17:08:52 +02:00
|
|
|
underscore to the beginning of the symbol name. Newer versions of
|
|
|
|
|
Cygwin do not seem to do this.
|
|
|
|
|
|
2015-09-24 22:53:04 +02:00
|
|
|
How do you know if you need this option? You could look at the generated
|
|
|
|
|
symbol tables to see if there are underscore characters at the beginning
|
|
|
|
|
of the symbol names. Or, if you need this option, the simulation will not
|
|
|
|
|
run: It will crash early, probably in some function due to the failure to
|
|
|
|
|
allocate memory.
|
|
|
|
|
|
2021-10-30 17:45:34 +02:00
|
|
|
config SIM_ASAN
|
2021-03-11 09:28:55 +01:00
|
|
|
bool "Address Sanitizer"
|
|
|
|
|
default n
|
2021-12-27 05:13:48 +01:00
|
|
|
depends on MM_CUSTOMIZE_MANAGER && FRAME_POINTER
|
2021-03-11 09:28:55 +01:00
|
|
|
---help---
|
|
|
|
|
AddressSanitizer (ASan) is a fast compiler-based tool for detecting memory
|
|
|
|
|
bugs in native code.
|
|
|
|
|
|
2021-10-30 17:45:34 +02:00
|
|
|
config SIM_UBSAN
|
|
|
|
|
bool "Undefined Behaviour Sanitizer"
|
|
|
|
|
default n
|
2021-12-27 05:13:48 +01:00
|
|
|
depends on FRAME_POINTER
|
2021-10-30 17:45:34 +02:00
|
|
|
---help---
|
|
|
|
|
Compile-time instrumentation is used to detect various undefined behaviours
|
|
|
|
|
at runtime.
|
|
|
|
|
|
2015-09-24 22:41:57 +02:00
|
|
|
choice
|
|
|
|
|
prompt "X64_64 ABI"
|
|
|
|
|
default SIM_X8664_SYSTEMV if HOST_LINUX
|
|
|
|
|
default SIM_X8664_MICROSOFT if HOST_WINDOWS
|
|
|
|
|
depends on HOST_X86_64 && !SIM_32
|
|
|
|
|
|
|
|
|
|
config SIM_X8664_SYSTEMV
|
|
|
|
|
bool "System V AMD64 ABI"
|
|
|
|
|
---help---
|
|
|
|
|
The calling convention of the System V AMD64 ABI is followed on Solaris,
|
2020-04-26 04:44:18 +02:00
|
|
|
Linux, FreeBSD, macOS, and other UNIX-like or POSIX-compliant operating
|
2015-09-24 22:41:57 +02:00
|
|
|
systems. The first six integer or pointer arguments are passed in registers
|
|
|
|
|
RDI, RSI, RDX, RCX, R8, and R9, while XMM0, XMM1, XMM2, XMM3, XMM4, XMM5,
|
|
|
|
|
XMM6 and XMM7 are used for floating point arguments. For system calls, R10
|
|
|
|
|
is used instead of RCX. As in the Microsoft x64 calling convention,
|
|
|
|
|
additional arguments are passed on the stack and the return value is stored
|
|
|
|
|
in RAX.
|
|
|
|
|
|
|
|
|
|
Registers RBP, RBX, and R12-R15 are callee-save registers; all others must
|
|
|
|
|
be saved by the caller if they wish to preserve their values.
|
|
|
|
|
|
|
|
|
|
Unlike the Microsoft calling convention, a shadow space is not provided; on
|
|
|
|
|
function entry, the return address is adjacent to the seventh integer argument
|
|
|
|
|
on the stack.
|
|
|
|
|
|
|
|
|
|
config SIM_X8664_MICROSOFT
|
|
|
|
|
bool "Microsoft x64 calling convention"
|
|
|
|
|
---help---
|
|
|
|
|
The Microsoft x64 calling convention is followed on Microsoft Windows and
|
|
|
|
|
pre-boot UEFI (for long mode on x86-64). It uses registers RCX, RDX, R8,
|
|
|
|
|
R9 for the first four integer or pointer arguments (in that order), and
|
|
|
|
|
XMM0, XMM1, XMM2, XMM3 are used for floating point arguments. Additional
|
|
|
|
|
arguments are pushed onto the stack (right to left). Integer return
|
|
|
|
|
values (similar to x86) are returned in RAX if 64 bits or less. Floating
|
|
|
|
|
point return values are returned in XMM0. Parameters less than 64 bits
|
|
|
|
|
long are not zero extended; the high bits are not zeroed.
|
|
|
|
|
|
|
|
|
|
endchoice
|
|
|
|
|
|
2020-09-21 15:50:52 +02:00
|
|
|
choice
|
|
|
|
|
prompt "Simulation at a fixed cadence in near real-time"
|
|
|
|
|
default SIM_WALLTIME_SLEEP
|
|
|
|
|
|
|
|
|
|
config SIM_WALLTIME_SLEEP
|
|
|
|
|
bool "Execution the simulation in near real-time using host sleep"
|
2012-04-17 23:53:05 +02:00
|
|
|
---help---
|
2021-03-31 16:11:59 +02:00
|
|
|
NOTE: This configuration setting will cause the sim target's IDLE loop to delay
|
2012-04-17 23:53:05 +02:00
|
|
|
on each call so that the system "timer interrupt" is called at a rate approximately
|
|
|
|
|
correct for the system timer tick rate. With this definition in the configuration,
|
|
|
|
|
sleep() behavior is more or less normal.
|
|
|
|
|
|
2020-09-21 15:50:52 +02:00
|
|
|
config SIM_WALLTIME_SIGNAL
|
|
|
|
|
bool "Execute the simulation using a host timer"
|
|
|
|
|
---help---
|
|
|
|
|
Run the NuttX simulation using a host timer that delivers periodic SIGALRM
|
|
|
|
|
events at a tick rate specified by CONFIG_USEC_PER_TICK. Enabling this option
|
|
|
|
|
will generate the timer 'tick' events from the host timer at a fixed rate.
|
|
|
|
|
The simulated 'tick' events from Idle task are no longer sent.
|
|
|
|
|
|
|
|
|
|
endchoice
|
|
|
|
|
|
2023-02-03 15:12:36 +01:00
|
|
|
config SIM_LOOPTASK_INTERVAL
|
|
|
|
|
int "looptask interval in us"
|
|
|
|
|
default 10000
|
|
|
|
|
---help---
|
|
|
|
|
Looptask sleep time
|
|
|
|
|
|
2021-12-12 16:26:45 +01:00
|
|
|
config SIM_STACKSIZE_ADJUSTMENT
|
|
|
|
|
int "The adjustment of stack size for sim"
|
|
|
|
|
default 65536
|
|
|
|
|
---help---
|
|
|
|
|
The adjustment of stack size for sim. When the task is created,
|
|
|
|
|
the stack size is increased by this amount.
|
|
|
|
|
|
2021-11-24 15:23:14 +01:00
|
|
|
config SIM_HOSTFS
|
|
|
|
|
bool "Simulated HostFS"
|
|
|
|
|
depends on FS_HOSTFS
|
|
|
|
|
---help---
|
|
|
|
|
Access host filesystem through HostFS.
|
|
|
|
|
|
2023-04-14 08:47:27 +02:00
|
|
|
config SIM_IMAGEPATH_AS_CWD
|
|
|
|
|
bool "Simulator switch working directory"
|
|
|
|
|
default n
|
|
|
|
|
---help---
|
|
|
|
|
If this option is enabled, the working path of nuttx will be modified
|
|
|
|
|
to the folder where the nuttx file is located.
|
|
|
|
|
It affects the file access of hostfs, which will start looking for
|
|
|
|
|
files based on the nuttx image folder.
|
|
|
|
|
Otherwise the default $CWD will be used as the starting path for the search.
|
|
|
|
|
Absolute paths are never affected.
|
|
|
|
|
|
2021-08-29 11:52:02 +02:00
|
|
|
choice
|
|
|
|
|
prompt "Simulated Network Interface"
|
|
|
|
|
default SIM_NETDEV
|
|
|
|
|
depends on NET
|
|
|
|
|
optional
|
|
|
|
|
|
2017-04-03 01:46:22 +02:00
|
|
|
config SIM_NETDEV
|
|
|
|
|
bool "Simulated Network Device"
|
2018-08-24 22:23:50 +02:00
|
|
|
select ARCH_HAVE_NETDEV_STATISTICS
|
2020-01-21 06:34:10 +01:00
|
|
|
select SCHED_LPWORK
|
2021-08-29 11:52:02 +02:00
|
|
|
select NET_ETHERNET
|
2020-03-18 13:12:26 +01:00
|
|
|
---help---
|
|
|
|
|
Build in support for a simulated network device.
|
|
|
|
|
|
2021-08-29 11:52:02 +02:00
|
|
|
config SIM_NETUSRSOCK
|
|
|
|
|
bool "Simulated Network Device with Native Stack via usrsock"
|
|
|
|
|
select NET_USRSOCK
|
|
|
|
|
---help---
|
|
|
|
|
Built-in support for a simulated network device using native stack via usrsock
|
|
|
|
|
|
|
|
|
|
endchoice
|
|
|
|
|
|
2020-03-18 13:12:26 +01:00
|
|
|
if SIM_NETDEV
|
|
|
|
|
|
|
|
|
|
choice
|
|
|
|
|
prompt "Simulated Network Device Type"
|
|
|
|
|
default SIM_NETDEV_TAP
|
|
|
|
|
|
|
|
|
|
config SIM_NETDEV_TAP
|
|
|
|
|
bool "Simulated Network Device with TAP/WPCAP"
|
2020-03-21 04:53:07 +01:00
|
|
|
depends on (HOST_LINUX || HOST_WINDOWS)
|
2017-04-03 01:46:22 +02:00
|
|
|
---help---
|
|
|
|
|
Build in support for a simulated network device using a TAP device on Linux or
|
|
|
|
|
WPCAP on Windows.
|
|
|
|
|
|
2020-03-18 13:12:26 +01:00
|
|
|
config SIM_NETDEV_VPNKIT
|
|
|
|
|
bool "Simulated Network Device with VPNKit"
|
|
|
|
|
---help---
|
|
|
|
|
Build in support for a simulated network device using VPNKit.
|
|
|
|
|
|
|
|
|
|
endchoice
|
|
|
|
|
|
2022-10-11 08:19:07 +02:00
|
|
|
config SIM_NETDEV_NUMBER
|
|
|
|
|
int "Number of Simulated Network Device"
|
|
|
|
|
default 1
|
|
|
|
|
range 1 8
|
|
|
|
|
depends on SIM_NETDEV_TAP
|
|
|
|
|
---help---
|
|
|
|
|
The number of simulated network devices.
|
|
|
|
|
|
|
|
|
|
Note that only one network device will be brought up by netinit automatically,
|
|
|
|
|
others will be kept in DOWN state by default.
|
|
|
|
|
|
2020-03-18 13:12:26 +01:00
|
|
|
endif
|
|
|
|
|
|
2020-03-21 03:55:58 +01:00
|
|
|
config SIM_NETDEV_VPNKIT_PATH
|
|
|
|
|
string "Unix domain socket to communicate with VPNKit"
|
|
|
|
|
default "/tmp/vpnkit-nuttx"
|
|
|
|
|
depends on SIM_NETDEV_VPNKIT
|
|
|
|
|
|
SUMMARY
-------
This patch enhances networking support for the simulation under Linux.
Includes updated support for Linux TUN/TAP, and the addition of support for
Linux bridge devices.
CHANGES
-------
o Check to see if the d_txavail callback is present before calling it in
the arp send code. This prevents a segfault when simulating the telnetd
daemon with arp send enabled.
o Adjust the simulation's netdriver_loop() so it will detect and respond to
ARP requests.
o Do not attempt to take the tap device's hardware address for use by the
simulation. That hardware address belongs to the host end of the link,
not the simulation end. Generate a randomized MAC address instead.
o Do not assign an IP address to the interface on the host side of the TAP
link.
+ Provide two modes: "host route" and "bridge".
+ In host route mode, maintain a host route that points any traffic for the
simulation's IP address to the tap device. In this mode, so long as the
simulation's IP is a free address in the same subnet as the host, no
additional configuration will be required to talk to it from the host.
Note that address changes are handled automatically if they follow the
rule of if-down/set-address/if-up, which everything seems to.
+ In bridge mode, add the tap device to the specified bridge instance. See
configs/sim/NETWORK-LINUX.txt for information and usage examples. This
enables much more flexible configurations (with fewer headaches), such as
running multiple simulations on a single host, all of which can access
the network the host is connected to.
o Refresh configurations in configs/sim where CONFIG_NET=y. They default
to "host route" mode.
o Add configs/sim/NETWORK-LINUX.txt
CAVEATS
-------
- The MAC address generation code is extremely simplistic, and does not
check for potential conflicts on the network. Probably not an issue, but
something to be aware of.
- I was careful to leave it in a state where Cygwin/pcap should still work,
but I don't have a Windows environment to test in. This should be
checked.
- I don't know if this was ever intended to work with OS X. I didn't even
try to test it there.
NOTES
-----
- Was able to get telnetd working and simulate nsh over telnet, but only so
long as listen backlogs were disabled.
There appears to be a bug in the backlog code where sockets are being
returned in SYN_RCVD state instead of waiting until they're ESTABLISHED;
if you perform an immediate send after accepting the connection, it will
confuse the stack and the send will hang; additionally, the connection
will never reach ESTABLISHED state.
Can be worked around by adding a sleep(1) after the accept in telnetd. I
don't have the necessary knowledge of the IP stack to know what the
correct fix is.
2016-05-21 01:36:14 +02:00
|
|
|
if HOST_LINUX
|
|
|
|
|
choice
|
|
|
|
|
prompt "Simulation Network Type"
|
|
|
|
|
default SIM_NET_HOST_ROUTE
|
2020-03-18 13:12:26 +01:00
|
|
|
depends on SIM_NETDEV_TAP
|
SUMMARY
-------
This patch enhances networking support for the simulation under Linux.
Includes updated support for Linux TUN/TAP, and the addition of support for
Linux bridge devices.
CHANGES
-------
o Check to see if the d_txavail callback is present before calling it in
the arp send code. This prevents a segfault when simulating the telnetd
daemon with arp send enabled.
o Adjust the simulation's netdriver_loop() so it will detect and respond to
ARP requests.
o Do not attempt to take the tap device's hardware address for use by the
simulation. That hardware address belongs to the host end of the link,
not the simulation end. Generate a randomized MAC address instead.
o Do not assign an IP address to the interface on the host side of the TAP
link.
+ Provide two modes: "host route" and "bridge".
+ In host route mode, maintain a host route that points any traffic for the
simulation's IP address to the tap device. In this mode, so long as the
simulation's IP is a free address in the same subnet as the host, no
additional configuration will be required to talk to it from the host.
Note that address changes are handled automatically if they follow the
rule of if-down/set-address/if-up, which everything seems to.
+ In bridge mode, add the tap device to the specified bridge instance. See
configs/sim/NETWORK-LINUX.txt for information and usage examples. This
enables much more flexible configurations (with fewer headaches), such as
running multiple simulations on a single host, all of which can access
the network the host is connected to.
o Refresh configurations in configs/sim where CONFIG_NET=y. They default
to "host route" mode.
o Add configs/sim/NETWORK-LINUX.txt
CAVEATS
-------
- The MAC address generation code is extremely simplistic, and does not
check for potential conflicts on the network. Probably not an issue, but
something to be aware of.
- I was careful to leave it in a state where Cygwin/pcap should still work,
but I don't have a Windows environment to test in. This should be
checked.
- I don't know if this was ever intended to work with OS X. I didn't even
try to test it there.
NOTES
-----
- Was able to get telnetd working and simulate nsh over telnet, but only so
long as listen backlogs were disabled.
There appears to be a bug in the backlog code where sockets are being
returned in SYN_RCVD state instead of waiting until they're ESTABLISHED;
if you perform an immediate send after accepting the connection, it will
confuse the stack and the send will hang; additionally, the connection
will never reach ESTABLISHED state.
Can be worked around by adding a sleep(1) after the accept in telnetd. I
don't have the necessary knowledge of the IP stack to know what the
correct fix is.
2016-05-21 01:36:14 +02:00
|
|
|
|
|
|
|
|
config SIM_NET_HOST_ROUTE
|
|
|
|
|
bool "Use local host route"
|
|
|
|
|
---help---
|
|
|
|
|
Add a host route for the simulation that points to the created tap device. The
|
|
|
|
|
simulation will not be able to access the public network unless iptables is
|
2019-08-08 16:46:54 +02:00
|
|
|
configured to masquerade for it. See boards/sim/sim sim/NETWORK-LINUX.txt
|
|
|
|
|
for more information.
|
SUMMARY
-------
This patch enhances networking support for the simulation under Linux.
Includes updated support for Linux TUN/TAP, and the addition of support for
Linux bridge devices.
CHANGES
-------
o Check to see if the d_txavail callback is present before calling it in
the arp send code. This prevents a segfault when simulating the telnetd
daemon with arp send enabled.
o Adjust the simulation's netdriver_loop() so it will detect and respond to
ARP requests.
o Do not attempt to take the tap device's hardware address for use by the
simulation. That hardware address belongs to the host end of the link,
not the simulation end. Generate a randomized MAC address instead.
o Do not assign an IP address to the interface on the host side of the TAP
link.
+ Provide two modes: "host route" and "bridge".
+ In host route mode, maintain a host route that points any traffic for the
simulation's IP address to the tap device. In this mode, so long as the
simulation's IP is a free address in the same subnet as the host, no
additional configuration will be required to talk to it from the host.
Note that address changes are handled automatically if they follow the
rule of if-down/set-address/if-up, which everything seems to.
+ In bridge mode, add the tap device to the specified bridge instance. See
configs/sim/NETWORK-LINUX.txt for information and usage examples. This
enables much more flexible configurations (with fewer headaches), such as
running multiple simulations on a single host, all of which can access
the network the host is connected to.
o Refresh configurations in configs/sim where CONFIG_NET=y. They default
to "host route" mode.
o Add configs/sim/NETWORK-LINUX.txt
CAVEATS
-------
- The MAC address generation code is extremely simplistic, and does not
check for potential conflicts on the network. Probably not an issue, but
something to be aware of.
- I was careful to leave it in a state where Cygwin/pcap should still work,
but I don't have a Windows environment to test in. This should be
checked.
- I don't know if this was ever intended to work with OS X. I didn't even
try to test it there.
NOTES
-----
- Was able to get telnetd working and simulate nsh over telnet, but only so
long as listen backlogs were disabled.
There appears to be a bug in the backlog code where sockets are being
returned in SYN_RCVD state instead of waiting until they're ESTABLISHED;
if you perform an immediate send after accepting the connection, it will
confuse the stack and the send will hang; additionally, the connection
will never reach ESTABLISHED state.
Can be worked around by adding a sleep(1) after the accept in telnetd. I
don't have the necessary knowledge of the IP stack to know what the
correct fix is.
2016-05-21 01:36:14 +02:00
|
|
|
|
|
|
|
|
config SIM_NET_BRIDGE
|
|
|
|
|
bool "Attach to Linux bridge"
|
2019-10-06 05:39:12 +02:00
|
|
|
---help---
|
SUMMARY
-------
This patch enhances networking support for the simulation under Linux.
Includes updated support for Linux TUN/TAP, and the addition of support for
Linux bridge devices.
CHANGES
-------
o Check to see if the d_txavail callback is present before calling it in
the arp send code. This prevents a segfault when simulating the telnetd
daemon with arp send enabled.
o Adjust the simulation's netdriver_loop() so it will detect and respond to
ARP requests.
o Do not attempt to take the tap device's hardware address for use by the
simulation. That hardware address belongs to the host end of the link,
not the simulation end. Generate a randomized MAC address instead.
o Do not assign an IP address to the interface on the host side of the TAP
link.
+ Provide two modes: "host route" and "bridge".
+ In host route mode, maintain a host route that points any traffic for the
simulation's IP address to the tap device. In this mode, so long as the
simulation's IP is a free address in the same subnet as the host, no
additional configuration will be required to talk to it from the host.
Note that address changes are handled automatically if they follow the
rule of if-down/set-address/if-up, which everything seems to.
+ In bridge mode, add the tap device to the specified bridge instance. See
configs/sim/NETWORK-LINUX.txt for information and usage examples. This
enables much more flexible configurations (with fewer headaches), such as
running multiple simulations on a single host, all of which can access
the network the host is connected to.
o Refresh configurations in configs/sim where CONFIG_NET=y. They default
to "host route" mode.
o Add configs/sim/NETWORK-LINUX.txt
CAVEATS
-------
- The MAC address generation code is extremely simplistic, and does not
check for potential conflicts on the network. Probably not an issue, but
something to be aware of.
- I was careful to leave it in a state where Cygwin/pcap should still work,
but I don't have a Windows environment to test in. This should be
checked.
- I don't know if this was ever intended to work with OS X. I didn't even
try to test it there.
NOTES
-----
- Was able to get telnetd working and simulate nsh over telnet, but only so
long as listen backlogs were disabled.
There appears to be a bug in the backlog code where sockets are being
returned in SYN_RCVD state instead of waiting until they're ESTABLISHED;
if you perform an immediate send after accepting the connection, it will
confuse the stack and the send will hang; additionally, the connection
will never reach ESTABLISHED state.
Can be worked around by adding a sleep(1) after the accept in telnetd. I
don't have the necessary knowledge of the IP stack to know what the
correct fix is.
2016-05-21 01:36:14 +02:00
|
|
|
Add the created tap device to the specified bridge. You will need to manually
|
|
|
|
|
configure the bridge IP address (if any) and routes that point to the bridge.
|
2019-08-08 16:46:54 +02:00
|
|
|
See boards/sim/sim/sim/NETWORK-LINUX.txt for more information.
|
SUMMARY
-------
This patch enhances networking support for the simulation under Linux.
Includes updated support for Linux TUN/TAP, and the addition of support for
Linux bridge devices.
CHANGES
-------
o Check to see if the d_txavail callback is present before calling it in
the arp send code. This prevents a segfault when simulating the telnetd
daemon with arp send enabled.
o Adjust the simulation's netdriver_loop() so it will detect and respond to
ARP requests.
o Do not attempt to take the tap device's hardware address for use by the
simulation. That hardware address belongs to the host end of the link,
not the simulation end. Generate a randomized MAC address instead.
o Do not assign an IP address to the interface on the host side of the TAP
link.
+ Provide two modes: "host route" and "bridge".
+ In host route mode, maintain a host route that points any traffic for the
simulation's IP address to the tap device. In this mode, so long as the
simulation's IP is a free address in the same subnet as the host, no
additional configuration will be required to talk to it from the host.
Note that address changes are handled automatically if they follow the
rule of if-down/set-address/if-up, which everything seems to.
+ In bridge mode, add the tap device to the specified bridge instance. See
configs/sim/NETWORK-LINUX.txt for information and usage examples. This
enables much more flexible configurations (with fewer headaches), such as
running multiple simulations on a single host, all of which can access
the network the host is connected to.
o Refresh configurations in configs/sim where CONFIG_NET=y. They default
to "host route" mode.
o Add configs/sim/NETWORK-LINUX.txt
CAVEATS
-------
- The MAC address generation code is extremely simplistic, and does not
check for potential conflicts on the network. Probably not an issue, but
something to be aware of.
- I was careful to leave it in a state where Cygwin/pcap should still work,
but I don't have a Windows environment to test in. This should be
checked.
- I don't know if this was ever intended to work with OS X. I didn't even
try to test it there.
NOTES
-----
- Was able to get telnetd working and simulate nsh over telnet, but only so
long as listen backlogs were disabled.
There appears to be a bug in the backlog code where sockets are being
returned in SYN_RCVD state instead of waiting until they're ESTABLISHED;
if you perform an immediate send after accepting the connection, it will
confuse the stack and the send will hang; additionally, the connection
will never reach ESTABLISHED state.
Can be worked around by adding a sleep(1) after the accept in telnetd. I
don't have the necessary knowledge of the IP stack to know what the
correct fix is.
2016-05-21 01:36:14 +02:00
|
|
|
|
|
|
|
|
endchoice
|
|
|
|
|
endif
|
|
|
|
|
|
|
|
|
|
if SIM_NET_BRIDGE
|
|
|
|
|
config SIM_NET_BRIDGE_DEVICE
|
|
|
|
|
string "Bridge device to attach"
|
|
|
|
|
default "nuttx0"
|
|
|
|
|
---help---
|
|
|
|
|
The name of the bridge device (as passed to "brctl create") to which the simulation's
|
|
|
|
|
TAP interface should be added.
|
|
|
|
|
|
|
|
|
|
endif
|
|
|
|
|
|
2020-07-24 04:40:54 +02:00
|
|
|
config SIM_SOUND
|
|
|
|
|
bool "Simulated sound support"
|
|
|
|
|
depends on AUDIO
|
|
|
|
|
default y
|
|
|
|
|
|
|
|
|
|
if SIM_SOUND
|
|
|
|
|
|
|
|
|
|
choice
|
|
|
|
|
prompt "Simulated sound Type"
|
|
|
|
|
default SIM_SOUND_ALSA
|
|
|
|
|
|
|
|
|
|
config SIM_SOUND_ALSA
|
|
|
|
|
bool "alsa support on sim"
|
|
|
|
|
depends on HOST_LINUX
|
|
|
|
|
|
|
|
|
|
endchoice
|
|
|
|
|
|
|
|
|
|
endif
|
|
|
|
|
|
2022-11-22 09:13:36 +01:00
|
|
|
config SIM_VIDEO
|
|
|
|
|
bool "Simulated video support"
|
|
|
|
|
depends on VIDEO
|
|
|
|
|
default y
|
|
|
|
|
|
|
|
|
|
if SIM_VIDEO
|
|
|
|
|
|
|
|
|
|
choice
|
|
|
|
|
prompt "Simulated video device type"
|
|
|
|
|
default SIM_VIDEO_V4L2
|
|
|
|
|
|
|
|
|
|
config SIM_VIDEO_V4L2
|
|
|
|
|
bool "V4L2 camera support on sim"
|
|
|
|
|
depends on HOST_LINUX
|
|
|
|
|
|
|
|
|
|
endchoice
|
|
|
|
|
|
|
|
|
|
config HOST_VIDEO_DEV_PATH
|
|
|
|
|
string "Host video device path"
|
|
|
|
|
default "/dev/video0"
|
|
|
|
|
|
|
|
|
|
config SIM_VIDEO_DEV_PATH
|
|
|
|
|
string "NuttX video device path"
|
|
|
|
|
default "/dev/video"
|
|
|
|
|
|
|
|
|
|
endif
|
|
|
|
|
|
2020-11-02 02:38:48 +01:00
|
|
|
menu "Simulated Graphics/Input"
|
2014-12-08 15:29:48 +01:00
|
|
|
|
2012-04-17 23:53:05 +02:00
|
|
|
config SIM_X11FB
|
2021-04-27 17:14:39 +02:00
|
|
|
bool "X11 graphics/input"
|
|
|
|
|
default n
|
|
|
|
|
select SCHED_LPWORK
|
2012-04-17 23:53:05 +02:00
|
|
|
---help---
|
2020-11-02 02:38:48 +01:00
|
|
|
Use X11 to provide graphics and input emulation to interact with host.
|
2012-04-17 23:53:05 +02:00
|
|
|
|
|
|
|
|
config SIM_X11NOSHM
|
|
|
|
|
bool "Don't use shared memory with X11"
|
|
|
|
|
default n
|
|
|
|
|
depends on SIM_X11FB
|
|
|
|
|
---help---
|
2020-11-02 02:38:48 +01:00
|
|
|
Don't use shared memory with the X11 graphics device emulation.
|
|
|
|
|
|
|
|
|
|
menu "Window Configuration"
|
2012-04-17 23:53:05 +02:00
|
|
|
|
|
|
|
|
config SIM_FBHEIGHT
|
|
|
|
|
int "Display height"
|
|
|
|
|
default 240
|
|
|
|
|
---help---
|
|
|
|
|
Simulated display height. Default: 240
|
|
|
|
|
|
|
|
|
|
config SIM_FBWIDTH
|
|
|
|
|
int "Display width"
|
2020-11-02 02:38:48 +01:00
|
|
|
default 320
|
2012-04-17 23:53:05 +02:00
|
|
|
---help---
|
2022-03-28 04:56:21 +02:00
|
|
|
Simulated width of the display. Default: 320
|
2012-04-17 23:53:05 +02:00
|
|
|
|
|
|
|
|
config SIM_FBBPP
|
|
|
|
|
int "Pixel depth in bits"
|
|
|
|
|
default 8
|
|
|
|
|
---help---
|
|
|
|
|
Pixel depth in bits. Valid choices are 4, 8, 16, 24, or 32.
|
|
|
|
|
If you use the X11 display emulation, the selected BPP must match the BPP
|
|
|
|
|
of your graphics hardware (probably 32 bits). Default: 8
|
|
|
|
|
|
2020-11-02 02:38:48 +01:00
|
|
|
endmenu
|
2014-12-08 15:29:48 +01:00
|
|
|
|
2014-12-14 17:19:07 +01:00
|
|
|
choice
|
2020-11-02 02:38:48 +01:00
|
|
|
prompt "Graphics Device"
|
|
|
|
|
default SIM_FRAMEBUFFER
|
|
|
|
|
---help---
|
|
|
|
|
Choose which kind of graphics device to emulate
|
|
|
|
|
|
|
|
|
|
config SIM_LCDDRIVER
|
|
|
|
|
bool "LCD device"
|
|
|
|
|
depends on LCD
|
|
|
|
|
---help---
|
|
|
|
|
Emulate an LCD driver
|
|
|
|
|
|
|
|
|
|
config SIM_FRAMEBUFFER
|
|
|
|
|
bool "Framebuffer"
|
|
|
|
|
depends on VIDEO_FB
|
|
|
|
|
---help---
|
|
|
|
|
Emulate a framebuffer
|
|
|
|
|
|
2021-10-28 12:44:40 +02:00
|
|
|
config SIM_VNCSERVER
|
|
|
|
|
bool "VNC server"
|
|
|
|
|
depends on VNCSERVER
|
|
|
|
|
---help---
|
|
|
|
|
Serve a VNC server
|
|
|
|
|
|
2020-11-02 02:38:48 +01:00
|
|
|
endchoice
|
|
|
|
|
|
|
|
|
|
if INPUT
|
|
|
|
|
choice
|
|
|
|
|
prompt "Input Device"
|
2014-12-14 17:19:07 +01:00
|
|
|
default SIM_NOINPUT
|
|
|
|
|
|
2012-04-17 23:53:05 +02:00
|
|
|
config SIM_TOUCHSCREEN
|
2014-12-14 17:19:07 +01:00
|
|
|
bool "X11 mouse-based touchscreen emulation"
|
2021-11-10 15:27:50 +01:00
|
|
|
select INPUT_TOUCHSCREEN
|
2020-11-02 02:38:48 +01:00
|
|
|
depends on SIM_X11FB
|
2012-04-17 23:53:05 +02:00
|
|
|
---help---
|
|
|
|
|
Support an X11 mouse-based touchscreen emulation. Also needs INPUT=y
|
|
|
|
|
|
2014-12-14 17:19:07 +01:00
|
|
|
config SIM_AJOYSTICK
|
|
|
|
|
bool "X11 mouse-based analog joystick emulation"
|
2020-11-02 02:38:48 +01:00
|
|
|
depends on SIM_X11FB
|
2014-12-14 17:19:07 +01:00
|
|
|
---help---
|
2018-07-09 02:24:45 +02:00
|
|
|
Support an X11 mouse-based analog joystick emulation. Also needs INPUT=y
|
2014-12-14 17:19:07 +01:00
|
|
|
|
2020-11-03 19:53:20 +01:00
|
|
|
config SIM_BUTTONS
|
|
|
|
|
bool "X11 mouse-based button emulation"
|
|
|
|
|
depends on SIM_X11FB
|
|
|
|
|
---help---
|
|
|
|
|
Support an X11 mouse-based button emulation
|
|
|
|
|
(left-click mapped to button press). Also needs INPUT=y
|
|
|
|
|
|
2014-12-14 17:19:07 +01:00
|
|
|
config SIM_NOINPUT
|
|
|
|
|
bool "No input device"
|
|
|
|
|
|
2020-11-02 02:38:48 +01:00
|
|
|
endchoice # Input Device
|
2022-04-06 06:37:32 +02:00
|
|
|
|
|
|
|
|
config SIM_KEYBOARD
|
|
|
|
|
bool "X11 keyboard"
|
|
|
|
|
select INPUT_KEYBOARD
|
|
|
|
|
depends on SIM_X11FB
|
|
|
|
|
---help---
|
|
|
|
|
Support an X11 mouse-based keyboard emulation. Also needs INPUT=y
|
|
|
|
|
|
|
|
|
|
config SIM_KEYBOARD_BUFFSIZE
|
|
|
|
|
int "sim keyboard buffer size"
|
|
|
|
|
default 64
|
|
|
|
|
depends on SIM_KEYBOARD
|
|
|
|
|
---help---
|
|
|
|
|
Emulator keyboard buffer size
|
|
|
|
|
|
2020-11-02 02:38:48 +01:00
|
|
|
endif # if INPUT
|
|
|
|
|
|
|
|
|
|
endmenu
|
2014-12-14 17:19:07 +01:00
|
|
|
|
2020-08-27 02:38:44 +02:00
|
|
|
config SIM_HCISOCKET
|
|
|
|
|
bool "Attach Host Bluetooth"
|
|
|
|
|
default false
|
2023-01-12 07:53:37 +01:00
|
|
|
depends on HOST_LINUX && (UART_BTH4 || WIRELESS_BLUETOOTH)
|
2020-08-27 02:38:44 +02:00
|
|
|
---help---
|
|
|
|
|
Attached the local bluetooth device to the simulation
|
|
|
|
|
target via HCI_CHANNEL_USER. This gives NuttX full
|
|
|
|
|
control of the device, but is abstracted from the
|
|
|
|
|
physical interface which is still handled by Linux.
|
|
|
|
|
|
2022-04-12 07:13:58 +02:00
|
|
|
config SIM_HCISOCKET_DEVID
|
|
|
|
|
int "Bluetooth Device ID"
|
|
|
|
|
default 0
|
|
|
|
|
depends on SIM_HCISOCKET
|
|
|
|
|
---help---
|
|
|
|
|
Attached the local bluetooth device use specific
|
|
|
|
|
Bluetooth HCI number id.
|
|
|
|
|
|
2020-10-29 09:41:58 +01:00
|
|
|
config SIM_I2CBUS
|
|
|
|
|
bool "Simulated I2C Bus"
|
|
|
|
|
default n
|
|
|
|
|
select I2C
|
|
|
|
|
---help---
|
|
|
|
|
Build in support for simulated i2c bus
|
|
|
|
|
|
|
|
|
|
if SIM_I2CBUS
|
|
|
|
|
|
|
|
|
|
choice
|
|
|
|
|
prompt "Simulated I2C Bus Type"
|
|
|
|
|
default SIM_I2CBUS_LINUX
|
|
|
|
|
|
|
|
|
|
config SIM_I2CBUS_LINUX
|
|
|
|
|
bool "Linux I2C Bus Character Dev"
|
|
|
|
|
depends on HOST_LINUX
|
|
|
|
|
---help---
|
|
|
|
|
Attach a Linux I2C bus via the character device
|
|
|
|
|
interface. This should be used with caution as it
|
|
|
|
|
could interfere with devices internal to the system.
|
|
|
|
|
It is recommended to use this with a USB<>I2C device
|
|
|
|
|
like the MCP2221 and set udev rules so that only
|
|
|
|
|
the bus provided by this device can be controlled
|
|
|
|
|
by the user running the simulator.
|
|
|
|
|
https://www.kernel.org/doc/html/latest/i2c/dev-interface.html
|
|
|
|
|
|
|
|
|
|
endchoice
|
|
|
|
|
|
2022-12-28 11:07:23 +01:00
|
|
|
config SIM_I2CBUS_ID
|
|
|
|
|
int "I2C host bus ID to attach to simulator"
|
|
|
|
|
default 0
|
|
|
|
|
depends on SIM_I2CBUS
|
|
|
|
|
---help---
|
|
|
|
|
This is the bus identifier that should be used by the host implementation to
|
|
|
|
|
attach to the simulator driver.
|
|
|
|
|
|
2020-10-29 09:41:58 +01:00
|
|
|
endif
|
|
|
|
|
|
2021-09-02 11:09:10 +02:00
|
|
|
config SIM_SPI
|
|
|
|
|
bool "Simulated SPI port"
|
|
|
|
|
default n
|
|
|
|
|
select SPI
|
|
|
|
|
---help---
|
|
|
|
|
Build in support for simulated spi port
|
|
|
|
|
|
|
|
|
|
if SIM_SPI
|
|
|
|
|
|
|
|
|
|
choice
|
|
|
|
|
prompt "Simulated SPI Type"
|
|
|
|
|
default SIM_SPI_LINUX
|
|
|
|
|
|
|
|
|
|
config SIM_SPI_LINUX
|
|
|
|
|
bool "Linux SPI Character Dev"
|
|
|
|
|
depends on HOST_LINUX
|
|
|
|
|
---help---
|
|
|
|
|
Attach a Linux SPI port via the character device
|
|
|
|
|
interface. To achieve a SPI port on Linux host, it is
|
|
|
|
|
recommended to use a USB<>SPI device such as CH341A/B.
|
|
|
|
|
|
|
|
|
|
endchoice
|
|
|
|
|
|
2022-12-28 11:07:23 +01:00
|
|
|
config SIM_SPIDEV_NAME
|
|
|
|
|
string "the name of SPI host dev to attach to simulator"
|
|
|
|
|
default "/dev/spidev0.0"
|
|
|
|
|
depends on SIM_SPI
|
|
|
|
|
---help---
|
|
|
|
|
This is the name of the SPI device on the host implementation to
|
|
|
|
|
attach to the simulator driver.
|
|
|
|
|
|
2021-09-02 11:09:10 +02:00
|
|
|
endif
|
|
|
|
|
|
2022-01-20 18:18:56 +01:00
|
|
|
menu "Simulated UART"
|
|
|
|
|
|
2023-02-03 11:44:03 +01:00
|
|
|
config SIM_UART_DMA
|
|
|
|
|
bool "SIM UART use DMA mode"
|
|
|
|
|
default y
|
|
|
|
|
select SERIAL_TXDMA
|
|
|
|
|
select SERIAL_RXDMA
|
|
|
|
|
---help---
|
|
|
|
|
console use DMA mode or single char mode
|
|
|
|
|
|
2020-08-31 14:12:32 +02:00
|
|
|
config SIM_UART_NUMBER
|
2022-01-20 18:18:56 +01:00
|
|
|
int "Number of simulated UART ports"
|
2020-08-31 14:12:32 +02:00
|
|
|
default 0
|
2022-01-20 18:18:56 +01:00
|
|
|
range 0 4
|
|
|
|
|
---help---
|
|
|
|
|
Under simulation, a NuttX port can be bound to a serial
|
|
|
|
|
port on the host machine. This way NuttX can access the
|
|
|
|
|
host's hardware directly.
|
2022-11-22 09:13:36 +01:00
|
|
|
|
2022-01-20 18:18:56 +01:00
|
|
|
There are two possibilities regarding the host's port:
|
|
|
|
|
it can be either a physical one, or a simulated one.
|
2022-11-22 09:13:36 +01:00
|
|
|
|
2022-01-20 18:18:56 +01:00
|
|
|
In case of a physical port, NuttX will be able to open
|
|
|
|
|
this port and communicate with any actual hardware that
|
|
|
|
|
it is connected to. This is useful for testing code that
|
|
|
|
|
uses external hardware (e.g. sensors or other boards).
|
|
|
|
|
In order for this to work, NuttX port name must be set to
|
|
|
|
|
the same name that the host is using for this port (e.g.
|
|
|
|
|
/dev/ttyUSB0).
|
2022-11-22 09:13:36 +01:00
|
|
|
|
2022-01-20 18:18:56 +01:00
|
|
|
Alternativelly, a "simulated" host port may be used to.
|
|
|
|
|
This is useful if you need to also simulate the external
|
|
|
|
|
hardware, or to have NuttX communicate with any other
|
|
|
|
|
software in your system.
|
|
|
|
|
You can create a "simulated" port in your host,
|
|
|
|
|
by running:
|
2022-11-22 09:13:36 +01:00
|
|
|
|
2022-01-20 18:18:56 +01:00
|
|
|
socat PTY,link=/dev/ttySIM0 PTY,link=/dev/ttyNX0
|
2023-05-09 15:26:24 +02:00
|
|
|
stty -F /dev/ttySIM0 raw
|
|
|
|
|
stty -F /dev/ttyNX0 raw
|
2022-11-22 09:13:36 +01:00
|
|
|
|
2022-01-20 18:18:56 +01:00
|
|
|
This will create two new ports on your system.
|
|
|
|
|
NuttX will use the ttySIM0 port, and another software
|
|
|
|
|
may open and use the ttyNX0 port.
|
|
|
|
|
Anything sent to the one of these ports will be relayed
|
|
|
|
|
automatically to the other, and vice-versa.
|
|
|
|
|
|
|
|
|
|
config SIM_UART_BUFFER_SIZE
|
|
|
|
|
int "UART buffer size"
|
|
|
|
|
default 256
|
|
|
|
|
depends on SIM_UART_NUMBER >= 1
|
|
|
|
|
---help---
|
|
|
|
|
The size of the transmit and receive buffers of the
|
|
|
|
|
simulated UART ports.
|
2022-11-22 09:13:36 +01:00
|
|
|
|
2022-01-20 18:18:56 +01:00
|
|
|
Note that all ports will have the same buffer size.
|
2020-08-31 14:12:32 +02:00
|
|
|
|
|
|
|
|
config SIM_UART0_NAME
|
2022-01-20 18:18:56 +01:00
|
|
|
string "UART port 0 name"
|
2020-08-31 14:12:32 +02:00
|
|
|
default "/dev/ttySIM0"
|
|
|
|
|
depends on SIM_UART_NUMBER >= 1
|
2022-01-20 18:18:56 +01:00
|
|
|
---help---
|
|
|
|
|
This is the name of the simulated UART port.
|
|
|
|
|
The port will be mounted in NuttX under this name.
|
2022-11-22 09:13:36 +01:00
|
|
|
|
2022-01-20 18:18:56 +01:00
|
|
|
A UART port must also exist on the host system
|
|
|
|
|
with the exact same name specified here.
|
2020-08-31 14:12:32 +02:00
|
|
|
|
|
|
|
|
config SIM_UART1_NAME
|
2022-01-20 18:18:56 +01:00
|
|
|
string "UART port 1 name"
|
2020-08-31 14:12:32 +02:00
|
|
|
default "/dev/ttySIM1"
|
|
|
|
|
depends on SIM_UART_NUMBER >= 2
|
2022-01-20 18:18:56 +01:00
|
|
|
---help---
|
|
|
|
|
This is the name of the simulated UART port.
|
|
|
|
|
The port will be mounted in NuttX under this name.
|
2022-11-22 09:13:36 +01:00
|
|
|
|
2022-01-20 18:18:56 +01:00
|
|
|
A UART port must also exist on the host system
|
|
|
|
|
with the exact same name specified here.
|
2020-08-31 14:12:32 +02:00
|
|
|
|
|
|
|
|
config SIM_UART2_NAME
|
2022-01-20 18:18:56 +01:00
|
|
|
string "UART port 2 name"
|
2020-08-31 14:12:32 +02:00
|
|
|
default "/dev/ttySIM2"
|
|
|
|
|
depends on SIM_UART_NUMBER >= 3
|
2022-01-20 18:18:56 +01:00
|
|
|
---help---
|
|
|
|
|
This is the name of the simulated UART port.
|
|
|
|
|
The port will be mounted in NuttX under this name.
|
2022-11-22 09:13:36 +01:00
|
|
|
|
2022-01-20 18:18:56 +01:00
|
|
|
A UART port must also exist on the host system
|
|
|
|
|
with the exact same name specified here.
|
2020-08-31 14:12:32 +02:00
|
|
|
|
|
|
|
|
config SIM_UART3_NAME
|
2022-01-20 18:18:56 +01:00
|
|
|
string "UART port 3 name"
|
2020-08-31 14:12:32 +02:00
|
|
|
default "/dev/ttySIM3"
|
|
|
|
|
depends on SIM_UART_NUMBER >= 4
|
2022-01-20 18:18:56 +01:00
|
|
|
---help---
|
|
|
|
|
This is the name of the simulated UART port.
|
|
|
|
|
The port will be mounted in NuttX under this name.
|
2022-11-22 09:13:36 +01:00
|
|
|
|
2022-01-20 18:18:56 +01:00
|
|
|
A UART port must also exist on the host system
|
|
|
|
|
with the exact same name specified here.
|
|
|
|
|
|
|
|
|
|
endmenu
|
2020-08-31 14:12:32 +02:00
|
|
|
|
2022-12-01 02:54:11 +01:00
|
|
|
config SIM_USB_DEV
|
|
|
|
|
bool "Linux USB Device"
|
|
|
|
|
select USBDEV
|
|
|
|
|
---help---
|
|
|
|
|
Build in support for simulated usb device
|
|
|
|
|
|
|
|
|
|
if SIM_USB_DEV
|
|
|
|
|
|
|
|
|
|
config SIM_USB_RAW_GADGET
|
|
|
|
|
bool "Simulated USB Raw Gadget Dev"
|
|
|
|
|
default n
|
|
|
|
|
depends on HOST_LINUX
|
|
|
|
|
---help---
|
2023-05-09 15:26:24 +02:00
|
|
|
Use USB Raw Gadget and Dummy HCD/UDC to set up virtual
|
|
|
|
|
USB Device and Host controller that connected to each
|
|
|
|
|
other inside the kernel.
|
2022-12-01 02:54:11 +01:00
|
|
|
|
2023-05-09 15:26:24 +02:00
|
|
|
Get Raw Gadget:
|
|
|
|
|
Get Raw Gadget code at https://github.com/xairy/raw-gadget.
|
2022-12-01 02:54:11 +01:00
|
|
|
|
2023-05-09 15:26:24 +02:00
|
|
|
Make Raw Gadget:
|
|
|
|
|
Run make in the raw_gadget and dummy_hcd directory. If raw_gadget
|
|
|
|
|
build fail, you need to check which register interface meets your
|
|
|
|
|
kenel version, usb_gadget_probe_driver or usb_gadget_register_driver.
|
2022-12-01 02:54:11 +01:00
|
|
|
|
2023-05-09 15:26:24 +02:00
|
|
|
Install Raw Gadget:
|
|
|
|
|
Run ./insmod.sh in the raw_gadget and dummy_hcd directory.
|
2022-12-01 02:54:11 +01:00
|
|
|
|
|
|
|
|
endif
|
|
|
|
|
|
2022-11-30 12:08:14 +01:00
|
|
|
config SIM_USB_HOST
|
|
|
|
|
bool "Linux USB Host"
|
|
|
|
|
select USBHOST
|
|
|
|
|
select USBHOST_HAVE_ASYNCH
|
|
|
|
|
select USBHOST_ASYNCH
|
|
|
|
|
---help---
|
|
|
|
|
Build in support for simulated usb host
|
|
|
|
|
|
|
|
|
|
if SIM_USB_HOST
|
|
|
|
|
|
|
|
|
|
config SIM_LIBUSB
|
|
|
|
|
bool "Simulated USB Host use libusb"
|
|
|
|
|
default n
|
|
|
|
|
depends on HOST_LINUX
|
|
|
|
|
---help---
|
2023-05-09 15:26:24 +02:00
|
|
|
Use libusb to set up virtual USB Host controller.
|
2022-11-30 12:08:14 +01:00
|
|
|
|
|
|
|
|
config SIM_USB_VID
|
|
|
|
|
hex "Simulated USB Dev VID"
|
|
|
|
|
default 0x18d1
|
|
|
|
|
|
|
|
|
|
config SIM_USB_PID
|
|
|
|
|
hex "Simulated USB Dev PID"
|
|
|
|
|
default 0x4e11
|
|
|
|
|
|
|
|
|
|
config SIM_USB_STACKSIZE
|
|
|
|
|
int "Simulated USB waiter stack size"
|
|
|
|
|
default 1024
|
|
|
|
|
|
|
|
|
|
config SIM_USB_PRIO
|
|
|
|
|
int "Simulated USB waiter task priority"
|
|
|
|
|
default 100
|
|
|
|
|
|
|
|
|
|
endif
|
|
|
|
|
|
2016-08-03 17:44:48 +02:00
|
|
|
endif # ARCH_SIM
|
