BLE Example Pillar 4 (Security) does NOT work

了解更多FAQsTutorials

12 posts / 0 new
Last post
advanchip@pacbe...
Offline
Last seen:3年6个月前
加入:2017-05-10 23:35
BLE Example Pillar 4 (Security) does NOT work

I am using DA14585-00ATDEVKT-P Development Kit - Pro with DA14585_SDK 6.0.2.243 and Keil uVersion V5.23.0.0.

我遵循UM-B-080_DA14585_586_SDK_6_Software_Developer's_guide_3V0.pdf,以查看没有任何代码修改的示例。现在我在8.5支柱4(安全),我没有看到我的iOS LightBlue应用程序中的设备名称“Dialog-Security”。(附件是错误的屏幕截图)。以前的所有示例都是成功的。

On UM-B-080_DA14585_586_SDK_6_Software_Developer's_Guide_3v0.pdf
Page 72 Figure 43: Pillar 4 Application - User Application Code Flow for Pairing using Passkey Entry, I can't find app_easy_security_set_tk(), app_easy_security_tk_exchange(), app_on_ltk_exchange() and default_app_on_ltk_exchange() in the project.

Also Page 73 Figure 44: Pillar 4 Application - User Application Code Flow for Pairing using Just Works, I can't find app_on_ltk_exchange() and default_app_on_ltk_exchange() in the project.

Please advise.

谢谢。

设备:
MT_dialog
Offline
Last seen:2 days 4 hours ago
工作人员
加入:2015-06-08 11:34
Hi advanchip,

Hi advanchip,

嗯,BLE_APP_Security项目需要闪存才能运行(即如果您设置了User_CFG_APP_BOND_DB_USE_SPI_PLASH,如果没有设备可以在没有闪存的情况下运行),因此如果没有闪光灯,则设备将在NMI_HANDLER()中最终闪烁在与闪光灯互动的情况下,没有闪光灯。nmi_handler()表示看门狗已经过去了。

Regarding the app_on_ltk_exchange, the callback that is triggered is the .app_on_ltk_exch and the default action from the application side is the default_app_on_ltk_exch, regarding the app_easy_tk_exchange() the function in the SDK is the app_easy_security_tk_exch() regarding the app_easy_security_set_tk() this is a function from an older SDK (a 580 SDK) which no longer used in the 6.0.2, the key was set via the app_easy_security_set_tk() function and then send via app_easy_security_tk_exch() function, is the new SDK the API directly sets and sends the tk.

对于.app_on_ltk_exchange回调,使用app_on_ltk_exch名称,相应的默认函数是default_app_on_ltk_exch()。

Also, if you dont mind me asking, the device that you are using is it a pro kit daughter board ?

Thanks MT_dialog

advanchip@pacbe...
Offline
Last seen:3年6个月前
加入:2017-05-10 23:35
Yes, the DA14585 device was

Yes, the DA14585 device was installed in the DA14585-00ATDEVKT-P Development Kit - Pro's daughter board (please see attached photo for the hardware information).

I followed UM-B-080_DA14585_586_SDK_6_Software_Developer's_Guide_3v0.pdf Figure 45 to select target processor "ble_app_security_585" which do not have a flash, I assume the software will automatically take care the flash issue. Now I changed USER_CFG_APP_BOND_DB_USE_SPI_FLASH to undef, and the example works. I want to know if Section 8.8 Pillar 7 (all in One) example will have the same problem?

谢谢。

MT_dialog
Offline
Last seen:2 days 4 hours ago
工作人员
加入:2015-06-08 11:34
Hi advanchip,

Hi advanchip,

您还可以使用主板提供的外部闪存,因此即使在585上也使用闪光灯使用闪光灯,或者使用闪光灯由我所示的user_cfg_app_bond_db_use_spi定义控制。是的,同样适用于所有在一个示例中,它在相同的定义下也具有相同的配置。

Thanks MT_dialog

advanchip@pacbe...
Offline
Last seen:3年6个月前
加入:2017-05-10 23:35
How can I use the external

