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.

TMS320F28388D: Development concept for commisioning of particular subsystems...

Part Number: TMS320F28388D
Other Parts Discussed in Thread: C2000WARE

Dear Sir,

related to the pending R&D activities on the electronic module based on one of the models from the latest generation of TI2000 series MCUs (e.g. F28379D and F28388D), I would like to know is it possible to apply gradual/partial R&D concept? In other words is it opportune to implement first the support only for the most required subsystems/peripherals (ADC subsystem, ePWM subsystem, eCAP…), i.e. while other subsystems (e.g. most of high-speed communication subsystems…) are left uninitialized (including internal ARM-M4 extension within F28388D model)? Is there a safe way to secure blockade of all unused subsystems, in order to avoid any related functional safety problems due to systematic/randomly triggered events within the MCU (potentially caused by the impact of unused subsystems to the target system)? What would you suggest as the most effective R&D roadmap for the design of the electronic module based on one of the previously mentioned MCU flagships...

Best regards

Nenad T.

At later R&D stages of that electronic module, all available subsystems/features provided by the MCU are supposed to be completely supported by the appropriate code generator employed by the dedicated Target Support Package (TSP) for our graphically oriented IDE (Integrated Development Environment), of course.

  • Hi Nenad, 

    I hope you had the opportunity to download the C2000Ware software, CCS, Compiler tools also have access to all the training material we have.  If not, please let us know and we will provide you with all of that collateral. 

    If you have the above, you can study our examples where you will see that the initialization code, for many of our targets, provides the ability to enable and disable peripherals.  It is along the lines of what you are asking about in your post.  Sure, you can disable the peripherals that you are not using and it will not only save power but it will also ensure that unused peripherals are not interfering with normal operations in any way. 

    Hope this helps.  Please let us know if we can be of any further assistance. 

    Cheers!

    Krshna

  • High Krshna,

    thank you indeed for your answer. It confirms what I was hoping for (the ability to explicitly enable/disable peripherals). So far I did not need any SW tools related to the code generation (other colleagues in my team have been in charge of that). I did install C2000Ware, CCS... and would appreciate if you could provide me all that collateral (training materials etc.).

    Best regards

    Nenad

  • Hi Nenad, 

    You can do a deep dive with the training material that we have available here: https://training.ti.com/c2000-workshops