From: dtran11 <dt...@gm...> - 2010-09-20 20:29:37
|
Is there a way to change u-boots environment variables, specifically "mpurate" in linux? Some of the expansion boards don't have a console port so this will be handy for me. I am using the overo earth. thanks. -- View this message in context: http://old.nabble.com/change-uboot-environment-variables-in-linux-tp29763351p29763351.html Sent from the Gumstix mailing list archive at Nabble.com. |
From: dtran11 <dt...@gm...> - 2010-09-20 20:31:07
|
I believe u-boot parameters are located in mtd2. I tried to mount it in linux but I don't know the filesystem type. -- View this message in context: http://old.nabble.com/change-uboot-environment-variables-in-linux-tp29763351p29763363.html Sent from the Gumstix mailing list archive at Nabble.com. |
From: Dave H. <dhy...@gm...> - 2010-09-20 20:48:35
|
On Mon, Sep 20, 2010 at 1:29 PM, dtran11 <dt...@gm...> wrote: > > Is there a way to change u-boots environment variables, specifically > "mpurate" in linux? Some of the expansion boards don't have a console port > so this will be handy for me. I am using the overo earth. uboot has a couple of utilities that can be run from linux. See this page for more information <http://elinux.org/U-boot_environment_variables_in_linux> -- Dave Hylands Shuswap, BC, Canada http://www.DaveHylands.com/ |
From: dtran11 <dt...@gm...> - 2010-09-20 21:32:33
|
Thanks for the help. This is what I get when doing fw_printenv: Warning: Bad CRC, using default environment bootcmd=bootp; setenv bootargs root=/dev/nfs nfsroot=${serverip}:${rootpath} ip=${ipaddr}:${serverip}:${gatewayip}:${netmask}:${hostname}::off; bootm bootdelay=5 baudrate=115200 Have you seen this error before? -- View this message in context: http://old.nabble.com/change-uboot-environment-variables-in-linux-tp29763351p29763959.html Sent from the Gumstix mailing list archive at Nabble.com. |
From: J. L. <vwy...@gm...> - 2010-09-20 21:36:27
|
On Mon, Sep 20, 2010 at 2:32 PM, dtran11 <dt...@gm...> wrote: > > Thanks for the help. > > This is what I get when doing fw_printenv: > > > > Warning: Bad CRC, using default environment Once you set some variables this should go away, does for me. When I have a clean uboot I get the message you saw then once putting in my own variables it goes away. I think its just a warning that nothings set. > bootcmd=bootp; setenv bootargs root=/dev/nfs nfsroot=${serverip}:${rootpath} > ip=${ipaddr}:${serverip}:${gatewayip}:${netmask}:${hostname}::off; bootm > bootdelay=5 > baudrate=115200 > > > > Have you seen this error before? > -- > View this message in context: http://old.nabble.com/change-uboot-environment-variables-in-linux-tp29763351p29763959.html > Sent from the Gumstix mailing list archive at Nabble.com. > > > ------------------------------------------------------------------------------ > Start uncovering the many advantages of virtual appliances > and start using them to simplify application deployment and > accelerate your shift to cloud computing. > http://p.sf.net/sfu/novell-sfdev2dev > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > |
From: Dave H. <dhy...@gm...> - 2010-09-20 22:42:52
|
Hi, On Mon, Sep 20, 2010 at 2:36 PM, J. L. <vwy...@gm...> wrote: > On Mon, Sep 20, 2010 at 2:32 PM, dtran11 <dt...@gm...> wrote: >> >> Thanks for the help. >> >> This is what I get when doing fw_printenv: >> >> >> >> Warning: Bad CRC, using default environment > > Once you set some variables this should go away, does for me. When I > have a clean uboot I get the message you saw then once putting in my > own variables it goes away. I think its just a warning that nothings > set. Yeah - I'd recommend that you drop into uboot and do: saveenv once. Then you should no longer see those messages. You don't even need to add any variables, just save the current ones so that the current variables and the CRC get saved. -- Dave Hylands Shuswap, BC, Canada http://www.DaveHylands.com/ |
From: Victor A. <vi...@cy...> - 2010-09-21 15:08:00
|
Hello. I have done that, from u-boot, saveenv. Then the warning message disapear, and from the linux you can list all u-boot variables: root@overo:~# fw_printenv bootcmd=if mmc init; 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 mpurate=500 vram=12M dvimode=1024x768MR-16@60 defaultdisplay=dvi mmcroot=/dev/mmcblk0p2 rw mmcrootfstype=ext3 rootwait nandroot=/dev/mtdblock4 rw nandrootfstype=jffs2 mmcargs=setenv bootargs console=${console} mpurate=${mpurate} vram=${vram} omapfb.mode=dvi:${dvimode} omapfb.debug=y omapdss.def_disp=${defaultdisplay} root=${mmcroot} rootfstype=${mmcrootfstype} nandargs=setenv bootargs console=${console} mpurate=${mpurate} vram=${vram} omapfb.mode=dvi:${dvimode} omapfb.debug=y omapdss.def_disp=${defaultdisplay} root=${nandroot} rootfstype=${nandrootfstype} loadbootscript=fatload mmc 0 ${loadaddr} boot.scr bootscript=echo Running bootscript from mmc ...; source ${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#=1ad600040000000004035c141801e006 But If I try to set a new value of 'bootdelay', for example, I get the follow messages: root@overo:~# fw_printenv bootdelay bootdelay=5 root@overo:~# fw_setenv bootdelay 4 Unlocking flash... Done Erasing old environment... Done Writing environment to /dev/mtd2... CRC write error on /dev/mtd2: Invalid argument Error: can't write fw_env to flash Thanks! Víctor Andrés |
From: dtran11 <dt...@gm...> - 2010-09-21 15:45:41
|
I did a saveenv in u-boot and I still get the crc error in linux. Do I need to recompile these uboot tools? Víctor Andrés wrote: > > Hello. > > I have done that, from u-boot, saveenv. Then the warning message disapear, > and from the linux you can list all u-boot variables: > root@overo:~# fw_printenv > bootcmd=if mmc init; 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 > mpurate=500 > vram=12M > dvimode=1024x768MR-16@60 > defaultdisplay=dvi > mmcroot=/dev/mmcblk0p2 rw > mmcrootfstype=ext3 rootwait > nandroot=/dev/mtdblock4 rw > nandrootfstype=jffs2 > mmcargs=setenv bootargs console=${console} mpurate=${mpurate} vram=${vram} > omapfb.mode=dvi:${dvimode} omapfb.debug=y > omapdss.def_disp=${defaultdisplay} > root=${mmcroot} rootfstype=${mmcrootfstype} > nandargs=setenv bootargs console=${console} mpurate=${mpurate} > vram=${vram} > omapfb.mode=dvi:${dvimode} omapfb.debug=y > omapdss.def_disp=${defaultdisplay} > root=${nandroot} rootfstype=${nandrootfstype} > loadbootscript=fatload mmc 0 ${loadaddr} boot.scr > bootscript=echo Running bootscript from mmc ...; source ${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#=1ad600040000000004035c141801e006 > But If I try to set a new value of 'bootdelay', for example, I get the > follow messages: > root@overo:~# fw_printenv bootdelay > bootdelay=5 > root@overo:~# fw_setenv bootdelay 4 > Unlocking flash... > Done > Erasing old environment... > Done > Writing environment to /dev/mtd2... > CRC write error on /dev/mtd2: Invalid argument > Error: can't write fw_env to flash > > > Thanks! > Víctor Andrés > > > > ------------------------------------------------------------------------------ > Start uncovering the many advantages of virtual appliances > and start using them to simplify application deployment and > accelerate your shift to cloud computing. > http://p.sf.net/sfu/novell-sfdev2dev > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > > -- View this message in context: http://old.nabble.com/change-uboot-environment-variables-in-linux-tp29763351p29770720.html Sent from the Gumstix mailing list archive at Nabble.com. |
From: dtran11 <dt...@gm...> - 2010-09-21 16:22:02
|
Does it have to do anything with the fw_env.config file? This is what I have in my fw_env.config: /dev/mtd1 0x0000 0x4000 0x4000 /dev/mtd2 0x0000 0x4000 0x4000 -- View this message in context: http://old.nabble.com/change-uboot-environment-variables-in-linux-tp29763351p29771095.html Sent from the Gumstix mailing list archive at Nabble.com. |
From: Victor A. <vi...@cy...> - 2010-09-21 17:11:44
|
This is my fw_env.config file # MTD device name Device offset Env. size Flash sector size Number of sectors /dev/mtd2 0x0000 0x20000 0x20000 And the /proc/mtd cat /proc/mtd dev: size erasesize name mtd0: 00080000 00020000 "xloader" mtd1: 001c0000 00020000 "uboot" mtd2: 00040000 00020000 "uboot environment" mtd3: 00400000 00020000 "linux" mtd4: 0f980000 00020000 "rootfs" ----- Original Message ----- From: "dtran11" <dt...@gm...> To: <gum...@li...> Sent: Tuesday, September 21, 2010 6:21 PM Subject: Re: [Gumstix-users] change uboot environment variables in linux > > Does it have to do anything with the fw_env.config file? > > This is what I have in my fw_env.config: > > /dev/mtd1 0x0000 0x4000 0x4000 > /dev/mtd2 0x0000 0x4000 0x4000 > -- > View this message in context: > http://old.nabble.com/change-uboot-environment-variables-in-linux-tp29763351p29771095.html > Sent from the Gumstix mailing list archive at Nabble.com. > > > ------------------------------------------------------------------------------ > Start uncovering the many advantages of virtual appliances > and start using them to simplify application deployment and > accelerate your shift to cloud computing. > http://p.sf.net/sfu/novell-sfdev2dev > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users |
From: Victor A. <vi...@cy...> - 2010-09-21 16:21:09
|
The U-boot version I'm using is U-Boot 2010.06 (Sep 16 2010 - 18:12:51) I compiled a complete image last week. ----- Original Message ----- From: "dtran11" <dt...@gm...> To: <gum...@li...> Sent: Tuesday, September 21, 2010 5:45 PM Subject: Re: [Gumstix-users] change uboot environment variables in linux > > I did a saveenv in u-boot and I still get the crc error in linux. Do I > need > to recompile these uboot tools? > > > Víctor Andrés wrote: >> >> Hello. >> >> I have done that, from u-boot, saveenv. Then the warning message >> disapear, >> and from the linux you can list all u-boot variables: >> root@overo:~# fw_printenv >> bootcmd=if mmc init; 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 >> mpurate=500 >> vram=12M >> dvimode=1024x768MR-16@60 >> defaultdisplay=dvi >> mmcroot=/dev/mmcblk0p2 rw >> mmcrootfstype=ext3 rootwait >> nandroot=/dev/mtdblock4 rw >> nandrootfstype=jffs2 >> mmcargs=setenv bootargs console=${console} mpurate=${mpurate} >> vram=${vram} >> omapfb.mode=dvi:${dvimode} omapfb.debug=y >> omapdss.def_disp=${defaultdisplay} >> root=${mmcroot} rootfstype=${mmcrootfstype} >> nandargs=setenv bootargs console=${console} mpurate=${mpurate} >> vram=${vram} >> omapfb.mode=dvi:${dvimode} omapfb.debug=y >> omapdss.def_disp=${defaultdisplay} >> root=${nandroot} rootfstype=${nandrootfstype} >> loadbootscript=fatload mmc 0 ${loadaddr} boot.scr >> bootscript=echo Running bootscript from mmc ...; source ${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#=1ad600040000000004035c141801e006 >> But If I try to set a new value of 'bootdelay', for example, I get the >> follow messages: >> root@overo:~# fw_printenv bootdelay >> bootdelay=5 >> root@overo:~# fw_setenv bootdelay 4 >> Unlocking flash... >> Done >> Erasing old environment... >> Done >> Writing environment to /dev/mtd2... >> CRC write error on /dev/mtd2: Invalid argument >> Error: can't write fw_env to flash >> >> >> Thanks! >> Víctor Andrés >> >> >> >> ------------------------------------------------------------------------------ >> Start uncovering the many advantages of virtual appliances >> and start using them to simplify application deployment and >> accelerate your shift to cloud computing. >> http://p.sf.net/sfu/novell-sfdev2dev >> _______________________________________________ >> gumstix-users mailing list >> gum...@li... >> https://lists.sourceforge.net/lists/listinfo/gumstix-users >> >> > > -- > View this message in context: > http://old.nabble.com/change-uboot-environment-variables-in-linux-tp29763351p29770720.html > Sent from the Gumstix mailing list archive at Nabble.com. > > > ------------------------------------------------------------------------------ > Start uncovering the many advantages of virtual appliances > and start using them to simplify application deployment and > accelerate your shift to cloud computing. > http://p.sf.net/sfu/novell-sfdev2dev > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > |