Hi team,
I am working on a project wherein, I am starting a timer using the API [ app_easy_timer() ] . After the timer expiry, in the callback function, I am deleting the timer using the following statements :
app_easy_timer_cancel(timer_id);
timer_id = EASY_TIMER_INVALID_TIMER ;
But, even after the execution, the timer _id value is not getting changed to 0, which implies that the timer has not been deleted.
请建议可能的可能原因。
谢谢，
Team Wisilica
Dear Support,
I am working on DA14580 Basic kit.SO far I have been working on the ble_app_perpheral project. I was able to send ADC data on request from light-blue IOS app.
We have a requirement for setting up a timer to take adc value for every 5 min and storing in a buffer of fixed length 12. The The idea is at every given point of time we will have ADC samples for last 60 min spread at 5 min interval.
Dear Dialog Team,
I would like to automatically send out adc measured data over the serial port service example whenever there is new Data available.
I have no understanding where to implement the services and callbacks.
Please provide me with a solution. I would like to the da14580 to act as a device and send out the data to a host (Mindstorm NXT EV3) so write without response should be used.
Hi Team,
Hi there,
I am having problem with the hrps profile. I am trying to create a hrps profile so that it can connect with my sensor. I have followed the example in UM-003 for DISS to implement the heart rate profile and I have also read this link about it (https://support.dialog-semiconductor.com/hrps-application-side). Here's in my attachment is the error that I have obtained in Keil MDK. Thanks!
Hi,
I am unable to understand the purpose/meaning of below macros in da1458x_config_advanced.h file. Can you explain what each one means:
#define DB_HEAP_SZ
#define ENV_HEAP_SZ
#define MSG_HEAP_SZ
#define NON_RET_HEAP_SZ
Hi, everyboady,
I have used the app_easy timer to do a Led blink function. but the device reboot continuous after I flashed the code to spi flash. I debuged the code and see that porgram goes into the blink function and the invoked app_easy_timer function.
the program never goes forward to code ( req->delay=delay; req->timer_id=timer_id; ke_msg_send(req);)
after it excute the code (struct create_new_timer_struct *req = KE_MSG_ALLOC(APP_CREATE_NEW_TIMER, TASK_APP, TASK_APP, create_new_timer_struct);
I have buying 3K DA14580 chip from your local team in ShenZhen China, and we also complete the PCB produce. Now we need this tool to do firmware program. I also asked your local team to buy this tools, but the local team didn't have this tools. Would you help us to buy this tools?
谢谢。
SDK5.0.3: How to create a service uses a 16-bit UUID, The cust_prf_func_callbacks is only for 128-bit UUID
This is a mature development. I use a Pro development kit to view and program a Murata based daughter board using the JTAG interface. I also use the DA14580 QFN48 daughter board. These 2 boards have had the OTP programmed with the same image. I have no issue using SmartSnippets to connect and read and program new Murata modules with a socketed daughter board.
I can't seem to connect to the off-the-shelf daughter board. I'm not totally sure how it was programmed but I believe at one point someone figured it out.
