DA14581

GAPC_CONNECTION_CFM

Thu, 2018-02-01 20:19--JamesHiebert

Hello,

I'm wondering what effect the "auth" field in the GAPC_CONNECTION_CFM message has on slave device behavior given a system with "just works" pairing. RW_BLE_GAP_IS doesn't provide this information.

The CONNECT_IND from the master will soon be followed by a Pairing Request from the master. At that time, the slave application will return the value of the "auth" flag to the master in the Pairing Response.

Does the value of "auth" in the GAPC_CONNECTION_CFM matter in this case?

Thanks,

Jim

Asserting DA14581 reset pin after power cycle

Wed, 2018-01-31 22:35--JamesHiebert

In our system, the Dialog DA14581 chip is powered down most of the time. Periodically it is powered up by a separate ASIC to advertise and possibly connect with a master device. There are also cases in which the Dialog chip is powered down and then immediately powered back up again.

For this particular case, a Dialog Field Application Engineer (FAE) recommended that our ASIC always assert the Dialog chip reset pin to perform a chip reset immediately after every power up since the chip may be left in an indeterminate state if powered up immediately after being powered down.

GAPC_PAIRING_FAILED reason "unspecified"

Sat, 2018-01-20 19:08--JamesHiebert

Hello,

When my master device (different vendor BLE chip) attempts to pair with my DA14581, the DA14581 responds with GAPC_PAIRING_FAILED and reason "unspecified". There isn't much in the documentation (RW-BLE-GAP-IS) beyond this.

Pairing works if the master sets the bonding flag.

Any help would be appreciated!

SmartSnippets can not load hex file

Mon, 2017-12-11 18:55--zheshen

I was trying to OTP the release build and the development build of an application on a DA14581 with SmartSnippets 3.9. The SmartSnippets could not load the hex file for the release build but the loading the development build was OK. Both builds were compiled and linked successfully and can be loaded through Keil GUI.

switch from 580 to 581

Mon, 2017-11-13 12:53--uta_lc

Dear Dialogue support,

我们正在努力switch the chip from wire bond 580 to the ultra thing 581 (34 pins). We got some issue so far and we cannot get the chip to respond to button press. In terms of firmware, apart from change build target from 580 to 581 (define __DA14581 ) as in the Keil project, is there anything else we need to consider - assume the same pins are still used?

In terms of OTP header, can we simply read that from 580, export it and write the content into 581?

Thanks for your attention,
uta_lc

Pages

订阅RSS - DA14581