Number of sectors (ignored in NOR) -> nothing.Pretty easy right? wrong!!! The right values are: Number of sectors (ignored in NOR)-> nothing.MTD device name -> /dev/mtd2 ("u-boot environment").Now we can fill in all the values we needed (that's what I thought) 0x00780000-0x20000000 : "File System"īut if we use the aproppiate kernel, in my case 2.6.33.7-0 with the onenand driver instead of the nand driver: mtd: partition "U-Boot Env" doesn't start on an erase block boundary - force read-only Creating 5 MTD partitions on "omap2-onenand": Through "dmesg" I could see this line indicating something was wrong: Ok, so in order to get all this information the easyest thing is to read it from dmesg or from /proc/mtdĪll my initial confusion comes from using an incorrect kernel, my first tries where with 2.6.28.10 and the driver used to read mtd was NAND, in the kernel configuration file I only had : Here comes the confusionįinding out the correct values for fw_env.config The next thing we will need is the fw_env.config file with the appropiate settings for our board. This will give us fw_printenv, in order to get fw_setenv we just have to change the name of the file. h file as it says in the tools/env/README file): In order to modify the uboot environment variables from userspace we will need a program called fw_setenv, we can compile this program ourselves from the u-boot sources, follow the instructions in this wiki page and then proceed to compile with (don't modify the. This is my first wiki page so please be benevolent with the formatting Tools needed This How-To is meant to be a starting point for people to learn how access to the uboot environment from userspace.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |