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

AM2432: Sysconfig Reset and Power Domain

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

Hi Team,

My customer has a questions regarding sysconfig as below.

  1. We plan to pull RESET_REQz, MCU_RESETz to High, and will not use warm reset. In this situation, when setting the pins, Peripherals->SYSTEM->RESET_REQz and POeripherals->MCU_SYSTEM->MCU_RESETz, do they need to tick these boxes? If they don't and RESET_REQz, MCU_RESETz are open, will these two signals be invalid and will they have issues (such as suddenly resetting)?
  2. We don't use EMU0, EMU1, MCU_RESETz, RESET_REQz signals, and on PWB these pins are supposed to be un-connected to any node, and we will use internal pull-up resistor on these pins. According to 6.4 Pin Connectivity Requirements on AM243x datasheet, "The internal pull-up may be used to hold a valid logic high level if no PCB signal trace is connected to the ball."
    But in Reversed Peripherals->JTAG tab of Sysconfig tool, I can't find the selection of Pullup/Pulldown. Where Can I set the internal pull-up using Sysconfigtool?
  3. In the power domains tab, they set VDDSHV_MCU=3.3V (Other than clock and DDR, all are set to 3.3V). Since MCU domain IO is also 3.3V, they set Peripherals->MCU_SYSTEM->Preferred Voltage to 3.3V. However, they have a voltage conflict with MCU_PORz. As this is most likely due to MCU_PORz is set to VDDSHV_OSC=1.8V (set in domain IO pin). Is it ok to leave this as a conflict. 
  4. Also, is their understanding that MCU_RESETz is set to 3.3V, MCU_PORz is set to 1.8V signals correct?

Best regards,

Mari Tsunoda

  • +1
    TI__Mastermind 22685 points

    Hi,

    1.  These signals do not have any pad config register associated with them, so selecting or unselecting them does not change any of the output from sysconfig.  The selection is for the user to know if they are used or not, so unselected is ok.

    2.  The selection for pull up / pull down on these pins is greyed out since they should be set a specific direction, and they are hard coded that way.

    3.  It is ok to leave this as a conflict.  The conflict notice is due to the way sysconfig groups pins together, which can be ignored in this case.

    4.  Yes, their understanding is correct.

    Thanks,
    Mike

  • 0 in reply to Mike Pridgen
    TI__Expert 5726 points

    Thanks Mike!

    -Mari