It's my full config, but to avoid the LittleVGL downloading, I remove
some graphic related config.
Here is my output with the latest mainline:
xiaoxiang@xiaoxiang-VirtualBox:~/nuttx/nuttx$ sudo ./nuttx
NuttShell (NSH) NuttX-8.2
nsh> ps
PID GROUP PRI POLICY TYPE NPX STATE EVENT SIGMASK
STACK USED FILLED COMMAND
0 0 0 FIFO Kthread N-- Ready 00000000
000000 000000 0.0% Idle Task
1 1 224 FIFO Kthread --- Waiting Signal 00000000
002032 000460 22.6% hpwork
2 1 100 FIFO Kthread --- Waiting Signal 00000000
002032 000924 45.4% lpwork
3 1 100 FIFO Task --- Running 00000000
004080 002096 51.3% init
5 4 100 FIFO Task --- Waiting Semaphore 00000010
002000 000804 40.2% Telnet daemon 0x56623690
6 4 100 FIFO Task --- Waiting Semaphore 00000010
002000 000804 40.2% Telnet daemon 0x56624510
7 4 100 FIFO Task --- Waiting Semaphore 00000000
002016 001828 90.6%! NTP daemon
nsh> ifconfig
eth0 Link encap:Ethernet HWaddr 42:09:36:15:9c:19 at UP
inet addr:10.0.2.18 DRaddr:10.0.2.2 Mask:255.255.255.0
inet6 addr: fe80::4009:36ff:fe15:9c19/64
inet6 DRaddr: ::/64
RX: Received Fragment Errors
00000014 00000000 00000000
IPv4 IPv6 ARP Dropped
00000003 00000010 00000001 00000000
TX: Queued Sent Errors Timeouts
00000012 00000012 00000000 00000000
Total Errors: 00000000
lo Link encap:Local Loopback at UP
inet addr:127.0.0.1 DRaddr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128
inet6 DRaddr: ::1/128
RX: Received Fragment Errors
00000000 00000000 00000000
IPv4 IPv6 ARP Dropped
00000000 00000000 00000000 00000000
TX: Queued Sent Errors Timeouts
00000000 00000000 00000000 00000000
Total Errors: 00000000
IPv4 IPv6 TCP UDP ICMP ICMPv6
Received 0003 0010 0000 0009 0000 000a
Dropped 0000 0000 0000 0000 0000 0008
IPv4 VHL: 0000 Frg: 0000
IPv6 VHL: 0000
Checksum 0000 ---- 0000 0000 ---- ----
TCP ACK: 0000 SYN: 0000
RST: 0000 0000
Type 0000 0000 ---- ---- 0000 0007
Sent 0006 000d 0000 0006 0000 000d
Rexmit ---- ---- 0000 ---- ---- ----
nsh> ping www.google.com
PING 216.58.200.68 56 bytes of data
56 bytes from 216.58.200.68: icmp_seq=0 time=240 ms
56 bytes from 216.58.200.68: icmp_seq=1 time=220 ms
56 bytes from 216.58.200.68: icmp_seq=2 time=210 ms
56 bytes from 216.58.200.68: icmp_seq=3 time=210 ms
56 bytes from 216.58.200.68: icmp_seq=4 time=210 ms
56 bytes from 216.58.200.68: icmp_seq=5 time=160 ms
56 bytes from 216.58.200.68: icmp_seq=6 time=120 ms
56 bytes from 216.58.200.68: icmp_seq=7 time=120 ms
56 bytes from 216.58.200.68: icmp_seq=8 time=260 ms
56 bytes from 216.58.200.68: icmp_seq=9 time=130 ms
10 packets transmitted, 10 received, 0% packet loss, time 10100 ms
On Tue, Feb 11, 2020 at 1:38 PM Adam Feuer <[email protected]> wrote:
>
> Thank you Xiang.
>
> I tried your config options, but the simulator still crashes when I do a
> ping.
>
> You didn't attach a whole config file– would you be willing to send one?
>
> cheers
> adam
>
> On Mon, Feb 10, 2020 at 8:50 PM Xiang Xiao <[email protected]>
> wrote:
>
> > Do you enable CONFIG_SIM_NET_BRIDGE?
> > To get the basic network, the below options are required:
> > CONFIG_NET=y
> >
> > CONFIG_NETINIT_DHCPC=y
> > CONFIG_NETUTILS_DHCPC=y
> >
> > CONFIG_NET_ICMP=y
> > CONFIG_NET_ICMP_SOCKET=y
> >
> > CONFIG_NET_UDP=y
> > CONFIG_NET_UDP_BINDTODEVICE=y
> >
> > CONFIG_SIM_NET_BRIDGE=y
> >
> > CONFIG_SYSTEM_PING=y
> >
> > IPv6 need more options:
> > CONFIG_NET_ICMPv6=y
> > CONFIG_NET_ICMPv6_AUTOCONF=y
> > CONFIG_NET_ICMPv6_SOCKET=y
> >
> > CONFIG_NET_IPv6=y
> >
> > CONFIG_SYSTEM_PING6=y
> >
> > Anyway, you can try the attached config which has more options to get
> > the better network.
> >
> >
> > On Tue, Feb 11, 2020 at 12:22 PM Adam Feuer <[email protected]> wrote:
> > >
> > > Xiang,
> > >
> > > Thanks for the tips! I tried to get this working, but I don't see any
> > > network interfaces on my nuttx system other than loopback.
> > >
> > > I ran the script on my Linux box, it created a nuttx0: interface with an
> > IP
> > > address. But on the nuttx simulator all I see is this:
> > >
> > > nsh> ifconfig
> > > > lo Link encap:Local Loopback at UP
> > > > inet addr:127.0.0.1 DRaddr:127.0.0.1 Mask:255.0.0.0
> > >
> > >
> > >
> > >
> > > Do you have a defconfig that I can run that will bring up NSH? Or any
> > > defconfig that will show the network is working?
> > >
> > > cheers
> > > adam
> > >
> > >
> > >
> > > On Mon, Feb 10, 2020 at 7:45 PM Xiang Xiao <[email protected]>
> > > wrote:
> > >
> > > > Adam, please follow this instruction if you want to connect the real
> > > > network instead loopback:
> > > >
> > > >
> > https://github.com/apache/incubator-nuttx/pull/249/commits/1b489449f790c2b4618df9133114bb05f0132e87
> > > > The setup is very simple, you don't need config any IP address
> > manually.
> > > >
> > > > Thanks
> > > > Xiang
> > > >
> > > > On Tue, Feb 11, 2020 at 2:23 AM Gregory Nutt <[email protected]>
> > wrote:
> > > > >
> > > > >
> > > > > > I'm trying to get the NuttX simulator working with TCP/IP
> > networking. I
> > > > > > used the sim:nsh defconfig as a base, then used "make menuconfig"
> > to
> > > > select
> > > > > > TCP/IP, ICMP, and ping commands.
> > > > > >
> > > > > > My host is Ubuntu 19.10 Eoan. I installed bridge-utils and
> > configured a
> > > > > > bridge device nuttx0 and gave it an IP address 10.0.1.1. From
> > linux I
> > > > can
> > > > > > ping the bridge.
> > > > > >
> > > > > > I can compile and run the simulator. Commands seem to work. I can
> > > > configure
> > > > > > the eth0 interface with IP address 10.0.1.2 and bring it up using
> > > > ifup. But
> > > > > > when I try to ping the bridge, the nuttx simulator immediately
> > exits
> > > > with
> > > > > > no messages.
> > > > > >
> > > > > > I checked the .config against the sim:nettest defconfig, and my
> > > > settings in
> > > > > > .config match that one.
> > > > > >
> > > > > > What am I doing wrong? How do I debug this?
> > > > >
> > > > > I don't use TCP/IP networking with the simulator. Perhaps Xiao Xiang
> > > > > will respond later.
> > > > >
> > > > > I am creating a simulator example that runs the TCP blaster example
> > > > > using the loopback 127.0.0.1 device. I will give that to you once I
> > > > > verify it.
> > > > >
> > > > >
> > > >
> > >
> > >
> > > --
> > > Adam Feuer <[email protected]>
> >
>
>
> --
> Adam Feuer <[email protected]>
