⚠️
Hi there.. thanks for coming to the forums. Exciting news! we’re now in the process of moving to our new forum platform that will offer better functionality and is contained within the main Dialog website. All posts and accounts have been migrated. We’re now accepting traffic on the new forum only - please POST any new threads at//www.xmece.com/support. We’ll be fixing bugs / optimising the searching and tagging over the coming days.
4 posts / 0 new
Last post
hem_forent
Offline
Last seen:3 years 1 week ago
Joined:2017-04-17 12:16
setup code

Hello support

i am using a da14581 development kit pro. The problem i am facing is i cant interface with it the mobile app.when i enter the setup code(pairing PIN) printed in the label it didn't get connected.Is there any other way to find the setup code(pairing PIN) of my da14681 or can i able to generate a setup code(pairing PIN) manually using software tools

please help,looking forward to hearing from you soon

Thankyou

HEMANTH

Device:
MT_dialog
Offline
Last seen:2 months 3 weeks ago
Staff
Joined:2015-06-08 11:34
Hi hem_forent,

Hi hem_forent,

To start with, which SDK example are you using ? and which SoC as well ? You mention DA14581 and in the device keyword you mention DA1468x. Regarding the label and the pin code, the fw that you load in the dev kit defines the PIN code that the device is going to use and it has nothing to do with any label or info on the dev kit it self.

So if its a 68x i assume that you are using the bms example, so the PIN code configuration is generated randomly and is printed through the UART (check the readme.md file in the SDK under the bms project), normally this demo should promt the passkey through the UART port along with some additional info and as soon as you enter the key then the device should be bonded. For further info please check the readme file i mentioned earlier.

If its on the 58x SDK then the pass key is hardcoded and defined in the APP_SECURITY_MITM_PASSKEY_VAL (123456 is the default) in the user_security.h file.

Thanks MT_dialog

hem_forent
Offline
Last seen:3 years 1 week ago
Joined:2017-04-17 12:16
Thank you for your valuable

Thank you for your valuable replay

The sdk i am using is DA1468x_SDK_BTLE_v_1.0.6_homekit_RC_8_5.968 and also attaching a image of the board which i am using.Now there is a problem that my home kit mobile app didn't detect the Bluetooth on my board.

Couple of days before i had connected it with my phone but now home kit mobile app not detecting it ,says couldn't find any devices. I dont know what wrong happened please help me as soon as possible

Attachment:
MT_dialog
Offline
Last seen:2 months 3 weeks ago
Staff
Joined:2015-06-08 11:34
Hi hem_forent,

Hi hem_forent,

因为我很困惑,你的问题是you are not able to pair with the device (this is what i understood from the original post), or that you are not able to trace the advertising events from the device. Can you please check via using the Smart Snippets and the power profiler that your device is advertising and if it is advertising check with another device (android preferably) if you can trace the device ?

If you can't see the device advertising (from the power profiler) please try to re - download the homekit code and check again, also please be aware that the homekit is builded for the 0x20000 address that means that the reference design requires the ble_suota_suota loader in address zero in order to boot using the bootloader and then start the homekit code. So you need to build the ble_suota_loader and then download the fw in the qspi by using the script suota_initial_flag_jtag_win.

Thanks MT_dialog