2008-04-04 10:51:49     u-boot 1.1.6 difficulties.

Document created by Aaronwu Employee on Sep 17, 2013
Version 1Show Document
  • View in full screen mode

2008-04-04 10:51:49     u-boot 1.1.6 difficulties.

blue hash (UNITED STATES)

Message: 53643    Hello,

I'm trying to use minicom to load u-boot(1.1.6) to SRAM.

I changed my board config files too.

 

 

However, the process stops at autobaud. I can load the files using LDRviewer in Windows.

 

[root@localhost u-boot-1.1.6-2008R1]# bfin-uclinux-ldr -v -l u-boot.ldr /dev/ttyS0

Loading LDR u-boot.ldr ... auto detected LDR as 'BF537'

OK!

Removing stale lock '//var/lock/LCK..ttyS0'

Opening /dev/ttyS0 ... OK!

Configuring terminal I/O ... [getattr] [setattr] [speed:115200] OK!

Trying to send autobaud ...

 

It hangs here and then times out.

Questions:

1>Whats "[getattr] [setattr] [speed:115200] OK!". Minicom is configured at 57600 N81, no flow.

 

2>how do I check if the SRAM  has U-boot loaded.

 

3>The process goes well in windows, but then theres no respone from u-boot. Is this because the clocks make be wrong or the u-boot did not load into SRAM.? or SRAM did not initialise.

QuoteReplyEditDelete

 

 

2008-04-04 11:07:01     Re: u-boot 1.1.6 difficulties.

Mike Frysinger (UNITED STATES)

Message: 53644    you cant run minicom (or any other terminal emulator) at the same time as ldr.  if it's hanging at "trying to send autobaud", it means there is something wrong on your host system.

 

ldr loads at a faster baud rate than the default console for obvious reasons.

 

u-boot doesnt get loaded into sram, it gets loaded into external memory.  but to check any such thing, you need jtag.

QuoteReplyEditDelete

 

 

2008-04-04 11:33:22     Re: u-boot 1.1.6 difficulties.

Graham Davies (UNITED STATES)

Message: 53645    I don't want to contradict Mike, but in case it helps you I want to say that I have had similar problems with u-boot 1.1.3.  Nobody here could figure out why, but it turned out that the solution was to have minicom up and running before starting ldrviewer.  Yes, this is the exact opposite of what makes sense.  But, it worked and was reproducible every time.  We have now brushed this under the carpet by switching to the Windoze version of ldrviewer, which behaves as you would expect.  The problem now is that ldrviewer has to finish before you can start TeraTerm (I refuse to even try to use HyperTerminal).  By the time TeraTerm is up on the screen, any output from u-boot has long gone.  But, if it worked, just rattling the Enter key produces the prompt.

 

Graham.

QuoteReplyEditDelete

 

 

2008-04-04 11:45:12     Re: u-boot 1.1.6 difficulties.

Mike Frysinger (UNITED STATES)

Message: 53646    older versions of ldr-utils would not fully configure the serial port and by running minicom first, it would properly configure everything.  this however should be resolved with 2008R1+.

QuoteReplyEditDelete

 

 

2008-04-04 12:28:44     Re: u-boot 1.1.6 difficulties.

Graham Davies (UNITED STATES)

Message: 53647    Then my experiences don't help the OP.  Darn.  Oh, well.

 

Graham.

QuoteReplyEditDelete

 

 

2008-04-04 12:36:40     Re: u-boot 1.1.6 difficulties.

Mike Frysinger (UNITED STATES)

Message: 53648    if you could retest your experience and see if things now work, that'd be helpful

QuoteReplyEditDelete

 

 

2008-04-04 12:48:00     Re: u-boot 1.1.6 difficulties.

Graham Davies (UNITED STATES)

Message: 53649    OK, we're dragging ourselves forward to u-boot 1.1.6 and 2008R1 and I will try to remember to report back when we get there.

 

Graham.

QuoteReplyEditDelete

 

 

2008-04-04 17:07:55     Re: u-boot 1.1.6 difficulties.

blue hash (UNITED STATES)

Message: 53654    Thank you both for your help. I tried what Graham said, but the port now gets locked.

 

For now, I'm working on a windows machine.(Debugging why the host is not loading u-boot will be done some other time)

The file init_sdram.S  (cpu/BF537/) is no longer present in 1.1.6, am I right?

I ask this because changes were made to this file in 1.1.3. where do I incorporate those changes now?

 

QuoteReplyEditDelete

 

 

2008-04-04 19:20:15     Re: u-boot 1.1.6 difficulties.

Mike Frysinger (UNITED STATES)

Message: 53658    all of the blackfin procs have been unified.  regardless, you should not be changing any code in the cpu blackfin directory.

 

why do you think you need to change something in there ?

QuoteReplyEditDelete

 

 

2008-04-10 19:09:37     Re: u-boot 1.1.6 difficulties.

blue hash (UNITED STATES)

Message: 54054    Thanmks Mike.

 

As of my first post:

 

I tried connecting a BF537-ezkit to  my linux box with the above command

bfin-uclinux-ldr -v -l u-boot.ldr /dev/ttyS0

 

u-boot is 1.1.6, kit is rev 2.2 in UART boot mode.

and it works well, I even get a prompt on minicom later on.

So it's probably not a host system problem.

However the same board when loaded via ldrviewer in Windows, shows no response after the DXE has loaded.

 

Now for the custom board.

Ldrviewer loads the DXE(1.1.6), but no response. But I have a compiled version of u-boot 1.1.3 and it loads and responds well.However, in linux it refuses to load any version of u-boot. It hangs at sending autobaud.

 

Sorry, there are alot of variables here, but why does the ezkit work well in linux and not in windows. And if the ezkit loads the DXE in linux, why cant my custom board load it.

 

 

QuoteReplyEditDelete

 

 

2008-04-10 21:19:34     Re: u-boot 1.1.6 difficulties.

Mike Frysinger (UNITED STATES)

Message: 54056    try the latest ldr version in toolchain svn trunk

QuoteReplyEditDelete

 

 

2008-04-11 11:52:08     Re: u-boot 1.1.6 difficulties.

blue hash (UNITED STATES)

Message: 54094    Mike,

Should I checkout ldr-utils and run make && make install or should I install the whole toolchain from trunk.

QuoteReplyEditDelete

 

 

2008-04-11 12:08:36     Re: u-boot 1.1.6 difficulties.

blue hash (UNITED STATES)

Message: 54097    Ha! it worked.

I think the problem was u-boot was looking for the RTS/CTS lines, which we dont have hooked up on the custom board.

Thats why the EZ kit worked in linux well.

 

The present release version of u-boot 1.1.6 doesn't have this feature.

From the svn log(ldr.c), revison 2151 has the option of disabling rts/cts.

 

Thanks for all the help.

QuoteReplyEditDelete

 

 

2008-04-11 12:28:22     Re: u-boot 1.1.6 difficulties.

Mike Frysinger (UNITED STATES)

Message: 54100    u-boot doesnt care about RTS/CTS ... the bootrom/development host use those lines only.  but if the pin was floating and the development host was checking it, then it'd think the board was asserting it and that it couldnt send anything just yet.

QuoteReplyEditDelete

 

 

2008-04-11 13:04:11     Re: u-boot 1.1.6 difficulties.

blue hash (UNITED STATES)

Message: 54102    Thanks,

But on the svn(http://blackfin.uclinux.org/gf/project/toolchain/scmsvn/?action=browse&path=%2Ftrunk%2Fldr-utils%2Fldr.c&view=log)

 

it says(2151):

"add an option to control hardware flow control and disable it by default as it can cause read/write hangs on ports that do not have crtrts hooked up"

<pre class="vc_log">Although I didnt see any options(-) for it, when I did a help on ldr.

 

 

QuoteReplyEditDelete

 

 

2008-04-11 13:20:27     Re: u-boot 1.1.6 difficulties.

Mike Frysinger (UNITED STATES)

Message: 54104    sorry, but did you have a question ?

QuoteReplyEditDelete

 

 

2008-04-11 13:25:38     Re: u-boot 1.1.6 difficulties.

blue hash (UNITED STATES)

Message: 54106    I meant I didnt see an option like the following:

      --show            <ldrs>          * Show details of a LDR

      --dump            <ldrs>          * Break DXEs out of LDR

      --load            <ldr> <tty>     * Load LDR over UART

      --create          <ldr> <elfs>    * Create LDR from binaries

 

Has there to be one for enabling/disabling RTS/CTS?

QuoteReplyEditDelete

 

 

2008-04-11 14:03:30     Re: u-boot 1.1.6 difficulties.

Mike Frysinger (UNITED STATES)

Message: 54107    rtscts is a load-specific option, so it isnt going to show up in the general help

Attachments

    Outcomes