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/echo_server/prj_frdm_k64f_cc2520.conf

54 lines
1.1 KiB
Plaintext
Raw Normal View History

samples: net: echo apps: Add cc2520 configuration for frdm_k64f Common code found in samples/net/common App is built with: make BOARD=frdm_k64f CONF_FILE=prj_frdm_k64f_cc2520.conf Note: debug messages are enabled on many parts of the system, and these are killing the timings. So it's not unusual at all to see rx errors on cc2520 side. Without most of the debug, much less error will occur (if any when dbg is fully disabled). Change-Id: Ib6f0868c300652270661e72e80108804308164ab Signed-off-by: Tomasz Bursztyka <tomasz.bursztyka@linux.intel.com>
2016-12-01 19:03:41 +08:00
CONFIG_NETWORKING=y
CONFIG_TEST_RANDOM_GENERATOR=y
samples: net: Fix echo applications setting for 15.4 When zephyr receives a 15.4 frames it allocates 1 RX buf (nbuf) and 1 DATA (buf), and it gets queued on net stack for post processing. Problem: receiving a lot of frames is just completely nominal and very fast (timing is critical in radio, and the rx thread of the radio driver has a high priority, much higher than net stack's rx post processing). So guess what happens when CONFIG_NET_NBUF_RX_COUNT=10 though let's say 12 packets are coming in? The RX buffer pools gets empty and soon the system hangs on getting a newly allocated one. This proper CONFIG_NET_NBUF_RX_COUNT tweak fixes the issue, however some future work will reduce the need of so many RX meta buf: - l2's recv could be called right away at net_recv_data, before queuing the buffer for post-processing, but this could affects reception timing on radio side, which is critical. - An l2 pre-processing (in the middle of what current l2 recv does) could be implemented, it would be technology depenedent (aka: not mandatory on all l2) and could quickly decide what to do and at best drop the whole, or at least drop the RX meta buf (frag would still be kept). Let's see. Jira: ZEP-1427 Change-Id: Ic75b02efa36e35b450c02b3e6439a8d73f03f839 Signed-off-by: Tomasz Bursztyka <tomasz.bursztyka@linux.intel.com>
2016-12-16 22:01:55 +08:00
CONFIG_NET_NBUF_RX_COUNT=20
CONFIG_NET_NBUF_TX_COUNT=5
samples: net: echo apps: Add cc2520 configuration for frdm_k64f Common code found in samples/net/common App is built with: make BOARD=frdm_k64f CONF_FILE=prj_frdm_k64f_cc2520.conf Note: debug messages are enabled on many parts of the system, and these are killing the timings. So it's not unusual at all to see rx errors on cc2520 side. Without most of the debug, much less error will occur (if any when dbg is fully disabled). Change-Id: Ib6f0868c300652270661e72e80108804308164ab Signed-off-by: Tomasz Bursztyka <tomasz.bursztyka@linux.intel.com>
2016-12-01 19:03:41 +08:00
CONFIG_NET_NBUF_DATA_COUNT=40
CONFIG_NET_IPV4=n
CONFIG_NET_IPV6=y
CONFIG_NET_IPV6_RA_RDNSS=y
CONFIG_NET_IF_UNICAST_IPV6_ADDR_COUNT=2
CONFIG_NET_6LO=y
CONFIG_NET_DEBUG_6LO=n
CONFIG_NET_LOG=y
CONFIG_SYS_LOG_SHOW_COLOR=y
CONFIG_INIT_STACKS=y
CONFIG_PRINTK=y
CONFIG_NET_DEBUG_CORE=y
CONFIG_NET_DEBUG_IPV6_NBR_CACHE=y
CONFIG_NET_DEBUG_IPV6=y
CONFIG_NET_DEBUG_CONTEXT=y
CONFIG_NET_DEBUG_NET_BUF=n
CONFIG_NET_DEBUG_UTILS=n
CONFIG_NET_DEBUG_IF=n
CONFIG_NET_DEBUG_ICMPV6=y
CONFIG_NET_DEBUG_CONN=n
CONFIG_NET_STATISTICS=y
net: statistics: Provide specific Kconfig options This will help to track only what's wanted (ipv6, tpc, udp, else...) if needed to. Change-Id: I5c2e5e582db629b5d0e1cd98004f693c50f532a4 Signed-off-by: Tomasz Bursztyka <tomasz.bursztyka@linux.intel.com>
2016-12-13 22:19:28 +08:00
CONFIG_NET_STATISTICS_PERIODIC_OUTPUT=y
samples: net: echo apps: Add cc2520 configuration for frdm_k64f Common code found in samples/net/common App is built with: make BOARD=frdm_k64f CONF_FILE=prj_frdm_k64f_cc2520.conf Note: debug messages are enabled on many parts of the system, and these are killing the timings. So it's not unusual at all to see rx errors on cc2520 side. Without most of the debug, much less error will occur (if any when dbg is fully disabled). Change-Id: Ib6f0868c300652270661e72e80108804308164ab Signed-off-by: Tomasz Bursztyka <tomasz.bursztyka@linux.intel.com>
2016-12-01 19:03:41 +08:00
CONFIG_NET_L2_IEEE802154=y
CONFIG_NET_DEBUG_L2_IEEE802154=y
CONFIG_NET_L2_IEEE802154_ORFD=y
CONFIG_NET_L2_IEEE802154_FRAGMENT=y
CONFIG_NET_DEBUG_L2_IEEE802154_FRAGMENT=n
CONFIG_GPIO=y
CONFIG_SPI=y
CONFIG_SPI_0=y
samples: net: Increase spi log level Change-Id: Ic067a93c1e24c12c7e531b1df590be252cd2531b Signed-off-by: Maureen Helm <maureen.helm@nxp.com>
2016-12-17 04:43:12 +08:00
CONFIG_SYS_LOG_SPI_LEVEL=1
samples: net: echo apps: Add cc2520 configuration for frdm_k64f Common code found in samples/net/common App is built with: make BOARD=frdm_k64f CONF_FILE=prj_frdm_k64f_cc2520.conf Note: debug messages are enabled on many parts of the system, and these are killing the timings. So it's not unusual at all to see rx errors on cc2520 side. Without most of the debug, much less error will occur (if any when dbg is fully disabled). Change-Id: Ib6f0868c300652270661e72e80108804308164ab Signed-off-by: Tomasz Bursztyka <tomasz.bursztyka@linux.intel.com>
2016-12-01 19:03:41 +08:00
CONFIG_TI_CC2520=y
CONFIG_TI_CC2520_AUTO_ACK=y
ieee802154: conf: add common log level Add common log level for all IEEE802154 drivers. Change-Id: If92c96b14e630d4482aadf9cacb25662d6663399 Signed-off-by: Johann Fischer <j.fischer@phytec.de>
2017-01-10 21:24:01 +08:00
CONFIG_SYS_LOG_IEEE802154_DRIVER_LEVEL=1
samples: net: echo apps: Add cc2520 configuration for frdm_k64f Common code found in samples/net/common App is built with: make BOARD=frdm_k64f CONF_FILE=prj_frdm_k64f_cc2520.conf Note: debug messages are enabled on many parts of the system, and these are killing the timings. So it's not unusual at all to see rx errors on cc2520 side. Without most of the debug, much less error will occur (if any when dbg is fully disabled). Change-Id: Ib6f0868c300652270661e72e80108804308164ab Signed-off-by: Tomasz Bursztyka <tomasz.bursztyka@linux.intel.com>
2016-12-01 19:03:41 +08:00
CONFIG_TI_CC2520_SPI_DRV_NAME="SPI_0"
CONFIG_TI_CC2520_SPI_FREQ=4000000
CONFIG_TI_CC2520_SPI_SLAVE=0
CONFIG_NET_SAMPLES_IP_ADDRESSES=y
CONFIG_NET_SAMPLES_MY_IPV6_ADDR="2001:db8::2"