| 08:15 | flips | Still seems to me that most of the useful stuff I need is gone from the new wiki ... |
| 08:20 | jnettlet | flips, what are you looking for? |
| 08:27 | flips | Well, the Multi-booting page is gone ... the page I first downloaded the busybox.img that described a more manual setup than ignition.img, seems gone (I can't remember what was in the wiki or not) |
| 08:28 | flips | Tried getting multiboot working, so far get "Wrong Image Type for bootm command" |
| 08:28 | flips | So I need more understanding of u-boot, I guess |
| 08:38 | jnettlet | flips, you will probably need to write your own boot scripts for that. Our boot scripts are very focused on generically finding a bootable kernel and loading that. |
| 08:38 | jnettlet | but it will definitely take some u-boot knowledge. |
| 08:41 | flips | I followed steps/principles from the google cached version of the wiki Multi-booting, it seems to find the file(s), printenv shows the uEnv.txt content, but somehow I get the Wrong Image Type for bootm command |
| 08:42 | vpeter | flips: And what type of image you load with bootm? |
| 08:44 | flips | The one that does boot, vmlinuz file in Debian/Armbian is "Linux kernel ARM boot executable zImage (little-endian)", and so is KERNEL from OpenELEC, so I'm trying to boot that |
| 08:45 | flips | (so I can make a shell-script to symlink-switch between the boot.scr/zImage/boot.cmd/uEnv.txt files) |
| 08:47 | flips | boot the u-boot.img and boot.scr seems different: http://pastebin.com/LkZ9ghQZ |
| 08:56 | vpeter | zImage must be booted with bootz. |
| 08:59 | flips | the openelec uEnv.txt doesn't have a specific boot command (and there's no boot.cmd file), maybe the u-boot version they use specifically tries bootz automatically? |
| 09:02 | vpeter | Yes, it uses correct boot cmd. |
| 09:23 | flips | URL to u-boot documentation? (A bit more in-depth than http://wiki.solid-run.com/doku.php?id=products:imx6:software:development:u-boot&s[]=boot ) |
| 09:53 | vpeter | flips: ok, so what exactly are you trying to achieve? Boot some image? |
| 10:20 | flips | vpeter: I'm trying to setup multiboot, have openelec run from mmcblk0p2, install debian jessie in mmcblk0p1 ... or something like that :) |
| 10:24 | vpeter | flips: Any url how to achieve that? Using HDMI menu to select system? |
| 10:33 | flips | vpeter: just shell for changing symlinks, following this (used to be on the wiki): http://webcache.googleusercontent.com/search?q=cache:O10XaUCGZIIJ:wiki.solid-run.com/index.php%3Ftitle%3DMulti-booting+&cd=1&hl=en&ct=clnk&gl=no&client=ubuntu |
| 10:41 | vpeter | Ok, so you run one system, execute program to switch to another system and so on. |
| 10:42 | flips | yep, that's the plan :) |
| 10:43 | vpeter | So you just need correct boot.scr for each system. |
| 10:44 | vpeter | Set correct root and and boot command - bootm for uImage and bootz for zImage. |
| 10:45 | flips | do I need to rebuild boot.scr for something/somehow? |
| 10:45 | flips | my last try resultet in "Bad image" ... ;) |
| 10:48 | vpeter | Yes, I think you will need to build new script for every system. |
| 10:48 | vpeter | because your root is different between them. |
| 10:52 | flips | so, if I don't have the kernel source and build stuff, I can't do that? (I didn't find info on building boot.scr) |
| 10:54 | vpeter | No, boot.scr can be manually build. No kernel needed: https://wiki.linaro.org/Resources/HowTo/boot.scr |
| 10:54 | vpeter | You write text file and "compile" it. |
| 12:23 | flips | well, I get no text file from this: dd bs=1 skip=72 if=/mnt/boot.scr of=/tmp/boot.script |
| 12:31 | vpeter | flips: mkimage -A arm -T script -C none -n "My Boot.scr" -d boot.script boot.scr |
| 12:32 | vpeter | boot.script is input text file, boot.scr is output script file to be used with u-boot. |
| 12:33 | flips | I understand that, but I need that text file, and the URL you gave claim I get it by that dd command |
| 12:39 | vpeter | You have orginal file with distribution you want to install. Or you just wrote something by hand. |
| 12:42 | flips | and then I need more info on how to write by hand, as I don't see any text file :) |
| 13:11 | flips | What would also be cool, was to create a boot.scr that could boot off the network/my server |
| 13:14 | jnettlet | flips that is very easy. |
| 13:14 | jnettlet | standard u-boot docs will apply. For the built in scripts you can load the kernel just by specifying a SERVERIP uenv variable |
| 13:16 | bencoh | .41 |
| 13:16 | bencoh | woops |
| 13:22 | flips | Is there a main u-boot authoritative page, or just many forks? (Also the various distros I've tested seem to use their own custom versions) |
| 13:52 | jnettlet | flips, u-boot tends to get forked because the maintainers aren't the most responsive groups. So individual board manufacturers fork u-boot and get it running for their board. Then u-boot doesn't like it, or just doesn't have time to review it. By the time someone gets an answer it is 6-8 months later and hardware manufacturers have no interest in putting dev time back into their u-boot which is already working as intended. |
| 13:53 | jnettlet | it would be great if this were not the case, but that is the ugly truth of it all. |
| 13:55 | flips | jnettlet: what site would you recommend for general documentation? (Like what files it will look for on tftp etc) |
| 13:58 | jnettlet | flips, sorry no specific sites...google is your best friend. |
| 14:00 | vpeter | flips: For example http://blackfin.uclinux.org/doku.php?id=bootloaders:u-boot:tftp_loading_files |
| 14:01 | vpeter | download files over tftp to some locations and boot. |
| 14:01 | vpeter | Or using nfs boot. |
| 14:01 | vpeter | http://www.denx.de/wiki/view/DULG/LinuxNfsRoot |
| 14:02 | vpeter | main page http://www.denx.de/wiki/view/DULG/Manual |
| 14:02 | vpeter | Check section 7 |
| 14:03 | flips | Where's the Helping Grandma understand U-boot book when you need it? ;) |
| 14:05 | vpeter | I think Grandma needs to learn as you do :) |
| 14:05 | vpeter | With trying. |
| 14:06 | flips | hehe ... How do I know the correct load address? |
| 14:06 | vpeter | loadaddr=10800000 fdt_addr=0x12000000 |
| 14:07 | flips | (I've seen so many different examples, none explained that part, like one Debian used 0x000000000) |
| 14:08 | vpeter | I don't think it was 0. |
| 14:10 | flips | well, it was in printenv, but that was probably when something went horribly wrong in my experiments ;) |
| 14:13 | flips | but ... how/where do you find those number, like in "tftp 0x1000 u-boot.bin" ... are 0x10800000 and 0x12000000 and 0x1000 hardcoded in the firmware, so the u-boot will always load from 0x1000 etc? |
| 14:23 | vpeter | I think printenv will already show you that. |
| 14:24 | jnettlet | flips, those addresses can be very generic, or very much hardware specific. There are a number of factors that could determine where you put things in memory. |
| 14:33 | flips | btw, so nice to have the ttyUSB0 interface available :) |
| 18:18 | vpeter | I'm giving up on LVDS. Tried everything what I can think of and still nothing. Time to move on :( |
| 19:00 | jnettlet | vpeter, i will be getting an lvds board to test soon. We can work from there afterwards. Did you enable debugging for all the mxc fb components? |
| 19:14 | vpeter | Honestly I don't even know anymore what I tried and what not. Little disappointed on myself :( |
| 19:14 | vpeter | SeemsI will just stay at userspace from now on. |
| 19:21 | jnettlet | vpeter, no worries. we all bang our heads against a problem. Sometimes you look too closely and miss the obvious things |
| 19:21 | jnettlet | been there don't that |
| 19:26 | vpeter | That's true. But seems kernel stuff is only for few people. No wonder there is so many forks for almost same things. |
| 19:26 | vpeter | Anyway, I really appreciate your work (and from others). |
| 22:11 | flips | btw: I don't get wifi to work in the ignition image |