Fota anomaly based on Ncs 1.9.0 sdk

RE: Fota anomaly based on Ncs 1.9.0 sdk

Vidar Berg — Mon, 10 Oct 2022 09:59:54 GMT

Can you post the current code and log output?

RE: Fota anomaly based on Ncs 1.9.0 sdk

duxinglang — Mon, 10 Oct 2022 03:04:28 GMT

I tried again according to your method. Unfortunately, after my device fota was successfully upgraded and restarted, it was still running the old firmware before the upgrade, and did not switch to the new firmware. I watched the boot_ write_ img_ The result returned by the confirmed function is 0, whether before or after the upgrade. So, what is the reason for this? This is the log file I grabbed.

RE: Fota anomaly based on Ncs 1.9.0 sdk

Vidar Berg — Mon, 03 Oct 2022 06:25:31 GMT

Based on what you describe, it seems as if the boot_write_img_confirmed() function only works when called before modem init.

Please check the return code from boot_write_img_confirmed(); and see if it returns with an error when CONFIG_NRF_MODEM_ LIB_SYS_INIT=y.

RE: Fota anomaly based on Ncs 1.9.0 sdk

duxinglang — Fri, 30 Sep 2022 10:34:09 GMT

OK.This is my initialization code:

void work_init(void)
{
	k_work_q_start(&nb_work_q, nb_stack_area,
					K_THREAD_STACK_SIZEOF(nb_stack_area),
					CONFIG_APPLICATION_WORKQUEUE_PRIORITY);
#ifdef CONFIG_IMU_SUPPORT	
	k_work_q_start(&imu_work_q, imu_stack_area,
					K_THREAD_STACK_SIZEOF(imu_stack_area),
					CONFIG_APPLICATION_WORKQUEUE_PRIORITY);
#endif
	
	if(IS_ENABLED(CONFIG_WATCHDOG))
	{
		watchdog_init_and_start(&k_sys_work_q);
	}
}

static int application_init(void)
{
	int err;

	err = fota_download_init(fota_dl_handler);
	if(err != 0)
	{
		return err;
	}

	return 0;
}

void fota_init(void)
{
	int err;

#ifdef FOTA_DEBUG
	LOGD("begin");
#endif

#if 0
	nrf_modem_lib_init(NORMAL_MODE);
#else
	err = nrf_modem_lib_get_init_ret();
	switch(err)
	{
	case 0:
		/* Initialization successful, no action required. */
	#ifdef FOTA_DEBUG
		LOGD("Initialization successful");
	#endif		
		break;

	case MODEM_DFU_RESULT_OK:
	#ifdef FOTA_DEBUG	
		LOGD("Modem firmware update successful!");
		LOGD("Modem will run the new firmware after reboot");
	#endif
		k_thread_suspend(k_current_get());
		break;
		
	case MODEM_DFU_RESULT_UUID_ERROR:
	case MODEM_DFU_RESULT_AUTH_ERROR:
	#ifdef FOTA_DEBUG
		LOGD("Modem firmware update failed");
		LOGD("Modem will run non-updated firmware on reboot.");
	#endif
		break;
		
	case MODEM_DFU_RESULT_HARDWARE_ERROR:
	case MODEM_DFU_RESULT_INTERNAL_ERROR:
	#ifdef FOTA_DEBUG
		LOGD("Modem firmware update failed");
		LOGD("Fatal error.");
	#endif
		break;
		
	default:
		break;
	}
#endif

	boot_write_img_confirmed();

	err = application_init();
	if(err != 0)
	{
		return;
	}

#ifdef FOTA_DEBUG
	LOGD("done");
#endif
}

void system_init(void)
{
	k_sleep(K_MSEC(500));//xb test 2022-03-11 启动时候延迟0.5S,等待其他外设完全启动
	
#ifdef CONFIG_FOTA_DOWNLOAD
	fota_init();
#endif

	InitSystemSettings();

	init_imu_int1();//xb add 2022-05-27
	PPG_i2c_off();
	
	pmu_init();
	flash_init();
	LCD_Init();
	
	ShowBootUpLogo();

	key_init();
#ifdef CONFIG_AUDIO_SUPPORT	
	audio_init();
#endif
	ble_init();
#ifdef CONFIG_PPG_SUPPORT	
	PPG_init();
#endif
#ifdef CONFIG_IMU_SUPPORT
	IMU_init(&imu_work_q);
#endif
#ifdef CONFIG_TEMP_SUPPORT
	temp_init();
#endif
#ifdef CONFIG_DATA_DOWNLOAD_SUPPORT
	dl_init();
#endif
	NB_init(&nb_work_q);
	GPS_init();
}