在此示例中如何使用主板提供的外部闪光灯?

在我的原始问题中,您告诉我#undef user_cfg_app_bond_db_use_spi才能使安全示例是有效的。从测试中,我知道#define user_cfg_app_bond_db_use_spi不起作用。现在你说“要么使用闪存或不受user_cfg_app_bond_db_use_spi定义来控制,这个陈述会困惑我。请说清楚。

谢谢。

MT_dialog
Offline
Last seen:2 days 4 hours ago
工作人员
加入:2015-06-08 11:34
Hi advanchip,

Hi advanchip,

在您测试的示例中,您可以使用闪存或不使用闪光灯进行操作,以便定义闪存是否使用闪存或不定义verify user_cfg_app_bond_db_use_spi_flash。如果您希望使用585使用Flash,您必须将位于Pro套件的主板上的闪光灯连接。为了检查如何连接闪光灯,请检查UM-B-049入门使用DA​​1458X开发套件 - Pro。在J5标题旁边的Pro Board本身上也存在示意图,以选择UART或SPI配置。

因此,如果您有闪存连接,这意味着如果您拥有user_cfg_app_bond_db_use_spi_flash定义,则该示例将能够运行。

如果您没有闪存连接,则示例将仅使用user_cfg_app_bond_db_use_spi_flash未定义。

Thanks MT_dialog

vanaja.
Offline
Last seen:2年2周前
加入:2018-11-27 07:25
I am using DA14580 dev kit.

I am using DA14580 dev kit. using uart connections to flash code. BLE Example Pillar 4 (Security) fails in NMI_Handler() as expected. if spi connections are made as illustrated on board to flash, keil gives "No Cortex-M SW Device Found" failure message.

我需要使用绑定功能。可能you please tell where i am missing.

PM_Dialog
Offline
Last seen:41 min 2 sec ago
工作人员
加入:2018-02-08 11:03
嗨vanaja,

嗨vanaja,

The question that you have posted is not related with this forum thread because the current thread is referring to the DA14585 chip and not to DA14580. If you have any other follow-up questions, please create a new for post and tag the DA14580 chip. This error mean the there is no communication between the DA14580 and the Keil. Could you please try to reset it and download any other example of the SDK? Do you still have the same issue? Also, please go to the Option for Target -> Debug -> Setting of the Keil environment and make sure that the DA14580 is detected. If yes, you should see the SN of the J-Link

Thanks, PM_Dialog

vanaja.
Offline
Last seen:2年2周前
加入:2018-11-27 07:25
PM_Dialog,

PM_Dialog,

I searched a lot in dialog website to create new post but couldn't then commented in existed post. before could able to create new post.

with SPI connections the SN of the J-Link is visible in setting window still same error.

PM_Dialog
Offline
Last seen:41 min 2 sec ago
工作人员
加入:2018-02-08 11:03
嗨vanaja,

嗨vanaja,

Could you please let me know if you are able to replicate it with any other example of the SDK? Also, have you downloaded firmware into the SPI flash? It seems that your device cannot be detected.

Thanks, PM_Dialog

vanaja.
Offline
Last seen:2年2周前
加入:2018-11-27 07:25
你好pm_dialog,

你好pm_dialog,

I am not able to flash any application. never downloaded firmware into SPI flash.

PM_Dialog
Offline
Last seen:41 min 2 sec ago
工作人员
加入:2018-02-08 11:03
HI vanaja,

HI vanaja,

Could you please try to connect your board with the SmartSnippets toolbox? Probably there is no connection between the DA14585 and the Jlink fw that tries to communicate with the device. That could be anything from connections up to problems with the PCB that make the 585 unable to operate. My suggestion is to check if the bootloader is executing in order to verify that the 585 is operating correctly. You could probe the P04 and P05 pins, and that pins should be toggled executing part of the bootloader, so when connecting to a terminal you should see the device printing garbage.

Thanks, PM_Dialog