MSPM33C321A: LVGL: sysconfig file for examples

Part Number: MSPM33C321A
Other Parts Discussed in Thread: SYSCONFIG,

I am getting back onto using LVGL with the touchscreen. For reference:

https://e2e.ti.com/support/microcontrollers/arm-based-microcontrollers-group/arm-based-microcontrollers/f/arm-based-microcontrollers-forum/1673077/faq-mspm33c321a-mspm33-lvgl-solution

Is is possible to get the sysconfig file used for the examples? It is not supplied with the source code, but it was clearly used because of the format of the supplied ti_msp_dl_config.c and ti_msp_dl_config.h.

I want to use the example code as the basis for my project, but it is really difficult to add other peripherals or GPIO's

  • Short answer: yes, for the SDK demo — the .syscfg is in the SDK, not in the forum attachment

    The official LVGL demo ships as a complete SysConfig project inside the MSPM33 SDK:

    C:\ti\mspm33_sdk_1_04_00_00\examples\nortos\LP_MSPM33C321A\demos\lvgl
    

    That project directory contains its .syscfg file, which opens in the SysConfig GUI from CCS 1. Import that example directly from the SDK (TI explicitly recommends SDK import rather than copying files, because the .syscfg-to-generated-file linkage depends on it) 2.

    Where no .syscfg exists: if you are working from the custom IPS Display 2 Click (ST7789V2) port in that FAQ thread, that port is not officially supported and the author deliberately did not share a .syscfg — the instruction was "Configure sysconfig along duplicated ti_msp_dl_config.c/.h. But I can't be bothered. Please copy the one in the attached project," i.e. only the pre-generated ti_msp_dl_config.c/.h were attached 1. A separate thread reported the same gap on the 1.03 SDK LVGL demo ("the example does not include the sysconfig file, it is difficult to parse the exact clock frequencies"), which was resolved by moving to the more complete 1.04.00.00 SDK demo 3.

    Why the generated files look that way

    ti_msp_dl_config.c/.h are standard SysConfig outputs and are regenerated/overwritten every time the .syscfg is modified and rebuilt — they are not meant to be maintained as the source of truth 4. The FAQ setup used SysConfig 1.27 with CCS 20.5, TI Clang v4.0.4, and MSPM33 SDK 1.03.0.01/1.04.00.00 1.

    Adding peripherals and GPIOs

    Preferred — use the SDK demo's .syscfg: double-click the .syscfg to launch the SysConfig GUI, add/configure the modules and IO pins, save, rebuild; ti_msp_dl_config.c/.h regenerate and you only call SYSCFG_DL_init() 56. Same double-click workflow applies in CCS and CCS Theia 7.

    If you must keep the forum-attachment files (no .syscfg): two documented paths —

    Option Procedure
    Reconstruct the config Create a new .syscfg for the same device/board (LP_MSPM33C321A), re-enter the pin/peripheral settings in the GUI, and let SysConfig own regeneration from then on 4
    Freeze the generated files Exclude the generated files from automatic regeneration (uncheck "include in build") before hand-editing them; TI documents an explicit Disable/Re-enable SysConfig procedure for CCS and IAR on MSPM33C321A 84

    Interim pattern that avoids both: rather than hand-editing ti_msp_dl_config.c, add the extra peripheral/GPIO setup in application code (e.g. main.c) with DriverLib calls placed after SYSCFG_DL_init() — this is the recommended approach for extending SysConfig-generated projects, since the generated file gets overwritten 9.

    One note for Keil users: if a SysConfig module emits files beyond ti_msp_dl_config.c/.h (e.g. a NONMAIN Configurator producing boot_config.c/.h), Keil will not auto-add them — add them manually to the Source group before rebuilding 2.

    Gap to flag: none of the retrieved documentation itemizes the file list of the lvgl demo folder, so I can't independently verify the .syscfg filename there beyond the FAQ author's statement that the SysConfig configuration is included in that project. Confirm by checking the installed demos\lvgl folder in SDK 1.04.00.00.

    Follow up: Which display/touch controller is your project targeting — the officially supported ST7796/DFT6636U in the SDK demo, or the ST7789V2 Click port from the FAQ? That determines whether you can start from the SDK's .syscfg directly or need to reconstruct one.

    1. FAQ: MSPM33C321A MSPM33 LVGL Solution (E2E)
    2. MSPM33 SDK Keil IDE Guide
    3. MSPM33C321A: Getting started with LVGL (E2E)
    4. Using SysConfig with MSPM33
    5. MSPM33 SDK Keil Quickstart Guide
    6. SLUUDG7 User's Guide
    7. MSPM33 SDK CCS IDE Guide
    8. SDAA228 User's Guide
    9. MSPM33 SDK MCAN module and filters (E2E)
  • The sysconfig file is not present in the demo file:

    from C:\ti\mspm33_sdk_1_04_00_00\examples\nortos\LP_MSPM33C321A\demos\lvgl

    Only the SysConfig generated ti_msp_dl_config.c and ti_msp_dl_config.h files are present in the root directory (So they by default are the "source of truth"). And in fact SysConfig is not listed as a dependency in the preferences:

    I am using the supported screen with the  ST7796 display driver and DFT6636U capacitive touch driver . I should have pointed out that I am using the example from SDK 1.03 because the example in sdk 1.04 hangs up reading the I2C. (Which I intend to look into). Anyway, neither example has a main.config available, just the SysConfig results in the root of the example as shown. The example from SDK 1.03 works fine with the screen and touch.

    (I am using CCS 21.0.0 on a PC.)

    Just for the record, this is what CCS shows with a fresh install of the lvgl example from the 1.04 SDK:

    Note the config .c and .h files with no .config in sight.

    And here are the sdk versions I am using:

  • Sorry, Of course I mean .syscfg not .config

  • Hi Keith 

    I will check the detailed and reply later.

    Thanks

  • Thanks, sorry to overdo the fact that the .syscfg is not included, but I was trying to make sure that I had left no stone unturned.

  • Hi Keith,
    I really appreciate your thoroughness and the clear screenshots! I just verified the project structure on my end as well, and you are completely right: the .syscfg file is indeed omitted from the LVGL demo in SDK 1.04.00.00, with only the pre-generated ti_msp_dl_config.c/.h files included.
    1. Adding peripherals/GPIOs without .syscfg:
    Since this demo uses pre-generated ti_msp_dl_config.c/.h files as static source code, the safest workflow to add your own peripherals or GPIOs on top of the working SDK 1.03 example is:
    • Keep ti_msp_dl_config.c/.h untouched (do not add a .syscfg file directly into this LVGL project, as it would overwrite the existing display/touch pinmux and SPI/I2C configurations).
    • Use a separate blank SysConfig project as a code generator for your new peripherals/GPIOs, then copy the generated DriverLib initialization code into your own setup function and call it right after SYSCFG_DL_init() in main.c.
    2. SDK 1.04 I2C hang issue:
    Thank you as well for flagging that the SDK 1.04 LVGL demo hangs during I2C reads with the ST7796/DFT6636U setup. I will check this with our internal software team so we can look into it for a future SDK update. Sticking with SDK 1.03 as your baseline in the meantime is definitely the right move.
    Thanks!
  • I would also hope that the 1.05 LVGL demo will include the syscfg file.

    But thanks for your help. Your solution is much better than mine which was to try and reverse engineer the .syscfg file! But it is a little difficult without knowing the exact clock setup.