Is there any way to quiet these boot logs?

*** Booting Zephyr OS build v2.4.0-ncs2 ***
Flash regions Domain Permissions
00 02 0×00000 0×18000 Secure rwxl
03 31 0×18000 0×100000 Non-Secure rwxl

Non-secure callable region 0 placed in flash region 2 with size 32.

SRAM region Domain Permissions
00 07 0×00000 0×10000 Secure rwxl
08 31 0×10000 0×40000 Non-Secure rwxl

Peripheral Domain Status
00 NRF_P0 Non-Secure OK
01 NRF_CLOCK Non-Secure OK
02 NRF_RTC0 Non-Secure OK
03 NRF_RTC1 Non-Secure OK
04 NRF_NVMC Non-Secure OK
05 NRF_UARTE1 Non-Secure OK
06 NRF_UARTE2 Secure SKIP
07 NRF_TWIM2 Non-Secure OK
08 NRF_SPIM3 Non-Secure OK
09 NRF_TIMER0 Non-Secure OK
10 NRF_TIMER1 Non-Secure OK
11 NRF_TIMER2 Non-Secure OK
12 NRF_SAADC Non-Secure OK
13 NRF_PWM0 Non-Secure OK
14 NRF_PWM1 Non-Secure OK
15 NRF_PWM2 Non-Secure OK
16 NRF_PWM3 Non-Secure OK
17 NRF_WDT Non-Secure OK
18 NRF_IPC Non-Secure OK
19 NRF_VMC Non-Secure OK
20 NRF_FPU Non-Secure OK
21 NRF_EGU1 Non-Secure OK
22 NRF_EGU2 Non-Secure OK
23 NRF_DPPIC Non-Secure OK
24 NRF_GPIOTE1 Non-Secure OK
25 NRF_REGULATORS Non-Secure OK

SPM: NS image at 0×1c200
SPM: NS MSP at 0×2003bff8
SPM: NS reset vector at 0×24439
SPM: prepare to jump to Non-Secure image.
*** Booting Zephyr OS build v2.4.0-ncs2 ***

Try this:

CONFIG_TFM_LOG_LEVEL_SILENCE=y
-- Generated devicetree_unfixed.h: C:/dev/v1.4.1/nrf/samples/nrf9160/mqtt_simple/build/zephyr/include/generated/devicetree_unfixed.h

**C:/dev/v1.4.1/nrf/samples/nrf9160/mqtt_simple/prj.conf:13: warning: attempt to assign the value 'y' to the undefined symbol TFM_LOG_LEVEL_SILENCE**
Parsing C:/dev/v1.4.1/nrf/samples/nrf9160/mqtt_simple/Kconfig
Loaded configuration 'C:/dev/v1.4.1/zephyr/boards/arm/circuitdojo_feather_nrf9160/circuitdojo_feather_nrf9160ns_defconfig'
Merged configuration 'C:/dev/v1.4.1/nrf/samples/nrf9160/mqtt_simple/prj.conf'

The one I suggested is only for newer versions of NCS. Try one of these:

CONFIG_SPM_BOOT_SILENTLY=y
CONFIG_BOOT_BANNER=n

*** Booting Zephyr OS build v2.4.0-ncs2 ***
Is that the NCS version. I don’t know how to check the version.
Those commands didn’t fail. They also didn’t supress the messages.
Is the bootloader printing those messages? Do i have to update the bootloader. Is there a way to update the bootloader over the USB serial port interface or DFU?

Thanks!

    RichSurprenant Is the bootloader printing those messages? Do i have to update the bootloader. Is there a way to update the bootloader over the USB serial port interface or DFU?

    No, I believe it’s the secure image that gets merged into yours. I would do a pristine build to make sure they’re getting set correctly. Especially if you’re entering these values into a board overlay.

      Easy way to check which version. Run:

      git describe --tags

      Just to mention:
      If you want to replace the bootloader with the newly build one you will need a Jlink. AFAIK it doesn’t work with USB serial.

        Terms and Conditions | Privacy Policy