**** BEGIN LOGGING AT Sun Jul 10 02:59:58 2016
Jul 10 04:14:03 <zmatt> lol... xorg.conf manpage:
Jul 10 04:14:09 <zmatt> VIDEOADAPTOR SECTION
Jul 10 04:14:09 <zmatt>        Nobody wants to say how this works.  Maybe nobody knows ...
Jul 10 16:34:36 <Sinestro> I can't get OpenOCD to work, and I'm not sure if it's not working because I did a shitty job of soldering the connector (or, eep, lifted a pad/trace)
Jul 10 16:38:39 <Sinestro> I get "Memory write failure!" whenever I try to do anything
Jul 10 17:15:31 * Sinestro gurgles incoherently, blood pouring from her mouth as you hear nothing but a strange croaking voice trying to scream 'OpenOCD'
Jul 10 18:07:45 * Ragnorok makes mental note to avoid OpenOCD blood spilling softare
Jul 10 19:20:04 <Sinestro> All I can find online are complaints about it not working
Jul 10 19:20:15 <Sinestro> Is it actually possible to use OpenOCD to debug a BBB?
Jul 10 19:43:40 <tbr> I'd very much expect so
Jul 10 19:55:44 <Sinestro> Well, that leaves two possibilities. Either I messed up while installing the JTAG header, or my computer is just terrible
Jul 10 20:01:56 <Ragnorok> I have JTAG but wasn't aware it was possible to get it it work with a BBB under Linux.
Jul 10 20:12:00 <Sinestro> I see references to it
Jul 10 20:12:06 <Sinestro> And I really, really don't want to use CCS
Jul 10 20:12:25 <Sinestro> I hate Eclipse, I don't think that poorly done vendor customization is really what it needs
Jul 10 20:15:16 <Sinestro> There are instructions online, they just don't 'work'
Jul 10 20:20:10 <Ragnorok> To each their own.  I've been using Eclipse since v1 and I've done all my development in CCS.  (shrug)  And online intructions typically are "you get what you pay for."  (wry grin)
Jul 10 20:34:55 <tbr> Sinestro: which jtag adapter are you using?
Jul 10 20:35:11 <Sinestro> XDS100v2
Jul 10 20:35:29 <tbr> mmm
Jul 10 20:35:42 <Sinestro> They're all FT2232s inside
Jul 10 20:35:45 <Sinestro> so it should work
Jul 10 20:35:47 <Sinestro> and it... kinda works
Jul 10 20:35:59 <Sinestro> It's like it can't sync up with the CPU or something
Jul 10 20:36:33 <Ragnorok> I am under the impression Linux prevents that, which is why I can't use mine, which is the same unit/version.
Jul 10 20:36:59 <Sinestro> I'm aware that you can't (easily) use it to debug kernel code
Jul 10 20:37:17 <tbr> it should still show up in the chain etc
Jul 10 20:37:22 <Sinestro> But I'm trying to load something right into place and run with it
Jul 10 20:37:28 <Sinestro> It is
Jul 10 20:37:38 <Sinestro> I can start and halt and stuff
Jul 10 20:37:57 <Sinestro> It's just the trying to do any debugging that doesn't work
Jul 10 20:39:12 <Ragnorok> Not just kernel.  Any Linux code.  Or so I believe after researching it; machineKit and bare metal were the only options I found that could work with JTAG.  I'm certainly no guru though.
Jul 10 20:39:21 <Sinestro> That's what I mean
Jul 10 20:39:31 <Sinestro> And actually, Linux isn't involved in this anywhere
Jul 10 20:40:11 <Sinestro> It's ARM assembly and C being compiled with arm-none-eabi-gcc on OS X and trying to be executed raw on the BBB
Jul 10 20:40:18 <Ragnorok> Oh.  Sorry.  Didn't get bare metal out of anything so far.  I'll quit being static then.
Jul 10 20:40:37 <Sinestro> Oh, I didn't say that upfront?
Jul 10 20:40:45 <Sinestro> Good job, me.
Jul 10 20:40:45 <Ragnorok> Mighta.  I could have missed it.
Jul 10 20:43:05 <Sinestro> JTAG-DP STICKY ERROR MEM_AP_CSW 0x2800062, MEM_AP_TAR 0x402f0400
Jul 10 20:43:36 <Sinestro> that's the specific error, everything I see is that it's an bug in openocd 0.4 and older, when I'm running 0.9
Jul 10 20:47:31 <Sinestro> Okay, it can see the 'jrc' but not the 'dap' or the 'm3_dap'
Jul 10 20:48:01 <Sinestro> Imagine a totally fictional scenario where I have no idea what that means.
Jul 10 20:51:52 <Sinestro> Okay, it is somehow able to get basic communication
Jul 10 20:52:11 <Sinestro> Since it knows if I halt it when U-Boot is running that the caches are on
Jul 10 21:08:17 <Sinestro> Ooh, I managed to get a new error
Jul 10 21:08:26 <Sinestro> Memory write failure! WARNING! The target is already running.
Jul 10 21:08:32 <Sinestro> Immediately after a halt, no less
Jul 10 22:16:11 <Sinestro> Okay, that seems to be the problem
Jul 10 22:16:16 <Sinestro> I can reset the board and write to memory
Jul 10 22:16:18 <Sinestro> But I can't halt
**** ENDING LOGGING AT Mon Jul 11 02:59:58 2016