NAND Flash erased - How to Boot?

Monica Sanchez

Other Parts Discussed in Thread: AM3359

Hello,

I was given a SBC8600B board, featuring a AM335x processor. The problem is that the flash was somehow erased, and now It is not possible to boot neither linux, android or WINCE700.

Basically, on the serial terminal it is never displayed the u-boot prompt, but only a sequence of "CCCCCCCC" characters. I also tried to use "starterware" to send .bin files, and those are excecuted (by uart, not SD), but I wonder if there is a possibility to copy a linux image (boot.img) to try to recover the FLASH.

The SDcard is useless since it is not recognized, I cannot even use it with the files from starterware.

Thanks in advance.. I would really appreciate some help with this issue :D

over 11 years ago

0 Monica Sanchez over 11 years ago

Prodigy 170 points

A little update,

As a mistake, I ran the application nandReadWrite.bin with starterware, and now I don't even get the CCCC output...

Thank you!

0 Miroslav Kiradzhiyski XID over 11 years ago

TI__Mastermind 25235 points

Hi,

You can boot your board from UART and then reflash the NAND. The example below uses "picocom" as the Terminal emulator:

1. Build U-Boot and save the u-boot-spl.bin from the ./spl folder inside the <u-boot_dir>.

2. Set the EVM switches for UART boot (1-5: 10000)

3. Start picocom (board is OFF):
# picocom -b 115200 /dev/ttyS0 --send-cmd "sx -vv"

4. Press CTRL+A; CTRL+S; to send the u-boot-spl.bin file via UART and then start the board.

5. After transfer is complete press CTRL+A; CTRL+S; to send the u-boot.img file.

6. After transfer is complete you can enter U-Boot mode.

7. Use picocom to transfer the MLO, u-boot.img, uImage, filesystem files to RAM and then write them to NAND.

IMPORTANT: Depending on whether you're using kermit or ymodem mode use one of these two commands to load the image files to RAM:

loadb - load binary file over serial line (kermit mode)
loady - load binary file over serial line (ymodem mode)

Best regards,
Miroslav

0 Monica Sanchez over 11 years ago in reply to Miroslav Kiradzhiyski XID

Prodigy 170 points

Hi,

Thanks for your answer,

I tried it, but when I try to send the file I receive a "invalid window size" error... As I wrote before, I no longer receive the CCCC output stream. Does it have anything to do with it?

Thank you

