DA14531- Power profile issue

Hi sir,

i am working on DA14531, after flashing the code into DA14531 then i started checking for power profile using smart snippets toolbar v5.0.24

it detects the device and J-tag, but it won't show the power profile.

what can be the issue behind this problem?

how can solve this issue??

Parents
  • Hi Stanly,

    Thanks for your inquiry. You will have to connect via UART to enable PowerProfiler functionalities. .

    BR,

    PM_Renesas

  • you can see that i have connect in the UART port

  • Hi Stanly,

    Sorry, this kit does not support power profile. because it does not have related circuits.

    Thanks

    JH_Renesas 

  • I have another doubt regarding the connectivity of 2 devices

    I have DA14531 as a peripheral device and it should keep on scanning for the central device

    once the central device is found it should connect with it (one peripheral device for one central device)

    is there any examples available for this, if not then please help me to make is possible 

  • Hi Stanly,

    Thank you for the reply.

    I have DA14531 as a peripheral device and it should keep on scanning for the central device

    once the central device is found it should connect with it (one peripheral device for one central device)

    This is not possible. 
    The Peripheral devices can only Advertise. 
    The Central devices can Scan for the Advertisement packets.
    The Central devices can send a connection request (CONNECT_IND packet) to the Peripheral devices.

    The Central device should scan, find your Peripheral device and initiate the connection.

    Best Regards,
    OV_Renesas

  • My da14531 needs to scan for the device all the time when that specific device mac Id is found then it needs to send connection request to that device, and it should be connected with the specific device

    is there any example available?

  • Hi Stanly,

    Thank you for the reply.
    Please refer on our Git Repo:
    1) Central Example

    2) Central with Security Example


    Best Regards,
    OV_Renesas

  • thanks for the example

    I don't have a DA14531 pro kit for power profile generation and battery life estimation 

    I have attached the HEX file, so that you can help me in power profile and battery life estimation from your kit

    https://1drv.ms/u/c/d0d24dad9c746036/EVdyVE3PAj1Bm_UbmXgtvEABr59bVNSROar0jOpxpFq7ZQ?e=Ly2gXh

  • Hi Stanly,

    Thank you for the reply.
    I tested your firmware with the DA14531MOD Daughterboard and the Development Kit Pro.
    I was not able to wake-up the DA14531 unless I used the HW Reset button (P0_0). 
    I am not sure if that is supposed to be the expected behavior.
    I could see that you are advertising for 1 second and then go back into sleep mode without advertising.



    For the Battery Life Estimation, I would need you to provide me the necessary information in order to test this:

    It highly depends on the configuration you have set on your project.

    Best Regards,
    OV_Renesas

  • we are using 2 buttons to wake up and send advertisement 

    #if defined (__DA14531__)
        #define GPIO_BUTTON_PORT        GPIO_PORT_0
        #define GPIO_BUTTON_PIN         GPIO_PIN_7
        #define GPIO_BUTTON_PIN1         GPIO_PIN_8
    #else

    For battery life estimation

    we are using a 3v CR1220 battery with - 35 MAH

    it will not advertise frequently because we are using DA14531 as a key fob

    there will be no connection between the peripherals and any other devices

    so, NO SPI, I2C

    it only advertises while button is pressed and then it goes to sleep

  • Hi Stanly,

    Thank you for the reply.
    Indeed I was able to wake up the device via P0_7.
    During advertising I get the following current consumption:

    During Sleep mode I get the following current consumption:

    Have you configured your device to perform non connectable Advertising?
    Have you considered using Deep Sleep when you do not want to advertise? 

    I still do not have enough information regarding the Battery Lifetime Estimator.
    Please share the exact application code size, how often are you going to press the button to advertise etc.

    Best Regards,
    OV_Renesas

  • Yes we have configured your device to perform non connectable advertisement 

    I need to configure deep sleep mode can you help me to do it (I can't able to do while seeing the documentation regarding deep sleep)

    I trying to do deep sleep but it won't works properly

    Can you help me out how to add deep sleep mode And battery life estimation

    I am just altering the SDK 6 file program for your project 

    Sdk-6 -> projects ->  target apps ->  ble examples ->  ble app sleepmode

    In this file where to add deep sleepmode

Reply
  • Yes we have configured your device to perform non connectable advertisement 

    I need to configure deep sleep mode can you help me to do it (I can't able to do while seeing the documentation regarding deep sleep)

    I trying to do deep sleep but it won't works properly

    Can you help me out how to add deep sleep mode And battery life estimation

    I am just altering the SDK 6 file program for your project 

    Sdk-6 -> projects ->  target apps ->  ble examples ->  ble app sleepmode

    In this file where to add deep sleepmode

Children
  • Hi Stanly,

    Thank you for the reply.
    For Deep Sleep, please refer on the prox_reporter example and on the following tutorials:
    1) DA1453x & DA1458x Sleep Modes Tutorial — DA1453x & DA1458x Tutorial Sleep Modes (renesas.com)
    2) 3. BLE Development Environment and First Application — DA14585/DA14531 SW Platform Reference Manual (renesas.com)

    You can follow the implementation shown on prox_reporter to enable Deep Sleep on ble_app_sleepmode example as well.

    Best Regards,
    OV_Renesas

  • now I am just trying to work on the examples in the GitHub

    BLE_SDK6_examples/Readme.md at main · dialog-semiconductor/BLE_SDK6_examples · GitHub

    but in central and central security example pops this error

    Rebuild started: Project: central
    *** Using Compiler 'V6.21', folder: 'C:\Keil_v5\ARM\ARMCLANG\Bin'
    Rebuild target 'DA14531'
    assembling startup_DA14531.s...
    compiling arch_console.c...
    compiling system_DA14531.c...
    compiling nmi_handler.c...
    compiling nvds.c...
    compiling hardfault_handler.c...
    compiling arch_main.c...
    compiling arch_sleep.c...
    compiling chacha20.c...
    compiling jump_table.c...
    compiling hash.c...
    compiling arch_rom.c...
    compiling arch_system.c...
    compiling otp_cs.c...
    compiling otp_hdr.c...
    compiling syscntl.c...
    compiling wkupct_quadec.c...
    compiling gpio.c...
    compiling battery.c...
    compiling adc_531.c...
    compiling trng.c...
    compiling spi_flash.c...
    compiling spi_531.c...
    compiling systick.c...
    compiling i2c_eeprom.c...
    compiling uart.c...
    compiling dma.c...
    compiling hw_otpc_531.c...
    compiling rf_585.c...
    compiling i2c.c...
    compiling attm_db_128.c...
    compiling rf_531.c...
    compiling rwip.c...
    compiling ble_arp.c...
    compiling rwble.c...
    compiling prf.c...
    compiling prf_utils.c...
    compiling app_security.c...
    compiling app_task.c...
    compiling app.c...
    compiling app_default_handlers.c...
    compiling app_security_task.c...
    compiling app_entry_point.c...
    compiling app_msg_utils.c...
    compiling app_easy_msg_utils.c...
    compiling app_easy_timer.c...
    compiling app_utils.c...
    compiling app_easy_security.c...
    compiling app_bond_db.c...
    compiling user_custs1_def.c...
    compiling user_custs_config.c...
    compiling user_ble_gatt.c...
    compiling user_ble_gap.c...
    compiling user_periph_setup.c...
    compiling user_central_app.c...
    linking...
    .\out_DA14531\Objects\central_531.axf: Error: L6218E: Undefined symbol my_custom_msg_handlers (referred from arch_rom.o).
    .\out_DA14531\Objects\central_531.axf: Error: L6218E: Undefined symbol patch_func (referred from user_periph_setup.o).
    .\out_DA14531\Objects\central_531.axf: Error: L6218E: Undefined symbol lld_force_timeout_refresh (referred from patch_1.o).
    Not enough information to produce a SYMDEFs file.
    Not enough information to list image symbols.
    Not enough information to list load addresses in the image map.
    Finished: 3 information, 0 warning and 3 error messages.
    ".\out_DA14531\Objects\central_531.axf" - 3 Error(s), 0 Warning(s).
    Target not created.
    Build Time Elapsed:  00:00:04

    how can I resolve this error

  • Hi Stanly,

    Thank you for the reply.
    Which is the SDK version you are trying to use?
    If you are using SDK v6.0.20 or v6.0.22, please make sure you do the following to integrate Git Repo examples:
    1) Make sure you add the system_library_531.c on the sdk_arch folder:

    2) You can do that by right-clicking on the sdk_arch folder:

    3)Navigate on the SDK files on the following path 
    ...\6.0.20.1338\sdk\platform\system_library\src\DA14531

    PS: For different kind of issues, please create new threads. This way when a new user searches for an answer on the communities, they will find it easier.

    Best Regards,
    OV_Renesas

  • Rebuild started: Project: ble_central_with_security
    *** Using Compiler 'V6.21', folder: 'C:\Keil_v5\ARM\ARMCLANG\Bin'
    Rebuild target 'DA14531'
    compiling system_DA14531.c...
    assembling startup_DA14531.s...
    compiling hardfault_handler.c...
    compiling nmi_handler.c...
    compiling arch_console.c...
    compiling nvds.c...
    compiling arch_main.c...
    compiling jump_table.c...
    compiling arch_sleep.c...
    compiling arch_system.c...
    compiling arch_rom.c...
    compiling chacha20.c...
    compiling hash.c...
    compiling otp_hdr.c...
    compiling otp_cs.c...
    compiling system_library_531.c...
    compiling syscntl.c...
    compiling gpio.c...
    compiling wkupct_quadec.c...
    compiling battery.c...
    compiling trng.c...
    compiling spi_flash.c...
    compiling i2c_eeprom.c...
    compiling systick.c...
    compiling adc_531.c...
    compiling spi_531.c...
    compiling uart.c...
    compiling hw_otpc_531.c...
    compiling i2c.c...
    compiling rf_585.c...
    compiling rwble.c...
    compiling rwip.c...
    compiling ble_arp.c...
    compiling rf_531.c...
    compiling attm_db_128.c...
    compiling custom_common.c...
    compiling custs1.c...
    compiling custs1_task.c...
    compiling custs2.c...
    compiling custs2_task.c...
    compiling prf.c...
    compiling prf_utils.c...
    compiling diss.c...
    compiling diss_task.c...
    compiling app_default_handlers.c...
    compiling app.c...
    compiling app_task.c...
    compiling app_security.c...
    compiling app_security_task.c...
    compiling app_diss.c...
    compiling app_diss_task.c...
    compiling app_entry_point.c...
    compiling app_msg_utils.c...
    compiling app_easy_msg_utils.c...
    compiling app_easy_security.c...
    compiling app_easy_timer.c...
    compiling app_customs.c...
    compiling app_customs_task.c...
    compiling app_customs_common.c...
    compiling app_bond_db.c...
    compiling app_utils.c...
    compiling user_custs_config.c...
    compiling user_custs1_def.c...
    compiling user_periph_setup.c...
    compiling user_central_scanner.c...
    compiling user_security.c...
    linking...
    .\out_531\ble_central_with_security_531.axf: Error: L6221E: Execution region ER_ZI with Execution range [0x07fc74e0,0x07fc85e0) overlaps with Execution region RET_DATA with Execution range [0x07fc83c0,0x07fc88c4).
    .\out_531\ble_central_with_security_531.axf: Error: L6221E: Execution region ER_NZI with Execution range [0x07fc85e0,0x07fc89ec) overlaps with Execution region RET_DATA with Execution range [0x07fc83c0,0x07fc88c4).
    .\out_531\ble_central_with_security_531.axf: Error: L6221E: Execution region ER_NZI with Execution range [0x07fc85e0,0x07fc89ec) overlaps with Execution region RET_HEAP_DB with Execution range [0x07fc88c4,0x07fc8cd0).
    Not enough information to produce a SYMDEFs file.
    Finished: 1 information, 0 warning and 3 error messages.
    ".\out_531\ble_central_with_security_531.axf" - 3 Error(s), 0 Warning(s).
    Target not created.
    Build Time Elapsed:  00:00:19

    this error pops in central security example coding

  • Hi Stanly,

    Thank you for the reply.
    On your Options for Target settings please check C/C++ tab and make sure that Link-Time Optimization is enabled:


    Best Regards,
    OV_Renesas

  • thanks, a lot all the errors are cleared

    but new error pops while debug

    Rebuild started: Project: ble_central_with_security
    *** Using Compiler 'V6.21', folder: 'C:\Keil_v5\ARM\ARMCLANG\Bin'
    Rebuild target 'DA14531'
    assembling startup_DA14531.s...
    compiling system_DA14531.c...
    compiling nvds.c...
    compiling nmi_handler.c...
    compiling arch_console.c...
    compiling hardfault_handler.c...
    compiling arch_main.c...
    compiling jump_table.c...
    compiling arch_sleep.c...
    compiling chacha20.c...
    compiling hash.c...
    compiling arch_rom.c...
    compiling otp_hdr.c...
    compiling arch_system.c...
    compiling otp_cs.c...
    compiling syscntl.c...
    compiling wkupct_quadec.c...
    compiling system_library_531.c...
    compiling gpio.c...
    compiling battery.c...
    compiling trng.c...
    compiling spi_flash.c...
    compiling i2c_eeprom.c...
    compiling systick.c...
    compiling adc_531.c...
    compiling spi_531.c...
    compiling uart.c...
    compiling hw_otpc_531.c...
    compiling i2c.c...
    compiling rf_585.c...
    compiling attm_db_128.c...
    compiling rf_531.c...
    compiling rwip.c...
    compiling custom_common.c...
    compiling custs1.c...
    compiling ble_arp.c...
    compiling rwble.c...
    compiling custs1_task.c...
    compiling custs2.c...
    compiling prf.c...
    compiling custs2_task.c...
    compiling prf_utils.c...
    compiling diss.c...
    compiling diss_task.c...
    compiling app_default_handlers.c...
    compiling app.c...
    compiling app_security.c...
    compiling app_task.c...
    compiling app_diss_task.c...
    compiling app_diss.c...
    compiling app_security_task.c...
    compiling app_entry_point.c...
    compiling app_easy_msg_utils.c...
    compiling app_msg_utils.c...
    compiling app_customs_task.c...
    compiling app_easy_timer.c...
    compiling app_customs.c...
    compiling app_easy_security.c...
    compiling app_customs_common.c...
    compiling app_utils.c...
    compiling app_bond_db.c...
    compiling user_custs_config.c...
    compiling user_custs1_def.c...
    compiling user_periph_setup.c...
    compiling user_central_scanner.c...
    compiling user_security.c...
    linking...
    Program Size: Code=20828 RO-data=1868 RW-data=12 ZI-data=9888  
    FromELF: creating hex file...
    ".\out_531\ble_central_with_security_531.axf" - 0 Error(s), 0 Warning(s).
    Build Time Elapsed:  00:00:04
    Load "D:\\BLE_SDK6_examples-main\\connectivity\\central_Security_Demo\\project_environment\\out_531\\ble_central_with_security_531.axf" 
    Set JLink Project File to "D:\BLE_SDK6_examples-main\connectivity\central_Security_Demo\project_environment\JLinkSettings.ini"
    * JLink Info: Device "CORTEX-M0" selected.
     
    JLink info:
    ------------
    DLL: V7.92k, compiled Oct 18 2023 14:58:31
    Firmware: J-Link OB-SAM3U128 V3 compiled Apr 11 2024 17:43:56
    Hardware: V3.00
    S/N : 483052500 
     
    * JLink Info: Found SW-DP with ID 0x0BC11477
    * JLink Info: DPIDR: 0x0BC11477
    * JLink Info: CoreSight SoC-400 or earlier
    * JLink Info: Scanning AP map to find all available APs
    * JLink Info: AP[1]: Stopped AP scan as end of AP map has been reached
    * JLink Info: AP[0]: AHB-AP (IDR: 0x04770031)
    * JLink Info: Iterating through AP map to find AHB-AP to use
    * JLink Info: AP[0]: Core found
    * JLink Info: AP[0]: AHB-AP ROM base: 0xE00FF000
    * JLink Info: CPUID register: 0x410CC601. Implementer code: 0x41 (ARM)
    * JLink Info: Found Cortex-M0 r0p1, Little endian.
    * JLink Info: FPUnit: 4 code (BP) slots and 0 literal slots
    * JLink Info: CoreSight components:
    * JLink Info: ROMTbl[0] @ E00FF000
    * JLink Info: [0][0]: E000E000 CID B105E00D PID 000BB008 SCS
    * JLink Info: [0][1]: E0001000 CID B105E00D PID 000BB00A DWT
    * JLink Info: [0][2]: E0002000 CID B105E00D PID 000BB00B FPB
    ROMTableAddr = 0xE00FF000
    * JLink Info: Reset: Halt core after reset via DEMCR.VC_CORERESET.
    * JLink Info: Reset: Reset device via AIRCR.SYSRESETREQ.
     
    Target info:
    ------------
    Device: ARMCM0P
    VTarget = 3.300V
    State of Pins: 
    TCK: 0, TDI: 1, TDO: 1, TMS: 0, TRES: 1, TRST: 1
    Hardware-Breakpoints: 4
    Software-Breakpoints: 8192
    Watchpoints:          2
    JTAG speed: 2667 kHz
     
    No Algorithm found for: 07FC0000H - 07FC00A7H
    No Algorithm found for: 07FC0110H - 07FC591BH
    Erase skipped!
    Error: Flash Download failed  -  "Cortex-M0+"
    Flash Load finished at 15:56:27

  • Hi Stanly,

    Thank you for the reply.
    Go again on Options for Target, on Utilities tab and select the Use External Tool for Flash Programming option:

    The J-Link debugger should be able to connect now.

    Best Regards,
    OV_Renesas

  • Set JLink Project File to "D:\BLE_SDK6_examples-main\connectivity\central_Security_Demo\project_environment\JLinkSettings.ini"* JLink Info: Device "CORTEX-M0" selected.
     
    JLink info:
    ------------
    DLL: V7.92k, compiled Oct 18 2023 14:58:31
    Firmware: J-Link OB-SAM3U128 V3 compiled Apr 11 2024 17:43:56
    Hardware: V3.00
    S/N : 483052500 
     
    * JLink Info: Found SW-DP with ID 0x0BC11477
    * JLink Info: DPIDR: 0x0BC11477
    * JLink Info: CoreSight SoC-400 or earlier
    * JLink Info: Scanning AP map to find all available APs
    * JLink Info: AP[1]: Stopped AP scan as end of AP map has been reached
    * JLink Info: AP[0]: AHB-AP (IDR: 0x04770031)
    * JLink Info: Iterating through AP map to find AHB-AP to use
    * JLink Info: AP[0]: Core found
    * JLink Info: AP[0]: AHB-AP ROM base: 0xE00FF000
    * JLink Info: CPUID register: 0x410CC601. Implementer code: 0x41 (ARM)
    * JLink Info: Found Cortex-M0 r0p1, Little endian.
    * JLink Info: FPUnit: 4 code (BP) slots and 0 literal slots
    * JLink Info: CoreSight components:
    * JLink Info: ROMTbl[0] @ E00FF000
    * JLink Info: [0][0]: E000E000 CID B105E00D PID 000BB008 SCS
    * JLink Info: [0][1]: E0001000 CID B105E00D PID 000BB00A DWT
    * JLink Info: [0][2]: E0002000 CID B105E00D PID 000BB00B FPB
    ROMTableAddr = 0xE00FF000
    * JLink Info: Reset: Halt core after reset via DEMCR.VC_CORERESET.
    * JLink Info: Reset: Reset device via AIRCR.SYSRESETREQ.
     
    Target info:
    ------------
    Device: ARMCM0P
    VTarget = 3.300V
    State of Pins: TCK: 0, TDI: 1, TDO: 1, TMS: 0, TRES: 1, TRST: 1
    Hardware-Breakpoints: 4
    Software-Breakpoints: 8192
    Watchpoints:          2
    JTAG speed: 2667 kHz
     
    Include "D:\\BLE_SDK6_examples-main\\connectivity\\central_Security_Demo\\project_environment\\..\\..\\..\\..\\..\\sdk\\common_project_files\\misc\\jlink_DA14531.ini" 
    ________^
    *** error 56: cannot open file

    this error pops while debugging 

    the setting i have is

    these are my settings

  • Hi Stanly,

    Thank you for the reply.
    From the screenshots you have shared, is that you are trying to debug the project directly from the BLE-SDK examples folder of the GitRepo.
    You should copy/paste the example you are interested in inside your SDK with the rest of the SDK examples included.
    Then use the python script included to fix the paths to your SDK. 
    The rest of the settings seems OK to me. 
    Keil is trying to locate the jlink_DA14531.ini which is part of the SDK folders and not from the GitRepo folder. This is why you cannot debug.

    Best Regards,
    OV_Renesas