> -Original Message-
> From: u-boot-boun...@lists.denx.de
> [mailto:u-boot-boun...@lists.denx.de] On Behalf Of Murali K. Vemuri
> Sent: Friday, November 19, 2010 1:49 PM
> To: u-boot@lists.denx.de
> Subject: [U-Boot] omap3 booting issues
>
> Hi there,
>
> This may not be the ideal place to post this question, but I thought
> someone might know this.
[sp] This is definitely not the right place. The question belongs to
linux-omap mailing list.
>
> 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 .
[sp] You have shared no information on versions of x-loader, u-boot and
kernel. How is your custom board different from any known platform
omap3evm, beagle, sdp, ...
In absence, you should look at your customizations and ensure all
board specific hook-ups or changes are properly handled in software.
> 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
[sp] Provide more details and move your kernel related queries to linux-omap.
> Thanks & regards
> Murali
> ___
> U-Boot mailing list
> U-Boot@lists.denx.de
> http://lists.denx.de/mailman/listinfo/u-boot
>
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot
