Netra: DM816x not booting after Nand flash

Hi,

are you sure about having DDR3 or DDR2 support?

Within the AM389x_PSP_Flashing_Tools_Guide it's mentioned that there is a difference, so probably you already checked this point.

But I had at my first tries seemingly the same problem, SD-Card generation worked well, but I got nothing from the U-Boot prompt.

For me that problem occured when changing from EZSDK version 5.00 to 5.01, as from then the EZSDK was prepared for the DDR3 boards. I had to change some DDR-concerning settings within two header files from DD3 to DDR2 for my somewhat older board and had to rebuild the U-Boot. Afterwards it booted as wanted.

Regards,
Joern.

Hi Joern,

Thanks for you suggestion, We have Revision B and Revision boards for ddr2 and ddr3 respectively.

When we use ddr2/3 , only the change is to use the corresponding Gel file.

So this is not the issue. My only concern is that why i am not getting uBoot prompt even after Nand write success..

If we trying from SD card is there any special settings, or addtional files required.. ? I farmated the SD card in windows, and put MLO, uBoot.bin and uImage but on booting nothing is coming on the terminal.

Please tel me where can I get more info on bringing up the uBoot.

As I am working only with EZSDK and am not using the GUI-IDE CCS I am not sure if you have the same tools available than me at EZSDK.

I followed the instructions from Software Developer Guide (until now I found that only below the EZSDK root directory and not online), but the instructions here seem to be almost the same.

Where I had to call something like "sudo ${EZSDK}/bin/mksdboot.sh --device /dev/sdb --sdk ${EZSDK}" to get automatically generated the SD card content (be carefully concerning the actual device name of the SD card!) for you maybe the mksd-ti816x.sh mentioned in the document linked above will be the right starting point - at least to analyze what they really do concerning formatting and partitioning the SD card... (I did not analyze the details, but I had luck and all worked from the beginning, aside from the point concerning DDR2/3).

Regards,
Joern.

HI Joern,

Thanx for your suggestion , now i am getting uboot prompt atleast .

I am facing problem in loading uImage, am getting kernel panic because of wrong  nfs.. where can i get the nfs.tar.gz that supports DM816x(Netra).

It seems as if you already got it to look for an root directory via nfs. For those who yet are looking for this step: within the first partition of the SD card change boot.cmd and, from that and by mkimage, boot.scr concerning our current network and boot settings.

If your nfs settings are right and the server is existing, then of course as well you need the content of the root directory.

For me that worked as well through the SD card generation script mentioned above - as for me this script generated a SD card booting into a root directory within the SD card itself. There it was situated at the second partition, at /dev/sdb2 (wheras the U-Boot stuff was on /dev/sdb1). For the first tries simply I copied that partitions content (by cp -a) into the nfs root directory meant for my EVM board. The only stumbling block remaining was that our NFS server was not fast enough and so I had to add rootdelay=4 to the kernel boot parameters.

Hope that helps,
regards,
Joern.

P.S. within my EZSDK installation directory I just found a directory named "filesystem" with these two files in it: arago-base-tisdk-image-dm816x-evm.tar.gz  and ezsdk-dm816x-evm-rootfs.tar.gz, but don't ask me if one of these (and which) was the right one; I simply worked as described above and afterwards had no need to change my root directory...