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.

AM5718: TimerSupport.availMask for DSP Timers

Part Number: AM5718
Other Parts Discussed in Thread: SYSBIOS

Tool/software:

Hello,

I'm looking to add additional Timers to our DSP Application for the AM5718 Processor using the TimerSupport Module. I've followed the directions in the documentation to add Timers 13 through 16, however I keep seeing a runtime error for using unallocated Timers. My current understanding is the DSP by default has Timers 5 & 6 enabled, one of which is used for the SYSBIOS Clock Tick. I've attempted using Timers 7/8 as well with the TimerSupport.availMask set to 0x00F0 without any luck either. Are there any existing further examples on how to implement more than the two Timers for the DSP, or is there a step that I'm missing in initialization here?

Documentation Link for Reference:

https://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/sysbios/6_73_00_12/exports/bios_6_73_00_12/docs/cdoc/ti/sysbios/family/shared/vayu/TimerSupport.html

Code Reference for the cfg File:

 var Timer = xdc.useModule('ti.sysbios.timers.dmtimer.Timer');
  var IntXbar = xdc.useModule('ti.sysbios.family.shared.vayu.IntXbar');
  var TimerSupport = xdc.useModule('ti.sysbios.family.shared.vayu.TimerSupport');

  // The new availability mask includes GP Timers 13, 14, 15 & 16.
  // The interrupt sources for these timers is not connected to the
  // DSP and need to be connected by the user.
  TimerSupport.availMask = 0xF000;

  // Connect GP Timer 13 to EventId 76 (XBAR Instance 45)
  IntXbar.connectMeta(45, 339);

  // Connect GP Timer 14 to EventId 77 (XBAR Instance 46)
  IntXbar.connectMeta(46, 340);

  // Connect GP Timer 15 to EventId 78 (XBAR Instance 47)
  IntXbar.connectMeta(47, 341);

  // Connect GP Timer 16 to EventId 81 (XBAR Instance 49)
  IntXbar.connectMeta(49, 342);

  // The DMTimer's timer mapping table shows that the intNum
  // for GP Timer 13, 14, 15 & 16 is -1 implying the intNum
  // has not been assigned by default. The below code utilizes
  // the DMTimer module's timerSettings array to assign
  // a default intNum to each of these timers.
  Timer.timerSettings[12].intNum = 14;
  Timer.timerSettings[13].intNum = 15;
  Timer.timerSettings[14].intNum = 4;
  Timer.timerSettings[15].intNum = 5;

Error Trace: