Flashing Evaluation BF537-EZKit Lite with uboot & kernel image

Hi Tejaswi,

1)bf537-stamp, bf537-mintaur, bf537-pnav and bf537-srv1 are configuration files for different boards from different vendors with BF537 processors on it.

2)If you are using the BF537 evaluation board from ADI, bf537-stamp is the one you want to use. To support your own BF537 customized board, you can take this file as reference to port for your own board.  

Hi Aaronwu,

thanks a lot for the response. I am currently facing two problems here.

1. Trying to enter into bootloader mode.

   a. Trying to get into bootloader mode using uart cable.

   b. SW16 is 7 mode

   c. SW4 0101 & JP9 no jumper connected.

   d. Set the minicom with Baud 57600 8N1, no hardware flow control

   e. Switched on the board and get junck character on the terminal.

Can you let me know if i am doing something wrong here ?

2. Build uboot on ubuntu 14.04

I have a bigger problem here building the uboot.

1. I am interested in flashing the uboot through uart, so i downloaded u-boot-2013.07-2014R1.tar.bz2 , changed the CONFIG_BFIN_BOOT_MODE to BFIN_BOOT_UART.

2. Steps to build, make mrproper, make bf537-stamp_config , make.

3. I get the following error.

ib/gcc/bfin-uclinux/4.5.3/include -pipe  -DCONFIG_BLACKFIN  -ansi -D__ASSEMBLY__ -P init.lds.S -o init.lds
bfin-uclinux-gcc   -D__ASSEMBLY__ -g  -Os   -ffixed-P3 -fomit-frame-pointer -mno-fdpic -ffunction-sections -fdata-sections -mcpu=bf537-0.2 -D__KERNEL__ -I/home/tjayaprakash/lt-CAIR/blackfin/uboot/u-boot-2013.07-2014R1/include -fno-builtin -ffreestanding -nostdinc -isystem /opt/uClinux/bfin-uclinux/lib/gcc/bfin-uclinux/4.5.3/include -pipe  -DCONFIG_BLACKFIN   -o init.o init.S -c
bfin-uclinux-gcc  -g  -Os   -ffixed-P3 -fomit-frame-pointer -mno-fdpic -ffunction-sections -fdata-sections -mcpu=bf537-0.2 -D__KERNEL__ -I/home/tjayaprakash/lt-CAIR/blackfin/uboot/u-boot-2013.07-2014R1/include -fno-builtin -ffreestanding -nostdinc -isystem /opt/uClinux/bfin-uclinux/lib/gcc/bfin-uclinux/4.5.3/include -pipe  -DCONFIG_BLACKFIN -Wall -Wstrict-prototypes -fno-stack-protector -Wno-format-nonliteral -Wno-format-security  -fno-function-sections -fno-data-sections     -o initcode.o initcode.c -c
In file included from /home/tjayaprakash/lt-CAIR/blackfin/uboot/u-boot-2013.07-2014R1/include/asm/serial.h:48:0,
                 from initcode.c:19:
/home/tjayaprakash/lt-CAIR/blackfin/uboot/u-boot-2013.07-2014R1/include/asm/serial1.h: In function ‘uart_init’:
/home/tjayaprakash/lt-CAIR/blackfin/uboot/u-boot-2013.07-2014R1/include/asm/serial1.h:238:2: warning: implicit declaration of function ‘BUG’
bfin-uclinux-ld.bfd -m elf32bfin  -T init.lds init.o initcode.o -o init.elf
bfin-uclinux-ld.bfd:init.lds:1: ignoring invalid character `#' in expression
bfin-uclinux-ld.bfd:init.lds:1: syntax error
Makefile:64: recipe for target 'init.elf' failed
make[1]: *** [init.elf] Error 1
make[1]: Leaving directory '/home/tjayaprakash/lt-CAIR/blackfin/uboot/u-boot-2013.07-2014R1/arch/blackfin/cpu'
Makefile:601: recipe for target 'arch/blackfin/cpu/libblackfin.o' failed
make: *** [arch/blackfin/cpu/libblackfin.o] Error 2

Request you to kindly address the problems faced.

Regards,

Tejaswi

Hi Tejaswi,

1. The SW16 set to 7 is right, jumper 9 not connected is right. for SW4, just make sure the UART0_RX bit is on, minicom setting is correct. If it does not load successfully, try press the reset button or power on/off for a few times.

2. you may double check the matched version of toolchain for the u-boot source code is installed, would recommend to use 2014R1 for both.

Thanks

Aaron

Thanks Aaron !!

1. Still with multiple resets there is not data in the minicom

2. Both the versions, toolchain and uboot are 2014R1.

Is there any other solution that is available for the above.

Regards,

Tejaswi

Hi Tejaswi,

For UART boot, after switching to position 7, and reset, you are not supposed to see meaningful output on the console, instead, you are suppose to download u-boot from this UART port, as described by the document. After the downloading through UART is done, u-boot will get run and you start to get output on console.

Thanks

Aaron