we flash .img file in da16600 module .once flashing completed but it's getting error watch dog timer its come lopping .same error getting .i attach error log also,i need solution asap, i need full information with documentation also.

We tried flashing the SDK which is provided by the reneses on DA16600 thorugh UART.After flashing we faced the watchdog timer expired isssue which resulted in looping of same thing agin and again.I have attcahed the log of what we got in the terminal here. Please provide the answer with complete documentation.

Wakeup source is 0x4
[dpm_init_retmemory] DPM INIT CONFIGURATION(1)


******************************************************
* DA16600 SDK Information
* ---------------------------------------------------
*
* - CPU Type : Cortex-M4 (120MHz)
* - OS Type : FreeRTOS 10.4.3
* - Serial Flash : 4 MB
* - SDK Version : V3.2.8.1 GEN
* - F/W Version : FRTOS-GEN01-01-2aa77df370-006629
* - F/W Build Time : Nov 7 2023 13:10:35
* - Boot Index : 0
*
******************************************************

gpio wakeup enable 00000402
[combo][iot_sensor]
is_provisioned = 0
is_sensor_started = 0
[combo] dpm_boot_type = 0

>>> UART1 : Clock=80000000, BaudRate=115200
>>> UART1 : DMA Enabled ...
[combo] BLE_BOOT_MODE_0
[combo] BLE FW VER to transfer ....
>>> v_6.0.14.1114.3 (id=1) at bank_1
[combo] S/W Reset................................................................................................................ [Wdog] callback.func 0x182c41
Status: Enabled
Task mask
01234567890123456789012345678901|01234567890123456789012345678901|
11100000000000000000000000000000|00000000000000000000000000000000|

Monitored mask
01234567890123456789012345678901|01234567890123456789012345678901|
10000000000000000000000000000000|00000000000000000000000000000000|

Notified mask
01234567890123456789012345678901|01234567890123456789012345678901|
01100000000000000000000000000000|00000000000000000000000000000000|

IDLE task: -1
Max task id: 2
Rescale time: 500(unit of time: 10 msec)
Task information
ID: 0, latency:0, Task handle: 0x000b4140, Name: system_laun
ID: 1, latency:0, Task handle: 0x000b90b0, Name: Console_OUT
ID: 2, latency:0, Task handle: 0x000bb0b0, Name: Console_IN


[Watch Dog Timer Expired]

Register-Dump
R0 :00000000, R1 :a5a5a5a5, R2 :a5a5a5a5, R3 :00000001
R4 :000ad5c0, R5 :000b5668, R6 :a5a5a5a5, R7 :a5a5a5a5
R8 :a5a5a5a5, R9 :a5a5a5a5, R10 :a5a5a5a5, R11 :a5a5a5a5
R12 :a5a5a5a5, SP :000b4340, LR :001a1cf1, PC :001a1cd6
PSR :61000000, EXC :00182f2d,
Status Register
SHCSR :00000000, CFSR :00000000, HFSR :00000000
DFSR :00000000, MMFAR :e000ed34, BFAR :e000ed38
AFSR :00000000,
SysInfo
SICS[0] = 04300000
SICS[1] = 00000000
SICS[2] = 00000000
SICS[3] = 00000000
SICS[4] = 00000000
SICS[5] = ffffc000


Current Thread
Thread: IDLE
stack ptr : 000b42fc
stack base: 000b41c0
stack end : 000b4348
stack high: 000b42fc
max usage : 0000004d
suspend : 00000000

Thread Stack (32)
[0x000b42fc] : 000AC488 A5A5A5A5 A5A5A5A5 A5A5A5A5 A5A5A5A5 A5A5A5A5 A5A5A5A5 A5A5A5A5
[0x000b431c] : FFFFFFFD 00000000 A5A5A5A5 A5A5A5A5 00000001 A5A5A5A5 001A1CF1 001A1CD6
[0x000b433c] : 61000000 A5A5A5A5 001A0DDD A5A5A5A5 A5A5A5A5 00000000 80000080 B698CDC7
[0x000b435c] : B9D639D6 B1936B82 D9524A71 000B42FC A42B3680 000AC204 000AC204 000B4368

