2009-10-24 02:59:49     Problems loading uImage onto bf533 EZKIT

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

2009-10-24 02:59:49     Problems loading uImage onto bf533 EZKIT

d h (AUSTRALIA)

Message: 81648   

 

Hey,

 

I have flash U-boot 'para' onto my ezkit and now I am trying to get the uClinux working. I set up kermit and try to send "uImage-bf533-ezkit-2009R1-RC6" to it but goes incredibly slow and the eventually dies because there are so many sending errors?? (Max it has gotten to is 8% and estimated time is 2hrs!). In frustration I tried to flash the uImage through VDSP using the HSUSB Emulator to the address 0x1000000 but it says there is not enough space.

 

I have also tried the tftp through the usb-lan extender but it keeps failing and saying "Retry Count exceded". If anyone can help that would be great.

 

Also, what is the difference between the U-boots "para" and "bypass" and which should be used and when?

 

Thanks..

QuoteReplyEditDelete

 

 

2009-10-24 03:05:04     Re: Problems loading uImage onto bf533 EZKIT

Mike Frysinger (UNITED STATES)

Message: 81649   

 

you need to make sure your tftp server is set up properly.  please read the documentation:

  docs.blackfin.uclinux.org/doku.php?id=setting_up_a_tftp_server

 

as for the boot modes, please read the HRM for your variant or the reduced documentation:

  docs.blackfin.uclinux.org/doku.php?id=bootloaders:bootrom

QuoteReplyEditDelete

 

 

2009-10-24 07:02:10     Re: Problems loading uImage onto bf533 EZKIT

d h (AUSTRALIA)

Message: 81671   

 

I was using a serial->usb converter and it seems to be hopeless? Lots of dropped packets and loading the uImage with it failed everytime.. I connected it to my desktop which has serial natively and the uImage loaded in about 12 mins. However - it didnt boot up? I used the "uImage-bf533-ezkit-2009R1-RC6" is this ok? Is there something else I should have done?

 

Didn't manage to get the tftp working - I have it set up per the debian instructions and I believe the ezkit usb lan is in the right configuration. Do I need to set the host computers eth0 ip or anything?

QuoteReplyEditDelete

 

 

2009-10-24 18:54:40     Re: Problems loading uImage onto bf533 EZKIT

Mike Frysinger (UNITED STATES)

Message: 81673   

 

you're probably using a cheap piece of ****.  a lot of usb<->serial converters are known to be terrible (just like our documentation says).

 

run at a lower baud rate or go buy a different one or get a machine with a real serial port.

 

i dont know what you mean by "didnt boot up".  you need to post actual output from the console that you're seeing.

 

umm, if your desktop computer doesnt have networking properly configured, i dont see how you could possibly expect to work with it via the network from other machines.

QuoteReplyEditDelete

 

 

2009-10-25 03:04:35     Re: Problems loading uImage onto bf533 EZKIT

d h (AUSTRALIA)

Message: 81674   

 

you're probably using a cheap piece of ****.  a lot of usb<->serial converters are known to be terrible (just like our documentation says).

 

    -Yeh I figured

 

i dont know what you mean by "didnt boot up".  you need to post actual output from the console that you're seeing.

 

    -I have posted what I have been doing below.

 

"i dont see how you could possibly expect to work with it via the network from other machines"

 

   -I dont expect this to work because I am not trying to and never said so? I am just trying from my desktop computer to the ezkit?

 

---

 

-I load the binary uImage via serial to the ezkit:

 

Linux Kermit> send Desktop/uImage

 

 

 

-When I connect after it shows:    

 

           

Linux Kermit> connect                             

Connecting to /dev/ttyS0, speed 57600             

Escape character: Ctrl-\ (ASCII 28, FS): enabled 

Type the escape character followed by C to get back,

or followed by ? to see other options.            

----------------------------------------------------

## Total Size      = 0x00379215 = 3641877 Bytes   

## Start Addr      = 0x01000000 

 

 

 

-When I reett the board I get this:

 

bfin>

 

U-Boot 2008.10 (ADI-2009R1-rc3) (Jul 16 2009 - 18:01:25)

 

CPU:   ADSP bf533-0.3 (Detected Rev: 0.5) (parallel flash boot)

Board: ADI BF533 EZ-Kit Lite board

       Support:   blackfin.uclinux.org/

