Update from nRF Connect SDK 1.7 to nRF Connect SDK 1.9.1

RE: Update from nRF Connect SDK 1.7 to nRF Connect SDK 1.9.1

user111786 — Tue, 24 May 2022 15:30:17 GMT

Hi Ed,

This would be a correct example to follow.
I would recommend you to start using Visual Studio Code with nRF Connect Extension instead of Segger Embedded Studio. I have tested unmodified littlefs sample myself in VS Code and there were no build errors.

Best regards,
Dejan

RE: Update from nRF Connect SDK 1.7 to nRF Connect SDK 1.9.1

user89639 — Mon, 23 May 2022 20:31:07 GMT

But the calls I make come directly from the example in:

zephyr/samples/subsys/fs/littlefs/src/main.c

Is there a different example I should be following?

RE: Update from nRF Connect SDK 1.7 to nRF Connect SDK 1.9.1

user111786 — Mon, 23 May 2022 07:35:43 GMT

Hi Ed,

If you are using partition manager in your project, it is recommended to use macros from flash_map_pm.h instead of DT natives.

Best regards,
Dejan

RE: Update from nRF Connect SDK 1.7 to nRF Connect SDK 1.9.1

user111786 — Wed, 18 May 2022 14:54:14 GMT

Hi Ed,

When using zero latency interrupt, 0-5 are available interrupt levels for the application.

Regarding DT_NODE_BY_FIXED_PARTITION_LABEL, I have asked internally and I will get back to you with more information, possibly till the end of this week.

Best regards,
Dejan

RE: Update from nRF Connect SDK 1.7 to nRF Connect SDK 1.9.1

user89639 — Mon, 16 May 2022 21:05:54 GMT

Here is the full error message:

