omap3 booting issues

Murali Vemuri

Hi There,

I have custom board using OMAP3 and I have a problem. We have more than one I2C slave connected on I2C1 & u-boot was not displaying the slave addresses correctly.

I fixed some issues in u-boot and am finally able to see the u-boot displaying the I2C devices correctly.

But after this Kernel stopped to boot. It just gives the message:

Starting kernel ...

Uncompressing Linux........................................................................................................................................................... done, booting the kernel.

and stops.

I tried to find out the possible reason, but no use so far (about 2 days). Currently my MLO (x-loader), u-boot.bin, & the kernel uImage reside on the SD Card .

BTW, I found a curious comment in the kernel code: /* First I2C bus is not muxable */

Can this be a problem for the board not booting?

As I had been playing with I2C only, I had to dig mainly on the I2C direction. any other pointers will be helpful

Thanks & regards

Murali

over 14 years ago

0 Michael T over 14 years ago

TI__Expert 6735 points

Murali:

This wiki article includes common causes of the loss ofterminal output after the "booting the kernel" msg.

http://processors.wiki.ti.com/index.php/Kernel_-_Common_Problems_Booting_Linux#Problem_.232_-_No_more_output_is_seen_on_the_console_after_.22booting_the_kernel.22

If that does not help, please halt boot process and enter printenv from U-BOOT prompt and

post the output.

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 Murali Vemuri over 14 years ago in reply to Michael T

Prodigy 80 points

Dear Michael,

Thank you for your response.

I checked the wiki page and not quite helpful.

This is my print env output:

# printenv

bootcmd=if mmc init; then if run loadbootscript; then run bootscript; else if run loaduimage; then run mmcboot; else run nandboot; fi; fi; else run nandboot; fi

bootdelay=10

baudrate=115200

bootfile=uImage

loadaddr=0x82000000

usbtty=cdc_acm

console=ttyS2,115200n8

mmcargs=setenv bootargs console=${console} root=/dev/mmcblk0p2 rw rootfstype=ext3 rootwait

nandargs=setenv bootargs console=${console} root=/dev/mtdblock4 rw rootfstype=jffs2

loadbootscript=fatload mmc 0 ${loadaddr} boot.scr

bootscript=echo Running bootscript from mmc ...; source ${loadaddr}

loaduimage=fatload mmc 0 ${loadaddr} uImage

mmcboot=echo Booting from mmc ...; run mmcargs; bootm ${loadaddr}

nandboot=echo Booting from nand ...; run nandargs; onenand read ${loadaddr} 280000 400000; bootm ${loadaddr}

dieid#=51fe000400000000040365fa0a01701f

filesize=1000000

bootargs=mem=128M console=ttyS0,115200n8 root=/dev/ram0 initrd=0x81600000,40M ramdisk_size=40960

stdin=serial

stdout=serial

stderr=serial

Environment size: 971/131068 bytes

Hope this info is useful.

Thanks & regards

Murali

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

TI__Expert 6735 points

Murali:

Change ttyS2 to ttyS0. Other than that it looks OK. But that may fix your problem.

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

omap3 booting issues