Clock: VCO: 594 MHz, Core: 594 MHz, System: 118.800 MHz

RAM:   32 MB

Flash:  2.1 MB

In:    serial

Out:   serial

Err:   serial

Net:   MAC:   00:E0:22:FE:58:A3

Hit any key to stop autoboot:  0

SMC91111: PHY auto-negotiate timed out

Using MAC Address 00:E0:22:FE:58:A3

TFTP from server 192.168.1.1; our IP address is 192.168.1.99

Filename 'uImage'.

Load address: 0x1000000

Loading: T T T T T T T T T T

Retry count exceeded; starting again

TFTP from server 192.168.1.1; our IP address is 192.168.1.99

Filename 'uImage'.

Load address: 0x1000000

Loading: T T T T T T T T T T

... forever

 

- I am not sure what to do?

QuoteReplyEditDelete

 

 

2009-10-25 03:31:14     Re: Problems loading uImage onto bf533 EZKIT

Mike Frysinger (UNITED STATES)

Message: 81676   

 

i'm not talking about the tftp errors.  you said booting the file loaded over the serial didnt work, but you didnt show any output.

 

to resolve the tftp issues, read the tftp documentation and the troubleshooting section.

QuoteReplyEditDelete

 

 

2009-10-25 03:39:25     Re: Problems loading uImage onto bf533 EZKIT

d h (AUSTRALIA)

Message: 81677   

 

I may be wrong, but from what I have read I thought that I was able to use "loadb" from U-boot then use kermit to send the binary uImage via serial. I got the file to transfer working via serial by using my desktop which a 'real' serial port.

 

My understand was that this uImage was stored in flash and U-boot would boot it up when i reset the board? However U-boot just times out forever trying to load it (as shown in my previous post).

QuoteReplyEditDelete

 

 

2009-10-25 04:17:05     Re: Problems loading uImage onto bf533 EZKIT

Mike Frysinger (UNITED STATES)

Message: 81678   

 

why would the image be written to flash ?  did you write the file to flash ?  if you dont write it, u-boot isnt going to do anything automatically for you.

 

transferring the file over the serial into ram does that -- writes to ram.  there is nothing else happening unless you told the board to do so.

QuoteReplyEditDelete

 

 

2009-10-25 04:42:16     Re: Problems loading uImage onto bf533 EZKIT

d h (AUSTRALIA)

Message: 81679   

 

ok.........

 

I thought it was writing it to flash. How do I save the uImage to flash?

QuoteReplyEditDelete

 

 

2009-10-25 05:17:27     Re: Problems loading uImage onto bf533 EZKIT

Mike Frysinger (UNITED STATES)

Message: 81680   

 

i imagine the documentation would explain it ...

 

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

QuoteReplyEditDelete

 

 

2009-10-25 05:34:16     Re: Problems loading uImage onto bf533 EZKIT

d h (AUSTRALIA)

Message: 81681   

 

yeh thanks - i hadn't seen that... However the ezkit only has 2mb which sucks.. I tried to save the flash but the uImage is 3.5mb and so there is not enough space.. That uImage says it is for the bf533 exkit so why is it 3.5mb when there is only 2mb flash available?

QuoteReplyEditDelete

 

 

2009-10-25 06:36:21     Re: Problems loading uImage onto bf533 EZKIT

Mike Frysinger (UNITED STATES)

Message: 81683   

 

if you want a smaller uImage, build one yourself and remove things you dont want

 

QuoteReplyEditDelete

 

 

2009-10-25 23:26:44     Re: Problems loading uImage onto bf533 EZKIT

d h (AUSTRALIA)

Message: 81693   

 

building the kernel seems a bit overwhelming right at the moment - I don't really know what the most important things are or what are the largest components to leave out to halve the size of the kernel for the bf533 ezkit...

 

I have momentarily switched over to a bf561 ezkit to get around this for now as it has 8mb flash. I read the link regarding flash - I am still unclear on something though. The loadb command loads it into the RAM at 0x01000000, but at what address should I save it to on flash? I am also wondering if I could just use my HSUSB JTAG to flash the uImage? Again - I am not too sure of the location though.

QuoteReplyEditDelete

 

 

2009-10-26 00:15:20     Re: Problems loading uImage onto bf533 EZKIT

d h (AUSTRALIA)

Message: 81694   

 

