Seriaous issue with CONFIG_MCUMGR, VBATT and SAADC

RE: Seriaous issue with CONFIG_MCUMGR, VBATT and SAADC

IvanR — Tue, 26 Mar 2024 13:39:55 GMT

added

&uart0 {

status = "disabled";

};

to mcuboot.overlay

It works now!

Thanks

RE: Seriaous issue with CONFIG_MCUMGR, VBATT and SAADC

Vidar Berg — Tue, 26 Mar 2024 13:12:49 GMT

Thanks for confirming. I suggest comparing the IO configurations with and without MCUBoot enabled to see if you can find any discrepancies.

You can do this for P0 and P1 in VS code:

Edit: Or you can apply an overlay to mcuboot to change the default pinout and disable UARTE if it is not needed in the bootloader.

https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/config_and_build/multi_image.html#permanent-configuration-changes-to-child-images

RE: Seriaous issue with CONFIG_MCUMGR, VBATT and SAADC

IvanR — Tue, 26 Mar 2024 13:05:19 GMT

It's a custom board with mx25r6435f.

its more or less DT overlays of the nRF5340dk_nrf5340 board

Its basically the overlay that was sent in hello_world.zip

When applying the same "commenting out" on the larger project config It passes all start up test but hangs on BLE initi.

 >>  ADC initialized... 
>>  ADC Channel 2 initialized... 
>>  Voltage divider initialized... 
Test 4

Test is read out of adc operation with 4 being the result...

  if (bt_enable(bt_ready)) {
    report_and_halt("Bluetooth init failed.");
  }
  
  while(1){
    int ret = test_vbat();
    printk("Test %d\n", ret);
    k_sleep(K_MSEC(500));
  }

RE: Seriaous issue with CONFIG_MCUMGR, VBATT and SAADC

Vidar Berg — Tue, 26 Mar 2024 12:56:16 GMT

I suspect the bootloader is configuring some pins (for UARTE, etc) that is causing this issue on your board. Have you created a custom board files for your board, or are you relying on DT overlays with the nRF5340dk_nrf5340 board ?

RE: Seriaous issue with CONFIG_MCUMGR, VBATT and SAADC

IvanR — Tue, 26 Mar 2024 12:52:32 GMT

The output is as expected

*** Booting nRF Connect SDK v3.5.99-ncs1 ***
Starting
3978
3969
3978
3960
3996
3978
3978
3978

RE: Seriaous issue with CONFIG_MCUMGR, VBATT and SAADC

IvanR — Tue, 26 Mar 2024 12:47:54 GMT

Sorry :) one sec, well a minute to compile

RE: Seriaous issue with CONFIG_MCUMGR, VBATT and SAADC

Vidar Berg — Tue, 26 Mar 2024 12:47:28 GMT

This is the configuration I wanted you to try:

# CONFIG_MCUMGR=y

CONFIG_BOOTLOADER_MCUBOOT=y

# CONFIG_NCS_SAMPLE_MCUMGR_BT_OTA_DFU=y

# CONFIG_ZCBOR=y

# CONFIG_STREAM_FLASH=y

# CONFIG_IMG_MANAGER=y

RE: Seriaous issue with CONFIG_MCUMGR, VBATT and SAADC

IvanR — Tue, 26 Mar 2024 12:45:47 GMT

This is the output of all uncommented:

*** Booting nRF Connect SDK v3.5.99-ncs1 ***
Starting
518373
3628800
200475
1555227
3004398
4453659
-3015900
3946797
2792502
2898459
4453614
-3015936
3946779
3310830

If I try to comment out only CONFIG_BOOTLOADER_MCUBOOT I get compile

n file included from C:/ncs/v2.6.0/zephyr/include/zephyr/storage/flash_map.h:275,
                 from C:/ncs/v2.6.0/zephyr/subsys/dfu/boot/mcuboot.c:12:
