DA14580

Get time from RTC module

Thu, 2020-06-25 10:20--Thanhtu131

Hi, i had bought DA14580 basic kit. I have to work with it. Now I am making a timer device using DA14580. The Specific time will be set on my android phone. DA14580 will take the set-time information from android phone( through BLE GATT connection). Then DA14580 will take real-time information from RTC module ds1307 ( through I2C communication protocol ) and activate the buzzer depending on the set-time.

Need help - use of arch_printf in barebone/ble_peripheral example and SPI flash integration

Thu, 2020-06-25 05:26--theultimateprasad

Hi I'm using Murata's ZY module which having DA14580 chipset. During the integration of SPI flash storage with ble_examples - ble_app_barebone or ble_app_peripheral I have two issues :

1. Unable to use the common_uart.h in ble examples / Also not able to get the results of arch_printf() function on UART.

2. Unable to use the SPI flash - spi_test() function in the ble example - ble_app_barebone or ble_app_peripheral

Details :

Not able to do SUOTA on DA14580

Tue, 2020-06-23 07:32--HarishKumar

Hi All,

We are trying to test SUOTA on DA14580, generate fw_1.img, fw_2.img, fw_multi_part_spi.bin as per the "AN-B-010_da14580_using_suota_0.pdf" stated step by step. After I burning the fw_multi_part_spi.bin into DA14580 development board (p2ml3656). It does not advertise. It works fine and advertise for fw_1.bin or fw_2.bin but not fw_multi_part_spi.bin.

In Smartsnippet toolbox, it writes till 0x7FF8 (32kb) even though it reads 0x1B090. Attached spi_smartsnippet.png

get time in sleep mode

Mon, 2020-06-22 20:45--Thanhtu131

Hi, i am making a timer medical BLE box. The box will receive shedule from android app. I want the box to trigger the buzzer in the right time. I have 2 questions:

1/ Does DA14580 have the real-time module so that i can get the time from it?

2/ if DA14580 does not have the real-time module, i will try to get the time from ds1307 through I2C communication. Can i do that in sleep mode?

Thanks!!!

Receiving CUSTS1_VAL_IND_CFM instead of CUSTS1_VAL_NTF_CFM in prox_reporter_ext

Mon, 2020-06-22 13:12--tsgowtham

Hi,

I have a modified version of prox_reporter_ext where I have 3 characteristics with notification configured for all. When I use the LightBlue app for android to subscribe to notifications of a specific characteristic, I received CUSTS1_VAL_IND_CFM (0xDC08) instead of CUSTS1_VAL_NTF_CFM .

Below is the configuration of the characteristic to which I tried to subscribe:

P-FET Power Switch

Mon, 2020-06-22 11:56--Yuseungho

Dear,

I'm using the device SLG46517M which has two P-FET power switches. Now, I'm testing the device in emulation mode

with the advanced board connected to the computer. Here I attatched the schematic and how I configured socket connection.

First, is the connection of P-FET that I understood right?

(VI1: Power switch 0 input, VO1: Power switch 0 output / VI2: Power switch 1 input, VO2: Power switch 1 output)

If it's right, according to the schematic,

Pages

订阅RSS - DA14580