Part Number: SYSCONFIG
Other Parts Discussed in Thread: C2000WARE,
Hi,
I’m currently working on driver development for C2000 MCUs (F28P55x family), and I have a clarification regarding the preferred development approach.
In our workflow, we see multiple ways to configure peripherals such as SPI, Timer, ADC, PWM and Watchdog:
- Using SysConfig-generated code (board.c/.h)
- Using C2000Ware driverlib APIs directly (manual configuration)
- Referring to TI example projects
- Using direct register-level programming
I would like to understand the recommended industry approach for production-level firmware development:
- Is SysConfig-based development preferred for embedded projects, and if so, why?
- What are the specific advantages of SysConfig beyond ease of configuration (e.g., pinmux consistency, clock configuration safety, error checking, optimization)?
- Does SysConfig have any impact on code optimization or runtime efficiency, or is it mainly a configuration and development productivity tool?
- In which scenarios would developers avoid SysConfig and instead use:
- only driverlib APIs, or
- direct register-level programming?
- How should we balance between:
- SysConfig-generated initialization code
- custom HAL/BSW written by developers
- For long-term maintainability and scalability (large projects with multiple peripherals), what approach is commonly followed?
Understanding this will help us define a consistent methodology for BSW design across modules.
Thanks in advance for your guidance.