Parents
  • Hi There,

    Happy New Year!
    Thank you for posting your question online.
    This is a known issue, caused by the DA14531 SW Reset not being able to be detected.
    Please find attached the DA16600_ble_sw_reset_fix.patch and apply it on the FreeRTOS SDK v3.2.8.1.

    • The BLE SW reset should be checked and then rebooted.
    • The BLE SW reset should do before the flash related functions because it takes some delay to send BLE SW reset command.
    • After fix/updating with the patch, the BLE related booting error was fixed.

    Please share any feedback!
    P.S. The patch will be included in the next SDK release.

    Best Regards,
    OV_Renesas


     DA16600_ble_sw_reset_fix.patch

  • Hi, Happy new year i am new to this can u elaborate the procedure to apply the patch.

  • Hi There,

    Thank you for the replies.
    Did you follow the UM-WI-006 DA16200 DA16600 Hardware Design Guide (renesas.com) while designing the custom board?

    Do you have a Host MCU on your custom board or any sensor?
    The RTC_WAKE_UP pin should have an Input High voltage > 2.2V @ 3.3VDD (I/O voltage check) with a 4.7kOhm pull-down resistor. Can be removed and RTC_WAKE_UP1/2 can be connected to GND directly when not used. 

    Best Regards,
    OV_Renesas

  • Hai, I am just trying to communicate with the module using USB TTL for that I have connected 3V3 to VBAT_BLE, VBAT_3V3, VDD_DIO1, VDD_DIO2,  RTC_WAKE_UP2 to GND. I am getting Wrong Image error now from the module.

    Boot Err: wrong image [40000000](04)


    *********************************************
    * FCI FC9K MaskROM BootLoader
    * Cortex-M4 (XTAL 40000 KHz, SYS 120000 KHz)
    * Console Baud Rate : 0 (00000000)
    * HW Version Num. : fc905010
    * Build Option : RomALL
    * RoSDK Date & Time : Mar 13 2019 13:05:45
    * Build Date & Time : Mar 13 2019 13:11:24
    * http://www.fci.co.kr
    *********************************************

  • I tried with a new module. At first the module is displayed in the blue-tooth terminal, then it is not displaying 
    I'm facing with the following error 

    >>> P.TIM is relocated to RETMEM (0x20f835c0, 3)
    [dpm_init_retmemory] DPM INIT CONFIGURATION(1)

    Wakeup source is 0x4


    **************************************************
    * DA16200 SDK Information
    * -----------------------------------------------
    *
    * - CPU Type : Cortex-M4 (80MHz)
    * - OS Type : ThreadX 5.7
    * - Serial Flash : 4 MB
    * - SDK Version : V2.3.2.0 CM
    * - F/W Version : RTOS-GEN01-01-12627-000000
    * : SLIB-GEN01-01-12283-000000
    * - F/W Build Time : Sep 23 2020 13:27:48
    * - Boot Index : 1
    *
    **************************************************

    gpio wakeup enable 00000402
    [combo] dpm_boot_type = 0
    ER[[OOPS Dump : c0f0]]
    [[Stack Fault]]
    --RTC Time : 00000000.00000c97

    Register-Dump
    R0 :00080778, R1 :00003a05, R2 :00000000, R3 :000b4cb4
    R4 :00000000, R5 :000b4cb4, R6 :00080774, R7 :00080778
    R8 :000b4cb4, R9 :ffffffff, R10 :001220d4, R11 :000b4bf8
    R12 :00000000, SP :000b4b38, LR :0000400d, PC :000

    Kindly provide a solution for the above issue 

  • Hi There,

    Thank you for the replies.

    Hai, I am just trying to communicate with the module using USB TTL for that I have connected 3V3 to VBAT_BLE, VBAT_3V3, VDD_DIO1, VDD_DIO2,  RTC_WAKE_UP2 to GND. I am getting Wrong Image error now from the module.

    Boot Err: wrong image [40000000](04)

    Since it is a custom board we would require to look at the schematic to understand why this is happening.
    Before, the same images worked but resulted in a Hard Fault?


    **************************************************
    * DA16200 SDK Information
    * -----------------------------------------------
    *
    * - CPU Type : Cortex-M4 (80MHz)
    * - OS Type : ThreadX 5.7
    * - Serial Flash : 4 MB
    * - SDK Version : V2.3.2.0 CM
    * - F/W Version : RTOS-GEN01-01-12627-000000
    * : SLIB-GEN01-01-12283-000000
    * - F/W Build Time : Sep 23 2020 13:27:48
    * - Boot Index : 1
    *
    **************************************************

    This is a quite old SDK image and it is for DA16200, not for DA16600. 
    The 2nd module is a DA16600MOD or a DA16200MOD?

    Best Regards,
    OV_Renesas

  • Hello,  This is how I configured the connections. Is this setup correct ? The second module is DA16600MOD, and that image was preloaded in that module. 

  • Hi There,

    Thank you for the reply.
    Please refer on the DA16600MOD Datasheet, on section 7. Application Schematic

    I do not see the necessary capacitors needed.
    For the DA16600MOD:


    1.Pin 28 (VBAT_3v3): Operating voltage 2.1V~3.6V (Typ. 3.3V), 10uF bypass capacitor

    2.Pin51 (VBAT_BLE): Operating voltage 1.8V~3.3V (Max 3.3V), 10uF bypass capacitor

    3.Pin 17,40 ( VDD_DIO1, VDD_DIO2): Check I/O voltage of MCU (1.8V ~3.3V).

    4.Pin 27: Should be connected to GND as well.

    We have also contacted your local FAE. They should reach out to you regarding your issue so you could share with them all the details.

    Best Regards,
    OV_Renesas

  • hai there, can i get the contact details of local technical person

  • Hi There,

    Thank you for the reply.

    can i get the contact details of local technical person

    I have asked the local FAE team to share with me the contact details you are going to need. I will reach out to you directly when I have a response.

    In the meantime, please try to manually download, via Tera Term as shown in the previous answers, the images attached on the FreeRTOS_v3.2.8.1_Images.zip file. It is the default getting started project and it works as expected on my side on the DA16600MOD EVK.
    You will not need to change the FBOOT image.
    FreeRTOS_v3.2.8.1_Images.zip

    Best Regards,
    OV_Renesas

  • Hai, I am still getting the Wrong image error even after flashing the patched image. I dont have DA16600MOD EVK board with me. Can you please share the working image and schematics of DA16600MOD custom board.

    wrong magic code ffffffff-4b394346 i am getting this error code

  • Hi There,

    Thank you for the reply.
    We received a similar question on our private platform from your Distributor FAE. 
    We will provide you the answer we gave them:
    There are 2 known issues for the DA16600 in the FreeRTOS SDK v3.2.8.1.
    One is related to the BLE SW reset which is the patch you have attached and there is another issue with the WatchDog timer.
    Please find attached the DA16600_watchdog_repeated_log_fix.patch file. 
    I applied the patch on the FreeRTOS SDK v3.2.8.1 and then compiled the DA16600 getting_started example (with AT commands enabled). 
    Please find the attached the img.zip file which contains the DA16600MOD images.
    Please also find attached the DA16600_get_started_watchdog_patch.log file with the Logs when running the specific images.

    Note: Both patches will be applied on the next SDK release.

    Best Regards,
    OV_Renesas

    DA16600_get_started_watchdog_patch.log
    Wakeup source is 0x4 
    [dpm_init_retmemory] DPM INIT CONFIGURATION(1)
    
    
    	******************************************************
    	*             DA16600 SDK Information
    	* --------------------------------------------------- 
    	*
    	* - CPU Type        : Cortex-M4 (120MHz)
    	* - OS Type         : FreeRTOS 10.4.3
    	* - Serial Flash    : 4 MB
    	* - SDK Version     : V3.2.8.1 GEN
    	* - F/W Version     : FRTOS-GEN01-01-2aa77df370-006629
    	* - F/W Build Time  : Feb 13 2024 13:31:21
    	* - Boot Index      : 0
    	*
    	******************************************************
    
    gpio wakeup enable 00000402
    [combo][iot_sensor]
       is_provisioned = 0
       is_sensor_started = 0 
    [combo] dpm_boot_type = 0
    
    >>> UART1 : Clock=80000000, BaudRate=115200
    >>> UART1 : DMA Enabled ...
    [combo] BLE_BOOT_MODE_0
    [combo] BLE FW VER to transfer .... 
       >>> v_6.0.14.1114.3 (id=1) at bank_1
    [combo] S/W Reset.
    RTC switched to XTAL
    [combo] BLE FW transfer done
    
    
    System Mode : Station Only (0)
    >>> Start DA16X Supplicant ...
    >>> DA16x Supp Ver2.7 - 2022_03
    >>> MAC address (sta0) : d4:3d:39:40:29:42
    >>> sta0 interface add OK
    >>> Start STA mode...
    by default, rf_meas_btcoex(1, 0, 0) 
    
    >>> UART2 : Clock=80000000, BaudRate=115200
    >>> UART2 : DMA Enabled ...
    <<< GAPM_DEVICE_READY_IND 
    IoT dev_name="DA16600-2942", len=12
    [combo] Advertising...
    
    Wakeup source is 0x4 
    [dpm_init_retmemory] DPM INIT CONFIGURATION(1)
    
    
    	******************************************************
    	*             DA16600 SDK Information
    	* --------------------------------------------------- 
    	*
    	* - CPU Type        : Cortex-M4 (120MHz)
    	* - OS Type         : FreeRTOS 10.4.3
    	* - Serial Flash    : 4 MB
    	* - SDK Version     : V3.2.8.1 GEN
    	* - F/W Version     : FRTOS-GEN01-01-2aa77df370-006629
    	* - F/W Build Time  : Feb 13 2024 13:31:21
    	* - Boot Index      : 0
    	*
    	******************************************************
    
    gpio wakeup enable 00000402
    [combo][iot_sensor]
       is_provisioned = 0
       is_sensor_started = 0 
    [combo] dpm_boot_type = 0
    
    >>> UART1 : Clock=80000000, BaudRate=115200
    >>> UART1 : DMA Enabled ...
    [combo] BLE_BOOT_MODE_0
    [combo] BLE FW VER to transfer .... 
       >>> v_6.0.14.1114.3 (id=1) at bank_1
    [combo] S/W Reset.
    RTC switched to XTAL
    [combo] BLE FW transfer done
    
    
    System Mode : Station Only (0)
    >>> Start DA16X Supplicant ...
    >>> DA16x Supp Ver2.7 - 2022_03
    >>> MAC address (sta0) : d4:3d:39:40:29:42
    >>> sta0 interface add OK
    >>> Start STA mode...
    by default, rf_meas_btcoex(1, 0, 0) 
    
    >>> UART2 : Clock=80000000, BaudRate=115200
    >>> UART2 : DMA Enabled ...
    <<< GAPM_DEVICE_READY_IND 
    IoT dev_name="DA16600-2942", len=12
    [combo] Advertising...
    
    Wakeup source is 0x4 
    [dpm_init_retmemory] DPM INIT CONFIGURATION(1)
    
    
    	******************************************************
    	*             DA16600 SDK Information
    	* --------------------------------------------------- 
    	*
    	* - CPU Type        : Cortex-M4 (120MHz)
    	* - OS Type         : FreeRTOS 10.4.3
    	* - Serial Flash    : 4 MB
    	* - SDK Version     : V3.2.8.1 GEN
    	* - F/W Version     : FRTOS-GEN01-01-2aa77df370-006629
    	* - F/W Build Time  : Feb 13 2024 13:31:21
    	* - Boot Index      : 0
    	*
    	******************************************************
    
    gpio wakeup enable 00000402
    [combo][iot_sensor]
       is_provisioned = 0
       is_sensor_started = 0 
    [combo] dpm_boot_type = 0
    
    >>> UART1 : Clock=80000000, BaudRate=115200
    >>> UART1 : DMA Enabled ...
    [combo] BLE_BOOT_MODE_0
    [combo] BLE FW VER to transfer .... 
       >>> v_6.0.14.1114.3 (id=1) at bank_1
    [combo] S/W Reset.
    RTC switched to XTAL
    [combo] BLE FW transfer done
    
    
    System Mode : Station Only (0)
    >>> Start DA16X Supplicant ...
    >>> DA16x Supp Ver2.7 - 2022_03
    >>> MAC address (sta0) : d4:3d:39:40:29:42
    >>> sta0 interface add OK
    >>> Start STA mode...
    by default, rf_meas_btcoex(1, 0, 0) 
    
    >>> UART2 : Clock=80000000, BaudRate=115200
    >>> UART2 : DMA Enabled ...
    <<< GAPM_DEVICE_READY_IND 
    IoT dev_name="DA16600-2942", len=12
    [combo] Advertising...
    

    4721.img.zipDA16600_watchdog_repeated_log_fix.patch

