• State
  • Locked Locked
  • Replies 1 reply
  • Subscribers 98 subscribers
  • Views 485 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 4460 - migration from pandaboard

Jozef Krivjansky
Prodigy 20 points

Hi all,

We have my prototype design build on Pandaboard. But there are many features missing so we created custom board. The pinout is a bit different from Pandaboartd. I have foud "Pad configurator tool". 

There is no pre-defined name of file and I do not know whch file I have to change in kernel for our custom board.

Is there any manual what to change in kernel for different pinout?

Thanks.

  • 0
    TI__Mastermind 29520 points

    Hello Jozef,

    The only available reference documents for OMAP4 are:

    - OMAP4 TRM Technical reference manual

    - OMAP4 DM Data manual

    Both are available through http://www.ti.com/product/omap4460

    What is your kind of Operating System?

    If you use Linux or Android releases see the following:

    At first, You must change board-omap4panda.c file. Available in arch/arm/mach-omap2/ board-omap4panda.c

    This file contains definitions of the specific features for your design.

    The structure struct omap_board_mux board_mux[] __initdata - defines mux-mode settings for some pads.

    In file - arch/arm/mach-omap2/mux44xx.c are defined:

    - Superset of all mux modes for omap4

    - Balls for 44XX CBL package

    - Balls for 44XX CBS package

    - Balls for 44XX CBL & CBS package - wakeup partition

    #define _OMAP4_MUXENTRY(M0, g, m0, m1, m2, m3, m4, m5, m6, m7)    \
    {                                    \
        .reg_offset    = (OMAP4_CTRL_MODULE_PAD_##M0##_OFFSET),    \
        .gpio        = (g),                        \
        .muxnames    = { m0, m1, m2, m3, m4, m5, m6, m7 },        \
    }

    #else

    #define _OMAP4_MUXENTRY(M0, g, m0, m1, m2, m3, m4, m5, m6, m7)    \
    {                                    \
        .reg_offset    = (OMAP4_CTRL_MODULE_PAD_##M0##_OFFSET),    \
        .gpio        = (g),                        \
    }

    #endif

    #define _OMAP4_BALLENTRY(M0, bb, bt)                \
    {                                    \
        .reg_offset    = (OMAP4_CTRL_MODULE_PAD_##M0##_OFFSET),    \
        .balls        = { bb, bt },                    \
    }

    Best regards,

    Yanko