Search Result

Hi, Because the efficiency of the production of Matter burning program is too slow. we want to insert multiple devices in the production environment to burn at the same time. But because of the reason of one machine and one code, this involves the problem of specifying the device when it needs to burn. I know that the SN number is the only difference between each device (can be seen via the "nrfjprog --ids" command) I have tried the following two commands but neither of them worked and each time a box pops up asking me to select the device. 1.nrfjprog -s 150710432 -f nrf52 -program 1.hex --verify 2.nrfjprog --snr 150710432 -f nrf52 -program 1.hex --verify When I have only one device connected to my system, using the -n parameter can specify it But when I have multiple devices connected to my system, using the -n parameter has no effect,

Hello, I am using nRF Connect 2.5.2 with a Xiao Seeed BLE Sense nRF52840 and Jlink EDU mini I am trying to flash the peripheral_hids_keyboard sample with Ozone, and I immediately hit a hard fault (escalation of a fault with configurable priority that cannot be handled) I can flash the peripheral_hids_keyboard sample using Vscode (nrfjprog / West) and debug successfully. I can even flash with Vscode and attach to process with Ozone. Ozone also worked fine to flash other samples (lsm6dsl) I am confused why Ozone can't flash the peripheral_hids_keyboard sample, and what Ozone is doing differently than Vscode / nrfjprog Thanks!

Generate Support Information fails dramatically: I don't remember how to find the log. How many average users would have the slightest clue!!! Please help. The other problem is one I have seen others comment on, but the usual solution makes no sense. They say to switch Device Provider from nrfutil to nrfjprog. But why would we do that? nrfutil works fine on the command line C:\ncs\v2.5.0\nrf\applications\asset_tracker_v2> nrfutil device list 50100377 product J-Link traits jlink, seggerUsb, usb 6&33aeebb&0&2 ports COM13 traits serialPorts Found 2 supported device(s) PS C:\ncs\v2.5.0\nrf\applications\asset_tracker_v2> So why doesn't work in VS Code? The reason I find this particularly obnoxious is that the documentation states that nrfutil is the default Device Provider. So, it should just work. It is obviously in my Path, too. Thanks. Burt

The MCUboot, Slot0, and Slot1 flash partitions are defined in the board file. E.g., nrf52840dk_nrf52840.dts has boot_partition at 0 with length 0xC000, slot0_partition at 0xC000 with length 0x76000, slot1_partition at 0x82000 with length 0x76000, and storage_partition picking up at 0xF8000, right after Slot1. In a Sigurd Hellesvik git repo, I learned about partition_manager_report; "west build -t partition_manager_report", which seems to say that Slot 0, for the primary image, is at 0xC000 with a length of 0x7A000 (starting with a 0x200 "pad") and Slot 1, for the secondary image, is at 0x86000 with a length of 0x7A000. It would seem the partition manager is free to allocate flash0 in nrf52840_qiaa.dtsi however it likes. Is the stuff in the DTS just a suggestion? This would seem to conflict with CONFIG_USE_DT_CODE_PARTITION=y in the prj.conf. If I put stuff like USB in MCUboot and have to grow the partition to fit it by setting

I created a new application using the "Create a new application" > "Copy a sample" > "zephyr/samples/basic/blinky" option in vscode. And I added a new build configuration using the default settings except for changing the board to "nrf5340dk_nrf5340_cpuapp". After building, I pressed the flash button in the actions panel to flash it to my NRF5340 DK. It executes the following command (without --log), which I also tried running manually: ➜ Desktop nrfjprog --program /opt/nordic/ncs/v2.6.1/nrf/applications/nrf5340dk_nrf5340_cpuapp/blinky/build/zephyr/zephyr.hex --chiperase --verify -f NRF53 --coprocessor CP_APPLICATION --snr 1050303214 --log [error] [ Client] - Encountered error -5: Command select_coprocessor executed for 6 milliseconds with result -5 ERROR: Failed when selecting coprocessor APPLICATION [error] [ Worker] - Encountered unexpected debug port ID 2, expected 6 ERROR: The --family option given with the command (or the default from ERROR: nrfjprog.ini) does not match the device connected. Why isn't it able to recognize the coprocessor when flashing? The computer (and

I recently bought PPK2. But am unable to connect it to my Linux PC with Power Profiler v4.1.0. Below is the log - 08:49:26.328 Error: Failed with exit code 1. Failed to device info one or more devices: * FEAC8E7BF8DD: [sdfu] No deviceInfo available for the device, code: Argument. Message: Operation device-info failed, [sdfu] No deviceInfo available for the device. 08:49:26.329 Validating firmware for device with s/n FEAC8E7BF8DD 08:49:26.329 Connected to device with serial number: FEAC8E7BF8DD and family: Unknown 08:49:26.329 Note: no pre-compiled firmware is available for the selected device. 08:49:26.329 Error while setting up device FEAC8E7BF8DD 08:49:26.329 "No device setup found" 08:49:26.329 Deselecting device I'm also attaching the complete log as well. devzone.nordicsemi.com/.../2024_2D00_05_2D00_04T03_5F00_14_5F00_56.088Z_2D00_log.txt

