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