Yeah, no problem. let me know how that works out. For the record, I suck with device tree files too . . . it seems very counter intuitive. Well I mean if you're a C programmer, the "syntax" is very odd. And I have not really found a decent write up of how it works. Bill King and Panto had a google doc on the subject a couple years back, but unfortunately the document for me was not concise enough.
But I'm sure it makes better sense to people who are used to hardware stuff ? On Sun, Aug 2, 2015 at 4:05 PM, Rick Mann <[email protected]> wrote: > Thanks! > > > On Aug 2, 2015, at 13:02 , William Hermans <[email protected]> wrote: > > > > This post here, Jen S' post > > > > > https://groups.google.com/forum/#!searchin/beagleboard/sdcard$20device$20tree/beagleboard/fOGeXCub9OY/lSNBcjpLvgkJ > > > > > > On Sun, Aug 2, 2015 at 12:57 PM, William Hermans <[email protected]> > wrote: > > Rick, I forget the steps, but last year, or even before that someone on > the groups showed how to use the device tree compiler to decompile a blob > file. So if you have the dtb for Angstrom, it should be decompilable. > > > > The post in question was in relation to the sdcard operating in 2bit > mode ? versus 4bit. But maybe someone else here recalls how to decompile > dt's using the device tree compiler ? > > > > Then if you can not get your hands on a device tree compiler old enough. > I do have several images ( including original Angstrom- updated to 3.8.8 ) > that should do the trick. SO at minimum if i can remember how, and had the > binary file i could decompile it myself, and give you a pastebin link to > the source. > > > > On Sun, Aug 2, 2015 at 12:51 PM, Rick Mann <[email protected]> > wrote: > > Thanks, William. > > > > Yeah, I saw that post. I've also emailed them for support. I could try > to fix it myself, but despite much time invested, I just don't "get" DTBs > (and I've written a lot of code on a lot of different platforms, and > designed and built boards around a lot of different MCUs). Their DTB source > doesn't seem to be available (I've asked for that, too), so I'd have to > make one from scratch. > > > > They don't have a proper schematic that I can find, but they do show the > GPIO and ADC pins used ( > https://docs.google.com/document/d/1XQtcoCa3WckPbJZpxYE6ueTVv-GCCfnqHIo7_dZ5UUs/edit, > page 4). This might be a good Cape for me to finally learn how to write an > overlay, but I feel completely helpless and don't even know where to begin. > > > > > On Aug 2, 2015, at 12:43 , William Hermans <[email protected]> wrote: > > > > > > Rick, have you read this yet ? > http://inspire.logicsupply.com/2014/06/relay-cape.html > > > > > > Particularly the comments. Seems they are unconcerned with making it > work with Debian. Which I would think would be fairly easy once one knows > how to muck around in device tree blobs. But hey, I'm not the one trying to > sell this product ;) > > > > > > Three options I can see, short of finding some one who has already > "ported" the device tree to debian. > > > > > > 1). Ask for your money back. > > > 2) Ask them to fix the problem. > > > 3) Fix it yourself . . . > > > > > > It's been quite a while since the BBB's have been shipped with > Angstrom. Yet they're still selling the product. Personally I think this is > on them to fix. *If* they expect to capitalize on this product. But maybe > reassigning a pin, or a few pins would be trivial for someone ? > > > > > > On Sun, Aug 2, 2015 at 12:20 PM, Rick Mann <[email protected]> > wrote: > > > I just got a Logic Supply Relay Cape, and I'm trying it out with a > recent Debian. I put their supplied .dtbo file in /boot/dtbs/3.8.13-bone70. > I disabled HDMI and tried to enable the cape, and I get this at boot: > > > > > > Uncompressing Linux... done, booting the kernel. > > > [ 0.337870] omap2_mbox_probe: platform not supported > > > [ 0.492868] tps65217-bl tps65217-bl: no platform data provided > > > [ 0.577268] bone-capemgr bone_capemgr.9: slot #1: No cape found > > > [ 0.614377] bone-capemgr bone_capemgr.9: slot #2: No cape found > > > [ 0.651486] bone-capemgr bone_capemgr.9: slot #3: No cape found > > > [ 0.669029] bone-capemgr bone_capemgr.9: slot #7: CBB-Relay > conflict P8.26 (#0:CBB-Relay) > > > [ 0.677638] bone-capemgr bone_capemgr.9: slot #7: Failed > verification > > > [ 0.684383] bone-capemgr bone_capemgr.9: loader: failed to load > slot-7 CBB-Relay:00A0 (prio 0) > > > [ 0.696333] bone-iio-helper CBB-Relay-ain.17: Could not get AIN1 > analog input > > > [ 0.708964] omap_hsmmc mmc.5: of_parse_phandle_with_args of 'reset' > failed > > > [ 0.772848] pinctrl-single 44e10800.pinmux: pin 44e10854 already > requested by 44e10800.pinmux; cannot claim for gpio-leds.8 > > > [ 0.784533] pinctrl-single 44e10800.pinmux: pin-21 (gpio-leds.8) > status -22 > > > [ 0.791815] pinctrl-single 44e10800.pinmux: could not request pin > 21 on device pinctrl-single > > > > > > Clearly I'm missing something, and googling has turned up nothing on > how to use it with debian. I also can't seem to find Logic Supply's github > repo for it. > > > > > > Has anyone made this work with Debian? Thanks! > > > > > > > > > -- > > > Rick Mann > > > [email protected] > > > > > > > > > -- > > > For more options, visit http://beagleboard.org/discuss > > > --- > > > You received this message because you are subscribed to the Google > Groups "BeagleBoard" group. > > > To unsubscribe from this group and stop receiving emails from it, send > an email to [email protected]. > > > For more options, visit https://groups.google.com/d/optout. > > > > > > > > > -- > > > For more options, visit http://beagleboard.org/discuss > > > --- > > > You received this message because you are subscribed to the Google > Groups "BeagleBoard" group. > > > To unsubscribe from this group and stop receiving emails from it, send > an email to [email protected]. > > > For more options, visit https://groups.google.com/d/optout. > > > > > > -- > > Rick Mann > > [email protected] > > > > > > -- > > For more options, visit http://beagleboard.org/discuss > > --- > > You received this message because you are subscribed to the Google > Groups "BeagleBoard" group. > > To unsubscribe from this group and stop receiving emails from it, send > an email to [email protected]. > > For more options, visit https://groups.google.com/d/optout. > > > > > > > > -- > > For more options, visit http://beagleboard.org/discuss > > --- > > You received this message because you are subscribed to the Google > Groups "BeagleBoard" group. > > To unsubscribe from this group and stop receiving emails from it, send > an email to [email protected]. > > For more options, visit https://groups.google.com/d/optout. > > > -- > Rick Mann > [email protected] > > > -- > For more options, visit http://beagleboard.org/discuss > --- > You received this message because you are subscribed to the Google Groups > "BeagleBoard" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
