Create Account
Search
You are here: TDG Forum  >>  Texas Instruments SOMs and Development Kits  >>  OMAP35x, DM3730, AM3703 Torpedo SOM Development Kit  >>  DM3730 Torpedo occasionally self-identifies as SOM-LV on custom carrier

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 07 Dec 2017 07:08 AM by  Stephen Newberry
DM3730 Torpedo occasionally self-identifies as SOM-LV on custom carrier
 4 Replies
Sort:
You are not authorized to post a reply.
Author Messages
Stephen Newberry
New Member
New Member
Posts:6


--
06 Dec 2017 09:15 AM

    Hello,

    We have a custom carrier using a LAN9221 and a USB device connected to the DM3730 Torpedo. We
    were noticing occasional failures on the LAN9221 and tracked it down to the board type/machine
    type being assigned as per console logs. Most of the time, the board is set as DM37xx Torpedo,
    but in about 15% of boot-ups, the board is set as DM37xx SOM LV. I believe this is dynamically
    set from omap3logic.c, and is supposed to change if there is a pull-down on HSUSB0_DATA5. Are
    any of the pins on the connector going to impact the results of that omap3logic pin check?
    Additionally, has anyone seen a situation where a SOM incorrectly self-identifies?

    Thank you,
    Stephen
    Adam Ford
    Advanced Member
    Advanced Member
    Posts:794


    --
    06 Dec 2017 09:39 AM
    Which version of the BSP are you using? We did correct some minor bugs in U-Boot during our 2.4-4 BSP update which were related to the pins and the detection of SOM-LV vs Torpedo.

    adam
    Stephen Newberry
    New Member
    New Member
    Posts:6


    --
    06 Dec 2017 10:06 AM
    Adam,

    I’m not sure which BSP version we’re using as we took the Timesys build from January 2016 and migrated it to a local mirror. We are using u-boot 2011.06 with the following patch files:
    • u-boot-2011.06-omap3logic-ts5.patch
    • u-boot-2011.06-nand-ecc-handling-fix.patch
    • u-boot-2011.06-platform-flags.patch
    • u-boot-2011-06-allow-omap3-hardfloat.patch

    Since upgrading to the latest BSP will be a lengthy process as we have to go through our entire regression test cycle, is it possible to send us the pertinent u-boot patch files that fix the minor bugs that we can quickly incorporate into our existing BSP?

    Thanks,
    Stephen
    Adam Ford
    Advanced Member
    Advanced Member
    Posts:794


    --
    06 Dec 2017 02:03 PM
    I will e-mail you directly. I tried to post it, but it doesn't come through correctly.

    adam
    Stephen Newberry
    New Member
    New Member
    Posts:6


    --
    07 Dec 2017 07:08 AM

    Adam,

    I've received the patch file and forwarded it on to the software team. Thank you for the quick replies.

    Thanks,

    Stephen
    You are not authorized to post a reply.

    Forums Texas Instruments SOMs and Development Kits OMAP35x, DM3730, AM3703 Torpedo SOM Development Kit