Need Help!! Booting from NAND!! TAM 3517

hrishikesh choudhary

Other Parts Discussed in Thread: ADS7846, AM3517

1222.android.TXT

Dear All!

Please suggest!

I have entered the commands for bootargs and bootcmd on u-boot prompt and used the command saveenv. This command were entered when i was booting angstorm from sd card , before this by changing switch setting i was able to boot android through NAND but now when i am trying to boot NAND it asks for MMC which it is not supposed to.

the command i entered when booting from sd card setenv bootargs 'mem=256M console=ttyS0,115200n8 root=/devmmcblk0p2 rw rootfstype=ext3 rootdelat=1'

2nd command is setenv bootcmd ' mmc init; fatload mmc 80008000 uImage;bootm 80008000'

Now can i retreive the original setting ? how can restore ?

previously it was directly booting from nand.

Printenv output

Texas Instruments X-Loader 1.47 (Jan 28 2011 - 14:26:12)
Booting from nand . . .
Starting OS Bootloader...

U-Boot 2010.06-rc1 (Jan 28 2011 - 14:26:17)

OMAP34xx/35xx-GP ES1.0, CPU-OPP2 L3-165MHz
TAM3517 TWISTER Board + LPDDR/NAND
I2C:   ready
DRAM: 256 MiB
NAND: 256 MiB
In:    serial
Out:   serial
Err:   serial
Customer/Vender : TechNexion
Project/Board   : tam3517
Sequence Number : 1052000000000069
revision        : TN15 1.0
eth0 addr      : 00:1F:7B:15:01:10
eth1 addr      : 00:1F:7B:15:01:11
eth2 addr      : 0
eth3 addr      : 00:1F:7B:15:01:13
Die ID #30e20000000000000155dc140400f016
Net:   Ethernet PHY: GENERIC @ 0x00
DaVinci EMAC, smc911x-0
Hit any key to stop autoboot: 0
No MMC card found
TAM3517 # printenv
bootdelay=1
baudrate=115200
ipaddr=192.168.1.5
serverip=192.168.1.4
console=ttyS0,115200n8
memsize=256M
nfseth=eth1
mpurate=600
touch_calibration=
nandparts=omap2-nand.0:512k(xloader),1024k(uboot),512k(params),6m(kernel),-(root
fs)
disp_mode_0=set def_disp lcd;set disp_mode panel-generic.disp_timings=8000,480/8
/4/41,272/4/2/10,24;set touch_calibration ads7846.calibration=8235,28,-981716,17
,4906,-1103000,65536
disp_mode_1=set def_disp lcd;set disp_mode panel-generic.disp_timings=33300,800/
210/46/1,480/22/23/1,24;set touch_calibration ads7846.calibration=-13943,25,5444
4704,-124,-9117,34403056,65536 ads7846.swap_left_right=1 ads7846.swap_top_down=1
ads7846.x_min=180 ads7846.y_min=330 ads7846.x_max=3900 ads7846.y_max=3800
disp_mode_2=set def_disp lcd;set disp_mode panel-generic.disp_timings=54200,1024
/320/320/1,600/
disp_mode_3=set def_disp dvi;set disp_mode omapfb.mode=dvi:1280x720@60
disp_mode_4=set def_disp tv;set disp_mode omapfb.mode=tv:ntsc
disp_mode_5=set def_disp tv;set disp_mode omapfb.mode=tv:pal
disp_mode_6=run disp_mode_0
disp_mode_7=run disp_mode_0
sys_mode_0=
sys_mode_1=set rootfs ubi0:android;set rootfsmmc 3;set nfsroot /nfsroot/android
vers=3;set android_args androidboot.console=ttyS0
sys_mode_2=run sys_mode_0
sys_mode_3=run sys_mode_0
sys_mode_4=run sys_mode_0
sys_mode_5=run sys_mode_0
sys_mode_6=run sys_mod
sys_mode_7=run sys_mode_0
boot_to_0=run nandboot
boot_to_1=run mmcboot
boot_to_2=run nfsboot
boot_to_3=run boot_to_0
vram_size=10M
android_args=
rootfs=ubi0:rootfs
rootfsmtd=4
rootfsmmc=2
nfsroot=/nfsroot/angstrom vers=3
defaultargs=run nandargs
nfsargs=run def_sys_mode;run def_disp_mode;setenv bootargs mem=${memsize} mpurat
e=${mpurate} console=${console} omapfb.vram=0:${vram_size} eth0addr=${eth0addr}
eth1addr=${eth1addr} eth2addr=${eth2addr} eth3addr=${eth3addr} ${android_args} $
{sys_mode} ${board_info} ${auto_run} omapdss.def_disp=${def_disp} ${disp_mode} $
{touch_calibration} mtdparts=${nandparts} root=/dev/nfs rw ip=${ipaddr}:::::${nf
seth}: nfsroot=${serverip}:${nfsroot}
mmcargs=run def_sys_mode;run def_disp_mode;setenv bootargs mem=${memsize} mpurat
e=${mpurate} console=${console} omapfb.vram=0:${vram_size} eth0addr=${eth0addr}
eth1addr=${eth1addr} eth2addr=${eth2addr} eth3addr=${eth3addr} ${android_args} $
{sys_mode} ${board_info} ${auto_run} omapdss.def_disp=${def_disp} ${disp_
{touch_calibration} mtdparts=${nandparts} root=/dev/mmcblk0p${rootfsmmc} rw root
fstype=ext3 rootwait
nandargs=run def_sys_mode;run def_disp_mode;setenv bootargs mem=${memsize} mpura
te=${mpurate} console=${console} omapfb.vram=0:${vram_size} eth0addr=${eth0addr}
eth1addr=${eth1addr} eth2addr=${eth2addr} eth3addr=${eth3addr} ${android_args}
${sys_mode} ${board_info} ${auto_run} omapdss.def_disp=${def_disp} ${disp_mode}
${touch_calibration} mtdparts=${nandparts} ubi.mtd=${rootfsmtd} root=${rootfs} r
w rootfstype=ubifs rootflags=bulk_read,chk_data_crc rw
load_b=tftp 80100000 boot/u-boot-32-256-nand-16.bin
load_xb=tftp 80100000 boot/mlo-32-256-nand-16
kernel_addr=200000
kernel_load=81000000
kernel_size=600000
uboot_nand_addr=80000
update_xb=run load_xb;nandecc hw;nand erase 0 20000;nand write 80100000 0 20000
update_b=run load_b;nandecc sw;nand erase ${uboot_nand_addr} 40000;nand write 80
100000 ${uboot_nand_addr} 100000
update_k=run load_k;nandecc sw;nand erase ${kernel_addr} ${kernel_size};nand wri
te.jffs2 ${kernel_load} ${kernel_addr} ${kernel_size}
load_nand_k=nandecc sw;nand read.jffs2 ${kernel_load} ${kernel_addr} ${kernel_si
ze}
nfsboot=run nfsargs;run load_k;bootm ${kernel_load}
mmcboot=mmc init;run loaduimage; run mmcargs; bootm ${kernel_load}
nandboot=run nandargs;run load_nand_k;bootm ${kernel_load}
dieid#=30e20000000000000155dc140400f016
ethact=DaVinci EMAC
bootargs=mem=256M console=ttyS0,15200n8 root=/dev/mmcblk0p2 rwrootfstype=ext3 ro
otdelay=1
bootcmd=mmc init
stdin=serial
stdout=serial
stderr=serial
eth0addr=00:1F:7B:15:01:10
eth1addr=00:1F:7B:15:01:11
eth2addr=00:1F:7B:15:01:12
eth3addr=00:1F:7B:15:01:13
ethaddr=00:1f:7b:15:01:10
board_info=CUSTOMER=TechNexion PRODUCT=tam3517 ID=1052000000000069 BOARD_TN=15 B
OARD_REVISION_MAJOR=1 BOARD_REVISION_FIXED=0
def_disp_mode=run disp_mode_1
def_sys_mode=run sys_mode_1
load_k=tftp ${kernel_load} boot/1/uImage
loaduimage=fatload mmc 0 ${kernel_load} boot/1/uImage
bootfile=boot/1/uImage
sys_mode=SYSTEM=1
def_boot_to=run boot_to_0

Environment size: 4370/131068 bytes
TAM3517 # boot
No MMC card found
TAM3517 #

over 14 years ago

0 Michael T over 14 years ago

TI__Expert 6735 points

Hrishikesh:

bootargs=mem=256M console=ttyS0,15200n8 root=/dev/mmcblk0p2 rwrootfstype=ext3 ro

Change this to have "115200n8" and space between "rw" and "rootfstype" like this:

bootargs=mem=256M console=ttyS0,115200n8 root=/dev/mmcblk0p2 rw rootfstype=ext3 ro

What are your SYSBOOT pins set to?

In our AM3517 SDK (for Linux), we do not use any mem=256M boot parameter.

Regards,

Michael T

PS: Please mark this post as answered via the Verify Answer button below if you think it answers your question. Thanks!

0 hrishikesh choudhary over 14 years ago in reply to Michael T

Expert 1390 points

1.Board Configuration

sw3_Pin7	sw3_Pin6	sw3_Pin5	Boot Mode	O S	AutoUpdate
Off	Off	Off	Sd card	Android	sw3_Pin8 = ON

Here it is Android as i am trying to restore the NAND through SD-CARD.

2.We have also tried booting with the below configuration:

sw3_Pin7	sw3_Pin6	sw3_Pin5	Boot Mode	O S	AutoUpdate
Off	Off	On	NAND	Android	sw3_Pin8 = ON

Can you enter few arguments with correct syntax to for

Bootargs and Boot CMD for Booting from NAND and SD card , similarly for selecting filesystem from sd card.

however if i enter the command setenv on U-boot prompt , until i use saveenv they are not saved to NAND . but do they work for that instance or i need to save them ?

0 Michael T over 14 years ago in reply to hrishikesh choudhary

TI__Expert 6735 points

Hrishikesh:

In the AM3517 SDK 4.1 there is a script you can run that creates a minicom script to set your boot parameters.

./<SDK-install-dir>/bin/setup-uboot-env.sh

You can create minicom scripts using that for different configurations.

Attached is an example for kernel and rootfs on SD card.

You can run that from Ubuntu console window:

minicom -S setup_uimage-sd_fs-sd.minicom

Or you can use this as a reference and enter commands at u-boot prompt.

When starting minicom, turn on wrap mode: minicom -w

Boot device where MLO and u-boot.bin are read depends on boot switches (SD Card, NAND,...).

Regards,

Michael T

PS: Please mark this post as answered via the Verify Answer button below if you think it answers your question. Thanks!

0 Michael T over 14 years ago in reply to Michael T

TI__Expert 6735 points

Hrishikesh:

Attached is another example. This reads kernel from NAND and uses SD Card for rootfs.

Regards,

Michael T

PS: Please mark this post as answered via the Verify Answer button below if you think it answers your question. Thanks!

Processors

Processors forum

Need Help!! Booting from NAND!! TAM 3517