Hello, I am trying to flash the nRF9160 application(merge.hex) which is created after build in an external board. The external board is from fanstel - BLG840F. Couple of days back, I could easily flash merge.hex using programmer v4.3.0 of nRF connect for desktop. Now suddenly, I am getting this error in the programmer. I tried using the nrfjprog --recover command but again, it failed (it is because my Fantsel module is connected to the Debug out of nRF9160dk board. And I want to recover Fantsel module not nRF9160dk). Below is the screenshot for the same I would greatly appreciate any help.

Log file of nRF connect for desktop BLE standalone 2024-05-03T03:44:32.571Z DEBUG Application data folder: /home/longqi/.config/nrfconnect-bluetooth-low-energy/bundle 2024-05-03T03:44:32.678Z INFO Using nrf-device-lib-js version: 0.4.4 2024-05-03T03:44:32.679Z INFO Using nrf-device-lib version: 0.10.3 2024-05-03T03:44:32.679Z INFO Using nrfjprog DLL version: 10.15.1 2024-05-03T03:44:32.679Z INFO Using JLink version: JLink_V7.66a 2024-05-03T03:44:32.684Z VERBOSE [nrfdl][trace](11:44:32.640) DeviceLister::enumerate: Checking future_status of enumerate_task_status 2024-05-03T03:44:32.687Z VERBOSE [nrfdl][trace](11:44:32.640) DeviceLister::enumerate: Waiting for enumerate task to complete 2024-05-03T03:44:32.689Z VERBOSE [nrfdl][trace](11:44:32.640) DeviceLister::enumerate::enumerate_task: Start 2024-05-03T03:44:32.691Z VERBOSE [nrfdl][trace](11:44:32.640) DeviceLister::enumerate::enumerate_task: Device_pool is empty 2024-05-03T03:44:32.693Z VERBOSE [nrfdl][trace](11:44:32.640) DeviceLister::enumerate::enumerate_task: Before async_lister->enumarate 2024-05-03T03:44:32.695Z VERBOSE [nrfdl][trace](11:44:32.640) USBPlatformAPI::enumerate: Starting iteration 0 2024-05-03T03:44:32.696Z VERBOSE [nrfdl][trace](11:44:32.640) USBPlatformAPI::enumerate: Doing copyDeviceToUsb of device #0 2024-05-03T03:44:32.698Z DEBUG [nrfdl][debug](11:44:32.640) NRFDLException(6): Unable to open USB device. Error code: -3. idProduct=1568, idVendor=1507 2024-05-03T03:44:32.699Z VERBOSE [nrfdl][trace](11:44:32.640) USBPlatformAPI::enumerate: new device is not registered, skipping to next entry in list! 2024-05-03T03:44:32.701Z VERBOSE [nrfdl][trace](11:44:32.640) USBPlatformAPI::enumerate: Starting iteration 1 2024-05-03T03:44:32.703Z VERBOSE [nrfdl][trace](11:44:32.640) USBPlatformAPI::enumerate: Doing copyDeviceToUsb of device #1 2024-05-03T03:44:32.704Z DEBUG [nrfdl][debug](11:44:32.640) NRFDLException(6): Unable to open USB device. Error code: -3. idProduct=3,

We are using SDK 17.0.2, which does not support the rev 3 APProtect features. We would like to update the SDK in the future, but are looking for a shorter-term solution now. We'd like to maintain the behavior we had previously, which is as follows: 1) Upon assembly, the board is booted and firmware is flashed. It is expected that APProtect is disabled. 2) Upon end of manufacturing process, firmware enables APProtect. I have read the latest product spec and seen the steps needed for this: Step #1: after loading firmware, write UICR->APPROTECT to HwDisabled (5A). Then, upon each reset, firmware is to write APPROTECT.DISABLE to HwDisabled (5A). Step #2: firmware should write ICR->APPROTECT to enabled and NRF_APPROTECT->FORCEPROTECT to APPROTECT_FORCE (00). I looked through the latest SDK and saw that the main line I was to emulate was NRF_APPROTECT->DISABLE = NRF_UICR->APPROTECT; which makes sense if NRF_UICR->APPROTECT was set during the

If you see i'm trying to install toolchain and nrf sdk v2.6.1 via vscode, the installations seems to be successful but at the end of toolchain as well as sdk installation the below [22:34:51] =========== Toolchain validation report for nRF Connect SDK Toolchain v2.6.1 =========== Using the nRF Connect SDK v2.6.1 at c:\ncs\v2.6.1 ️ ️ nrfjprog couldn't be executed. Please ensure that SEGGER J-Link Software and Documentation Pack and nRF Command Line Tools are both installed. [23:38:08] =========== Toolchain validation report for nRF Connect SDK Toolchain v2.6.1 =========== Using the nRF Connect SDK v2.6.1 at c:\ncs\v2.6.1 ️ ️ nrfjprog couldn't be executed. Please ensure that SEGGER J-Link Software and Documentation Pack and nRF Command Line Tools are both installed. FYI: I did install the nRF command line tools prior to the above step Download link: https://www.nordicsemi.com/Products/Development-tools/nRF-Command-Line-Tools/Download?lang=en#infotabs