Posted by hans2 on Feb 28, 2016; 3:50pm
URL: https://itus.accessinnov.com/Help-with-boot-process-tp192p199.html

Hi Roadrunner

i am making dumps from my bootprocess. I did this the following way:

1) reboot shield
2) interrupt the boot process when Shield mentions "Hit any key to stop autoboot"
3) use commands like printenv mmcinfo

Bootloader stage 1:

Octeon sff7000# mmcinfo
MMC Device 0 not found
no mmc device at slot 0
<raw>
Octeon sff7000# version
<raw>
U-Boot 2013.07 (Development build, svnversion: u-boot:exported, exec:) (Build time: Mar 05 2015 - 12:15:47)
mips64-octeon-linux-gnu-gcc (Cavium Inc. Version: SDK_3_1_0 build 32) 4.7.0
GNU ld (Cavium Inc. Version: SDK_3_1_0 build 32) 2.23.52
Octeon sff7000# bdinfo
boot_params = 0x4FBF5E70
memstart    = 0x80000000
memsize     = 0x40000000
flashstart  = 0x00000000
flashsize   = 0x00000000
flashoffset = 0x00000000
ethaddr     = (not set)
ip_addr     = <NULL>
baudrate    = 115200 bps

Octeon sff7000# grepenv

boardname=sff7000
bootcmd=bootstage3
bootdelay=3
loadaddr=0x20000000
numcores=2
octeon_failsafe_mode=0
octeon_ram_mode=0
octeon_stage3_bootloader=u-boot-octeon_rhino_itus7x.bin
stderr=serial
stdin=serial
stdout=serial
ver=U-Boot 2013.07 (Development build, svnversion: u-boot:exported, exec:) (Build time: Mar 05 2015 - 12:15:47)

This clearly shows that stage1 will look for u-boot-octeon_rhino_itus7x.bin to load next as stage 3 (cmd: bootstage3)

In stage3:

Octeon cust_private_rhino_itus7x(ram)# printenv
do_env_print ......
autoload=n
baudrate=115200
bf=bootoct $(flash_unused_addr) forceboot numcores=$(numcores)
boardname=cust_private_rhino_itus7x
bootcmd=run image_run
bootdelay=2
bridge=mmc dev 1;fatload mmc 1 $(loadaddr) brigdeImage;bootoctlinux $(loadaddr) mem=0 numcores=2
burn_app=erase $(flash_unused_addr) +$(filesize);cp.b $(fileaddr) $(flash_unused_addr) $(filesize)
dram_size_mbytes=1024
eth1addr=XX:XX:XX:XX:XX:XX
eth2addr=XX:XX:XX:XX:XX:XX
eth3addr=XX:XX:XX:XX:XX:XX
ethact=octeth0
ethaddr=XX:XX:XX:XX:XX:XX
gateway=mmc dev 1;fatload mmc 1 $(loadaddr) gatewayImage;bootoctlinux $(loadaddr) mem=0 numcores=2
image_run=mmc dev 1;fatload mmc 1 $(loadaddr) ItusbridgeImage;bootoctlinux $(loadaddr) mem=0 numcores=2 serial#=$(serial#)
linux_mmc=fatload mmc 1 $(loadaddr) vmlinux.64;bootoctlinux $(loadaddr) mem=0 numcores=2
loadaddr=0x20000000
ls=fatls mmc 1
numcores=2
octeon_failsafe_mode=0
octeon_ram_mode=1
router=mmc dev 1; fatload mmc 1 $(loadaddr) routerImage;bootoctlinux $(loadaddr) mem=0 numcores=2
serial#=XXXXXXXXXXXXXXXXXX
stderr=serial
stdin=serial
stdout=serial
ver=U-Boot 2013.07 (Development build, svnversion: u-boot:exported, exec:) (Build time: Apr 28 2015 - 15:37:10)

Environment size: 1233/8188 bytes

I am running my sandbox in BRIDGE mode. That explains "image_run=mmc dev 1;fatload mmc 1 $(loadaddr) ItusbridgeImage;bootoctlinux $(loadaddr) mem=0 numcores=2 serial#=$(serial#)"

but it could also be that in some cases it is still loading the bridgeImage/gatewayImage/RouterImage, based on

bridge=mmc dev 1;fatload mmc 1 $(loadaddr) brigdeImage;bootoctlinux $(loadaddr) mem=0 numcores=2
gateway=mmc dev 1;fatload mmc 1 $(loadaddr) gatewayImage;bootoctlinux $(loadaddr) mem=0 numcores=2
router=mmc dev 1; fatload mmc 1 $(loadaddr) routerImage;bootoctlinux $(loadaddr) mem=0 numcores=2