• State TI Thinks Resolved
  • Locked Locked
  • Replies 5 replies
  • Answers 2 answers
  • Subscribers 97 subscribers
  • Views 522 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.

AM3352: AM3352BZCZA100

VINEETH S
Prodigy 40 points

Part Number: AM3352

Hi,

We have a custom board with an AM3352 mounted on it, and a DDR3 chip. 

we had fabricated 2 cards,in which one of the card is having an issue with booting , boot process stops when the kernel takes over.

I am booting from the SD card.

The other card is working properly.

Here is our boot log:

U-Boot SPL 2014.07 (Sep 19 2020 - 11:36:54)

Board identification from EEPROM contents: after
        Magic numbr  : 0xEE3355AA
        Board name   : A335BNLT
        Board version: 000C
        Board serial : 2314BBBK0212
Board identification from EEPROM contents: after
        Magic numbr  : 0xEE3355AA
        Board name   : A335BNLT
        Board version: 000C
        Board serial : 2314BBBK0212
 **** U-boot >>> inside file = board/ti/am335x/mux.c, line num = 400, func = enable_board_pin_mux ****
Board identification from EEPROM contents: after
        Magic numbr  : 0xEE3355AA
        Board name   : A335BNLT
        Board version: 000C
        Board serial : 2314BBBK0212
Board identification from EEPROM contents: after
        Magic numbr  : 0xEE3355AA
        Board name   : A335BNLT
        Board version: 000C
        Board serial : 2314BBBK0212
reading u-boot.img
reading u-boot.img
U-Boot 2014.07 (Sep 19 2020 - 11:36:54)
I2C:   ready
DRAM:  512 MiB
MMC:   OMAP SD/MMC: 0, OMAP SD/MMC: 1
Board identification from EEPROM contents: after
        Magic numbr  : 0xEE3355AA
        Board name   : A335BNLT
        Board version: 000C
        Board serial : 2314BBBK0212
Net:   Board identification from EEPROM contents: after
        Magic numbr  : 0xEE3355AA
        Board name   : A335BNLT
        Board version: 000C
        Board serial : 2314BBBK0212
 **** U-boot >>> inside file = board/ti/am335x/board.c, line num = 711, func = board_eth_init, PHY_MODE = MII ****
cpsw, usb_ether
Hit any key to stop autoboot:  0
switch to partitions #0, OK
mmc0 is current device
SD/MMC found on device 0
reading uEnv.txt
3992024 bytes read in 257 ms (14.8 MiB/s)
31506 bytes read in 36 ms (854.5 KiB/s)
Kernel image @ 0x82000000 [ 0x000000 - 0x3ce9d8 ]
## Flattened Device Tree blob at 88000000
   Booting using the fdt blob at 0x88000000
   Loading Device Tree to 8fff5000, end 8ffffb11 ... OK
Starting kernel ...

What would be the issue with hardware or any memory related issue?                                                                                     

Help would be appreciated.

  • 0
    TI__Mastermind 41450 points

    Hi,

    I am not sure how to help with issue. If the card that boots is reliable then I would say that there is an issue with the card that does not boot. Does the failing card ever boot? 

    To emphasize a successful boot would indicate the memory is working correctly. If you are concerned about the memory using the card that boots successfully run memtester to test the DDR. For example if the board has 512MB run memtester like this on a subset of memory, here the parameter passed is telling memtester to test 128MB of memory.

    memtester 128

    Best Regards,

    Schuyler

  • 0 in reply to Schuyler Patton
    Prodigy 40 points

    Hi,

    The  failing card does not Boot completely, its getting stuck in the starting kernel from the beginning.

    The DDR Memory is getting detected randomly as 512MB,256MB,32MB in serial message.

    Best Regards,

    Vineeth

  • 0 in reply to VINEETH S
    TI__Mastermind 41450 points

    Hi,

    Are your trying both of the SD cards in one board one after the other? If one SD card boots the board and the other SD does not boot the board I would suggest re-making the failed SD card.

    Best Regards,

    Schuyler

  • 0 in reply to Schuyler Patton
    Prodigy 40 points

    Hi,

    Both SD cards are booting on working card. So we are not expecting issue with SD card.

    But we noticed that DDR value in serial message randomly changing at beginning of booting like 52MB,256MB,512MB.

    Boot log:
    reading u-boot.img
    reading u-boot.img
    U-Boot 2014.07 (Sep 19 2020 - 11:36:54)
    I2C:   ready
    DRAM:  512 MiB
    MMC:   OMAP SD/MMC: 0, OMAP SD/MMC: 1
  • 0 in reply to VINEETH S
    TI__Mastermind 41450 points

    Hi,

    I apologize, I missed what you have been trying to tell me.

    I can point to where the memory size is calculated so you can look at further debug options. The DRAM size is calculated in get_ram_size() which is defined in this file of the sdk: board-support / u-boot-<year- commit id>/common/memsize.c

    I would also recommend using the memtester app as I mentioned above to test the memory on a booted board too.

    When the DRAM size is being mis-reported does the board still boot? In the above log output showing a boot failure is that the correct size?

    Is this the first time this board is being booted? Were there any issues following the EMIF configuration procedure application note?

    Best Regards,

    Schuyler