• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 30 subscribers
  • Views 287 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.

LP-AM243: MCSPI issues updating from MCU plus SDK v08.01.00.36 to v08.02.00.31

Jesse Baker
Expert 7950 points
Part Number: LP-AM243
Other Parts Discussed in Thread: SYSCONFIG,

Hi,

I have an existing project working on the LP-AM243 with SDK v08.01.00.36 and I am trying to update to v08.02.00.31. I configured the SysConfig settings in my updated project to be exactly the same as my project on the old SDK, but the MCSPI peripheral isn't behaving as expected.

Is there any insight as to what my issue could be here? I see that there is a v0 and v1 folder in the newest SDK under source/drivers/mcspi, while the old sdk just had a v0 folder. Could this be the source of the issue?

Best regards,

Jesse

  • 0
    TI__Guru 54955 points

    Hi Jesse,

    The AM243x is using MCSPI v0. It is defined in C:\ti\mcu_plus_sdk_am243x_08_02_00_31\source\drivers\hw_include\am64x_am243x\soc_config.h. The MCSPI v1 is used by other Sitara MPU SoC.

    One thing may need you attention: MCU+ SDK 08.02.00.31 is using sysconfig-1.11.0_2225, while MCU+ SDK 08.01.00.36 were using sysconfig-1.10.0_2163. You may need to update your SysConfig accordingly.

    Best regards,

    Ming

  • 0 in reply to Ming Wei
    TI__Expert 7950 points

    Hi Ming,

    Thanks for the clarification on MCSPI v0 and v1.

    I am using SysConfig version 1.11 so I don't believe that is the issue.

    I did notice that when I update the AM243x SDK in CCS from 8.1.0.36 to 8.2.0.31, I get the following error in the example.syscfg file, and when I click "Go Back" I end up having to reconfigure my sysconfig settings the way they were before.

    I noticed that when I when configuring the MCSPI in example.syscfg in SDK 8.1.0.36, under MCSPI Channel Configuration, there is a field for Data Frame Size (bits) which I have set to 32. But when I'm configuring the MCSPI in example.syscgf in SDK 8.2.0.31, I don't see Data Frame Size as a field to set. I've attached comparison photos below.

    Could this cause issues? Do you know where I can set this value using v8.2.0.31 of the SDK?

    8.1.0.36

    8.2.0.31

    Best regards,

    Jesse

  • +1 in reply to Jesse Baker
    TI__Guru 54955 points

    Hi Jesse,

    You are correct. The way MCU+ SDK handles data frame size in 08.01.00.36 and 08.02.00.31 is different:

    08.01.00.36:

    Sysconfig set Data Frame Size to  gConfigMcspi0ChCfg[0].dataSize,

    then it passed to dataWidth with "dataWidth  = gConfigMcspi0ChCfg[0U].dataSize;" when  MCSPI_setDataWidth(baseAddr, chNum, dataWidth) is called.

    08.02.0.31:

    dataWidth is set to 32, when  MCSPI_setDataWidth(baseAddr, chNum, dataWidth) is called.

    Best regards,

    Ming