Because of the Thanksgiving holiday in the U.S., TI E2E™ design support forum responses may be delayed from November 25 through December 2. Thank you for your patience.

  • State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 103 subscribers
  • Views 1685 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

OMAP3530 Rev E update looking for (AT400/AT401) Errata Notice

Matt Callahan
Prodigy 20 points
Other Parts Discussed in Thread: OMAP3530

In SPRZ278F The following is listed, can someone please direct to the (AT400/AT401) Errata Notice?

Thank you

2.1.1 Cortex-A8 Errata List

The OMAP3530/25/15/03 Applications Processor Silicon Revisions 3.1.2, 3.1, 3.0, 2.1, and 2.0 Silicon

Errata does not cover the advisories associated with the Cortex-A8 processor. For a list of the advisories

associated with each version of the Cortex-A8 processor, contact your TI representative for a copy of the

ARM Core Cortex-A8 (AT400/AT401) Errata Notice. See Table 2 to determine which version of the

Cortex-A8 processor is included in each OMAP35x silicon revision.

  • 0
    Prodigy 20 points

    More info:

    Upon switching to the Rev E of this part the system (beagle board based design) won't load firmware from the SD card and the system fails while starting to load Uboot

    Thanks!

  • 0
    TI__Guru 65405 points

    Hi Matt,

    You should contact with your local FAE engineer to get ARM Core Cortex-A8 (AT400/AT401) errata because seems that there are some restrictions to it.

    BR

    Tsvetolin Shulev

  • 0 in reply to Matt Callahan
    Prodigy 40 points

    Hi Matt,

    I was just looking for some answers about TI OMAP3530 revision effect on the devkit8000 board.

    Embest has changed there revision D processor with a revision E (OMAP3530ECUS vs OMAP3530DCUS).

    Since that change, my firmware hangs at the same level as yours.

    I'm trying to flash an 0xdroid version on the NAND but it doesn't work anymore with new board. 

    Did you fix that issue or do you have any suggestion about this case.

    Thank you