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.

how to save uboot env while using SD card boot in DM8148?

I am using SD card boot,  and I am using nfsroot

1.how to save uboot env while using SD card boot?

2. My SD card seems broken, report following error.

  error transfering data, card status 0x80900.

 a. why this happened.

 b. I often power off and on, because DSP often locked, so I have to do code start.

    Is that the cause why SD card broken?

c. Can I fixed it by reformat and rewrite data on it? how?

  • 1. To save env, type in 'savenv' from command prompt after uboot.

    2. a, b, -don't know and not sure

        c. yes

  • when I saveenv from commmand prompt,

    with the following response, and system dead.  I think maybe should write to SD card instead of nand. how to fix that?

    saving enviroment to NAND...

    Erasing NAND...

  • My experience is not with the 8148. Take my comments withs a grain of salt. I don't believe it is possible to write back runtime environment variable changes to the SD Card file. I think it assumed that that you will change the file on the SD Card outside of U-Boot. This file is on the first partition of the SD Card. I vaguely remember U-boot has two format. One is a plain text file, something like boot.txt. The other is a binary file boot.scr. A utility is required to create the boot.scr. I don't know which one is used on your board. Your SDK documentation should detail much of this. Online version is at the TI Wiki.

    http://processors.wiki.ti.com/index.php/DM814x_AM387x_PSP_U-Boot
    http://processors.wiki.ti.com/index.php/DM814x_AM387x_PSP_User_Guide

    The links above show some instructions on how to build a SD-Card image using a shell script on a Linux host. The links imply that your board supports NAND. Maybe try using that instead.

    I've found SD-Cards are a bit sensitive to power cycling during writes. It can result in the corruption of files. The Linux way to handle that is to use a jounalling file system that will recover on boot.

  • Ethan,

    it seems that your NAND flash (where u-boot is trying to save the parameters) is not working.

    What evaluation board are you using?

    Have you checked if there are jumpers to set in order to enable the NAND flash and to unprotect it?

    Have you checjed if you have a NAND flash chip?

    Matteo