Hi Sal, thanks for the suggestion. I see that that example project uses direct register access using the HWREG macros. I'm trying to stick with the structure/bitfield style API used by the example projects in the c2000ware "device support" folder (as opposed to the driverlib folder). Far easier to manage that way... I was able to find at least one example project, sdfm_filter_sync_cla_cpu01, which accesses peripherals via the normal API inside the CLA tasks. It includes several extra header files (F2837xD_cla.h, F2837xD_sdfm_drivers.h, F2837xD_struct.h, etc) in the .cla source file. Not sure how it works in the example project, including such files in my own just breaks things further....
↧