[U-Boot] AM3517_EVM, MLO not booting

[U-Boot] AM3517_EVM, MLO not booting

[James Chandler]

Hello,

I am new to *nix/open-source mailing lists, so please provide any feedback about my post that would make future posts cleaner or easier to respond to.

I am trying to build the u-boot-arm tree/fork from denx.de (new to git so the correct terminology escapes me) for a AM3517_EV LogicPD evaluation board.  I cloned the git repository, built the MLO and u-boot.img files and then placed them on the first partition of my SD card (fat32, active, correct #of cylinders and heads).  When I switch the power on I get two characters on my serial console ( the first is a checker-board block from extended ascii of 170ish and the other is a 't') and then no output follows.

I am switching to the u-boot-arm tree/fork from the u-boot-am33x tree/fork at the Arago project, because the u-boot-am33x code from there doesn't have functional fatwrite and ext4write commands (I can build with them in place, but fatwrite causes mmc errors and timeout errors while ext4write does not give an error but does not create a file).  If I use the MLO from u-boot-am33x but the u-boot.img from u-boot-arm, I can boot into the u-boot environment and into Linux.  The fatwrite and the ext4write commands on u-boot-arm also work unlike those in u-boot-am33x.

I also have a custom board based on the AM3517_EVM (same CPU and RAM just no flash).  I copied the AM35117_EVM configuration and board/* files and made only changes related to removing flash support (since the custom board does not have it) and the custom board does boot using both MLO and u-boot.img from u-boot-arm.

Has anyone else had issues with MLO on the AM3517_EVM?  If so, are there any workable solutions?

Thanks,
James

[U-Boot] AM3517_EVM, MLO not booting

[James Chandler]

Hello,

I was able to snag a BDI3000 and debug the issue.  It turns out that the NS16550 driver contains a while loop that waits for register or some other value to be set during the SPL's serial_init() function.  This condition was not being met, causing serial_init() to hang.  The solution was to add #define CONFIG_SYS_NS16550_BROKEN_TEMT to the AM3517_EVM configuration.  I tried to push this back into the git repository but get unexpected hang-up errors (new to git as well).

Thanks,
James
________________________________
From: James Chandler
Sent: Monday, April 01, 2013 11:29 AM
To: u-boot at lists.denx.de
Subject: AM3517_EVM, MLO not booting

Hello,

I am new to *nix/open-source mailing lists, so please provide any feedback about my post that would make future posts cleaner or easier to respond to.

I am trying to build the u-boot-arm tree/fork from denx.de (new to git so the correct terminology escapes me) for a AM3517_EV LogicPD evaluation board.  I cloned the git repository, built the MLO and u-boot.img files and then placed them on the first partition of my SD card (fat32, active, correct #of cylinders and heads).  When I switch the power on I get two characters on my serial console ( the first is a checker-board block from extended ascii of 170ish and the other is a 't') and then no output follows.

I am switching to the u-boot-arm tree/fork from the u-boot-am33x tree/fork at the Arago project, because the u-boot-am33x code from there doesn't have functional fatwrite and ext4write commands (I can build with them in place, but fatwrite causes mmc errors and timeout errors while ext4write does not give an error but does not create a file).  If I use the MLO from u-boot-am33x but the u-boot.img from u-boot-arm, I can boot into the u-boot environment and into Linux.  The fatwrite and the ext4write commands on u-boot-arm also work unlike those in u-boot-am33x.

I also have a custom board based on the AM3517_EVM (same CPU and RAM just no flash).  I copied the AM35117_EVM configuration and board/* files and made only changes related to removing flash support (since the custom board does not have it) and the custom board does boot using both MLO and u-boot.img from u-boot-arm.

Has anyone else had issues with MLO on the AM3517_EVM?  If so, are there any workable solutions?

Thanks,
James

[U-Boot] AM3517_EVM, MLO not booting

[Andreas Bießmann]

Dear James Chandler,

On 02.04.13 00:24, James Chandler wrote:
> Hello,
> 
> I was able to snag a BDI3000 and debug the issue.  It turns out that the NS16550 driver contains a while loop that waits for register or some other value to be set during the SPL's serial_init() function.  This condition was not being met, causing serial_init() to hang.  The solution was to add #define CONFIG_SYS_NS16550_BROKEN_TEMT to the AM3517_EVM configuration.  I tried to push this back into the git repository but get unexpected hang-up errors (new to git as well).

can you please read this thread [1] about the same issue? And maybe test
the latest patch [2] out of the thread (v5 currently) on your
environment and send tested-by if it works out.

Best regards

Andreas Bie?mann

[1]
http://thread.gmane.org/gmane.comp.boot-loaders.u-boot/154996/focus=157422
[2] http://patchwork.ozlabs.org/patch/232394/

PS: Think about fixing your MUA, it is broken in terms of line length ...

[U-Boot] AM3517_EVM, MLO not booting

[Manfred Huber]

Hello James,

you found the same bug in the ROM code of some OMAP3 devices as I did. 
Look at the Patch 'Flush UART3 xmit on enable if TEMT is broken'. Try 
the Patch and let us know if it works.

Best regards,
Manfred

On 2013-04-02 00:24, James Chandler wrote:
> Hello,
>
> I was able to snag a BDI3000 and debug the issue.  It turns out that the NS16550 driver contains a while loop that waits for register or some other value to be set during the SPL's serial_init() function.  This condition was not being met, causing serial_init() to hang.  The solution was to add #define CONFIG_SYS_NS16550_BROKEN_TEMT to the AM3517_EVM configuration.  I tried to push this back into the git repository but get unexpected hang-up errors (new to git as well).
>
> Thanks,
> James
> ________________________________
> From: James Chandler
> Sent: Monday, April 01, 2013 11:29 AM
> To: u-boot at lists.denx.de
> Subject: AM3517_EVM, MLO not booting
>
> Hello,
>
> I am new to *nix/open-source mailing lists, so please provide any feedback about my post that would make future posts cleaner or easier to respond to.
>
> I am trying to build the u-boot-arm tree/fork from denx.de (new to git so the correct terminology escapes me) for a AM3517_EV LogicPD evaluation board.  I cloned the git repository, built the MLO and u-boot.img files and then placed them on the first partition of my SD card (fat32, active, correct #of cylinders and heads).  When I switch the power on I get two characters on my serial console ( the first is a checker-board block from extended ascii of 170ish and the other is a 't') and then no output follows.
>
> I am switching to the u-boot-arm tree/fork from the u-boot-am33x tree/fork at the Arago project, because the u-boot-am33x code from there doesn't have functional fatwrite and ext4write commands (I can build with them in place, but fatwrite causes mmc errors and timeout errors while ext4write does not give an error but does not create a file).  If I use the MLO from u-boot-am33x but the u-boot.img from u-boot-arm, I can boot into the u-boot environment and into Linux.  The fatwrite and the ext4write commands on u-boot-arm also work unlike those in u-boot-am33x.
>
> I also have a custom board based on the AM3517_EVM (same CPU and RAM just no flash).  I copied the AM35117_EVM configuration and board/* files and made only changes related to removing flash support (since the custom board does not have it) and the custom board does boot using both MLO and u-boot.img from u-boot-arm.
>
> Has anyone else had issues with MLO on the AM3517_EVM?  If so, are there any workable solutions?
>
> Thanks,
> James
>
>
>
> _______________________________________________
> U-Boot mailing list
> U-Boot at lists.denx.de
> http://lists.denx.de/mailman/listinfo/u-boot
>

[U-Boot] AM3517_EVM, MLO not booting

[James Chandler]

Manfred & Albert,

The patch did work.

Thanks,
James

P.S. Unfortunately my MUA is OWA, and I cannot change the line length myself.
________________________________________
From: Manfred Huber [man.huber at arcor.de]
Sent: Tuesday, April 02, 2013 1:25 AM
To: James Chandler
Cc: u-boot at lists.denx.de; Scott Wood; Albert ARIBAUD; Javier Martinez Canillas
Subject: Re: [U-Boot] AM3517_EVM, MLO not booting

Hello James,

you found the same bug in the ROM code of some OMAP3 devices as I did.
Look at the Patch 'Flush UART3 xmit on enable if TEMT is broken'. Try
the Patch and let us know if it works.

Best regards,
Manfred

On 2013-04-02 00:24, James Chandler wrote:
> Hello,
>
> I was able to snag a BDI3000 and debug the issue.  It turns out that the NS16550 driver contains a while loop that waits for register or some other value to be set during the SPL's serial_init() function.  This condition was not being met, causing serial_init() to hang.  The solution was to add #define CONFIG_SYS_NS16550_BROKEN_TEMT to the AM3517_EVM configuration.  I tried to push this back into the git repository but get unexpected hang-up errors (new to git as well).
>
> Thanks,
> James
> ________________________________
> From: James Chandler
> Sent: Monday, April 01, 2013 11:29 AM
> To: u-boot at lists.denx.de
> Subject: AM3517_EVM, MLO not booting
>
> Hello,
>
> I am new to *nix/open-source mailing lists, so please provide any feedback about my post that would make future posts cleaner or easier to respond to.
>
> I am trying to build the u-boot-arm tree/fork from denx.de (new to git so the correct terminology escapes me) for a AM3517_EV LogicPD evaluation board.  I cloned the git repository, built the MLO and u-boot.img files and then placed them on the first partition of my SD card (fat32, active, correct #of cylinders and heads).  When I switch the power on I get two characters on my serial console ( the first is a checker-board block from extended ascii of 170ish and the other is a 't') and then no output follows.
>
> I am switching to the u-boot-arm tree/fork from the u-boot-am33x tree/fork at the Arago project, because the u-boot-am33x code from there doesn't have functional fatwrite and ext4write commands (I can build with them in place, but fatwrite causes mmc errors and timeout errors while ext4write does not give an error but does not create a file).  If I use the MLO from u-boot-am33x but the u-boot.img from u-boot-arm, I can boot into the u-boot environment and into Linux.  The fatwrite and the ext4write commands on u-boot-arm also work unlike those in u-boot-am33x.
>
> I also have a custom board based on the AM3517_EVM (same CPU and RAM just no flash).  I copied the AM35117_EVM configuration and board/* files and made only changes related to removing flash support (since the custom board does not have it) and the custom board does boot using both MLO and u-boot.img from u-boot-arm.
>
> Has anyone else had issues with MLO on the AM3517_EVM?  If so, are there any workable solutions?
>
> Thanks,
> James
>
>
>
> _______________________________________________
> U-Boot mailing list
> U-Boot at lists.denx.de
> http://lists.denx.de/mailman/listinfo/u-boot
>