• State Answer Suggested
  • Locked Locked
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 97 subscribers
  • Views 356 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.

OMAP 35xx : Can't access GPIO1 module ??

IsaacLeung
Intellectual 395 points

I'm trying this on Mistral EVM, under U-Boot. (Default configuration)

For some reason, I can't even read any memory region for GPIO1 module (0x48310000 to 0x48310FFF) , this causes U-Boot to hang.

This is rather odd, I can read and configure all the other GPIO modules, I can access the register that controls the MUX mode. I can even get at all the other modules situated around GPIO1 module memory space (i.e. WDTIMER2, GPTIMER1, Power & Reset manager).

Is there anything special about GPIO1 module? Is there some particular mode or pin usage on some of the pins which would cause me not to be able to use  or even look at this particular region in memory?

  • 0
    Intellectual 395 points

    Seems like at default (or perhaps U-Boot configures this), funny thing, GPIO1 is not available.

    To get at it, configure the interface clock for GPIO1 and possibly the GPIO1 functional clock as well. (look at CM_FCLKEN_WKUP and CM_ICCLKEN_WKUP), make sure they are enabled.

    At least that's how I've gotten it to work so far. If anyone has a better explanation or answer, please feel free to elaborate.