⚠️
Hi there.. thanks for coming to the forums. Exciting news! we’re now in the process of moving to our new forum platform that will offer better functionality and is contained within the main Dialog website. All posts and accounts have been migrated. We’re now accepting traffic on the new forum only - please POST any new threads at//www.wsdof.com/support. We’ll be fixing bugs / optimising the searching and tagging over the coming days.
5 posts / 0 new
Last post
NickYang
Offline
Last seen:1 year 2 months ago
加入:2019-07-26 03:53
DA14695 SUOTA failed

Hi Experts!

I have a trouble about SUOTA .

My hardware use DA14695 as MCU,16MB gd25LE128 as qspiFlash.My project is based /pxp_reporter.it worked perfect before I adjusted ROMSize to 2048*1024。

I made the following adjustments。

1>made our custom qspi_gd25LE128.h,rebuild uartboot&cli_programmer

2>redifine dg_configQSPI_CODE_SIZE_AA, add a new partition_table

#define dg_configQSPI_CODE_SIZE_AA (2048*1024) /* Take into account CMI firmware size */
#define NVMS_PRODUCT_HEADER_PART_START 0x000000 #define NVMS_PRODUCT_HEADER_PART_SIZE 0x002000 #define NVMS_FW_EXEC_PART_START 0x002000 /* Alignment to 512KB is dictated by the default FLASH_REGION_SIZE. */ #define NVMS_FW_EXEC_PART_SIZE 0x400000 /* +----------------512KB---------------------+ */ #define NVMS_GENERIC_PART_START 0x420000 #define NVMS_GENERIC_PART_SIZE 0x020000 #define NVMS_PLATFORM_PARAMS_PART_START 0x500000 #define NVMS_PLATFORM_PARAMS_PART_SIZE 0x0FF000 #define NVMS_PARAM_PART_START 0x6FF000 #define NVMS_PARAM_PART_SIZE 0x001000 /* Recommended location, 4KB before the end of the 1st flash section. */ /* +------------------2MB---------------------+ */ #define NVMS_FW_UPDATE_PART_START 0x700000 /* Alignment to 512KB is dictated by the default FLASH_REGION_SIZE. */ #define NVMS_FW_UPDATE_PART_SIZE 0x400000 /* This size is dictated by the default (512KB) FLASH_REGION_SIZE. */ #define NVMS_LOG_PART_START 0xB00000 #define NVMS_LOG_PART_SIZE 0x0FF000 #define NVMS_PARTITION_TABLE_START 0xBFF000 #define NVMS_PARTITION_TABLE_SIZE 0x001000 /* Recommended location, 4KB before the end of the flash. */ #define NVMS_USER_PART_START 0xC00000 #define NVMS_USER_PART_SIZE 0x100000 PARTITION2( NVMS_PRODUCT_HEADER_PART , 0 ) PARTITION2( NVMS_FW_EXEC_PART , 0 ) PARTITION2( NVMS_GENERIC_PART , PARTITION_FLAG_VES ) PARTITION2( NVMS_PLATFORM_PARAMS_PART , PARTITION_FLAG_READ_ONLY ) PARTITION2( NVMS_PARAM_PART , 0 ) PARTITION2( NVMS_FW_UPDATE_PART , 0 ) PARTITION2( NVMS_LOG_PART , 0 ) PARTITION2( NVMS_PARTITION_TABLE , PARTITION_FLAG_READ_ONLY ) PARTITION2( NVMS_USER_PART , 0 )

3>added some code and The compiled bin file size is 655,004 bytes.
4>burn CS code in OPT,set CACHE_FLASH_REG as 0x3

5>We can burn the running application.

6>copy The .img file under DA1469x-00-Release_QSPI_SUOTA to Android Phone,and Upgrade with Android SUOTA APP.After the file transfer is completed, the system does not work after reboot

7>I checked the Product Hearder using the toolbox,active FW image Address Was Set 0x700000

When using IDE debug, it looks like FW image is not loaded.

阅读64字节@ddress 0xEFFFFFC0 WARNING: Failed to read memory @ address 0xEFFFFFC0 WARNING: Failed to read memory @ address 0xEFFFFFFC
effffffe: Failed to execute MI command: -data-disassemble -s 4026531838 -e 4026531966 -- 3 Error message from debugger back end: Cannot access memory at address 0xeffffffe

Can you give me some help?

Device:
PM_Dialog
Offline
Last seen:1 day 7 hours ago
Staff
加入:2018-02-08 11:03
Hi NickYang,

Hi NickYang,

Many thanks for your inputs and for your question online. I will check your issue and I will get back to you shortly.

Thanks, PM_Dialog

PM_Dialog
Offline
Last seen:1 day 7 hours ago
Staff
加入:2018-02-08 11:03
Hi NickYang,

Hi NickYang,

Apologies for the delay. I am working on your issue and I have asked someone else internally. I will let you know as soon as possible.

Regards, PM_Dialog

NickYang
Offline
Last seen:1 year 2 months ago
加入:2019-07-26 03:53
How is this going?

How is this going?

PM_Dialog
Offline
Last seen:1 day 7 hours ago
Staff
加入:2018-02-08 11:03
Hi Nick,

Hi Nick,

May I ask you why you changed CACHE_FLASH_REG to 0x3 since the SUOTA was working with the default value? Did you follow this tutorial?

http://lpccs-docs.dialog-semiconductor.com/tutorial_da1469x_supporting_fw_images_bigger_than_512kb/introduction.html

When he CACHE_FLASH_REG[FLASH_REGION_SIZE] = 0x3, this means that the system can run applications up to 4MB? Is this your requirement? Can you please change this filed to the default value following the tutorial?

Thanks, PM_Dialog