int main(void)
{
	work_init();
	system_init();

	while(1)
	{
		KeyMsgProcess();
		TimeMsgProcess();
		NBMsgProcess();
	#ifdef CONFIG_WIFI	
		WifiProcess();
	#endif
		GPSMsgProcess();
		PMUMsgProcess();
	#ifdef CONFIG_IMU_SUPPORT	
		IMUMsgProcess();
	#ifdef CONFIG_FALL_DETECT_SUPPORT
		FallMsgProcess();
	#endif
	#endif
	#ifdef CONFIG_PPG_SUPPORT	
		PPGMsgProcess();
	#endif
		LCDMsgProcess();
	#ifdef CONFIG_TOUCH_SUPPORT
		TPMsgProcess();
	#endif
		AlarmMsgProcess();
		SettingsMsgPorcess();
		SOSMsgProc();
		UartMsgProc();
	#ifdef CONFIG_ANIMATION_SUPPORT
		AnimaMsgProcess();
	#endif		
		ScreenMsgProcess();
	#ifdef CONFIG_DATA_DOWNLOAD_SUPPORT
		DlMsgProc();
	#endif
	#ifdef CONFIG_FOTA_DOWNLOAD
		FotaMsgProc();
	#endif
	#ifdef CONFIG_AUDIO_SUPPORT
		AudioMsgProcess();
	#endif
	#ifdef CONFIG_SYNC_SUPPORT
		SyncMsgProcess();
	#endif
	#ifdef CONFIG_TEMP_SUPPORT
		TempMsgProcess();
	#endif
		system_init_completed();
		k_cpu_idle();
	}
}

RE: Fota anomaly based on Ncs 1.9.0 sdk

Vidar Berg — Fri, 30 Sep 2022 10:22:38 GMT

OK, thanks for confirming. Could you try to initialize the modem library yourself from main(),etc and see if it works then (i.e. both DFU and modem lib).

RE: Fota anomaly based on Ncs 1.9.0 sdk

duxinglang — Fri, 30 Sep 2022 10:11:07 GMT

Sorry， I made a mistake. It is the CONFIG_NRF_MODEM_ IB_SYS_INIT.

RE: Fota anomaly based on Ncs 1.9.0 sdk

Vidar Berg — Fri, 30 Sep 2022 08:45:25 GMT

What SDK version are you building the app with now? I read it as being 1.9.0, but this version does not define the CONFIG_BSD_LIBRARY_SYS_INIT symbol (BSD lib was renamed to modem lib in v1.5.0), so I don't understand how you can still use this symbol and build your project.

RE: Fota anomaly based on Ncs 1.9.0 sdk

duxinglang — Fri, 30 Sep 2022 08:15:45 GMT

Thanks for your reply. My current operation is to create an app on ncs1.9.0_ update. Bin, and then modified the interface to compile and burn it to the device. That is to say, when testing, the old firmware of the device and the new firmware of FOTA are compiled on ncs1.9.0, which should have nothing to do with slot partitions. Later, I found out that if Add CONFIG to conf_ BSD_ LIBRARY_ SYS_ INIT=n, after compiling and burning, my device will switch to the new firmware that was fota last time after it is powered on again, but it cannot operate the modem. It is strange whether the modem is turned on or off. By the way, the firmware version of my modem is v1.3.1.

RE: Fota anomaly based on Ncs 1.9.0 sdk

Vidar Berg — Thu, 29 Sep 2022 11:41:43 GMT

Hello,

Could it be that the memory layout has changed between these versions? For DFU to work, it is important that the primary and secondary slot partitions remain at the same addresses between updates. The normal way we ensure this is to use a startic partition file as explained here: https://developer.nordicsemi.com/nRF_Connect_SDK/doc/2.0.2/nrf/scripts/partition_manager/partition_manager.html#configuring-static-partitions.

You can for instance make a copy of the partitions.yml file from your v1.2.0 project and use it as a static partitions file in your new project.

Best regards,

Vidar