**** BEGIN LOGGING AT Sun Jul 19 02:59:58 2015 Jul 19 11:53:25 hello Jul 19 11:54:35 I'm new to beaglebone black, but I'm trying to upgrade the flash via the sdcard. I held the boot button until all four leds were solid and then released. It seems to be taking longer than 45 mins. Jul 19 11:55:13 I've been waiting for all four leds to stop flashing and turn on continously to signal end of programming for at least an hour. Jul 19 11:55:15 davis: what flashing image did you use? Jul 19 11:55:40 hay, can I use pulse audio to play music from my laptop to my jolla over the lan? Jul 19 11:55:41 the debian image Jul 19 11:55:56 I think the "all solid" is no longer in use. I think that was with the angstrom images Jul 19 11:56:06 ahh Jul 19 11:56:37 how do I see if its complete? Jul 19 11:56:51 power it off remove the card, boot. wait a few minutes. first boot takes longer (10-15min sometimes) Jul 19 11:59:35 tbr thank you Jul 19 12:00:26 easiest to verify is if you have a usb-serial adapter plugged into the debug port Jul 19 12:02:05 tbr, a usb/serial dongle and a null modem serial cable? Jul 19 12:05:11 davis: a 3.3V reference UART cable. you can use a usb-serial (RS-232C) adaptor for it, but MUST use a level shifter for the 3.3V reference Jul 19 12:18:05 is this to connect to the DEBUG serial header? Jul 19 12:19:48 yes Jul 19 12:20:14 the header has the pin assignment often found on so called 'ftdi' cables Jul 19 12:20:32 thank you Jul 19 12:21:00 if you order one, make sure it's either 3.3V or can be switched between 5 and 3.3V Jul 19 12:21:31 https://www.adafruit.com/products/954 Jul 19 12:21:51 that is a USB to TTL serial cable debug/console cable for PI Jul 19 12:22:12 yes, that will work too Jul 19 12:34:24 thank you Jul 19 13:26:54 hi guys can anybody recommend a good way to send a float over udp through c++ I can integers to work using unit32_t but cant figure out float Jul 19 13:28:29 mistawright: if in doubt, use an union... Jul 19 13:29:55 but maybe you show us your code and someone can tell you whats the problem is. Jul 19 13:30:13 use an ieee encapsulation :p Jul 19 13:30:31 stt_michael: xml! Jul 19 13:30:32 Humpelstilzchen: my question is how would a structure change the way the data is interpreted once sent from my pc to the beaglebone black Jul 19 13:30:59 it's entirely up to your ijmplementatino Jul 19 13:33:24 mistawright: what structure? Jul 19 15:48:45 _av500_: I'd like to let you know that I've managed to sort my problem Jul 19 15:48:52 I was missing proper UDC support Jul 19 15:49:41 the 3.14.34 kernel from buildroot's GH repo (the newer linux one, not the old kernel one) just wouldn't handle the UDC properly and /sys/class/udc always remained empty Jul 19 15:49:56 both the hacked g_hid and gadgetfs relied on it, but wouldn't tell you unless you enabled debugging options Jul 19 15:50:11 so I'm now using 3.8.13-bone72 which solves that Jul 19 15:51:17 image size tripled though for some reason haha Jul 19 15:51:30 but that's less of a concern and I'll look at that later. Jul 19 15:58:18 you could also go full upstream. 4.1 and up Jul 19 15:58:46 I think the patch set between rcn's version of it and vanilla is very thin Jul 19 15:59:44 now that I finally got this g_hid thing working after spending two full days on it, I think I'm good. Jul 19 15:59:59 I can finally start writing my own code now haha Jul 19 16:00:35 although, after I'm done with this project, I'll still have the bbb and it'd be interesting to get 4.1 on it Jul 19 16:00:56 I feel like I should know a little more about this device tree stuff though because that still eludes me Jul 19 16:01:34 I managed to generate my own dtb a few months ago but I can't recall how, and it doesn't work anymore with today's 3.8 kernel, so now I'm reusing some u-boot magic to find the appropriate dtb from flash Jul 19 16:02:25 speaking of which, saveenv didn't seem to do anything at all Jul 19 16:02:39 so I made a oneliner now in a textfile that I copy and paste on each boot Jul 19 16:06:39 in theory the dtb should work with every kernel. guess where the emphasis lies. Jul 19 16:08:55 theory :p? Jul 19 16:09:08 yeah Jul 19 16:09:17 I don't even know what it is, why it's generated, or why we need it at all. I know I didn't use to need it for 2.6 stuff. Jul 19 16:09:30 it is a description of the hardware Jul 19 16:09:46 2.6 had board-files Jul 19 16:10:12 and ACPI on PC hardware Jul 19 16:10:20 that was simpler once set up, your generated image would just work. (or not :p) Jul 19 16:16:54 <_av500_> Derecho: nice Jul 19 16:17:26 <_av500_> Derecho: saveenv does not work Jul 19 16:17:29 <_av500_> it assumed NAND flash Jul 19 16:17:41 <_av500_> making it write to e.g. sdcard is tbd Jul 19 16:17:44 <_av500_> afaik Jul 19 16:18:00 I thought there was some way to make it write to FAT on newer versions Jul 19 16:18:01 <_av500_> Derecho: there is uEnv.txt for uboot Jul 19 16:18:05 <_av500_> tbr: mayb Jul 19 16:18:06 <_av500_> e Jul 19 16:18:10 <_av500_> but is it enabled? Jul 19 16:19:24 adj: right so saveenv is supposed not to work. so where's the environment coming from? I kinda assumed it'd just write to NAND Jul 19 16:22:10 the default environment is usually compiled into uboot Jul 19 16:22:14 as fallback Jul 19 16:26:38 I see. that's a massive default environment then. Jul 19 18:39:57 Hi, I'm using the standard debian emmc flasher image, and it appears only the UART0 (the debug serial) is available by default. Is there an east wasy to turn on the the other UART devices Jul 19 18:40:14 I've been reading some comflict docs about export dtb and such Jul 19 18:40:30 and really sure which is the way to go Jul 19 18:41:02 I'm not really sure (i mean) Jul 19 19:32:13 foundatron_ the other uarts are exposed by loading virtual capes afaik ... cape_mgr.enable_partno=BBB-UART-nn or similar Jul 19 19:34:09 and that is done in the uEnv.txt Jul 19 19:34:10 ? Jul 19 19:34:27 or can i do that on the fly Jul 19 19:34:28 ? Jul 19 19:36:34 I don't think you can load the dtbs on-the-fly .. so uEnv is the safer bet .. Jul 19 19:38:15 depends on the kernel Jul 19 19:38:20 http://www.armhf.com/beaglebone-black-serial-uart-device-tree-overlays-for-ubuntu-and-debian-wheezy-tty01-tty02-tty04-tty05-dtbo-files/ Jul 19 19:38:41 this article is talking about applying dtbo's after each boot Jul 19 19:38:54 as said, depends on the kernel version Jul 19 19:39:37 i'm using 3.8.13-bone71 Jul 19 19:39:50 that has cape manager Jul 19 19:39:54 at least thats what uname spits out Jul 19 19:40:24 which means you can apply dtbo on the fly Jul 19 19:40:38 or through kernel cmdline too, I guess Jul 19 19:42:26 ok... Jul 19 19:44:56 so i should be able to just add "cape_enable=capemgr.enable_partno=BB-UART1" to /boot/uboot/uEnv.txt? Jul 19 19:45:04 and it will load each boot? Jul 19 19:45:37 foundatron_ .. this is the dynamic principle .. http://tenderlovemaking.com/2014/01/19/enabling-ttyo1-on-beaglebone.html Jul 19 19:47:57 ahh this is perfect Jul 19 19:48:07 I need just a little bit more hand holding Jul 19 19:48:09 thank you Jul 19 19:50:01 np Jul 19 19:50:10 ok I'm out .. long day ahead tmoz .. nite all Jul 20 02:43:50 hey. i just tried to dd this image ( https://rcn-ee.com/rootfs/bb.org/release/2015-07-06/console/bone-debian-7.8-console-armhf-2015-07-06-2gb.img.xz ) onto an SD card but my beagleboard isn't showing up as a usb network device Jul 20 02:44:13 it did with an older version. that image only has one partition it seems, there is no BOOT partition **** ENDING LOGGING AT Mon Jul 20 02:59:58 2015