This is my first time developing for Nordic processors. I am using Zephyr 3.0.99 with the nrf52810 on a ublox BMD-330 eval board. I connected a W25X20CL 2M-bit chip via the SPI bus. I have used the “littlefs” file system to create and read/write files on the external flash. The application will be BLE enabled and I am planning on using a custom service to transfer a new bootable image to the external flash. When I enable the MCUMGR with bluetooth the image is too large for the flash. But our app builds and still has some headroom left. So if I can do OTA updates to the external flash we should be good. I have enabled MCUBOOT and it goes through the 2 phase build. However when I flash the image onto the board I get the following
I am just using a simple hello world app to try and get this working. The partitions.yml looks like it has placed the mcuboot_secondary on the external flash. But I don't know what the above error means. The default was 128 and I managed to figure out how to change to 256. 512 will make the image too large. I have read dev zone articles and searched the web for 2 days. But all suggestions usually don't work because they are out of date and the configuration options have changed with the latest Zephyr. I would really appreciate if you could point me to a working example that uses your latest SDK or up to date info. on how to solve this problem.
Thanks
/*
* Copyright (c) 2012-2014 Wind River Systems, Inc.
*
* SPDX-License-Identifier: Apache-2.0
*/
#include <zephyr.h>
#include <sys/printk.h>
#define IMAGE_VERSION CONFIG_MCUBOOT_IMAGE_VERSION
void main(void)
{
printk("Hello World! board: %s image: %s\n", CONFIG_BOARD, IMAGE_VERSION);
}
