• State TI Thinks Resolved
  • Locked Locked
  • Replies 7 replies
  • Answers 2 answers
  • Subscribers 100 subscribers
  • Views 620 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.

AM623: Warning showing in Sysconfig

Johnny Chen
Expert 5310 points

Part Number: AM623

Tool/software:

Hi Champ,

I am asking for my customer. 

(1). MCU_RESETSTAT & MCU_RESETz, it is used VDDSHV_MCU with 3.3V. Showing warning with Voltage conflict, is it abnormal ? Does user have to do with any fix on that ?

(2).MCU_RESETSTAT, it is used VDDSHV_MCU with 3.3V, then the following warning appears with the configuration in GUI 

"Read only value changed. This is likely caused by an incorrect text edit of the script, a backwards compatibility discrepancy, and/or by a unsaved change that temporarily made this value writable."

The Voltage setting reference DEBOUNCE CIRCUIT schematic is in PROC142E1_SCH_SK-AM62-P1 EVM Page 43

What is the warning meaning in customer's design or configuration ? 

Asking on does user have to fix the warning or may ignore (suppress) it ? And how to fix it ?

Thanks and regards,

Johnny

  • 0
    TI__Guru 54908 points

    Hello Johnny,

    I am looking at your queries, and you may expect reply in one or two days.

    Regards,

    Anil.

  • 0 in reply to Swargam Anil
    TI__Expert 5310 points

    Hi Anil,

    Any luck to have some update on this ?

    Thanks and regards,

    Johnny

  • 0 in reply to Johnny Chen
    TI__Guru 54908 points

    Hello Johny,

    Even if you configure anything in the reserved peripherals window,  syscfg is not generated any code.

    Johnny Chen said:
    Asking on does user have to fix the warning or may ignore (suppress) it ? And how to fix it ?

    Please you can skip this setting and there are no problems.

    Regards,

    Anil.

  • 0 in reply to Swargam Anil
    TI__Expert 5310 points

    Hi Anil,

    Thanks for taking time to look at the query and the input.

    Swargam Anil said:
    Please you can skip this setting and there are no problems.

    Are you saying the warning for both questions 1 & 2 could be skipped w/o problem ? 

    Any information about why the warnings pop out ?

    Regards,

    Johnny

  • 0
    TI__Guru 64018 points

    Hi Johnny,

    Johnny Chen said:
    MCU_RESETSTAT, it is used VDDSHV_MCU with 3.3V, then the following warning appears with the configuration in GUI 

    Can you please tell how are you modifying this value? 

    As I can see this is a read only field and is not configurable. The Warning message also clearly says, "Read only value changed".

    The preferred voltage value for the above pin is configured as 1.8 V. The above conflict is coming because you are trying to configure it to 3.3 V.

    Please refer highlighted section in the below image.

    Regards,

    Tushar

  • 0 in reply to Tushar Thakur
    TI__Expert 5310 points

    Hi Tushar,

    Customer configures VDDSHV_MCU to 3.3V in power domain is because the voltage reference as PROC142E1_SCH_SK-AM62-P1 EVM Page 14 shown, and a corresponding relationship can also be found in GPIO MAPPING TABLE, as follows:

    It is true that all warnings are removed after power domain is set to 1.8V, and 1.8V as preferred voltage for MCU_SYSTEM. 

    Therefore, to confirm the setting in power domain should be 1.8V ? With such configuration, it won't match to above diagram. Would you clarify on this with our EVM schematic and GUI configuration ?

    Thanks and regards,

    Johnny

  • 0 in reply to Johnny Chen
    TI__Guru 64018 points

    Hi Johnny,

    Johnny Chen said:
    It is true that all warnings are removed after power domain is set to 1.8V, and 1.8V as preferred voltage for MCU_SYSTEM. 

    There are different power domain associated with the MCU_SYSTEM. 

    MCU_ERRORN and MCU_PORZ is connected grouped with Power Domain VDD_OSC, similarly MCU_RESETSTATZ and MCU_RESETZ is grouped with VDDSHV_MCU & EXTINTN, PORZ_OUT, RESET_REQZ, RESETSTATZ is grouped with VDDSHV0. 

    Please refer below image.

    The conflict is coming because the VDDSHV_MCU has dual voltage IO supply(i.e. 1.8/3.3V) but the VDDS_OSC0 only supports 1.8 V. when you try to configure MCU_SYSTEM to 3.3V the VDDS_OSC0 gives warning about voltage conflict.

    Please refer to device datasheet for more info. Please refer below image.

    Johnny Chen said:
    Therefore, to confirm the setting in power domain should be 1.8V ? With such configuration, it won't match to above diagram. Would you clarify on this with our EVM schematic and GUI configuration ?

    The pinmux tool doesn't have any impact on power domain configured, As I can not see any code that is getting generated when the power domain values are changed. The Pinmux tool can provide you the option to modify the pin functionality supported by the device.

    Hope the above information helps.

    Regards,

    Tushar