**** BEGIN LOGGING AT Thu May 11 03:00:02 2017 May 11 14:00:53 i have a beaglebone black connected to a replicape and then to a 4dcape-70t display. May 11 14:01:08 why does the display stay black? May 11 14:01:22 the 2 led's is on May 11 14:08:13 no one here to tell me what i do wrong? May 11 14:46:09 Give it some time guest May 11 14:46:39 People probably idle when they sleep May 11 15:45:07 hey guys. anyone familiar with the bluetooth on the beaglebone green May 11 15:46:05 whenever i try to init the BLE, its being blocked by rf-kill May 11 15:46:22 but when i list rf-kill no hci0 devices show May 11 16:35:39 Hello! I got a question about the TI Wilink 8 Wifi module. The schematics of this board says the wifi-module is connected via the mmc1 pins to the cpu. so can you use the eMMC flash and the wifi-module at the same time so that the 2 modules share the mmc1 pins? and is it possible with the beaglebone black to connect another sd-card via the mmc2 pins, because the schematics say that only the data pins are available at the pin headers. May 11 17:04:59 im at a uboot comandline, can i force a boot from the sd card May 11 17:05:13 holding downt he boot button didn't work, i'm trying to a flash a 2G early rev May 11 19:05:14 ayjay_t: uboot normally prefers booting sd over booting emmc May 11 19:06:26 the boot button is only required if you need to force RBL to load u-boot from sd instead of emmc (e.g. if the one on eMMC is hosed, or just too ancient to boot the sd card) May 11 19:07:38 hotschi: no you can't use eMMC if you connect another device to the same pins May 11 19:07:56 hotschi: and all mmc2 pins are available on the expansion headers May 11 19:08:08 iirc one is on P9 instead of P8 May 11 19:24:16 zmatt: one of the images that we downloaded was bunk, i guess, but we found one off rcn's site that looks much more promising May 11 19:29:32 http://elinux.org/Beagleboard:BeagleBoneBlack_Debian is generally the place to go May 11 19:29:51 (or indeed https://rcn-ee.com/rootfs/bb.org/testing/ ) May 11 20:01:15 Anyone know the dimensions of a BB Blue? May 11 22:05:12 Hi all! Can anyone tell me which file points to the script that flashes the 2G beaglebone? I'm looking in uEnv.txt but that seems to be the wrong place. May 12 01:11:56 Is it possible to access USB through the header pins on the beagle-bone? May 12 01:22:32 no May 12 01:27:49 So what options do I have for >1Mbps data rates? May 12 01:28:04 On the headers May 12 01:28:15 SPI, GPMC, PRU, MCASP, etc May 12 01:28:39 SDIO May 12 01:32:13 I'm redesigning a cape I made a while ago. Part of the cape has a USB to Half-Duplex converter based off an ATmega32u2. It is working well, but I'm trying to eliminate the need for a separate USB cable. May 12 01:35:38 I can design hardware all day long, I'm just terrible when it comes to programming May 12 01:39:41 actually for 1Mbps, the serial ports can do that May 12 01:39:58 I do both :D May 12 01:44:17 So right now the dataflow looks like this: C++ Program -> USB Driver -> USB -> ATMega -> Half-Duplex Servos. My biggest issue is that the USB servo driver code looks rather complex and my runtime code already works properly with the driver. Is there some stupid simple quick solution that could solve this problem, or should I consider refactoring the drivers? May 12 01:44:59 what kind of servo are you talking about? May 12 01:45:22 http://www.trossenrobotics.com/dynamixel-ax-12-robot-actuator.aspx May 12 01:46:02 The hardware I used to reference my design (and ultimately copied the firmware from) is here: http://www.xevelabs.com/doku.php?id=product:usb2ax:usb2ax May 12 01:46:55 and a render of my project: http://imgur.com/a/cdB0D May 12 01:47:26 I wonder if you can just use a uart on the bone May 12 01:50:00 Which would require writing some kind of interface or driver code wouldn't it? May 12 01:51:50 okay, nevermind! I think I remember writing that already, I just have to find the code, I know this project started out using a UART port... I forget why I switched May 12 01:55:57 not really May 12 01:56:03 UART is pretty straight forward May 12 01:56:16 only thing I don't know is how tight are the timing requirements May 12 01:56:34 assuming there is no tight timing, it can be as simple as "echo SFKSDFKSDFKSDF > /dev/ttyS1" May 12 01:58:27 okay, and if it turns out there are timing requirements? how about the half-duplex triggering, the last time I saw this done it was using a tri-state buffer and a gpio to switch May 12 01:59:47 there is the PRU... May 12 02:00:24 okay, you've at least nudged me in a better direction, thank you for the help! May 12 02:00:36 I'm going to have to look into this a little more May 12 02:02:42 if you don't know, the PRU is a microcontroller on the same die May 12 02:02:48 could replace the avr May 12 02:03:23 how would I get started learning about that? May 12 02:03:37 search for PRU or PRUSS on search engine May 12 02:05:56 and which UARTs are open for use? May 12 02:06:35 pretty much any except for the console one May 12 02:06:47 only tricky part is finding out if you have a conflicting pin May 12 02:07:07 each pin on the header that is not power/ground/analog/power button can have up to 7 functions May 12 02:07:22 selecting which one is done by the pinmux **** ENDING LOGGING AT Fri May 12 03:00:02 2017