• State Resolved
  • Locked Locked
  • Replies 1 reply
  • Subscribers 85 subscribers
  • Views 283 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

Original question:

TMS320F28386S: Sysconfig: problem with Shared Peripheral Allocation

TMS320F28386S: Sysconfig: problem with Shared Peripheral Allocation

Ramon Martins
Prodigy 216 points
Part Number: TMS320F28386S
Other Parts Discussed in Thread: SYSCONFIG, C2000WARE

Hi there,

I am back with this topic. Is this the place to make suggestions about sysconfig tool?

Until now sdk: "C2000Ware 5.1.0.0", the sysconfig tool doesn't have a resource of does not include "myCanx_init" on Board_Init -> CAN_Init.

Therefore when you set a CAN to Communication manager, the program get stuck in the function CAN_initRAM(). This issue arises because this peripheral no longer belongs to CPU1, and its configuration must be set by the CM Core. My suggestion is to include a checkbox in each peripheral instance within sysconfig, allowing users to indicate whether they want to add this initialization to Board_Init(). Without this feature, utilizing CAN on the CM core renders the Board_Init() function unusable for functional code.

Best Regards,

Ramon

  • +1
    TI__Expert 6035 points

    Ramon, 

    Ramon Martins said:
    I am back with this topic. Is this the place to make suggestions about sysconfig tool?

    Yes, appreciate your suggestion. 

    Ramon Martins said:
    My suggestion is to include a checkbox in each peripheral instance within sysconfig, allowing users to indicate whether they want to add this initialization to Board_Init().

    I have filed a Jira for this issue, and it will be fixed in future C2000ware releases. 

    In the meantime, we can provide a workaround fix for this by Wednesday, 20th March. 

    Thanks.