• State TI Thinks Resolved
  • Locked Locked
  • Replies 5 replies
  • Answers 1 answer
  • Subscribers 99 subscribers
  • Views 434 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.

Original question:

AM3356: AM3356x-Micron 8Gb:x8 Flash Integration Issue

AM3356: U-boot & Kernel changes to integrate 512MB (4Gb)-256Mx16 ISSI SDRAM with am335x platform

Sreesyam K
Prodigy 160 points
Part Number: AM3356

Hello,

1. We are having a device which uses TI's Sitara-am335x processor (Part No: AM3356BZCZD60).

2.  We are Currently trying to upgrade to new 512MB (4Gb)-256Mx16 ISSI SDRAM (part no:IS43TR16256B-125KBLI). Previously We were using 256MB (2Gb)-128Mx16 ISSI SDRAM (part no:512MBIS43TR16128B-125KBLI)

2. We transferred the uboot-spl.bin file over X-Modem protocol, but when we tried to transfer the uboot-img.bin over Y-Modem, the operation gets failed. I assume this is because the required support for 512MB RAMSIZE is not present in the uboot-spl.bin image.

3. Kindly advise what are the changes required in U-boot & kernel source to integrate the new RAM support for am335x.

4. Below is the Uboot version taken from a working device (with 256MB/2Gb RAM). We are using the same  u-boot-spL and u-boot.img images in the new proto as well.

U-Boot 2018.01-00444-g96cdbef-dirty (Dec 01 2021 - 23:25:16 +0530)

  • 0
    TI__Guru**** 167581 points

    Hi,

    Our U-Boot expert is currently out of office. Please expect delayed response.

  • 0 in reply to Bin Liu
    Prodigy 160 points

    Okey Bin Liu,

    It would be really helpful if you could provide a response soon. I am stuck up with my board bring up, since I could not even get spl & uboot, up and running.

  • 0 in reply to Sreesyam K
    TI__Guru 68290 points

    Hi,
    When DDR is changed, it is necessary to update DDR configuration in SPL.
    Please see the section "Port DDR configuration if your DDR setup (devices, clock speeds, etc.) differs from the originating platform (EVM)"
    in software-dl.ti.com/.../U-Boot.html
    Best,
    -Hong

  • 0 in reply to Hong Guan64
    Prodigy 160 points

    Dear Hong,

    We could transfer the uboot-spl.bin & u-boot.img images after defining the below configuration registers in sdram_init() code.

            config_ddr(400, &ioregs_bonelt,
                       &ddr3_beagleblack_data,
                       &ddr3_beagleblack_cmd_ctrl_data,
                   &ddr3_beagleblack_emif_reg_data, 0);

    We could login to uboot successfully over Console, with below message

    U-Boot 2018.01-00444-g96cdbef-dirty (Apr 05 2022 - 11:37:47 +0530)

    CPU  : AM335X-GP rev 2.1
    Model: TI AM335x EVM
    DRAM:  512 MiB
    NAND:  1024 MiB
    MMC:   OMAP SD/MMC: 0
    ** Bad device mmc 0 **
    Using default environment

    After this, we could could successfully nand write MLO & u-boot.img files from u-boot using below commands.

    Filename 'MLO'.
    Load address: 0x82000000
    Loading: ########
             650.4 KiB/s
    done
    Bytes transferred = 110688 (1b060 hex)

    NAND erase: device 0 offset 0x0, size 0x7ffff
    Erasing at 0x40000 -- 100% complete.
    OK

    NAND write: device 0 offset 0x0, size 0x1b060
     110688 bytes written: OK

    NAND write: device 0 offset 0x40000, size 0x1b060
     110688 bytes written: OK

    NAND write: device 0 offset 0x80000, size 0x1b060
     110688 bytes written: OK

    NAND write: device 0 offset 0xc0000, size 0x1b060
     110688 bytes written: OK

    Filename 'u-boot.img'.
    Load address: 0x82000000
    Loading: ############################################
             2.3 MiB/s
    done
    Bytes transferred = 637556 (9ba74 hex)

    NAND erase: device 0 offset 0x100000, size 0x100000
    Erasing at 0x1c0000 -- 100% complete.
    OK

    NAND write: device 0 offset 0x100000, size 0x9ba74
     637556 bytes written: OK

    After this we rebooted the device. SPL is getting loaded, but SPL is not able to load u-boot with below error.

    U-Boot SPL 2018.01-00444-g96cdbef-dirty (Apr 05 2022 - 11:37:47)
    Trying to boot from NAND
    ** Bad device mmc 0 **
    Using default environment

    Please advise, what could be the reason for this failure.

  • 0 in reply to Sreesyam K
    TI__Guru 68290 points

    Hello,
    It is good to know the new DDR works on your board now.
    Can we close this e2e, and re-submit a new e2e ticket to follow-up the new NAND boot issue?
    Best,
    -Hong