users@lists.zephyrproject.org

Re: Making use of Hardware debugger available with nrf52840 preview development kit

Hello all, I got Ozone working for nrf52840 PDK. Thanks a lot. -- Warm regards, Ashish Shukla Jr. Embedded Engineer Research & Development www.corvi.com Please consider the environment before

By ashish.shukla@corvi.com <ashish.shukla@...> · #391 ·

Re: Making use of Hardware debugger available with nrf52840 preview development kit

Hi there, Once the PR below is merged, you will be able to use GDB by simply typing “make debug” if you prefer it to Ozone: https://github.com/zephyrproject-rtos/zephyr/pull/5435

By Carles Cufi · #390 ·

Re: Making use of Hardware debugger available with nrf52840 preview development kit

Hi there, You can use both GDB and Ozone using the built-in Segger chip. Take a look at this page: http://docs.zephyrproject.org/tools/nordic_segger.html#nordic-segger Regards,

By Carles Cufi · #389 ·

Re: Sending notification with MTU size more than 23 bytes - BLE

Hello Johan, Many thanks for the reply. I tried changing the configuration for CONFIG_BT_L2CAP_TX_MTU to my required size (30 bytes to test) and used the nRF connect app as client on my

By dhguja@gmail.com · #388 ·

Making use of Hardware debugger available with nrf52840 preview development kit

Hi ! I've got nrf52840 pdk and I'm working with blue tooth mesh developed by zephyr community. I want to make use of hardware debugger available with development kit, i.e. I should be able see

By ashish.shukla@corvi.com <ashish.shukla@...> · #387 ·

Re: Sending notification with MTU size more than 23 bytes - BLE

Hi DJ, The maxium ATT MTU Zephyr will use is based on the values you've given to CONFIG_BT_L2CAP_TX_MTU and CONFIG_BT_L2CAP_RX_MTU. Additionally, there's a runtime API bt_gatt_exchange_mtu() that can

By Johan Hedberg · #386 ·

Re: [Zephyr-devel] I2C driver for nrf52840 not being compiled

Hi, Thanks, it compiles and run successfully. -- Warm regards, Ashish Shukla Jr. Embedded Engineer Research & Development www.corvi.com Please consider the environment before printing this e-mail

By ashish.shukla@corvi.com <ashish.shukla@...> · #385 ·

Confusion about Zephyr ADC API semantics

Hi, I've been reading through the ADC API, its users, and its test cases, and I'm confused about the semantics of struct adc_seq_entry, in particular the field named "buffer". The API docs are vague

By Marti Bolivar · #384 ·

CMSIS linking problem

Hi all! Im having a problem when linking my app. It's not linking to cmsis libraries. ``` src/libs/kalman.c:7: undefined reference to `arm_mat_init_f32' ``` ``` src/libs/kalman.c 1

By Inaki Malerba <ina@...> · #383 ·

Sending notification with MTU size more than 23 bytes - BLE

Hello all, I have a question regarding handling MTU size more than 23 bytes during notification. I have a custom service on a peripheral device app to which client app(lets say android app) will

By dhguja@gmail.com · #382 ·

Re: per app device tree overlay

You should be able to use an device tree overlap file. There’s examples in ./samples/bluetooth/hci_uart. The overlay file needs to be named BOARD_NAME.overlay. I opened up Issue #5408 in GitHub to

By Kumar Gala · #380 ·

per app device tree overlay

Hi! I haven’t found any Documentation, how to make changes to a boards device tree from inside my app. I’m neither really familiar with device tree or cmake, so looking thorugh the source

By Daniel Wagenknecht · #379 ·

Re: [Zephyr-devel] I2C driver for nrf52840 not being compiled

Hi. For nRF52840 I2C driver is zephyr. All its option are in general i2c Kconfig file. I attached configuration I had used to compile example you mentioned. BR Andrzej

By Puzdrowski, Andrzej <Andrzej.Puzdrowski@...> · #381 ·

Re: I2C driver for nrf52840 not being compiled

Hi Ashish, Did you select CONFIG_I2C_NRF5 in menuconfig or set CONFIG_I2C_NRF5=y in prj.conf file? Also, you need to set CONFIG_I2C_NRF5_GPIO_SCA_PIN , CONFIG_I2C_NRF5_GPIO_SCA_PIN ,CONFIG_I2C_0=y,

By Chettimada, Vinayak Kariappa · #378 ·

I2C driver for nrf52840 not being compiled

Hello everyone ! I'm trying to interface an I2C device with nrf52840 controller. When I look into ../zephyr/drivers/i2c directory, there is no Kconfig file corresponding to i2c_nrf5.c Again in

By ashish.shukla@corvi.com <ashish.shukla@...> · #377 ·

Re: [Zephyr-devel] Zephyr IPSP sample crashes and ble controller crashes (IPv6 over BLE)

Hi Priyanka, Upgrading is recommended since the IPSP implementation on Linux was broken when generating the IID, though we are preparing to deprecate the debugfs interface as that was never meant for

By Luiz Augusto von Dentz · #376 ·

Re: [Zephyr-devel] Zephyr IPSP sample crashes and ble controller crashes (IPv6 over BLE)

Hi Luiz I am on $ uname -r 4.4.0-98-generic Linux 4.4.0-98-generic #121-Ubuntu SMP Tue Oct 10 14:24:03 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux So if I enable ZEP1656 config option kconifg option in

By Priyanka · #375 ·

Re: [Zephyr-devel] Zephyr IPSP sample crashes and ble controller crashes (IPv6 over BLE)

Hi Priyanka, Current IPSP configuration only works with Linux kernel version 4.12 or later, zephyr 1.9 used to have the infamous ZEP1656 config option set which has been removed in 1.10. -- Luiz

By Luiz Augusto von Dentz · #374 ·

Re: [Zephyr-devel] Zephyr IPSP sample crashes and ble controller crashes (IPv6 over BLE)

Hi Luiz The HCI firmware hci_blackbox is from KW41Z SDK2.2. BLE controller remains connected and bt0 does not go down if most of the debug logs are disabled in prj.conf As with debug logs enabled, it

By Priyanka · #373 ·

Re: I2C and adc support for nRF5

Hi Ashish, The board name is nrf52840_pca10056 That works on my boards. Steve

By Steve Brown · #372 ·

Messages