Just for informational purposes here is that one pin in my custom overlay:
. . .
> exclusive-use =
> /* the pin header uses */
> "P8.11",
> . . .
> /* P8_11 (ZCZ ball R12) */
> P8_11_default_pin: pinmux_P8_11_default_pin {
> pinctrl-single,pins = <0x034 0x27>; }; /* Mode 7,
> Pull-Down, RxActive */
> . . .
> fragment@1 {
> target = <&ocp>;
> __overlay__ {
>
> P8_11_pinmux {
> compatible = "bone-pinmux-helper";
> status = "okay";
> pinctrl-names = "default";
> pinctrl-0 = <&P8_11_default_pin>;
> };
> . . .
>
> P8_11 {
> gpio-name = "P8_11";
> gpio = <&gpio1 13 0>;
> input;
> dir-changeable;
> };
> . . .
Then the P8.26 1-wire overlay is exactly the same as the one example 1-wire
overlay included with the stock image. But I changed the pin configuration
to match P8.26 instead of what was it ? P9.12 was it ? No idea why I'm
getting that boot message, and this is the first time I've ever seen it.
On Wed, Jan 18, 2017 at 1:39 PM, William Hermans <yyrk...@gmail.com> wrote:
> The error I noticed on my end was: *libfdt fdt_check_header():
> FDT_ERR_BADMAGIC* Which did not really make sense to me as the overlays
> seems to work just fine. I did not check everythign with my overlays, but I
> did check gpio45, and according to the direciton, and value files it's
> configured correctly. But I was getting some odd boot log error message
> about the capemgr back peddling a non existent pin conflict. From where it
> came, I have no idea.
>
> beaglebone login: [ 19.548440] omap-sham 53100000.sham: initialization
>> failed.
>> [ 19.880445] pinctrl-single 44e10800.pinmux: pin 44e10834.0 already
>> requested by ocp:P8_11_pinmux; cannot claim for onewire
>> [ 19.921657] pinctrl-single 44e10800.pinmux: pin-13 (onewire) status -22
>> [ 20.000724] pinctrl-single 44e10800.pinmux: could not request pin 13
>> (44e10834.0) from group pinmux_P8_11_default_pin on device pinctrl-single
>> [ 20.093995] w1-gpio onewire: Error applying setting, reverse things
>> back
>>
>
> That's another error message I've been noticing lately. omap_sham
> initialization failing. But when I take a look at the output of lsmod . . .
> *root@beaglebone:~#* lsmod |grep omap
> omap_aes 13637 0
> omap_rng 4572 0
> omap_sham 21458 0
> rng_core 7390 1 omap_rng
>
> It seems to have loaded fine ? So I'm guessing omap_sham is related to SHA
> somehow, and thus probably important. Not sure why this error message
> though :/
> I'm also assuming it's fine since it's already loaded, but . . .I'm not
> 100% positive.
>
> On Wed, Jan 18, 2017 at 1:29 PM, Robert Nelson <robertcnel...@gmail.com>
> wrote:
>
>> On Wed, Jan 18, 2017 at 2:24 PM, William Hermans <yyrk...@gmail.com>
>> wrote:
>> > Not enough memory allocated ?
>>
>> Correct by default it was only 4k, defaulted to 0x60000
>>
>> seems to have fixed the big overlays...
>>
>> https://github.com/RobertCNelson/Bootloader-Builder/commit/6
>> f3929a577056d10a7994252aa521835bf3f3984
>>
>> Regards,
>>
>> --
>> Robert Nelson
>> https://rcn-ee.com/
>>
>> --
>> 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 beagleboard+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit https://groups.google.com/d/ms
>> gid/beagleboard/CAOCHtYiu5hnmwr23woC5ST6X7HR2KJA8%2BfQkaA8U_
>> %3DpaGkO%2BBA%40mail.gmail.com.
>> 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 beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/beagleboard/CALHSORojFT8bfr2%3DQ%3DYVjT0k93TnkEs_N2xhLiQsW_2BSNr71Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
