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.

AM5728: Functional changes of eCAP, eQEP, eHRPWM

Guru 15520 points
Part Number: AM5728
Other Parts Discussed in Thread: AM4379

Hi,

I have a question about eHRPWM, eCAP, eQEP of AM4379 and AM5728.
My customer are using eCAP, eQEP, and eHRPWM of AM4379 on production board.
Now they are planning to use AM5728 on new board and also eCAP, eQEP, eHRPWM of AM5728 will be used.

They would like to use eCAP, eQEP, eHRPWM the same way as AM4379.
So, they want to know if there are any changes in eCAP, eQEP, eHRPWM between AM5728 and AM4379.
For example, if setting the same values to the appropriate registers, does it operate exactly the same?

The GPMC Bus Clock frequency was different between AM572x and AM437x.
So, they want to know if there are any changes against the same function.

best regards,
g.f.

  • Hi g.f.,

    In general, the eCAP, eQEP, and eHRPWM operate the same between AM4379 and AM5728. The only register difference I'm aware of is that the PWM’s HRCTL register is at a different offset. However, there are some SoC integration differences (i.e. where the PWMSS interrupts are routed to on the device, the max frequency for the functional clock source, etc.) These details can be found in the device TRM.

    I am looking into your GPMC question and will get back with you.

    Regards,
    Melissa
  • Hi Melissa,

    Thank you for the relpy.
    I understood that eCAP, eQEP, and eHRPWM will operate the same between AM4379 and AM5728.
    But the max frequency was different(AM4379:max 100MHz, AM5728:max 266MHz), so that they need to
    change the register value which depend to the functional clock.

    best regards,
    g.f.

  • Hi g.f.-san

    As you stated the GPMC_FCLK is 266MHz on the AM57x family. The GPMC_FCLK frequency for AM437x is 100MHz.
    Consequently, the GPMC_config registers that are used with AM437x need to be modified when running on AM57x.

    The GPMC_CONFIG_n registers trigger events using counters that increment with each GPMC_FCLK cycle. With the GPMC_FCLK being 2.66x faster on AM57x, the counter values need to be increased by ~2.66x to maintain the same timings on the GPMC pins as with AM437x. If the counter does not have enough counts (ie more than 31 counts are required), then the TIMEPARAGRANULARITY bit can be set to increase the counter every other cycle instead of every GPMC_FCLK cycle.

    If the GPMC_CLK is being used, the datasheet for AM57x states that the maximum GPMC_CLK supported is 88.7MHz. To achieve this frequency, GPMCFCLKDIVIDER must be set to a value of 2, so that the 266MHz clock is divided by 3. Rules for synchronous transfers must be followed (for both write and read cycles): processors.wiki.ti.com/.../Tips_for_configuring_Sitara_GPMC_registers

    Additionally, the AM57x supports 8 chip selects, while AM437x supports 7 chip selects.

    The number of address lines and addressable range is the same. Documentation is slightly different however regarding whether GPMC_A[1] carries A0 or A1 in 16-bit mode.
    AM437x states that A0 appears on GPMC_A[1] in Non-muxed, 16-bit mode (with the note (1) below).
    AM57x states that A1 appears on GPMC_A[1] in Non-muxed, 16-bit mode (without any note).

    “(1) The values in this column represent the signals on the memory. Be aware that some 16-bit memories may label the address lines differently. Some label (the LSB as A0, while others use A1 for the LSB. These columns assume the LSB is A0.”

    What is the use case for the GPMC? Synchronous/Asynchronous, burst/non-burst, Non-muxed/AD-muxed/AAD-muxed, etc.?

    Let me know if they need help modifying the GPMC_CONFIG registers to achieve the same function.

    Regards,
    Mark

    [EDIT - AM437x  instead of AM335x]

  • Hi Mark-san,

    Thank you for the details and I'm sorry for the delay response from me.
    I understood and I'm clear now.

    By the way, the use case for the GPMC is Synchronous/burst/AD-muxed.

    For now, it seems that my customer are doing fine and have no question so far.
    Thank you so much for the support.

    best regards,
    g.f.