**** BEGIN LOGGING AT Sun Jul 26 02:59:58 2015 Jul 26 03:39:36 Hi. I bought a Beaglebone black and would like to use the JTAG interface. I'm rubbish at soldering though, so I was wondering if anyone knew an alternative way to get a header attached? i.e. anyplace that sells them already installed, or shops that would do soldering for me? Jul 26 03:50:32 bcran_: finding someone better at soldering is your best bet probably... that's what I did Jul 26 03:50:59 (and give it big legs to stand on... http://gerbil.xs4all.nl/barebone.jpg ) Jul 26 03:56:00 zmatt: yeah, that would be the best way - but being fairly new to the area I don't know anyone else into electronics. Just found a repair shop that might do it though, so I'll phone them on Monday Jul 26 03:56:39 amusingly it is actually possible to have the am335x control its own jtag port provided the pins are externally driven/pulled high, but that still requires solderwork and is obviously not the most practical way to use jtag ;) Jul 26 03:57:17 you already got the connector? because it's not exactly a standard one Jul 26 03:57:54 yup - got it a few days ago. But I suspect I've ruined *both* the board and the connector so will go get a new one before heading to the shop! Jul 26 03:58:52 got a better soldering kit and a new board from Radioshack yesterday at least - was surprised to find it's still around and has decent stuff Jul 26 04:00:23 you can of course have 'em take a look at it to see if it's salvageable Jul 26 04:01:01 a short-circuit in a wrong place there will make the board dead but not necessarily ruined Jul 26 04:02:27 but yeah it's really annoying they made it so hard to use jtag Jul 26 04:02:28 I might do that - would be good to have a spare board for future use Jul 26 04:05:31 self-debugging is actually still an interesting possibility, e.g. a PRU core could provide full debugging of the cortex-a8 Jul 26 04:05:49 but still needs nTRST driven high, and it has an on-board pull-down Jul 26 04:07:56 (connecting it to vcc could be done with a single wire between two JTAG header pads though) Jul 26 04:10:32 it's really obnoxious... all debug registers are actually memory-mapped Jul 26 04:11:08 but using debug functionality is only possible if you first set a bit that's only accessible via JTAG Jul 26 04:15:09 even though that functionality would also be extremely useful without JTAG: it gives an OS the ability to use watchpoints Jul 26 07:57:09 Hopefully this is a dumb/common question: I just pulled out my BeagleBone White after ~2y of non-use, downloaded and installed the latest image, and I can't use "opkg". Are packages installed with apt-get these days? Jul 26 08:01:21 dohzer: if you put on a debian image, then yes Jul 26 08:06:43 hmmm... it is a Debian image. I must have missed the difference. Thanks for the info Jul 26 08:56:21 Trying to flash my BBB with debian-8.1 ... after a few minutes of the "night rider" LED run I get flashes of all 4 LED's going QUICK-QUICK-OFF ... what's broken? Jul 26 08:56:51 which board revision do you have? Jul 26 08:57:08 Where do I find its revision? Jul 26 08:57:23 sticker on the side of one of the connectors IIRC Jul 26 08:57:36 or on the PCB Jul 26 08:57:56 Does A6 sound righgt? Jul 26 08:57:59 right? Jul 26 08:58:58 yeah Jul 26 08:59:15 so that board only has a 2GB eMMC, make sure you don't try to flash a 4GB image Jul 26 08:59:49 Check ... I got this one BBB-eMMC-flasher-debian-8.1-console-armhf-2015-07-08-2gb.img.xz Jul 26 09:05:11 I also verified that the md5sum of the xz is correct. Jul 26 09:05:30 is there doco anywhere on what which blinkenlight sequence means? Jul 26 09:12:43 temping: not sure Jul 26 09:12:53 temping: it might be that it already means 'done' Jul 26 09:14:21 tbr: I didn't get anything in dmesg on the Linux box it's hooked up to after a reboot, though ... I just did what Einstein defines as insanity, did a fourth repeat, and this time the LED's went soilid. Go figure :/ Jul 26 09:15:14 temping: note that it takes 5-10min on first boot before you get anything on usb IIRC Jul 26 09:15:29 temping: if you interrupt that first boot it breaks the install, in my experience Jul 26 09:17:25 It's all good, successfully ssh'ed into the new 8.1 install via usb Jul 26 09:17:31 thanks for your help Jul 26 19:21:52 i'm trying to clean up my build and move past prototyping. i'd love to replace this mess of individual wires with a single ribbon cable. anyone have a good example? Jul 26 19:22:25 this socket -> pins ribbon seems like one option: http://www.modmypi.com/raspberry-pi/gpio-and-breadboarding/jumper-wires/raspberry-pi-gpio-socket-connector-to-labelled-pins-male-150mm Jul 26 19:58:31 hi, I'm trying to install fedora to my beaglebone, and following these instructions: https://fedoraproject.org/wiki/Architectures/ARM/F22/Installation#For_the_BeagleBone_.28_Black_.26_White_.29 Jul 26 19:58:43 after I did that dd, the root partition became blank Jul 26 19:58:52 boot is still readable Jul 26 19:59:20 how do I make the image bootable without killing the filesystem? Jul 26 23:56:50 zmatt, i was under the impression that i2c-2 went to P9-19 and P9-20 by default Jul 27 01:06:53 does anybody know how to determine which pins are I2C on the elinux ubuntu image? I think SCL is P9_19, SDA P9_20, but want to confirm Jul 27 01:07:09 i guess it must be define in the device tree file somewhere Jul 27 01:09:03 you can check device tree (decompile the dtb, find its source, or inspect the live version in /proc/device-tree ) Jul 27 01:09:11 or check the actual pinmux Jul 27 01:09:24 how do you check the actual pinmux? Jul 27 01:11:35 /sys/kernel/debug/pinctrl/44e10800.pinmux Jul 27 01:12:00 the file "pins" contains the raw pinmux Jul 27 01:13:59 I have a spreadsheet with pin data aggregated from multiple sources, I personally find it useful -> https://docs.google.com/spreadsheets/d/1CK5c-Cs8G1RtzGo-J3VJsD9m5K-fp06AncgeYWsdjSU/edit Jul 27 01:15:09 zmatt, thanks that is super helpful Jul 27 01:15:11 the Pinmux tab is generic for the AM335x, the BBB tab is the same table but customized for the BBB (e.g. hiding unusuable functions, showing which pins corresponding to expansion headers Jul 27 01:15:27 zmatt, in the pins file, are the pin numbers with respect to the AM3358? Jul 27 01:17:05 the pin numbers are basically the only way to unambiguously identify IO pins of the Subarctic die (i.e. AM335x / DRA61x parts) Jul 27 01:17:17 they're also indices in the pinmux array in the control module Jul 27 01:17:49 so 0x44e10800 + 4 * (pin_number) is the address of the pinmux register Jul 27 01:19:35 for the BBB the most relevant tabs are BBB and BBB2, and possibly Boot and Elec Jul 27 01:22:06 (apart from graying out unusable functionality, the BBB tab is a superset of the information found on the Pinmux tab Jul 27 01:22:09 ) Jul 27 01:23:13 hmm Jul 27 01:23:32 do you know if i2cdetect actively probes the bus each time it is run Jul 27 01:23:33 ? Jul 27 01:23:40 or is it done on boot or something Jul 27 01:24:07 I'm not sure how much auto-detection is done on the i2c bus, if any (other than by bone_capemgr) Jul 27 01:24:20 there's in general no reliable way to identify i2c devices Jul 27 01:24:27 :) Jul 27 01:24:36 and attempts to probe may actually muck things up Jul 27 01:25:49 generally you'd explicitly list the i2c devices on the bus via device tree Jul 27 01:28:00 DLPeterson: btw, I did mention the i2c-2 mux: 04:14 < zmatt> note that you can also connect devices to i²c 2, which in a typical bbb device tree is already enabled and muxed to { P9.20, P9.19 } for cape detection Jul 27 01:28:59 what i2c device are you trying to use? Jul 27 02:00:53 zmatt, I'm trying to use a Invensense MPU-6050, don't have a preference on which peripheral of the BBB; I have no capes Jul 27 02:01:30 do you happen to know if it has a kernel driver? Jul 27 02:01:51 as, it does Jul 27 02:06:51 see https://groups.google.com/forum/#!topic/beagleboard/hqqecmOjpTU for efforts to get the driver to work Jul 27 02:11:47 sounds like the driver currently requires patches to work, and most people just use i2cdev from userspace Jul 27 02:26:38 DLPeterson: sounds like the MPU-6050 also supports SPI instead of I2C Jul 27 02:31:26 oh, nm, that's the MPU-6000 Jul 27 02:31:36 so you're stuck with i2c, too bad **** ENDING LOGGING AT Mon Jul 27 02:59:58 2015