# C-Script Blocks Prevent DSP Flashing on LAUNCHXL-F28379D

**URL:** <https://forum.plexim.com/t/c-script-blocks-prevent-dsp-flashing-on-launchxl-f28379d/3158>\
**Category:** TI C2000\
**Tags:** c-script, plecs-coder, c2000\
**Created:** [June 12, 2026, 1:19pm UTC](https://forum.plexim.com/t/c-script-blocks-prevent-dsp-flashing-on-launchxl-f28379d/3158 "2026-06-12T13:19:36Z")\
**Posts on this page:** 1\
**Showing post:** 9

<div class="post-metadata">

**Author:** ![Bryan\_Lieblick](https://dub1.discourse-cdn.com/flex006/user_avatar/forum.plexim.com/bryan_lieblick/32/10_2.png) [@Bryan\_Lieblick](https://forum.plexim.com/u/Bryan_Lieblick)\
**Post date:** [June 15, 2026, 6:55pm UTC](https://forum.plexim.com/t/c-script-blocks-prevent-dsp-flashing-on-launchxl-f28379d/3158/9 "2026-06-15T18:55:32Z")

</div>

If you test a simple model with a reasonable step size with the latest target support package release you should notice that the behavior is the same whether the C-Script or constant blocks are used. The problem only arises in the context of your complete model.

Your actual model has a CPU overrun when the C-Script is included. The C-Script block has more overhead than a basic constant block. However, your code was likely marginal to begin with as the discretization step size is 10 usec (100 kHz).

There is a [support article](https://forum.plexim.com/t/cpu-overruns-and-cpu-usage-a-debugging-guide/2877) further describing this issue and suggested next steps. These changes to your model are important as it looks like you ultimately want to add even more logic to your C-Scripts.

Another point is that you are doing the carrier compare in the model using PLECS blocks and then connecting to a GPIO. You should be using the PWM blocks which use the ePWM peripheral that generates the carrier in hardware. This will greatly improve the PWM resolution.

---

_[View the full topic](https://forum.plexim.com/t/c-script-blocks-prevent-dsp-flashing-on-launchxl-f28379d/3158)._
