AM2634-Q1: 50us timer interrupt using ClockP_construct function of DPL

Hi Hideaki Matsumoto,

You can use RTI for the same. Let me share detailed steps by Thursday for the same.

Best Regards,
Aakash

Hi Aakash,

Thank you for your reply. OK, I'm waiting for the detailed steps until Thursday.

Thanks and regards,
Hideaki

Hi Aakash,

Thank you so much for your answer, but let me confirm the above GUI.

Is it SysConfig tool ?

Were you able to set 50us Tick Period ? As mentioned at the first post in this thread, they cannot set 50us on the Sysconfig.

Hideaki Matsumoto said:

but the minimum value that can be set for Clock->Tick Period (usecs) in sysconfig is 100(us). They were not able to create a 50us periodic timer interrupt.

Do you know why they cannot do that ?

Thanks and regards,
Hideaki

Hi Hideki,

Hideaki Matsumoto said:

My customer wants to create a 50us timer interrupt using the Driver Porting Layer's ClockP_construct function, but the minimum value that can be set for Clock->Tick Period (usecs) in sysconfig is 100(us). They were not able to create a 50us periodic timer interrupt.

Is there a way to implement a 50us timer interrupt ?

Could you clarify why customer was not able to modify the syscfg, as Aakash suggested it it possible to modify the value to 50 in syscfg, Please share the above with customer and let me know in case they still face the issue.

Hi Aakash, Nilabh,

The error occurs as "Value must be between 100 .. 1000000" on the SysConfig when they set 50us in th Tick Period cell. See the attached figure.

They're using the latest SysConfig v1.18.0.

Thanks and regards,
Hideaki