Which version of Zephyr are you trying to build? Run ‘git branch’ to find out. The newer versions of Zephyr require Zephyr SDK newer than v0.11.1 Also did you do a ‘west update’? this is required to p

Thanks Charles. Bug #26939 filed…. Let me know if there is any other info I can provide. https://github.com/zephyrproject-rtos/zephyr/issues/26939 Lawrence King Principal Developer +1(416)627-7302

Hi Charles, I tried your suggestion, unfortunately it doesn’t help. Every dts that uses mcumgr, also has the console on the same port, there is no existing board that routes the mcumgr to a different

Dear All: I am trying to setup mcumgr to allow code download over a serial port and use the shell. In this case I have 2 serial ports in play. The first serial port is where printk() sends messages. I

Hi Charles: This just my personal opinion on the subject. Two approvals is the right thing to do and what the TSC approved earlier this year. BUT, if the second +1 is just a rubber stamp approval of t

I experienced the same ABI issue linking an existing library when moving from Zephyr v2.2.0 to Zephyr v2.3.0. In addition to the suggestions Charles made: CONFIG_FP_SOFTABI=y or CONFIG_FP_HARDABI=y in

Hi Simon: Which revision of Zephyr are you using? On Zephyr v2.1.0 I had no problems, but with Zephyr 2.2.0 I am having problems. I have filed a bug for this: https://github.com/zephyrproject-rtos/zep

#hci

HI Vince, There is no ‘official’ SPI specification, it is a defacto standard, and chip manufacturers can implement it any way they want. Generally most peripherals don’t care what level the data pin i

Hi Vince: 2) I am not sure what you mean when you say “the voltage on the MOSI signal is unstable”. The Oscilloscope traces below look fine, however, the probes on your oscilloscope have not been prop

Hi Teijo I’m not sure if this code fragment solves your problem /** @brief LE connection parameter update request. * * This callback notifies the application that a remote device * is requesting to up

Dear All: I have finally gotten around to writing a driver for the lsm9ds1 sensor. Boy have I learned a lot about the core of the Zephyr kernel and sensor sub-system, and in general I really like it.

Dear All: I have finally gotten around to writing a driver for the lsm9ds1 sensor. As I look through the sensor driver examples, both the drivers, and the sample user land code I see a pattern. Sensor

I am not sure how much display you need, but a good board to get started with Zephyr that has a display is Electronut Labs Papyr Lawrence King Principal Developer Irdeto +1(416)627-7302

Adding devel@... to the email address. Lawrence King Principal Developer +1(416)627-7302

This is what I have my prj.conf, yours might be different, an I’m not sure what I have is 100% correct: # BT settings CONFIG_BT=y CONFIG_BT_SMP=y CONFIG_BT_SIGNING=y CONFIG_BT_BONDABLE=y CONFIG_BT_PER

I had the same issue when moving forward kernel versions. The API for At the top level get rid of the bt_gatt_ccc_cfg variables (my code has two characteristics) : #ifndef NEW_BT_STACK static struct b

Hi Mayank: I had a similar requirement, also without a button on the same Nordic chip. I simply copied this file into my project, and called smp_svr_init() from my main() after bluetooth was up and ru

#ble #hci #nrf52480 #uart

The function k_uptime_get() returns time in milliseconds, since this is a 64-bit number (63-bits if you use signed math), it will almost never wrap (well, once every 292 million years, but as far as I

I’m with Charles. I had to add this to my .bashrc export PATH=~/.local/bin:$PATH Once I did this everything is good. Lawrence King Principal Developer +1(416)627-7302