**** BEGIN LOGGING AT Tue Jun 18 02:59:59 2013 Jun 18 07:44:53 av500: tried to boot with a kernel from the link you gave me but it fails and tells me that my hardware id is not good Jun 18 07:45:44 any idea with what toolchain are the kernels built? i tried with the angstrom one and it fails miserably Jun 18 07:46:30 what about the DTB? Jun 18 07:46:37 angstrom toolchain is fine Jun 18 07:46:51 you have to pass the DTB with the kernel or append it Jun 18 07:46:56 pastebin the log Jun 18 07:47:06 a second, to reboot into linux(osx now) Jun 18 07:51:27 av500: http://pastebin.com/LGFVmBrm Jun 18 07:55:00 another thing i discovered yesterday: if u-boot is built with gcc-linux-gnueabi- when it starts rndis it throws an memory alignment error. if u-boot is built with angstrom toolchain it works perfect Jun 18 09:37:47 av500: got this when tried to compile kernel with angstrom toolchain http://pastebin.com/2N328m2R Jun 18 09:40:47 which angstrom toolchain? Jun 18 09:41:09 ah Jun 18 09:41:22 vvu|Mobile: CROSS-COMPILE <- that needs to have an underscore, not a hyphen Jun 18 09:41:54 right Jun 18 09:42:10 sorry for that one, me stupid sometimes. now i get Assembler messages: Jun 18 09:42:10 Error: unrecognized option -mauto-it Jun 18 09:42:10 make[2]: *** [scripts/mod/empty.o] Error 1 Jun 18 09:42:10 make[1]: *** [scripts/mod] Error 2 Jun 18 09:42:10 make[1]: *** Waiting for unfinished jobs.... Jun 18 09:42:35 koen: this is my toolchain : angstrom-2011.03-x86_64-linux-armv7a-linux-gnueabi-toolchain.tar.bz2 Jun 18 09:58:01 got it to compile with sourcery codebench 2013.05-24 Jun 18 09:59:47 same error about machine id http://pastebin.com/L41aztMf Jun 18 10:06:38 looks like it did not like the FDT Jun 18 10:06:45 that error means there is not FDT Jun 18 10:06:46 AIUI Jun 18 10:07:01 koen: ? Jun 18 10:07:54 as device tree i used the one from arch/arm/boot/dts/am335x-boneblack.dtb Jun 18 10:08:09 yes Jun 18 10:08:13 but something seems not to work Jun 18 10:09:32 even if i put device tree or not same error Jun 18 10:10:05 yes Jun 18 10:11:39 vvu|Mobile: use a more recent toolchain please, like v2012.12 Jun 18 10:11:55 i used sourcery codebench 2013.05-24 Jun 18 10:13:08 e.g.angstrom-eglibc-x86_64-armv7a-vfp-neon-v2012.12-toolchain.gz Jun 18 10:13:20 yep Jun 18 10:13:21 dwlding now Jun 18 10:15:49 anybody has a mirror for this toolchain? the link on angstrom website i 4kb/s dwld speed for me :( Jun 18 10:39:53 maybe i`m clumsy but where can i find gcc for this toolchain? went through all "bin" dirs but nothing there Jun 18 11:21:50 no gcc? Jun 18 12:44:25 av500: can`t find the tools Jun 18 12:45:32 what did you download? Jun 18 12:45:34 the archive extracts oecore-x86_64 and no building binaries, just some qemu stuff there. maybe i`m doing something retarded Jun 18 12:45:49 url? Jun 18 12:45:52 angstrom-eglibc-x86_64-armv7a-v2012.05-toolchain.tar.bz2 Jun 18 12:46:05 http://www.angstrom-distribution.org/toolchains/angstrom-eglibc-x86_64-armv7a-v2012.05-toolchain.tar.bz2 Jun 18 12:46:31 wow, slow Jun 18 12:46:47 http://www.facebook.com/l.php?u=https%3A%2F%2Fwww.dropbox.com%2Fs%2Fwivuzit80sjca6l%2Fangstrom-eglibc-x86_64-armv7a-vfp-neon-v2012.12-toolchain.gz&h=oAQFaEIr0 Jun 18 12:46:51 try this one Jun 18 12:46:56 asked a friend to dropbox it to me Jun 18 12:46:58 he had speed Jun 18 12:52:33 i think the problem is from u-boot because when i used the angstrom kernel from the image got the same error with the mach id Jun 18 13:07:35 av500: any idea? Jun 18 13:13:47 at this point i can start and shape the app for android, but i really wanted to have an working example for linux :) Jun 18 13:26:18 well, you need a uboot that knows DT Jun 18 13:26:28 can you boot MLO uboot and uimage from sD? Jun 18 13:27:47 yep Jun 18 13:27:49 sdcard work ok Jun 18 13:27:59 i got working MLO, uboot over usb Jun 18 13:28:03 and then inserted sdcard Jun 18 13:28:17 and tftp uImage and put root=/dev/mmcblk020 or how was it Jun 18 13:28:23 to use sdcard as rootfs and worked Jun 18 13:28:32 arrived at angstrom login Jun 18 14:07:01 nice Jun 18 14:07:10 vvu|Mobile: nice. Jun 18 14:07:24 thx Jun 18 14:07:37 how are you planning on doing the rootfs thing? Jun 18 14:08:45 spoke with ka6sox-away about it a bit but i know nothing about how nfs works Jun 18 14:08:55 a kernel + ramdisk might provide you functionality to go to the next level Jun 18 14:09:01 thi is my 1st idea, trying to implement nfs Jun 18 14:09:13 but don`t want to end up with an overkill Jun 18 14:09:14 that would be crazy Jun 18 14:09:20 yep :)) Jun 18 14:10:28 perhaps it's time to switch host and device and start communicating over something else Jun 18 14:10:35 i don`t have any knowledge in this area, hoping to get some hints from here Jun 18 14:10:50 e.g. upload a kernel + ramdisk doing a different usb protocol(adb?) Jun 18 14:11:32 kernel+ramdisk i have with usb communication bulk_transfer, can`t i get rootfs with adb? Jun 18 14:11:39 or fastboot/dfu Jun 18 14:12:04 vvu|Mobile: the thing is that you can include a ramdisk (smallish root file system) Jun 18 14:13:07 this file system can get the real root from anywhere. e.g. you are in a state where you can use existing kernel modules and userland tools to do anything Jun 18 14:13:35 choosing the right tool is the key now Jun 18 14:14:16 IMHO you will need to write to the MMC. but the current tools you have is really great for bootstrapping. Jun 18 14:15:34 What I have previously done is expose the whole MMC over usb mass storage to a PC (this is just a script that loads the mass storage gadget) Jun 18 14:15:54 at this point we need a bit to decide where this project leads to =>testingTool and not uing any resources the board has except usb, ram or have a running board with full x11 and all the set Jun 18 14:15:55 upon eject you reboot. Jun 18 14:16:06 this is nice to have it as a mass stoarge Jun 18 14:16:24 open it from android write all stuff there then change to that fs Jun 18 14:17:42 this does reverse the roles. I think the proper solution is to enable DFU in the bootloader Jun 18 14:18:30 having the mmc as mass storage? Jun 18 14:19:01 why should it inverse the roles, isn`t like plugging an usb drive into a PC(host)? Jun 18 14:20:54 we discussed a few things ( BBB as usb device to flash it, Android as mass storage device to boot from, DFU on BBB in u-boot to flash the device) Jun 18 14:21:48 now is the point in taking the final decision Jun 18 14:22:05 BBB as usb mass storage might be a bit more compilcated when using Android (e.g. you need to mount file system or get permissions to do so) Jun 18 14:22:20 also, no ext drivers Jun 18 14:22:23 or in a few weeks*until i implement spl, u-boot transfer on andoid* Jun 18 14:22:25 most likely Jun 18 14:22:32 vvu|Mobile: not now Jun 18 14:22:45 for now, I would be happy to get mlo+uboot+kenrel and initrd Jun 18 14:22:48 from java API Jun 18 14:23:09 i think in 2 weeks*max* we will have it running like this Jun 18 14:23:17 fine Jun 18 14:23:24 seems resonable to you or need to move faster? Jun 18 14:23:27 the DFU road will probably work in a few hours and you can after that start flashing anything you want on that Jun 18 14:23:28 no Jun 18 14:24:11 keesj: use android to flash bbb? Jun 18 14:24:43 using dfu-utils to flash the BBB(work on Android and normal desktop pc) Jun 18 14:26:01 av500 what do you think? Jun 18 14:26:57 flash 2GB with DFU? Jun 18 14:27:03 yes Jun 18 14:28:16 hmm Jun 18 14:32:32 on my side i will stay 2-3 days to repair my current code, and make more functions..split the code then i will start working my way on java Jun 18 14:32:49 It might be simple and it might just work[tm]. Jun 18 14:33:06 sure Jun 18 14:33:24 vvu|Mobile: I will give DFU a little try and let you know if it works Jun 18 14:33:29 perfect Jun 18 14:34:00 off-topic a bit uboot supports multiple setenv commands in one? setenv ipaddr 192.168.1.3 serverip 192.168.1.9 Jun 18 14:59:28 you can use ";" **** ENDING LOGGING AT Wed Jun 19 02:59:58 2013