00:09 <set_> and again!

00:10 <set_> If no one will answer me, I shall run through 'em all!

00:13 <set_> I am not blaming you guys/gals. I am the only person on the TI and ARM forums right now...

00:13 <set_> Ha.

00:13 <set_> Can I hear the utterance of winner?

00:13 <set_> Ya boy!

00:17 <set_> So, instead of friends and family gathering for the 4th, I am building a wonder of libs. into this BBAI-64.

00:19 <set_> I have to remember this time, "One thing at a time when building." Last time, three terminals and each of them building something new simultaneously created concern for my better being. So, small steps.

09:33 <aussetg> Is there any way to check directly ? I have an ai64 if you want me to check and tell me what to run

09:39 <zmatt> check what?

09:43 <zmatt> set_: arm64-v8a

15:49 <Guest4455> I've got 3.3v running to jumpers on P8_30, P8_32, P8_34, and P8_36 to indicate some configuration depending on which of those is actually jumpered.

15:50 <Guest4455> It was working yesterday, but today, having a jumper on P8_32 messes with the serial console display turning all text to garbage.

15:51 <Guest4455> If I jumper any of the other pins, it's fine.  It's just a jumper on P8_32 that causes problems.  Any idea why?

15:52 <Guest4455> For the record I'm using a DTB file built from am335x-bonegreen.dts on a Beaglebone Black, so that I can more easily use all those HDMI pins.

16:04 <zmatt> Guest4455: P8.31-46 are strapping options for the SoC, and many of them need to have specific values at power-on-reset

16:05 <zmatt> which is accomplished by 100 kΩ pull-up/down resistors on the board

16:05 <zmatt> see https://goo.gl/Jkcg0w#gid=1847985463

16:13 <zmatt> Guest4455: and it would be better to just disable HDMI if you don't need it rather than using the wrong base dts (even if it's very similar), e.g.: https://pastebin.com/hRCZBwFA

16:15 <zmatt> I'm assuming you're using yocto or something? (since on beagleboard.org debian images you'd normally use either cape-universal or a DT overlay rather than a fully custom dts)

16:20 <Guest4455> Yes, I'm using buildroot.

16:20 <zmatt> as for why pulling up P8.32 caused a garbled serial console... P8.31+32 are sysboot14+15 which tell bootrom what crystal is used for the main oscillator, and by pulling P8.32 high (at power-on) you're telling bootrom the crystal is 26 MHz (rather than its true value of 24 MHz). bootrom and u-boot will configure the PLLs based on that information, resulting in all clocks on the system being about 7.7% ...

16:20 <zmatt> ...too slow

16:20 <zmatt> which will run just fine, but obviously mess up every communications interface

16:23 <zmatt> ok, if you're using a debian system you can omit lines 3-5 of https://pastebin.com/hRCZBwFA ... or leave them, they have no actual effect, it's just a convention to make it easy to tell (by inspecting /proc/device-tree/chosen/base_dtb) which dtb has been loaded

16:24 <zmatt> *if you're using a non-debian system

16:26 <Guest4455> Great.  Thanks for that, and that spreadsheet.

16:26 <zmatt> np

16:27 <zmatt> if you're curious what the other sysboot strapping options do, see the Boot tab of that spreadsheet