• State
  • Locked Locked
  • Replies 1 reply
  • Subscribers 30 subscribers
  • Views 386 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.

RM44L520PZ: HalCoGen 4.06 shows conflict between EQEP and GIOA_2 pin, why?

Matthias Schmitt
Expert 5560 points
Other Parts Discussed in Thread: HALCOGEN

Dear Hercules-team,

my customer is trying to use the EQEP module and the GIOA_2 pin and is getting a "Conflict" for GIOA_2 when enabling the EQEP module in the PINMUX of HalCoGen v4.06 (latest release).

We do not see any specific relationship of GIOA_2 and the EQEP module.

Might this be a bug in the PINMUX tool?

Please provide a solution on how EQEP and GIOA_2 can be used independently.

BR,
Matthias

  • 0
    TI__Guru 68930 points

    Matthias,

    Thanks - this is a bug in the pinmux tool.
    The generated code to me seems ok:
    pinMuxReg->PINMMR2 = PINMUX_PIN_5_GIOA_2 | PINMUX_PIN_10_GIOA_5;
    in the sense that it still selects GIOA_2

    So you could suggest living with the issue for now until we fix it. I'll file a ticket. But otherwise there could be some XML edits made into the HalCoGen folders which might remove the 'conflict' bar but that would not really change the outcome in terms of code generated. So probably not worth doing it.

    -Anthony

    EDIT: ticket filed is SDOCM00122787