Part Number: TDA4VEN-Q1
Other Parts Discussed in Thread: CCSTUDIO, SYSCONFIG
Following this thread, I have a few questions about the status of CCS Theia and microprocessors (Sitara, Jacinto, ...).
First, updates for CCSTUDIO (12.x) seem to have stopped since september, which led us to start migrating to Theia. For example, XDS110 firmware versions in 12.x have already fallen behind Theia, which shows that the migration is starting to become mandatory.
Second, it seems that, despite not being officially supported on Theia, all Sitara processors seem to work just fine. Here is what works so far:
- Opening projects created in 12.x
- Product dependencies & SysConfig integration (for general audience processors)
- (Almost) all project options get ported with success from old CCS projects (including post build steps, again with a few tweaks required)
- Target configurations and debugging work perfectly using respective guides
- Specifically for TDA4: we were able to fully port the launch.js script used to initialize debugging, with a few modifications based on this guide and bit of trial and error
In Theia, the debugging process is even more streamlined since you can pre-load both the sciserver into R5F core and the actual program in another core with a single button press.
The only problem that remains with Theia is project creation. In older CCS, TDA4x projects are created using the default "bare" creation process (Project > New CCS Project), without any template: choose device, core, compiler, and optionally products.
Are there any plans to add such a "manual" project creation feature in Theia?
For now, projectspec present in e.g. j722s RTOS SDK cannot import because core names are not recognized. Being able to create projects from scratch would solve this. (The projectspec files do not work on 12.x either, but at least there you can create a project from scratch.)
