Skip to main content
M
mark9
Visitor II
March 16, 2007
Question

Silicon Bug or mistake in Datasheet? on ETM_EXTRIG MII_MDC port 1.7

  • March 16, 2007
  • 1 reply
  • 431 views
Posted on March 16, 2007 at 03:22

Silicon Bug or mistake in Datasheet? on ETM_EXTRIG MII_MDC port 1.7

    This topic has been closed for replies.

    1 reply

    M
    mark9Author
    Visitor II
    May 17, 2011
    Posted on May 17, 2011 at 09:39

    Port 1.7, aka ETM_EXTRIG or MII_MDC causes weird behavior if SCU_GPIOIN1.7 is not 1. Supposedly, if this bit is cleared, then nothing happens on this pin according to table 4 of the data sheet. However, if the MII is used, whenever a packet arrives, the debugger halts!

    I looked at the documentation, and it seems there is a feature on Port 3.0 that has a similar feature. cf EXT_ETMT_EDBGR and P30_SELEDBG on SCU_SCR0. But Port 3.0 is not Port 1.7.

    Is there a mistake in the datasheet, table 4? Is the default input behavior of Port 1.7 actual ''External Debug Request''? Or is this a silicon bug?

    Terms & ConditionsAccessibility statement