**** BEGIN LOGGING AT Sat Jun 30 03:00:03 2018 Jun 30 03:19:57 I got more jokes for some eastness. sudo apt install sl and then use the cmd sl. Jun 30 03:20:10 Sorry. Jun 30 03:23:10 [ whereis my brain? Jun 30 03:32:10 bash: [: missing ] Jun 30 03:35:22 Frz: Hello...what are you doing? Jun 30 03:53:36 Can I use a .tk file to run a GUI in the shell env? Jun 30 03:53:40 On the BBB? Jun 30 05:13:23 How can I change users on the BBB distro we use? Jun 30 05:15:38 su? Jun 30 05:20:41 forget it. I got it now. Sort of. Jun 30 08:31:13 Hello Jun 30 08:31:50 I am interested in developing my asset tracking system on Pocket Beagle Jun 30 08:32:22 May I know what all I need to have apart from the Pocket Beagle?? Jun 30 08:33:20 I intend to have the RFID module communicate with the Pocket on UART? Jun 30 08:33:48 why are you phrasing that as a question. you're unsure what your intentions are? Jun 30 08:34:29 Sorry. Jun 30 08:34:56 and the question to that is broad and vague and not likely to get a useful response Jun 30 08:35:19 I am sure of interfacing the RFID on UART. Jun 30 08:35:33 it sounds a bit like you're asking "hey, I have an idea, who wants to design it for me?" or something Jun 30 08:35:57 No.. That's not my intention. Jun 30 08:36:38 I just need to know... What all is needed except the Pocket and RFID? Jun 30 08:37:02 if the rfid module runs on 3.3v and uses an uart interface, then all you need to interface them is four wires (ground, power, rxd, txd) Jun 30 08:37:08 I mean where will I get the Software toolchain? Jun 30 08:39:07 ehm, basic development tools (including c/c++ compiler, perl, probably python) are installed on the default debian image, and you can simply install additional stuff using apt Jun 30 08:42:47 it's just a debian linux system. the only thing you may have to get used to (depending on your background) is the lack of gui on the pocketbeagle itself, but you can of course write code on your own computer and sync it to the pocketbeagle Jun 30 08:43:01 and then compile (if applicable) and test it there Jun 30 10:03:28 hi Jun 30 10:04:37 ı am having difficulty in the ethernet connection Jun 30 10:05:08 ı have a beagle bone black debian rev c Jun 30 10:06:47 ı have finally manged to download and intall the drivers with windows 7 Jun 30 10:07:07 in cloud9 Jun 30 10:07:52 ı cannot see the static ıp of bbb in eth0 when ı ifconfig Jun 30 10:08:55 mjkllş Jun 30 10:13:38 what do you mean? Jun 30 10:15:12 eth0 normally doesn't have a static ip, it uses dhcp **** BEGIN LOGGING AT Sat Jun 30 20:18:14 2018 Jun 30 21:25:31 Can we connect a serial terminal to a maybe bricked beaglebone and see the terminal output? Jun 30 21:30:23 depends on if it's really bricked or only not booting Jun 30 21:33:54 vagrantc: How can I determine that? Right now only the power LED works, it doesnt show up as a USB device on the computer either.. Jun 30 21:34:55 I tried checking the /dev/tty.** to see the serial port number. Does that only work if I connect to serial debug?  Jun 30 21:35:25 All of this makes me feel that it is bricked..? Jun 30 21:36:33 checking /dev/tty where? Jun 30 21:37:17 https://elinux.org/Beagleboard:BeagleBone_Black_Serial Jun 30 21:37:44 presuming you're talking about the beaglebone black Jun 30 21:38:31 Nope, sorry I should've mentioned, its a beaglebone green Jun 30 21:39:06 on my macbook where the beaglebone is connected Jun 30 21:39:48 yes, it needs to be connected to the serial debug header Jun 30 21:41:38 I see, is there any other options? Jun 30 21:42:27 Or at least, how can I isolate the problem here? Is it bricked? Or is it something else? Jun 30 21:42:42 simplest thing is to see if you get output on the serial Jun 30 21:43:06 trying to debug without that is not trivial Jun 30 21:43:11 without the cable? Jun 30 21:43:30 you're going to need a cable to do that, yes. Jun 30 21:43:59 okay. Do i need it to perform the recovery as well? Jun 30 21:44:19 depends on what output comes out of the serial cable Jun 30 21:44:43 you could blindly try to re-install and hope ... but if you're having issues, a serial debug cable is invaluable Jun 30 21:44:58 okay. So I guess there is nothing we could do without the cable Jun 30 21:45:21 if you have microSD, you might be able to get it to boot a known working image from that Jun 30 21:46:09 not quite as familiar with the green ... so take it with a grain of salt. Jun 30 21:47:12 Yes, i do have a microSD card, and that'd great if I can get it to boot with it. Jun 30 21:52:19 Are you suggesting to burn the OS image on SD card, and then use it in green?  Jun 30 22:06:40 shreeya: yes, just download the latest stretch-iot image from https://beagleboard.org/latest-images and flash it to SD card Jun 30 22:07:41 usually in the (rare) cases that a beaglebone is genuinely bricked (due to hardware damage), it won't even power on anymore Jun 30 22:11:04 I had flashed debain on emmc and then I was trying to reflash it with ubuntu, it's then when all the leds shut down, and the beaglebone has never booted since then. Nor does it boot from the SD card. Jun 30 22:11:25 Only power LED works when I give power to it. Jun 30 22:11:50 zmatt: ^^ Jun 30 22:16:55 shreeya: try powering up with the S2 button held down (i.e. make sure the beaglebone is off, sd card inserted, hold S2 down, apply power. you can let go of S2 once the power led turns on) Jun 30 22:18:02 (this bypasses the bootloader on eMMC, which may be preventing boot e.g. if it is corrupted) Jun 30 22:21:49 zmatt: I've tried that already but didn't work. Jun 30 22:24:44 well it's difficult to remotely diagnose something like this Jun 30 22:24:59 (e.g. how sure are you the sd card is flashed correctly?) Jun 30 22:26:02 it seem very unlikely to me that flashing ubuntu (or attempting to) could result in hardware damage Jun 30 22:40:57 just checked the shasum, matches with original file... so that is enough, right? Jun 30 22:59:28 In order to use the DSP on the BeagleBone Black, we apparently need to use TI's proprietary binaries. Jun 30 22:59:52 Did someone write a FOSS replacement, I'm wondering? Jun 30 23:00:16 there's no dsp on the beaglebone black Jun 30 23:00:25 either you mean the gpu on the beaglebone, or the dsp on the beagleboard-x15 Jun 30 23:03:30 Yes, I think I'm referring to the DSP on the Beagleboard X15 - Jun 30 23:03:47 I was reading this page - https://elinux.org/BeagleBoard/DSP_Howto Jun 30 23:03:47 it doesn't require any proprietary binaries (unless you mean the C/C++ compiler) Jun 30 23:04:10 It suggests we need TI's DSP binaries, but I wasn't sure Jun 30 23:04:25 or is it out of date? Jun 30 23:05:44 that's talking about the old omap3 beagleboard Jun 30 23:05:58 whose DSP was part of the video encoding/decoding subsystem Jun 30 23:06:08 the binaries referred to are codecs Jun 30 23:06:25 none of this has anything to do with the beagleboard-x15 Jun 30 23:06:34 hint: "view history" on the wiki page shows last edit in 2010 Jun 30 23:06:35 :) Jun 30 23:07:11 I guess I'm rather mixed up then - I have the original Beaglebone somewhere, which was what I was interested in. Jun 30 23:07:19 (rathe rthan the X15, I guess) Jun 30 23:09:16 Thanks. Jun 30 23:10:21 you don't need binaries to run software on its DSP in general either, everything needed to use the DSP subsystem is publicly documented and quite decently so. but like I said, the software it's referring to is for video en-/decoding and those codecs are definitely proprietary Jun 30 23:17:59 That makes sense. Thanks for the clarification. **** ENDING LOGGING AT Sun Jul 01 02:59:59 2018