IRC log of #cubox of Tue 22 Apr 2014. All times are in CEST < Back to index

02:28 dtroyz I started reading the HAB documentation and it seems you have to have some fuses blown to enable secure boot. Does anyone know what fuses (if any) are nuked by solidrun ?
02:28 dtroyz Do I have to have a dev board to be able to play with these things ?
05:35 jnettlet dtroyz, the only fuses burnt are to set the default boot device and the ethernet mac address.
05:36 jnettlet you can burn fuses from the u-boot command prompt. Be warned once fuses are burnt it is permanent, so you could brick your device.
05:54 dtroyz Yeah, I know jnettlet. But theoretically you only need to do it once for the keys.
05:55 jnettlet dtroyz, yes. just warning you.
05:55 dtroyz Is it different with the dev board ? Are they hardware jumpers ?
05:56 jnettlet I don't know, I have not used Freescale's reference board design
06:06 dtroyz If you leave the SEC_CONFIG fuse as Open Configuration it should output any errors with the keys but still boot. I think that's what I'll do first
08:25 davorin morgaehn...
08:54 rabeeh dtroyz: secure booting through jumpers isn't really a secure boot :)
08:54 rabeeh i think with the sabre board you can play with the boot device if serial downloader (i.e. download through USB) or boot from whatever configured via fuses.
09:09 dtroyz @rabeeh, Just for development so I don't brick cubox machines
09:10 dtroyz unless you can supply me some disposable ones ;)
09:11 dtroyz Are you no longer selling those "HummingBoard " boards ?
09:13 dtroyz rabeeh, maybe we can workout a process to blow the right fuses with the right keys and make that set public (on the wiki ? ) so people can develop/test secure boot ?
09:13 dtroyz Of course those set of keys won't be "secure"
09:21 jnettlet okay finally had time to get some kernel hacking done again. DVI support has been pushed to my repo for testing
12:55 davorin hmm...what is the reason a cbi shows sometimes white nosie on screen after booting up?
12:55 davorin like an analogue tv with no station tuned in...
14:23 alpha_one_x86 Hello, for cubox, uboot launch the kernel: Starting kernel... but nothing after...
14:23 alpha_one_x86 I don't found why
14:23 alpha_one_x86 I use https://github.com/SolidRun/linux-linaro-stable-mx6
15:21 jnettlet alpha_one_x86, most likely it can't find the .dtb file for your board.
15:22 alpha_one_x86 I have tryed multiple way, include with append at the end of kernel, I use cubox i 4pro
15:27 jnettlet alpha_one_x86, the best way to debug it is to build a kernel with EARLY_PRINTK enabled
15:27 jnettlet that will allow you to see the beginning output of the kernel
15:59 alpha_one_x86 jnettlet: big thanks for your tips, work, I have the error message: Error: unrecognized/unsupported machine ID (r1 = 0x000012d5).
15:59 jnettlet alpha_one_x86, that means it is not finding the device-tree. Can you send me your u-boot output?
16:00 alpha_one_x86 http://pastebin.com/CiHrguKb
16:02 jnettlet alpha_one_x86, first you probably want to update u-boot. There have been quite a few changes to the code since Jan.
16:02 jnettlet secondly it looks like you are booting a uImage kernel.
16:03 alpha_one_x86 I have updated... where found the last update?
16:03 jnettlet it is generally recommended that you switch to using zImage with newer kernels
16:04 jnettlet https://github.com/SolidRun/u-boot-imx6
16:04 jnettlet but you may need to revert 6fc18f0fa040b8e32eed267445760b1baf7f2b3a
16:04 jnettlet we are still working that out.
16:05 jnettle 16:05 * jnettlet &
16:07 alpha_one_x86 how revert?
16:07 jnettlet git revert 6fc18f0fa040b8e32eed267445760b1baf7f2b3a
16:07 alpha_one_x86 ok
16:11 alpha_one_x86 http://pastebin.com/rHUnKvYZ -> will boot zImage?
16:14 jnettlet oh that is your problem.
16:14 alpha_one_x86 git revert 6fc18f0fa040b8e32eed267445760b1baf7f2b3a fatal: bad object 6fc18f0fa040b8e32eed267445760b1baf7f2b3a
16:14 jnettlet strange. must have a different hash
16:15 jnettlet for your uEnv.txt just have mmcargs=setenv bootargs 'and then your bootargs here'
16:15 jnettlet and leave the rest out. We have autodetecting scripts to find the zImage and load the proper .dtb file for your board
16:15 jnettle 16:15 * jnettlet really is leaving now
16:27 alpha_one_x86 how make uboot ?
16:38 _dab_ http://imx.solid-run.com/wiki/index.php?title=Building_the_kernel_and_u-boot_for_the_CuBox-i_and_the_HummingBoard
17:44 alpha_one_x86 re
17:44 alpha_one_x86 what is the procedure to compil uboot for cubox i 4 pro?
17:45 alpha_one_x86 found
17:50 alpha_one_x86 http://pastebin.com/4irG8Tvx
17:52 alpha_one_x86 That's mean I have already the last uboot...
18:04 jnettlet alpha_one_x86, the timestamp and git code are wrong for the current head. Are you using SolidRun's repo?
18:04 alpha_one_x86 yes
18:05 alpha_one_x86 git clone and the url given by you
18:05 jnettlet alpha_one_x86, then I think your dd commands aren't working properly. Can you paste those
18:05 alpha_one_x86 I have cubox-i clock drift... and I compil directly on cubox-i
18:07 jnettlet but I am not sure why it is trying to load a uImage
18:07 alpha_one_x86 dd if=SPL of=/dev/mmcblk0 bs=1K seek=1
18:07 alpha_one_x86 dd if=u-boot.img of=/dev/mmcblk0 bs=1K seek=42
18:07 jnettlet okay. can you break into the u-boot shell and run printenv
18:10 alpha_one_x86 http://pastebin.com/rxrEqt95
18:11 jnettlet ah you have a stored env trying to load the uImage
18:11 alpha_one_x86 I use the default env from debian...
18:12 jnettlet u-boot env
18:12 jnettlet is debian still forcing people to use uImage?
18:12 alpha_one_x86 I'm newbie for uboot... and I'm on gentoo
18:13 jnettlet okay. then lets reset your env to my default
18:13 alpha_one_x86 I use just boot/kernel from debian
18:13 jnettlet env default -f -a
18:13 jnettlet then saveenv
18:13 jnettlet then reset
18:15 alpha_one_x86 done, but exacte same printenv...
18:16 jnettlet the bootfile is still uImage?
18:16 alpha_one_x86 yes
18:16 alpha_one_x86 but I prefer zImage
18:17 jnettlet I am a bit confused how that is being set. We don't use uImage unless the user sets it up.
18:19 alpha_one_x86 I will try clear with my poor english: SPL + u-boot.img -> from git, uImage-ok -> kernel from debian boot -> uImage https://github.com/SolidRun/linux-linaro-stable-mx6
18:21 jnettlet if you want to use a uImage with a device-tree file you need to create a zImage, append the .dtb and then encode it into a uImage
18:23 alpha_one_x86 https://wiki.gentoo.org/wiki/Cubox-i
18:23 alpha_one_x86 I have following this procedure, in best case: Uncompressing Linux... done, booting the kernel. -> and no more
18:25 alpha_one_x86 just now I try, make uImage...
18:26 alpha_one_x86 http://pastebin.com/7TP8cxTC
18:30 jnettle 18:30 * jnettlet shrugs. could be a problem with the gentoo compiler. Or a problem with the uImage format. I haven't tested that in a long time.
18:49 alpha_one_x86 The compiler should work, because I have compiled each application of the os with it...
18:56 alpha_one_x86 I don't found what's appen, and why seombody have boot under gentoo, not others...
18:56 slangen alpha_one_x86: how did you create the uImage?
18:58 alpha_one_x86 or make uImage -> illegal instruction, or https://wiki.gentoo.org/wiki/Cubox-i but block at booting kernel...
19:34 jenkins101 anyone working on HD audio for cuboxi here?
19:34 jenkins101 I am testing the latest patches that enables it but I get a error
19:34 jenkins101 http://sprunge.us/CORb
19:34 jenkins101 xbmc log
20:23 jas-hacks jnettlet: I noticed 3.10.17_1.0.0 GA release, need to see if the BSP libs are available
20:38 jnettlet jas-hacks, yep. I will start tearing through patches over the weekend.
20:39 jas-hacks jnettlet: did they include your patches?
20:39 jnettlet jas-hacks, nope. I think they got pushed back to Vivante but haven't heard much about it.
20:42 jas-hacks jnettlet: also saw the challenge from Novena
20:42 jnettlet jas-hacks, yes. hopefully we can reach our funding. It will help move things along.
21:13 jenkins101 where can I find this release?
21:56 jas-hacks jenkins101: http://git.freescale.com/git/cgit.cgi/imx/linux-2.6-imx.git/log/?h=imx_3.10.17_1.0.0_ga
21:57 jenkins101 jas-hacks: linux-2.6 ?
21:58 jas-hacks jenkins101: thats just the same of the repo, the branch is 3.10.17.1.0.0_ga
22:01 jenkins101 aa