• State Resolved
  • Locked Locked
  • Replies 12 replies
  • Answers 3 answers
  • Subscribers 31 subscribers
  • Views 532 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.

AM2634: Sysconfig pins not configurable

Mari Tsunoda
Expert 5726 points
Part Number: AM2634
Other Parts Discussed in Thread: SYSCONFIG

Hi Team,

My customer is configuring SysConfig, but could not configure the two pins below:

  • A9: OSPI0 ECC FAIL could not be configured
  • LB: sysconfig does not have LB pin

Are these pins not configurable via sysconfig?

They are using sysconfig versions 1.18.0.3266 and 1.19.0.3426, but could not configure on both versions.

Best regards,

Mari Tsunoda

  • 0
    TI__Mastermind 24583 points

    Hello Mari,

    I have received your question and will look into it with the OSPI expert. Please provide up to two days for a response.

    Best Regards,

    Zackary Fleenor

  • 0 in reply to Fleenor
    TI__Expert 5726 points

    Hi Zackary,

    Any update on this?

    -Mari

  • 0 in reply to Mari Tsunoda
    TI__Mastermind 24583 points

    Hey Mari,

    Sorry for the delay here. AM263x devices use the QSPI IP (not OSPI) and does not support the ECC_FAILn signal. The QSPI_CLKLB pin is configured as a virtual pin as it is a pad only signal and remains internal to the package.

    What is the expectation for QSPI_CLKLB configuration option? I will need to work with the team on an update for exposing the signal in the QSPI configurables.

    Best Regards,

    Zackary Fleenor

  • 0 in reply to Fleenor
    TI__Expert 5726 points

    Hi Zack,

    Sorry, my customer was referring to the AM263Px device. I believe the ECC_FAILn signal should be supported then? 

    Fleenor said:
    The QSPI_CLKLB pin is configured as a virtual pin as it is a pad only signal and remains internal to the package.

    Is it ok to assume that this is also applicable to the OSPI interface?

    -Mari

  • 0 in reply to Mari Tsunoda
    TI__Mastermind 24583 points

    Hey Mari,

    This is correct, the AM263Px OSPI IP supports the ECC_FAIL signal and it is present in the PMT along with LBCLKO. The OSPI interface does still have the CLKLB pad-only signal which remains internal to the package, but supports the LBCLKO (Loopback Clock Out) pin for OSPI clocking topology requirements.

    Best Regards,

    Zackary Fleenor

  • 0 in reply to Fleenor
    TI__Expert 5726 points

    Hi Zackary,

    Thanks for your response.

    I was looking at sysconfig and couldn't find the ECC_FAIL signal. Am I looking at the wrong place?

    I also only see the LBCLKO setting in the reserve peripheral tab but not the software tab. Should they configure this in the reserve peripherals tab then?

    I am using online sysconfig so I assume this is the newest version available. Can you tell me what version of sysconfig you are using?

     software tab

    reserve peripheral tab

    -Mari

  • 0 in reply to Mari Tsunoda
    TI__Mastermind 24583 points

    If you use the raw pinmux tool (don't select an SDK), then the option is available for configuration. I will file a ticket with the SDK team to resolve this issue from the OSPI SDK side.

    Best Regards,

    Zackary Fleenor

  • 0 in reply to Fleenor
    TI__Expert 5726 points

    Hi Zackary,

    Thanks for your reply.

    I did as you mentioned, but this is what shows up for me when I use the online sysconfig tool.

    Am I choosing wrong in the sysconfig menu?

    Best regards,

    Mari

  • 0 in reply to Fleenor
    TI__Mastermind 24583 points

    Hello Mari,

    Apologies for the confusion. I just confirmed that this change is represented in the SysConfig 1.20.0 release expected later this week.

    Best Regards,

    Zackary Fleenor

  • 0 in reply to Fleenor
    TI__Expert 5726 points

    Hi Zackary, 

    Thanks, I see that it has been reflected now.

    Since they use sysconfig with the SDK selected in the menu, how are they supposed to migrate the changes from adding the ECC fail and LB signals from non-product version to a product selected version?

    Or is there no way to migrate it? If not, are there any plans to support the signals in the product-selected version?

    Best regards,

    Mari Tsunoda

  • 0 in reply to Mari Tsunoda
    TI__Mastermind 24583 points

    Hey Mari,

    There is a ticket filed to have these signals included in the SDK configuration options. I will check on the timeline for this update.

    Best Regards,

    Zackary Fleenor

  • +1 in reply to Fleenor
    TI__Mastermind 24583 points

    The update will be included in the MCU_PLUS_SDK v10.0.0 release, I believe this is expected in Q42024 timeframe. The pinmux configuration output text generated by the standalone PMT can be copy and pasted into the project files, but CCS should be configured to not regenerate config files from the .syscfg file to prevent the manual changes from being overridden by the sysconfig configuration.

    Best Regards,

    Zackary Fleenor