Because of the holidays, TI E2E™ design support forum responses will be delayed from Dec. 25 through Jan. 2. Thank you for your patience.

  • State Resolved
  • Locked Locked
  • Replies 6 replies
  • Subscribers 101 subscribers
  • Views 1554 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

U-BOOT-2015-01： SPL boot UBOOT

zhongfeng chen
Intellectual 275 points
Other Parts Discussed in Thread: OMAP-L138, OMAPL138

Hi:

I'm porting u-boot-2015-01 release version to my board whose cpu is OMAP-L138. I have succed make the source files,then burned u-boot.ais and u-boot.bin files into the board, the u-boot.ais works well, but can't boot u-boot. The u-boot.ais echo informations:


U-Boot SPL 2015.01 (Apr 21 2015 - 22:01:53)
Boot device SPI FLASH
************ SPI1_BUS 1 *************
SPI probe success.
spl_image header info:
spl_image.name = `
spl_image.entry_point = 0xc1080000
spl_image.load_addr = 0xc107ffc0
spl_image.size = 0x3a0c8
spl_image.flags = 0 spl_image.os=17
image entry point: 0xC1080000 //This infor is jump_to_image_no_args function echo 

From above echo information, u-boot.ais works well,and the u-boot.bin file's head is ok. But head information seems different to u-boot.map file:(following is part of u-boot.map )

Linker script and memory map

Address of section .text set to 0xc1080000
0x00000000 . = 0x0
0x00000000 . = ALIGN (0x4)

.text 0xc1080000 0x285c0
*(.__image_copy_start)
.__image_copy_start
0xc1080000 0x0 arch/arm/lib/built-in.o
0xc1080000 __image_copy_start
*(.vectors)
.vectors 0xc1080000 0x300 arch/arm/lib/built-in.o
0xc1080030 _not_used
0xc108002c _data_abort
0xc1080034 _irq
0xc1080040 IRQ_STACK_START_IN
0xc1080028 _prefetch_abort
0xc1080000 _start
0xc1080038 _fiq
0xc1080020 _undefined_instruction
0xc1080024 _software_interrupt
arch/arm/cpu/arm926ejs/start.o(.text*)
.text 0xc1080300 0x5c arch/arm/cpu/arm926ejs/start.o
0xc1080300 reset
0xc1080318 c_runtime_cpu_setup
*(.text*)
.text 0xc108035c 0x4 arch/arm/cpu/arm926ejs/built-in.o
0xc108035c lowlevel_init

The entry point is 0xc1080300?

Could someone give me any help?

Thanks!

Regards,

Zhongfeng Chen

 

 

 

  • 0
    TI__Guru** 116100 points

    I'm porting u-boot-2015-01 release version to my board whose cpu is OMAP-L138. I have succed make the source files,then burned u-boot.ais and u-boot.bin files into the board, the u-boot.ais works well, but can't boot u-boot. The u-boot.ais echo informations:

    Why did you flash "u-boot.ais" and "u-boot.bin" ?
    Are you flashed both binaries ?

    What type of board are you using ?
    EVM or LCDK or custom ?

    If it custom, what flash device are you using ? SPI flash or NAND flash etc., ?
  • 0 in reply to Titusrathinaraj Stalin
    Intellectual 275 points

    Hi:

    I have tested both EVM board and custom board.Custom board has both SPI flash and NAND flash. And currently I just use SPI flash on custom board.

    I flashed both binaries: u-boot.ais and u-boot.bin through sfh_omap-l138.exe tool.

    The storage of SPI flash on custom board is 32Mb,which is half of the EVM board's SPI flash. BUt it's enough to contain both binaries.

    Thanks!

  • 0 in reply to zhongfeng chen
    TI__Guru** 116100 points
    Hi,
    I've tested with LogicPD EVM board and working good.

    To build:
    make da850evm_config ARCH=arm CROSS_COMPILE=arm-arago-linux-gnueabi-
    make all ARCH=arm CROSS_COMPILE=arm-arago-linux-gnueabi-

    Now, you would get "u-boot.ais" file and needs to be flashed into SPI flash.

    To flash:
    sfh_OMAPL138.exe -flashType SPI_MEM -targetType OMAPL138 -flash_noubl u-boot.ais -p COM1

    Here is the log:

    U-Boot SPL 2015.04 (Apr 23 2015 - 15:29:00)

    U-Boot 2015.04 (Apr 23 2015 - 15:29:00)

    I2C: ready
    DRAM: 64 MiB
    WARNING: Caches not enabled
    MMC: davinci: 0
    SF: Detected M25P64 with page size 256 Bytes, erase size 64 KiB, total 8 MiB
    *** Warning - bad CRC, using default environment

    In: serial
    Out: serial
    Err: serial
    SF: Detected M25P64 with page size 256 Bytes, erase size 64 KiB, total 8 MiB
    Warning: Invalid MAC address read from SPI flash
    Net: DaVinci-EMAC
    Error: DaVinci-EMAC address not set.

    U-Boot >
    U-Boot >
    U-Boot >
  • 0 in reply to Titusrathinaraj Stalin
    TI__Guru** 116100 points
    Hi,

    I flashed both binaries: u-boot.ais and u-boot.bin through sfh_omap-l138.exe tool.

    The storage of SPI flash on custom board is 32Mb,which is half of the EVM board's SPI flash. BUt it's enough to contain both binaries.

    You should not flash "u-boot.bin" and "u-boot.ais" file into SPI flash.
    You have to flash "u-boot.ais" file alone.
    u-boot.bin is the u-boot image whereas u-boot.ais file is the same u-boot binary image with AIS headers for booting purpose.
  • 0 in reply to Titusrathinaraj Stalin
    Intellectual 275 points
    Thanks ! I thought u-boot.ais just act as UBL,and u-boot.bin as APP.
    It works,I flash u-boot.ais alone!
    thanks!
  • 0 in reply to zhongfeng chen
    TI__Guru** 116100 points
    Sounds good.
    Thanks for your update.