⚠️
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.xmece.com/support. We’ll be fixing bugs / optimising the searching and tagging over the coming days.
12 posts / 0 new
Last post
邓昌永
Offline
Last seen:3 months 1 week ago
加入:2020-02-10 02:23
BLE SUOTA

hi there,

I use the routines in the SDK_10.0.8.105 \ projects \ dk_apps \ demos \ pxp_reporter directory to upgrade. But the program cannot run after the upgrade. I use the mobile application Dialog SUOTA to operate. The routine does not modify any code. Please give me some hints.

Device:
PM_Dialog
Offline
Last seen:1 day 4 hours ago
工作人员
加入:2018-02-08 11:03
Hi There,

Hi There,

Please refer toUM-B-092: DA1469x Software Platform Reference Manualand section 5.2. Software Upgrade Over The Air (SUOTA) in order to find detailed information regarding the SUOTA. Specifically, in section 5.2.4, you will find detailed steps for performing SUOTA upgrade using a mobile phone and the pxpx_reporter example of the SDK. Please make sure that you are following the correct steps.

Thanks, PM_Dialog

邓昌永
Offline
Last seen:3 months 1 week ago
加入:2020-02-10 02:23
hi there,

hi there,

I can use the partition table under SDK / 4M / suota / to upgrade. Since my image size is 950kb, I need to modify the partition table. After the modification of the partition table, the program cannot run, please give me some guidance. Below is my partition table code.

Normal partition table:

#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 0x07E000

/* +----------------512KB---------------------+ */

#define NVMS_GENERIC_PART_START 0x0E0000
#define NVMS_GENERIC_PART_SIZE 0x020000
#define NVMS_PLATFORM_PARAMS_PART_START 0x100000
#define NVMS_PLATFORM_PARAMS_PART_SIZE 0x0FF000
#define NVMS_PARAM_PART_START 0x1FF000
#define NVMS_PARAM_PART_SIZE 0x001000 /* Recommended location, 4KB before the end of the 1st flash section. */

/* +------------------2MB---------------------+ */

#定义NVMS_FW_UPDATE_PART_START 0 x200000讽刺笑星阿里•g / *nment to 512KB is dictated by the default FLASH_REGION_SIZE. */
#define NVMS_FW_UPDATE_PART_SIZE 0x07E000 /* This size is dictated by the default (512KB) FLASH_REGION_SIZE. */
#define NVMS_LOG_PART_START 0x300000
#define NVMS_LOG_PART_SIZE 0x0FF000
#define NVMS_PARTITION_TABLE_START 0x3FF000
#define NVMS_PARTITION_TABLE_SIZE 0x001000 /* Recommended location, 4KB before the end of the flash. */

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 )

Partition table that cannot run:

#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 0x100000

#define NVMS_GENERIC_PART_START 0x102000
#define NVMS_GENERIC_PART_SIZE 0x00F000
#define NVMS_PLATFORM_PARAMS_PART_START 0x111000
#define NVMS_PLATFORM_PARAMS_PART_SIZE 0x002000
#define NVMS_PARAM_PART_START 0x113000
#define NVMS_PARAM_PART_SIZE 0x001000 /* Recommended location, 4KB before the end of the 1st flash section. */

#define NVMS_FW_UPDATE_PART_START 0x114000 /* Alignment to 512KB is dictated by the default FLASH_REGION_SIZE. */
#define NVMS_FW_UPDATE_PART_SIZE 0x100000 /* This size is dictated by the default (512KB) FLASH_REGION_SIZE. */
#define NVMS_LOG_PART_START 0x214000
#define NVMS_LOG_PART_SIZE 0x00C000
#define NVMS_PARTITION_TABLE_START 0x220000
#define NVMS_PARTITION_TABLE_SIZE 0x001000 /* Recommended location, 4KB before the end of the flash. */

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 )

PM_Dialog
Offline
Last seen:1 day 4 hours ago
工作人员
加入:2018-02-08 11:03
Hi There,

Hi There,

Can you please indicate the size of the firmware? Is it bigger than 512KB ?

Thanks, PM_Dialog

邓昌永
Offline
Last seen:3 months 1 week ago
加入:2020-02-10 02:23
Hi there,

Hi there,

yes,my firmware has more than 900 KB.

PM_Dialog
Offline
Last seen:1 day 4 hours ago
工作人员
加入:2018-02-08 11:03
Hi There,

Hi There,

By default, both the SDK and chip configurations support running application images of up to 512 kB in size. Since your firmware is 900KB, I would suggest you to read theDA1469x Supporting Images Bigger than 512kBtutorial.

Thanks, PM_Dialog

邓昌永
Offline
Last seen:3 months 1 week ago
加入:2020-02-10 02:23
Hi,There,

Hi,There,

The current situation is that it can be started, but the program will not start after the upgrade, and I don't know the reason. My partition table is also posted on it, please help analyze the reason, thank you very much.

PM_Dialog
Offline
Last seen:1 day 4 hours ago
工作人员
加入:2018-02-08 11:03
Hi There,

Hi There,

Please clarify the following. You have posted 2 different partition table. The first is the default, and the second is the customized. Both partition table are not working after the software update is that correct? Also, you binary image is around 900KB, that’s why you have changed the execution and the firmware update. Could you please indicate if my understanding is correct?

Thanks, PM_Dialog

邓昌永
Offline
Last seen:3 months 1 week ago
加入:2020-02-10 02:23
Hi There,

Hi There,

Yes, your understanding is correct. But why is there a situation where it cannot start after the upgrade?

PM_Dialog
Offline
Last seen:1 day 4 hours ago
工作人员
加入:2018-02-08 11:03
Hi There,

Hi There,

As already mentioned in my previous comment, the DA1469x supports different sizes of FW. However, both the SDK and chip configurations support running application images of up to 512 kB in size. This is the default configuration. Since the FW before the SUOTA is bigger than 512KB, did you follow the tutorial in order to add support for FW up to 1MB? If the FW is bigger than 512KB, you should change the flash region size in the Configuration Script.

Thanks, PM_Dialog

邓昌永
Offline
Last seen:3 months 1 week ago
加入:2020-02-10 02:23
Hi there,

Hi there,

Thank you for your reply,I have used SmartSnippets Toolbox to change FLASH_REGION_SIZE to 1MBytes, but still cannot start after upgrading.

PW_Dialog
Offline
Last seen:1 month 2 weeks ago
工作人员
加入:2019-04-03 02:54
Hi Changyong,

Hi Changyong,

Can you confirm that you've followed all the steps ashttp://lpccs-docs.dialog-semiconductor.com/tutorial_da1469x_supporting_fw_images_bigger_than_512kb/Implementation.html

If yes please send the new partition file you modified to local supporter.

Br,

PW_Dialog