One thing you could try is to use grep to see if the build version of u-boot has your new character

I changed mmc1 to xxlmmc1 and to confirm it was located in u-boot, I did

grep xxlmmc1 rpm/BUILD/u-boot-2011.06/
Binary file u-boot matches
Binary file u-boot.bin matches
Binary file u-boot.bin.ift matches

That would confirm your u-boot has binaries have your new character.

If it shows up in there, then I would suggest to do a chip erase just to make sure it can't exist anymore.

OMAP Logic # nand erase.chip

NAND erase.chip: device 0 whole chip
Erasing at 0x1ffe0000 -- 100% complete.
OK
OMAP Logic # reset

Try those ideas and let me know what you find.

adam

oh geez now I erased all of nand and can't boot into anything. what can I do now?

ok I connected via serial port and reinstalled. I am still investigating the issue with installing a new u-boot. it seems makeyaffsboot won't update u-boot unless I do a nand erase.chip first

I verified the u-boot.bin and u-boot.bin.ift on the SD card are the new ones. I did a nand erase.chip and nand erase.part u-boot. then rand make yaffsboot and I can see that it is writing my new u-boot.bin.ift because it tells me the size in bytes and I Just changed it so it is a new size. On reboot, I get the same u-boot without my changes

I followed the manual procedures in the BSP UG and that updated it, so something in the script is running differently. I noticed the script uses u-boot.bin.ift and the manual method uses u-boot.bin.

Daniel,

 bash$ ./ltib -p u-boot -m scbuild && ./ltib -p u-boot -m scdeploy

 After I perform the scbuild and scdeploy above I generally pull the u-boot.bin and u-boot.bin.ift files from the directory below.

 ~/logic/Logic_BSPs/Linux_3.0/1026167_LogicPD_Linux_BSP_2.4-3/rootfs/boot

 Please verify that these files match the files on your SD Card.  They should have the similar date and time near the time you last performed your build as seen in my example below.

-rw-r--r-- 1 root root   455608 Nov  8 21:09 u-boot.bin

-rw-r--r-- 1 root root   455620 Nov  8 21:09 u-boot.bin.ift

Next you can check your build time when you boot from SD and then the build time of u-boot when you boot from NAND.  If both of those agree, check that your object files for your source is getting rebuilt in the /rpm/BUILD/u-boot-2011.06 sub-directories.

In the attached log file I took the Linux 2.4-3 demo image files and only changed u-boot.bin and uboot.bin.ift.  I followed these steps below.

1. Updated the u-boot.bin and u-boot.ift on my SD-Card

2. Booted the system from SD.

3. Erase NAND

    OMAP Logic # nand erase.chip

4. Programmed NAND

    OMAP Logic # run makeyaffsboot

5. Removed the SD Card

6. Cycled power.how_to_install_new_u-boot.log.txt

In the log file below you can see that my u-boot took when I booted from the SD Card (ln 10)  and when I booted from NAND (ln 129).

 ln 10: U-Boot 2011.06 BSP-dm37x-2.4-3 (Nov 08 2014 - 21:09:00)

ln 129: U-Boot 2011.06 BSP-dm37x-2.4-3 (Nov 08 2014 - 21:09:00)

how_to_install_new_u-boot.log.txt

 

I think it has something to do with my u-boot environment. I can get it to work every time by running these commands.

nand erase.part u-boot
env default -f
run makeyaffsboot