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/mqtt_publisher/prj_96b_nitrogen.conf

67 lines
1.4 KiB
Plaintext
Raw Normal View History

net/mqtt: Add BT support to MQTT publisher sample Change-Id: I56d54c3550a530bf250210e939840e7c7e89c5d9 Signed-off-by: Jorge Ramirez-Ortiz <jorge.ramirez-ortiz@linaro.org>
2017-02-03 20:45:11 +08:00
CONFIG_INIT_STACKS=y
CONFIG_NETWORKING=y
CONFIG_NET_TCP=y
net: udp: Remove NET_UDP_HDR() macro and direct access to net_buf Remove NET_UDP_HDR() macro as we cannot safely access UDP header via it if the network packet header spans over multiple net_buf fragments. Fixed also the UDP unit tests so that they pass correctly. Signed-off-by: Jukka Rissanen <jukka.rissanen@linux.intel.com>
2017-06-30 22:46:01 +08:00
CONFIG_NET_UDP=y
net/mqtt: Add BT support to MQTT publisher sample Change-Id: I56d54c3550a530bf250210e939840e7c7e89c5d9 Signed-off-by: Jorge Ramirez-Ortiz <jorge.ramirez-ortiz@linaro.org>
2017-02-03 20:45:11 +08:00
CONFIG_NET_ARP=y
Bluetooth: Kconfig: Rename CONFIG_BLUETOOTH_* to CONFIG_BT_* The API name space for Bluetooth is bt_* and BT_* so it makes sense to align the Kconfig name space with this. The additional benefit is that this also makes the names shorter. It is also in line with what Linux uses for Bluetooth Kconfig entries. Some Bluetooth-related Networking Kconfig defines are renamed as well in order to be consistent, such as NET_L2_BLUETOOTH. Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2017-08-09 14:21:11 +08:00
CONFIG_NET_L2_BT=y
CONFIG_NET_L2_BT_SEC_LEVEL=1
net/mqtt: Add BT support to MQTT publisher sample Change-Id: I56d54c3550a530bf250210e939840e7c7e89c5d9 Signed-off-by: Jorge Ramirez-Ortiz <jorge.ramirez-ortiz@linaro.org>
2017-02-03 20:45:11 +08:00
CONFIG_NET_LOG=y
CONFIG_NET_IPV6_RA_RDNSS=y
CONFIG_NET_IPV4=n
CONFIG_NET_IPV6=y
CONFIG_NET_IPV6_MAX_NEIGHBORS=8
CONFIG_NET_MAX_CONTEXTS=5
CONFIG_NET_SHELL=y
net: Renaming net nbuf API to net pkt API There have been long lasting confusion between net_buf and net_nbuf. While the first is actually a buffer, the second one is not. It's a network buffer descriptor. More precisely it provides meta data about a network packet, and holds the chain of buffer fragments made of net_buf. Thus renaming net_nbuf to net_pkt and all names around it as well (function, Kconfig option, ..). Though net_pkt if the new name, it still inherit its logic from net_buf. ' This patch is the first of a serie that will separate completely net_pkt from net_buf. Change-Id: Iecb32d2a0d8f4647692e5328e54b5c35454194cd Signed-off-by: Tomasz Bursztyka <tomasz.bursztyka@linux.intel.com>
2017-04-03 23:14:35 +08:00
CONFIG_NET_PKT_RX_COUNT=16
CONFIG_NET_PKT_TX_COUNT=16
CONFIG_NET_BUF_DATA_SIZE=256
CONFIG_NET_BUF_RX_COUNT=15
CONFIG_NET_BUF_TX_COUNT=15
net/mqtt: Add BT support to MQTT publisher sample Change-Id: I56d54c3550a530bf250210e939840e7c7e89c5d9 Signed-off-by: Jorge Ramirez-Ortiz <jorge.ramirez-ortiz@linaro.org>
2017-02-03 20:45:11 +08:00
net: Rename Kconfig.samples and its main option for future changes s/SAMPLES/APP for name shortening. Applying the change where relevant. Not only IP addresse will be available as samples settings there but also IEEE 802.15.4 channel, pan_id, and more for instance. Change-Id: I05dd24989bd0c804d9588092d67044a3e063bc88 Signed-off-by: Tomasz Bursztyka <tomasz.bursztyka@linux.intel.com>
2017-03-15 23:01:47 +08:00
CONFIG_NET_APP_SETTINGS=y
CONFIG_NET_APP_MY_IPV6_ADDR="2001:db8::1"
CONFIG_NET_APP_PEER_IPV6_ADDR="2001:db8::2"
Bluetooth: Kconfig: Rename CONFIG_BLUETOOTH_* to CONFIG_BT_* The API name space for Bluetooth is bt_* and BT_* so it makes sense to align the Kconfig name space with this. The additional benefit is that this also makes the names shorter. It is also in line with what Linux uses for Bluetooth Kconfig entries. Some Bluetooth-related Networking Kconfig defines are renamed as well in order to be consistent, such as NET_L2_BLUETOOTH. Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2017-08-09 14:21:11 +08:00
CONFIG_NET_APP_BT_NODE=y
net/mqtt: Add BT support to MQTT publisher sample Change-Id: I56d54c3550a530bf250210e939840e7c7e89c5d9 Signed-off-by: Jorge Ramirez-Ortiz <jorge.ramirez-ortiz@linaro.org>
2017-02-03 20:45:11 +08:00
net: Rename Kconfig.samples and its main option for future changes s/SAMPLES/APP for name shortening. Applying the change where relevant. Not only IP addresse will be available as samples settings there but also IEEE 802.15.4 channel, pan_id, and more for instance. Change-Id: I05dd24989bd0c804d9588092d67044a3e063bc88 Signed-off-by: Tomasz Bursztyka <tomasz.bursztyka@linux.intel.com>
2017-03-15 23:01:47 +08:00
CONFIG_NET_APP_MY_IPV4_ADDR="192.168.1.101"
CONFIG_NET_APP_PEER_IPV4_ADDR="192.168.1.10"
net/mqtt: Add BT support to MQTT publisher sample Change-Id: I56d54c3550a530bf250210e939840e7c7e89c5d9 Signed-off-by: Jorge Ramirez-Ortiz <jorge.ramirez-ortiz@linaro.org>
2017-02-03 20:45:11 +08:00
CONFIG_NET_IF_UNICAST_IPV6_ADDR_COUNT=3
CONFIG_NET_IF_MCAST_IPV6_ADDR_COUNT=3
CONFIG_PRINTK=y
CONFIG_MQTT_LIB=y
CONFIG_MAIN_STACK_SIZE=2048
drivers: Rename `random` to `entropy` This should clear up some of the confusion with random number generators and drivers that obtain entropy from the hardware. Also, many hardware number generators have limited bandwidth, so it's natural for their output to be only used for seeding a random number generator. Signed-off-by: Leandro Pereira <leandro.pereira@intel.com>
2017-10-14 07:30:55 +08:00
CONFIG_ENTROPY_GENERATOR=y
net/mqtt: Add BT support to MQTT publisher sample Change-Id: I56d54c3550a530bf250210e939840e7c7e89c5d9 Signed-off-by: Jorge Ramirez-Ortiz <jorge.ramirez-ortiz@linaro.org>
2017-02-03 20:45:11 +08:00
CONFIG_TEST_RANDOM_GENERATOR=y
CONFIG_TIMER_RANDOM_GENERATOR=y
Bluetooth: Kconfig: Rename CONFIG_BLUETOOTH_* to CONFIG_BT_* The API name space for Bluetooth is bt_* and BT_* so it makes sense to align the Kconfig name space with this. The additional benefit is that this also makes the names shorter. It is also in line with what Linux uses for Bluetooth Kconfig entries. Some Bluetooth-related Networking Kconfig defines are renamed as well in order to be consistent, such as NET_L2_BLUETOOTH. Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2017-08-09 14:21:11 +08:00
CONFIG_BT_RX_STACK_SIZE=1024
CONFIG_BT_DEVICE_NAME="Zephyr"
net/mqtt: Add BT support to MQTT publisher sample Change-Id: I56d54c3550a530bf250210e939840e7c7e89c5d9 Signed-off-by: Jorge Ramirez-Ortiz <jorge.ramirez-ortiz@linaro.org>
2017-02-03 20:45:11 +08:00
samples: net/mqtt_publisher: Explicitly disable BT_TINYCRYPT_ECC This app will not fit in the 96b_nitrogen board with ECC enabled. "real-ld: region `SRAM' overflowed by 68 bytes". Disable the feature explicitly since a subsequent patch will auto-enable it for all combined Bluetooth Host-Controller builds. Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2018-07-31 17:27:51 +08:00
# The app wont fit in RAM with ECC enabled
CONFIG_BT_TINYCRYPT_ECC=n
Bluetooth: Kconfig: Rename CONFIG_BLUETOOTH_* to CONFIG_BT_* The API name space for Bluetooth is bt_* and BT_* so it makes sense to align the Kconfig name space with this. The additional benefit is that this also makes the names shorter. It is also in line with what Linux uses for Bluetooth Kconfig entries. Some Bluetooth-related Networking Kconfig defines are renamed as well in order to be consistent, such as NET_L2_BLUETOOTH. Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2017-08-09 14:21:11 +08:00
CONFIG_BT_L2CAP_TX_BUF_COUNT=3
CONFIG_BT_L2CAP_TX_MTU=65
net/mqtt: Add BT support to MQTT publisher sample Change-Id: I56d54c3550a530bf250210e939840e7c7e89c5d9 Signed-off-by: Jorge Ramirez-Ortiz <jorge.ramirez-ortiz@linaro.org>
2017-02-03 20:45:11 +08:00
Bluetooth: Kconfig: Rename CONFIG_BLUETOOTH_* to CONFIG_BT_* The API name space for Bluetooth is bt_* and BT_* so it makes sense to align the Kconfig name space with this. The additional benefit is that this also makes the names shorter. It is also in line with what Linux uses for Bluetooth Kconfig entries. Some Bluetooth-related Networking Kconfig defines are renamed as well in order to be consistent, such as NET_L2_BLUETOOTH. Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2017-08-09 14:21:11 +08:00
CONFIG_BT_HCI_TX_STACK_SIZE=640
CONFIG_BT_HCI_HOST=y
CONFIG_BT_RECV_IS_RX_THREAD=y
CONFIG_BT_HCI_CMD_COUNT=2
CONFIG_BT_RX_BUF_COUNT=20
CONFIG_BT_RX_BUF_LEN=1024
CONFIG_BT_CONN=y
CONFIG_BT_SIGNING=y
CONFIG_BT_L2CAP_DYNAMIC_CHANNEL=y
CONFIG_BT_DEBUG_LOG=y
net/mqtt: Add BT support to MQTT publisher sample Change-Id: I56d54c3550a530bf250210e939840e7c7e89c5d9 Signed-off-by: Jorge Ramirez-Ortiz <jorge.ramirez-ortiz@linaro.org>
2017-02-03 20:45:11 +08:00
CONFIG_CONSOLE_SHELL=y
CONFIG_CONSOLE_SHELL_STACKSIZE=2000
CONFIG_CONSOLE_SHELL_MAX_CMD_QUEUED=3