**** BEGIN LOGGING AT Tue Oct 15 02:59:57 2019 Oct 15 03:02:04 GenTooMan: not enough over-25s in software these days :/ Oct 15 03:07:37 or those that are have short memories ;D Oct 15 10:50:31 help me with BB Oct 15 12:22:23 No. :] Oct 15 12:47:53 veremitz awesome deny Oct 15 13:04:26 :D Oct 15 13:04:34 #denied :p Oct 15 14:10:40 zmatt, fbdev is used over modesetting due to a nice lockup bug when you open any png or jpg image, back in wheezy/jessie. something hardlocks the core.. i'd love to see if that's been fixed.. Oct 15 14:28:23 that sounds really bizare Oct 15 14:28:26 *bizarre Oct 15 15:01:28 what's bizarre... it locks up the jtag port. ;) we first found it when we firsted switch to debian by default.. every once in a awhile i recheck... Oct 15 15:13:52 m Oct 15 16:12:21 rcn-ee[m]: could be a bus lockup e.g. due to a protocol error Oct 15 16:14:19 rcn-ee[m]: do you have exact steps I can follow to reproduce? if I find a moment I could see if I can figure anything out Oct 15 16:14:58 e.g. via JTAG but making sure to not attach to the core but just carefully poke around via DAP **** BEGIN LOGGING AT Tue Oct 15 18:01:41 2019 Oct 15 20:18:57 Hello All, I have a question on the FAT Formatting when booting a BBB from an SD Card. I've read some forums and documentation from Beaglebone, and some mention FAT16 while others FAT32. I'm using a >2GB SD card so I'm leaning towards utilizing FAT32 rather than FAT16 for formatting the boot partition, but i'm looking for confirmation about this. Oct 15 20:18:58 That the boot formatting is based on the Size of the SD Card rather than a fixed "rule" that has to be followed. Oct 15 20:21:45 BAR43: the bootrom also supports fat12.. Oct 15 20:23:18 You can use either, the bootrom won't care, just use what works best for you.. Oct 15 20:24:46 yea, but that really no longer applies (not unless you somehow have a 16 MB SD card handy). Oct 15 20:25:36 the bootrom isn't the issue. my question is tied closer to whether it's best to use FAT16 for a >4GB SD Card Oct 15 20:26:21 especially since FAT16 doesn't support volume sizes >2GB. Oct 15 20:26:36 if it's best to use FAT16 for the boot partition Oct 15 20:30:32 BAR43: use fat32 Oct 15 20:33:13 But since your using a BBB, pick either ext or btrfs, no reason to use a real fat partition.. just make a virtual fat, then you don't have to worry about corrupting the BBB's fat partition with u-boot in it. Oct 15 20:36:12 never thought of doing that..... cool thanks! Oct 15 21:01:50 zmatt: earlier today you pointed me to how to use the BeagleBone-AI with your py-uio library. You say to #include dra7-uio-pruss.dtsi into your dts and recompile the dtb. Oct 15 21:02:26 I can find the location of the dtb files on the BeagleBone AI, but I'm not able to find any .dtsi files on the BBAI. Oct 15 21:04:21 Someone pointed me to this repo: https://github.com/beagleboard/BeagleBoard-DeviceTrees So does this mean I need to download the .dtsi files from here and compile them? Oct 15 21:43:52 hunter2018: use the dtb-rebuilder repo.... I think it should already be at /opt/source/dtb-4.14-ti/ Oct 15 21:44:27 if not, clone it from https://github.com/RobertCNelson/dtb-rebuilder/ and if necessary switch to the branch corresponding to the kernel series you're using (which I think is still 4.14-ti, which should be the default branch) Oct 15 21:44:39 dtb-rebuilder is dead for v4.14.x+ ;) Oct 15 21:44:56 it all got moved to github.com/beagleboard/ ;) Oct 15 21:45:35 github.com/beagleboard/what? Oct 15 21:45:59 https://github.com/beagleboard/BeagleBoard-DeviceTrees/tree/v4.14.x-ti Oct 15 21:46:13 oh the repo hunter2018 actually found Oct 15 21:46:38 okay so this is still just dtb-rebuilder, just under a different name Oct 15 21:47:25 yeap, and beagleboard.org admin's can easily push changes/etc.. For AI stuff, nothing been backported to the old dtb-rebuilder.. Oct 15 21:49:10 So is the proper practice to clone the repo to the BBAI and then somehow compile the file BeagleBoard-DeviceTrees/src/arm/am5729-beagleboneai.dts after adding the #include dra7-uio-pruss.dtsi line to it? Oct 15 21:49:30 I mean to clone the device tree repo. Oct 15 21:49:30 no, don't do that Oct 15 21:50:11 it's better create your own .dts file, #include "am5729-beagleboneai.dts", append your customizations, compile that dtb and configure it in /boot/uEnv.txt Oct 15 21:50:15 *to create Oct 15 21:50:50 * rcn-ee[m] sent a long message: < https://matrix.org/_matrix/media/r0/download/matrix.org/AqpVpkeTAXNBcHwnViDHQoKz > Oct 15 21:51:54 rcn-ee[m]: so why is this a completely new repo instead of being a continuation of dtb-rebuilder? Oct 15 21:52:19 more generally, what was the reason for this change? Oct 15 21:53:25 Less maintenance for me, and the org could do what they wanted when i was too busy to help.. Oct 15 21:57:25 zmatt and rcn-ee[m] thanks for the help! Oct 15 21:57:28 So this isn't a Oct 15 21:57:57 device tree overlay, I need to actually rebuild the device tree itself, the "base one" Oct 15 22:06:29 yeah Oct 15 22:07:48 rcn-ee[m]: is there any obstacle to porting overlay support to the x15/ai u-boot, to allow users to configure custom overlays in /boot/uEnv.txt ? **** ENDING LOGGING AT Wed Oct 16 02:59:57 2019