OMG, your video has helped me a lot.... In the world of Zephry there is so much information (with a lot of depreciated methods and old instruction). Your video was perfect and worked !!! Well done and thanks for sharing
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
Thank you so much for updating that old video with 1.9.1 SDK version. Do you know if there are some deprecated functions for OpenThread in 1.9.1 version? Why did you upgrade the SDK version?
For OpenThread I think not. But there were a lot of minor changes overall that didn't fit in the old video anymore. These are for example changes to the header files and the graphical interface in VS Code, especially the selection of the toolchain, the creation of projects and the graphical interface of the DeviceTree.
@@wsniot Thank you so much for your reply, I asked you this because I trying to replicate the CoAP protocol with 840DK's again, but now with 2.4.2 SDK version is not working anymore, is compiling and flashing into devices but doesn't has the expected behavior. Do you might explaining to me which are those changes made for newest version? The code is the same. We cannot find out some probable solution.
@@brandonmoncada1951 I tried my CoAP example and it works the same as before. The biggest problem I had with the SDK v2.4.2 was that uart1 was disabled by default in the devicetree, otherwise my programs all ran as usual so far. What exactly is not working? Is the CLI working? Do both have the same dataset? Does sending UDP packets via the CLI work?
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
Hello, really nice tutorial :) my device won't show in the "connected devices" view when I plug it in... By any chance do you have any idea why? would appreciate any tips ahah
Thx for the feedback. I dont have the nRF5340-dk here, but it should work similiar like the nRF52840: ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-Lcjt2Iu2xvY.html
@@wsniot I'm having one issue though. The issue is that some of the examples work just fine when making a new application based on some example let's say blinky. But SAADC example doesn't work when I build it. It gives an error CMake Error at CMakeLists.txt:11 (GET_DEVICE_CONFIG_FILES): I tried googling it but there's only one link explaining it but I couldn't understand what to do. If you could help me out, that'd be a huge help. It seems like nRF has very poor documentation and no explanation on working examples. Could you refer me to channel or website which could help me out. And I really appreciate your reply. 😊
@@wsniot Actually I'm new to the nRF family. And it feels to me that the learning curve is too high. And very few people seem to have worked on this. I'm quite good with STM32 but to fail here with nRF. 😔
@@NoumanAli Which build did you use? With nrf5340dk_nrf5340_cpuapp compiling works fine with me. In nrf5340dk_nrf5340_cpunet near all is disabled as default in the devicetree.
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
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
@@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!
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.
That depends. The simplest solution is to use an existing board such as the Xiao BLE and customise the DeviceTree. Or you adding your own custom board: ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-V_dVKgWKILM.html
Check if all the switches in the right position. Check if your device is accessable in the device manager. Do you have a JLink CDC Device as com-Port for instance?
@@patil29066 Did you check the power switch on the board? Should be set to on. And the second switch should be set to default, not to nRF ONLY. Does the power LED light? In the device manager there should be a device. If the driver is not installed properly than at least as unknown device.