C:/ncs/v2.6.0/zephyr/subsys/dfu/boot/mcuboot.c: In function 'boot_is_img_confirmed':
C:/ncs/v2.6.0/nrf/include/flash_map_pm.h:43:22: error: 'PM_mcuboot_primary_ID' undeclared (first use in this function)
   43 | #define PM_ID(label) PM_##label##_ID
      |                      ^~~
C:/ncs/v2.6.0/nrf/include/flash_map_pm.h:48:35: note: in expansion of macro 'PM_ID'
   48 | #define FIXED_PARTITION_ID(label) PM_ID(label)
      |                                   ^~~~~
C:/ncs/v2.6.0/zephyr/subsys/dfu/boot/mcuboot_priv.h:22:34: note: in expansion of macro 'FIXED_PARTITION_ID'
   22 | #define FLASH_AREA_IMAGE_PRIMARY FIXED_PARTITION_ID(SLOT0_LABEL)
      |                                  ^~~~~~~~~~~~~~~~~~
C:/ncs/v2.6.0/zephyr/subsys/dfu/boot/mcuboot.c:192:30: note: in expansion of macro 'FLASH_AREA_IMAGE_PRIMARY'
  192 |         rc = flash_area_open(FLASH_AREA_IMAGE_PRIMARY, &fa);
      |                              ^~~~~~~~~~~~~~~~~~~~~~~~
C:/ncs/v2.6.0/nrf/include/flash_map_pm.h:43:22: note: each undeclared identifier is reported only once for each function it appears in
   43 | #define PM_ID(label) PM_##label##_ID
      |                      ^~~
C:/ncs/v2.6.0/nrf/include/flash_map_pm.h:48:35: note: in expansion of macro 'PM_ID'
   48 | #define FIXED_PARTITION_ID(label) PM_ID(label)
      |                                   ^~~~~
C:/ncs/v2.6.0/zephyr/subsys/dfu/boot/mcuboot_priv.h:22:34: note: in expansion of macro 'FIXED_PARTITION_ID'
   22 | #define FLASH_AREA_IMAGE_PRIMARY FIXED_PARTITION_ID(SLOT0_LABEL)
      |                                  ^~~~~~~~~~~~~~~~~~
C:/ncs/v2.6.0/zephyr/subsys/dfu/boot/mcuboot.c:192:30: note: in expansion of macro 'FLASH_AREA_IMAGE_PRIMARY'
  192 |         rc = flash_area_open(FLASH_AREA_IMAGE_PRIMARY, &fa);
      |                              ^~~~~~~~~~~~~~~~~~~~~~~~

If I comment out a

# CONFIG_MCUMGR=y

# CONFIG_BOOTLOADER_MCUBOOT=y

# CONFIG_NCS_SAMPLE_MCUMGR_BT_OTA_DFU=y

# CONFIG_ZCBOR=y

# CONFIG_STREAM_FLASH=y

# CONFIG_IMG_MANAGER=y

I get output:

*** Booting nRF Connect SDK v3.5.99-ncs1 ***
Starting
3924
3969
3924
3978
3969
3960
3978
3915
3960
3978

Which is what I expect ....

RE: Seriaous issue with CONFIG_MCUMGR, VBATT and SAADC

Vidar Berg — Tue, 26 Mar 2024 12:32:33 GMT

Hello,

I tried running your project on an nRF5340 DK both with and without the configuration mentioned above, but it did not appear to affect the SAADC measurements in my case. Do you observe the same issue when only CONFIG_BOOTLOADER_MCUBOOT is enabled?

Best regards,

Vidar

RE: Seriaous issue with CONFIG_MCUMGR, VBATT and SAADC

IvanR — Tue, 26 Mar 2024 10:15:42 GMT

devzone.nordicsemi.com/.../64420.hello_5F00_world.zip

Example code.

CONFIG_MCUMGR=y

CONFIG_BOOTLOADER_MCUBOOT=y

CONFIG_NCS_SAMPLE_MCUMGR_BT_OTA_DFU=y

CONFIG_ZCBOR=y

CONFIG_STREAM_FLASH=y

CONFIG_IMG_MANAGER=y

if this is commented out it works, if not it produces random values