Project

General

Profile

Double boot u-Boot

Added by Oleh Mela over 1 year ago

Hi,

I run myfile.out on the MityDSP-L138 (L138-DX-225-RI) module (not MityDSP-L138F). Linux not use (according to DSP Quick Start). myfile.out is compiled in CCS and works fine. At startup (according to Autoload DSP during boot from SPI NOR) there is a double launch of the u-Boot, and then myfile.out is functioning fine. There was no such problem on the MityDSP-L138F module.
Why does this occur? Is it possible to avoid double boot?

OMAP-L138/AM-1808/AM-1810 initialization passed! <---------------- Power on (first boot)
Configuring 128MB mDDR
Booting TI User Boot Loader
UBL Version: 1.65:2.28.1 BuiltJul 11 2011 12:49:53
UBL Flashtype: SPI
Starting SPI Memory Copy...
Valid magicnum, 0x55424CBB, found at offset 0x00010000.
DONE
Jumping to entry point at 0xC1080000.

U-Boot 2009.11 (Jan 13 2014 - 11:14:02)

I2C: ready
DRAM: 128 MB
NAND: 256 MiB
MMC: davinci: 0
In: serial
Out: serial
Err: serial
ARM Clock : 300000000 Hz
DDR Clock : 150000000 Hz
EMIFA CLock : 100000000 Hz
DSP Clock : 300000000 Hz
ASYNC3 Clock : 150000000 Hz
Enet config : 2
MMC 0 Enable : 0
Resetting ethernet phy
Net: No ETH PHY detected!!!

Hit any key to stop autoboot: 0
8192 KiB M25P64 at 0:0 is now current device
Loading coff data from address 0xc0700000
... loading 512 bytes to address 0xc62f7c00
... loading 21888 bytes to address 0xc62de200
... loading 294784 bytes to address 0xc628e280
... loading 19540 bytes to address 0xc62e8a68
... loading 1284 bytes to address 0xc62f6b20
... loading 124 bytes to address 0xc62f8360
... loading 1952 bytes to address 0xc62f58e0
... loading 12 bytes to address 0xc62f7af4
... loading 21218 bytes to address 0xc62e3780
... loading 4 bytes to address 0xc628e27c
... loading 512 bytes to address 0xc62f7e00
... loading 24 bytes to address 0xc62f8578
... loading 16 bytes to address 0xc628e26c
... loading 1984 bytes to address 0x11808800
Starting DSP at address 0xc62f5e60

OMAP-L138/AM-1808/AM-1810 initialization passed! <--------------Second boot
Configuring 128MB mDDR
Booting TI User Boot Loader
UBL Version: 1.65:2.28.1 BuiltJul 11 2011 12:49:53
UBL Flashtype: SPI
Starting SPI Memory Copy...
Valid magicnum, 0x55424CBB, found at offset 0x00010000.
DONE
Jumping to entry point at 0xC1080000.

U-Boot 2009.11 (Jan 13 2014 - 11:14:02)

I2C: ready
DRAM: 128 MB
NAND: 256 MiB
MMC: davinci: 0
In: serial
Out: serial
Err: serial
ARM Clock : 300000000 Hz
DDR Clock : 150000000 Hz
EMIFA CLock : 100000000 Hz
DSP Clock : 300000000 Hz
ASYNC3 Clock : 150000000 Hz
Enet config : 2
MMC 0 Enable : 0
Resetting ethernet phy
Net: No ETH PHY detected!!!

Hit any key to stop autoboot: 0
8192 KiB M25P64 at 0:0 is now current device
Loading coff data from address 0xc0700000
... loading 512 bytes to address 0xc62f7c00
... loading 21888 bytes to address 0xc62de200
... loading 294784 bytes to address 0xc628e280
... loading 19540 bytes to address 0xc62e8a68
... loading 1284 bytes to address 0xc62f6b20
... loading 124 bytes to address 0xc62f8360
... loading 1952 bytes to address 0xc62f58e0
... loading 12 bytes to address 0xc62f7af4
... loading 21218 bytes to address 0xc62e3780
... loading 4 bytes to address 0xc628e27c
... loading 512 bytes to address 0xc62f7e00
... loading 24 bytes to address 0xc62f8578
... loading 16 bytes to address 0xc628e26c
... loading 1984 bytes to address 0x11808800
Starting DSP at address 0xc62f5e60 <----------------- Fine working
U-Boot >


Replies (7)

RE: Double boot u-Boot - Added by Jonathan Cormier over 1 year ago

Oleh,

Could you provide your u-boot environment? printenv

Does this processor reset happen when the DSP program isn't automatically loaded? Does it happen if you try to load a simple hello world dsp program?

RE: Double boot u-Boot - Added by Oleh Mela over 1 year ago

