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

AM263P4: strange behavior of sysconfig after changing the other setting

Jeeuk Chang
Prodigy 240 points
Part Number: AM263P4
Other Parts Discussed in Thread: SYSCONFIG, UNIFLASH

Tool/software:

Hi, TI experts.

-------------------------------

My environments

- CCS v12.8.1 and CCS v20.1.1.8

- Sysconfig 1.23.0

- MCU+ SDK for AM263Px v10.02.00.15

-------------------------------

I imported "examples/drivers/boot/sbl_uart_uniflash" example.

When I build the project just after importing it, it works well like pre-built SBL file. (sbl_uart_uniflash.release.tiimage)

Next step, I checked a syscfg file.

The original syscfg file was made maybe at sysconfig v1.20.0 and sysconfig v1.23.0 forces selecting exact chip information.

Just selecting chip information did not activate "save" menu and I changed the contents slightly. (or revert to original value)

After then, the output tiimage file did not work normally.

-------------------------------

I found when I modify sysconfig contents the OSPI output pin settings are automatically modified.

For example, I modified the name of OSPI then the OSPI output pin settings are automatically modified.

I think the settings should not change since there are no interfering pins.

I do not know if this phenomenon has been around for a long time, but I think it needs to be corrected.

Best regards,

Jeeuk Chang

  • 0
    TI__Mastermind 44734 points

    Hi Jeeuk,

    Jeeuk Chang said:

    I found when I modify sysconfig contents the OSPI output pin settings are automatically modified.

    For example, I modified the name of OSPI then the OSPI output pin settings are automatically modified.

    This expected only when you add OSPI module in syscfg for the first time. If you have saved it as you mentioned in thread it should not happen.

  • 0 in reply to Nilabh Anand
    Prodigy 240 points

    Hi Nilabh Anand.

    I imported sysconfig file of example and the sysconfig file exists already.

    And I did not add a new OSPI module. It also existed already.

    The pin changing occurred also when I modified the other features. (for example, I modified memory setting.)

  • 0 in reply to Jeeuk Chang
    TI__Mastermind 44734 points

    Hi Jeeuk,

    I tried it on my setup, but I am unable to reproduce the issue.
    Are you able to consistently see the issue?

  • 0 in reply to Nilabh Anand
    Prodigy 240 points

    Hi Nilabh Anand.

    Today I tested it with standalone sysconfig (v1.23.1) and I got the same result.

    ----------

    1. I imported the example : {MCU+SDK}/examples/drivers/boot/sbl_uart_uniflash_am263px-cc ~

    2. I opened syscfg file of the example with standalone sysconfig. (v1.23.1)

    3.A device selection popup appears. Whatever I select in a drop list, it is not important.

    4. Open "OSPI" settings. Pin settings are all "ANY" attached.

    5. In this stage, if I change a certain setting slightly, OSPI pin settings are changed.

    (for example, I tried changing the name of OSPI instance.)

    ----------

    I did not define the chip name exactly in the above process.

    At this time, I confirm chip information with "switch" menu in Device View between 3 stage and 4 stage.

    Then all uncertain pin settings of OSPI are fixed and it has no problems.

    ----------

    These are my results.

  • +1 in reply to Jeeuk Chang
    TI__Mastermind 44734 points

    Hi Jeeuk,

    I understand the issue now, I have created a bug for the same for the next version of SDK to be fixed.

    Meanwhile, once you import the project , open the syscfg, please lock the pins of OSPI then try to modify the other modules like below:

    Then you will see exact pin number instead of ANY.

  • 0 in reply to Nilabh Anand
    Prodigy 240 points

    Hi, Nilabh Anand.

    I recognized and understood the pin lock feature.

    Thanks for your suggestion.