Hi,
I'm new to Dialog products and my end goal is to use the DA14580 as a external/connectivity chip with my own custom service and characteristics.
- 我能够修改ble_app_profile例子nd add a characteristic to it which responds on a write to the control point characteristic. I would instead like to send the data immediately once the central device i.e. my phone, connects to it and subscribes to notifications. I believe there is a message sent to user_catch_rest_hndl when the phone subsribes to notifications. Previous forum posts have pointed to a RW-BLE-GATT-IS document which contains the BLE messages but I'm unable to find it. Can you please share this document and confirm the existence of a message which is sent when the connected device subscribes to notifications.
- My next aim is to use DA14580 as an external chip over SPI. I took a look at the prox_reporter_ext_spi example and noticed that a message is sent to the external chip to add the service. So does this mean that the firmware running on the DA14580 when it is acting as an external chip is a generic one and the master needs to provide it with what serives it should register? Also, can you give some steps/resources as to how I can proceed with making this? Should ble_app_profile be used as a base code or the prox_reporter_ext_spi?
Thanks
Gowtham
Keywords:
Device:
Hi tsgowtham,
Thanks for your question. Let me check it and I’ll get back to you.
Thanks, PM_Dialog
Hi PM_Dialog,
Thanks for responding. Till you are able to get back with the answers to my question, can you please share RW-BLE-GATT-IS and RW-BLE-HOST-IS or provide a link to where I can download these docs from? Are there any other docs too which would be required to be read for using the DA14580 as an external chip?
Thanks
Hi tsgowtham,
The RW-BLE-*** documents are not available on our support website anymore, because typically people do not need those documents for developing their application. You should use the provided easy-to-use APIs in order to start developing your project. In case of notifications, please take a look at the ble_app_peripheral example of the SDK. This example uses the app_easy_timer in order to send notification to peer Central device every APP_PERIPHERAL_CTRL_TIMER_DELAY. Upon timer expiration, the app_adcval1_timer_cb_handler() callback is triggered.
If I understood correctly, your requirement is to use the DA14580 as an SPI master. Please check the booting procedure as described in theAN-B-001 : DA14580/581/583 Booting from serial interfaces. Additionally, you should look at the prox_reporter_ext_spi project in order to check how to setup the HW as an SPI slave.
In the meanwhile, would it be share a high level description of your application?
If you are starting a new design, we would strongly recommend to start with DA14531 or DA14585/586 products and our latest SDK6.0.14, as it is much more improved. We have a lot of code examples and improved documentation, and there is also software roadmap support. There is not any software roadmap support for DA14580 product family and SDK5.
Please check out DA14531:
//www.xmece.com/products/connectivity/bluetooth-low-energy/products/da14531
Additionally the DA14531 SmartBond TINY™ Module is now released! Follow the link below to find datasheet, documentation and HW collaterals for the module:
//www.xmece.com/products/bluetooth-module-da14531-smartbond-tiny
Moreover, Dialog Serial Port Service (DSPS) and CodeLess are now available for the DA14531!
Thanks, PM_Dialog
Hi,
Since the RW-BLE files are not available anymore, where can I find the list of message IDs used in the user_catch_rest_hndl function?
The ble_app_peripheral project starts transmiting once a value is written to the control point characteristic. I would like to change it such that it starts transmitting once a mobile app enables the notification for a specific characteristic.
One thing I would like to clarify is that my requirement is to use the DA14580 as a SPI slave, NOT master. I am using another microcontroller as the master.
我不能理解他initiates the communication between the master and the slave? What message is sent as the first message?
Also, if I would like to use the cust1 profile, do I need to modify the target app of prox_reporter_ext_spi or are the services and profile loaded from the SPI master?
About your question regarding my application, I cannot reveal any details as the client is in a regulated industry. I'm working on an existing design, so I'm unfortunately unable to shift to a DA14531.
Thanks
Hi tsgowtham,
The messages for the custom 1 service can be found in custs1_task.h file. When the control point characteristic is written, the user_svc1_ctrl_wr_ind_handler() will be triggered and if the value is 0x01 then the DA14580 will send the data over notification to the peer device. In app_adcval1_timer_cb_handler() you could how to send notification. So you can, you could use similar implementation as soon as the device is connected (for example). In case of prox_reporter_ext_spi, I assume that you can add the implementation from the ble_app_peripheral.
Thanks, PM_Dialog
Hi PM_Dialog,
Thanks for your reply, I took a look at the custs1_task.h file and I think I understand the messages being sent a for custome profile bit better now.
But I still am not able to find the answer to the question I had mentioned in my last post.
"And I'm unable to understand who initiates the communication between the master and the slave? What message is sent as the first message?"
Can you please help me with this question too?
Thanks
Hi PM_Dialog,
Can you please help me with figuring out who starts the communication? My question is in my last post.
Also, is there any API reference doc for all the message structures in cust1_task.h? I'm unable to figure out how to use custs1_create_db_req and I searched in the Software Platform Reference oc but couldn't find anything. I tried to take a look at how it's being implemented in the ble_app_profile example but I couldn't find how it's being passed to custs1_create_db_req_handler.
Thanks
Hi tsgowtham,
My apologies - propably i missed your last question. Let me check it and I'll reply you soon.
Thanks, PM_Dialog
Hi tsgowtham,
Please refer to section 6.1 DA1458x connected to SPI Master in theAN-B-001 : DA14580/581/583 Booting from serial interfacesapplication note. According to this document, the communication starts with the external SPI master device sending the Preamble bytes (0x70 and 0x50) followed by a zero byte. The Custom 1 profile is already implemented by the SDK. Probably the following documents might help you:
//www.xmece.com/sites/default/files/training_02_custom_profile_example_v1.2_0_0.pdf
//www.xmece.com/sites/default/files/an-b-029_developing_a_bluetooth_smart_custom_profile_v1.0.pdf
Thanks, PM_Dialog
Thanks PM_Dialog, these documents helped out quite a bit.
Hi tsgowtham,
Thanks for accepting my answer. If you have any other question, please feel free to create a new forum thread.
Thanks, PM_Dialog