Other Parts Discussed in Thread: TMS320F28377D,
Hello.
I am looking through a few examples of codes in Code Composer Studio, and wondered what exactly does one need to get up and running when developing their OWN code?
It seems that in every example I am looking at, all the header files, assembly codes, etc are unique. Is there any kind of "skeleton" that one needs to get up and running, a framework on which to build our own codes?
My MCU is the F2837xD, and I am designing a power converter which has a resonant converter LLC, and a flyback converter in parallel which needs to be very accurate - so I plan to use the high resolution PWM for that with a high switching frequency. I navigated to the HRPWM example folders and there seems to be some kind of "skeleton" code in here - includes the following files:
2837xD_RAM_lnk_cpu1.cmd
2837xD_FLASH_lnk_cpu1.cmd
The linker file TMS320F28377D, and then a folder of "device" which includes device.c, device.h, driverlib.h, and F2837xD_CodeStartBranch.asm.
Are these specific to this file, or can I use them to begin writing my own code?
I am finding the number of examples very, very informative - thankful for that. However, I really am struggling to find a resource that runs me through "how" to start writing my "own" code, logically and sequentially.
A bit more information: Since I am running two power converters in parallel, I thought the best route would be to assign CPU1 to one converter, and CPU2 to the other converter, and assign each a CLA if needed. Is there any benefit to doing the computations in this way, or is it best to just utilize CPU1?
Thanks for any advice on this.
Regards,
Joel
