**** BEGIN LOGGING AT Mon Aug 31 02:59:59 2015 Aug 31 06:16:38 Hi, does anyone know the list or can give me a link of kernel drivers for the BBB ? Aug 31 06:56:12 Gwak: just look at the config used for building the official debian based images? Aug 31 07:53:38 Devices tree and pinmuxing is making me crazy guys :(, is there any way to properly redefine the default configuration of the board ? Here is my problem : I want to properly remap the board for embeded use, I don't need any fun features of the board, I wan't a minimal kernel with my digital and analog I/O for which I will wrote my own drivers to work with gpio registers... How can I achieve that ? I've rewrite the boneblack dts and us Aug 31 07:53:48 is making me sometrouble for gpio bank0 Aug 31 07:55:56 MUX_MOD7 do not apply for this one something is overwritting my configuration (P9_17 P9_18) Aug 31 08:02:46 find all dts envovled and change em Aug 31 08:02:56 nothing is in your way to do so Aug 31 08:06:47 That's what i've done but I can't find were P9_17 and P9_18 are set to 0x62 mode ... (it's i2c1) Aug 31 08:07:20 0x15c (PIN_OUTPUT_PULLDOWN | MUX_MODE7) /* P9_17 GPIO0[5] digital_out4 */ 0x158 (PIN_OUTPUT_PULLDOWN | MUX_MODE7) /* P9_18 GPIO0[4] digital_out5 */ Aug 31 08:08:08 just above those line i'm setting the other I/O and it works well but for P9_18 and 17 this doesn't work Aug 31 08:08:36 did a search on every file included and nothing if referencing to 0x15c and 0x158 Aug 31 09:20:57 Does anyone kown a link or a book that explain how to create a device driver and the device tree related from scratch (defining pinmux in DT, plateform driver ..) The ones i've read are quite old and don't refer to device tree when working on plateform drivers Aug 31 09:37:04 I dont know of a book that covers DT Aug 31 09:37:17 I would look into existing drivers for guidance Aug 31 09:37:30 and look into how drivers were converted to DT Aug 31 09:39:32 I'm digging in dts kernel src but i'm going crazy with DT >.<, does pinmux apply if I just define it in the DT and with a compatible ="foo" property but don't activate the driver ? Aug 31 09:39:54 or the pinmux apply only if the driver is loaded ? Aug 31 09:40:19 That could explain why my DT doesn't work Aug 31 10:27:10 hey i had a question, is there any way to move the linux ditro image straight onto the BB black ? Aug 31 10:28:38 basically, can you access the sd card as a volume on the BBB in order to move files to it? Aug 31 10:29:30 this is just because I don't have a microsd -> sd convertor Aug 31 11:10:56 wtfsoko, u can acces both with basic mount + cp commands Aug 31 11:16:25 thank you! Aug 31 12:35:33 Hi, is there a particular lib for using the PRU on kernel side ? I've only seen infos on user side Aug 31 12:51:54 ok, I just got my beaglebone green and I understand why so many people are happy with it Aug 31 13:17:14 citylight2: and why, exactly? Aug 31 13:17:26 ok, is anyone here using the beaglebone green? Aug 31 13:18:10 the wiki page is very basic, how to connect the groove relay? Aug 31 13:19:09 samael: it is very convenient for adding sensors Aug 31 13:19:28 and the buttons are a bit bigger Aug 31 13:20:42 but as i understand, you need the groove sensors (which is a proprietary standard?) at hand Aug 31 13:22:53 I am just figuring all this out now, worst case I will build my small circuit Aug 31 16:19:31 hi i have problem u-boot in beagle bone black Aug 31 16:19:59 unable to load second stage boot loader Aug 31 16:20:27 http://pastebin.ca/3145632 Aug 31 16:21:11 please guide me how to debug u-boot loader Aug 31 16:21:54 ganeshkumar, look like u-boot can't read the mmc... since your using "2013.04" it's probally been fixed a long time ago.. retry with 2015.10-rc2 Aug 31 16:22:27 or you broke the mmc pins... Aug 31 16:24:04 thanks i ll try 2015.10-rc2 Aug 31 19:09:30 rcn-ee: here? Aug 31 19:30:11 so I got back to 3.8.13-bobe71 and need some help with loading the dtbo here Aug 31 19:37:38 root@beaglebone:/home/debian# ls /lib/firmware/PyBBIO-gpio0_2-00A0.dtbo Aug 31 19:37:38 /lib/firmware/PyBBIO-gpio0_2-00A0.dtbo Aug 31 19:38:03 # echo PyBBIO-gpio0_2 > /sys/devices/bone_capemgr.9/slots Aug 31 19:38:03 bash: echo: write error: Invalid argument Aug 31 19:40:54 citylight2, after the echo write error: dmesg | grep bone Aug 31 19:42:03 thanks I am lost here.. Aug 31 19:42:32 [ 216.917792] bone-capemgr bone_capemgr.9: slot #11: Incompatible with baseboard for 'PyBBIO-gpio0_2' Aug 31 19:42:42 so I need to compile it , ok Aug 31 19:43:11 I need some of your DT wisdom sir Aug 31 19:43:41 the compaitble flag must be off, you'll see it in PyBBIO-gpio0_2-00A0.dts Aug 31 19:44:03 I seek to change P9_22 from uart2-rxd -> gpio0(2) (mode7) Aug 31 19:44:08 that much I do know Aug 31 19:45:16 now the dts file here looks like this: http://nopaste.linux-dev.org/?743003 Aug 31 19:46:12 am I suppose to remove lines 68-70 and 72-73 then compile it? Aug 31 19:47:23 hmm, I think you mean line 61 Aug 31 19:48:26 the baseboard reference comes from line 6.. Aug 31 19:49:48 I see is it wrong? I do have a beaglebone black Aug 31 19:51:53 nope, but there's probally something else under "dmesg | grep bone" Aug 31 19:52:15 ok Aug 31 19:53:18 ok, let me start again Aug 31 19:54:31 this is all I got: Aug 31 19:54:32 http://nopaste.linux-dev.org/?743013 Aug 31 19:56:28 ok, I compiled it from the dts, and it is identicle to the dtbo I use Aug 31 19:56:29 odd Aug 31 19:57:01 same dtc compiler, the 3.8 vs 4.1+ is different Aug 31 19:57:30 DTC 1.4.0 Aug 31 19:57:48 must I build it from source Aug 31 19:57:49 ? Aug 31 20:08:28 which hash to use to build dtc for 3.8.13-bone71? Aug 31 20:13:35 citylight2, this one: https://github.com/RobertCNelson/tools/blob/master/pkgs/dtc.sh Aug 31 20:13:45 thanks a lot Aug 31 20:15:32 ok, so do I need to remove any lines in the PyBBIO-gpio0_2-00A0.dts in http://nopaste.linux-dev.org/?743003 to get is working as gpio? Aug 31 20:17:49 o here the compiler yels at me Aug 31 20:18:00 Reference to non-existent node or label "am33xx_pinmux" Aug 31 20:18:13 I guess I need to get all the sources Aug 31 20:18:41 maybe here /opt/source/PyBBIO/tools/overlays/ Aug 31 20:19:06 no same problem Aug 31 20:19:53 need I git clone https://github.com/RobertCNelson/dtb-rebuilder.git ? Aug 31 20:20:18 for PyBBIO-gpio0_2? no.. Aug 31 20:21:14 debian@beaglebone:/tmp$ /usr/local/bin/dtc -O dtb -o PyBBIO-gpio0_2-00A0.dtbo -b 0 PyBBIO-gpio0_2-00A0.dts Aug 31 20:21:22 ERROR (phandle_references): Reference to non-existent node or label "am33xx_pinmux" Aug 31 20:21:30 ERROR (phandle_references): Reference to non-existent node or label "ocp" Aug 31 20:21:37 help Aug 31 20:23:01 the target = <&am33xx_pinmux>; was always good Aug 31 20:23:18 as well as the &ocp Aug 31 20:25:11 where's the "-@' Aug 31 20:25:32 https://learn.adafruit.com/introduction-to-the-beaglebone-black-device-tree/compiling-an-overlay Aug 31 20:25:59 YES Aug 31 20:26:41 ok, same dtbo: Aug 31 20:26:49 debian@beaglebone:/tmp$ md5sum PyBBIO-gpio0_2-00A0.dtbo /lib/firmware/PyBBIO-gpio0_2-00A0.dtbo.orig Aug 31 20:26:49 07936cef55246d4a8894509d371b0359 PyBBIO-gpio0_2-00A0.dtbo Aug 31 20:26:49 07936cef55246d4a8894509d371b0359 /lib/firmware/PyBBIO-gpio0_2-00A0.dtbo.orig Aug 31 20:27:04 so I am back to square one Aug 31 20:27:20 I got a dtc compiler but maybe the dts is faulty Aug 31 20:27:52 debian@beaglebone:/tmp$ /usr/local/bin/dtc -O dtb -o PyBBIO-gpio0_2-00A0.dtbo -b 0 -@ PyBBIO-gpio0_2-00A0.dts Aug 31 20:28:20 thia line is above the three I pasted to show where the PyBBIO-gpio0_2-00A0.dtbo came from Aug 31 20:30:48 sorry, but I am stuck, Aug 31 20:40:42 so my guess is that something is wrong with this PyBBIO-gpio0_2-00A0.dts Aug 31 20:40:54 but don't understand how to fix it Aug 31 20:41:13 so I must upgrade to kernel 4.0 Aug 31 20:41:14 ? Aug 31 20:41:47 rcn-ee .. question for you .. is there a way we can patch mainline kernel for the rs485 gpio ? I saw a certain amount of integration .. but don't know whether it actually works .. since there's probably a D-T overhead associated with it Aug 31 20:43:34 I've been trying to set the "bootretry" environment variable in uboot with no success. Has anyone used this before? Aug 31 20:45:44 veremit, i believe the 8250_omap driver is getting those, gpio defined rts/cts/etc... Aug 31 20:46:11 rcn-ee .. the omap_serial.c still exists in 4.1 I see .. Aug 31 20:46:20 no idea whether it works Aug 31 20:46:49 I can't remember now who in here was talking about rs485, but they were on 3.8 and my curiosity was rekindled Aug 31 20:47:02 rcn-ee: sorry, if I upgrade to 4.1 what to do to get P9_22 as gpio ? Aug 31 20:47:09 previously I cheated with a usb hub chip and ftdi bridges :D Aug 31 20:47:23 veremit, the omap_serial.c been depreciated.. it's functionaly has been merged back to 8250_omap, next their was patches to add the rs485 stuff on top of that.. Aug 31 20:47:37 citylight2, config-pin P9_22 out.. Aug 31 20:47:44 rcn-ee, aha, thanks .. figured you were the person to ask ;) Aug 31 20:48:04 just one command line. ok Aug 31 20:48:13 citylight2, config-pin P8.22 hi/low Aug 31 20:48:29 4.1 or 4.2? Aug 31 20:48:29 citylight2, yeap, setup by 'default' like that in the lxqt/jessie image.. Aug 31 20:49:55 citylight2, the jessie image is "4.1.x-ti" but i'm keeping 4.2.x/etc in sync with the v4.1.x-ti base.. Aug 31 20:51:06 I see linux-image-4.1.6-ti-rt-r12 and linux-image-4.1.6-ti-r12 Aug 31 20:51:11 what ? Aug 31 20:52:05 rt= realtime.. Aug 31 20:52:12 ok, thnaks Aug 31 20:52:36 by the way can I also upgrade dist? Aug 31 20:53:30 o ya, rcn-ee , do you have a garden? can I send you a gift? Aug 31 20:54:03 citylight2, reflash, to get config-pin working out of the box in jessie.. Aug 31 20:54:21 there's really no easy dist-upgrade patch from wheezy/gtk2.x -> jessie/qt5... Aug 31 20:54:46 I see Aug 31 20:55:22 and the current image for jessie is.... Aug 31 20:57:01 https://rcn-ee.com/rootfs/bb.org/testing/2015-08-16/console/bone-debian-8.1-console-armhf-2015-08-16-2gb.img.xz Aug 31 20:57:24 no there is a 08-30 Aug 31 20:57:29 citylight2, grab this one: https://rcn-ee.com/rootfs/bb.org/testing/2015-08-30/lxqt-4gb/ Aug 31 20:57:30 but its missing in the wiki Aug 31 20:58:18 yeap no wiki update yet... needed a newer kernel for the x15-beta board's.. so for bbb users, it won't be any different then the 08-30 ^^^ Aug 31 20:58:55 (in about 10 hours, 08-31 will be all uploaded, that one is going on the wiki) Aug 31 21:00:14 ok Aug 31 21:00:54 veremit, http://www.spinics.net/lists/linux-serial/msg17639.html yuck! ;) Aug 31 21:01:39 veremit, but you can see the mctrl gpio helpers are available, just need to update 8250_omap to use them.. Aug 31 21:01:53 yes I saw somethign about the mctrl stuff Aug 31 21:03:54 *yawn* Aug 31 21:05:22 I need a pointer. What is the best approach to deploy a consumer product where if the image is corrupted the user can re-image without bricking; in a consumer user friendly way Aug 31 21:05:33 rcn-ee ,, whilst the omap prevails, it's one avenue, although I think integration with the 8250 driver is invariably the right path .. Aug 31 21:07:12 veremit, on i meant, yuck as in ti hadn't bee testing rs485, so it's going to be from a user of 8250_omap to add rs485.. i had thought ti had a patch in queue... Aug 31 21:08:06 In other words I am looking for a user friendly bootloader. Think NOT uboot Aug 31 21:08:21 rcn-ee .. the chip vendor does one permutation, then, like much of linux .. you're reliant on the community to fill in the gaps... Aug 31 21:08:49 gt465 .. all that can be acomplished automagically with uboot Aug 31 21:09:14 think of all the consumer networking devices out there ... Aug 31 21:09:32 all that I've found use uboot .. except one. Aug 31 21:09:45 think that uses something like 'cfl'? Aug 31 21:10:10 redboot/lilo/barebox... u-boot is about the most friendly you can get.. ;) Aug 31 21:11:01 redboot... i havent heard that name in a decade... Aug 31 21:11:22 always fastboot Aug 31 21:11:24 * ds2 ducks Aug 31 21:11:56 ds2: if you want a reason to duck, mention uefi Aug 31 21:12:14 yes but think a clueless user, not a semi competent person. Someone that asks "what is that black thingy" meaning shell. Aug 31 21:12:42 clueless users should _NOT_ do embedded linux Aug 31 21:12:47 then gt465 you need to hide u-boot, boot into a linux and give them a pretty gui... Aug 31 21:13:11 unxz -c ~/Downloads/bone-debian-8.1-console-armhf-2015-08-30-2gb.img.xz | sudo dd of=/dev/mmcblk0p1 bs=1M - right ? Aug 31 21:13:16 gt465: what rcn-ee said Aug 31 21:13:26 or /dev/mmcblk0 ? Aug 31 21:13:39 citylight2, the one without the 'partition'.. Aug 31 21:13:46 thanks Aug 31 21:14:10 KotH and rcn-ee, exactly, I agree, so my question is, is there something out there already that I can leverage? Aug 31 21:14:17 I don't want to reinvent the wheel Aug 31 21:14:27 'android'.... ducks and runs... Aug 31 21:14:28 gt465: there was a bof session at last ELCE on that topic Aug 31 21:14:35 gt465: IIRC there is a video of that Aug 31 21:15:01 where do Ifind the video? Aug 31 21:15:19 elinux, where everything worth reading/watching is Aug 31 21:20:28 KotH: I don't think sucking will save you from a 20mega ton... Aug 31 21:20:52 ducking Aug 31 21:20:53 blah Aug 31 21:42:59 on the green should I hold the USER button near the micro sd when I want to boot from it? Aug 31 21:43:26 the file system on the micro sd passed fsck, yet the green does not boot from it Aug 31 21:44:43 and /dev/ttyACM0 for the serial does not show up, and the usb does not give IP... hmmm Aug 31 21:44:50 maybe it needs to ripen Aug 31 21:45:04 what? Aug 31 21:45:12 I'm having a hard time editing the uboot environment on the eMMC. Can anyone give me a good spot to start? Aug 31 21:45:15 it worked fine from the image it came with Aug 31 21:45:15 wait till it turns red.. Aug 31 21:45:53 citylight2, please pastebin a serial boot log... Aug 31 21:46:16 I have no serial connection when I boot from micro sd Aug 31 21:46:34 6 pin header... Aug 31 21:46:37 when I boot from eMMC I do have serial Aug 31 21:47:04 pin 1- black pin 4 green Aug 31 21:47:13 pin 5 white Aug 31 21:47:16 nothing Aug 31 21:47:31 led are blinking Aug 31 21:47:36 odd Aug 31 21:48:09 ok, good night Aug 31 21:48:53 rcn-ee: is it still correct that there is only one BeagleBone image for all the different hues of it? Aug 31 21:49:19 ds2, correct... "but" nothing "eariler.."... Aug 31 21:49:41 the Green will work on the 2014-debian and 2013-angstrom... Aug 31 21:49:47 is it possile the 30 Aug image is bad? Aug 31 21:50:14 rcn-ee: was more of wondering if you really care how the eMMC is wired up (expansion signals vs the "on board" signals) Aug 31 21:50:51 if you use the same eMMC signals as the black/green, you can pretty much use the old images too... Aug 31 21:51:34 rcn-ee: but the white has no eMMC and the only mmcblk device is wired differently then the black Aug 31 21:51:50 citylight2, could be... been mostly focusing on the bbx15, so beta users can atleast boot something. ;) Aug 31 21:51:53 but it sounds like your scripts are agnostic to that Aug 31 21:52:50 u-boot read's the serial eeprom and decides what to do, otherwise white/black/green are all generic together.. Aug 31 21:53:12 'k Aug 31 21:53:21 if the eeprom was mis-programmed, well it'll go off in the weeeds.. ;) Aug 31 21:53:37 u-boot can be patched Aug 31 21:53:56 u-boot is easy to screw it. it is the damn userland that is like quicksand Aug 31 21:54:04 which we do for the 'blank' black's... and 'blank' green's.. the black blank image is available in my rootfs dir. .. ;) Aug 31 21:54:34 does the kernel look at the eeprom thesedays? Aug 31 21:55:39 ds2 it does as v4.2.x: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/arch/arm/boot/dts/am335x-bone-common.dtsi#n228 (cape eeprom's are there too below the baaseboard) Aug 31 21:55:52 I see Aug 31 21:55:53 sigh Aug 31 21:56:01 as far as "doing" somethign with that... maybe v4.3/v4.4... Aug 31 21:56:54 there was a talk bout it at the last plumblers conference a few weeks back, wasn't there so i dont' know the current issue.. Aug 31 21:57:13 one more complication for pero loco :( Aug 31 21:59:38 no another green does not boot from microsd wit 08-30 Aug 31 22:03:31 ok, second green does boot from jessie 8,0 micro sd Aug 31 22:19:37 citylight2, might be the eeprom on the other one.. i think my production green's just arrived (had a fedex please sign posted on my door) Aug 31 22:28:48 where to get config-pin from? Aug 31 23:15:28 has anyone successfully used CONFIG_RESET_TO_RETRY + CONFIG_BOOT_RETRY_TIME to get uboot to automatically reboot Aug 31 23:37:32 never mind, I got my answer on the #u-boot channel Aug 31 23:40:04 +1 abferm :) Sep 01 00:32:11 hello people Sep 01 00:32:36 i thought that i could use the beaglebone like arduino Sep 01 00:32:39 with an ide Sep 01 00:32:50 debugging and else Sep 01 00:33:42 think im gonna burn this shit before run my first program **** ENDING LOGGING AT Tue Sep 01 02:59:58 2015