**** BEGIN LOGGING AT Wed Dec 14 03:00:00 2016 Dec 14 11:15:22 Hi Dec 14 11:16:24 anybody is online Dec 14 11:21:07 Hi sgflt Dec 14 11:21:17 hello! Dec 14 11:21:47 are you aware of beaglebone black? Dec 14 11:21:51 i've got a question regarding the bbb boot process; does the stock-image (unupgraded) boot loader boot from sd card if it is present? Dec 14 11:22:58 where to get the .config file to build kernel? Dec 14 11:23:59 hi Dec 14 11:24:13 Hi zeekhuge Dec 14 11:25:18 Madhu: ahh .. Hey ! Dec 14 11:25:29 I have doubt Dec 14 11:25:42 where to get .config file for kernel build Dec 14 11:25:52 for bbb Dec 14 11:26:11 I downloaded 4.8.y kernel Dec 14 11:26:24 there is no .config present in kernel tree Dec 14 11:26:51 sure . Dec 14 11:26:53 export NEW="" Dec 14 11:26:53 $ wget -c http://rcn-ee.net/deb/jessie-armhf/v$NEW/defconfig -O config-$NEW Dec 14 11:27:24 source : www.zeekhuge.me/post/a_handfull_of_commands_and_scripts_to_get_started_with_beagleboneblack/ Dec 14 11:27:46 point number 6th in the kernel dev section Dec 14 11:27:47 thanks a lot Dec 14 11:27:58 ZeekHuge: you wouldn't have a blog post explaining the boot process, would you? =) Dec 14 11:28:16 boot process . Nope. Dec 14 11:28:44 I used omap2_defconfig file from /config folder is that ok? Dec 14 11:28:48 too bad Dec 14 11:29:37 sgflt: Try asking your problem here, someone might have a solution for it. Dec 14 11:29:46 ZeekHuge: you just missed it =) Dec 14 11:30:13 ZeekHuge: trying to figure out if the BBB boots from SD card even when the button isn't pressed Dec 14 11:30:51 i'm guessing that it will boot from eMMC, runs a boot loader and that loader then boots from SD card? i'm not sure here Dec 14 11:31:20 sgflt: I dont think so. Though its still suggested to remove sd card (if its bootable )so as to avoid un-intentional format. Dec 14 11:31:38 my issue is, i seem to have booted from sd card Dec 14 11:32:11 (judging by the fact that the bbb reports 2016-11-06 and it has been sitting on my desk unused after purchase for at least 6 month) Dec 14 11:32:34 but i have never touched the user boot button in this device Dec 14 11:33:41 so either the bbb must have booted from sd card directly (doesn't it need a FAT partition to do so?) or it chain-booted off of the emmc Dec 14 11:34:43 IF you sure that its automatically booting from the SD, then for some reason bbb was not able to boot from the eMMC Dec 14 11:35:01 the boot sequence is first eMMC and then SD Dec 14 11:35:03 hmm, that's an option as well. but it boots from emmc just fine, i think. Dec 14 11:35:08 i'll try it once more to make sure Dec 14 11:35:50 the eMMC gets bypassed on press of that button Dec 14 11:36:28 That's what I remember at-least. Dec 14 11:36:54 okay, so no sd card, no buttons pressed, reset by disconnecting usb cable -> boot from emmc Dec 14 11:37:00 boots up just fine =) Dec 14 11:39:01 with sd card inserted, again no buttons pressed and reset by disconnecting the usb cable -> boot from sd card Dec 14 11:40:44 sgflt: tried this - https://groups.google.com/forum/#!category-topic/beagleboard/beaglebone-black/_mOlo6T-70E ? Dec 14 11:41:22 do you mean do i shut down the system properly? Dec 14 11:41:43 yes, i turn it off by running `systemctl poweroff` through ssh and waiting for the leds to turn off Dec 14 11:42:40 ah, i believe you mean the 4th post then Dec 14 11:43:46 I think you'll have to modify the env file - /boot/uEnv.txt Dec 14 11:44:37 don't get me wrong, i don't want to change anything, i want to _understand_ how it works. so for now, i'm guessing that its check button pressed (its not) -> load bootloader from emmc -> bootloader boots from sdcard Dec 14 11:45:46 which, technically/from a hardware point of view is booting from the emmc (provided i got this correct) Dec 14 11:54:27 The BBB will always boot from the SD, if it finds it. The button is related to the loading of the bootloader environment. Dec 14 11:54:36 how does the button help then ? Dec 14 11:54:50 Well, thats when you want to install a new image Dec 14 11:55:08 pressing the button loads the bootloader env in from the SD card Dec 14 11:55:24 that has commands to install new image onto the eMMC Dec 14 11:56:05 so booting from SD > booting from eMMC Dec 14 11:56:19 how would one boot from emmc with a bootable sd card present? Dec 14 11:56:45 thats where you need to make changes in the bootloader's env file. Dec 14 11:57:24 but why would you want to have a bootable SD card plugged into BBB ? Dec 14 11:57:37 so where does this bootloader reside? Dec 14 11:57:52 /boot/uEnv.txt Dec 14 11:58:00 i mean physically. emmc or sd card? Dec 14 11:58:30 on both, the pressing of the button decides which to choose. Dec 14 11:58:59 i see Dec 14 11:59:01 thanks Dec 14 11:59:13 button pressed = SD card. eMMC otherwise. Dec 14 12:01:05 Did you ever succeed flashing a bone generated with a sd card generated with the beaglebone-black-make-microSD-flasher-from-eMMC.sh script? Dec 14 12:02:50 I succeed only with the dd Image bone-debian-8.6-lxqt-4gb-armhf-2016-11-06-4gb.img. Dec 14 12:03:38 the former stalled. Dec 14 12:04:48 I ordered a debug cable to look inside the process. but it hadnt arrived yet. Dec 14 12:09:38 Stalled: the bone booted and after a while only the outer led (of the 4) was constantly lighting. Nothing changed in the emmc after rebooting without sd card. Dec 14 12:42:11 Hi Dec 14 12:42:35 I would like to contribute to linux kernel for BBB Dec 14 12:42:46 Any suggestions ? Dec 14 12:45:56 hi. Suggestions on what to contribute, or where to get started? Dec 14 12:46:42 I already developed PWM driver for RTEMS Dec 14 12:46:46 RTOS Dec 14 12:47:11 So I want to contribute similar kind of thing for linux kernel Dec 14 12:50:48 So, the general flow would be: Dec 14 12:50:59 - Set up build environment to build your own kernel for the BBB Dec 14 12:51:02 - Make patch Dec 14 12:51:05 - Submit patch upstream Dec 14 12:52:29 For building/instruction : http://elinux.org/Beagleboard:BeagleBoneBlack_Rebuilding_Software_Image Dec 14 12:52:45 The BBB Kernel tracks the repo here: https://github.com/beagleboard/linux and Dec 14 12:53:14 The upstream kernel documentation for contribution is here: https://www.kernel.org/doc/Documentation/SubmittingPatches Dec 14 12:53:32 HTH, HAND Dec 14 12:54:04 wow Dec 14 12:54:23 Spidler: are you a bot? Dec 14 12:57:03 thinkfat: No: ) Dec 14 12:57:27 I just went through exact these steps a few weeks ago to support a board we built for the BBG Dec 14 13:02:33 Thanks for the info Dec 14 13:03:36 I have already idea about this all but I dont know which support is missing in BBB which community significantly need Dec 14 13:04:08 That's one where I can't answer you :) Dec 14 13:04:26 Can you suggest me some device driver ideas that I could start as small project ? Dec 14 13:04:34 ah okay Dec 14 13:04:48 BTW what are you working on for BBG ? Dec 14 13:05:06 Serial cape with power supply Dec 14 13:05:19 RS485 Dec 14 13:05:32 great ! Dec 14 13:06:02 May I know which tool are you going to use to design cap ? Dec 14 13:06:34 No idea, I'm just doing software once the protoytpes were in place Dec 14 13:07:07 ok. Dec 14 13:13:06 punitvara: please note that many people want to "contribute" to the kernel because its a very prominent part, yet there is a lot more to a linux platform, and a lot of projects are constantly underpowered. Dec 14 13:14:24 punitvara: so maybe picking another less prominent part is more rewarding for easier contribution and more usefulness (the board support for the BBB is kinda complete) Dec 14 13:19:17 LetoThe2nd: I would appreciate if you can give me pointer to any underpowered projects that I can contribute Dec 14 13:21:43 punitvara: any open source project, besides the linux kernel, glibc, gcc, llvm :) Dec 14 13:22:28 LetoThe2nd: Thanks I will look into that Dec 14 13:22:36 punitvara: just depends a bit on your field of interest/expertise Dec 14 13:23:28 Yeah that's true as well. I have seen some EQEP need to be fixed for BBB Dec 14 13:23:32 punitvara: i'd guess you can even contribute greatly if you provide thorough and good documentation, like on the PRU(SS) Dec 14 13:25:07 EQEP support seems to be fixed. PRU (SS) Docs ? Yeah I would love to do that. Dec 14 13:25:38 see, then there's your first idea. Dec 14 13:25:47 Is there any link to existing PRU (SS) dev ? Dec 14 13:26:04 *Documentation Dec 14 13:26:11 check elinux.org and google.com ;-) Dec 14 13:26:29 ah I see. :) Dec 14 15:22:24 hi Dec 14 15:26:30 anybody is onliune Dec 14 15:27:22 nope Dec 14 15:27:24 http://www.catb.org/esr/faqs/smart-questions.html Dec 14 15:28:21 i have a question regarding bbb Dec 14 15:34:08 hi nerienna\ Dec 14 15:34:55 from where to download the .config file kernel build Dec 14 15:40:26 hi folk, I' looking for someone who can develop a relais card control for bbb. Dec 14 15:41:16 target: x times 16 relais can be switched via a python module. Dec 14 15:42:22 currently im targeting for 16-Channel 5V Relay Module from sainsmart Dec 14 15:43:54 anybody can help me to download the .config file for bbb? Dec 14 15:46:10 nobody knows? Dec 14 15:54:17 There are many resources online for building a BBB kernel. Simplest is use rcn-ee's builder. Or you could look at the git for his builder and see if it has a config file. I personally go teletubbie and rely on the script, because I have other fish to fry. Dec 14 15:54:18 reply something Dec 14 15:54:27 Wait. You're being annoying. Dec 14 15:56:32 the kernel config is also installed in /boot as part of a kernel package, so you can find one on any bbb (and any disk image for a bbb) Dec 14 15:58:47 no it is not there in /boot Dec 14 16:01:32 I have a config- in /boot. Maybe you don't have a BBB. Dec 14 16:01:43 maybe if you're looking at some ancient system (wheezy with kernel 3.8) then it might be in a different location since that predates the use of kernel packages Dec 14 16:02:16 i downloaded the 4.8.y kernel from linus git repo Dec 14 16:02:30 since when does linus host beaglebone black images? Dec 14 16:02:36 lol Dec 14 16:02:47 it doesn't contain any .config file in kernel tree Dec 14 16:02:57 can you actually read what I said? Dec 14 16:03:13 If it's not a BBB kernel we don't care. Use a BBB kernel source. Dec 14 16:03:16 I never mentioned the kernel tree Dec 14 16:03:46 from where i can download Dec 14 16:03:56 kernel for bbb Dec 14 16:04:47 https://lmgtfy.com/?q=beaglebone+black+kernel Dec 14 16:05:35 why cann't i use linus kernel for bbb Dec 14 16:05:54 you probably can nowadays Dec 14 16:05:56 I recommend researching hardware architectures to answer that. Dec 14 16:07:34 no we can use any kernel...but we should have appropriate .config file to build for particular board Dec 14 16:08:28 actually that's wrong, the configuration for the particular board is done via Device Tree Dec 14 16:09:26 https://github.com/RobertCNelson/bb-kernel/tree/am33x-v4.9/patches you can try it with that defconfig-bone there Dec 14 16:09:56 also feel free to browse the patches to see what's different in a 4.9-bone kernel compared to mainline 4.9 Dec 14 16:10:02 you are correct...but to generate zimage we need .confug file right? Dec 14 16:10:14 i am talking about that Dec 14 16:10:38 (not all of the patches are specific to the beaglebone btw, a lot of it is also for other SoCs and boards such as the beagleboard-x15 ) Dec 14 16:11:03 yes correct Dec 14 16:11:46 "correct" ? you already assessed this collection of patches in the last two minutes? Dec 14 16:12:31 anyway, I got better stuff to do. have fun with your kernel Dec 14 16:14:22 do you see any config files in /arch/arm/config folder?? Dec 14 18:26:34 i'm trying to get a device tree overlay loaded, is it preferable to use the bone_capemgr, or can i install those statically somehow? (the bbb is single purpose!) Dec 14 22:15:05 where can i find sources for the bbb device tree? Dec 14 22:31:38 sgflt, https://github.com/beagleboard/linux/tree/4.4/arch/arm/boot/dts Dec 14 22:32:03 dlech: thanks Dec 14 22:32:34 dlech: but how do i find out which one exactly my beagle is currently running? Dec 14 22:33:14 Hello can someone help me with getting the hardware files for Beagleboneblack industrial? Dec 14 22:33:29 The link on the page seems to be broken. Dec 14 23:01:12 sgflt, cat /proc/device-tree/model Dec 14 23:01:26 This will match the model in the device tree file Dec 14 23:06:00 dlech: that gives me a lot of hits still Dec 14 23:06:40 dlech: https://gist.github.com/anonymous/6f429101a79b1fba4786de043152949e Dec 14 23:12:57 sgflt, Assuming you don't have "cape=*something*" in your uEnv.txt, it is am335x-boneblack.dts Dec 14 23:14:11 dlech: thank. so i can just patch my overlays into there, recompile and run that, correct? Dec 14 23:15:41 I suppose you can do that. I use cape=... so that I don't mess up the original file. Dec 14 23:16:16 dlech: i don't think it's possible in this case, as i want to activate dcan0. from what i understand, i need to remove the i2c pins from the pinmux Dec 14 23:16:26 ls Dec 14 23:16:31 (sorry) Dec 14 23:18:02 you should just be able to set the i2c node status="disabled". Dec 14 23:18:36 oh, let me try that Dec 14 23:34:10 dlech: kernel:[ 273.941776] Internal error: Oops: 17 [#1] SMP ARM Dec 14 23:34:16 not a success =) Dec 14 23:34:27 doesn't the cape manager need the i2c2? Dec 14 23:34:50 yes. I don't use cape manager ;-) Dec 14 23:37:31 dlech: oh, i thought you need the manager for cape= to work? Dec 14 23:39:05 nope. cape=*name* causes the boot loader to use am335x-bone-*name*.dtb instead of am335x-bone.dtb Dec 14 23:39:16 but i only have .dtbos Dec 14 23:39:29 so i *do* need to generate those .dtb files by patching the .dts first? Dec 14 23:39:39 also, how do i disable the cape manager? Dec 14 23:41:09 I created a new dts that includes am335x-bone-common-no-capemgr.dtsi Dec 14 23:41:21 instead of am355x-bone.dtsi Dec 14 23:41:43 i see Dec 14 23:43:26 dlech: if i read that file correctly, it conveniently also leaves out i2c2 as well? Dec 14 23:43:58 correct Dec 14 23:44:27 awesome Dec 15 00:12:14 dlech: i seem to have two working can devices. thank you very much! Dec 15 00:33:16 sgflt, super! **** ENDING LOGGING AT Thu Dec 15 03:00:00 2016