**** BEGIN LOGGING AT Fri Jul 17 02:59:58 2015 Jul 17 04:30:14 Hi Jul 17 04:38:56 zmatt: yeah, i think 4.1 switched back to ttyS as per a conversation with rcn-ee earlier Jul 17 04:39:29 but even if it was a tty issue, i would assume that ssh would still be okay? Jul 17 04:39:53 I'd normally expect so, but iirc for some reason it refused to boot Jul 17 04:40:33 maybe there'd be some message on the console explaining why, but wel... ;P Jul 17 04:41:49 do you have a 4.x kernel working? did you use a fresh config or try to patch in the 3.x? Jul 17 04:43:21 as my log shows I have a kernel running derived from 4.2.0-rc1-bone1 Jul 17 04:43:46 ah, i missed that Jul 17 04:44:35 but, conceivably you could have inherited an earlier config Jul 17 04:45:19 correct, I have a custom config and sort track and merged with rcn-ee's linux-dev tree Jul 17 04:45:37 4.1.1-bone however failed to compile Jul 17 04:45:57 interesting Jul 17 04:46:19 it seems rcn-ee merged some power management stuff into his 4.1.1 Jul 17 04:46:59 including a new-and-shiny sleep33xx.S which refuses to assemble in Thumb mode -.- Jul 17 04:47:27 quite an accomplishment in ARMv7 Jul 17 04:47:50 to manage to use the rare few constructs that are available in one instruction set but not the other Jul 17 04:49:09 murphy's ISA Jul 17 04:50:11 rcn-ee solved it by compiling the kernel in ARM mode Jul 17 04:50:31 but I refuse to make that compromise to compensate for the incompentence of whatever TI engineer wrote that code :P Jul 17 04:51:00 it's a mystery to me why anyone would compile anything at all in ARM mode anymore since ARMv7 Jul 17 04:52:58 I also doubt it would be accepted upstream in such a state, so hopefully the issue will be fixed soon enough Jul 17 04:53:21 (or I might look at it myself if I can muster the motivation) Jul 17 04:55:13 I still have no idea what the pros or cons are of SERIAL_8250_OMAP (ttyS*) versus SERIAL_OMAP (ttyO*) Jul 17 04:55:37 do you like the letter O or S better? Jul 17 04:56:46 I'd personally lean more torwards using a driver written specifically for the omap UART.... provided it's written more competently than the one in StarterWare :P Jul 17 04:57:24 (which regularly plays russian roulette with the data stream) Jul 17 04:59:19 horrible little peripheral that uart is anyhow... it's amazing how something with such a simple task to perform can be made such a mess Jul 17 04:59:38 the Ethernet Switch subsystem is actually easier to initialize than an UART Jul 17 05:02:14 ah it seems the problem was fixed... 4.1.2-bone12 defconfig has CONFIG_THUMB2_KERNEL=y again Jul 17 05:05:32 zmatt: the O* driver was done because it wasd too messy to put the omap specific stuff into the generic serial driver Jul 17 05:05:36 like DMA etc... Jul 17 05:05:47 for my use, the S driver worked fine Jul 17 05:06:40 DMA sounds safer to use... the cpu can actually perform posted writes to the UART too fast for the UART to handle (even with sufficient FIFO space), corrupting its FIFO pointers Jul 17 05:07:18 (EDMA uses non-postes writes, max 4 outstanding at any given time, per TC) Jul 17 05:07:25 *non-posted Jul 17 05:09:17 so question is, why'd rcn-ee switch away from omap-serial ? Jul 17 05:14:33 Hello there, can I run TI's Sitara Linux on the Beaglebone black board? Jul 17 05:14:57 Jason___: no idea Jul 17 05:15:07 what board does TI say it is for? Jul 17 05:15:28 rcn-ee's "ti" kernels are derived from TI's tree presumably Jul 17 05:15:58 thanks, here is the imformation: LINUXEZSDK-AM35X: Linux EZ SDK for AM3517, AM3505 Jul 17 05:16:11 that's absolutely the wrong SDK Jul 17 05:16:17 there is SDK from TI for the linux dev Jul 17 05:16:34 AM35xx and AM335x are totally different processors Jul 17 05:16:55 beaglebone black has AM335x Jul 17 05:17:06 LINUXEZSDK-AM335X: Linux Processor SDK for AM3352, AM3354, AM3356, AM3357, AM3358, AM3359 Jul 17 05:17:10 this one. Jul 17 05:17:24 http://www.ti.com/tool/linuxezsdk-sitara Jul 17 05:17:40 here is a link for that information. Jul 17 05:17:46 that would be the right one yes. whether it supports the beaglebone or not I dunno, I'd say check its documentation Jul 17 05:19:03 OK. i see. and is it possible to run WinCE on the beaglebone board? Jul 17 05:20:17 check microsoft's WinEC (as it's called nowadays) website? Jul 17 05:21:19 or google Jul 17 05:21:32 apparently someone did manage to -> http://blogs.msdn.com/b/laurelle/archive/2015/02/26/internet-of-things-installing-mono-linux-and-windows-embedded-on-a-beaglebone-black-board-bbb.aspx Jul 17 05:22:28 see also https://beaglebonebsp.codeplex.com/ Jul 17 05:23:20 next time do a bit of googling yourself :P I know nothing about nor have ever used Windows CE / EC yet I could find this with ease Jul 17 05:23:52 Thank you Jul 17 06:02:47 lol, excellent candidate for "most vaguely described driver ever"... Jul 17 06:02:52 CONFIG_IFB: Jul 17 06:02:52 This is an intermediate driver that allows sharing of resources. Jul 17 06:47:50 Hi Jul 17 06:47:58 I'm new to this field and I am facing a problem Jul 17 06:48:30 When I boot my Beagleboard xM with a demo build, all the LED's are glowing and nothing is happening Jul 17 06:48:46 Can someone please help me out? Jul 17 08:12:02 What do you mean by demo build? Jul 17 13:14:06 hello guys, any reason why BBB on the latest prod jessie is running at 720MHz and not 1GHz ? Jul 17 13:14:30 3.14 ti kernels are running fine Jul 17 13:15:09 you'd need to prod rcn-ee I guess Jul 17 13:15:49 running 4.1.2-ti-r4 from rcn-ee Jul 17 13:27:24 any ideas ? I have a hunch the cpufreq_dt is f...ing up Jul 17 13:27:52 or somehow the dtbs have been copied wrongly from bb-xm Jul 17 19:06:59 rcn-ee: http://pastebin.com/n6QrNHig regarding failure to boot 4.1.1 Jul 17 19:12:12 cc0 ouch 2013.04.. .what's your loadaddr, etc.. (proobally overwriting zimage..) Jul 17 19:12:56 cc0: make sure you are using: loadaddr=0x82000000 fdtaddr=0x88000000 rdaddr=0x88080000 Jul 17 19:14:03 https://wiki.gentoo.org/wiki/BeagleBone_Black i essentially used this guide Jul 17 19:14:22 but, that's odd because i thought i had loaded a newer version of u-boot Jul 17 19:15:57 it's using the one from eMMC... either nuke that partition (dd with /dev/zero) .. Jul 17 19:16:15 or have a simple uEnv.txt with those 3 values set. ;) Jul 17 19:16:36 ahh, ok Jul 17 19:17:02 my knowledge gap of the boot process is becoming quite apparent Jul 17 19:18:33 cc0 i'm a littl surpised you didn't run into that with 3.14.x as that zImage was already fat enough to trigger that over 3.8.x Jul 17 19:18:50 hah, i was in the process of typing, why would emmc u-boot work with 3.14 but not 4.1.1? Jul 17 19:18:52 (basicly with the old default loadaddr, zImage/dtb where overrithing either other, kernel just hard locks in decompression) Jul 17 19:20:03 can i move the updated version of u-boot from the microsd to emmc without problems? Jul 17 19:22:28 yep it should work Jul 17 19:27:44 hm, if i somehow bork the u-boot, can i still access the partition via USB? Jul 17 19:36:19 via USB... I don't think that's in the default boot sequence on the bbb Jul 17 19:38:13 hey, it works :) Jul 17 19:40:18 the uEnv.txt settings did the trick, thanks rcn-ee Jul 17 20:01:29 Hi Jul 17 20:01:58 Look to get beagle puppy Jul 17 20:02:04 Advice? Jul 17 20:02:54 yeah dont plug it in Jul 17 20:03:01 they dont like that Jul 17 22:20:57 I flashed a BBB using the latest flasher image. It runs the cylon LED pattern for a while and then starts flashing all LEDs on and off. This is not the behavior described in al the FAQs I found. This is obviously an error condition because after I reboot it is not working correctly. I'm just trying to figure out what it means. Does anyone know? Jul 17 22:23:01 best way to figure it out is with a serial console cable Jul 17 22:36:04 has someone ever installed gentoo on BBB ? I'm gonna try, just waiting for the serial cable Jul 17 23:09:37 is anyone here running beagleboard/bone + monitor off a battery? Jul 17 23:17:55 monitor?! Jul 17 23:18:03 i have it running with a LCD Jul 17 23:19:24 ds2: where does the LCD takes power from? Jul 17 23:19:46 I would really love to have a portable setup i can put in my backpack and use anywhere Jul 17 23:20:17 as not I *think* (may be wrong) that I need a battery to power the beagle (5v) and a battery to power the usb hub? Jul 17 23:20:25 battery Jul 17 23:21:42 ds2: do you have pictures of your setup? Jul 17 23:21:48 I am quite interested! Jul 17 23:21:50 let me see Jul 17 23:22:35 beaglebone or beagleboard? Jul 17 23:23:02 board, but bone is ok too! Jul 17 23:25:04 http://www.hy-research.com/beagle_mid.html Jul 17 23:25:43 http://www.hy-resarch.com/beagle_mid2.html Jul 17 23:25:48 first is with the BegaleBoard, second is Bone Jul 17 23:25:59 typo Jul 17 23:26:09 http://www.hy-research.com/beagle_mid2.html Jul 17 23:27:10 quite awesome ds2! I am probably looking for something a bit larger (7"), but it's nice to see that was doable! Jul 17 23:28:41 if you follow the link, I have a 7" version too :D Jul 17 23:28:56 links Jul 17 23:29:29 i have a 9" LCD working with it too Jul 17 23:30:40 http://www.hy-research.com/beagle_tab7.html lovely Jul 17 23:32:22 The expansion board contains circuitry to generate all assortment of voltages needed, level shifters, and the touch screen controller, and the battery charger. <-- I see! Jul 17 23:34:38 for the bone, you could potentially use the onboard battery charger and TSC Jul 17 23:35:03 for time reasons, it was easier to reuse the same stuff as the BeagleBoard on the Bone version **** ENDING LOGGING AT Sat Jul 18 02:59:59 2015