U-Boot > printenv
bootargs=mem=96M console=ttyS1,115200n8 root=/dev/mtdblock0 rw rootwait
bootdelay=3
baudrate=115200
bootfile="uImage"
flashuboot=tftp 0xc0700000 mityomap/u-boot-ubl.bin; sf probe 0; sf erase 0x10000 0x80000; sf write 0xc0700000 0x10000 ${filesize}
flashkernel=tftp 0xc0700000 mityomap/uImage; sf probe 0; sf erase 0x100000 0x280000; sf write 0xc0700000 0x100000 ${filesize}
flashubl=tftp 0xc0700000 mityomap/UBL_SPI_MEM.ais; sf probe 0; sf erase 0 0x10000; sf write 0xc0700000 0 0x10000
flashrootfs=tftp 0xc2000000 mityomap/mityomap-base-mityomapl138.jffs2; nand erase 0 0x08000000; nand write.jffs2 0xc2000000 0 ${filesize}
serverip=10.0.0.23
autoload=no
mtdids=nand0=nand
mtdparts=mtdparts=nand:128M(rootfs),-(userfs)
bootargsbase=mem=96M console=ttyS1,115200n8
flashargs=setenv bootargs ${bootargsbase} ${mtdparts} root=/dev/mtdblock0 rw,noatime rootfstype=jffs2
filesize=1732CC
bootcmd=sf probe 0; sf read 0xc0700000 0x100000 0x300000;bootdsp 0xc0700000;
stdin=serial
stdout=serial
stderr=serial
ethaddr=00:50:c2:fc:6c:cf
ver=U-Boot 2009.11 (Jan 13 2014 - 11:14:02)

Environment size: 1070/65532 bytes

Does this processor reset happen when the DSP program isn't automatically loaded?

No.

Does it happen if you try to load a simple hello world dsp program?

No, with simple hello world dsp program working fine.

RE: Double boot u-Boot - Added by Oleh Mela over 1 year ago

Jonathan,
with simple hello world dsp program following is:

OMAP-L138/AM-1808/AM-1810 initialization passed!
Configuring 128MB mDDR
Booting TI User Boot Loader
UBL Version: 1.65:2.28.1 BuiltJul 11 2011 12:49:53
UBL Flashtype: SPI
Starting SPI Memory Copy...
Valid magicnum, 0x55424CBB, found at offset 0x00010000.
DONE
Jumping to entry point at 0xC1080000.
OMAP-L138/AM-1808/AM-1810 initialization passed!
Configuring 128MB mDDR
Booting TI User Boot Loader
UBL Version: 1.65:2.28.1 BuiltJul 11 2011 12:49:53
UBL Flashtype: SPI
Starting SPI Memory Copy...
Valid magicnum, 0x55424CBB, found at offset 0x00010000.
DONE
Jumping to entry point at 0xC1080000.

U-Boot 2009.11 (Jan 13 2014 - 11:14:02)

I2C: ready
DRAM: 128 MB
NAND: 256 MiB
MMC: davinci: 0
In: serial
Out: serial
Err: serial
ARM Clock : 300000000 Hz
DDR Clock : 150000000 Hz
EMIFA CLock : 100000000 Hz
DSP Clock : 300000000 Hz
ASYNC3 Clock : 150000000 Hz
Enet config : 2
MMC 0 Enable : 0
Resetting ethernet phy
Net: No ETH PHY detected!!!

Hit any key to stop autoboot: 0
8192 KiB M25P64 at 0:0 is now current device
Loading coff data from address 0xc0700000
... loading 512 bytes to address 0x11811800
... loading 17152 bytes to address 0x118058a0
... loading 12 bytes to address 0x1180f7f4
... loading 22688 bytes to address 0x11800000
... loading 4004 bytes to address 0x1180dfc0
... loading 76 bytes to address 0x1180f798
... loading 1376 bytes to address 0x11810000
... loading 12 bytes to address 0x118117f4
... loading 4032 bytes to address 0x1180d000
... loading 905 bytes to address 0x11810e78
... loading 4 bytes to address 0x1180ef64
... loading 512 bytes to address 0x11811588
... loading 48 bytes to address 0x118117c4
... loading 48 bytes to address 0x11811ce8
Starting DSP at address 0x11810380
U-Boot >

RE: Double boot u-Boot - Added by Jonathan Cormier over 1 year ago

That is very strange. Could you comment out pieces of your code until it starts working again? To see if you can determine a section of the code that causes this and we can look at it to see if we can determine what is going wrong.

RE: Double boot u-Boot - Added by Oleh Mela over 1 year ago

Jonathan,
Could be my problem connected with to the that there is no pull-up on SPI1 on the own carrier board?

Thanks

RE: Double boot u-Boot - Added by Jonathan Cormier over 1 year ago

Oleh Mela wrote:

Jonathan,
Could be my problem connected with to the that there is no pull-up on SPI1 on the own carrier board?

Thanks

Looking at our devkit, we don't put any pull-ups on the spi1 pins. https://support.criticallink.com/redmine/attachments/download/15416/80-000268RI-3_SCH_RevC.PDF

RE: Double boot u-Boot - Added by Oleh Mela over 1 year ago

Thank Jonathan,

The problem is resolved. The problem was in hardware.

    (1-7/7)
    Add picture from clipboard (Maximum size: 500 MB)