Unrecognized Files in UFS on EC200 runnning quecopen SDK

Technical Subjects Open Solution
1

Hello,
We’re running opencpu on an EC200UCN_AA module running LTE. In our understanding, we have about 1.8 Mb in the UFS for our internal usage, that we plan to use for storing application data.
However, looking at the contents of the UFS during runtime we see the following files:

  1. boot
  2. firm
  3. gnss_xxx files

We’re assuming the gnss info is saved to get a faster position lock and avoid a cold start. We want to understand:

  1. what do the boot and firm files do
    Since there are separate sections for bootloader and code flash, this seems redundant. --How to avoid storing these and impact
  2. Impact of not storing gnss files
    We’re okay taking a slight performance hit with the GPS if that means there’s more empty space in the UFS:
    -How to avoid storing these and impact
2

Hi @Punit_Rajwani,

Those files are crucial to the correct functioning of GNSS capability in the module.

Removing those file will render the GNSS part inoperable.

However the “gnss_xxx” is used for warm start so you can remove it if you want. But they don’t take a lot of space anyway.

1 Like
3

Which files are crucial? Can you comment in more detail?

  1. understood that the ‘gnss_xxx’ files are positioning data used for warm start and can be removed.
  2. What about the ‘boot’ and ‘firm’ files ? Are these GNSS related too ?
4

Hi @Punit_Rajwani,

The boot and firm file are bootloader and firmware for the GNSS chip. The chip itself don’t have persistent storage so those files will be loaded onto the GNSS chip when we initializes it.

1 Like
5

Got it. Thanks!
Related to this, but on a side note:
I’m Seeing a lot of logging functionality that we have no idea how to use, simply because the documentation isn’t there.
Apparently, there are ways to store the log file in the File System. How can we get some more detailed documentation on log features with quecopen ?
I keep checking with our PoC, but they seem to be really limited.

6

Hi @Punit_Rajwani,

Yes you can store log file to file system but only to external storage.
In ql_init.c enable ql_fs_trace_init() then configure it by ql_log_set_port() .
There’re no documentations on this however.

1 Like
7

Will attempt this. On the analogous, is there a way to disable Logs and save code flash usage in production SW?

8

That is not possible sadly

9

Understood, appreciate the quick and relevant responses.
Thanks!