5340 hwo to DFU external Flash

RE: 5340 hwo to DFU external Flash

AHaug — Mon, 31 Oct 2022 08:22:33 GMT

For more information about MCUboot I suggest you examine the MCUboot-documentation pages for NCS:

https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/mcuboot/wrapper.html

In addition I recommend you have a look at the adding dfu support to your application

The next item I would have a look at is the following ticket

ncs external flash ota change qspi to spi

Here you will find this sample for NCS v1.7.1, where with a DFU sample that uses BLE and writes the data to external flash. This ticket should also give some information about how to write and read from a specific part of the external flash

Kind regards,
Andreas

RE: 5340 hwo to DFU external Flash

yoyou — Sat, 29 Oct 2022 01:22:18 GMT

i know how to write to flash,

my question is: in DFUing, How to distinguish the download data is app or for external Flash?

ps:

in nRF5_SDK_17.0.2\examples\dfu\secure_bootloader\

verify receive data , then distinguish the data, then do update APP or write to external Flash.

in NCS where is bootloader codes and how to change it?

see code as follow, NCS only

#include <mgmt/mcumgr/smp_bt.h>

#include "os_mgmt/os_mgmt.h"

#include "img_mgmt/img_mgmt.h"

not use bootloader?

#include <bluetooth/bluetooth.h>
#if defined (NRF5340_XXAA_APPLICATION)
  #define CLOCK_FEATURE_HFCLK_DIVIDE_PRESENT
  #include "nrfx_clock.h"
#endif
#include <zephyr.h>
#include <sys/printk.h>
#include <devicetree.h>
#include <logging/log.h>
#include <device.h>
#include <drivers/gpio.h>
#include <hal/nrf_gpio.h>
#include <drivers/gpio.h>
#include <sys/reboot.h>
#include <settings/settings.h>
#include <mgmt/mcumgr/smp_bt.h>
#include "os_mgmt/os_mgmt.h"
#include "img_mgmt/img_mgmt.h"

LOG_MODULE_REGISTER(main, 4);

void ota()
{
	printk("\n----------------OTA doing----------------\n\n");
	os_mgmt_register_group();
	img_mgmt_register_group();
	smp_bt_register();

	int err = bt_enable(NULL);
	if (err) {
		printk("Bluetooth init failed (err %d)\n", err);
		return;
	}
	if (IS_ENABLED(CONFIG_SETTINGS)) {
		settings_load();
	}

	err = bt_le_adv_start(BT_LE_ADV_CONN, upad, ARRAY_SIZE(upad),upsd, ARRAY_SIZE(upsd));
	if (err) {
		printk("Advertising failed to start (err %d)\n", err);
		return;
	}
	printk("   OTA Advertising started: %s\n",bt_get_name());
	
	// if wait no OTA start, timeout 3min will reboot
	for (int i=0;i<180;i++) {
		k_msleep(1000);
	}
	printk("\n---------------OTA timeout---------------\n\n");
	sys_reboot(0);
}

void main(void)
{
	ota();
	while(true){
		printk("********Hello World!********\n" );
		k_msleep(1000);
	}
}

Best regards

RE: 5340 hwo to DFU external Flash

bdodge09 — Tue, 25 Oct 2022 15:19:00 GMT

You can read/write external flash from the 5340 to update the DSP. Look at the sample in ncs called ./sdk-zephyr/samples/drivers/spi_flash/src/main.c It shows how to access qspi nor flash.

RE: 5340 hwo to DFU external Flash

yoyou — Tue, 25 Oct 2022 03:10:15 GMT

Hi,

thanks for reply,

i think,

modify bootloader code to judge the download hex is App or external Flash for DSP.

if App, do update self;

if for DSP, write to external Flash only;

but i don't know how to find the code in NCS2.0.2.

Best regards

RE: 5340 hwo to DFU external Flash

AHaug — Mon, 24 Oct 2022 11:40:08 GMT

Hi,

Unfortunately we don't have any demos or guides for how to do this for a DSP. However it is possible to do the DFU for the DSP as well, but you will need to implement what you need yourself. One starting point is to add the update bin/hex to a part of the flash that the DSP can access, and then perform the DFU from there

Kind regards,
Andreas