How to Build Modem Shell sample App to fit in the Thingy:91

[Boudrox]

Hello,

For network testing, I would like to use the Modem Shell App sample with the Thingy:91.

As suggested in the overlay file, I can disable some features, so the Build can fit the application memory. But, if the MCUboot is disabled, is there a way to flash the applications (.hex below) to the kit without using a debug’s probe? For instance, using FOTA feature?

Otherwise, which features are you recommending disabling in the prj.conf, so I can have the following tools in the same build: LTE link control, AT commands, Ping, Iperf3, SMS tool and Socket Tool?

Thanks a lot!
Bernard

[Øyvind]

Hello Bernard, 

MCUBOOT is needed for both FOTA and programming via USB on the Thingy:91. If you do not need location services, then you could try the following settings in the thingy91_nrf9160_ns.conf overlay

#
# Copyright (c) 2021 Nordic Semiconductor ASA
#
# SPDX-License-Identifier: LicenseRef-Nordic-5-Clause
#

# Configuration file for Thingy:91.
# This file is merged with prj.conf in the application folder, and options
# set here will take precedence if they are present in both files.

# Disabling some of the features by default to fit MOSH into the flash
CONFIG_MOSH_CURL=n
CONFIG_MOSH_REST=n
CONFIG_MOSH_SMS=y
CONFIG_MOSH_IPERF3=y
CONFIG_MOSH_WORKER_THREADS=y
CONFIG_MOSH_CLOUD_REST=n
CONFIG_MOSH_FOTA=n
CONFIG_MOSH_GNSS=n
CONFIG_MOSH_LOCATION=n
CONFIG_NRF_CLOUD_REST=n
CONFIG_MULTICELL_LOCATION=n

# MCUBOOT
CONFIG_BOOTLOADER_MCUBOOT=y
CONFIG_IMG_MANAGER=y
CONFIG_MCUBOOT_IMG_MANAGER=y
CONFIG_IMG_ERASE_PROGRESSIVELY=y

Kind regards,
Øyvind

[Boudrox]

Hello Øyvind,

Thank you very much for the quick response. I confirm the build is now working with all requested features.

Best regards,
Bernard