Search

Technical Discussion Group Forum

This forum is provided for user discussion. While Beacon EmbeddedWorks support staff and engineers participate, Beacon EmbeddedWorks does not guarantee the accuracy of all information within in the Technical Discussion Group (TDG).

The "Articles" forums provide brief Articles written by Beacon EmbeddedWorks engineers that address the most frequently asked technical questions.

To receive email notifications when updates are posted for a Beacon EmbeddedWorks product download, please subscribe to the TDG Forum of interest.

TDG Forum

PrevPrev Go to previous topic
NextNext Go to next topic
Last Post 02 Apr 2012 02:25 PM by  glennj@logicpd.com
Article: OMAP-L138 silicon 2.0+ does not boot 2.6.33 kernel
 0 Replies
Sort:
You are not authorized to post a reply.
Author Messages
glennj@logicpd.com
New Member
New Member
Posts:


--
02 Apr 2012 02:25 PM
    Q:
    How do I get the OMAP-L138 silicon revision 2.0+ to boot with the Linux 2.6.33 kernel?

    A:
    The new revision boards were getting stuck in setup_arch() when the CPU ID is determined. There were accommodations in 2.6.33 for silicon revisions up to 1.1 but not for 2.0+ as there are in 2.6.37. To account for this, Below is a patch for the following change:

    In kernel linux-2.6.33/arch/arm/mach-davinci/da850.c, add a definition to da850_id list which is needed for OMAP-L138 silicon revision 2.0+

    /* Contents of JTAG ID register used to identify exact cpu type */

    static struct davinci_id da850_ids[] = {
    {
    .variant = 0x0,
    .part_no = 0xb7d1,
    .manufacturer = 0x017, /* 0x02f >> 1 */
    .cpu_id = DAVINCI_CPU_ID_DA850,
    .name = "da850/omap-l138",
    },
    /* Added definition for variant 0x01 which is needed for silicon revision 2.0+ */
    {
    .variant = 0x1,
    .part_no = 0xb7d1,
    .manufacturer = 0x017, /* 0x02f >> 1 */
    .cpu_id = DAVINCI_CPU_ID_DA850,
    .name = "da850/omap-l138/am18x",
    },


    Products Included:
    OMAP-L138
    You are not authorized to post a reply.