| 16:34 | bartolo | hi, I'm trying to boot debian on the cubox-i. I've this boot.scr http://pastebin.com/V9e8pSLt but it fails on this command " && load ${device} ${partition} ${ramdiskaddr} ${pathprefix}initrd.img-${kvers}". By debugging it i've noticed that ramdiskaddr is undefined, but i have no idea on how to find the correct value |
| 16:34 | bartolo | (debian jessie) |
| 16:38 | Catwich | bartolo |
| 16:38 | Catwich | you probably dont want to use a ramdisk |
| 16:39 | Catwich | I happen to know you can omit the ramdiskaddr, by replacing it with teh character '-' |
| 16:39 | Catwich | I have no idea where this is documented though |
| 16:39 | Catwich | but why use load |
| 16:39 | Catwich | and not bootz? |
| 16:39 | bartolo | Catwich: yes i've tried both using - and by leave it undefined but if fails |
| 16:40 | bartolo | with - it says that the address of the ramdisk is invalid |
| 16:40 | Catwich | try using bootz |
| 16:40 | bartolo | without it load ${device} ${partition} ${ramdiskaddr} ${pathprefix}initrd.img-${kvers} fails |
| 16:40 | Catwich | oh wait |
| 16:40 | Catwich | you want to laod the initrd? |
| 16:40 | Catwich | I really dont know a thing about load command |
| 16:40 | bartolo | dunno, it's the default for debian |
| 16:40 | Catwich | but here is how I write my boot.scr files: |
| 16:41 | Catwich | load kernel into memoery |
| 16:41 | Catwich | load initrd into memory |
| 16:41 | Catwich | load dtb into memory |
| 16:41 | Catwich | call bootz with all 3 addresses |
| 16:41 | bartolo | uhm maybe ramdiskaddr is the address of initrd |
| 16:41 | Catwich | I had a nice sample I linked here several times |
| 16:41 | Catwich | but no idea where it is |
| 16:41 | Catwich | ramdiskaddr is the address of the ramdisk, if you loaded it there |
| 16:41 | bartolo | by looking on how it is used |
| 16:41 | Catwich | usually |
| 16:41 | Catwich | and its porbbaly predefined |
| 16:42 | Catwich | that means, someone already figured a good address to load the initrd to |
| 16:42 | bartolo | yes but if you look at my boot.snr it is used in this way: load ${device} ${partition} ${ramdiskaddr} ${pathprefix}initrd.img-${kvers} |
| 16:42 | bartolo | and by default it is undefined |
| 16:42 | Catwich | then define it :) |
| 16:43 | bartolo | ehm with which value? |
| 16:43 | Catwich | xD |
| 16:43 | Catwich | I will look them up |
| 16:43 | Catwich | I good a few really good ones |
| 16:44 | Catwich | I even added code to opensuse to calculate it |
| 16:44 | Catwich | them* |
| 16:46 | Catwich | kerneladdr=0x10800100 |
| 16:47 | Catwich | fdtaddr=0x14700100 |
| 16:48 | Catwich | ramdiskaddr=0x14800100 |
| 16:48 | Catwich | basically, kerneladdr is a suggested default laod address for imx6 |
| 16:48 | Catwich | add 63MB space for kernel |
| 16:48 | Catwich | then load fdt |
| 16:49 | Catwich | add 1MB space for fdt |
| 16:49 | Catwich | then load ramdisk |
| 16:49 | bartolo | uhm i have loadaddr=0x10800000 fdtaddr=0x18000000 |
| 16:50 | Catwich | that leaves hiw much? 128MB space between loaddr and fdtaddr? |
| 16:50 | Catwich | (I am not good at reading hex, or calculating in head) |
| 16:50 | Catwich | anyway, the values I provided work perfectly |
| 16:50 | Catwich | and are used by the opensuse images |
| 16:50 | Catwich | kernel cant be >63MB |
| 16:50 | Catwich | fdt wont be >1MB |
| 16:51 | bartolo | yes more or less |
| 16:51 | Catwich | and then plenty of space after |
| 16:51 | bartolo | uhm ok |
| 16:51 | Catwich | I calculated these values because I had trouble with space in memory (huge ramdisk) |
| 16:51 | Catwich | so I had to put ramdisk as early as possible |
| 16:54 | bartolo | i've done a quick test by putting ramdiskaddr=0x18100000 but it doesn't work |
| 16:55 | bartolo | same error "Wrong ramdisk image format" "Ramdisk image is corrupt or invalid" |
| 16:56 | Catwich | Oh |
| 16:56 | Catwich | what uboot are you using? |
| 16:57 | bartolo | https://github.com/rabeeh/u-boot-imx6.git |
| 16:57 | Catwich | default configuration? |
| 16:57 | Catwich | the ramdisk needs to be uboot'ized |
| 16:57 | bartolo | yes just compiled and copied |
| 16:57 | Catwich | aka mkimage |
| 16:57 | Catwich | else uboot will complain |
| 16:58 | Catwich | however, uboot supports un-uboot'ized initrds |
| 16:58 | Catwich | just requires enabling an uboot option |
| 16:58 | Catwich | but then, boot.scr becomes a bit more complicated |
| 16:58 | Catwich | so jsut try mkimage on your initrd |
| 17:00 | bartolo | https://linux-sunxi.org/Initial_Ramdisk <- in this way? |
| 17:00 | bartolo | mkimage -A arm -T ramdisk -C none -n uInitrd -d /path/to/initrd.img /path/to/uInitrd |
| 17:00 | bartolo | then I need to point boot.snr to uInitrd rather then on initrd? |
| 17:04 | Catwich | yep |
| 17:04 | bartolo | same error |
| 17:04 | bartolo | *coff* i forgot to generate the boot.snr |
| 17:07 | bartolo | yes now it works! thanks a lot, i've wasted a day on this thing :( |
| 17:07 | bartolo | well I have a "no signal" from the monitor but i've seen the kernel booting for a second :p |
| 17:08 | Catwich | good :) |
| 17:08 | Catwich | and, it took me quite a while to figure this stuff out myself |
| 23:03 | tinycomp | Hey folks, quick question to see if anyone has gotten the BRCM 4330 bluetooth interface working on the freescale 3.10.53 GA kernel? I've been banging my head on this for a couple of days (okay, weeks) and wanted to make sure I'm not chasing something that got broken low level. I'm using the brcm-patchram-plus to inject the firmware; have had this working on 3.10.30 GA + Debian 7 on a cubox-i dual lite (and on a 3.10.17-5-ARCH |
| 23:03 | tinycomp | wandboard quad). |