Пікірлер
@bittesh
@bittesh 3 күн бұрын
Very Nice n informative video
@user-mz8ro5bm8b
@user-mz8ro5bm8b 21 күн бұрын
Could anyone clarify me on how to install sdk from nrf connect extension and also regarding how to flash the nrf device
@blankrofl
@blankrofl 24 күн бұрын
Did you ever find a way to upload code without entering bootloader mode every time? The button is so small it's a deterrent to use this chip in my projects.
@wsniot
@wsniot 24 күн бұрын
Not really. You could try to solder a bigger switch to reset on the downer side and GND. Or using a J-Link programmer, but also not more comfortable. Or you are just using another dongle like from Nordic or MDK instead with the ner52840. MDK support also uf2 Bootloader as i remember.
@edgarwcl
@edgarwcl Ай бұрын
Right, honestly, I am a hardware engineer and also would like to understand the deep therories in every functional diagram a long time. This video really inspir me a lot. thank you! I also also pricking up the Nordic nRF52840 :)
@patil29066
@patil29066 Ай бұрын
Hello Sir, Is it possible to get the address of the connected centralized device into the peripheral device and print it using any services?
@user-yb9yr2wu8v
@user-yb9yr2wu8v Ай бұрын
没有中文字幕,看起来,太费劲了.
@carloseduardomayerdeolivei2913
@carloseduardomayerdeolivei2913 Ай бұрын
Just perfect! Thank you
@michaeldalby1971
@michaeldalby1971 Ай бұрын
Hi Markus, This is a great and informative video for an introduction into the Zephyr I2C implementation. I have a quick question if I may; You described a method to connect to an I2C device if you don't have an inbuilt library and a method if you do have access to a library. My question is, how do you mix the two if you have for example a sensor on your I2C bus for which you need to write your own interface driver and another sensor on the I2C bus (at a different I2C address) that has a Zephyr driver? is it possible to use both I2C drivers methods on the same port? Cheers Michael
@wsniot
@wsniot Ай бұрын
Thanks for the nice feedback. Yes, should be no problem. The access to the I2C-bus is not exclusive. At the end the driver uses the same instruction like writing it manually with the Zephyr functions.
@carloseduardomayerdeolivei2913
@carloseduardomayerdeolivei2913 Ай бұрын
Thanks a lot for your videos!!
@jakoblepur9692
@jakoblepur9692 Ай бұрын
I had an issue with my BMP280 sensor that the value printed out would not change. For anyone else that this might help I had looked in the driver code and the datasheet and figured out that I had to turn the device from sleep mode to normal mode (or forced). I did this by adding these lines: #define BME280_TEMP_OVER (3 << 5) //3.3.2 #define BME280_PRESS_OVER (3 << 2) //normal power. 3.3.1 of datasheet #define BME280_MODE 0x03 //normal mode #define BME280_CTRL_MEAS_VAL (BME280_PRESS_OVER | BME280_TEMP_OVER | BME280_MODE) err = i2c_reg_write_byte(i2c_dev, BMP280_I2C_ADDRESS, 0xF4, BME280_CTRL_MEAS_VAL); where 0xF4 is the ctrl_meas register. Thanks for the videos they are really helping with learning zephyr RTOS!
@patil29066
@patil29066 Ай бұрын
This video is helpful. How can I connect my BLE peripheral to only a specific Central device?
@abelashenafi6291
@abelashenafi6291 2 ай бұрын
Thanks for this amazint content. What you are doing is really really really amazing. Danke
@DriesMoerman
@DriesMoerman 2 ай бұрын
Hi Markus. I've been following your process with the dk version with a Pi4 and been able to fix some of the issues on the way. Now I'm getting stuck at the script for bootloader "Detecting C compiler ABI info - failed" Pardon my ignorance, but I can't seem to find a way for cmake to recognize the compiler. Would you be able to point me in the right direction?
@adityavarma2138
@adityavarma2138 2 ай бұрын
Awesome sir!! Thanks for sharing..🙏
@SagarBhavar
@SagarBhavar 2 ай бұрын
Done with same setup however not able to sniff zigbee communication - getting only broadcast beacon requests ............. am I missing something ?
@wsniot
@wsniot 2 ай бұрын
You are probably missing something. The stick is an IEEE 802.15.4 sniffer. If you have set the correct channel, you will also receive ZigBee packets since IEEE 802.15.4 are the two downer layer from ZigBee. Is your ZigBee network encrypted? Have you set the network key in Wireshark? At least you should see the IEEE 802.15.4 part from the ZigBee-pakets
@RaghavParwal-ko5ot
@RaghavParwal-ko5ot 2 ай бұрын
Hello @wsniot, I am not able to read uart via putty with port ComX. I seen it inside Device Manager -> Ports (COM & LPT)
@user-pe2sc2ur2o
@user-pe2sc2ur2o 2 ай бұрын
Hi, this video is very useful, thank you for sharing. I try with nRF52840 it is working but, when l try with nRF52832 it can't build. is the nRF52832 not support battery services? What is the problem?
@wsniot
@wsniot 2 ай бұрын
The BAS support is normaly only a software point of view. If it canont be build with the nRF52832, I guess there is another problem. Maybe not enough memory.
@thatcringingdude7920
@thatcringingdude7920 2 ай бұрын
How could I implement a GATT client? Any examples anyone can point me to?
@user-ms3id7jv7v
@user-ms3id7jv7v 2 ай бұрын
why printk and rtt dont working with out sleep at least 1ms?
@pmull252
@pmull252 2 ай бұрын
Thanks for this. Can you please explain how the passcide or QR code gets generated? Can this be anything? I read somewhere that the QR code gets generated from the Vendor and product ID. How does the commissioner then check that this passcode or QR code is something valid that makes sense?
@violinsheetmusicblog
@violinsheetmusicblog 2 ай бұрын
So close to working, but I keep getting the following error when I try to install the blinky application "Access protection is enabled, can't read device version." I have two NRF53 DK boards and it does the same thing on both, not sure why
@wsniot
@wsniot 2 ай бұрын
Strange. Had newer problems with access protection. Did you maybe flash a programm where the FLAGS for access protection are set? You can try to setting the access protection to disable with an ERASEALL. See also: developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/security/ap_protect.html
@violinsheetmusicblog
@violinsheetmusicblog 2 ай бұрын
@@wsniot I figured it out. In addition to running eraseall and recover, I had the wrong board configuration selected and I finally found the right one! All works now, thanks!
@raniaamara6715
@raniaamara6715 2 ай бұрын
hi I am using nrf52840dk- nrf52840 board to interface the IMU Sensor lsm6dsox using I2C using nrf connect sdk for vs code. But I am facing error: i'm using the code in ncs/samples/sensor/lsm6dso here is prj.conf: CONFIG_STDOUT_CONSOLE=y CONFIG_I2C=y CONFIG_SENSOR=y CONFIG_CBPRINTF_FP_SUPPORT=y CONFIG_LSM6DSO_TRIGGER_GLOBAL_THREAD=y CONFIG_LSM6DSO=y here is thr overlay file: &pinctrl { i2c0_default: i2c0_default { group1 { psels = <NRF_PSEL(TWIM_SDA, 0, 26)>, <NRF_PSEL(TWIM_SCL, 0, 27)>; bias-pull-up; }; }; i2c0_sleep: i2c0_sleep { group1 { psels = <NRF_PSEL(TWIM_SDA, 0, 26)>, <NRF_PSEL(TWIM_SCL, 0, 27)>; low-power-enable; }; }; }; &i2c0 { compatible = "nordic,nrf-twi"; status = "okay"; pinctrl-0 = <&i2c0_default>; pinctrl-1 = <&i2c0_sleep>; pinctrl-names = "default", "sleep"; label = "I2C_0"; clock-frequency = <I2C_BITRATE_STANDARD>; lsm6dso@6a { compatible = "st,lsm6dso"; reg = <0x6a>; }; }; the probleme is when i flash my code this the output : *** Booting nRF Connect SDK v2.5.2 *** Testing LSM6DSO sensor in trigger mode. Could not set sensor type and channel can you please help me
@wsniot
@wsniot 2 ай бұрын
I dont have an lsm6dso sensor, so i cannot test it. So you dont get an error warning? Can be also connection problem or a faulty sensor. You should check the I2C connection if the sensor response. If you dont have a i2c capture device try to communicate with the sensor directly.
@adrianw75
@adrianw75 2 ай бұрын
I followed this exactly, but the command "commissioner joiner add * JO1NME" returns with Error 7: InvalidArgs
@patil29066
@patil29066 2 ай бұрын
It's really helpful! Can you please make videos related to MCUBoot on nRF Board?
@Nurof3n_
@Nurof3n_ 3 ай бұрын
thanks for taking the time to create these
@alishakerian1173
@alishakerian1173 3 ай бұрын
hello thank you for nice video, Can you make one for GATT client or how to read data from a periphral device? thank you
@abelashenafi6291
@abelashenafi6291 3 ай бұрын
Thanks for this amazing video. I followed your instructions step-by-step and everything works like a charm. Thank you and you just earned a new subscriber for your superb explanation and guidance. Thanks again
@wsniot
@wsniot 3 ай бұрын
Thank you for the positive feedback.
@SamuelKodi-hs4rk
@SamuelKodi-hs4rk 4 ай бұрын
Only discussed the host layer ignoring the controller layer😢
@user-yb9yr2wu8v
@user-yb9yr2wu8v 4 ай бұрын
英文不好, 能否配上字幕???????
@user-yb9yr2wu8v
@user-yb9yr2wu8v 4 ай бұрын
讲的很好, 希望多讲点,新手入门的, 毕竟zephyr 对于新手来说,学习难度太大
@saanumaurya6019
@saanumaurya6019 4 ай бұрын
from where i get this example code
@user-yb9yr2wu8v
@user-yb9yr2wu8v 4 ай бұрын
能不能配上中文字幕?
@user-rb2dr5pt6j
@user-rb2dr5pt6j 4 ай бұрын
I really really appreciate your tutorial. It was the only thing I found online that was of high quality for this lil board!! Your video is also super well annotated. As someone who is trying to get into embedded stuff, this has helped tremendously
@ammarq0
@ammarq0 4 ай бұрын
You are a phenomenal instructor, you make things effortlessly understandable! I always feel more confident engaging with these materials after watching your videos!
@xThirdOpsx
@xThirdOpsx 4 ай бұрын
Thanks for putting this together.
@isd-oj4zr
@isd-oj4zr 4 ай бұрын
I need to configure BMI323 on i2c bus in my custom board
@a_man5747
@a_man5747 4 ай бұрын
Hi sir, I need your help to configure BMA400 with Zypher OS.
@wsniot
@wsniot 4 ай бұрын
I didnt work with the BMA400 yet. The data sheet is very comprehensive and the communication workflow looks similar to the BNO055. Where you have difficulties?
@user-gj1ru2lx4n
@user-gj1ru2lx4n 4 ай бұрын
Great Video for Matter instruction!Thank you !!
@rgruberski
@rgruberski 4 ай бұрын
Hi! This video is fantastic! Would you share the code described in the video or some link to the repository? Many thanks for considering my request.
@hjw9347
@hjw9347 4 ай бұрын
Thank you for posting this helpful guide. Looking forward to getting stuck into the follow up videos!. Thanks!
@Baltrum2307
@Baltrum2307 4 ай бұрын
Thanks for your informative Video! Does the CCS detect VOC and calculate an CO2 equivalent? From my understanding VOC don’t include CO2, or am I wrong there? Greetings :)
@wsniot
@wsniot 4 ай бұрын
The CCS is a MOX-sensor which react to changes in electrical conductivity caused by the presence of volatile organic compounds. CO2 is not a VOC. Normally with other factors MOX-sensors can estimate the CO2 value (eCO2), but from my experience the estimation is not good and with the CS811 we got the same graph for CO2 like for VOC when we measure over a longer periode. So it seems they use here only a factor for estimation.
@Baltrum2307
@Baltrum2307 4 ай бұрын
Thanks again for that fast response and your understandable answer! My goal is actually to monitor VOC values, because I was monitoring high levels of VOC with another smarthkme device. Do you have any data on how reliable the CCS can detect VOCs? (I know that VOC value is really not so meaningful because you can’t say which gas exactly is detected. But I wanted to verify whether there is really a high VOC pollution in my rooms)
@wsniot
@wsniot 4 ай бұрын
@@Baltrum2307 The VOC value itself isn't really meaningful, but it's good enough for a relative comparison. Measure the VOC value in a non-contaminated place and compare it with your room. The concentration is usually higher at the point of origin, for example the floor covering, wall or sofa, wherever the VOCs come from. And which VOC it is cannot be determined with the CSS811.
@user-kh3xu8uv2d
@user-kh3xu8uv2d 5 ай бұрын
Hi sir, I'm new in thread protocol, may I ask if it is possible to replace the nRF52840 Developerkit to nRF52840 dongle? Then I can use two dongles to do same way as you did in video. Thank you!
@wsniot
@wsniot 4 ай бұрын
Yes, its possible. Bit of course the flashing of the firmware you have to make manually with the programmer app.
@user-kh3xu8uv2d
@user-kh3xu8uv2d 4 ай бұрын
@@wsniot Got it! Thank you for your quick answer! For flash part, so I just need to follow your way (build dongle firmware as RCP part in your video) to flash my dongle, final step to select ot-cli-ftd instead of ot-rcp, am I correct? Thank you!
@wsniot
@wsniot 4 ай бұрын
@@user-kh3xu8uv2d You can flash the compiled hex-file with the programmer over the bootloader. Of course dont forget to use the build-file for the usb dongle instead the dk-file.
@cozmo4452
@cozmo4452 5 ай бұрын
Hello, when I create new application and choose a path, not matter where i choose it says (File path) already exists. Do you know the cause? Thankyou very much
@isd-oj4zr
@isd-oj4zr 5 ай бұрын
what if the board's name is not in the list? my board has BMD340 and I chose ubx_bmd340eval_nrf52840 as my board, but I am not getting any output
@wsniot
@wsniot 5 ай бұрын
The ubx_bmd340eval_nrf52840 has a atmel chips as j-link and usb-uart-bridge on board. If you use only a BMD340 it has actual only the nrf52840 and a few basic elements for supplying the SoC with power, oscillators and rf components. Maybe you can try using a usb dongle version works like the nrf52840-usb. The dongle will work as CDC-USB device. Or just simply connect an uart-usb-bridge to your BMD340.
@Steveshp1
@Steveshp1 5 ай бұрын
Your book is not sold in Korea, so I purchased it from Amazon in the US. I'm looking forward to it.
@wsniot
@wsniot 5 ай бұрын
Thanks, I hope it gives you a lot new insights.
@roysigurdkarlsbakk3842
@roysigurdkarlsbakk3842 5 ай бұрын
I got some SCD40 from china and they work, ish, but I want to create something that is meant to be used inside and having to take it outside or into a somewhat controlled atmosphere once a week, won't do. So, I tried to turn off autocalibration and rather do a forced calibration instead. This works, ish, but with the standard probe time of every four seconds, the measured rate of co2 rises quickly over a few days. So I tried to enable power saving, reducing the probe time down to every 30 seconds. I generally probe this every minute, so not an issue. This reversed the problem, by drifting downwards instead of upwards and after they reached zero, they now crash if I try to forcely calibrate them. Have you seen any of this or do you have any idea if it's possible somehow to find a co2 detector that can last for some time without having to be recalibrated all the time? I know such things exist, you can get them in shops, but I have no idea what they use internally. Thanks for the good work! roy
@wsniot
@wsniot 5 ай бұрын
But to use it inside under most conditions is normally not a problem as long there is at least once a week anykind of ventilation and no person or animal inside. As I know the most other CO2 sensors are not deliver good absolut values. Calibration is difficult. A lot cheap CO2 detection systems using an analog sensor and comparing just relative values. For fire detection for example you will have a high increase in a short time. Actually I dont know what they use in more modern air quality devices but I guess they also expect that the device is at least once in a specific time period exposed to the minimum CO2 value from around 400 ppm.
@michaeldalby1971
@michaeldalby1971 5 ай бұрын
Great Video Markus - Love your pace and explanations... it really helps to break down those barriers into learning a new subject
@michaeldalby1971
@michaeldalby1971 5 ай бұрын
Hi Markus, I have a question if I may? I have a BL653 demo kit (based on an NRF52840). I tried to use pin 0.19 as a general I/O pin (for your led blinking example), but I think it is already defined to be used for UART1 in the main device tree. I am using UART1 in my project, but I only need the RX & TX lines (I do not require Hardware flow control, so 0.19 & 0.21 can be freed up for other things). If I look at the device tree it looks like RTS (pin 0.19 ) and CTS (pin 0.21) are already defined as part of the ‘&pinctrl’ declaration &pinctrl { uart1_default:uart1_default { group1 { psels = <NRF_PSEL(UART_TX,0, 17)>, <NRF_PSEL(UART_RX,0, 20)>, <NRF_PSEL(UART_RTS,0, 19)>, <NRF_PSEL(UART_CTS,0, 21)>; }; }; }; How do I free up these two pins (and still keep the RX/TX functionality for UART1) by modifying the Device Tree Overlay ? Best regards Michael
@aokerem
@aokerem 5 ай бұрын
Well, I use nrf52832 on a my special card, which board I choose in build configuration or what can I do? I am open to your advice.
@wsniot
@wsniot 5 ай бұрын
What do you mean with special card? Did you design one by your own? For programming you can use what fits to your board best as long it has a nrf52832 chip (i.e nrf52dk_nrf52832). You have to adapt probably the device tree. And of course you need an external j-link programmer or a bootloader on the nrf52832.
@michaeldalby1971
@michaeldalby1971 6 ай бұрын
Great video - very useful