![]() The ble_app_uart app is intended to be use with the PCA10056 (nRF52840-DK). Modifying the Nordic Project to target the nRF52840 USB Dongle The updated version of wireless_uart.c on .uk contains this modification. This has been added to the NXP project so that we can connect to the board. The third UUID is the Nordic custom UUID coded into the UART project. Characteristic: Peripheral Preferred Connection Parameters.There are two mandatory services (both 16-bit):ġ. The next step is to add the Nordic device to the BleApp_CheckScanEvent callback, we add the following after the existing check for the NXP UART. Adding the Nordic device to the Scan Results This sets the thirteenth byte to be 1, so we have set the thirteenth byte in the nordic_service array. This value is defined as NUS_BASE_UUID in the Nordic Project within ble_nus.c.This value is then modified later to create a custom UUID.Įrr_code = sd_ble_uuid_vs_add(&nus_base_uuid, &p_nus->uuid_type) The nordic_service array is the UUID that is reported by the nRF52840 and this is checked further in the application. We add this name to the NXP project so that we can allow the QN9090 to allow this board to connect. The DEVICE_NAME “Nordic_UART” is defined in the main.c of the Nordic project. ![]() Accessing the application notes within the NXP SDK will only unzip the files required by that application note. This is an important step as this allows the SDK to be fully unzipped and accessed. Note that the SDK location points to a user defined folder. See the following sections to, 5.2, 5.3 and 5.5 to JN-AN-1260-Zigbee-3-0-Getting-Started.pdf contains details on setting up the SDK even though we are not using Zigbee in this application note. The application note had been tested with versions:Īlso download the documentation for this SDK (SDK_2.6.x_QN9090DK6_doc.zip).ĭownload the document JN-AN-1260 from the NXP website ( Zigbee 3.0 Getting Started) under the documentation tab. The application note had been tested with versions:ĭownload the latest QN9090DK6 SDK (SDK_2.6.x_QN9090DK6.zip) from the NXP website ( NXP website). You will also require the QN9090 SDK Installing the NXP SDKĭownload MCUXpresso from the NXP website ( MCUXpresso-IDE). The NXP project is built using MCUXpresso which is available free of charge from the NXP website. See the following link for further details. This is built using the excellent third party Segger Embedded Studio for ARM which is available for free to all Nordic Semiconductor customers. The Nordic project is the ble_peripheral/ble_app_uart application available in the SDK. Applications for each end are available within the relevant SDKs. The interoperability test demonstrates a wireless UART connection between the two devices. To read more about the DevKit, refer to RuuviLab’s tutorial.The intention of this application note is to demonstrate connectivity between an NXP QN9090 (or K32W061) and a Nordic nRF52840. A great tool for this is Nordic Semiconductor’s Power Profiler Kit which is compatible with the nRF52-DK evaluation board. Note also that if you’re developing your own firmware, power consumption measurements are recommended so that possible current leaks can be obtained. The DevKit isn’t needed if you’re happy to flash your RuuviTags over-the-air.įor most of the people, DFU OTA (Device Firmware Update Over-the-Air) is enough if no protocol stack or bootloader has to be replaced or no serious debugging is needed. No hassle with a battery while developing because the shield powers the RuuviTag.Safely test different protocol stacks in development (Bluetooth 5 for example, an upcoming feature).The original RuuviTag software can be restored (factory reset).Easy access to all the IO pins found on bottom of the RuuviTag.Debug your firmware via SWD (the nRF52-DK has an integrated Segger J-Link programmer).Use third-party protocol stacks or operating systems (ie.1 x Development shield designed for RuuviTag.1 x Nordic Semiconductor nRF52-DK evaluation kit.The Development Kit is designed for hardcore developers who would like to take their RuuviTag sensors to the limit by flashing and debugging the devices via SWD (Serial-Wire-Debug) bus or use RuuviTag’s extra IO connections on bottom of the circuit board.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |