2008-04-11 05:46:44     BF527 u-boot booting from UART trouble

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

2008-04-11 05:46:44     BF527 u-boot booting from UART trouble

Ji Ma (CHINA)

Message: 54086   

 

HI, everybody, my ADSP-BF527 EZ-KIT LITE 1.4 demo board with the part number ADZS-BF5270EZLITE shipped from ADI can not boot up when I put the demo image "u-boot-bf527-ezkit-uart-2008r1.ldr" download from this websit's u-boot project (the demo board have no hardware bug, can run the demo routine in the parallel flash). I am using ldrviewer1.2 on windows XP download today. Some questions I have to ask your kindly help:

 

        1. Which console uart port does the demo BF527 uart  boot ldr image file refer to (could you please give me a standard and detail deal procedure for this situation)?

 

         2. When I compile the u-boot.ldr to uart booting, I am only known the system clock is generated the frequency setted by me, in the u-boot srouce I just modify the marcro BFIN_BOOT_MODE to BFIN_BOOT_UART, the other are the default setting , is it enough for the DEMO board boot up? (the u-boot.ldr is picked up at the u-boot source tree's root directory).

 

many thanks for all of your attention.

 

Ji Ma

 

       

QuoteReplyEditDelete

 

 

2008-04-11 12:08:41     Re: BF527 u-boot booting from UART trouble

Mike Frysinger (UNITED STATES)

Message: 54098    the UART# should be on the silkscreen of the board itself.  otherwise, check the BF527-EZKIT manual from analog.com.

 

you must also load the ldr at 115200 baud or it probably wont work.

 

the default clock settings work fine regardless of boot mode.

QuoteReplyEditDelete

 

 

2008-04-11 22:00:58     Re: BF527 u-boot booting from UART trouble

Ji Ma (CHINA)

Message: 54130   

 

Mike,Thanks for your reply.

 

BF527-EZKIT has two uarts are all silksreened on the board , UART1 is a complete RS232 port, UART0 is just expansion with a simple slot use for stamp mode. both two UARTS can be used for boot issue.

 

I can not get the correct processor's first reply (this reply is not after ldr loaded but when autobaud)  when I use 115200 baud rate,but use 57600. I think the serial port is already set the baud rate at 57600 in u-boot.ldr , so, when I finish download the ldr file through uart , I can get the right response data feedback from the processor with ldrvierwer or other uart tools.

 

I am sure I got the right boot mode setting. if this thing goes wrong ,no first reply I metioned above can be obtain. and about the frequency I describled above , I just want to tell you , the u-boot.ldr I compiled can correct make one thing change for the board, but can not get the final console message output.

 

For the simplest solution. could you please tell me , how to load the demo image for bf527-ezkit  from website to  get the console message? (please in detail, make sure you have ever done this procedure, or this image  is under tested on the bf527-ezkit).

 

many many thanks.

QuoteReplyEditDelete

 

 

2008-04-11 23:34:38     Re: BF527 u-boot booting from UART trouble

Mike Frysinger (UNITED STATES)

Message: 54131    the u-boot.ldr assumes 115200 baud while loading and wont work at any other rate

 

it doesnt matter what the serial port is configured as before executing ldr as it will reconfigure everything for you

 

if you cant get it to autobaud properly, please try svn toolchain trunk

 

the method for booting over uart is the same regardless of processor:

http://docs.blackfin.uclinux.org/doku.php?id=bootloaders:u-boot:loading

 

as for testing the released images, every single on posted on the release page has been tested

QuoteReplyEditDelete

 

 

2008-04-12 00:06:14     Re: Re: BF527 u-boot booting from UART trouble

Pafone Lee (CHINA)

Message: 54132    can i have your qq , Ji Ma? I 'm from SCUT,Guangzhou

TranslateQuoteReplyEditDelete

 

 

2008-04-12 01:50:50     Re: BF527 u-boot booting from UART trouble

Ji Ma (CHINA)

Message: 54135   

 

Hi, Mike, Am I got this equal message from you , the newest verion 1.2 of ldrvierwer on Windows XP for this demo image load to this demo board only support 115200 baud rate (May be these will abandon the gerenal theory ,but  if I can boot up this board,I made myself accept this issue temporarily).

 

For the "properly autobaud get",I can get 57600 autobaud properly, but can not get the 115200, my workstation's serial port and serial port cable are good, They are loopback tested under 115200. May be much SI(signal integrity) problem happened under 115200 when on ldr load application. it should be a less probability .  I think whatever the baudrate I use for the ldr loading,the u-boot shoud be booted well, then I can change the baud rate to the ldr file pre-setted to get the console.

 

and, Which uart port as the console when demo ldr uart u-boot file boot the device up, UART0 or UART1?

 

Finally, wha't the matter to the toolchain on autobaud issue?

 

thanks a lot

 

你好,李生:我一般用SKYPE:maji_999 QQ:84155986

QuoteReplyEditDelete

 

 

2008-04-12 04:20:44     Re: BF527 u-boot booting from UART trouble

Ji Ma (CHINA)

Message: 54143   

 

Mike , I think something wrong in the file u-boot-bf527-ezkit-uart-2008R1.ldr posted on your websit. I return to the linux deal the same thing get the following message:

 

 

 

<< start

 

[root@localhost ~]# ./bfin-uclinux-ldr -l u-boot-bf527-ezkit-uart-2008R1.ldr /dev/ttyS0 && kermit -l /dev/ttyS0 -b 115200 -C connect

Loading LDR u-boot-bf527-ezkit-uart-2008R1.ldr ... auto detected LDR as 'BF548'

OK!

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

Opening /dev/ttyS0 ... OK!

Configuring terminal I/O ... OK!

Trying to send autobaud ... OK!

Trying to read autobaud ... OK!

Checking autobaud ... Failed: wanted {0xBF,..,..,0x00} but got {0xBF,[0x90],[0x80],0x80}

Failed: Bad file descriptor

[root@localhost ~]# ./bfin-uclinux-ldr -l u-boot-bf527-ezkit-uart-2008R1.ldr /dev/ttyS0 && kermit -l /dev/ttyS0 -b 57600 -C connect

Loading LDR u-boot-bf527-ezkit-uart-2008R1.ldr ... auto detected LDR as 'BF548'

OK!

Opening /dev/ttyS0 ... OK!

Configuring terminal I/O ... OK!

Trying to send autobaud ... OK!

Trying to read autobaud ... OK!

Checking autobaud ... Failed: wanted {0xBF,..,..,0x00} but got {0xBF,[0x10],[0x80],0x80}

Failed: Bad file descriptor

[root@localhost ~]#

 

>> end

 

Why such the ldr I loaded is bf527 but appear 'BF548'?

 

I compiled  the u-boot by myself also complain this message. I don't want modify this ID-like string in LDR file manually to fit the program's requirements pass to the next  following stage.

 

 

QuoteReplyEditDelete

 

 

2008-04-12 13:03:02     Re: BF527 u-boot booting from UART trouble

Mike Frysinger (UNITED STATES)

Message: 54147    there is no id string in the LDR file.  the BF52x and BF54x have the same LDR format, so the message is perfectly ok.

QuoteReplyEditDelete

 

 

2008-04-12 13:40:25     Re: BF527 u-boot booting from UART trouble

Mike Frysinger (UNITED STATES)

Message: 54148    there are plans to make u-boot load over the uart at any baud rate, but today it wont work.  the released images only work at 115200 baud.  if you need a slower baud, you'll have to reconfigure the source yourself and build/boot the new image.

 

the ldr itself doesnt matter though if ldr-utils cant autobaud with the board.  the ldr is not used at all until autobaud has completed.  if you're getting back garbage bytes during the autobaud process, then something below ldr-utils is messing up.  either bum driver, or bum hardware, or bum cable, something.

 

the bf527-ezkit only has one uart, so it stands to reason that would be the default console.

QuoteReplyEditDelete

Attachments

    Outcomes