partitions size definition

[otosan-maker]

Hello

Here I am, again, lost in the config files. It is a good job to define the partitions automatically, but I have a few boards with a 16 MB flash, and the FAT partition is only 1.3 MB. Where can I define the partitions I want to use? I am used to it and I prefer to define the partitions size and type. I plan to play with it in the future, rebooting in another partition.

Thanks

[otosan-maker]

I have seen the --flash-size=16 flag, and in the custom board definition I see it is defined a custom partition, I will try to go that way.

[kdschlosser]

when using a custom board path all other build options get ignored. The reason why this occurs is because you will be able to set all other options from that board specification. There is no longer the need to tell the build what the flat size is or what kind of SPIRAM the MCU has. You need to set all of that stuff yourself in the custom board files.

USER_C_MODULES and FROZEN_MANIFEST should also not be used as these can once again be supplied in the custom board. There needs to be a cmake build script in the custom board location and that script is where you would include your user c module cmake script and define the build rules for the user c module. There should me a manifest.py file in your custom board which is the reason why you would not need to use FROZEN_MANIFEST. that file automatically gets used when a custom board is used.

If you have you code uploaded to GitHub I can take a look at it and put together the code needed to get it all working for you.

[kdschlosser]

OH and DO NOT place the custom board path anywhere inside the repo. A custom board is something you make so it should be in a location outside of the cloned repository code. That is why you are getting that specific error popping up. The build script makes a copy of your custom board and places it into the repo and then it modifies the files in the board to make it work with the build system. So if you have the location the same as where it would be copying it to your files are going to end up getting modified and then deleted after it has finished compiling. I don't think you want that to happen.

[otosan-maker]

here it is.

https://github.com/otosan-maker/lvgl_maker/tree/main/boards/GALDEANO_CLASSIC

I can create the firmware with the custom partition table, but it is not working C_MODULE nor freeze the micropython code.

Thanks for your assistance.

[kdschlosser]

all you should have to do is include the user c module into the cmake file that is in there. You don't need to try and set it as a variable because it will be too late by time that cmake file gets included. It has already passed the point where processing is done of the user c module that you supply with that variable.

As far as as the manifest file is concerned.. Absolute paths is what you need to use in the manifest file. You do not need to specify the manifest file in the cmake file at all, it should automatically get used by MicroPython.

[otosan-maker]

I am used to Makefile, cmake is a spell for me. Can you please tell me how to include the c module?

thanks

[kdschlosser]

Also, to let you know you can also use a toml file which will direct the build and it will even write the touch and display driver for you so all you will need to do is point the build script to that toml file and it will handle compiling everything and also writing the scripts used to get the display and the touch working.