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.

Linux / TMS320DM355: TMS320DM355 outputs a "bad CRC error" and stops.

Part Number: TMS320DM355

Tool/software: Linux

When we turned on the product after turning it off, it didn't start.

 I have checked the serial output of the product. It stopped with a bad CRC error.

 

There may be hardware failure (NAND failure) or software failure (setting error and U-Boot bug).

・In this version, do bugs cause any symptoms?

・Can you determine the countermeasure from the log?e?

 

 

※NANDは以下製品から変更しています。MT29F2G08AADWP-D→MT29F2G08ABAEAWP:E

変更前製品では、この症状の報告はありませんでした。

※ NAND has been changed from the following products.

 MT29F2G08AADWP-D → MT29F2G08ABAEAWP: E

There were no reports of this symptom before changing the NAND.

 

 

“LOG”

UBL: Entering UBL NANDBoot routine

UBL:  NANDInit() Successful

UBL:  Nand Detected:  Manufacturers ID:  0x0000002C

UBL:                  Device ID:         0x000000DA

UBL:                  page size:         0x00000800 bytes per page

UBL:                  block size:         0x00000040 pages per block

UBL:                  address cycles:    00000005 cycles

UBL: detected valid U-Boot magic number

UBL: booting to U-Boot

 

 

U-Boot 1.2.0 (Mar 30 2010 - 15:39:27)

 

DRAM:  128 MB

NAND:  NAND device: Manufacturer ID: 0x2c, Chip ID: 0xda (Micron NAND 256MiB 3,3V 8-bit)

Bad block table found at page 131008, version 0x01

Bad block table found at page 130944, version 0x01

No NAND device found!!!

256 MiB

*** Warning - bad CRC or NAND, using default environment

 

In:    serial

Out:   serial

Err:   serial

ARM Clock :- 216MHz

DDR Clock :- 171MHz

Hit any key to stop autoboot:  0

 

Loading from NAND 256MiB 3,3V 8-bit, offset 0x400000

   Image Name:   Linux-2.6.18-100311_pro500-davin

   Image Type:   ARM Linux Kernel Image (uncompressed)

   Data Size:    1972408 Bytes =  1.9 MB

   Load Address: 80008000

   Entry Point:  80008000

## Booting image at 80700000 ...

   Image Name:   Linux-2.6.18-100311_pro500-davin

   Image Type:   ARM Linux Kernel Image (uncompressed)

   Data Size:    1972408 Bytes =  1.9 MB

   Load Address: 80008000

   Entry Point:  80008000

   Verifying Checksum ... Bad Data CRC

 

Loading from NAND 256MiB 3,3V 8-bit, offset 0x800000

   Image Name:   Linux-2.6.18-100311_pro500-davin

   Image Type:   ARM Linux Kernel Image (uncompressed)

   Data Size:    1972408 Bytes =  1.9 MB

   Load Address: 80008000

   Entry Point:  80008000

## Booting image at 80700000 ...

   Image Name:   Linux-2.6.18-100311_pro500-davin

   Image Type:   ARM Linux Kernel Image (uncompressed)

   Data Size:    1972408 Bytes =  1.9 MB

   Load Address: 80008000

   Entry Point:  80008000

   Verifying Checksum ... Bad Data CRC

DM355 EVM #

Thank you,best regards.

  • Hi user357205584,

    From what I understand, you are using DM355 custom board. When you are using your DM355 custom board with MT29F2G08AADWP-D NAND part, your custom board boot fine. When you are using MT29F2G08ABAEAWP: E NAND part, your board fails to boot with "Bad Data CRC" message. Is that correct?

    Regards,
    Pavel
  • Hi Pavel.
    Your understanding is correct.
    Once a BOOT error occurs, it can not be restored just by turning the power ON / OFF.
    Also, boot errors do not occur with so many products. (One out of ten has failed.)

    Regards
  • Hi user357205584,

    From what I understand, you have ten DM355 custom boards with MT29F2G08ABAEAWP: E NAND chips, nine working fine and just one fail with "Bad Data CRC", is that correct?

    Regards,
    Pavel
  • That understanding is correct.
    Although it started successfully several times, suddenly this product got a BOOT error.
  • I think it is similar to this problem, how is it?
    e2e.ti.com/.../73788
  • user357205584,

    Let me summarize what we have so far.

    - you have ten DM355 custom boards with MT29F2G08ABAEAWP: E NAND chips, nine working fine and just one fail with "Bad Data CRC"
    - on this one fail board, when you replace MT29F2G08ABAEAWP: E NAND chip with MT29F2G08AADWP-D NAND chip, the board boot fine

    It seems to me that you have issue with this one MT29F2G08ABAEAWP: E NAND chip, you might check with the vendor (Micron) support team.

    What I can suggest you from TI side is to try with the latest TI SDK:

    software-dl.ti.com/.../index_FDS.html

    Regards,
    Pavel

  • Hi,Pavel
    Excuse me, please correct.

    - you have ten DM355 custom boards with MT29F2G08ABAEAWP: E NAND chips, nine working fine and just one fail with "Bad Data CRC"
    →That's right.
    - on this one fail board, when you replace MT29F2G08ABAEAWP: E NAND chip with MT29F2G08AADWP-D NAND chip, the board boot fine
    →I have not replaced it yet.

    Please tell us for reference. What kind of survey should I ask Micron?

    Regards,
  • user357205584 said:
    on this one fail board, when you replace MT29F2G08ABAEAWP: E NAND chip with MT29F2G08AADWP-D NAND chip, the board boot fine
    →I have not replaced it yet.

    If you can try this, you can isolate if the issue is in this specific DM355 custom board or in this specific NAND part.

    If DM335 board issue, it seems to me like HW malfunction. You should refer to below pointers:

     - DM335 DM, sections 3.11.5 AEMIF Configuration and 5.7.1 Asynchronous EMIF (AEMIF)

    - DM335 AMIF TRM - SPRUED1B

    - DM355 Silicon errata, section 2.1.1 ROM Bootloader (RBL) Functionality, check which silicon revision is your DM335 device, 2.1.9 GIO0 Low Setting During Device Boot May Cause Boot to Fail, 4.1.1 NAND Layout Assumed by RBL for Big Block NAND Does Not Match NAND Manufacturers' Recommendations, Advisory 1.1.1 RBL Code ECC Limitation, Advisory 1.4.13 — Change in ROM Boot Loader (RBL) NAND Boot Device ID Table

     - DM355 EVM

    Regards,
    Pavel