I am trying to build the uImage and reduce it to fit on the bf533 ezkit... However, after doing 'make menuconfig' then 'make' it continues to fail at this point...

 

At first it was failing at 'freetype' so I removed it from my build, but I get the same error but now for something different..

 

 

 

make[3]: Leaving directory `/home/dan/Desktop/uClinux-dist/lib/sphinxbase'

make[3]: Leaving directory `/home/dan/Desktop/uClinux-dist/lib/lzo'

make[2]: Leaving directory `/home/dan/Desktop/uClinux-dist/lib'

[ -z "libg zlib lzo blackfin-gsm bluez-libs dmalloc ftplib libaudio libmodbus mpeg2dec libtool libusb speex sphinxbase" ] || /home/dan/Desktop/uClinux-dist/tools/cross-fix-root

[ -z "boost           " ] || make -j4 boost || exit $?

make[2]: Entering directory `/home/dan/Desktop/uClinux-dist/lib'

[ ! -d "boost" ] || ( touch boost/.sgbuilt_lib && make -C boost ) || exit $?

make[3]: Entering directory `/home/dan/Desktop/uClinux-dist/lib/boost'

cd boost_1_38_0/tools/jam/src && env LOCATE_TARGET=build ./build.sh

echo 'using gcc : 4.1.2 : bfin-uclinux-g++ : <cxxflags>"-pipe -Wall -g -O2  -mcpu=bf533-0.3 -DEMBED -D__uClinux__ -I/home/dan/Desktop/uClinux-dist  -mcpu=bf533-0.3 -DBOOST_NO_INTRINSIC_WCHAR_T" <linkflags>" -Wl,-elf2flt    -mcpu=bf533-0.3 -Wl,-z,defs" ;' > boost_1_38_0/user-config.jam

###

### Using 'gcc' toolset.

###

rm -rf bootstrap

mkdir bootstrap

gcc -o bootstrap/jam0 command.c compile.c debug.c expand.c glob.c hash.c hdrmacro.c headers.c jam.c jambase.c jamgram.c lists.c make.c make1.c newstr.c option.c output.c parse.c pathunix.c pathvms.c regexp.c rules.c scan.c search.c subst.c timestamp.c variable.c modules.c strings.c filesys.c builtins.c pwd.c class.c native.c w32_getreg.c modules/set.c modules/path.c modules/regex.c modules/property-set.c modules/sequence.c modules/order.c execunix.c fileunix.c

hash.c: In function ‘hashstat’:

hash.c:458: warning: format ‘%ld’ expects type ‘long int’, but argument 7 has type ‘unsigned int’

In file included from jam.c:109:

patchlevel.h:16:1: warning: "VERSION" redefined

In file included from /opt/ode/ode/include/ode/memory.h:28,

                 from jam.h:415,

                 from jam.c:107:

/usr/local/include/ode/config.h:251:1: warning: this is the location of the previous definition

./bootstrap/jam0 -f build.jam --toolset=gcc --toolset-root= clean

re error corrupted program

re error corrupted program

re error corrupted program

re error corrupted program

re error corrupted program

re error corrupted program

re error corrupted program

re error corrupted program

re error corrupted program

re error corrupted program

re error corrupted program

re error corrupted program

re error corrupted program

re error corrupted program

re error corrupted program

re error corrupted program

re error corrupted program

re error corrupted program

re error corrupted program

re error corrupted program

re error corrupted program

###

### No toolset specified. Please use --toolset option.

###

### Known toolsets are: acc, borland, cc, como, darwin, gcc, gcc-nocygwin, intel-linux, intel-win32, kcc, kylix, metrowerks, mingw, mipspro, msvc, qcc, pathscale, pgi, sun, sunpro, tru64cxx, vacpp, vc7, vc8, vc9, vmsdecc

###

make[3]: *** [/home/dan/Desktop/uClinux-dist/lib/boost/boost_1_38_0/tools/jam/src/build/bjam] Error 1

make[3]: Leaving directory `/home/dan/Desktop/uClinux-dist/lib/boost'

make[2]: *** [boost] Error 2

make[2]: Leaving directory `/home/dan/Desktop/uClinux-dist/lib'

make[1]: *** [all] Error 2

make[1]: Leaving directory `/home/dan/Desktop/uClinux-dist/lib'

make: *** [subdirs] Error 1

QuoteReplyEditDelete

 

 

2009-10-26 01:18:56     Re: Problems loading uImage onto bf533 EZKIT