2> Compiling ‘littlefs_fs.c’
2> In file included from [01m[KE:/N/S/v1.9.1/zephyr/include/sys/util_macro.h:34[m[K,
2> from [01m[KE:/N/S/v1.9.1/zephyr/include/sys/atomic.h:16[m[K,
2> from [01m[KE:/N/S/v1.9.1/zephyr/include/kernel_includes.h:21[m[K,
2> from [01m[KE:/N/S/v1.9.1/zephyr/include/kernel.h:17[m[K,
2> from [01m[KE:/N/S/v1.9.1/zephyr/subsys/fs/littlefs_fs.c:10[m[K:
2> [01m[KE:/N/S/v1.9.1/zephyr/include/devicetree/fixed-partitions.h:53:9:[m[K [01;31m[Kerror: [m[K'[01m[KDT_COMPAT_fixed_partitions_LABEL_storage_PARTITION_ID[m[K' undeclared here (not in a function); did you mean '[01m[KDT_COMPAT_fixed_partitions_LABEL_image_1_EXISTS[m[K'?
2> [01m[KE:/N/S/v1.9.1/zephyr/include/sys/util_internal.h:67:26:[m[K [01;36m[Knote: [m[Kin definition of macro '[01m[K__DEBRACKET[m[K'
2> [01m[KE:/N/S/v1.9.1/zephyr/include/sys/util_internal.h:59:2:[m[K [01;36m[Knote: [m[Kin expansion of macro '[01m[K__GET_ARG2_DEBRACKET[m[K'
2> [01m[KE:/N/S/v1.9.1/zephyr/include/sys/util_internal.h:54:2:[m[K [01;36m[Knote: [m[Kin expansion of macro '[01m[K__COND_CODE[m[K'
2> [01m[KE:/N/S/v1.9.1/zephyr/include/sys/util_macro.h:157:2:[m[K [01;36m[Knote: [m[Kin expansion of macro '[01m[KZ_COND_CODE_1[m[K'
2> [01m[KE:/N/S/v1.9.1/zephyr/include/devicetree.h:2873:2:[m[K [01;36m[Knote: [m[Kin expansion of macro '[01m[KCOND_CODE_1[m[K'
2> [01m[KE:/N/S/v1.9.1/zephyr/include/sys/util_internal.h:64:53:[m[K [01;36m[Knote: [m[Kin expansion of macro '[01m[K__DEBRACKET[m[K'
2> [01m[KE:/N/S/v1.9.1/zephyr/include/sys/util_internal.h:59:2:[m[K [01;36m[Knote: [m[Kin expansion of macro '[01m[K__GET_ARG2_DEBRACKET[m[K'
2> [01m[KE:/N/S/v1.9.1/zephyr/include/sys/util_internal.h:54:2:[m[K [01;36m[Knote: [m[Kin expansion of macro '[01m[K__COND_CODE[m[K'
2> [01m[KE:/N/S/v1.9.1/zephyr/include/sys/util_macro.h:157:2:[m[K [01;36m[Knote: [m[Kin expansion of macro '[01m[KZ_COND_CODE_1[m[K'
2> [01m[KE:/N/S/v1.9.1/zephyr/subsys/fs/littlefs_fs.c:819:4:[m[K [01;36m[Knote: [m[Kin expansion of macro '[01m[KCOND_CODE_1[m[K'
2> [01m[KE:/N/S/v1.9.1/zephyr/include/devicetree/fixed-partitions.h:69:40:[m[K [01;36m[Knote: [m[Kin expansion of macro '[01m[KDT_CAT[m[K'
2> [01m[KE:/N/S/v1.9.1/zephyr/include/storage/flash_map.h:270:2:[m[K [01;36m[Knote: [m[Kin expansion of macro '[01m[KDT_FIXED_PARTITION_ID[m[K'
2> [01m[KE:/N/S/v1.9.1/zephyr/include/devicetree/fixed-partitions.h:53:2:[m[K [01;36m[Knote: [m[Kin expansion of macro '[01m[KDT_CAT[m[K'
2> [01m[KE:/N/S/v1.9.1/zephyr/include/storage/flash_map.h:270:24:[m[K [01;36m[Knote: [m[Kin expansion of macro '[01m[KDT_NODE_BY_FIXED_PARTITION_LABEL[m[K'
2> [01m[KE:/N/S/v1.9.1/zephyr/subsys/fs/littlefs_fs.c:821:10:[m[K [01;36m[Knote: [m[Kin expansion of macro '[01m[KFLASH_AREA_ID[m[K'
2> [01m[Kzephyr/include/generated/devicetree_unfixed.h:8231:56:[m[K [01;36m[Knote: [m[Kin expansion of macro '[01m[KDEFINE_FS[m[K'
2> [01m[KE:/N/S/v1.9.1/zephyr/include/sys/util_internal.h:99:36:[m[K [01;36m[Knote: [m[Kin expansion of macro '[01m[KDT_FOREACH_OKAY_INST_zephyr_fstab_littlefs[m[K'
2> [01m[KE:/N/S/v1.9.1/zephyr/subsys/fs/littlefs_fs.c:826:1:[m[K [01;36m[Knote: [m[Kin expansion of macro '[01m[KDT_INST_FOREACH_STATUS_OKAY[m[K'

RE: Update from nRF Connect SDK 1.7 to nRF Connect SDK 1.9.1

user89639 — Mon, 16 May 2022 14:20:04 GMT

Hi Dejan,

Thanks for the reply.

I changed the priority in the IRQ_CONNECT() call from 6 to 5 and that seemed to clear that error. (But why?)

I don't call DT_NODE_BY_FIXED_PARTITION_LABEL directly... So it must be being called through this code:

#if 1
//
// LITTLEFS declaration
//
#if DT_NODE_EXISTS(PARTITION_NODE)
FS_FSTAB_DECLARE_ENTRY(PARTITION_NODE);
#else /* PARTITION_NODE */
FS_LITTLEFS_DECLARE_DEFAULT_CONFIG(storage);
static struct fs_mount_t lfs_storage_mnt = {
	.type = FS_LITTLEFS,
	.fs_data = &storage,
	.storage_dev = (void *)FLASH_AREA_ID(storage),
	.mnt_point = "/lfs1",
};
#endif /* PARTITION_NODE */

// For LITTLEFS
void
initFileSystem(fileSystemInfo *fs) {
  fs->mp=
#if DT_NODE_EXISTS(PARTITION_NODE)
       &FS_FSTAB_ENTRY(PARTITION_NODE)
#else
       &lfs_storage_mnt
#endif
       ;

  int err= fs_mount(fs->mp);
  fs->devId= (uintptr_t)fs->mp->storage_dev;
}




#endif

Note that DT_NODE_EXISTS(PARTITION_NODE) resolves to TRUE, so the first part of both #if clauses is used.

Here is the region of portion of the .overlay file where the partition is defined:

/ {
fstab {
compatible = "zephyr,fstab";
lfs1: lfs1 {
compatible = "zephyr,fstab,littlefs";
mount-point = "/lfs1";
partition = <&lfs1_part>;
/*
automount;
*/
read-size = <16>;
prog-size = <16>;
cache-size = <64>;
lookahead-size = <32>;
block-cycles = <512>;
};
};
};

&mx25r64 {
jedec-id = [01 20 18];
size = <134217728>;
partitions {
compatible = "fixed-partitions";
#address-cells = <1>;
#size-cells = <1>;

lfs1_part: partition@0 {
label = "lfs1";
/*
reg = <0x00000000 0x02000000>;
*/
reg = <0x00000000 0x00020000>;
};
};

(Note that the above code doesn't "survive" being put into a "code box")

But for both errors... This all works fine with nRF Connect SDK version 1.7.1

But it fails for version 1.9.1

I need to understand what has changed in the OS that the IRQ level needs to change from 6 to 5 and the file specification doesn't work.

Thanks!

RE: Update from nRF Connect SDK 1.7 to nRF Connect SDK 1.9.1

user111786 — Mon, 16 May 2022 12:48:37 GMT

Hi, Ed,

Regarding the first error, could you please provide more information how you use DT_NODE_BY_FIXED_PARTITION_LABEL()?

Regarding the second error, this is an interrupt priority issue. You could try changing the priority level from 6 to 5 in IRQ_CONNECT().

Best regards,
Dejan