**** BEGIN LOGGING AT Tue May 03 02:59:58 2016 May 03 03:04:23 if it works on wheezy its the new pinmux driver i mentioned May 03 03:21:27 Has anyone had success with the RS485 to Can cape? May 03 03:28:52 I don't have it but looking at it now, I can't imagine why anyone would take issue with it May 03 04:03:35 Can anyone here running Jessie check to see if the analog.js example works for them? About to try Wheezy, but would like to know if I am one of few people having an issue with Jessie. May 03 04:03:57 PDogJr: meaning bad or good way? May 03 04:04:06 When I run it I get a write error May 03 04:05:05 meaning that it looks like a fairly straightforward cape and I don't see why anyone would have trouble with it May 03 04:05:40 between Wheezy and Jessie (really Linux 3.8 and 4.x) the cape management interface was rewritten. It's different in Jessie. May 03 04:05:54 The same code won't necessarily work May 03 04:06:02 unless it's especially written to do it both ways May 03 04:06:27 Should the built in examples not be usable though? May 03 04:07:07 One would expect so but not everything can be tested. May 03 04:07:11 The issue seems to be with bonescript May 03 04:07:25 As Python code does work May 03 04:07:41 No bonescript code will run for me though May 03 04:09:33 I found someone saying to update bonescript, but attempting so based on the instructions on git just throws endless dependency errors May 03 04:09:38 I dont have a bbb to try Jessie on, my only one is in service with wheezy and half fried from ESD apparently too May 03 04:09:59 that was a nice surprise today May 03 04:11:21 Does not help that my knowledge of Linux is sketchy at best, anyway, that's fine. Maybe someone else has a Jessie board to try? May 03 04:12:37 Been using the BB to learn Linux and make various projects. May 03 04:18:43 so learn how to flash wheezy and test it. May 03 04:20:35 I know how to flash the images. As expected, it works. But I need the newer kernel.... May 03 04:21:46 what for? May 03 04:22:03 node-red May 03 04:22:18 or more specifically May 03 04:22:27 node-red-beagle May 03 04:22:41 which does not seam to work on wheezy May 03 04:44:51 Engine: there are a number of kernels you can apt-get .. but if you want something mainline/bleeding-edge ... you might need t oroll your own. Suggest perhaps looking at... May 03 04:45:38 .. https://www.eewiki.net/display/linuxonarm/BeagleBone+Black for BBB May 03 04:45:53 but you probably won't get a capemgr May 03 04:45:56 if you need it May 03 05:52:29 vermit: Does the official Jessie image not maintain original functionality? May 03 05:53:20 the official images are fine .. hence why they are Official :D May 03 06:09:34 But yet I can't run anything on bonescript. May 03 06:42:37 yeah that may still be one glitch May 03 06:43:14 I think there has been some odd permission/path issue that occasionally rears its head in here .. but i don' tknow whether its documeted (or even fixed) .. bloody beagle* documentation May 03 11:19:25 For anyone having issues with bonescript on 4.x kernels, here is a page saying why this is. Sadly it does not have a fix. http://crufti.com/node-red-on-the-beagle-bone-black/ May 03 11:32:47 can anyone please explain how come TI are still releasing software for the SoC the BBB uses? May 03 11:34:54 because the SoC is going to be around for a looong time and they support it? May 03 11:36:34 hi tbr, May 03 11:37:15 I see that rcn-ee is adding fixes released by TI to his kernel May 03 11:38:45 Isn't TI planing to replce the SoC with a new module? wont they put their effort to that new SoC and ditch out current chip? May 03 11:39:26 I also do not understand how you can release a graphics core without having a driver to test it with May 03 11:39:30 there are many SoCs May 03 11:39:53 there are SGX drivers AFAIU and I'm sure TI supports that May 03 11:39:55 maybe some minor bug fixes, but it seems this SoC is still under development May 03 11:40:40 tbr: so they included a graphics core on the silicon and did not write any driver for it? May 03 11:40:48 isn't this odd? May 03 11:41:16 citylight2: did you ignore what I just said? there *are* SGX drivers May 03 11:41:32 oh May 03 11:42:04 ok, except for the graphics, what did TI develop for this chip after it was released? May 03 11:42:26 where there any missing drivers? May 03 15:30:07 Hi anyone able to help with connecting the BBB out of the box to Windows 10? May 03 15:31:28 I have plugged in the new device and opened the start.htm but unfortunately the Steop1: Plug in BBB via usb doesnt go green but allows me to install the drivers. Unfortunately trying to connect through the browser just times out =/ May 03 15:32:17 If I plug it into my friends ubuntu machine the step 1 turns green so I can only assume it is a windows 10 issue but havent found a solution in the last few hours May 03 15:33:32 http://beagleboard.org/getting-started#step2 May 03 15:34:25 so are the drivers installed? May 03 15:34:33 do the LEDs blink? May 03 15:34:45 yes and yes May 03 15:35:00 leds blinking away and when i installed the drivers i got all ticks May 03 15:35:05 check your network settings May 03 15:35:16 it should show up as a network device May 03 15:36:06 Yes it shows up as a "unidentified network, no network access and shows as Ethernet 2" May 03 15:37:36 check its status and if it received an IP address May 03 15:37:50 One thing I should mention: in the guide I have it says be careful not to delete the "MLO, u-boot.img or the uEnv.txt" however when the file explorer pops up I only have the the uEnv.txt :S May 03 15:38:20 how do i do that please? May 03 15:38:32 that is normal on newer images (I think) May 03 15:38:52 usually there should be a way to check 'status' for an connection May 03 15:38:58 don't have a win10 machine at hand May 03 15:40:18 well it is saying connected but no internet access, I'm not sure how to check if it has an ip but assumed it was the default as stated in the guide (192.168.7.2) May 03 15:41:22 192.168.7.2 is the default for the beaglebone, 192.168.7.1 is the default for the PC side May 03 15:41:46 also it's perfectly normal that the BBB doesn't provide "internet connectivity" as it only provides connectivity to itself May 03 15:42:06 have you tried opening http://192.168.7.2 in a browser? May 03 15:43:11 ahhh okay so i just turned the network adapter off then on... seems to work now. Sorry if i wasted your time and thank you May 03 15:43:33 np May 03 15:43:38 have fun May 03 15:43:54 cheers May 03 16:04:04 how could I use the BBB as a full desktop computer when it needs a host system to read from the serial console? any hints? May 03 16:06:43 Host system? Do an HDMI monitor and an USB keyboard not suffice? May 03 16:08:05 Display won't work when using the terminal May 03 16:08:21 that's what I'm trying to solve here :) May 03 16:09:02 I am not using some linux distro with a fancy GUI, I'm just using OpenBSD May 03 16:09:10 So you're locked into use the serial console? May 03 16:09:34 I would expect any VT100 terminal to work. (wink) May 03 16:10:33 there are no modern terminals :( May 03 16:12:29 Correct. No one does that anymore. Your options are use a host system to emulate a terminal, find an old terminal that still works, build a terminal using some embedded system, or remote into it. I don't see what else is available. May 03 16:13:53 how can people use the BBB as a desktop then :/ May 03 16:13:54 Or use a GUI and HDMI. That is an option, just not one that uses the serial console. May 03 16:13:59 ^^ May 03 16:15:48 Technically it's not a desktop without a GUI to be "the desktop". It's a commmand line workstation. I do command line all the time .. from a GUI window. I can't remember the last time I used tty as the primary means of interaction with a box, including a BBB. May 03 16:21:31 Is there any more work needed to make drivers for the SoC used in the BBB> May 03 16:21:34 ? May 03 16:22:08 X.org is just a terminal multiplexer anyway… ;-) May 03 16:22:29 citylights__: are you referring to something specific? May 03 16:22:50 I must say I was happy with it a long time ago, but as I see more commits, I ask May 03 16:23:07 as there is _always_ some driver that could be improved or written or rewritten May 03 16:23:18 The Linux kernel will *never* be "done" May 03 16:23:24 for example there was the musb issue, if I remember May 03 16:24:15 I do not mean new features, I just mean being able to take advantage of the SoC May 03 16:24:55 for example the network driver may use the PRU and run faster May 03 16:33:17 1moreFINAL May 03 17:09:15 hi all. having trouble with am335. was working before and now it isn't happy with driver. May 03 17:09:43 is there a way to test if hardware has issue? tried on 2 computers, but it was working before on 1 of them May 03 23:23:22 I am using an image based on seeed's Debian 8.3 image, and it is randomly shutting down. When it happens, all four software controlled LEDs are off, but the power LED stays on. I had a serial console plugged in at some point, there are no messages. I had a loop of ps auxfww running, there is no special command running when it stops. Does anyone know what can cause this? May 03 23:23:39 This happens both on Beaglebone Blacks and Greens. May 03 23:25:00 how many have you tested? May 03 23:25:08 is there a specific time when it stops? May 03 23:26:04 can you link the exact image? May 03 23:29:30 http://most.mse.mtu.edu/franklin/BBB-eMMC-flasher-debian-8.3-athena-armhf-2016-04-13-1gb.img May 03 23:29:41 I've seen it happen on at least 10, I think. May 03 23:30:26 It happens randomly; sometimes within minutes, sometimes it takes a day, sometimes it doesn't seem to happen at all. May 03 23:31:31 I've never seen it happen with the older (Debian 7) images, so I'm suspecting the kernel may have something to do with it. May 03 23:34:00 Or wait! I just remember there was a warning in the build scripts about using qemu (which it does) to run them; can that cause these problems? Should I run it on a Beaglebone instead? May 03 23:40:28 this is in qemu? May 03 23:40:52 No, I ran the image build scripts on my desktop, which is amd64; it uses qemu for some parts of the build. May 03 23:41:16 oh ok May 04 00:14:31 uhm. lol. May 04 01:11:21 shevek: just sharing different results... debian_version = 8.4 uptime = 20 days, 4:55 on a bbb **** ENDING LOGGING AT Wed May 04 02:59:58 2016