OrgZephyr/zephyr
OrgZephyr
/
zephyr
mirror of https://github.com/zephyrproject-rtos/zephyr.git
1
0
Fork 0
Code Issues Releases Wiki Activity
zephyr/samples/net/coap_client/prj.conf

13 lines
257 B
Plaintext
Raw Normal View History

samples/net: Add a sample for a CoAP client Change-Id: I17d88081eb719e55d97a5a034f6861e01ebb6a52 Signed-off-by: Vinicius Costa Gomes <vinicius.gomes@intel.com>
2016-06-18 06:21:33 +08:00
CONFIG_NETWORKING=y
iot/zoap: Port to the native stack This ports zoap to the native stack. Just for reference, and totally not scientific, here are the numbers using the old stack: $ size outdir/qemu_x86/zephyr.elf text data bss dec hex filename 34657 10316 16916 61889 f1c1 outdir/qemu_x86/zephyr.elf With yaip: $ size outdir/qemu_x86/zephyr.elf text data bss dec hex filename 30575 9148 6164 45887 b33f outdir/qemu_x86/zephyr.elf Jira: ZEP-818 Change-Id: I7992a3e2af7d419081ee5a64d7cc2d49fb628ead Signed-off-by: Vinicius Costa Gomes <vinicius.gomes@intel.com>
2016-09-22 22:23:16 +08:00
CONFIG_NET_IPV6=y
CONFIG_NET_LOG=y
CONFIG_NET_UDP=y
CONFIG_SYS_LOG=y
CONFIG_SYS_LOG_SHOW_COLOR=y
random: Restructure RANDOM Kconfig Restructure the RANDOM Kconfig to match the structure used in other drivers with a single top level menu. Move the true random number generators to appear first in the menu, with pseudo generators at the bottom. Do not present pseudo generators if a true random generator is presented. This change implies that tests, samples and applications that require the random driver interface must now select CONFIG_RANDOM_GENERATOR. In order for tests and samples to build (and run) on platforms that have no random driver it remains necessary to select the CONFIG_TEST_RANDOM_GENERATOR. Note that CONFIG_TEST_RANDOM_GENERATOR retains its original purpose of enabling a random driver that delivers non random numbers for the purpose of testing only. Change-Id: I2e28e44b4adf800e64a885aefe36a52da8aa455a Signed-off-by: Marcus Shawcroft <marcus.shawcroft@arm.com>
2016-11-29 04:39:43 +08:00
CONFIG_RANDOM_GENERATOR=y
iot/zoap: Port to the native stack This ports zoap to the native stack. Just for reference, and totally not scientific, here are the numbers using the old stack: $ size outdir/qemu_x86/zephyr.elf text data bss dec hex filename 34657 10316 16916 61889 f1c1 outdir/qemu_x86/zephyr.elf With yaip: $ size outdir/qemu_x86/zephyr.elf text data bss dec hex filename 30575 9148 6164 45887 b33f outdir/qemu_x86/zephyr.elf Jira: ZEP-818 Change-Id: I7992a3e2af7d419081ee5a64d7cc2d49fb628ead Signed-off-by: Vinicius Costa Gomes <vinicius.gomes@intel.com>
2016-09-22 22:23:16 +08:00
CONFIG_TEST_RANDOM_GENERATOR=y
net: samples: Modify zoap_client to new CoAP api's Signed-off-by: Ravi kumar Veeramally <ravikumar.veeramally@linux.intel.com>
2017-08-28 19:00:35 +08:00
CONFIG_COAP=y
net: samples: fix coap_client early unref packet issue 1. After calling sendto(), the packet will be unreferenced. Call coap_pending_cycle() to make sure the packet is referenced until we got the response from the peer or retransmission timeout. 2. In retransmit_request(), we rearrange the order to avoid the issue. 3. Remove IPv4 configuration for source code is expecting IPv6 4. Correct a typo in README.rst 5. Initialize the interface w/ IPv6 address Signed-off-by: Robert Chou <robert.ch.chou@acer.com>
2017-10-12 18:22:53 +08:00
CONFIG_NET_APP_SETTINGS=y
CONFIG_NET_APP_MY_IPV6_ADDR="2001:db8::2"