• State
  • Locked Locked
  • Replies 53 replies
  • Subscribers 36 subscribers
  • Views 1041 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

MCU-PLUS-SDK-AM243X: SYSCONFIG and compile time very slow

Tron
Prodigy 170 points
Part Number: MCU-PLUS-SDK-AM243X
Other Parts Discussed in Thread: SYSCONFIG

Hi all,

I have two issues:

1. My M4 core will only launch sometimes

I haven't been able to find anything in my code to cause this, but if I build the exact same code 9/10 times it will load with no symbols. I can't open the ROV, see the stack, or anything. There's not much running on this core, but I've tried to increase the stack size of the tasks and no difference is made.

If I'm lucky, it will sometimes just work - no changes, I just need to keep trying and it will eventually load. I'm not sure what's changed to lead to this. Any help/suggestions are greatly appreciated.

2. sysconfig is really, really slow now

Is it normal for a multicore project using a lot of peripherals to be such a challenge for CCS 12?

It takes about 20 minutes now to just open a syscfg file from a project I'm working on. It's using most GPIO pins and other peripherals across all 5 cores, so it is comprehensive, but the time still seems disproportionate.

It also takes me about 20 minutes to run debug for the full multi core project, or 3 minutes for an individual core. This is very frustrating when I might forget to run the DSMC initialisation script between attempts, which means it's then 40 minutes.

I know a part of the reason is that I do a full make clean before each build, which was the only way I could get a multicore project to actually build properly. But it seems to largely be the sysconfig portion.

Is there something I can do to speed things up? I'm using pretty powerful computers, so I'm surprised at how my dev has crawled to a snails pace with CCS.

  • 0 in reply to Darian Sale
    Prodigy 170 points

    Hi Darian. I've got the OOM error with Sysconfig again, caused by adding one more GPIO so I can switch the ePWM2/FSI MUX.

    "C:\\ti\\ccs1250\\ccs\\utils\\bin\\gmake" -k -j 12 all -O 
 
Building file: "../DAQ.syscfg"
Invoking: SysConfig
"C:/ti/ccs1250/ccs/utils/sysconfig_1.18.0/sysconfig_cli.bat" --script "C:/Users/xxxx/Documents/Git/Firmware/xxxx-Firmware/R5F01/PB.syscfg" --context "r5fss0-1" --script "C:/Users/xxxx/Documents/Git/Firmware/xxxx-Firmware/R5F10/INK.syscfg" --context "r5fss1-0" --script "C:/Users/xxxx/Documents/Git/Firmware/xxxx-Firmware/R5F11/COM.syscfg" --context "r5fss1-1" --script "C:/Users/xx/Documents/Git/Firmware/xxxx-Firmware/M4/GOV.syscfg" --context "m4fss0-0" --script "C:/Users/xxxx/Documents/Git/Firmware/xxxx-Firmware/R5F00/DAQ.syscfg" -o "syscfg" -s "C:/ti/mcu_plus_sdk_am243x_08_06_00_43/.metadata/product.json" --context "r5fss0-0" --part ALX --package ALX --compiler ticlang
Running script...tr
subdir_rules.mk:9: recipe for target 'build-1286570383' failed
OOM
RuntimeError: abort(OOM). Build with -s ASSERTIONS=1 for more info.
    at y (C:\ti\ccs1250\ccs\utils\sysconfig_1.18.0\dist\webpack:\src\pinmux\services\solver\glucose.js:7:110)
    at m (C:\ti\ccs1250\ccs\utils\sysconfig_1.18.0\dist\webpack:\src\pinmux\services\solver\glucose.js:77:392)
    at null.<anonymous> (wasm://wasm/0004f042:1:8484)
    at null.<anonymous> (wasm://wasm/0004f042:1:13429)
    at null.<anonymous> (wasm://wasm/0004f042:1:4535)
    at null.<anonymous> (wasm://wasm/0004f042:1:17704)
    at null.<anonymous> (wasm://wasm/0004f042:1:36853)
    at apply (wasm://wasm/0004f042:1:56202)
    at glucoseSolve (C:\ti\ccs1250\ccs\utils\sysconfig_1.18.0\dist\webpack:\src\pinmux\services\solver\glucose.js:83:78)
    at Object.solve (C:\ti\ccs1250\ccs\utils\sysconfig_1.18.0\dist\webpack:\src\pinmux\services\solver\glucoseFunctions.ts:208:19)
gmake: *** [build-1286570383] Error 1
gmake: Target 'all' not remade because of errors.

**** Build Finished ****

  • 0 in reply to Tron
    TI__Expert 5945 points

    Hi Tron,

    Can you please attach the new .syscfg script that leads to the crash?  I'll see if I can find a workaround until the SDK fix is in place.

    Darian

  • 0 in reply to Darian Sale
    Prodigy 170 points

    Thanks, Darian.

    For anyone else reading this with this OOM challenge, make sure you modify the correct Sysconfig install because you may have doubles: we had the same version installed twice, one in C:\ti and another in C:/ti/ccs1250/ccs/utils/.