Re: [net] net samples not working?


최형준 <hj210.choi@...>
 

 

 

--------- Original Message ---------

Sender : 최형준 <hj210.choi@...> S5(책임)/책임/IoT Lab(S/W센터)/삼성전자

Date : 2017-02-09 09:54 (GMT+9)

Title : FW: Re: [Zephyr-devel] [net] net samples not working?

 

 

 

Hello Richard,

 

>the SLIP-TAP driver seems not to be working in qemu for cortex-m targets,too.

>I can not  get any network traffic between, either between to

>qemu_cortex_m3 targets nor to the PC.

 

>Has anyone tried networking in qemu with qemu_cortex_m3 target?

I did it and it works well even if it printed some error messages about “net_buf_get_reserve()”.

I used "echo_server" sample app. 

 

>I don't think that this is a configuration problem.

>The SLIP-TAP driver was disabled in the cortex_m3 defconfig.

>I enabled it, but no luck.

 

>Would be great to get some help on this!

 

I’ll share the conf file for qemu_cortex_m3 when I tested it.

Please make a file in your PC. (i.e.: zephyr/samples/net/echo_server/prj_qemu_cortex_m3.conf)

 

“prj_qemu_cortex_m3.conf” file has below configurations.

--------------------------------------------

CONFIG_NETWORKING=y

CONFIG_NET_IPV6=y

CONFIG_NET_IPV4=y

CONFIG_NET_UDP=y

CONFIG_NET_TCP=y

CONFIG_TEST_RANDOM_GENERATOR=y

CONFIG_NET_BUF_LOG=y

CONFIG_SYS_LOG_NET_BUF_LEVEL=2

CONFIG_NET_LOG=y

CONFIG_SYS_LOG_NET_LEVEL=2

CONFIG_NET_SLIP_TAP=y

CONFIG_SYS_LOG_SHOW_COLOR=y

CONFIG_INIT_STACKS=y

CONFIG_PRINTK=y

CONFIG_NET_STATISTICS=y

CONFIG_NET_NBUF_RX_COUNT=14

CONFIG_NET_NBUF_TX_COUNT=14

CONFIG_NET_NBUF_DATA_COUNT=30

CONFIG_NET_IF_UNICAST_IPV6_ADDR_COUNT=3

CONFIG_NET_IF_MCAST_IPV6_ADDR_COUNT=2

CONFIG_NET_MAX_CONTEXTS=10

 

CONFIG_NET_SHELL=y

 

CONFIG_NET_SAMPLES_IP_ADDRESSES=y

CONFIG_NET_SAMPLES_MY_IPV6_ADDR="2001:db8::1"

CONFIG_NET_SAMPLES_PEER_IPV6_ADDR="2001:db8::2"

CONFIG_NET_SAMPLES_MY_IPV4_ADDR="192.0.2.1"

CONFIG_NET_SAMPLES_PEER_IPV4_ADDR="192.0.2.2"

 

 

CONFIG_UART_PIPE_ON_DEV_NAME="UART_1"

-------------------------------------------- 

I think this problem is happened because of "CONFIG_UART_PIPE_ON_DEV_NAME".

You can check your echo_server app's connection status by “net shell” after running it.

(e.g.: > select net and conn)

 

Here is my test scenario.

a.     Run echo_server app on qemu_cortex_m3. (e.g.: make BOARD=qemu_cortex_m3 V=1 DEBUG=1 run)

b.     Send echo message on Host(Linux) (e.g.: $ echo HELLO | nc -u 192.0.2.1 4242)

 

I hope it'll help you.

 

Best Regards,

Hyungjun.

 

 

 

 

Join devel@lists.zephyrproject.org to automatically receive all group messages.