*** file: /home/devid/u-boot-spl
sx -w /home/devid/u-boot-spl 
sx: invalid window size `/home/devid/u-boot-spl'

0 Miroslav Kiradzhiyski XID over 11 years ago in reply to Monica Sanchez

TI__Mastermind 25235 points

Your picocom command is not correct.

It should be:

picocom -b 115200 /dev/ttyS0 --send-cmd "sx -vv"

This is two times "v", not "w".

Best regards,
Miroslav

0 Monica Sanchez over 11 years ago in reply to Miroslav Kiradzhiyski XID

Prodigy 170 points

Hi, Thank you..

I fixed it, but now I get this:

Sending /home/devid/u-boot-spl, 1985 blocks: Give your local XMODEM receive command now.
Xmodem sectors/kbytes sent:   0/ 0kRetry 0: Timeout on sector ACK

Retry 0: Timeout on sector ACK
Retry 0: Timeout on sector ACK

0 Miroslav Kiradzhiyski XID over 11 years ago in reply to Monica Sanchez

TI__Mastermind 25235 points

Please share your SYSBOOT pins configuration.

Best regards,
Miroslav

0 Monica Sanchez over 11 years ago in reply to Miroslav Kiradzhiyski XID

Prodigy 170 points

Hi,

I am working with an EMBEST SBC8600B board, which features a AM3359 Processor.

On the Embest documentation, there is no information regarding SYSBOOT pins.

I found 5 jumpers on the board, and I know the configuration 00001 is used for SD boot.

0 Miroslav Kiradzhiyski XID over 11 years ago in reply to Monica Sanchez

TI__Mastermind 25235 points

You need to set the SYSBOOT pins for UART boot. Please check Table 26-7. SYSBOOT Configuration Pins from the AM335x Technical Reference Manual for the correct SYSBOOT pins configuration and then ask your board manufacturer how to do this if possible.

Best regards,
Miroslav

0 Biser Gatchev-XID over 11 years ago in reply to Miroslav Kiradzhiyski XID

TI__Guru**** 393215 points

The EMBEST SBC8600B board seems to be hardwired to boot only from SD card or NAND. You will need to prepare an SD card and boot from it.

0 Monica Sanchez over 11 years ago in reply to Biser Gatchev-XID

Prodigy 170 points

Hi,

I already tried to boot from SD card, but I don't get any response from the serial terminal, Not even the U-Boot prompt.

0 Biser Gatchev-XID over 11 years ago in reply to Monica Sanchez

TI__Guru**** 393215 points

I am afraid we cannot help any further on this forum. This is a third-party product. Please contact your board manufacturer/reseller for support.

0 Monica Sanchez over 11 years ago in reply to Biser Gatchev-XID

Prodigy 170 points

Thanks a lot for your support, I will ask the manufacturer,

Anyway, I would like to know if there is a possibility of recover the CCCCC chacacter string on the serial terminal

I used Starterware, particularly the application nandReadWrite.bin, and I didn't get the character string again... Now I am not even able to send the boot.bin file trough hyperterminal.

What could have happened?

How could I fix it?

Thank you

0 Biser Gatchev-XID over 11 years ago in reply to Monica Sanchez

TI__Guru**** 393215 points

The CCCC string is sent from the processor ROM code when attempting to boot from UART0. As said above you have a third-party product, we don't have any documentation on this board, therefore we cannot support it. Please turn to board manufacturer for support.

0 Monica Sanchez over 11 years ago in reply to Miroslav Kiradzhiyski XID

Prodigy 170 points

Hello,

After some time, I managed to setup my board and I could successfuly do all that was recommended here by Miroslav.

You can boot your board from UART and then reflash the NAND. The example below uses "picocom" as the Terminal emulator:

1. Build U-Boot and save the u-boot-spl.bin from the ./spl folder inside the <u-boot_dir>.

2. Set the EVM switches for UART boot (1-5: 10000)

3. Start picocom (board is OFF):
# picocom -b 115200 /dev/ttyS0 --send-cmd "sx -vv"

4. Press CTRL+A; CTRL+S; to send the u-boot-spl.bin file via UART and then start the board.

5. After transfer is complete press CTRL+A; CTRL+S; to send the u-boot.img file.

6. After transfer is complete you can enter U-Boot mode.

7. Use picocom to transfer the MLO, u-boot.img, uImage, filesystem files to RAM and then write them to NAND.

IMPORTANT: Depending on whether you're using kermit or ymodem mode use one of these two commands to load the image files to RAM:

loadb - load binary file over serial line (kermit mode)
loady - load binary file over serial line (ymodem mode)

I used kermit to transfer the MLO, u-boot.img, uImage, filesystem files to RAM, but I don't know how to write them on NAND. I thought it was done bu the loadb command, but no.. I rebooted the board after sending all those files and the transfers didn't have any effect.

So my question is: After I transfer a file using the loadb command, how can I write this content on the NAND?

Thanks in advance

Monica

0 Miroslav Kiradzhiyski XID over 11 years ago in reply to Monica Sanchez

TI__Mastermind 25235 points

Monica, here is an expanded version of step number 7:

U-Boot# nand erase.chip
U-Boot# loadb 0x81000000
<transfer MLO>
U-Boot# cp.b 0x81000000 0x81020000 20000
U-Boot# cp.b 0x81000000 0x81040000 20000
U-Boot# cp.b 0x81000000 0x81060000 20000
U-Boot# loadb 0x81080000
<transfer u-boot.img>
U-Boot# loadb 0x81280000
<transfer uImage>
U-Boot# loadb 0x81780000
<transfer ubi.img>
U-Boot# nand write 0x81000000 0x0 0x2000000

The commands marked in red are optional, depending on whether or not you want to have your filesystem flashed on the NAND.

Best regards,
Miroslav

0 Monica Sanchez over 11 years ago in reply to Miroslav Kiradzhiyski XID

Prodigy 170 points

Thank you Miroslav for your recommendation. I followed all the steps you provided, and I would like to post the output from the serial terminal, since It didn't work completely:

CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
U-Boot SPL 2011.09 (Feb 12 2014 - 16:23:09)
Texas Instruments Revision detection ¹¥µÁ±•µ•¹Ñ•‘5
Booting from UART...
CCCCxyzModem - CRC mode, 1837(SOH)/0(STX)/0(CAN) packets, 5 retries
Loaded 234896 bytes

U-Boot 2011.09-svn55 (Dec 04 2012 - 09:29:02)

Net: cpsw
Hit any key to stop autoboot: 0
SBC8600# nand erase.chip

NAND erase.chip: device 0 whole chip
Skipping bad block at 0x001c0000
Skipping bad block at 0x02720000
Skipping bad block at 0x04b00000
Skipping bad block at 0x05880000
Skipping bad block at 0x061c0000
Skipping bad block at 0x07040000
Skipping bad block at 0x07b00000
Skipping bad block at 0x0a700000
Skipping bad block at 0x0a720000
Skipping bad block at 0x0f040000
Skipping bad block at 0x0f060000
Skipping bad block at 0x10480000
Skipping bad block at 0x104a0000
Skipping bad block at 0x105c0000
Skipping bad block at 0x105e0000
Skipping bad block at 0x117c0000
Skipping bad block at 0x117e0000
Skipping bad block at 0x12d00000
Skipping bad block at 0x12d20000
Skipping bad block at 0x157c0000
Skipping bad block at 0x157e0000
Skipping bad block at 0x16840000
Skipping bad block at 0x16860000
Skipping bad block at 0x16880000
Skipping bad block at 0x168a0000
Skipping bad block at 0x181c0000
Skipping bad block at 0x181e0000
Skipping bad block at 0x18780000
Skipping bad block at 0x187a0000
Skipping bad block at 0x1abc0000
Skipping bad block at 0x1abe0000
Skipping bad block at 0x1cb00000
Skipping bad block at 0x1cb20000
Skipping bad block at 0x1d880000
Skipping bad block at 0x1d8a0000
Skipping bad block at 0x1e1c0000
Skipping bad block at 0x1e1e0000
Skipping bad block at 0x1fb00000
Skipping bad block at 0x1fb20000
Erasing at 0x1ffe0000 -- 100% complete.
OK

SBC8600# loadb 0x81000000
## Ready for binary (kermit) download to 0x81000000 at 115200 bps...
## Total Size = 0x00008cef = 36079 Bytes
## Start Addr = 0x81000000
SBC8600# cp.b 0x81000000 0x81020000 20000
SBC8600# cp.b 0x81000000 0x81040000 20000
SBC8600# cp.b 0x81000000 0x81060000 20000
SBC8600# loadb 0x81080000
## Ready for binary (kermit) download to 0x81080000 at 115200 bps...
## Total Size = 0x00039590 = 234896 Bytes
## Start Addr = 0x81080000
SBC8600# loadb 0x81280000
## Ready for binary (kermit) download to 0x81280000 at 115200 bps...
## Total Size = 0x00318548 = 3245384 Bytes
## Start Addr = 0x81280000
SBC8600# loadb 0x81780000
## Ready for binary (kermit) download to 0x81780000 at 115200 bps...
## Total Size = 0x00e20000 = 14811136 Bytes
## Start Addr = 0x81780000
SBC8600# nand write 0x81000000 0x0 0x2000000

NAND write: device 0 offset 0x0, size 0x2000000
Skip bad block 0x001c0000
33554432 bytes written: OK

U-Boot SPL 2011.09-svn55 (Dec 04 2012 - 09:29:02)
Texas Instruments Revision detection unimplemented
Booting from NAND...

Now, I rebooted, but then this is printed:

U-Boot 2011.09svn55 (Dec 04 2012 - 09:29:02)

I2C: ready
DRAM: 512 MiB
WARNING: Caches not enabled
Did not find a recognized configuration, assuming General purpose EVM in Profile
0 with Daughter board
NAND: HW ECC Hamming Code selected
512 MiB
MMC: OMAP SD/MMC: 0
Error: Bad compare! failed
Error: Bad compare! failed
Error: Bad compare! failed
Error: Bad compare! failed
Error: Bad compare! failed
Error: Bad compare! failed
Error: Bad compare! failed
Error: Bad compare! failed
Error: Bad compare! failed
Error: Bad compare! failed
NAND read from offset 260000 failed -74
*** Warning - readenv() failed, using default environment

Net: cpsw
Hit any key to stop autoboot: 0
Card did not respond to voltage select!
Booting from nand ...
HW ECC BCH8 Selected

NAND read: device 0 offset 0x280000, size 0x400000
4194304 bytes read: OK
Wrong Image Format for bootm command
ERROR: can't get kernel image!
SBC8600#

Did I do something wrong?. Why the image is not found?

Thank you!

0 Miroslav Kiradzhiyski XID over 11 years ago in reply to Monica Sanchez

TI__Mastermind 25235 points

Monica, please let me know which version of the TI SDK are you using? Also let me know about the commands you use to build the kernel image, or if you are using the pre-built kernel image from the SDK.

Best regards,
Miroslav

0 Monica Sanchez over 11 years ago in reply to Miroslav Kiradzhiyski XID

Prodigy 170 points

Miroslav, Thank you for your answer.

I used the files provided by my third party provider. I installed a cross compiler tool on my linix host as follows:

mkdir $HOME/tools
cd /media/cdrom/linux/tools
tar xvf arm-2009q1-203-arm-none-linux-gnueabi-i686-pc-linux-gnu.tar.bz2 -C $HOME/tools
tar xvf arm-eabi-4.4.0.tar.bz2 -C $HOME/tools

cp /media/cdrom/linux/tools/mkimage $HOME/tools
cp /media/cdrom/linux/tools/mkfs.ubifs $HOME/tools
cp /media/cdrom/linux/tools/ubinize $HOME/tools
cp /media/cdrom/linux/tools/ubinize.cfg $HOME/tools

Then it is adviced to add temporary environment variables

export PATH=$HOME/tools/arm-2009q1/bin:$HOME/tools/arm-eabi-4.4.0/bin:$HOME/tools:$PATH

For System Compilation:

mkdir $HOME/work
cd $HOME/work
tar xvf /media/cdrom/linux/source/u-boot-2011.09-psp04.06.00.03.tar.bz2
tar xvf /media/cdrom/linux/source/linux-3.2.0-psp04.06.00.08.sdk.tar.bz2
tar xvf /media/cdrom/linux/demo/android/source/linux-3.1.0-android.tar.bz2
sudo tar xvf /media/cdrom/linux/source/rootfs.tar.bz2
tar xvf /media/cdrom/linux/demo/android/source/rowboat-android-gingerbread-am335xevm.tar.bz2

Compilation of booting code - MLO and u-boot.img

cd u-boot-2011.09-psp04.06.00.03
make distclean
make sbc8600_config
make

Kernel Compilation - uImage

cd Linux-3.2.0-psp04.06.00.08.sdk
make distclean
make sbc8600_defconfig
make uImage

UBI File - ubi.img

cd $HOME/work
sudo $HOME/tools/mkfs.ubifs -r rootfs -m 2048 -e 126976 -c 812 -o ubifs.img
sudo $HOME/tools/ubinize -o ubi.img -m 2048 -p 128KiB -s 512 -O 2048 $HOME/tools/ubinize.cfg

That would be all what I did to build the kernel image, the boot files and the ubi file. I also tried the precompiled images I was provided.

Thank you

0 Monica Sanchez over 11 years ago in reply to Monica Sanchez

Prodigy 170 points

In addition, today I managed to load all the files and write them on the NAND, however, the results are not as expected. I provide the logs I obtained.

First log: 4606.180214_noUBI_loaded.txt

In this try I didn't wrote the ubi.img file

Second log: 1513.190214-ubi.txt

In this attepmt I wrote all the files

As you can see, none of those are successfull.

Thank you

0 Miroslav Kiradzhiyski XID over 11 years ago in reply to Monica Sanchez

TI__Mastermind 25235 points

The software you are using is based on a quite old version of the TI PSP (04.06.00.08). This version needs you to explicitly select the ecc scheme before writing the data to the NAND flash. Later versions of the PSP support only BCH8 ECC scheme.

Take a look at this page from the U-Boot User's Guide history to get a general idea of how to write to the NAND flash with this older version.

Best regards,
Miroslav

0 Monica Sanchez over 11 years ago in reply to Miroslav Kiradzhiyski XID

Prodigy 170 points

Thank you Miroslav, I will give it a try..

As you know, those transfers take a while, so probably you will hear from me tomorrow..

However, I would like to ask you, where can I find the exact addresses where I am supposed to write the image files on the nand: MLO, u-boot.img, uImage, ubi.img

Thank you!

0 Miroslav Kiradzhiyski XID over 11 years ago in reply to Monica Sanchez

TI__Mastermind 25235 points

The expected NAND layout is shown on the AM335x U-Boot User's Guide page I posted above.

Here it is:

+------------+-->0x00000000-> SPL start         (SPL copy on 1st block)
|            |
|            |-->0x0001FFFF-> SPL end 
|            |-->0x00020000-> SPL.backup1 start (SPL copy on 2nd block)
|            |
|            |-->0x0003FFFF-> SPL.backup1 end 
|            |-->0x00040000-> SPL.backup2 start (SPL copy on 3rd block)
|            |
|            |-->0x0005FFFF-> SPL.backup2 end 
|            |-->0x00060000-> SPL.backup3 start (SPL copy on 4th block)
|            |
|            |-->0x0007FFFF-> SPL.backup3 end
|            |-->0x00080000-> U-Boot start
|            |                                    
|            |-->0x002BFFFF-> U-Boot end 
|            |-->0x00260000-> ENV start
|            |
|            |
|            |-->0x0027FFFF-> ENV end
|            |-->0x00280000-> Linux Kernel start
|            |
|            |
|            |
|            |
|            |-->0x0077FFFF-> Linux Kernel end
|            |-->0x00780000-> File system start
|            |
|            |
|            |
|            |
|            |
|            |
|            |
|            |
|            |
|            |
|            |
|            |
+------------+-->0x10000000-> NAND end (Free end)

0 Monica Sanchez over 11 years ago in reply to Miroslav Kiradzhiyski XID

Prodigy 170 points

Thank you! I found it later :D

I will let you know how it goes!

0 Maria Monica Sanchez Ramirez over 11 years ago in reply to Monica Sanchez

Prodigy 10 points

Hello Miroslav,

I tried what you suggested with the ecc configuration. Particularly, I used "nandecc hw 2" and then I loaded one by one the image files.

It seems to be some problem with the ubi image, although I tried both the precompiled image and one I compiled myself. I attach the log file from putty(

1346.putty.log), and maybe you can give me some light with this issue.

0 Miroslav Kiradzhiyski XID over 11 years ago in reply to Maria Monica Sanchez Ramirez

TI__Mastermind 25235 points

Can you try changing your U-Boot Env variables, so that you may boot from NAND, but load the filesystem from the SD card?

Changing the "nandargs" variable should do it:

root=${mmcroot} rootfstype=${mmcrootfstype}

I understand you had some issues with your SD card, but can you try if it can be detected/accessed from U-Boot with the "mmc" set of commands? Also, have you tried using another SD card? Maybe this one is faulty.

Best regards,
Miroslav

0 Monica Sanchez over 11 years ago in reply to Miroslav Kiradzhiyski XID

Prodigy 170 points

Hi,

In deed I have some issues with the SD card, since it is not recognized. I have already tried three different, of 2, 4 and 8 GB, using FAT and FAT32 formats (format applied with windows tool and HP Format Tool 2.0.6, recommended by the board manufacturer).

I applied the changes on the nandargs, but it is also unsuccessful. In the log

Fullscreen 1464.log_change_on_nandargs.txt Download

=~=~=~=~=~=~=~=~=~=~=~= PuTTY log 2014.02.20 07:43:45 =~=~=~=~=~=~=~=~=~=~=~=

U-Boot SPL 2011.09 (Feb 12 2014 - 16:23:09)
Texas Instruments Revision detection unimplemented
Booting from NAND...


U-Boot 2011.09 (Feb 12 2014 - 16:23:09)

I2C:   ready
DRAM:  512 MiB
WARNING: Caches not enabled
Did not find a recognized configuration, assuming General purpose EVM in Profile 0 with Daughter board
NAND:  HW ECC Hamming Code selected
512 MiB
MMC:   OMAP SD/MMC: 0
Error: Bad compare! failed
Error: Bad compare! failed
Error: Bad compare! failed
Error: Bad compare! failed
Error: Bad compare! failed
Error: Bad compare! failed
Error: Bad compare! failed
Error: Bad compare! failed
NAND read from offset 260000 failed -74
*** Warning - readenv() failed, using default environment

Net:   cpsw
Hit any key to stop autoboot:  3  0 
SBC8600# 

SBC8600# 

SBC8600# 

SBC8600# printenv        setenv nand_args 'run bootargs_defaults;setenv bootargs ${bootargs} dispmode=${dispmode} consoleblank=${consoleblank} root=${mmcroot} noinitrd rootfstype=${mmcrootfstype} ip=${ip_method}'

SBC8600# 

SBC8600# 

SBC8600# 

SBC8600# printenv

android_args=run bootargs_defaults;setenv bootargs ${bootargs} dispmode=${dispmode} root=${android_root}  rootfstype=${nand_root_fs_type} earlyprintk init=/init androidboot.console=ttyO0
android_boot=echo Booting from android ...; run android_args; nandecc hw 2; nand read.i ${kloadaddr} ${nand_src_addr} ${nand_img_siz}; bootm ${kloadaddr}
android_root=ubi0:rootfs  ubi.mtd=7,2048
autoload=yes
baudrate=115200
bootargs_defaults=setenv bootargs console=${console} ${optargs}
bootcmd=if mmc rescan; then echo SD/MMC found on device ${mmc_dev};if run loadbootenv; then echo Loaded environment from ${bootenv};run importbootenv;fi;if test -n ${uenvcmd}; then echo Running uenvcmd ...;run uenvcmd;fi;if run mmc_load_image; then run mmc_args;bootm ${kloadaddr};fi;fi;run nand_boot
bootdelay=3
bootenv=uEnv.txt
bootfile=uImage
console=ttyO0,115200n8
consoleblank=0
dispmode=4.3inch_LCD
dvsdk_args=run bootargs_defaults;setenv bootargs ${bootargs} dispmode=${dispmode} root=${dvsdk_root}  rootfstype=${dvsdk_root_fs_type} earlyprintk
dvsdk_boot=echo Booting from dvsdk ...; run dvsdk_args; mmc rescan; run dvsdk_load_image;bootm ${kloadaddr}
dvsdk_load_image=fatload mmc ${mmc_dev} ${kloadaddr} ${bootfile};
dvsdk_root=/dev/mmcblk0p2 rw 
dvsdk_root_fs_type=ext3 rootwait
ethact=cpsw
ethaddr=c8:a0:30:c4:bf:ed
importbootenv=echo Importing environment from mmc ...; env import -t ${loadaddr} ${filesize}
ip_method=none
kloadaddr=0x80007fc0
loadaddr=0x82000000
loadbootenv=fatload mmc ${mmc_dev} ${loadaddr} ${bootenv}
mmc_args=run bootargs_defaults;setenv bootargs ${bootargs} dispmode=${dispmode} consoleblank=${consoleblank} root=${mmc_root} initrd=${rdloadaddr},32MB rootfstype=${mmc_root_fs_type} ip=${ip_method}
mmc_boot=run mmc_args; mmc rescan; run mmc_load_image; bootm ${kloadaddr}
mmc_dev=0
mmc_load_image=fatload mmc ${mmc_dev} ${kloadaddr} ${bootfile};fatload mmc ${mmc_dev} ${rdloadaddr} ${ramdisk}
mmc_root=/dev/ram rw 
mmc_root_fs_type=ext2
nand_args=run bootargs_defaults;setenv bootargs ${bootargs} dispmode=${dispmode} consoleblank=${consoleblank} root=${mmcroot} noinitrd rootfstype=${mmcrootfstype} ip=${ip_method}
nand_boot=echo Booting from nand ...; run nand_args; nandecc hw 2; nand read.i ${kloadaddr} ${nand_src_addr} ${nand_img_siz}; bootm ${kloadaddr}
nand_img_siz=0x400000
nand_root=ubi0:rootfs rw ubi.mtd=7,2048
nand_root_fs_type=ubifs rootwait
nand_src_addr=0x280000
net_args=run bootargs_defaults;setenv bootargs ${bootargs} dispmode=${dispmode} root=/dev/nfs nfsroot=${serverip}:${rootpath},${nfsopts} rw ip=dhcp
net_boot=echo Booting from network ...; setenv autoload no; dhcp; tftp ${kloadaddr} ${bootfile}; run net_args; bootm ${kloadaddr}
nfsopts=nolock
nor_args=run bootargs_defaults;setenv bootargs ${bootargs} dispmode=${dispmode} root={nor_root} rootfstype=${nor_root_fs_type} ip=${ip_method}
nor_boot=echo Booting from NOR ...; run nor_args; cp.b ${0x08080000} ${kloadaddr} ${nor_img_siz}; bootm ${kloadaddr}
nor_img_siz=0x280000
nor_root=/dev/mtdblock3 rw
nor_root_fs_type=jffs2
nor_src_addr=0x08080000
ramdisk=ramdisk.gz
rdloadaddr=0x81600000
rootpath=/export/rootfs
script_addr=0x81900000
spi_args=run bootargs_defaults;setenv bootargs ${bootargs} dispmode=${dispmode} root=${spi_root} rootfstype=${spi_root_fs_type} ip=${ip_method}
spi_boot=echo Booting from spi ...; run spi_args; sf probe ${spi_bus_no}:0; sf read ${kloadaddr} ${spi_src_addr} ${spi_img_siz}; bootm ${kloadaddr}
spi_bus_no=0
spi_img_siz=0x280000
spi_root=/dev/mtdblock4 rw
spi_root_fs_type=jffs2
spi_src_addr=0x62000
static_ip=${ipaddr}:${serverip}:${gatewayip}:${netmask}:${hostname}::off
stderr=serial
stdin=serial
stdout=serial
updatesys=nand erase.chip;mmc rescan; fatload mmc 0 82000000 MLO;nandecc hw 2;nand write.i 82000000 0 ${filesize}; fatload mmc 0 82000000 u-boot.img;nandecc hw 2;nand write.i 82000000 80000 ${filesize};fatload mmc 0 82000000 uImage;nandecc hw 2;nand write.i 82000000 280000 ${filesize}; fatload mmc 0 82000000 ubi.img;nandecc sw;nand write.i 82000000 780000 ${filesize};led flash all

Environment size: 4145/8188 bytes
SBC8600# boot

SD/MMC found on device 0
mmc_send_cmd: timedout waiting for cmddis!
** Can't read from device 0 **

** Unable to use mmc 0:1 for fatload **
mmc_send_cmd: timedout waiting for cmddis!
** Can't read from device 0 **

** Unable to use mmc 0:1 for fatload **
mmc_send_cmd: timedout waiting for cmddis!
** Can't read from device 0 **

** Unable to use mmc 0:1 for fatload **
Booting from nand ...
HW ECC BCH8 Selected

NAND read: device 0 offset 0x280000, size 0x400000
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
ECC: uncorrectable.
NAND read from offset 280000 failed -74
 0 bytes read: ERROR
## Booting kernel from Legacy Image at 80007fc0 ...
   Image Name:   Linux-3.2.0
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    3243016 Bytes = 3.1 MiB
   Load Address: 80008000
   Entry Point:  80008000
   Verifying Checksum ... OK
   XIP Kernel Image ... OK
OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
Linux version 3.2.0 (devid@UbuntuSitaraID) (gcc version 4.3.3 (Sourcery G++ Lite 2009q1-203) ) #1 Wed Feb 12 16:33:39 COT 2014
CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7), cr=10c53c7d
CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
Machine: am335xevm
Memory policy: ECC disabled, Data cache writeback
AM335X ES1.0 (sgx neon )
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 130048
Kernel command line: console=ttyO0,115200n8 dispmode=4.3inch_LCD consoleblank=0 root= noinitrd rootfstype= ip=none
----lcd_type_init 4.3inch_LCD
PID hash table entries: 2048 (order: 1, 8192 bytes)
Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
Memory: 512MB = 512MB total
Memory: 512960k/512960k available, 11328k reserved, 0K highmem
Virtual kernel memory layout:
    vector  : 0xffff0000 - 0xffff1000   (   4 kB)
    fixmap  : 0xfff00000 - 0xfffe0000   ( 896 kB)
    vmalloc : 0xe0800000 - 0xff000000   ( 488 MB)
    lowmem  : 0xc0000000 - 0xe0000000   ( 512 MB)
    modules : 0xbf000000 - 0xc0000000   (  16 MB)
      .text : 0xc0008000 - 0xc05cb000   (5900 kB)
      .init : 0xc05cb000 - 0xc060c000   ( 260 kB)
      .data : 0xc060c000 - 0xc0674670   ( 418 kB)
       .bss : 0xc0674694 - 0xc06a17e4   ( 181 kB)
NR_IRQS:396
IRQ: Found an INTC at 0xfa200000 (revision 5.0) with 128 interrupts
Total of 128 interrupts on 1 active controller
OMAP clockevent source: GPTIMER2 at 25000000 Hz
omap_dm_timer_switch_src: Switching to HW default clocksource(sys_clkin_ck) for timer1, this may impact timekeeping in low power state
OMAP clocksource: GPTIMER1 at 25000000 Hz
sched_clock: 32 bits at 25MHz, resolution 40ns, wraps every 171798ms
Console: colour dummy device 80x30
Calibrating delay loop... 718.02 BogoMIPS (lpj=3590144)
pid_max: default: 32768 minimum: 301
Security Framework initialized
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
omap_hwmod: pruss: failed to hardreset
print_constraints: dummy: 
NET: Registered protocol family 16
OMAP GPIO hardware version 0.1
omap_mux_init: Add partition: #1: core, flags: 0
----am335x_evm_i2c_init----
 omap_i2c.1: alias fck already exists
The board is SBC8600.
 omap_hsmmc.0: alias fck already exists
 da8xx_lcdc.0: alias fck already exists
 davinci-mcasp.0: alias fck already exists
--------uart1_init
--------uart2_init
--------uart3_init
--------uart4_init
--------uart5_init
 d_can.0: alias fck already exists
--------buzzer_init
registered am33xx_sr device
 omap2_mcspi.1: alias fck already exists
 omap2_mcspi.2: alias fck already exists
 edma.0: alias fck already exists
 edma.0: alias fck already exists
 edma.0: alias fck already exists
bio: create slab <bio-0> at 0
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
registerd cppi-dma Intr @ IRQ 17
Cppi41 Init Done Qmgr-base(e087a000) dma-base(e0878000)
Cppi41 Init Done
musb-ti81xx musb-ti81xx: musb0, board_mode=0x13, plat_mode=0x3
musb-ti81xx musb-ti81xx: musb1, board_mode=0x13, plat_mode=0x1
omap_i2c omap_i2c.1: bus 1 rev2.4.0 at 100 kHz
tps65910 1-002d: could not be detected
Advanced Linux Sound Architecture Driver Version 1.0.24.
Switching to clocksource gp timer
musb-hdrc: version 6.0, ?dma?, otg (peripheral+host)
musb-hdrc musb-hdrc.0: dma type: dma-cppi41
MUSB0 controller's USBSS revision = 4ea20800
musb-hdrc musb-hdrc.0: USB OTG mode controller at e083c000 using DMA, IRQ 18
musb-hdrc musb-hdrc.1: dma type: dma-cppi41
MUSB1 controller's USBSS revision = 4ea20800
musb-hdrc musb-hdrc.1: MUSB HDRC host driver
musb-hdrc musb-hdrc.1: new USB bus registered, assigned bus number 1
usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb1: Product: MUSB HDRC host driver
usb usb1: Manufacturer: Linux 3.2.0 musb-hcd
usb usb1: SerialNumber: musb-hdrc.1
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
musb-hdrc musb-hdrc.1: USB Host mode controller at e083e800 using DMA, IRQ 19
NET: Registered protocol family 2
IP route cache hash table entries: 4096 (order: 2, 16384 bytes)
TCP established hash table entries: 16384 (order: 5, 131072 bytes)
TCP bind hash table entries: 16384 (order: 4, 65536 bytes)
TCP: Hash tables configured (established 16384 bind 16384)
TCP reno registered
UDP hash table entries: 256 (order: 0, 4096 bytes)
UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
NET: Registered protocol family 1
RPC: Registered named UNIX socket transport module.
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
NetWinder Floating Point Emulator V0.97 (double precision)
omap-gpmc omap-gpmc: GPMC revision 6.0
Registering NAND on CS0
VFS: Disk quotas dquot_6.5.2
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
msgmni has been set to 1001
alg: No test for stdrng (krng)
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
da8xx_lcdc da8xx_lcdc.0: GLCD: Found 4.3inch_LCD panel
Console: switching to colour frame buffer device 60x34
omap_uart.0: ttyO0 at MMIO 0x44e09000 (irq = 72) is a OMAP UART0
console [ttyO0] enabled
omap_uart.1: ttyO1 at MMIO 0x48022000 (irq = 73) is a OMAP UART1
omap_uart.2: ttyO2 at MMIO 0x48024000 (irq = 74) is a OMAP UART2
omap_uart.3: ttyO3 at MMIO 0x481a6000 (irq = 44) is a OMAP UART3
omap_uart.4: ttyO4 at MMIO 0x481a8000 (irq = 45) is a OMAP UART4
omap_uart.5: ttyO5 at MMIO 0x481aa000 (irq = 46) is a OMAP UART5
brd: module loaded
loop: module loaded
i2c-core: driver [tsl2550] using legacy suspend method
i2c-core: driver [tsl2550] using legacy resume method
mtdoops: mtd device (mtddev=name/number) must be supplied
omap2-nand driver initializing
ONFI flash detected
ONFI param page 0 valid
NAND device: Manufacturer ID: 0xad, Chip ID: 0xdc (Hynix H27U4G8F2DTR-BC)
Creating 8 MTD partitions on "omap2-nand.0":
0x000000000000-0x000000020000 : "SPL"
0x000000020000-0x000000040000 : "SPL.backup1"
0x000000040000-0x000000060000 : "SPL.backup2"
0x000000060000-0x000000080000 : "SPL.backup3"
0x000000080000-0x000000260000 : "U-Boot"
0x000000260000-0x000000280000 : "U-Boot Env"
0x000000280000-0x000000780000 : "Kernel"
0x000000780000-0x000020000000 : "File System"
OneNAND driver initializing
CAN device driver interface
CAN bus driver for Bosch D_CAN controller 1.0
d_can d_can.0: device registered (irq=52, irq_obj=53)
usb 1-1: new high-speed USB device number 2 using musb-hdrc
davinci_mdio davinci_mdio.0: davinci mdio revision 1.6
davinci_mdio davinci_mdio.0: detected phy mask ffffffaf
davinci_mdio.0: probed
davinci_mdio davinci_mdio.0: phy[4]: device 0:04, driver unknown
davinci_mdio davinci_mdio.0: phy[6]: device 0:06, driver unknown
PPP generic driver version 2.4.2
PPP BSD Compression module registered
PPP Deflate Compression module registered
PPP MPPE Compression module registered
NET: Registered protocol family 24
usbcore: registered new interface driver zd1201
usbcore: registered new interface driver cdc_ether
usbcore: registered new interface driver cdc_eem
usbcore: registered new interface driver dm9601
cdc_ncm: 04-Aug-2011
usbcore: registered new interface driver cdc_ncm
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
 gadget: using random self ethernet address
 gadget: using random host ethernet address
usb0: MAC 5a:19:36:03:f7:24
usb0: HOST MAC 22:39:14:e0:dd:e9
 gadget: Ethernet Gadget, version: Memorial Day 2008
 gadget: g_ether ready
musb-hdrc musb-hdrc.0: MUSB HDRC host driver
musb-hdrc musb-hdrc.0: new USB bus registered, assigned bus number 2
usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb2: Product: MUSB HDRC host driver
usb usb2: Manufacturer: Linux 3.2.0 musb-hcd
usb usb2: SerialNumber: musb-hdrc.0
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 1 port detected
mousedev: PS/2 mouse device common for all mice
input: ti-tsc-adcc as /devices/platform/omap/tsc/input/input0
omap_rtc omap_rtc: rtc core: registered omap_rtc as rtc0
i2c /dev entries driver
Linux video capture interface: v2.00
usb 1-1: New USB device found, idVendor=0424, idProduct=2512
usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
usbcore: registered new interface driver uvcvideo
USB Video Class driver (1.1.1)
hub 1-1:1.0: USB hub found
hub 1-1:1.0: 2 ports detected
OMAP Watchdog Timer Rev 0x01: initial timeout 60 sec
_regulator_get: deviceless supply vdd_mpu not found, using dummy regulator
cpuidle: using governor ladder
cpuidle: using governor menu
omap4_aes_mod_init: loading AM33X AES driver
omap4-aes omap4-aes: AM33X AES hw accel rev: 3.02
omap4_aes_probe: probe() done
omap4_sham_mod_init: loading AM33X SHA/MD5 driver
omap4-sham omap4-sham: AM33X SHA/MD5 hw accel rev: 4.03
omap4_sham_probe: probe() done
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
usbcore: registered new interface driver snd-usb-audio
sgtl5000 1-000a: Device with ID register ffff is not a sgtl5000
sgtl5000 1-000a: asoc: failed to probe CODEC sgtl5000.1-000a: -19
asoc: failed to instantiate card AM335X EVM: -19
ALSA device list:
  No soundcards found.
oprofile: hardware counters not available
oprofile: using timer interrupt.
nf_conntrack version 0.5.0 (8015 buckets, 32060 max)
ip_tables: (C) 2000-2006 Netfilter Core Team
TCP cubic registered
NET: Registered protocol family 17
can: controller area network core (rev 20090105 abi 8)
NET: Registered protocol family 29
can: raw protocol (rev 20090105)
can: broadcast manager protocol (rev 20090105 t)
Registering the dns_resolver key type
VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 3
ThumbEE CPU extension supported.
mux: Failed to setup hwmod io irq -22
Power Management for AM33XX family
Trying to load am335x-pm-firmware.bin (60 secs timeout)
Copied the M3 firmware to UMEM
Compensating OPP0 for 0mV Orig nvalue:0x999280 New nvalue:0x999280 
Compensating OPP1 for 0mV Orig nvalue:0x999280 New nvalue:0x999280 
_regulator_get: deviceless supply vdd_core not found, using dummy regulator
smartreflex smartreflex: am33xx_sr_probe: cannot determine opp
smartreflex: probe of smartreflex failed with error -22
sr_init: platform driver register failed
clock: disabling unused clocks to save power
Detected MACID=c8:a0:30:c4:bf:ed
cpsw: Detected MACID = c8:a0:30:c4:bf:ef
input: gpio-keys as /devices/platform/gpio-keys/input/input1
omap_rtc omap_rtc: setting system clock to 2000-01-01 00:00:01 UTC (946684801)
Root-NFS: no NFS server address
VFS: Unable to mount root fs via NFS, trying floppy.
List of all partitions:
1f00             128 mtdblock0  (driver?)
1f01             128 mtdblock1  (driver?)
1f02             128 mtdblock2  (driver?)
1f03             128 mtdblock3  (driver?)
1f04            1920 mtdblock4  (driver?)
1f05             128 mtdblock5  (driver?)
1f06            5120 mtdblock6  (driver?)
1f07          516608 mtdblock7  (driver?)
No filesystem could mount root, tried: 
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(2,0)
Backtrace: 
[<c0018b90>] (dump_backtrace+0x0/0x110) from [<c0451310>] (dump_stack+0x18/0x1c)
 r7:c05fd4e4 r6:df1a0000 r5:c0612374 r4:c0675608
[<c04512f8>] (dump_stack+0x0/0x1c) from [<c0451388>] (panic+0x74/0x1a4)
[<c0451314>] (panic+0x0/0x1a4) from [<c05cbed4>] (mount_block_root+0x208/0x240)
 r3:00000029 r2:df02df40 r1:df02df40 r0:c0529c50
[<c05cbccc>] (mount_block_root+0x0/0x240) from [<c05cbfb4>] (mount_root+0xa8/0xdc)
[<c05cbf0c>] (mount_root+0x0/0xdc) from [<c05cc130>] (prepare_namespace+0x148/0x1dc)
 r5:c060b7b8 r4:c0674720
[<c05cbfe8>] (prepare_namespace+0x0/0x1dc) from [<c05cb324>] (kernel_init+0x120/0x13c)
 r6:c060b1b8 r5:c060b7b8 r4:c060b7b8
[<c05cb204>] (kernel_init+0x0/0x13c) from [<c0042624>] (do_exit+0x0/0x6cc)
 r7:00000013 r6:c0042624 r5:c05cb204 r4:00000000

is seen that the mmc is not readed and it continues with the nand boot, with the same error.

0 Miroslav Kiradzhiyski XID over 11 years ago in reply to Monica Sanchez

TI__Mastermind 25235 points

Monica, I'm out of ideas. I'm ruling out the possibility for incorrectly built UBI image, since the board manufacturer has provided pre-built images for their board.

There seem to be some hardware issues with your board, perhaps even something wrong with the NAND flash. Please turn to the board manufacturer for support.

Best regards,
Miroslav

0 Ebrahim Talaq over 11 years ago in reply to Monica Sanchez

Prodigy 50 points

Dear Monica,

Can you provide me with the steps you did for getting back the boot on the SBC8600?

The board I have is displaying the "C" character nonstop.

Thanks.

0 Monica Sanchez over 11 years ago in reply to Ebrahim Talaq

Prodigy 170 points

Hi,

The steps followed were provided by Miroslav on his first reply on this same thread. Find them in the previous page. I din't use picocom, but Hyperterminal for file transfer, but it is the same.

It didn't work for me, because there might be a problem with the physical device, but I was always able to copy the boot files to the Nand.

0 Ebrahim Talaq over 11 years ago in reply to Miroslav Kiradzhiyski XID

Prodigy 50 points

I tried the commands with "loadb" but the unit couldn't make the transfer so I switched to "loady" with some changes and it worked now.

It shows the "ECC: uncorrectable" message but that's fine ... from here I can redo the system loading using the SDK with "run updatesys" after having the correct files.

Thanks for the help.

Processors

Processors forum

NAND Flash erased - How to Boot?