雷竞技电竞平台对话框半导体客户支持-作品 计画ps://support.dialog-semiconductor.com/resource-keywords/blinky en DA14531 Kit-USB, blinky example problem 计画ps://support.dialog-semiconductor.com/forums/post/dialog-smartbond-bluetooth-low-energy-%E2%80%93-software/da14531-kit-usb-blinky-example-problem < div class = "字段field-name-taxonomy-forums字段-type-taxonomy-term-reference field-label-above">
Forums: 

Hi,

I have recently started to work with the DA14531 Kit-USB.

After reception of the board I have tested the Demo. Everything was fine: led was blinking and the BD address was received by my computer terminal via UART.

I then tried to use the blinky example, as explained in the tutorial, and here comes the problem:
When I start the debug session in Keil, I can see the led blinking (I have tried to change the blinking frequency to be sure that it was the good code, and it is), but I can't receive the communication with my terminal. Am I missing something (like hardware configuration, pin assignments or something)?

  • The switches are in the default configuration,
  • I have a second kit (same, USB) with the default Demo and I am still able to receive the BD address via UART with this one,
  • I am using Realterm, but also tried Tera term and PuTTY without better results

Do you have any hint to solve this?

Thank you in advance.

Device: 
Fri, 20 Mar 2020 14:40:55 +0000 MathieuB 348928 at https://support.dialog-semiconductor.com 计画ps://support.dialog-semiconductor.com/forums/post/dialog-smartbond-bluetooth-low-energy-%E2%80%93-software/da14531-kit-usb-blinky-example-problem#comments
GPIO Interrupt Detection 计画ps://support.dialog-semiconductor.com/forums/post/dialog-smartbond-bluetooth-low-energy-%E2%80%93-software/gpio-interrupt-detection < div class = "字段field-name-taxonomy-forums字段-type-taxonomy-term-reference field-label-above">
Forums: 

Hi Dialog,

Problem Statement
- Register a GPIO interrupt/ISR using GPIO_RegisterCallback( ) and detect if the short press and long press on the button when the system is up and running.

What I tried

  • I'm using the SW_2 (P0_6) for this functionality since the SW_3 is currently been used for wkupct_register_callback( ) that initialises the BLE advertisement.
  • I was able to register the GPIO interrupt callback by the following method
  • void register_button_isr(void)
    {
    NVIC_DisableIRQ(GPIO1_IRQn);
    // set isr callback for button pressed interrupt
    GPIO_RegisterCallback(GPIO1_IRQn, push_button_callback);
    // Push Button input
    GPIO_EnableIRQ(GPIO_PORT_0, GPIO_PIN_6, GPIO1_IRQn, true, true, 0);
    }

  • I've configured the GPIO under the set_pad_functions( ) and reserved the GPIO in GPIO_reservations( ).
  • Turn the LED on the DA14583_ProDK if the SW_2 is pressed, and when pressed again, turn off the LED.

Observation

  • When the system is in active mode, i.e. broadcasting BLE advertisement packets, the ISR is not generated by the SW_2 pin
  • If I follow the same process by modifying the Blinky example, everything just works perfect

Attached below (ble_examples.zip) is the file containing the modified Blinky example and the new file that I added in the ble_all_in_one application

Looking towards a positive response.

Thanking you in advance

Regards
Dhruv Shah

Device: 
Sun, 24 Jun 2018 14:10:02 +0000 dhruv11593 198548 at https://support.dialog-semiconductor.com 计画ps://support.dialog-semiconductor.com/forums/post/dialog-smartbond-bluetooth-low-energy-%E2%80%93-software/gpio-interrupt-detection#comments
"error 56: cannot open file" 计画ps://support.dialog-semiconductor.com/forums/post/dialog-smartbond-bluetooth-low-energy-%E2%80%93-tools/error-56-cannot-open-file < div class = "字段field-name-taxonomy-forums字段-type-taxonomy-term-reference field-label-above">
Forums: 

Hi,

I tried to download the blinky sample application to my brand-new development kit.
Following all steps described in "UM-B-049 Getting started with the DA1458x Development Kit–Pro", I come to the step 17 of section "4.1
Run an example on the DA14580/581/583", and got this error:

Include "C:\\Users\\hp\\Downloads\\GreenVirtue\\Dialog\\SDK 5.0.4\\SDK 5.0.4\\DA1458x_SDK_5.0.4\\DA1458x_SDK\\5.0.4\\projects\\target_apps\\peripheral_examples\\blinky\\Keil_5\\..\\..\\shared\\sysram.ini"
________^
*** error 56: cannot open file

I search for the file, but it does not exist anywhere. Note that I build the project without error.
So, where is that "sysram.ini"? Is it generated by the build process? If not, is it missing from the SDK 5.0.4?

Keywords: 
Device: 
Sun, 04 Feb 2018 04:42:53 +0000 cdang_2000 146147 at https://support.dialog-semiconductor.com 计画ps://support.dialog-semiconductor.com/forums/post/dialog-smartbond-bluetooth-low-energy-%E2%80%93-tools/error-56-cannot-open-file#comments
Pro board not detected when running Blinky https://support.dialog-semiconductor.com/pro-board-not-detected-when-running-blinky < div class = "字段field-name-taxonomy-forums字段-type-taxonomy-term-reference field-label-above">
Forums: 

I am trying to run the Blinky Example as shown in the 'Getting started with the DA1458x Development Kit – Pro' guide. I get to step seven, the step where you check that the SW device has been detected correctly. However when I try to do this, no device is recognized. When I try to run the debugger after this it leads to the error: "No Cortex-M SW Device Found".
How can I make the debugger recognize my board? What could I have done improperly along the way that would lead to this problem?

Thanks

Device: 
Thu, 07 Jul 2016 15:23:45 +0000 jamartin 4108 at https://support.dialog-semiconductor.com https://support.dialog-semiconductor.com/pro-board-not-detected-when-running-blinky#comments
Tera Term not working 计画ps://support.dialog-semiconductor.com/tera-term-not-working < div class = "字段field-name-taxonomy-forums字段-type-taxonomy-term-reference field-label-above">
Forums: 

I am using the Basic DA14580 development board, following instructions in UM_B_025 DA14580_581_Bluetooth_Smart_developement_kit-Basic V2.2, using Keil 5.15. The Blinky example runs on the board fine, i.e. LED blinks. However, the Tera Term is not showing any output. I am connected through COM9, Jlink CDC UART port in the drop down. The appearance of that in the dropdown should indicate it's detecting the device correctly, but yet no output in the terminal.

Any advice? Thank you.

Device: 
Tue, 09 Jun 2015 12:50:29 +0000 danielc008 1663 at https://support.dialog-semiconductor.com 计画ps://support.dialog-semiconductor.com/tera-term-not-working#comments