Mike Frysinger (UNITED STATES)

Message: 81697   

 

typical development is not "download prebuilt image, write into flash, and boot that" as you will often need to change kernel options and/or user space appliations.  you need to fix your environment so that things boot over the network quickly so you can make minor changes, rebuild, and boot the new image.

 

there is no specific location where things must be written in flash.  the hardware is there for you to use however you want.  that means you program the image wherever you want.  the only thing already being used in the flash is u-boot (the sectors marked RO in the default `flinfo` output), so you probably dont want to clobber those.

 

as for the HSUSB JTAG, please read the documentation (it does have a search function you know):

  docs.blackfin.uclinux.org/doku.php?id=hw:jtag:adi-usb-ice

QuoteReplyEditDelete

 

 

2009-10-26 01:19:53     Re: Problems loading uImage onto bf533 EZKIT

Mike Frysinger (UNITED STATES)

Message: 81698   

 

instead of making things complicated, you should just start out with the default settings and build those up.  once you have something working, then you can add/remove packages.  in this case, i highly doubt you actually want boost, and it isnt in any default build.

 

QuoteReplyEditDelete

 

 

2009-10-26 02:33:05     Re: Problems loading uImage onto bf533 EZKIT

d h (AUSTRALIA)

Message: 81699   

 

I just tried to make the default dist but I get this:

 

  CC      libbb/xrealloc_vector.o

  CC      libbb/xregcomp.o

  AR      libbb/lib.a

  LINK    busybox_unstripped

Trying libraries: crypt m

Library crypt is not needed, excluding it

Library m is not needed, excluding it

Final link with: <none>

make[4]: Leaving directory `/home/dan/Desktop/uClinux-dist/user/busybox/build-busybox-1.13.4'

make[3]: Leaving directory `/home/dan/Desktop/uClinux-dist/user/busybox'

make[2]: Leaving directory `/home/dan/Desktop/uClinux-dist/user'

make[1]: *** [all] Error 2

make[1]: Leaving directory `/home/dan/Desktop/uClinux-dist/user'

make: *** [subdirs] Error 1

dan@dan:~/Desktop/uClinux-dist$

dan@dan:~/Desktop/uClinux-dist$

 

 

 

I also have some trouble understanding the exact commands to get uImage from memory to flash...

 

protect off all

 

erase 0x201C0000 0x2026FFFF

 

cp.b 0 0x201c0000 10 <-- how do I tell this command that I want the uImage from memory to be

copied to the flash address starting at 0x201c0000?

 

Thanks for your patience mike, I am obviously very new to all this but keen to get things going..

 

QuoteReplyEditDelete

 

 

2009-10-26 03:30:59     Re: Problems loading uImage onto bf533 EZKIT

Mike Frysinger (UNITED STATES)

Message: 81704   

 

your output doesnt include the actual error.  you need to either read the whole log to find the error or run `make single` so that the build aborts when the first error is hit.

 

your example u-boot command is already copying to 0x201c0000

QuoteReplyEditDelete

 

 

2010-05-27 06:46:51     Re: Problems loading uImage onto bf533 EZKIT

Waqas Saleem (PAKISTAN)

Message: 89914   

 

Im having the same error while compiling the uclinux distro.

 

  LINK    busybox_unstripped

Trying libraries: crypt m

Library crypt is not needed, excluding it

Library m is not needed, excluding it

Final link with: <none>

make[4]: Leaving directory `/home/user/Desktop/uClinux-dist/user/busybox/build-busybox-1.13.4'

make[3]: Leaving directory `/home/user/Desktop/uClinux-dist/user/busybox'

make[2]: Leaving directory `/home/user/Desktop/uClinux-dist/user'

make[1]: *** [all] Error 2

make[1]: Leaving directory `/home/user/Desktop/uClinux-dist/user'

make: *** [subdirs] Error 1

 

 

help needed.....

QuoteReplyEditDelete

 

 

2010-05-27 14:22:35     Re: Problems loading uImage onto bf533 EZKIT

Mike Frysinger (UNITED STATES)

Message: 89924    no, you arent. this is an old thread, and you didnt even follow the

recommendation i gave regarding this output. do what i said already

and if you still cant figure out what's broken on your system, start a

new thread:

  blackfin.uclinux.org/gf/forummessage/81704

Attachments

    Outcomes