Re: [Gumstix-users] Password at login using putty on Overo Fire

[Dave H. <dhy...@gm...>]

Hi Titusgroan,

> Typing printenv whilst in U-Boot results in the following output:
>
> Overo # printenv
> bootcmd=if mmcinit; then if run loadbootscript; then run bootscript; else if
> run loaduimage; then run mmcboot; else run nandboot; fi; fi; else run
> nandboot; fi
> bootdelay=5
> baudrate=115200
> loadaddr=0x82000000
> console=ttyS2,115200n8
> vram=12M
> dvimode=1024x768MR-16@60
> defaultdisplay=dvi
> mmcargs=setenv bootargs console=${console} vram=${vram}
> omapfb.mode=dvi:${dvimode} omapfb.debug=y omapdss.def_disp=${defaultdisplay}
> root=/dev/mmcblk0p2 rw rootfstype=ext3 rootwait
> nandargs=setenv bootargs console=${console} vram=${vram}
> omapfb.mode=dvi:${dvimode} omapfb.debug=y omapdss.def_disp=${defaultdisplay}
> root=/dev/mtdblock4 rw rootfstype=jffs2
> loadbootscript=fatload mmc 0 ${loadaddr} boot.scr
> bootscript=echo Running bootscript from mmc ...; autoscr ${loadaddr}
> loaduimage=fatload mmc 0 ${loadaddr} uImage
> mmcboot=echo Booting from mmc ...; run mmcargs; bootm ${loadaddr}
> nandboot=echo Booting from nand ...; run nandargs; nand read ${loadaddr}
> 280000 400000; bootm ${loadaddr}
> stdin=serial
> stdout=serial
> stderr=serial
> dieid#=132400040000000004032d460c013009
>
> Environment size: 1055/131068 bytes
>
> This doesn't quite correlate with what is presented in the link that you
> sent me. Does it matter that those instructions assume a non-overo Gumstix
> is being used? I boot from a microSD card so I'm guessing that I have to
> change:
>
> mmcargs=setenv bootargs console=${console} vram=${vram}
> omapfb.mode=dvi:${dvimode} omapfb.debug=y omapdss.def_disp=${defaultdisplay}
> root=/dev/mmcblk0p2 rw rootfstype=ext3 rootwait
>
> I'm confused, if I type setenv bootargs... does that change bootargs for
> both mmcargs and nandargs?

Well, it depends on how you do things. bootcmd is the command that's
executed at boot time. Eventually, it winds up calling the bootm
command. Whatever bootargs is in effect at that time is what gets
used.

If you just set bootargs, then your change will be overwritten when
mmcargs is executed (because it sets bootargs). So with your current
environment, you'd want to modify mmargs to add the init=/bin/sh to
the end of the mmcargs.

I think you should also be able to do something like this:

setenv mmcargs ${mmcargs} init=/bin/sh
run mmcboot

No permanent change required.

-- 
Dave Hylands
Shuswap, BC, Canada
http://www.DaveHylands.com/