Search Result

I'm trying to get the example application Asset Tracker V2 communicating with an Azure IoT Hub. I'm following the directions on the following pages: Cloud wrapper API — nRF Connect SDK 2.3.99 documentation (nordicsemi.com) Azure IoT Hub — nRF Connect SDK 2.3.99 documentation (nordicsemi.com) In Kconfig I changed Asset Tracker v2 -> Application cloud codec -> Application cloud codec backend, from Enable nRF Cloud codec backend to Enable Azure IoT Hub codec backend. I've added my CA cert, Client cert, and Private key in the CERTIFICATE MANAGER of LTE Link Monitor. There is a note about changing CONFIG_MQTT_HELPER_SEC_TAG but I can not find that in Kconfig. Is that step important? Are there other Kconfig changes that I'm missing?

hello ., is it possible to subscribe to temperature value or any other value from the thingy 52 rather than flip state as stated in the sample of https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/samples/nrf9160/lte_ble_gateway/README.html ., Could you please provide the best way to subscribe to temperature value from the THINGY 52 and send it to the cloud? please and thank you .,

I'm trying to set up the two-stage bootloader on nRF5340, NCS version 2.3.0. I am using a custom board with this pm_static_ _cpuapp.yml: b0_container: address: 0x0 size: 0x8000 region: flash_primary span: - b0 b0: address: 0x0 size: 0x8000 region: flash_primary s0: address: 0x8000 size: 0xc000 region: flash_primary span: - s0_pad - s0_image s0_image: address: 0x8200 size: 0xbe00 region: flash_primary span: - mcuboot s0_pad: address: 0x8000 size: 0x200 region: flash_primary s1: address: 0x14000 size: 0xc000 region: flash_primary span: - s1_pad - s1_image s1_image: address: 0x14200 size: 0xbe00 region: flash_primary s1_pad: address: 0x14000 size: 0x200 region: flash_primary mcuboot: address: 0x8200 size: 0xbe00 region: flash_primary mcuboot_pad: address: 0x20000 size: 0x200 region: flash_primary app_image: address: 0x20200 size: 0xdbe00 region: flash_primary span: - app settings_storage: address: 0xfc000 size: 0x4000 region: flash_primary mcuboot_primary: address: 0x20000 size: 0xdc000 region: flash_primary span: - mcuboot_pad - app_image mcuboot_primary_1: address: 0x40000 size: 0x40000 region: ram_flash device: nordic_ram_flash_controller mcuboot_secondary: address: 0x0

Describe the issue(Question in my case): I recently acquired an NRF-7002DK from Digikey, and I have been pleased messing around with the Zephyr SDK so far. I like the capabilities of the SDK and the hardware that the NRF-7002 brings to the table. I noticed that the NRF-7002 is being interacted with on the development kit via an NRF-5430 host SoC, and I began to read the documentation about how the two interact. I know other host controllers are built using Nordic SoCs that are equally capable of performing as a host as the NRF5430, if not more; they just do not come packaged with the Zephyr SDK from their respective manufacturers, such as the Particle B4xx series( https://docs.particle.io/assets/pdfs/datasheets/b404x-b404-b402-datasheet.pdf ) My question : If I wanted to implement just the NRF-7002 wifi companion IC in one of my circuits, would I be able to use this companion IC without a

The notification in the subject occurs each time v2.3.0 nRF Connect for VS Code is started. A select compiler button is present, but this does not have valid choices. Obviously, the gcc compiler is hiding somewhere in the system. How should this issue be fixed? Thank you, Ken

I try to subscribe to a MQTT topic on AWS using the following code which is used to compose a dynamic MQTT topic based on IMEI char imei[32] = {'\0',}; modem_info_string_get(MODEM_INFO_IMEI, imei, sizeof(imei)); printk("Modem IMEI: %s \n", imei); static char settingsString[20] = "/settings\0"; static char topicString[75]; strcpy(topicString, imei); strcat(topicString, settingsString); printk("Subscribe string: %s \n", imei); printk("Subscribe string length: %d \n", strlen(imei)); const struct aws_iot_topic_data topics_list[APP_TOPICS_COUNT] = { [0].str = *topicString, [0].len = strlen(*topicString)}; err = aws_iot_subscription_topics_add(topics_list, ARRAY_SIZE(topics_list)); if (err) { printk("aws_iot_subscription_topics_add, error: %d\n", err); } The output is this (*** for security reasons) Modem IMEI: 351358815046*** Subscribe string: 351358815046***/settings Subscribe string length: 24 If I now publish a message using AWS MQTT Client the message will not reach the device. The strange thing is if i declare the same variable hard coded using static char topicString[75] = "351358815046880/settings" All works as expected and the publish messages get received as expected.

I have a question: do BLE events (such as connect/disconnect/read GATT/write GATT/notify GATT) pre-empt timer events (started by app_timer2.c) such that the app timer events can sometimes not fire for a long period of time? Can this be the reason why a watchdog set for a period of 1 second, for example, not fire, because the BLE events are dominating the CPU cycles and not allowing the timer events to fire? If this is the case, what is the recommended strategy for patting a hardware watchdog in the scenario of high BLE traffic?

Hi, I have an error when I enable CONFIG_DFU_TARGET_STREAM_SAVE_PROGRESS =y for fota. More detail about err: [00:11:19.945,312] aws_fota_netfeasa: job_update_accepted: Job document was updated with status IN_PROGRESS [00:11:19.945,465] aws_iot_netfeasa: mqtt_evt_handler: MQTT_EVT_PUBACK: id = 15010 result = 0 [00:11:19.945,495] aws_iot_integration: aws_iot_event_handler: AWS_IOT_EVT_PUBACK [00:11:19.945,739] cbprintf_package: (unsigned) char * used for %p argument. It's recommended to cast it to void * because it may cause misbehavior in certain configurations. String:"%s: Receiving up to %d bytes at %p..." argument:2 [00:11:19.945,770] download_client: download_thread: Receiving up to 2300 bytes at 0x2000c964... [00:11:20.391,998] download_client: download_thread: Read 459 bytes from socket [00:11:20.392,089] download_client: http_header_parse: GET header size: 459 [00:11:20.392,303] download_client: http_header_parse: File size = 371099 [00:11:20.392,456] cbprintf_package: (unsigned) char * used for %p argument. It's recommended to cast it to void * because it may cause misbehavior in certain configurations. String:"%s: Receiving up to %d bytes at %p..." argument:2 [00:11:20.392,486] download_client: download_thread: Receiving up to 2300 bytes at 0x2000c964...

I am trying to change the "Matter Accessory" display name in the Apple Home app. I am setting the following: CONFIG_BT_DEVICE_NAME="Smart Button" CONFIG_CHIP_DEVICE_TYPE=59 CONFIG_BT_DEVICE_APPEARANCE=1352 You can see in the screenshot, Eve has the appropriate information and icon displayed.

Is it possible to disable a GPIOTE interrupt, while performing some processing, and latch any incoming interrupt while that processing is occurring, so it fires once the interrupt is reenabled? My scenario, external SPI device receives some data, signals the nRF by an interrupt line, I want to disable the interrupt while I retrieve that data, if an interrupt occurs while I'm retrieving that data, I want to finish processing, reenable interrupts and then process go ahead and process it. I tried nrfx_gpiote_in_event_disable but the interrupt is 'lost' as the interrupt is not latched while disabled. Is this possible?