Hello @sobo,
There are multiple ways which can be used to handle the code generation:
1. Using the EB Tresos GUI.
2. Take advantage of tresos_cmd.bat:
2.1 by using legacy generate with input as .epc files or .arxml files:
call .\..\Tresos\bin\tresos_cmd.bat -Dtarget=CORTEXM -Dderivate=S32K3XX legacy generate .\a.arxml@asc:4.4.0 -o .\outputt -g Wdg_TS_T40D34M10I0R0
Detail can be found in 6.12.3. Commands for legacy code generation - Development users guide of EB Tresos Studio.
2.2. or using generate/autoconfigure with the whole project. It's required that you have a EB Tresos project already:
$(TRESOS_DIR)/bin/tresos_cmd.bat deleteProject $(TRESOS_PROJECT_NAME) || exit 0 2>&1
$(TRESOS_DIR)/bin/tresos_cmd.bat importProject $(call winpath, $(call my_abspath, ./TresosProject/$(TRESOS_PROJECT_NAME))) 2>&1
ifeq ($(VARIANT_NO),0)
$(TRESOS_DIR)/bin/tresos_cmd.bat generate $(TRESOS_PROJECT_NAME) 2>&1
else
$(TRESOS_DIR)/bin/tresos_cmd.bat autoconfigure $(TRESOS_PROJECT_NAME) GenerateAllVariants 2>&1
endif
(The above script is taken from a RTD example)
Our testing team has been using the 2.2 way to handle code generation in CI/CD. But it's verified under Windows environment.
Best Regards,
Nam