Reply
  • Hi There,

    Thank you for the reply.
    We received a similar question on our private platform from your Distributor FAE. 
    We will provide you the answer we gave them:
    There are 2 known issues for the DA16600 in the FreeRTOS SDK v3.2.8.1.
    One is related to the BLE SW reset which is the patch you have attached and there is another issue with the WatchDog timer.
    Please find attached the DA16600_watchdog_repeated_log_fix.patch file. 
    I applied the patch on the FreeRTOS SDK v3.2.8.1 and then compiled the DA16600 getting_started example (with AT commands enabled). 
    Please find the attached the img.zip file which contains the DA16600MOD images.
    Please also find attached the DA16600_get_started_watchdog_patch.log file with the Logs when running the specific images.

    Note: Both patches will be applied on the next SDK release.

    Best Regards,
    OV_Renesas

    DA16600_get_started_watchdog_patch.log
    Wakeup source is 0x4 
    [dpm_init_retmemory] DPM INIT CONFIGURATION(1)
    
    
    	******************************************************
    	*             DA16600 SDK Information
    	* --------------------------------------------------- 
    	*
    	* - CPU Type        : Cortex-M4 (120MHz)
    	* - OS Type         : FreeRTOS 10.4.3
    	* - Serial Flash    : 4 MB
    	* - SDK Version     : V3.2.8.1 GEN
    	* - F/W Version     : FRTOS-GEN01-01-2aa77df370-006629
    	* - F/W Build Time  : Feb 13 2024 13:31:21
    	* - Boot Index      : 0
    	*
    	******************************************************
    
    gpio wakeup enable 00000402
    [combo][iot_sensor]
       is_provisioned = 0
       is_sensor_started = 0 
    [combo] dpm_boot_type = 0
    
    >>> UART1 : Clock=80000000, BaudRate=115200
    >>> UART1 : DMA Enabled ...
    [combo] BLE_BOOT_MODE_0
    [combo] BLE FW VER to transfer .... 
       >>> v_6.0.14.1114.3 (id=1) at bank_1
    [combo] S/W Reset.
    RTC switched to XTAL
    [combo] BLE FW transfer done
    
    
    System Mode : Station Only (0)
    >>> Start DA16X Supplicant ...
    >>> DA16x Supp Ver2.7 - 2022_03
    >>> MAC address (sta0) : d4:3d:39:40:29:42
    >>> sta0 interface add OK
    >>> Start STA mode...
    by default, rf_meas_btcoex(1, 0, 0) 
    
    >>> UART2 : Clock=80000000, BaudRate=115200
    >>> UART2 : DMA Enabled ...
    <<< GAPM_DEVICE_READY_IND 
    IoT dev_name="DA16600-2942", len=12
    [combo] Advertising...
    
    Wakeup source is 0x4 
    [dpm_init_retmemory] DPM INIT CONFIGURATION(1)
    
    
    	******************************************************
    	*             DA16600 SDK Information
    	* --------------------------------------------------- 
    	*
    	* - CPU Type        : Cortex-M4 (120MHz)
    	* - OS Type         : FreeRTOS 10.4.3
    	* - Serial Flash    : 4 MB
    	* - SDK Version     : V3.2.8.1 GEN
    	* - F/W Version     : FRTOS-GEN01-01-2aa77df370-006629
    	* - F/W Build Time  : Feb 13 2024 13:31:21
    	* - Boot Index      : 0
    	*
    	******************************************************
    
    gpio wakeup enable 00000402
    [combo][iot_sensor]
       is_provisioned = 0
       is_sensor_started = 0 
    [combo] dpm_boot_type = 0
    
    >>> UART1 : Clock=80000000, BaudRate=115200
    >>> UART1 : DMA Enabled ...
    [combo] BLE_BOOT_MODE_0
    [combo] BLE FW VER to transfer .... 
       >>> v_6.0.14.1114.3 (id=1) at bank_1
    [combo] S/W Reset.
    RTC switched to XTAL
    [combo] BLE FW transfer done
    
    
    System Mode : Station Only (0)
    >>> Start DA16X Supplicant ...
    >>> DA16x Supp Ver2.7 - 2022_03
    >>> MAC address (sta0) : d4:3d:39:40:29:42
    >>> sta0 interface add OK
    >>> Start STA mode...
    by default, rf_meas_btcoex(1, 0, 0) 
    
    >>> UART2 : Clock=80000000, BaudRate=115200
    >>> UART2 : DMA Enabled ...
    <<< GAPM_DEVICE_READY_IND 
    IoT dev_name="DA16600-2942", len=12
    [combo] Advertising...
    
    Wakeup source is 0x4 
    [dpm_init_retmemory] DPM INIT CONFIGURATION(1)
    
    
    	******************************************************
    	*             DA16600 SDK Information
    	* --------------------------------------------------- 
    	*
    	* - CPU Type        : Cortex-M4 (120MHz)
    	* - OS Type         : FreeRTOS 10.4.3
    	* - Serial Flash    : 4 MB
    	* - SDK Version     : V3.2.8.1 GEN
    	* - F/W Version     : FRTOS-GEN01-01-2aa77df370-006629
    	* - F/W Build Time  : Feb 13 2024 13:31:21
    	* - Boot Index      : 0
    	*
    	******************************************************
    
    gpio wakeup enable 00000402
    [combo][iot_sensor]
       is_provisioned = 0
       is_sensor_started = 0 
    [combo] dpm_boot_type = 0
    
    >>> UART1 : Clock=80000000, BaudRate=115200
    >>> UART1 : DMA Enabled ...
    [combo] BLE_BOOT_MODE_0
    [combo] BLE FW VER to transfer .... 
       >>> v_6.0.14.1114.3 (id=1) at bank_1
    [combo] S/W Reset.
    RTC switched to XTAL
    [combo] BLE FW transfer done
    
    
    System Mode : Station Only (0)
    >>> Start DA16X Supplicant ...
    >>> DA16x Supp Ver2.7 - 2022_03
    >>> MAC address (sta0) : d4:3d:39:40:29:42
    >>> sta0 interface add OK
    >>> Start STA mode...
    by default, rf_meas_btcoex(1, 0, 0) 
    
    >>> UART2 : Clock=80000000, BaudRate=115200
    >>> UART2 : DMA Enabled ...
    <<< GAPM_DEVICE_READY_IND 
    IoT dev_name="DA16600-2942", len=12
    [combo] Advertising...
    

    4721.img.zipDA16600_watchdog_repeated_log_fix.patch

Children