**** BEGIN LOGGING AT Thu Nov 09 03:00:03 2017 Nov 09 03:01:33 If I was to find out my pin states for the BBG (which has the Motor Bridge Cape working) and my pin states for the BBB (which has the Motor Bridge Cape not working), would changing the state of the pins be an example of a step to make the MBC (Motor Bridge Cape) work for the BBB? Nov 09 03:01:34 ... Nov 09 03:07:10 For instance, the Header Pins may be in a specific mode (all of them for some reason) on the BBB versus the BBG. Nov 09 03:07:35 ... Nov 09 03:08:36 I would have to change each, separate pin mode on each header pin to suit the Motor Bridge Cape and that functionality. Nov 09 03:09:20 I think this is the answer. Does anyone disagree or does anyone have experience w/ Capes at all that can tell me something? Nov 09 08:05:19 Hello. Are EMU0/1 absolutely required for JTAG on a AM335X? Nov 09 08:06:43 I'm working on a board which doesn't seem to have these routed to pads, whereas the rest are (TCK, TDI ...) Nov 09 08:06:49 WHat are they supposed to do? I don't remember using those Nov 09 08:06:59 but there are 4.7k pullups close Nov 09 08:07:27 I think last time I used JTAG on the AM335x, I used a standard digilent HS1 Nov 09 08:07:34 6-pin JTAG Nov 09 08:07:40 I'm not sure what they're used for, most (simple) embedded chips I've seen don't have these Nov 09 08:07:55 I've got an XDS100v2 Nov 09 08:08:29 I never used those Nov 09 08:09:11 mostly because they didn't play too nice with openocd. Or not as nice as the digilent Nov 09 08:09:18 Best thing to do is try and see if it works without EMU0/1 Nov 09 08:10:24 strange thing is they might be pulled up correctly (cannot really tell thanks to the BGA package), I just didn't find the corresponding pads Nov 09 08:11:01 yeah I'll try as is first, thanks Nov 09 09:03:33 doesn't seem to work without E0/E1 Nov 09 09:03:51 which software do you recommend with XDS100v2 ? Nov 09 09:04:01 did you use openocd, or crap composer studio? Nov 09 09:04:06 I used CCS Nov 09 09:04:17 which I guess is crap then Nov 09 09:04:34 it's based on eclipse Nov 09 09:04:41 alternatively I've got a SEGGER somewhere, AM335x is probably supported Nov 09 09:04:43 that says it all Nov 09 09:05:14 I would try openocd Nov 09 09:05:18 being eclipse doesn't say much about the JTAG connection code which is all I care about Nov 09 09:05:59 eclipse is the absolute worst development environment I have ever seen Nov 09 09:06:18 I would see if openocd can run a basic GDB server with the XDS100 Nov 09 09:07:11 I don't think ccs has too many options for configuring the JTAG adapters. It's whatever TI deemed to support at the time Nov 09 09:07:30 you might have better luck with openocd, if you're willing to spend the time Nov 09 09:07:35 higher learning curve though Nov 09 09:07:48 heh, it's TI software with a TI JTAG and a TI chip sooooo I hope *this* works Nov 09 09:08:03 It's not a portable solution Nov 09 09:08:09 if I'm desperate enough I'll try your way ;) Nov 09 09:08:29 * mrnuke remembers the time he had to port a whole SW infrastructure from CCS to ARC Nov 09 09:09:05 actually, I didn't. I just ran linux on the ARC, and tolf Nov 09 09:09:14 told my client to port it to userspace Nov 09 09:13:13 problem with CCS is vendor lock-in, and it's pretty effective Nov 09 09:13:46 unless you use GCC instead of TICC, you'll have a hell of a time porting things to anything other than a TI ARMv7 AM33xx chip Nov 09 09:14:53 I don't really need a dev toolchain, I'm just hacking the board and usually compile my exploits using buildroot Nov 09 16:32:50 gquere: I assume you've seen this -> http://processors.wiki.ti.com/index.php/Debug_Handbook_for_CCS Nov 09 18:47:41 Hello. I have received the BBB today. I have istalled the drivers (using a MacBook) following the START.htm file but I can´t see a network connection. The BBB is not listed. Nov 09 19:36:32 gquere: EMU0/1 are not that important, they're for pretty specialized stuff Nov 09 19:39:38 their main uses are wait-in-reset mode (power-on-reset with EMU0 held low), cross-triggering for debugging multi-SoC boards, system trace output (optionally combined with EMU2/3/4 for extra bandwidth) Nov 09 19:39:50 Hello. I have installed the Beagle Bone Black drivers but the network connection is not being created and I can´t see the Beagle listed under Network on my Mac. What to do? Nov 09 19:40:18 highly recommend using a regular ethernet cable, personally. that may not be the answer you're looking for, i'm sorry. Nov 09 19:40:54 Guest86137: hmm, I thought that the latest bbb images worked on Mac even without installing any drivers, but I'm not sure Nov 09 19:41:53 if you're not running a recent image, consider reflashing the bbb Nov 09 19:44:43 I´ll try. Thank you. Nov 09 19:58:30 does anyone know how I can create my own .img.xs beaglebone images by cloning an sd card, like the ones you download from the beaglebone latest-releases page? So far I can use cc to clone to a .dmg but that's not compatible with their Etcher tool Nov 09 19:58:44 *dd not cc Nov 09 20:06:37 and .img.xz not .img.xs Nov 09 20:36:18 got it: Nov 09 20:36:30 sudo dd if=/dev/disk2 | xz > BBG.img.xz Nov 10 00:55:42 Hello! Nov 10 00:56:09 Did anyone answer about capes and the Cape Overlay section for the Motor Bridge Cape? Nov 10 00:59:51 Hold on...paste bin on its way. Nov 10 01:12:35 I have a damn flickr.com account to show photos of my pin mux on a BBG that works w/ the MBC and a BBB that does not work w/ the MBC. Nov 10 01:12:36 ... Nov 10 01:12:46 Here: https://www.flickr.com/photos/poor_pill/38242521686/in/dateposted-public/ Nov 10 01:12:48 ... Nov 10 01:13:04 I am looking to figure out exactly what is wrong. If you want to play along, get at me. Cool! Nov 10 01:15:26 There is some type of pin mux differences. These differences are prompting my BBB to not work w/ this specific Cape. Nov 10 01:15:54 I bet it all on this factoid. Nov 10 01:21:15 Okay...I am wrong as usual. Nov 10 01:22:55 GPIO_115 is a PRU pin in a specific setting but I think w/ this cape, they use it as a reset pin for the Cape. Nov 10 01:24:39 hence...I am damn wrong again. Please hold. Nov 10 01:32:17 P9_23 is my reset pin. Sorry. Nov 10 01:33:11 So, how, if the two, separate boards (BBB and BBG) show the same pin mux, could one work while the other does not work? Nov 10 01:33:17 ... Nov 10 01:33:22 https://github.com/Seeed-Studio/MotorBridgeCapeforBBG_BBB/blob/master/BBG_MotorBridgeCape/MotorBridge.py Nov 10 01:33:48 ... ^ This hyperlink is the Python module/library. Nov 10 01:35:07 Unless, I was sold a different board when I ordered the Rev. C but my pin mux still states what it states. Nov 10 01:35:32 ... Nov 10 01:35:41 <<<< finally calming down. Nov 10 01:45:29 Error accessing Ox4B: Check your I2C Address Nov 10 01:45:44 ^ this is the error when running the correct software Nov 10 01:46:27 any pointers? Nov 10 01:57:57 I tried config-pin p9.23 i2c and notta-bean so far. Invalid mode: i2c Nov 10 01:59:28 P9_23 Mode: default Direction: in Value: 0 is a read-out after config-pin -q p9.23. **** ENDING LOGGING AT Fri Nov 10 02:59:59 2017